Project

General

Profile

Actions

Feature #2264

closed

make sure osmo-hnbgw re-connects dynamically

Added by neels almost 7 years ago. Updated over 5 years 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 VoiceClosed05/14/2016

Actions
Actions #1

Updated by neels almost 7 years ago

Actions #2

Updated by laforge over 6 years ago

  • Assignee changed from 118 to 4368
Actions #3

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...

Actions #4

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?

Actions #5

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.

Actions #6

Updated by laforge over 5 years ago

  • Status changed from New to Closed
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)