Project

General

Profile

Bug #3392

SCCPlite: xua_asp_fsm.c hardcodes a routing key

Added by neels 6 days ago. Updated 6 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
07/11/2018
Due date:
% Done:

0%

Estimated time:
Spec Reference:

Description

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);
        //...
        OSMO_ASSERT(as);

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
  remote-ip 10.9.8.7
 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/libosmocore.so.10(+0xc53cb) [0x7efc610c53cb]
/usr/local/lib/libosmocore.so.10(osmo_panic+0x14b) [0x7efc610c52db]
/usr/local/lib/libosmo-sigtran.so.0(+0xfd3af) [0x7efc60a043af]
/usr/local/lib/libosmocore.so.10(_osmo_fsm_inst_term+0x53e) [0x7efc610af9de]
/usr/local/lib/libosmo-sigtran.so.0(osmo_ss7_asp_restart+0x5e1) [0x7efc609f9491]
/usr/local/lib/libosmo-sigtran.so.0(osmo_sccp_simple_client_on_ss7_id+0x1e3) [0x7efc609e6f23]
osmo-bsc(+0x571c56) [0x55fb04019c56]
osmo-bsc(+0x36a878) [0x55fb03e12878]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0x7efc5f6242b1]
osmo-bsc(+0x36b52a) [0x55fb03e1352a]
Aborted

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.gitIn Progress2017-10-06

History

#1 Updated by neels 6 days ago

#2 Updated by neels about 20 hours ago

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

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)