Project

General

Profile

Actions

Feature #2623

open

SCCP/M3UA: detect restart of osmo-msc and osmo-sgsn

Added by neels about 5 years ago. Updated almost 2 years ago.

Status:
New
Priority:
High
Assignee:
Target version:
-
Start date:
11/07/2017
Due date:
% Done:

50%

Spec Reference:

Description

Connecting osmo-bsc and osmo-hnbgw to the MSC and SGSN via an OsmoSTP instance, it is currently not possible to detect that the MSC or SGSN has restarted.

Scenario: using a sysmoBTS as a NITB, change MSC config, restart MSC -- now osmo-bsc happily continues to run and does not even notice that it is an entirely new MSC instance running in the core net now.

In the old days, the SCCPlite link would go down, but since now OsmoSTP is in-between and has no concept of who depends on who, no-one is notifying BSC or HNBGW that MSC or SGSN have gone down. Find out how this is intended to be solved if at all, and devise a way how osmo-bsc will restart and/or reconnect to a new MSC instance, and so forth.


Related issues

Related to OsmoSGSN - Bug #3403: osmo-sgsn doesn not connect properly with via SCCP when restartedNewlynxis07/17/2018

Actions
Related to Cellular Network Infrastructure - Feature #4701: implement OsmoSTP notification of peers disconnecting, e.g. for OsmoBSC to detect that a specific MSC in the pool is disconnectedResolvedneels08/11/2020

Actions
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)