Beta · Free account required
SIP Call Stories
Upload a packet capture, pick a call, and read the story of what happened — in plain English.
Privacy
Your capture file is processed in memory and never written to disk or stored. Only SIP signaling packets are extracted. All other traffic (RTP audio, DNS, ARP) is discarded immediately. No capture data or analysis results are logged or retained after the response is returned to your browser.
How it works
- Upload a .pcap or .pcapng from Wireshark or tcpdump
- Parser extracts SIP packets and groups by Call-ID
- Every identified call is listed with its outcome
- Select a call for its full story, timing, and SIP ladder
Best results
- Pre-filter to SIP in Wireshark:
sipdisplay filter, then File → Export Specified Packets → Displayed - Keep captures under 20MB (pure SIP is very small)
- Include the full call flow (INVITE through BYE)
- Include REGISTER traffic if troubleshooting registration
What gets analyzed
Failed calls get a plain-English diagnosis: what was attempted, the decisive SIP response code, what that code actually means, and concrete troubleshooting steps drawn from our SIP response code reference. Authentication problems, busy and unreachable destinations, and codec rejections are all called out by name.
Quality signals are flagged on every call: excessive post-dial delay, codec negotiation problems (no common codec, DTMF gaps, downgrades), missing ACKs, retransmission bursts, holds that never resume, and mid-call renegotiation failures.
Registrations and overhead signaling are summarized per endpoint: REGISTER attempts, successes, auth challenges, and refresh intervals, plus counts of OPTIONS and SUBSCRIBE traffic.
Every finding is computed deterministically from the packets in your capture — no AI, no guesswork, and the same capture always produces the same report.