From b2daa0d803ee529af9549e1a9884e209729be6d3 Mon Sep 17 00:00:00 2001 From: Harald Welte Date: Sat, 19 Dec 2015 13:05:19 +0100 Subject: ranap ASN.1: Define IMSI as OCTET STRING to work around asn1c bug When IMSI is a TBCD-STRING type, and TBCD-STRING is defined as OCTET STRING, we end up encoding the IMSI the wrong way. I don't knwo why that is, but changing it fixed the problem, as described below: before this commit: 00 17 PeranentNAS-UE-ID 40 criticality ignore 0a (length) 00 presence = IMSI 08 BUG: why the additional length field? 46 23 91 34 70 77 80 f3 IMSI (643219430777083) after this commit: 00 17 PeranentNAS-UE-ID 40 criticality ignore 09 (length) 50 presence = IMSI 46 23 91 34 70 77 80 f3 IMSI (643219430777083) --- asn1/ranap/RANAP-IEs.asn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'asn1') diff --git a/asn1/ranap/RANAP-IEs.asn b/asn1/ranap/RANAP-IEs.asn index 9593ee8..78fcfbe 100644 --- a/asn1/ranap/RANAP-IEs.asn +++ b/asn1/ranap/RANAP-IEs.asn @@ -842,7 +842,7 @@ ImmediateMDT ::= SEQUENCE { iE-Extensions IE-Extensions OPTIONAL } -IMSI ::= TBCD-STRING (SIZE (3..8)) +IMSI ::= OCTET STRING (SIZE (3..8)) -- Reference: 23.003 IncludeVelocity ::= ENUMERATED { -- cgit v1.2.3