ASN.1 decoding problems with H.323

Bruce Fitzsimons bruce@REDACTED
Mon May 21 02:01:10 CEST 2001


Hello again,

I am having problems with the ASN.1 per decoding in R7B. If you are familiar
with H323 then this is specifically when the endpointAlias field of the
Gatekeeper contains an E164 alias. It works fine with H323 aliases, but
consistently fails if there is an E164 (telephone number). This is from
several different clients on the sending side, so I don't believe that the
source encoding is faulty.

If someone could give me an hints on debugging the ASN.1 decoding it would
be appreciated. I'm going to start reverse-engineering what its doing
internally...

The decoding failed with reason {function_clause,
                                    [{asn1rt_per_v1,getbit1,[{0,[]}]},
                                     {asn1rt_per_v1,getbits,3},
                                     {asn1rt_per_v1,chars_decode2,5},
                                     {'H323-MESSAGES',dec_AliasAddress,2},
                                     {'H323-MESSAGES',

dec_GatekeeperRequest_endpointAlias_components,
                                         4},

{'H323-MESSAGES',dec_GatekeeperRequest,2},
                                     {'H323-MESSAGES',dec_RasMessage,2},
                                     {asn1rt,decode,3}|
                                     more]}

Cheers,
Bruce

PS Is there any plans for a per_bin option?




More information about the erlang-questions mailing list