This wiki has been migrated to and is now deprecated. Please use that site instead.
Differences between revisions 5 and 6
Revision 5 as of 2008-10-25 11:36:19
Size: 1856
Editor: JaapKeuter
Comment: Add description of PIDF support
Revision 6 as of 2008-10-28 10:04:48
Size: 1852
Editor: AndersBroman
Comment: Reassembly is implemented
Deletions are marked like this. Additions are marked like this.
Line 24: Line 24:
Reassembly of segmented TCP packages is NOT implemented. Reassembly of segmented TCP packages is implemented.

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


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


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


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 


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