https://osmocom.org/https://osmocom.org/favicon.ico?16647414092018-04-04T08:42:36ZOpen Source Mobile CommunicationsOsmoBSC - Bug #3099: dynamic timeslots not tested by BSC_Tests.ttcnhttps://osmocom.org/issues/3099?journal_id=86502018-04-04T08:42:36Zlaforge
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-3 priority-2 priority-default closed" href="/issues/1853">Bug #1853</a>: validate dynamic TCH/PDCH support in osmo-bts-trx</i> added</li></ul> OsmoBSC - Bug #3099: dynamic timeslots not tested by BSC_Tests.ttcnhttps://osmocom.org/issues/3099?journal_id=86562018-04-04T09:49:51Zlaforge
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-3 priority-2 priority-default closed" href="/issues/3131">Bug #3131</a>: dynamic timeslots not tested by BTS_Tests.ttcn</i> added</li></ul> OsmoBSC - Bug #3099: dynamic timeslots not tested by BSC_Tests.ttcnhttps://osmocom.org/issues/3099?journal_id=86632018-04-04T09:54:32Zlaforge
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-1 priority-1 priority-lowest" href="/issues/1902">Feature #1902</a>: unify/refactor dynamic timeslot code</i> added</li></ul> OsmoBSC - Bug #3099: dynamic timeslots not tested by BSC_Tests.ttcnhttps://osmocom.org/issues/3099?journal_id=86672018-04-04T09:55:33Zlaforge
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-3 priority-2 priority-default closed" href="/issues/1841">Bug #1841</a>: Dynamic PDCH / TCH switching assumes RSL link is up</i> added</li></ul> OsmoBSC - Bug #3099: dynamic timeslots not tested by BSC_Tests.ttcnhttps://osmocom.org/issues/3099?journal_id=87102018-04-06T17:01:20Zlaforge
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li><li><strong>Assignee</strong> changed from <i>4368</i> to <i>laforge</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>20</i></li></ul> OsmoBSC - Bug #3099: dynamic timeslots not tested by BSC_Tests.ttcnhttps://osmocom.org/issues/3099?journal_id=87162018-04-07T09:40:33Zlaforge
<ul></ul><p>This is relatively difficult without infrastructural changes in RSL_Emulation.ttcn.</p>
<p>The reason is that, as soon as any TS is a dynamic PDCH, the BSC will send the PDCH activation command immediately upon RSL start-up. At this point, the related chan_nr is not yet (and cannot possibly be) registered with RSL_Emulation, and hence RSL_Emulation fails to dispatch it to the respective ConnHdlr.</p>
Possible options are:
<ul>
<li>suspend processing incoming RSL messages at RSL connection time until the testcase actively enables it, basically delaying the processing of the PDCH ACT messages until we've had a chance to register ConnHdlrs</li>
<li>implement DYN PDCH tests without RSL_Emulation, instead directly on top of a RSL_CodecPort </li>
<li>handle PDCH activation inside RSL_Emulation, similar to how we handle RSL CHAN ACT, keeping the state about the activation somewhere and permitting this state to be accessed via a procedure port.
<ul>
<li>this has the disadvantage that we cannot easily simulate failure scenarios without modifying RSL_Emulation :(</li>
</ul></li>
</ul> OsmoBSC - Bug #3099: dynamic timeslots not tested by BSC_Tests.ttcnhttps://osmocom.org/issues/3099?journal_id=87172018-04-07T17:29:11Zlaforge
<ul><li><strong>% Done</strong> changed from <i>20</i> to <i>80</i></li></ul><p>Initial 4 testcases in <a class="external" href="https://gerrit.osmocom.org/7664">https://gerrit.osmocom.org/7664</a></p>
<p>I chose the option to "go without RSL_Emulation" and use RSL_CodecPort directly.</p> OsmoBSC - Bug #3099: dynamic timeslots not tested by BSC_Tests.ttcnhttps://osmocom.org/issues/3099?journal_id=87182018-04-07T17:30:01Zlaforge
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>80</i> to <i>100</i></li></ul><p>patch merged</p>