There is a wealth of information in there (well, maybe not a wealth, but some useful information for a non-voice engineer like me).įirstly, because the ports are non-standard, Wireshark doesn’t recognize the packets as RTP streams. Ports discovered, I decided to take a look in the Telephony menu. I am building a QoS policy to take into account the new IP handsets, however, the handset signalling and voice RTP streams don’t use any kind of standard port. The IP handsets are compatible with PoE, and I can look at doing SIP trunks between offices once the new network from the carrier is installed.

However, interbuilding copper cabling is nonexistent in some places, and uneconomic to install in a hurry (read – no budget).

The upgraded system has IP telephony capability, and this was important as we are expanding our services on the main office campus. A couple of weeks ago, we upgraded our existing office PBX. Like many, though, I’ve found it inevitable that pure packet herding will intersect with voice at some point.

Wireshark rtp stream analysis