Bhandare Shashidhar wrote: > I am trying to use Ethereal for monitoring ANSI SCCP. > I observed the following problems while using GT > format 0 and GT Format 1. Can you please let me know > were there any fixes done to resolve these problems. > > I have not used GT Format 2 yet. > > I am using 0.10.4 release of Ethereal on SUN OS 5.9. > > > Problems: > > 1. For GT Format 0, the SCCP Called and Calling Party > IE headers are decoded similar to ITU. Where as the > ordering of SSN and PC fields are reversed. > > 2. For GT Format 1, the Called and Calling party IE > has these fields: > > OCTET x: > - Translation type > > OCTET y: > - Numbering Plan > - Encoding scheme > > The present decode assumes one more field Nature of > Address at OCTET z: and decodes the fist byte of > address digits. Please note that you probably have to configure Ethereal to handle ANSI instead of ITU. Edit/Preferences.../Protocols/MTP3/MTP3 Standard I don't know if that will solve your problems, but at least it seems that packet-sccp.c is using the mtp3_standard setting from MTP3 dissector.
Powered by MHonArc 2.6.10