Ethereal-users: RE: [Ethereal-users] Issue in INAP decoding

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

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: "Anders Broman (AL/EAB)" <anders.broman@xxxxxxxxxxxx>
Date: Thu, 8 Sep 2005 13:33:02 +0200
Hi,
The best way is to insert code in the inap.cnf file to create a prameter tvb with the octet string and the call the apropriate function in
packet ISUP with that tvb (dissect_isup_called_party_number_parameter()), include packet-isup.h in packet-template-inap.c if not allready done.
Brg
Anders
-----Original Message-----
From: ethereal-users-bounces@xxxxxxxxxxxx [mailto:ethereal-users-bounces@xxxxxxxxxxxx]On Behalf Of Jeetendra Singh
Sent: den 8 september 2005 13:23
To: Ethereal user support
Subject: [Ethereal-users] Issue in INAP decoding
Hi,

I am using Ethereal to decode INAP PDUs but certain fields are not decoded
completely. For. example

Called Party Number
Calling Party Number
Forward Call Indicators.

I know that INAP dissector has been generated by using ASN.1 specification
and that specification defines Called Party Number, Calling Party Number &
Forward Call Indicators as OCTET STRING but includes a comment pointing to
ETS 300 356-1 for decoding of all the above fields.

I require INAP dissector to handle complete decoding. What's the best way of
achieving that?

Regards,
Amit Dang