[PATCH] Fix RANAP SSN: it's 142, not 143

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/.

Neels Hofmeyr nhofmeyr at sysmocom.de
Wed Apr 13 15:45:25 UTC 2016


143 is actually the SSN for RNSAP. Wireshark displayed a RNSAP message type
and malformed packet warning until I fixed this to 142. Now I get the proper
RANAP and id-Paging reported.

There has been a reallocation for RANAP and RNSAP SSNs, though the old SSN for
RANAP is apparently 32 (seen in a pcap from a real 3G network). When I send 32
instead of 142, wireshark also decodes the message as valid RANAP.
---
 include/osmocom/sigtran/sccp_sap.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/include/osmocom/sigtran/sccp_sap.h b/include/osmocom/sigtran/sccp_sap.h
index 5696b47..15aa840 100644
--- a/include/osmocom/sigtran/sccp_sap.h
+++ b/include/osmocom/sigtran/sccp_sap.h
@@ -106,7 +106,7 @@ enum osmo_sccp_ssn {
 	OSMO_SCCP_SSN_RES_INTL		= 0x0c,
 	OSMO_SCCP_SSN_BISDN		= 0x0d,
 	OSMO_SCCP_SSN_TC_TEST		= 0x0e,
-	OSMO_SCCP_SSN_RANAP		= 143,
+	OSMO_SCCP_SSN_RANAP		= 142,
 };
 
 struct osmo_sccp_gt {
-- 
2.1.4




More information about the OpenBSC mailing list