Osmocom Libraries » libosmo-sccp + libosmo-sigtran

At first, during N-CONNECT, the RSL request is going through to BSSMAP/IPA fine:

20180727183939313 DCHAN DEBUG abis_rsl.c:1612 lchan(0-0-0-CCCH_SDCCH4-0)[0x6120000021a0]{WAIT_RLL_RTP_ESTABLISH}: (type=SDCCH) SAPI=0 ESTABLISH INDICATION
20180727183939313 DCHAN DEBUG abis_rsl.c:1645 lchan(0-0-0-CCCH_SDCCH4-0)[0x6120000021a0]{WAIT_RLL_RTP_ESTABLISH}: Received Event LCHAN_EV_RLL_ESTABLISH_IND
20180727183939313 DCHAN DEBUG lchan_fsm.c:710 lchan(0-0-0-CCCH_SDCCH4-0)[0x6120000021a0]{WAIT_RLL_RTP_ESTABLISH}: state_chg to ESTABLISHED
20180727183939313 DMSC NOTICE fsm.c:299 SUBSCR_CONN[0x612000003220]{INIT}: Allocated
20180727183939313 DLCLS NOTICE fsm.c:299 LCLS[0x6120000033a0]{NO_LCLS}: Allocated
20180727183939313 DLCLS NOTICE fsm.c:329 LCLS[0x6120000033a0]{NO_LCLS}: is child of SUBSCR_CONN[0x612000003220]
20180727183939313 DMSC INFO gsm_08_08.c:373 Tx MSC COMPL L3
20180727183939314 DMSC NOTICE osmo_bsc_sigtran.c:285 Initializing resources for new SIGTRAN connection to MSC: RI=SSN_PC,PC=100,SSN=BSSAP...
20180727183939314 DMSC NOTICE gsm_08_08.c:500 SUBSCR_CONN[0x612000003220]{INIT}: Received Event MO-CONNECT.req
20180727183939314 DMSC DEBUG osmo_bsc_sigtran.c:327 Allocated new connection id: 1
20180727183939314 DMSC NOTICE osmo_bsc_sigtran.c:331 Opening new SIGTRAN connection (id=1) to MSC: RI=SSN_PC,PC=100,SSN=BSSAP
20180727183939314 DLSCCP DEBUG sccp_scoc.c:1615 Received SCCP User Primitive N-CONNECT.request)
20180727183939314 DLSCCP DEBUG fsm.c:299 SCCP-SCOC(1)[0x612000003520]{IDLE}: Allocated
20180727183939314 DLSCCP DEBUG sccp_scoc.c:1657 SCCP-SCOC(1)[0x612000003520]{IDLE}: Received Event N-CONNECT.req
20180727183939314 DLSS7 DEBUG sccp_scrc.c:398 sccp_scrc_rx_scoc_conn_msg:  HDR=(CO:CORE,V=0,LEN=0),
    PART(T=Routing Context,L=4,D=00000000),
    PART(T=Protocol Class,L=4,D=00000002),
    PART(T=Source Reference,L=4,D=00000001),
    PART(T=Destination Address,L=20,D=00020003800200080000006480030008000000fe),
    PART(T=Sequence Control,L=4,D=00000000),
    PART(T=Source Address,L=20,D=0002000380020008000004ac80030008000000fe),
    PART(T=Data,L=30,D=001c5705080032f44000c851e0170f05080232f44000c85005f45b45589f)
