https://osmocom.org/https://osmocom.org/favicon.ico?16647414092018-03-28T13:59:09ZOpen Source Mobile CommunicationsOsmoMSC - Bug #3122: fix subscr_conn fsm: safely catch all compl-l3 failures, properly handle all release situationshttps://osmocom.org/issues/3122?journal_id=85812018-03-28T13:59:09Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-3 priority-2 priority-default closed" href="/issues/3062">Bug #3062</a>: osmo-msc crash while running osmo-gsm-tester voice:nanobts</i> added</li></ul> OsmoMSC - Bug #3122: fix subscr_conn fsm: safely catch all compl-l3 failures, properly handle all release situationshttps://osmocom.org/issues/3122?journal_id=86052018-03-29T15:34:19Zpespin
<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 #3122: fix subscr_conn fsm: safely catch all compl-l3 failures, properly handle all release situationshttps://osmocom.org/issues/3122?journal_id=86242018-04-03T00:12:46Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>60</i></li></ul> OsmoMSC - Bug #3122: fix subscr_conn fsm: safely catch all compl-l3 failures, properly handle all release situationshttps://osmocom.org/issues/3122?journal_id=87392018-04-09T01:15:58Zneelsnhofmeyr@sysmocom.de
<ul></ul><p>Testing against the current ttcn3 test suite yields 6 tests being fixed (proper Clear Request / Clear Complete messages now).<br />But a corner case (<a class="issue tracker-1 status-3 priority-2 priority-default closed" title="Bug: osmo-msc crash while running osmo-gsm-tester voice:nanobts (Resolved)" href="https://osmocom.org/issues/3062">#3062</a>) is re-raised by the changes, still need to address that (shouldn't be too hard). It should also be part of the ttcn3 (or at least some) test suite.<br />I would like to get this merged sooner rather than later and get back to inter-bsc HO, but <a class="issue tracker-1 status-3 priority-2 priority-default closed" title="Bug: osmo-msc crash while running osmo-gsm-tester voice:nanobts (Resolved)" href="https://osmocom.org/issues/3062">#3062</a> shows that I need to be patient enough to not break things that had workarounds before.</p>
<p>Also still trying to reproduce <a class="issue tracker-1 status-1 priority-1 priority-lowest" title="Bug: testcase for fixed "osmo-msc crashes while handling a call" (New)" href="https://osmocom.org/issues/3125">#3125</a> in ttcn3, see there. Took me a lot of time to get a simple MNCC REL REQ case going (mostly log interpretation retard: this time I got mixed up between MNCC Alerting vs. DTAP CC Alerting, and then it took forever to figure out that I need to expect an IPACC DLCX + ACK to not run into T_guard...) -- now it still needs to actually trigger the bug instead of succeeding, so that I can see whether the new code fixes the bug.</p> OsmoMSC - Bug #3122: fix subscr_conn fsm: safely catch all compl-l3 failures, properly handle all release situationshttps://osmocom.org/issues/3122?journal_id=88152018-04-11T11:51:01Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Subject</strong> changed from <i>fix subscr_conn fsm: safely catch all compl-l3 failures, properly handle all release situations, handle overlapping CM Service Requests</i> to <i>fix subscr_conn fsm: safely catch all compl-l3 failures, properly handle all release situations</i></li><li><strong>Description</strong> updated (<a title="View differences" href="/journals/8815/diff?detail_id=14013">diff</a>)</li><li><strong>% Done</strong> changed from <i>60</i> to <i>90</i></li></ul><p>waiting for CR on <a class="external" href="https://gerrit.osmocom.org/#/q/status:open+project:osmo-msc+branch:master+topic:fsm_refactor">https://gerrit.osmocom.org/#/q/status:open+project:osmo-msc+branch:master+topic:fsm_refactor</a></p>
<p>I think handling overlapping CM Service Requests should be a separate issue -> <a class="issue tracker-2 status-6 priority-2 priority-default closed" title="Feature: make sure we handle N overlapping CM Service Requests properly (Rejected)" href="https://osmocom.org/issues/3156">#3156</a></p> OsmoMSC - Bug #3122: fix subscr_conn fsm: safely catch all compl-l3 failures, properly handle all release situationshttps://osmocom.org/issues/3122?journal_id=88982018-04-15T20:57:51Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>90</i> to <i>100</i></li></ul><p>all patches are merged now</p>