Ethereal-dev: RE: [Ethereal-dev] [Camel] BER error

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: "Anders Broman (AL/EAB)" <anders.broman@xxxxxxxxxxxx>
Date: Fri, 25 Nov 2005 12:13:39 +0100
Hi,
the problem is :
That in a newer spec it says:
 
InitialDPArgExtension  ::= SEQUENCE {
 gmscAddress       [0] ISDN-AddressString      OPTIONAL,
 forwardingDestinationNumber   [1] CalledPartyNumber      OPTIONAL,
 ms-Classmark2      [2] MS-Classmark2       OPTIONAL,
 iMEI        [3] IMEI         OPTIONAL,
 supportedCamelPhases    [4] SupportedCamelPhases     OPTIONAL,
 offeredCamel4Functionalities  [5] OfferedCamel4Functionalities   OPTIONAL,
 bearerCapability2     [6] BearerCapability      OPTIONAL,
 ext-basicServiceCode2    [7] Ext-BasicServiceCode     OPTIONAL,
 highLayerCompatibility2    [8] HighLayerCompatibility     OPTIONAL,
 lowLayerCompatibility    [9] LowLayerCompatibility     OPTIONAL,
 lowLayerCompatibility2    [10] LowLayerCompatibility     OPTIONAL,
 ...,
 enhancedDialledServicesAllowed  [11] NULL         OPTIONAL,
 uu-Data        [12] UU-Data        OPTIONAL
}
 
An I think your trace has tag = 1
 
 forwardingDestinationNumber   [1] CalledPartyNumber      OPTIONAL,
 
I'll try to update the asn1 spec.
Brg
Anders


From: ethereal-dev-bounces@xxxxxxxxxxxx [mailto:ethereal-dev-bounces@xxxxxxxxxxxx] On Behalf Of Jacques, Olivier (OCBU-Test Infra)
Sent: den 24 november 2005 18:54
To: Ethereal development
Subject: [Ethereal-dev] [Camel] BER error

Hello,
 
I'm using svn 16577.
I'm fighting (with no luck :) ) with a BER error in the decoding of a Camel InitialDP:
In the parameter "initialDPArgExtension", I get "BER error: this field lies beyond the end of the known sequence definition".
The parameter is defined in the .asn file of Camel as:
----------------------------------
-- InitialDPArgExtension notes: not recursive, exported,
-- locally refd 1 times, import refd 0 times
InitialDPArgExtension ::=   SEQUENCE
{
    gmscAddress [0] ISDN-AddressString OPTIONAL
}
----------------------------------
 
I also attached the message in question.
 
Any idea what could be wrong?
 
Thanks,
Olivier.