20180727183939314 DLSUA DEBUG sua.c:385 sua_addr_parse_part(IEI=0x0103) (20) 00 02 00 03 80 02 00 08 00 00 00 64 80 03 00 08 00 00 00 fe 
20180727183939314 DLSUA DEBUG sua.c:439 SUA IEI 0x0103 pos 4/20: subpart tag 0x8002, len 8
20180727183939314 DLSUA DEBUG sua.c:439 SUA IEI 0x0103 pos 12/20: subpart tag 0x8003, len 8
20180727183939314 DLSUA DEBUG sua.c:385 sua_addr_parse_part(IEI=0x0103) (20) 00 02 00 03 80 02 00 08 00 00 00 64 80 03 00 08 00 00 00 fe 
20180727183939315 DLSUA DEBUG sua.c:439 SUA IEI 0x0103 pos 4/20: subpart tag 0x8002, len 8
20180727183939315 DLSUA DEBUG sua.c:439 SUA IEI 0x0103 pos 12/20: subpart tag 0x8003, len 8
20180727183939315 DLSUA DEBUG sua.c:385 sua_addr_parse_part(IEI=0x0102) (20) 00 02 00 03 80 02 00 08 00 00 04 ac 80 03 00 08 00 00 00 fe 
20180727183939315 DLSUA DEBUG sua.c:439 SUA IEI 0x0102 pos 4/20: subpart tag 0x8002, len 8
20180727183939315 DLSUA DEBUG sua.c:439 SUA IEI 0x0102 pos 12/20: subpart tag 0x8003, len 8
20180727183939315 DLSS7 DEBUG osmo_ss7_hmrt.c:278 m3ua_hmdc_rx_from_l2(): dpc=100=100 not local, message is for routing
20180727183939315 DLSS7 DEBUG osmo_ss7_hmrt.c:227 Found route for dpc=100=100: pc=0=0 mask=0x0=0 via AS as-clnt-msc-0 proto=ipa
20180727183939315 DLSCCP DEBUG sccp_scoc.c:732 SCCP-SCOC(1)[0x612000003520]{IDLE}: state_chg to CONN_PEND_OUT
20180727183939315 DMSC NOTICE bsc_subscr_conn_fsm.c:253 SUBSCR_CONN[0x612000003220]{INIT}: state_chg to WAIT_CC
20180727183939315 DLINP DEBUG stream.c:279 connected write
20180727183939315 DLINP DEBUG stream.c:204 sending data
20180727183939315 DLINP DEBUG stream.c:279 connected write
20180727183939315 DLINP DEBUG stream.c:204 sending data

But right after than, e.g on an MM Identity Response, the message is not routed to the MSC:

20180727183939782 DCHAN DEBUG abis_rsl.c:1603 lchan(0-0-0-CCCH_SDCCH4-0)[0x6120000021a0]{ESTABLISHED}: (type=SDCCH) SAPI=0 DATA INDICATION
20180727183939783 DMSC INFO gsm_08_08.c:601 Tx MSC DTAP LINK_ID=0x00
20180727183939783 DMSC NOTICE gsm_08_08.c:623 SUBSCR_CONN(conn1)[0x612000003220]{ACTIVE}: Received Event MO_DTAP
20180727183939783 DMSC INFO osmo_bsc_sigtran.c:363 Tx MSC DTAP
20180727183939783 DMSC DEBUG osmo_bsc_sigtran.c:381 Sending connection (id=1) oriented data to MSC: RI=SSN_PC,PC=100,SSN=BSSAP (01 00 0b 05 59 08 3a 65 24 05 35 31 76 08 )
20180727183939783 DLSCCP DEBUG sccp_scoc.c:1615 Received SCCP User Primitive N-DATA.request)
20180727183939783 DLSCCP DEBUG sccp_scoc.c:1657 SCCP-SCOC(1)[0x612000003520]{ACTIVE}: Received Event N-DATA.req
20180727183939783 DLSS7 DEBUG sccp_scrc.c:398 sccp_scrc_rx_scoc_conn_msg:  HDR=(CO:CODT,V=0,LEN=0),
    PART(T=Routing Context,L=4,D=00000000),
    PART(T=Destination Reference,L=4,D=001f0000),
    PART(T=Data,L=14,D=01000b0559083a65240535317608)
20180727183939783 DLSCCP ERROR sccp_scrc.c:138 MTP-TRANSFER.req from SCCP without DPC?!? called=RI=0

The log clearly shows DPC=100, yet sccp_scrc.c:138 complains about a missing DPC.