

Unless you’re using a capture filter, Wireshark captures all traffic on the interface you selected when you opened the application. You can add this filter to a column in Wireshark so you can see if we have QOS configure correctly as soon as you open the file.The ability to filter capture data in Wireshark is important. Not be able to pinpoint the issue makes it extremely hard to precent a valid argument if you are dealing with multiple teams. Most of the time these issues are directly associated to the network been misconfigure or excessive traffic. When analyzing traces specially voice quality issues is good to alway check DSCP/QOS to see if it has been configured correctly.

Wireshark has filters for almost anything you can think off, SIP and VOIP are not the exception.
