
If you are troubleshooting cases where calls fail only intermittently and you need to take a long duration capture of all traffic for a VoIP card be sure to impress upon your clients that the calls are being recorded during that time period. You should not perform a Wireshark trace on client systems during sensitive calls as you will be recording the call, which can be a violation of many wiretapping laws if the participants are unaware of the recording being made.

This can be an important part of troubleshooting for VoIP systems which are malfunctioning. This means that it is possible to listen to the calls which have been captured from the Wireshark data. IMPORTANT - A Wireshark trace captures (or records) all of the packets sent to and from a VoIP endpoint. When all captures have been completed stop the current trace by selecting Stop from the Capture pull down menu.Depending on the specific nature of the problem it may be necessary to make a call to or from the VoIP device with Wireshark running in order to further troubleshoot.This will cause the VoIP device to start its registration over again while Wireshark documents the process. With the Wireshark capture running, unplug the Biamp VoIP device from the switch for 5 seconds then plug back in.If this list does not appear there may be a problem with the port mirroring process described previously in this document.įigure 3 – Scrolling List of a Wireshark Trace

You should now see a scrolling list of packets being displayed in the Wireshark window.

In the Capture pull down menu select Options.
