VOS3000 fix

VOS3000 debug trace and SIP capture

When the end reason is not enough, the signalling tells the whole story: who sent what, and when.

Updated · By the VOS3000 Web team

Quick answer: In the VOS3000 desktop client, turn on System, Debug trace, then right-click a call in Current call or CDR and open Call analysis to see the caller and callee signalling. On the server, tcpdump or sngrep capture the SIP packets for Wireshark.

Turn on
System, Debug trace
Read
Right-click a call, Call analysis
Trace file size
SS_TRACE_CALL_FILE_SIZE, 16 MB
On the server
tcpdump or sngrep

Debug trace in the desktop client

  1. In the VOS3000 desktop client, click System → Debug trace.
  2. Tick On. Trace length stops the trace automatically after that time; untick it to trace until you turn it off.
  3. Make a test call, or wait for the problem to happen again.
  4. Right-click the call in Current call or in the CDR and choose Call analysis.

Call analysis shows the Caller signaling (between the customer and VOS3000), the Callee signaling (between VOS3000 and the carrier) and the Detailed signaling. Compare the two sides: the INVITE that came in, how VOS3000 changed the numbers, what the carrier answered, and who sent the BYE.

Trace files and their size

VOS3000 writes the trace into two files and switches to the other when one is full, so the space used is double the limit, and old calls are overwritten. The limits are softswitch parameters:

ParameterDefaultWhat it sets
SS_TRACE_CALL_FILE_SIZE16 MBCall signalling trace file size (16 to 2048 MB).
SS_TRACE_REGISTER_FILE_SIZE16 MBRegistration signalling trace file size (16 to 2048 MB).
SS_TRACE_MASKERRORHow much the softswitch writes to its debug log.

On a busy switch, raise the call trace size so the call you need is still there when you look. Turn the trace off when you are done.

Capture on the server

For the full packets, including RTP, capture on the VOS3000 server over SSH:

CommandWhat it does
tcpdump -i any -n -s 0 port 5060 -w /tmp/sip.pcapSaves all SIP on port 5060 to a file for Wireshark. Use your SIP port if you changed it.
tcpdump -i any -n -s 0 host 203.0.113.10 -w /tmp/call.pcapSaves everything to and from one customer or carrier IP, including RTP.
sngrepShows SIP calls live as ladder diagrams in the terminal, if installed.

Stop tcpdump with Ctrl+C, copy the file to your computer and open it in Wireshark. Telephony → VoIP Calls lists each call; Flow Sequence draws the SIP exchange, and RTP Streams shows whether audio flowed both ways.

What to look for

  • Call fails: the first error response and who sent it; see calls failing.
  • No or one-way audio: the IP in the SDP c= line and whether RTP arrives; see one-way audio.
  • Wrong numbers: the Request-URI, From and To in the outgoing INVITE; see caller ID settings.

Questions about this topic

How do I see the SIP messages of a call in VOS3000?

Turn on System, Debug trace in the desktop client, make the call, then right-click it in Current call or CDR and choose Call analysis.

Why is Call analysis empty?

Debug trace was off when the call was made, or the trace file has since been overwritten. Turn the trace on and repeat the call.

Can I open a VOS3000 call in Wireshark?

Yes. Capture on the server with tcpdump to a .pcap file and open it in Wireshark; Telephony, VoIP Calls shows each call and its flow.

Run VOS3000 without the server work

Pick a VOS3000 server hosted by us, or have us install VOS3000 on your own server. VOS3000 Web and the Android app come with it.