Tech

PCAP made it

Published on:

July 21, 2015

Once we have the PCAP, finding a problem is becoming almost a pleasure. Because the files are small, and everything is in the same place. It becomes easy to find jitter problems, missing RTP packets and so on. Last week I saw how another external tool took the PCAP idea to the next level. Using an Ethernet switch with port mirroring, all the traffic that hits the PBX also hits the monitoring server, which also sorts the traffic by calls and then puts them into different files. There were nice logs of SIP packets, RTP analysis and other things you want to know about a call.

A few years ago, we have added PCAP recording to the list of features supported by the Vodia PBX. At that time we were just so sick of going through Gigabytes of Wireshark traces that we just added something in the code that does this job based on the associated call. It would save us a lot of time sipping through endless lists of calls that have been recorded over hours of conversations, literally trying to find the needle in the haystack.

Once we have the PCAP, finding a problem is becoming almost a pleasure. Because the files are small, and everything is in the same place. It becomes easy to find jitter problems, missing RTP packets and so on. Last week I saw how another external tool took the PCAP idea to the next level. Using an Ethernet switch with port mirroring, all the traffic that hits the PBX also hits the monitoring server, which also sorts the traffic by calls and then puts them into different files. There were nice logs of SIP packets, RTP analysis and other things you want to know about a call.

There is only one problem when using the port mirror method: Encrypted calls will be invisible there. Because the TLS traffic cannot be intercepted by the monitoring device, it will not be able to figure out which RTP packets belong to which call, and thus not be able to put the whole call together. The PBX can do that, because it has the cryptographic context.

The disadvantage of the PBX recording all the PCAP is performance. It simply takes additional CPU horse power to write the files. The decoding is not so much a problem as it has to be done anyway. But the writing to the file system causes the system some extra work. Compared to the call recording this causes less work, because the PBX does not actually have to look into the media packets.

I can think about two things that the PBX could have in the next version. The first thing is to automatically delete the PCAP files after so-and-so many days, simply to make sure that the system is not eventually running out of disk space. The other thing is to make the PCAP files accessible from the web interface, possibly linked to the CDR records.

Latest Articles

View All

Vodia Participates in VoIP Planning Meeting

Vodia Sales Engineer Eric Altman participated in a strategic planning meeting in Washington, DC, with BCM One, SIP Trunk, Cove Central, and elite resellers to discuss joint strategies and goals for 2025. As a trusted partner of these organizations and a member of the Cove Central Technology Alliance Partner Program (TAPP) since November 2023, Vodia continues to build on its strong industry relationships. The meeting highlighted opportunities for collaboration and innovation, aligning with Vodia's 2019s recent milestone: the certification of the Vodia PBX for Microsoft Teams. Announced in November, this certification enables businesses to enhance their Teams ecosystems with critical functionalities such as SIP trunk call routing and VoIP endpoint connectivity.

January 17, 2025

Vodia & Microsoft Teams: A VoIP Solution for Transportation

Transportation companies require robust communication tools that go beyond standard features. By integrating the Microsoft-certified Vodia PBX with MS Teams, businesses gain essential functionalities like overhead paging, emergency calling, priority routing, and failover solutions. This powerful combination ensures seamless connectivity between drivers, dispatchers, and office staff, even in remote areas. With its ability to integrate with vehicle systems and non-Teams-compatible devices, the Vodia PBX transforms communication for logistics companies, enhancing safety, productivity, and customer service. It empowers transportation businesses to maintain 24/7 operational efficiency, even in the most demanding scenarios.

January 10, 2025

Vodia Networks | 2024 End-of-Year Recap

Vodia’s 2024 recap highlights several key milestones, including the certification of our PBX for Microsoft Teams, which will shape the direction of our platform moving forward. We’re addressing areas where Teams falls short, particularly through SIP interoperability. In addition, our efforts to integrate Realtime AI via APIs have shown great progress, with exciting advancements planned for 2025. We’ve also made significant improvements to our PBX interface, transitioning to the more modern Tailwind framework, and launched a native Android app. iOS improvements are also in the pipeline. With AI set to transform telephony, Vodia is positioned to lead the way, bringing AI-driven capabilities to enhance productivity in 2025.

December 20, 2024