Bug #3392

SCCPlite: xua_asp_fsm.c hardcodes a routing key

Added by neels over 1 year ago. Updated about 1 year ago.

Target version:
Start date:
Due date:
% Done:


Spec Reference:


If I configure a specific routing key in the 'cs7 instance' vty for an IPA SIGTRAN MSC, osmo-bsc won't start up.

Normal startup behavior seems to be to terminate the FSM and then re-allocate it.
During the termination, in ipa_asp_fsm_cleanup() it says

        struct osmo_ss7_as *as = osmo_ss7_as_find_by_rctx(inst, 0);

The above essentially asserts a routing key of 0. If the VTY configured a routing key of, say, 2 for the AS like

cs7 instance 0
 point-code format 24
 point-code 1196
 asp asp-clnt-msc-0 5000 0 ipa
 as as-clnt-msc-0 ipa
  asp asp-clnt-msc-0
  routing-key 2 100

this leads to

20180711020641670 DLSCCP NOTICE sccp_user.c:426 msc-0: Creating default route
20180711020641670 DLSS7 INFO osmo_ss7.c:811 0: Creating route: pc=0=0 mask=0x0 via AS 'as-clnt-msc-0'
20180711020641670 DLSS7 INFO osmo_ss7.c:1221 0: Restarting ASP asp-clnt-msc-0
20180711020641670 DLSS7 DEBUG osmo_ss7.c:1277 IPA_ASP(asp-clnt-msc-0)[0x61200000b620]{ASP_DOWN}: Terminating (cause = OSMO_FSM_TERM_REQUEST)
Assert failed as ../../../src/libosmo-sccp/src/xua_asp_fsm.c:1045
backtrace() returned 11 addresses
/usr/local/lib/ [0x7efc610c53cb]
/usr/local/lib/ [0x7efc610c52db]
/usr/local/lib/ [0x7efc60a043af]
/usr/local/lib/ [0x7efc610af9de]
/usr/local/lib/ [0x7efc609f9491]
/usr/local/lib/ [0x7efc609e6f23]
osmo-bsc(+0x571c56) [0x55fb04019c56]
osmo-bsc(+0x36a878) [0x55fb03e12878]
/lib/x86_64-linux-gnu/ [0x7efc5f6242b1]
osmo-bsc(+0x36b52a) [0x55fb03e1352a]

The error does not occur iff the hardcoded routing key matches osmo-bsc.cfg.

Related issues

Related to OsmoBSC - Bug #2544: IPA/SCCPlite not fully supported from new osmo-bsc.gitResolved10/06/2017


#1 Updated by neels over 1 year ago

#2 Updated by neels over 1 year ago

  • Related to Bug #2544: IPA/SCCPlite not fully supported from new osmo-bsc.git added

#3 Updated by neels about 1 year ago

  • Assignee set to neels

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.

#4 Updated by neels about 1 year ago

  • Status changed from New to Rejected

nah, this is just confusing. If there is any real problem, we'll notice in the future anyway.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)