[EMAIL PROTECTED] wrote:
Hi,
I have just verified that this definition ( 8 octets ) is the right one.
I need to encode the MSISDN into 8 octets as this definition says.
Can you please explain me how can I go ahead
encoding the MSISDN ( +919448458398 ) into 8 octets?
Most probably the supporting documentation requires some sort of
additional encoding. For MSISDN, I suppose, the documentation requires
the use of TBCD encoding. While TBCD comes in two flavors, the
most widespread one is big-endian one. This way, 919448458398
will have to be encoded as (hexadecimal):
FF FF 91 94 48 45 83 98
But please consult the documentation to make sure it is TBCD.
Thanks and Regards,
Murugan
-----Original Message-----
From: Lev Walkin [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 18, 2006 10:42 AM
To: Natesan Murugan (IFIN SW WS)
Cc: [email protected]
Subject: Re: [Asn1] Basic ASN.1 PER encoding of MSISDN
[EMAIL PROTECTED] wrote:
Hi,
Thanks for your response.
Find below the definition of MSISDN in SUPL spec.
SETId ::= CHOICE {
msisdn OCTET STRING(SIZE (8)),
mdn OCTET STRING(SIZE (8)),
min BIT STRING(SIZE (34)), -- coded according to TIA-553
imsi OCTET STRING(SIZE (8)),
nai IA5String(SIZE (1..1000)),
iPAddress IPAddress,
...}
You cannot encode msisdn subfield of SETId type into 4 octets using this
specification. Exactly 8 octets are required.
Sorry, either supporting documentation or the ASN.1 module file is not
correct.
--
Lev Walkin
[EMAIL PROTECTED]
_______________________________________________
Asn1 mailing list
[email protected]
http://lists.asn1.org/mailman/listinfo/asn1
