https://projects.osmocom.org/https://projects.osmocom.org/favicon.ico?16647414092018-03-29T15:34:28ZOpen Source Mobile CommunicationsOsmoMSC - Bug #2880: OsmoMSC never releases MO call if MNCC doesn't respond to SETUPhttps://projects.osmocom.org/issues/2880?journal_id=86072018-03-29T15:34:28Zpespin
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-1 priority-1 priority-lowest" href="/issues/3125">Bug #3125</a>: testcase for fixed "osmo-msc crashes while handling a call"</i> added</li></ul> OsmoMSC - Bug #2880: OsmoMSC never releases MO call if MNCC doesn't respond to SETUPhttps://projects.osmocom.org/issues/2880?journal_id=86272018-04-03T10:46:27Zneelsnhofmeyr@sysmocom.de
<ul></ul><p>There is a patch series coming to refactor the MSC's conn FSM to discard connections as soon as the use count reaches zero.<br />It is worth checking this error separately, i.e. make sure that an MNCC SETUP timeout indeed results in a use count decrement.</p>
<p>The FSM does not handle CC timeouts, that is still done the "old" way within our CC implementation.<br />Might be worth a thought to implement an actual CC FSM as well, as a child of the subscr_conn FSM, with timeouts for each state except the active call.</p> OsmoMSC - Bug #2880: OsmoMSC never releases MO call if MNCC doesn't respond to SETUPhttps://projects.osmocom.org/issues/2880?journal_id=86422018-04-04T08:38:19Zlaforge
<ul><li><strong>Assignee</strong> changed from <i>4368</i> to <i>neels</i></li></ul> OsmoMSC - Bug #2880: OsmoMSC never releases MO call if MNCC doesn't respond to SETUPhttps://projects.osmocom.org/issues/2880?journal_id=108562018-08-20T15:23:18Zneelsnhofmeyr@sysmocom.de
<ul></ul><p>(I'm not that familiar with MNCC setups, maybe someone else could investigate this one?)</p> OsmoMSC - Bug #2880: OsmoMSC never releases MO call if MNCC doesn't respond to SETUPhttps://projects.osmocom.org/issues/2880?journal_id=148572019-06-18T22:04:24Zneelsnhofmeyr@sysmocom.de
<ul></ul><p>(I have since then become familiar with MNCC setups and can indeed investigate this one. Once I get to it.)</p> OsmoMSC - Bug #2880: OsmoMSC never releases MO call if MNCC doesn't respond to SETUPhttps://projects.osmocom.org/issues/2880?journal_id=148582019-06-18T22:23:38Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Resolved</i></li></ul><p>TC_mo_setup_and_nothing passes.<br />I hope that means the issue is resolved.</p>