Thanks Rajul,
I agree with you. another possibilty is that the asn spec is wrong : the
constraint could be different.
applicationInformation SET (SIZE (0..65535)) OF
SEQUENCE
-- One for each Application Protocol Session;
-- all Application Protocol Sessions if full refresh;
-- no Application Protocol Session shall be
-- listed more than once
{sessionKey SessionKey,
would make a length encoding on 2 bytes (rigth?). If somebody knows what
syntax is used by Netmeeting... I am interested!
Thanks a lot
Bruno
> -----Message d'origine-----
> De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]De la part de Rajul
> Gupta
> Envoy� : dimanche 1 d�cembre 2002 07:12
> � : [EMAIL PROTECTED]
> Objet : Re: [ASN.1] pb with T124 encoding.
>
>
> Hi Bruno,
>
> ----- Original Message -----
> From: "Bruno.Konik" <[EMAIL PROTECTED]>
> To: "* ASN.1 liste" <[EMAIL PROTECTED]>
> Sent: Friday, November 29, 2002 5:51 PM
> Subject: [ASN.1] pb with T124 encoding.
>
>
> > Hello,
> >
> > I am trying to decode the following pdu with the type GCCPDU
> found in T124
> > (attached). It is PER aligned.
> >
> > 86 08 01 61 90 0c 20 61 8b 20 10 00 42 00 72 00
> > 75 00 6e 00 6f 00 20 00 4b 00 6f 00 6e 00 69 00
> > 6b 00 20 00 4b 00 49 00 57 00 49 03 c0 40 b5 00
> > 53 4c 01 80 a8 70 85 aa 6c e5 ca cf 11 8f a5 00
> > 80 5f 74 2e f6 54 00 43 00 50 00 3a 00 31 00 39
> > 00 32 00 2e 00 31 00 36 00 38 00 2e 00 30 00 2e
> > 00 31 00 00 00 54 00 43 00 50 00 3a 00 31 00 39
> > 00 32 00 2e 00 31 00 36 00 38 00 2e 00 30 00 2e
> > 00 31 00 00 00 56 00 45 00 52 00 3a 00 30 00 34
> > 00 30 00 34 00 30 00 44 00 33 00 43 00 00 00 45
> > 00 4d 00 41 00 49 00 4c 00 3a 00 62 00 72 00 75
> > 00 6e 00 6f 00 2e 00 6b 00 6f 00 6e 00 69 00 6b
> > 00 40 00 75 00 6e 00 69 00 67 00 6f 00 6e 00 65
> > 00 2e 00 63 00 6f 00 6d 00 00 00 00 00 c0 40 b5
> > 00 53 4c 01 14 90 a5 8b 5e 59 8c d0 11 8d d6 00
> > 00 f8 03 a4 46 37 00 0a 00 c0 40 b5 00 53 4c 01
> > 20 81 38 42 74 84 cc d2 11 b4 e3 00 a0 c9 0d 06
> > 60 28 da a5 86 92 03 d7 11 95 52 00 c0 4f 09 4b
> > 14 00 01 80 00 01 20 40 b5 00 53 4c 02 00 40 01 <--
> > 61 90 00 01 0a 00 01 80 00 00 11 42 72 75 6e 6f |
> > 20 4b 6f 6e 69 6b 20 4b 49 57 49 00 00 00 01 80 |
> > |
> > I have got a little problem 3 lines before the end | where we
> see 80 00
> 01
> > 20 40 ... . There should be a length for the following
> component (in type
> > RosterUpdateIndication) :
> >
> > ...},
> > applicationInformation SET (SIZE (0..65536)) OF
> > SEQUENCE
> > -- One for each Application Protocol Session;
> > -- all Application Protocol Sessions if full refresh;
> > -- no Application Protocol Session shall be
> > -- listed more than once
> > {sessionKey SessionKey,
> >
> >
> > As we can see it is a length for SET (SIZE(0..65536)) OF . This length
> > should be encoded on only 1 octet if my understanding of 10.9 of x691 is
> > correct but I see here 2 bytes for the length "00 01". Where is the
> mistake?
>
> One possibility could be that there is no applicationInformation
> in the PDU,
> as size of applicationInformation could be 0 too, and data after
> "80 00" may
> be any other PDU.
>
> Also, when I removed "00" from the erratic part "80 00 01 20 40", I could
> decode applicationInformation without any error. So, there may be a
> possibility that data was encoded incorrectly.
>
> Rajul Gupta
> OSS Nokalva
> [EMAIL PROTECTED]
> 1-732-302-9669 (x-137)
> http://www.oss.com
>
>
> > BTW : this pdu is extracted from an exchange of T120 using MS
> Netmeeting.
> >
> > Thanks for your time.
> >
> > Bruno KONIK - uniGone
> > Tel : +33 (0)1 60 12 77 64
> > Fax : +33 (0)1 60 12 77 65
> > 41-43 rue de Cronstadt - 75015 PARIS FRANCE
> > mailto:[EMAIL PROTECTED]
> > URL : http://www.unigone.com
> >
> > -- uniGone provides a complete environment for ASN.1 users : JAVA
> compiler,
> > ASN.1 IP analyzer, simulator... contact us for more information... --
> >
>
