OsmoBSC - SCCP Connection to Nokia MSC

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.

Sonny Lafuente sonny.lafuente at entropysolution.com
Wed Jan 6 07:53:18 UTC 2021


Hi Community,

Happy New Year!

Would like to ask if anyone here have experience integrating OsmoBSC to Nokia MSC? Currently we are doing the integration in Nokia MSC and we encountered issue. Basically, in the SCCP part, the BSC is trying to send UDT (BSSAP) Reset but no response from the MSC. After the default timer of the RESET, we observed a SACK SST and SACK UDTS. In the SACK SST, we saw the trace that there is no Calling indicator which is my BSC point code. When checking the trace we saw this Affected Subsystem Number: 254. I’ve red some documentations in OSMO but I don’t find any SCCP management configuration in OSMO so I think this one is on MSC side. Below is the Trace we captured.


BSC Point code - 2262
Nokia Point code - 7039




Logs Below:


<001f> sccp_scrc.c:420 sccp_scrc_rx_sclc_msg:  HDR=(CL:CLDT,V=0,LEN=0),
PART(T=Routing Context,L=4,D=00000000),
PART(T=Protocol Class,L=4,D=00000000),
PART(T=Source Address,L=20,D=0002000380020008000008d680030008000000fe),
PART(T=Destination Address,L=20,D=000200038002000800001b7f80030008000000fe),
PART(T=Sequence Control,L=4,D=00000000),
PART(T=Data,L=6,D=000430040120)
<001f> osmo_ss7_hmrt.c:278 m3ua_hmdc_rx_from_l2(): dpc=7039=3.111.7 not local, message is for routing
<001f> osmo_ss7_hmrt.c:227 Found route for dpc=7039=3.111.7: pc=0=0.0.0 mask=0x0=0.0.0 via AS nokia_msc proto=m3ua
<001f> osmo_ss7_hmrt.c:233 rt->dest.as proto is M3UA for dpc=7039=3.111.7
<001f> m3ua.c:507 XUA_AS(nokia_msc)[0x11886f0]{AS_ACTIVE}: Received Event AS-TRANSFER.req
<0007> a_reset.c:110 A-RESET(msc-0)[0x1194c80]{DISC}: state_chg to DISC
<0007> fsm.c:189 A-RESET(msc-0)[0x1194c80]{DISC}: Timeout of T4
<0007> a_reset.c:106 A-RESET(msc-0)[0x1194c80]{DISC}: (re)sending BSSMAP RESET message...
<0007> osmo_bsc_sigtran.c:93 Sending RESET to MSC: RI=SSN_PC,PC=3.111.7,SSN=BSSAP
<001f> sccp_scrc.c:420 sccp_scrc_rx_sclc_msg:  HDR=(CL:CLDT,V=0,LEN=0),
PART(T=Routing Context,L=4,D=00000000),
PART(T=Protocol Class,L=4,D=00000000),
PART(T=Source Address,L=20,D=0002000380020008000008d680030008000000fe),
PART(T=Destination Address,L=20,D=000200038002000800001b7f80030008000000fe),
PART(T=Sequence Control,L=4,D=00000000),
PART(T=Data,L=6,D=000430040120)
<001f> osmo_ss7_hmrt.c:278 m3ua_hmdc_rx_from_l2(): dpc=7039=3.111.7 not local, message is for routing
<001f> osmo_ss7_hmrt.c:227 Found route for dpc=7039=3.111.7: pc=0=0.0.0 mask=0x0=0.0.0 via AS nokia_msc proto=m3ua
<001f> osmo_ss7_hmrt.c:233 rt->dest.as proto is M3UA for dpc=7039=3.111.7
<001f> m3ua.c:507 XUA_AS(nokia_msc)[0x11886f0]{AS_ACTIVE}: Received Event AS-TRANSFER.req
<0007> a_reset.c:110 A-RESET(msc-0)[0x1194c80]{DISC}: state_chg to DISC




OSMOBSC Version:

OsmoBSC# show version
OsmoBSC 1.3.0.132-bcbc5 (OsmoBSC).
Copyright (C) 2008-2018 Harald Welte, Holger Freyther
Contributions by Daniel Willmann, Jan Lübbe, Stefan Schmidt
Dieter Spaar, Andreas Eversberg, Sylvain Munaut, Neels Hofmeyr

License AGPLv3+: GNU AGPL version 3 or later <http://gnu.org/licenses/agpl-3.0.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

OsmoBSC#


Regards,

Sonny Lafuente | Systems Engineer | Entropy Solution Philippines
Mobile: +639985365206 | Office: 028931781 | Email: sonny.lafuente at entropysolution.com<mailto:sonny.lafuente at entropysolution.com>
Office Address: Unit 2103 Antel Corporate  Centre 121 Valero St. Salcedo Village Makati City Philippines 1227

[cid:907cda3a-190d-48c4-bd09-a9b05bf0c799 at apcprd04.prod.outlook.com]

Singapore * Philippines
Products:
Gridloc*Intelle*Hype*Lighthouse*Telco Services*Software Development
This email (including any attachment to it) is confidential and intended only for the use of the individual named above and may contain information that is privileged. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this email is strictly prohibited. If you have received this email in error, please notify us immediately by return email or telephone and destroy the original message (including any attachment to it). Thank you.

On 6 Jan 2021, at 8:41 AM, Sonny Lafuente <sonny.lafuente at entropysolution.com<mailto:sonny.lafuente at entropysolution.com>> wrote:

Hi Community,

Happy New Year!

Would like to ask if anyone here have experience integrating OsmoBSC to Nokia MSC? Currently we are doing the integration in Nokia MSC and we encountered issue. Basically, in the SCCP part, the BSC is trying to send UDT (BSSAP) Reset but no response from the MSC. After the default timer of the RESET, we observed a SACK SST and SACK UDTS. In the SACK SST, we saw the trace that there is no Calling indicator which is my BSC point code. When checking the trace we saw this Affected Subsystem Number: 254. I’ve red some documentations in OSMO but I don’t find any SCCP management configuration in OSMO so I think this one is on MSC side. Below is the Trace we captured.


BSC Point code - 2262
Nokia Point code - 7039













Regards,
Sonny
<PastedGraphic-1.tiff><PastedGraphic-2.tiff><PastedGraphic-3.tiff><sccp captured nokia MSC.pcap>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20210106/41fe9428/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Entropy Logo Email.png
Type: image/png
Size: 32853 bytes
Desc: Entropy Logo Email.png
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20210106/41fe9428/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sccp captured nokia MSC.pcap
Type: application/octet-stream
Size: 2748 bytes
Desc: sccp captured nokia MSC.pcap
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20210106/41fe9428/attachment.obj>


More information about the OpenBSC mailing list