A SIP call flow diagram, with the dialplan on it
Every SIP message between your PBX and each peer on a ladder diagram, beside the dialplan steps that produced them. No more reading two halves of a story in one interleaved file.
Your log never leaves your browser
The Asterisk log analyzer that tells you why the call failed.
Drop an Asterisk or FreePBX full
log in. Get the call as a SIP ladder diagram - signalling beside dialplan execution -
and a plain-English diagnosis of what went wrong.
No card. No log upload. Nothing to redact first.
Create your account
Free to start. No card.
Already have an account?
Recording of pbxray parsing a log
How it works
Three steps, and the middle one is a drag and drop.
-
01
Capture the log
Asterisk's
fulllog, at verbose level 3 or higher, withpjsip set logger on. That combination is what puts SIP messages and dialplan steps in the same file. -
02
Drop it in
The file is read straight off your disk by the page. Calls start filling the list within a second, while the rest of the file is still being parsed.
-
03
Read the diagnosis
Filter to the failures, open one, and see the ladder with the offending message highlighted and the likely cause named in plain English.
What you get
A diagnosis, not just a dump
26 rules written from real troubleshooting name the likely cause - a 401 auth loop on a realm mismatch, a 488 Not Acceptable Here from codec mismatch, a dial string whose variable resolved to nothing - and point at the exact line that shows it.
Built for real files
A day's log off a busy PBX is hundreds of megabytes. A 342 MB capture parses end to end in about 39 seconds, in a browser tab, on a laptop.
Client-side by construction
Your log never leaves your browser.
Parsing runs entirely on your machine, in WebAssembly. The file is never uploaded - not to us, not to anyone. There is no endpoint on this site that accepts log content, and the page's own content security policy blocks it from talking to any other server at all.
That means nothing to redact before you can use it, no customer call detail sitting on someone else's server, and no procurement conversation about where your PBX logs went.
Questions
Is my log file uploaded anywhere?
No. Parsing runs in your browser, in WebAssembly. The file is read from disk by the page and never sent to a server - there is no endpoint that could receive one.
Does it work with FreePBX?
Yes. FreePBX, Issabel and VitalPBX are Asterisk underneath and write the same
/var/log/asterisk/full file, so the log from any
of them parses the same way. Turn up verbosity and SIP logging from the Asterisk CLI
as usual.
Which SIP errors and call failures can it diagnose?
26 rules cover the failures that come up most in real troubleshooting: 401 and 407 authentication loops from a realm or credential mismatch, 403 Forbidden, 404 Not Found, 480 Temporarily Unavailable, 486 Busy Here, 488 Not Acceptable Here from a codec mismatch, 503 Service Unavailable, 603 Declined, 483 Too Many Hops from a routing loop, and on the dialplan side CHANUNAVAIL fallthrough, congestion, an empty dial string from an unset variable, a missing Goto or Gosub target, a failed AGI script and a DNS lookup that never resolved. Each one has a page in the Asterisk error reference explaining what it means and how to fix it.
Can I analyze a pcap or SIP trace instead of a log?
No. pbxray reads the Asterisk full log, not packet captures. That is deliberate: a pcap shows you SIP signalling only, while the log carries the dialplan execution beside it, which is usually the half that explains the failure.
Which Asterisk versions and channel drivers are supported?
Asterisk full logs from chan_pjsip and the older chan_sip. You need verbose level 3 or higher for dialplan detail, and SIP message logging on for the signalling half.
How large a log can it handle?
A 342 MB log parses end to end in about 39 seconds. Past roughly 600 MB a browser tab runs out of addressable memory, so split the file by day or by hour first.
Does it work with FreeSWITCH or Kamailio?
Not today. pbxray reads Asterisk logs only. Other platforms log SIP and their own routing in formats different enough that support would be a separate parser, not a flag.
What does it cost?
Free to start, and no card is needed to sign up. An account exists so your analyses can be counted against a fair monthly limit, not so anything can be billed to you by surprise.
Stop scrolling through full.
Sign up, drop in this morning's log, and see what the call actually did.
Chasing one specific error? Start from the error reference.
Analyze a log free