Skip to main content
PCAP (Packet Capture) files record raw network traffic and are invaluable for diagnosing SIP call issues — including codec negotiation failures, audio quality problems, one-way audio, and missed DTMF tones. This guide walks through capturing and analyzing these files.

​
Prerequisites

Install the tools you need:
  • Wireshark — GUI packet analyzer (includes tshark CLI)
Verify installation: 
wireshark --version
tshark --version

​
Step 1: Open and filter the PCAP in Wireshark

Open the file in Wireshark: Once Wireshark is installed you can double click on the PCAP file and your system should open it automatically using Wireshak application. Alternatively, you can open it by using the following command: 
wireshark call_capture.pcap

​
Filter for SIP traffic only

In the Display Filter bar, enter: 
sip
This shows all SIP messages: INVITE, 100 Trying, 180 Ringing, 200 OK, ACK, BYE, CANCEL, etc.

​
Filter for a specific call (optional)

If you need to isolate a single call, find the Call-ID value in any SIP packet, then filter on it: 
sip.Call-ID == "abc123@192.168.1.1"

​
Filter for RTP media streams

rtp
Or combine SIP and RTP: 
sip or rtp

​
Step 2: Reconstruct the SIP call flow

After filtering SIP call(s), you can view the sequence (ladder) diagram by selecting Telephony → VoIP Calls:
Wireshark Telephony menu with VoIP Calls option selected
Select the call(s) from the popup window and click Flow Sequence:
VoIP Calls popup with Flow Sequence button
After clicking Flow Sequence, a new window opens with the ladder diagram showing the complete message exchange between endpoints:
SIP flow sequence ladder diagram with INVITE, 100 Trying, 180 Ringing, 200 OK, ACK, and BYE messages
The diagram shows the full call flow — INVITE → 100 Trying → 180 Ringing → 200 OK → ACK → BYE.

​
Read a SIP INVITE manually

Click the INVITE packet and expand Session Initiation Protocol in the packet detail pane. Key fields to inspect:
Wireshark packet detail view of a SIP INVITE showing Request-URI, SIP headers, and SDP parameters including codecs and DTMF negotiation
FieldWhat to look for
Request-URIDestination SIP address
From / ToCaller and callee
Call-IDUnique call identifier
SDP → m=audioNegotiated RTP port and codec list
SDP → a=rtpmapCodec payload type mappings (e.g., PCMU=0, PCMA=8, G.722=9)
SDP → a=fmtpCodec parameters

​
Step 3: Common issues and what to look for

SymptomWhat to check in PCAP
One-way audioRTP flowing only in one direction; check both SSRC streams or check the SDP → c=IN IP4 x.x.x.x information
No audio at allm=audio port in SDP is 0 (call on hold), or RTP packets absent(where RTP is supposed to be captured)
DTMF not recognizedPayload type mismatch between INVITE SDP and actual RTP packets
Audio choppy or roboticHigh jitter or packet loss in RTP Streams
Call drops unexpectedlyLook for BYE or CANCEL; check SIP response codes (4xx, 5xx)
Codec mismatchSDP 200 OK a=rtpmap differs from INVITE; or RTP payload type not in SDP
SIP auth failure407 Proxy Authentication Required or 403 Forbidden in SIP flow
408 response to INVITERemote SIP infrastructure may be unreachable — verify reachability, firewall settings, port (typically 5060 or 5061 for TLS), and SIP URI
486 response to INVITECallee rejected the call. Call maybe retried later
500/503/603 response to INVITECheck remote SIP infrastructure and downstream call routing status such as when call is routed to a downstream carrier for delivery; if you purchased phone numbers through Retell, contact Retell support

​
Common SIP response code reference

CodeMeaning
100Trying
180Ringing
200OK
401 / 407Authentication required
403Forbidden
404Not found (wrong SIP URI)
408Request timeout
486Busy here
487Request terminated (caller hung up)
500Server internal error
503Service unavailable
603Decline

​
Quick reference: filter cheatsheet

GoalWireshark filter
All SIPsip
Specific Call-IDsip.Call-ID == "id@host"
SIP INVITE onlysip.Method == "INVITE"
SIP errors (4xx/5xx)sip.Status-Code >= 400
All RTPrtp
RFC 2833 DTMFrtp.p_type == 101
SIP + RTP combinedsip or rtp
From specific IPip.src == 192.168.1.10 and (sip or rtp)

​
Advanced Debugging

The sections below use additional tools:
  • tcpdump — command-line capture (pre-installed on Linux/macOS; see tcpdump.org for other platforms)
  • sngrep — SIP-specific terminal UI (install instructions in the sngrep section below)

​
Analyze RTP streams

This applies only when your PCAP file contains RTP media packets. Some captures include SIP signaling only — for example, the PCAP files available on the Retell call details dashboard — in which case RTP and DTMF analysis are not available.

​
View all RTP streams

