make sure osmo-hnbgw re-connects dynamically
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.
- Assignee changed from Osmocom CNI Developers to sysmocom
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...
- Assignee changed from sysmocom to lynxis
lynxis: Is thre any known issue with current osmo-hnbgw to fail to reconnect to MSC or SGSN?
I don't know any recent issues here. The problems I had, which you might refer to, were a problem of the STP daemon.
- Status changed from New to Closed
Also available in: Atom