https://projects.osmocom.org/https://projects.osmocom.org/favicon.ico?16647414092019-09-10T11:56:45ZOpen Source Mobile CommunicationsOsmoBSC - Support #4057: verify that re-using ARFCN+BSIC pairs within a BSS workshttps://projects.osmocom.org/issues/4057?journal_id=159042019-09-10T11:56:45Zlaforge
<ul><li><strong>Assignee</strong> changed from <i>neels</i> to <i>osmith</i></li></ul> OsmoBSC - Support #4057: verify that re-using ARFCN+BSIC pairs within a BSS workshttps://projects.osmocom.org/issues/4057?journal_id=159202019-09-11T12:16:27Zosmith
<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><p><a class="user active" href="https://projects.osmocom.org/users/91">neels</a> replaced the mentioned function bts_by_neighbor_ident() with a new function find_handover_target_cell(), that resolves exactly this problem:<br /><a class="external" href="https://gerrit.osmocom.org/c/osmo-bsc/+/14769">https://gerrit.osmocom.org/c/osmo-bsc/+/14769</a></p>
<p>You've also added a related test already, "f_tc_ho_neighbor_config_3":<br /><a class="external" href="https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/14765/3/bsc/BSC_Tests.ttcn#3791">https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/14765/3/bsc/BSC_Tests.ttcn#3791</a></p>
<blockquote>
<p>HO to bts 2 works, explicitly listed as neighbor; no ambiguity because bts 3 is not listed as neighbor</p>
</blockquote> OsmoBSC - Support #4057: verify that re-using ARFCN+BSIC pairs within a BSS workshttps://projects.osmocom.org/issues/4057?journal_id=159752019-09-16T14:24:06Zneelsnhofmeyr@sysmocom.de
<ul></ul><p>that's accurate. Apologies, it seems I failed to update this issue back then :/</p>