How to capture a SIP trace.
Before you can debug a SIP call, you need a trace — a .pcap, a sngrep dump, a vendor log. These short, opinionated guides walk through the fastest path for each tool real VoIP engineers actually reach for. Once you have the file, drop it into SIP Flow to render the ladder and surface RFC issues.
GUI tools
Desktop apps with a UI.
CLI tools
Headless capture from a shell.
Centralized SIP capture
Platforms that collect SIP from your whole estate.
PBX-side traces
Capture from inside your PBX.
Capture SIP traces with Asterisk
- .txt
- .pcap
Asterisk's PJSIP and chan_sip stacks both expose verbose SIP logging from the CLI. You can dump SIP messages straight to the Asterisk console or full log file, then either send the text log to SIP Flow or pcap the loopback to convert it to .pcap.
Read the Asterisk guide
Capture SIP traces with FreeSWITCH
- .txt
- .pcap
FreeSWITCH exposes SIP via the Sofia stack, and `sofia loglevel` / `sofia global siptrace` give you message-level traces without restarting. Combine with `fs_cli` and tcpdump for a complete capture suitable for SIP Flow.
Read the FreeSWITCH guide
SBC-side traces
Capture from your session border controller.
Cloud carriers
Pull traces from your provider's portal.
Got the trace? Render the ladder.
Drop your .pcap, .pcapng, or sngrep log into SIP Flow and we'll render the call flow, surface RFC issues, and (optionally) ask Gemini to explain what went wrong — all client-side by default.
Open analyzer