How can we help?

Perform a packet capture/TCP dump

Have you ever wanted to check out your signaling? Want to try and do some personal troubleshooting? Or do you have a ticket open that requires a PCAP (packet capture)? No matter the situation, the following article describes easy steps you can follow to get your PCAP. This article describes performing a packet capture/TCP dump for both Linux-based and Windows-based systems. The default port for SIP signaling (UDP or TCP) is port 5060; port 5160 can be used as an alternative port for SIP signaling. 

NOTE: Port 5061 (TCP) is used for TLS communications. If you are using TLS our Support Team will be unable to decrypt your packet capture.

 

For Linux-based systems

  1. Start a trace by running the following command: 

    tcpdump -s 3000 -w ~/flowroute-{{case.id}}.pcap port 5060 or portrange 10000-35000 
    
    tcpdump -s 3000 -w ~/flowroute-{{ticket.requester.first_name | downcase}}.pcap port 5060 or portrange 10000-35000. 
     NOTE: If you don't have tcpdump, it should be available through your distribution's package manager or from http://www.tcpdump.org/.
  2. Place a test call to reproduce the problem you're experiencing.
  3. Close the trace by pressing CTRL+C.
  4. Compress and attach the resulting file, flowroute-{{case.id}}.pcap, to the ticket so that we can analyze the file to diagnose the issue. This file will be located in your home or ~/ directory.
  5. Compress and attach the resulting file, flowroute-{{ticket.requester.first_name | downcase}}.pcap, to the ticket so that we can analyze the file to diagnose the issue. This file will be located in your home or ~/ directory.

 

For Windows-based systems

  1. Download and install a network capture tool, such as Wireshark.
  2. Click the Capture menu, and then click Interface.
  3. Select the network interface on which the traffic is being sent and received, and then click Start.
  4. Place a test call to reproduce the problem you're experiencing.
  5. Click the Stop Capture icon on the menu.
  6. Click File, and then click Save As and save the file as flowroute-{{ticket.id}}.pcap.
  7. Compress and attach the resulting file, flowroute-{{ticket.id}}.pcap, to the ticket so that we can analyze the file to diagnose the issue.
  8. Click File, and then click Save As and save the file as flowroute-{{ticket.requester.first_name | downcase}}.pcap.
  9. Compress and attach the resulting file, flowroute-{{ticket.requester.first_name | downcase}}.pcap, to the ticket so that we can analyze the file to diagnose the issue. 

 

Submit your request to Support

In order to achieve faster and more accurate support response please follow our best practices while submitting your request:

  • Authorization. Supply your account Auth information so that Support can easily locate your account: Email address on your Flowroute Account + Tech Prefix (an 8-digit number that can be located on your Dashboard)
  • Call Examples. When submitting an issue with calls, always provide us with a call example. A good call example must:
    • be less than 24 hours old: most of our carriers only store logs for 24 hours and it's critical when the issue requires escalation to external peers.
    • contain FROM and TO numbers, TIMESTAMP along with TIMEZONE, CALL-ID (you can find "sip_callid" value in CDR Report), the detailed DESCRIPTION of the issue (one-way-audio/dead-air/fast-busy/etc., error-code/message), and any other information you believe can help us to investigate this issue.