https://osmocom.org/https://osmocom.org/favicon.ico?16647414092020-08-11T21:05:23ZOpen Source Mobile CommunicationsCellular Network Infrastructure - Feature #4701: implement OsmoSTP notification of peers disconnecting, e.g. for OsmoBSC to detect that a specific MSC in the pool is disconnectedhttps://osmocom.org/issues/4701?journal_id=193052020-08-11T21:05:23Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-1 priority-3 priority-high3" href="/issues/2623">Feature #2623</a>: SCCP/M3UA: detect restart of osmo-msc and osmo-sgsn</i> added</li></ul> 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 disconnectedhttps://osmocom.org/issues/4701?journal_id=193072020-08-11T21:05:33Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-3 priority-3 priority-high3 closed" href="/issues/4619">Bug #4619</a>: ttcn3-bsc-test: all LCLS test cases broken since build #987</i> added</li></ul> 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 disconnectedhttps://osmocom.org/issues/4701?journal_id=201942020-10-28T23:02:54Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-7 priority-1 priority-lowest" href="/issues/4832">Bug #4832</a>: osmo-bsc hard-releases lchan if no MSC is found</i> added</li></ul> 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 disconnectedhttps://osmocom.org/issues/4701?journal_id=212082021-02-07T12:55:52Zlaforge
<ul><li><strong>Assignee</strong> set to <i>neels</i></li></ul><p>I've implemented notification of SCCP users via the SCCP-User SAP in <a class="external" href="https://gerrit.osmocom.org/c/libosmo-sccp/+/22778">https://gerrit.osmocom.org/c/libosmo-sccp/+/22778</a></p>
<p>This means that every time a [remote] point code becomes available or unavailable, the SCCP user application (MSC, BSC, SGSN, SMLC, ...) should now receive a N-PCSTATE.ind stating the "affected point code". and either <br />sp_status OSMO_SCCP_SP_S_INACCESSIBLE or OSMO_SCCP_SP_S_ACCESSIBLE.</p>
<p>This indication should then be used by the applications to trigger whatever internal logic that needs to happen if a remote point-code disappears or re-appears. I'll leave that part to <a class="user active" href="https://osmocom.org/users/91">neels</a>. I'll just implement some tests to ensure we get those notifications as expected now.</p> 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 disconnectedhttps://osmocom.org/issues/4701?journal_id=212612021-02-11T11:42:46Zlaforge
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><ul>
<li>We have MTP-level notifications by means of M3UA DUNA/DAVA in place now, as shown by the below three test cases
<ul>
<li>TC_ssnm_aspac_dava_aspia_duna</li>
<li>TC_ssnm_distribution_dava_duna</li>
<li>TC_ssnm_distribution_dava_duna_multipc</li>
</ul>
</li>
<li>those are now reported via N-PCSTATE primitives on the SCCP user SAP</li>
</ul>
<p>There's some additional work in the pipeline to also provide separate notifications of SSN availability, etc. but none of that would strictly fall within the scope of this specific issue. Marking it resolved.</p>