Go to Telephony → RTP → RTP Streams. Wireshark lists each detected stream with:
ColumnDescription
Source / DestinationIP:port pairs
SSRCSynchronization source ID
Payload typeCodec ID (e.g., 0 = PCMU, 8 = PCMA, 111 = Opus)
PacketsTotal packets in stream
LostPacket loss count and percentage
Max jitterMaximum inter-packet jitter in ms
High packet loss (>3%) or jitter (>30ms) typically causes degraded audio quality or choppy speech on Retell calls. See Call Performance for remediation steps.

​
Play back RTP audio

  1. Select a stream in RTP Streams.
  2. Click Analyze → Play Streams.
  3. Wireshark decodes and plays back the audio. This lets you hear exactly what was sent or received.

​
Save RTP audio to a file

In the RTP player, click Save payload to export raw audio. You can then open it in Audacity or convert it with ffmpeg. Install ffmpeg if needed: brew install ffmpeg (macOS) or sudo apt install ffmpeg (Debian/Ubuntu). 
# Convert raw PCMU (G.711 ulaw, 8kHz, mono) to WAV
ffmpeg -f mulaw -ar 8000 -ac 1 -i rtp_payload.raw output.wav

​
Extract and inspect DTMF events

​
Check for DTMF negotiation in SDP

In the INVITE SDP body, look for: 
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
This means RFC 2833 DTMF is negotiated on payload type 101. If this line is absent, in-band or SIP INFO DTMF may be used instead.

​
RFC 2833 / RFC 4733 DTMF (most common)

DTMF tones sent as RTP events show up as separate RTP packets with the negotiated telephone-event payload type (commonly 101). Filter for them in Wireshark: 
rtp.p_type == 101
Click any matching packet and expand Real-Time Transport Protocol → RFC 2833 RTP Event:
FieldDescription
Event IDDigit pressed: 0–9, *=10, #=11, A–D=12–15
End of eventTrue on the final packet for this digit
VolumeSignal level in dBm0
DurationTone duration in RTP timestamp units (divide by clock rate for ms)

​
SIP INFO DTMF (less common)

Some providers send DTMF as SIP INFO messages instead of RTP. Filter for them: 
sip.Method == "INFO"
Expand the packet and look for a body like: 
Signal=5
Duration=160

​
In-band DTMF (audio tones in RTP)

In-band DTMF is embedded in the audio stream as 350/440 Hz or 697–1633 Hz dual tones and cannot be filtered directly in Wireshark. To detect it:
  1. Export the RTP audio as described in Analyze RTP streams above.
  2. Analyze in Audacity (View → Spectrogram) or use a DTMF decoder library.
Retell captures RFC 2833 DTMF by default. Refer to Capture DTMF input from user for configuring DTMF completion options (digit limit, termination key, timeout).

​
Capture a PCAP file

If you don’t already have a PCAP, capture one at the network level.

​
Option A: Capture with tcpdump

tcpdump is pre-installed on Linux and macOS. For other platforms, see tcpdump.org. Capture all SIP (port 5060) and RTP (UDP ports 10000–20000) traffic on your network interface: 
sudo tcpdump -i eth0 -w call_capture.pcap \
  'udp port 5060 or (udp portrange 10000-20000)'
FlagDescription
-i eth0Network interface to capture on (use any to capture all)
-w call_capture.pcapOutput file
udp port 5060SIP signaling traffic
udp portrange 10000-20000Typical RTP media port range
Stop the capture with Ctrl+C once the call ends.

​
Option B: Capture with Wireshark (GUI)

  1. Open Wireshark and select your network interface.
  2. Set the capture filter: udp port 5060 or udp portrange 10000-20000
  3. Click Start (blue shark fin icon).
  4. Place and complete the test call.
  5. Click Stop, then File → Save As to save as .pcap or .pcapng.
If you are using Retell with a custom SIP trunk, capture traffic on the server or gateway that terminates SIP — not your local machine. See Custom Telephony for Retell’s SIP server IP ranges to filter for.

​
Analyze with tshark (CLI)

For scripting and server-side analysis without a GUI:

​
Extract all SIP messages

tshark -r call_capture.pcap -Y sip -T fields \
  -e frame.time \
  -e ip.src \
  -e ip.dst \
  -e sip.Method \
  -e sip.Status-Code \
  -e sip.Call-ID

​
List all RTP streams with stats

tshark -r call_capture.pcap -q -z rtp,streams

​
Extract RFC 2833 DTMF events

tshark -r call_capture.pcap \
  -Y "rtp.p_type == 101" \
  -T fields \
  -e frame.time \
  -e ip.src \
  -e rtpevent.event_id \
  -e rtpevent.end_of_event

​
Export all RTP audio for a stream

tshark -r call_capture.pcap \
  --export-objects rtp,/tmp/rtp_streams/

​
Use sngrep for a quick terminal SIP view (optional)

sngrep provides a real-time or offline SIP ladder diagram in the terminal — no GUI needed. 
# Install
brew install sngrep        # macOS
sudo apt install sngrep    # Debian/Ubuntu

# Read from PCAP
sngrep -I call_capture.pcap

# Live capture on SIP port
sudo sngrep -d eth0 port 5060
Navigate with arrow keys to select a call, then press Enter to view its full SIP flow and raw message content.