Drop any trace: a capture, a test-system report, a vendor export or a phone log. You get the verdict, the root cause read against the 3GPP, IETF and ITU-T codes, and the signaling flow drawn for you.
5 free analyses every month, no sign-up. The examples use synthetic traces and don't count.
The 403 was stamped by the visited network's P-CSCF, not by the home IMS. Ask the visited operator to enable IMS roaming for this home network.
Not just the last error code. Who sent it, which step really failed first, and what to ask the other side.
Not the subscriber and not the radio: the gateway's IP pool for that APN is full, so every new session fails until addresses are freed or the pool grows.
Two separate problems, not one: PTC_B never reached its P-CSCF, while PTC_A was refused by the IMS. Each gets its own next step.
The answer isn't in a phone log, but the phone's ACK reuses the INVITE branch, so per RFC 3261 the call got a final error response.
Success or failure in one sentence, the root cause, and concrete next steps per protocol.
End-to-end or hop-by-hop. Test reports and phone logs get a story view without the RRC and probe noise.
Grouped by protocol layer, searchable by IMSI, number or message name.
Dozens of traces at once with a summary by cause, multi-node merge, IMSI masking and a Word case report.
Ask for a pilot: juferfelipe+uta@gmail.com
Summary only. Full texts: Terms of Service · Privacy Policy · Refund & Cancellation.