Ethereal-users: Re: [Ethereal-users] M3UA Decoding Error
Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.
From: Michael Tuexen <Michael.Tuexen@xxxxxxxxxxxxxxxxx>
Date: Thu, 9 Jun 2005 22:48:34 +0200
which means that your traffic is in the format described in RFC 3332
and not in the
older ID... Best regards Michael On Jun 9, 2005, at 5:10 PM, Sig Tran wrote:
I'm using Ethereal to display an M3UA capture session. I've found a very weird thing analyzing a M3UA packet If I use "RFC 3332" version to decode the packet everything is correct, but if I use any "Internet Draft" version I get a lot "Unknown Parameters". We did not find any difference in Payload Data Message (DATA) parameters between those version.You can see what I mean in the attached files. Thank you. Correo Yahoo! Comprueba qué es nuevo, aquí http://correo.yahoo.esNo. Time Source Destination Origen UDP Destino UDP Protocol Info 52 17.999104 localhost.localdomain localhost.localdomain 2905 2907 ISUP (ITU) IAM (CIC 1)Frame 52 (118 bytes on wire, 118 bytes captured) Ethernet II, Src: 00:00:00:00:00:00, Dst: 00:00:00:00:00:00Internet Protocol, Src Addr: localhost.localdomain (127.0.0.1), Dst Addr: localhost.localdomain (127.0.0.1)User Datagram Protocol, Src Port: 2905 (2905), Dst Port: 2907 (2907) MTP 3 User Adaptation Layer Version: Release 1 (1) Reserved: 0x00 Message class: Transfer messages (1) Message type: Payload data (DATA) (1) Message length: 76 Network appearance (28036591) Parameter Tag: Network appearance (512) Parameter length: 8 Network appearance: 28036591 Routing context (1 context) Parameter Tag: Routing context (6) Parameter length: 8 Routing context: 287454020 Protocol data (SS7 message of 28 bytes) Parameter Tag: Protocol data (528) Parameter length: 44 OPC: 65793 DPC: 66308 SI: ISUP (5) NI: 0 MP: 4 SLS: 6 Correlation identifier (4242281112) Parameter Tag: Correlation identifier (19) Parameter length: 8 Correlation Identifier: 4242281112 ISDN User Part CIC: 1 Message type: Initial address (1) Nature of Connection Indicators: 0x0 Forward Call Indicators: 0x2200 Calling Party's category: 0xa (ordinary calling subscriber) Transmission medium requirement: 0 (speech) Called Party Number: 910025775 Pointer to start of optional part: 9 Calling Party Number: 915555052 End of optional parameters (0)No. Time Source Destination Origen UDP Destino UDP Protocol Info 52 17.999104 localhost.localdomain localhost.localdomain 2905 2907 M3UA (ID 07) DATAFrame 52 (118 bytes on wire, 118 bytes captured) Ethernet II, Src: 00:00:00:00:00:00, Dst: 00:00:00:00:00:00Internet Protocol, Src Addr: localhost.localdomain (127.0.0.1), Dst Addr: localhost.localdomain (127.0.0.1)User Datagram Protocol, Src Port: 2905 (2905), Dst Port: 2907 (2907) MTP 3 User Adaptation Layer Version: Release 1 (1) Reserved: 0x00 Message class: Transfer messages (1) Message type: Payload data (DATA) (1) Message length: 76 Unknown parameter (tag 512 and 4 bytes value) Parameter Tag: Unknown (512) Parameter length: 8 Parameter value: 01ABCDEF Routing context (1 context) Parameter Tag: Routing context (6) Parameter length: 8 Routing context: 287454020 Unknown parameter (tag 528 and 40 bytes value) Parameter Tag: Unknown (528) Parameter length: 44Parameter value: 0001010100010304050004060100010022000A0002090783...Unknown parameter (tag 19 and 4 bytes value) Parameter Tag: Unknown (19) Parameter length: 8 Parameter value: FCDC1298 _______________________________________________ Ethereal-users mailing list Ethereal-users@xxxxxxxxxxxx http://www.ethereal.com/mailman/listinfo/ethereal-users
- References:
- [Ethereal-users] M3UA Decoding Error
- From: Sig Tran
- [Ethereal-users] M3UA Decoding Error
- Prev by Date: Re: [Ethereal-users] Question regarding capturing protocol.
- Next by Date: [Ethereal-users] Measuring bandwidth using Ethereal?
- Previous by thread: [Ethereal-users] M3UA Decoding Error
- Next by thread: Re: Re: [Ethereal-users] M3UA Decoding Error
- Index(es):