In contrast to pother protocols like H.323, SIP is a human readable format just like HTTP or SMTP. Some people say that this was the reason why SIP was more successful than H.323.
But the word human readable does not mean it can be read by all humans. Especially those who did not have the time to flip through the pages of RFC3261, RFC3262, RFC3263 and so on might have 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 pages when it comes to understanding SIP.
However, 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 is already helping. Not to mention the fact that the people supporting snom ONE get access to traces that are telling a lot about what potential problems could be.
In the multi-domain environment, SIP logs are even more difficult to read. Especially on busy systems finding the right messages is like searching the needle in the hay stack. Filtering by IP address was a workaround; however that works only on 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 include the messages also on the domain level. This will make it possible that the 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.
.svg)
