Harald Welte b2daa0d803 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)		2015-12-19 13:05:19 +01:00
..
ffasn1c	fixup ffasn1	2015-08-30 12:19:54 +02:00
RANAP-CommonDataTypes.asn	Add Procedure Codes and IEI constants to CommonDataTypes	2015-08-30 19:09:55 +02:00
RANAP-Constants.asn	RANAP: Further qualify Constants. They're not just integer	2015-08-30 19:03:57 +02:00
RANAP-Containers.asn	Import RANAP from 3GPP TS 25.413 V12.4.0 (2015-03)	2015-08-29 12:19:42 +02:00
RANAP-IEs.asn	ranap ASN.1: Define IMSI as OCTET STRING to work around asn1c bug	2015-12-19 13:05:19 +01:00
RANAP-PDU-Contents.asn	One further RANAP hacking session	2015-12-16 17:26:05 +01:00
RANAP-PDU-Descriptions.asn	Import RANAP from 3GPP TS 25.413 V12.4.0 (2015-03)	2015-08-29 12:19:42 +02:00
RANAP-PDU.asn	ranap: Don't forget ProtocolIE-CointainerPair around ProtocolIE-FieldPair	2015-12-19 02:37:35 +01:00