Back to Blog
Tech

SIP Messages of the Call

Published on:

May 22, 2013

SIP's human-readable format, unlike H.323, allows easier understanding of the communication between clients and servers, though not everyone can interpret the details without understanding the specific RFCs. This clarity helps when troubleshooting issues, especially when reviewing SIP logs. In multi-domain environments, however, finding relevant messages can be challenging, especially when filtering by IP only works at the system level. The upcoming version 5.0.11 will address this by allowing domain administrators to access SIP logs, making it easier to diagnose issues in isolated environments independent of other system traffic. This update promises significant improvements.

Christian Stredicke

In contrast to other protocols like H.323, SIP is a "human readable" format just like HTTP or SMTP. Some people say this was the reason why SIP was more successful than H.323.

But human readable doesn't mean it can be read by all humans, especially those who didn't have the time to flip through the pages of RFC3261, RFC3262, RFC3263 and so on - and they would have had a hard time to understand what exactly is going on between the client and the server. On a side note, http://rfc3261.net is still one of the "favorite" web pages when it comes to understanding SIP.

Reading the SIP messages helps a lot to troubleshoot the problems with the many SIP service providers out there. Even if the reader understands only a fraction of the content, it's already helping. Not to mention that the people supporting snom ONE get access to traces that tell a lot about potential problems.

In the multi-domain environment, SIP logs are even more difficult to read. Especially on busy systems, finding the right messages is like searching for a needle in a hay stack. Filtering by IP address was a workaround, but it only works only at system level, which leaves the domain administrators without a workable solution.

We already collected the call-related SIP packages in the call. For example, when the PBX detected one-way audio, it would append the messages in the email that reports this event.

In the next version we will also include messages on the domain level. This will make it possible that domain administrators can look at the SIP packets. And it will make it easier to look at problems in the isolated environments independently from other traffic on the PBX.

5.0.11 will be the best we ever had.

Latest Articles

View All
Tech

Jitsi Video Conferencing in V70: A Controlled Approach to Privacy

Video conferencing is widely used, but rarely examined in terms of where it runs and who controls the infrastructure behind it. In many cases, video traffic is handled by external systems, introducing dependencies that are often overlooked. This piece explores how integrating Jitsi directly into the PBX brings video into the same environment as voice and communication management, giving organizations clearer boundaries, reduced reliance on third-party platforms, and greater control over how communication is handled.

April 21, 2026
Tech

Skills-Based Routing in V70: Match Calls to the Right Agent

Skills-based routing in V70 helps ensure incoming calls are matched with the most qualified available agents based on defined skills, language, and expertise. By combining IVR input with intelligent call distribution, organizations can reduce unnecessary transfers, improve first-contact resolution, and shorten handling time. With V70, skills can be defined directly within the PBX, allowing teams to set thresholds, prioritize expertise, and control how calls are routed across departments, queues, and different operational environments.

April 7, 2026
Tech

Snapshots in V70: Capture and Restore Your PBX with Confidence

PBX snapshots in V70 provide a reliable way to capture system state before changes are applied, enabling fast recovery, controlled rollback, and more predictable system management when updating configurations, testing call flows, or operating across multiple tenants. By preserving a point-in-time version of the system, administrators can reduce the risk of disruption, restore services quickly when issues arise, and maintain stability while making ongoing changes in complex communication environments.

March 31, 2026