The Session Initiation Protocol (SIP) is a signaling protocol that enables the Voice Over Internet Protocol (VoIP) by defining the messages sent between endpoints and managing the actual elements of a call. SIP supports voice calls, video conferencing, instant messaging, and media distribution.

By using VSM, SIP Session traces can be captured and stored before a problem is reported, making trouble shooting a  breeze when end users report problems. 

Use the call record to determine root cause and if the problem is internal, with a Telco or with the integrated application (eg: unsupported media type).

SIP Session traces can be stored in VSM for:

  • Session Managers
  • Session Border Controllers
    • Audio Codes
    • Avaya 
    • Cisco Unified Border Element (CUBE) 
    • Ribbon Edge Series (SWe Lite,1000,2000)


If TraceSM is run on the Session Manager it disables the output of SIP Traces to an external destination, until it is manually re-enabled.


SIP files can be huge, and cumbersome to manage, processing 10,000s of sessions per hour, each with their own message trace.  


VSM has the functionality to automatically parse this data, and show the SIP session trace, for every call ID. When configured, you'll find it under Availability Manager > SIP Session Trace.

VSM shows the full SIP trace and direction of the messages for every session, with rich filtering, sorting, and color coding of SIP responses.

By default data for the last hour is shown, but our quick filter allows users to peruse SIP traces for the last 6 hours, 24 hours, 7 days, or a custom date.

Sessions are color coded based on the SIP response code:

  • Any calls with a 5xx or 6xx error code are shown as red
  • Any calls with a 4xx error code as shown as amber
  • All other response codes are shown as green

Tip: Click above the colored RAG bar to sort by Red response codes 


To further ease troubleshooting, for any given message segment, the raw trace data can be viewed or down loaded.