Project

General

Profile

Feature #2264

make sure osmo-hnbgw re-connects dynamically

Added by neels over 1 year ago. Updated 3 days ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
-
Start date:
05/16/2017
Due date:
% Done:

0%

Spec Reference:

Description

currently, when the MSC and/or SGSN are started after the HNBGW, the connections do not work.
One needs to wait for MSC,SGSN to start up and only then launch the HNBGW. That's really cumbersome.
(Also, the HNBGW does not fail when a connection did not succeed, so it has to be restarted manually)

Make HNBGW reconnect automatically.


Related issues

Related to OsmoNITB - Feature #1712: 3G VoiceClosed2016-05-14

History

#1 Updated by neels over 1 year ago

#2 Updated by laforge about 1 year ago

  • Assignee changed from Osmocom Developers to sysmocom

#3 Updated by neels about 1 year ago

since osmo-hnbgw was changed over to the new M3UA SIGTRAN, re-/connection is now completely a matter of libosmo-sigtran. We can still re-check the status quo and probably just reject this issue...

#4 Updated by laforge 20 days ago

  • Assignee changed from sysmocom to lynxis

lynxis: Is thre any known issue with current osmo-hnbgw to fail to reconnect to MSC or SGSN?

#5 Updated by lynxis 12 days ago

I don't know any recent issues here. The problems I had, which you might refer to, were a problem of the STP daemon.

#6 Updated by laforge 3 days ago

  • Status changed from New to Closed

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)