Your log never leaves your browser

Find out why the call failed, without reading the log.

Drop an Asterisk full log in. Get the call as a timeline - SIP signalling beside dialplan execution - and a plain-English diagnosis of what went wrong.

Analyze a log free See how it works

No card. No log upload. Nothing to redact first.

Create your account

Free to start. No card.

Already have an account?

How it works

Three steps, and the middle one is a drag and drop.

01
Capture the log

Asterisk's full log, at verbose level 3 or higher, with pjsip 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

Both halves of the call, one time axis

Every SIP message between your PBX and each peer, beside the dialplan steps that produced them. No more reading two halves of a story in one interleaved file.

A diagnosis, not just a dump

Rules written from real troubleshooting name the likely cause - auth realm mismatch, codec mismatch, a variable that 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.

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`.

Analyze a log free