https://osmocom.org/https://osmocom.org/favicon.ico?16647414092019-06-27T10:02:48ZOpen Source Mobile CommunicationsOsmoBSC - Bug #4078: osmo-bsc: Sends duplicated BSSMAP Clear Request upon HO failure (TC_ho_out_fail_no_ho_detect)https://osmocom.org/issues/4078?journal_id=150052019-06-27T10:02:48Zpespin
<ul><li><strong>Subject</strong> changed from <i>osmo-bsc: Sends duplicated BSSMAP Clear Request uponh HO failure (TC_ho_out_fail_no_ho_detect)</i> to <i>osmo-bsc: Sends duplicated BSSMAP Clear Request upon HO failure (TC_ho_out_fail_no_ho_detect)</i></li></ul> OsmoBSC - Bug #4078: osmo-bsc: Sends duplicated BSSMAP Clear Request upon HO failure (TC_ho_out_fail_no_ho_detect)https://osmocom.org/issues/4078?journal_id=150662019-07-04T13:12:37Zpespin
<ul><li><strong>Assignee</strong> changed from <i>pespin</i> to <i>neels</i></li></ul> OsmoBSC - Bug #4078: osmo-bsc: Sends duplicated BSSMAP Clear Request upon HO failure (TC_ho_out_fail_no_ho_detect)https://osmocom.org/issues/4078?journal_id=150672019-07-04T13:13:55Zpespin
<ul></ul><p>TTCN3 tests were merged, so this issue already shows up in jenkins runs.</p> OsmoBSC - Bug #4078: osmo-bsc: Sends duplicated BSSMAP Clear Request upon HO failure (TC_ho_out_fail_no_ho_detect)https://osmocom.org/issues/4078?journal_id=150892019-07-08T12:30:01Zneelsnhofmeyr@sysmocom.de
<ul></ul><p>One underlying aspect to consider is that the BSSMAP Clear Request from the BSC is not imperative.<br />The BSC can send Clear Requests as much as it likes, the MSC is the one that decides to send a Clear Command when it sees fit.<br />So theoretically, it is not really an error to send more Clear Requests than strictly necessary.</p>
<p>On the other hand, if the BSC has one cause to want a Clear, it should ideally send only one Request, of course.</p>
<p>In fact we could adjust the ttcn3 to be fine with N Clear Requests from the BSC.<br />Making the BSC send only one Clear Request would, strictly speaking, be a kind of "cream on top".</p>
<p>In practice though it might be less effort to simply make the BSC send only one Clear Request.<br />So that's what I am going to investigate now.</p> OsmoBSC - Bug #4078: osmo-bsc: Sends duplicated BSSMAP Clear Request upon HO failure (TC_ho_out_fail_no_ho_detect)https://osmocom.org/issues/4078?journal_id=150902019-07-08T12:30:10Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li></ul> OsmoBSC - Bug #4078: osmo-bsc: Sends duplicated BSSMAP Clear Request upon HO failure (TC_ho_out_fail_no_ho_detect)https://osmocom.org/issues/4078?journal_id=150932019-07-08T14:31:39Zneelsnhofmeyr@sysmocom.de
<ul></ul><p>...actually, if a handover out of the BSC fails, the lchan should just continue as before.<br />Need to take a closer look at that test.</p> OsmoBSC - Bug #4078: osmo-bsc: Sends duplicated BSSMAP Clear Request upon HO failure (TC_ho_out_fail_no_ho_detect)https://osmocom.org/issues/4078?journal_id=150942019-07-08T15:40:44Zneelsnhofmeyr@sysmocom.de
<ul></ul><p>got a patch coming up to remove the double clear.<br />Created a new issue for the failure to continue on the old lchan for failed inter-BSC-out HO: <a class="issue tracker-1 status-6 priority-2 priority-default closed" title="Bug: osmo-bsc closes lchan after inter-BSC HO out of the current BSC times out, instead should continu... (Rejected)" href="https://osmocom.org/issues/4093">#4093</a></p> OsmoBSC - Bug #4078: osmo-bsc: Sends duplicated BSSMAP Clear Request upon HO failure (TC_ho_out_fail_no_ho_detect)https://osmocom.org/issues/4078?journal_id=150952019-07-08T16:53:59Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>% Done</strong> changed from <i>0</i> to <i>90</i></li></ul><p><a class="external" href="https://gerrit.osmocom.org/c/osmo-bsc/+/14700">https://gerrit.osmocom.org/c/osmo-bsc/+/14700</a></p> OsmoBSC - Bug #4078: osmo-bsc: Sends duplicated BSSMAP Clear Request upon HO failure (TC_ho_out_fail_no_ho_detect)https://osmocom.org/issues/4078?journal_id=169082019-12-16T15:03:06Zneelsnhofmeyr@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>merged a long time ago</p>