https://osmocom.org/https://osmocom.org/favicon.ico?16647414092018-07-11T00:15:03ZOpen Source Mobile Communicationslibosmo-sccp + libosmo-sigtran - Bug #3392: SCCPlite: xua_asp_fsm.c hardcodes a routing keyhttps://osmocom.org/issues/3392?journal_id=102822018-07-11T00:15:03Zneelsnhofmeyr@sysmocom.de
<ul></ul> libosmo-sccp + libosmo-sigtran - Bug #3392: SCCPlite: xua_asp_fsm.c hardcodes a routing keyhttps://osmocom.org/issues/3392?journal_id=103182018-07-16T14:12:52Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-3 priority-3 priority-high3 closed" href="/issues/2544">Bug #2544</a>: IPA/SCCPlite not fully supported from new osmo-bsc.git</i> added</li></ul> libosmo-sccp + libosmo-sigtran - Bug #3392: SCCPlite: xua_asp_fsm.c hardcodes a routing keyhttps://osmocom.org/issues/3392?journal_id=108762018-08-20T16:12:49Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Assignee</strong> set to <i>neels</i></li></ul><p>IIUC this issue mixes up routing-key with routing context. I think we always have just one routing context so far (0). Not sure what the routing key's use is. This should probably be rejected, but maybe someone else / me-from-the-future is more certain about it.</p> libosmo-sccp + libosmo-sigtran - Bug #3392: SCCPlite: xua_asp_fsm.c hardcodes a routing keyhttps://osmocom.org/issues/3392?journal_id=119172018-10-02T18:58:04Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Rejected</i></li></ul><p>nah, this is just confusing. If there is any real problem, we'll notice in the future anyway.</p>