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 4 and 5
Revision 4 as of 2008-04-12 17:50:30
Size: 1684
Editor: localhost
Comment: converted to 1.6 markup
Revision 5 as of 2008-10-25 11:36:19
Size: 1856
Editor: JaapKeuter
Comment: Add description of PIDF support
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
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).
Signaling Compression (Sig``Comp), 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).
Line 14: Line 12:
Typically, Sigcomp uses the same transport protocol as the compressed protocol. Typically, Sig``Comp uses the same transport protocol as the protocol being compressed.
Line 23: Line 21:
messages containing the UDVM code is seen. The SIP library is included. Reassembly of segmented TCP packages is NOT implemented. messages containing the UDVM code is seen. The following libraries are included:
 * [[
SIP]]/[[SDP]] (1.0 and later)
 * PIDF and extensions (1.1.3 and later)
Reassembly of segmented TCP packages is NOT implemented.
Line 27: Line 28:
The level of detail of UDVM execution can be set, as well as UDP/TCP ports used. The level of detail of UDVM execution can be set, as well as [[UDP]]/[[TCP]] ports used.
Line 33: Line 34:
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]] A complete list of Sig``Comp display filter fields can be found in the [[http://www.wireshark.org/docs/dfref/s/sigcomp.html|display filter reference]]
Line 35: Line 36:
 Show only the SigComp based traffic: {{{  Show only the Sig``Comp based traffic: {{{
Line 40: Line 41:
You cannot directly filter SigComp traffic while capturing. However, if you know the [[UDP]] port used (see above), you can filter on that one. You cannot directly filter Sig``Comp traffic while capturing. However, if you know the port used (see above), you can filter on that one.
Line 42: Line 43:
 Capture only the SigComp traffic over the default SIP UDP port (5060): {{{  Capture only the Sig``Comp traffic over the default SIP UDP port (5060): {{{
Line 47: Line 48:
 * [[http://www.ietf.org/rfc/rfc3320.txt?number=3320|rfc3320]]
 * [[http://www.ietf.org/rfc/rfc3321.txt?number=3321|rfc3321]]
 * [[http://www.ietf.org/rfc/rfc4077.txt?number=4077|rfc4077]]
 * [[http://www.ietf.org/rfc/rfc3320.txt?number=3320|RFC 3320]]
 * [[http://www.ietf.org/rfc/rfc3321.txt?number=3321|RFC 3321]]
 * [[http://www.ietf.org/rfc/rfc4077.txt?number=4077|RFC 4077]]
 * [[http://www.ietf.org/rfc/rfc5112.txt?number=5112|RFC 5112]]

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 protocol being compressed.

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 following libraries are included:

  • SIP/SDP (1.0 and later)

  • PIDF and extensions (1.1.3 and later)

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 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 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)