This wiki has been migrated to https://gitlab.com/wireshark/wireshark/-/wikis/home and is now deprecated. Please use that site instead.
Differences between revisions 2 and 3
Revision 2 as of 2006-12-15 12:32:05
Size: 1660
Editor: cacher6
Comment:
Revision 3 as of 2007-06-20 16:13:30
Size: 1676
Editor: no-dns-yet
Comment: Fill in more of the boiletplate fields.
Deletions are marked like this. Additions are marked like this.
Line 23: Line 23:
messages containing the UDVM code is seen. The SIP library is included. Reassembly of segmented TCP packaages are NOT included. messages containing the UDVM code is seen. The SIP library is included. Reassembly of segmented TCP packages is NOT implemented.
Line 27: Line 27:
The level of detail of UDVM execution can be set as well as port used. The level of detail of UDVM execution can be set, as well as UDP/TCP ports used.
Line 33: Line 33:
A complete list of Sigcomp display filter fields can be found in the [http://www.wireshark.org/docs/dfref/protofirstletter/proto.html display filter reference] A complete list of Sigcomp display filter fields can be found in the [http://www.wireshark.org/docs/dfref/s/sigcomp.html display filter reference]
Line 35: Line 35:
 Show only the PROTO based traffic: {{{
 proto }}}
 Show only the SigComp based traffic: {{{
 sigcomp }}}
Line 40: Line 40:
You cannot directly filter PROTO protocols while capturing. However, if you know the ["TCP"] port used (see above), you can filter on that one. You cannot directly filter SigComp traffic while capturing. However, if you know the ["UDP"] port used (see above), you can filter on that one.
Line 42: Line 42:
 Capture only the PROTO traffic over the default port (80): {{{
 tcp port 80 }}}
 Capture only the SigComp traffic over the default SIP UDP port (5060): {{{
 udp port 5060 }}}

Signaling Compression (SIGCOMP)

Signaling Compression (SigComp), a solution for compressing messages generated by application protocols such as the Session Initiation Protocol (SIP) (RFC 3261) and the Real Time Streaming Protocol (RTSP) (RFC 2326).

History

Protocol dependencies

Typically, Sigcomp uses the same transport protocol as the compressed protocol.

Example traffic

XXX - Add example decoded traffic for this protocol here (as plain text or Wireshark screenshot).

Wireshark

The SIGCOMP dissector is fully functional, and can display the uploded UDVM code and decompress messages if the messages containing the UDVM code is seen. The SIP library is included. Reassembly of segmented TCP packages is NOT implemented.

Preference Settings

The level of detail of UDVM execution can be set, as well as UDP/TCP ports used.

Example capture file

Display Filter

A complete list of Sigcomp display filter fields can be found in the [http://www.wireshark.org/docs/dfref/s/sigcomp.html display filter reference]

  • Show only the SigComp based traffic:

     sigcomp 

Capture Filter

You cannot directly filter SigComp traffic while capturing. However, if you know the ["UDP"] port used (see above), you can filter on that one.

  • Capture only the SigComp traffic over the default SIP UDP port (5060):

     udp port 5060 

Discussion

Sigcomp (last edited 2008-10-28 10:04:48 by AndersBroman)