Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-dev: Re: [Wireshark-dev] Network Instruments Observer - Unistim Decoder

From: "Newton, Don" <dnewton@xxxxxxxxxxxxxx>
Date: Tue, 21 Aug 2007 12:46:00 -0400

Can you attach a pcap file?

 

Don Newton


From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of J P
Sent: Tuesday, August 21, 2007 12:32 PM
To: wireshark-dev@xxxxxxxxxxxxx
Subject: Re: [Wireshark-dev] Network Instruments Observer - Unistim Decoder

 

Hi Jaap,

 

Thanx for the speedy response.

 

Here is the decode of a Unistim Packet from a call I made:

Frame 31 (164 bytes on wire, 164 bytes captured)
Ethernet II, Src: Cisco_01:54:01 (00:05:32:01:54:01), Dst: Nortel_e4:62:ab (00:15:9b:e4:62:ab)
Internet Protocol, Src: 204.83.231.69 (204.83.231.69), Dst: 10.1.1.56 (10.1.1.56)
User Datagram Protocol, Src Port: commplex-main (5000), Dst Port: commplex-main (5000)
    Source port: commplex-main (5000)
    Destination port: commplex-main (5000)
    Length: 130
    Checksum: 0x7e31 [correct]
        [Good Checksum: True]
        [Bad Checksum: False]
Data (122 bytes)

0000  00 00 e3 6f 02 01 17 05 0f 10 01 17 05 0f 10 02   ...o............
0010  17 06 10 81 04 00 17 05 10 87 00 17 07 1b 04 00   ................
0020  05 47 17 07 1b 04 01 05 52 17 07 1b 04 02 05 4f   .G......R......O
0030  17 07 1b 04 03 05 4e 17 07 1b 04 04 05 4b 17 05   ......N......K..
0040  0f 10 02 17 07 1b 04 20 05 34 17 07 1b 04 21 05   ....... .4....!.
0050  32 17 07 1b 04 22 05 32 17 07 1b 04 23 05 30 17   2....".2....#.0.
0060  0b 1b 04 00 05 47 52 4f 4e 4b 17 0a 1b 04 20 05   .....GRONK.... .
0070  34 32 32 30 17 06 10 81 04 24                     4220.....$

Do you know what I am doing wrong so that I am seeing only data and not the Unistim Decode?

 

Thanx,

 

John

 

From: Jaap Keuter <jaap.keuter@xxxxxxxxx>
Date: Tue, 21 Aug 2007 17:56:13 +0200

 

 
Hi,
 

The beauty of subversion is that any change to the repository simply increments the revision number. If you know the tree to take from you can be assured that everything is in there. The buildbot builds from /trunk and that's where all the development is happening, so yes the build from revision 22562 should have it.

Thanx,
Jaap