Feature #2264
closedmake sure osmo-hnbgw re-connects dynamically
0%
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
Updated by neels over 6 years 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...
Updated by laforge over 5 years ago
- Assignee changed from 4368 to lynxis
lynxis: Is thre any known issue with current osmo-hnbgw to fail to reconnect to MSC or SGSN?
Updated by lynxis over 5 years 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.