Voice Over Ip Troubleshooting Web Site; Network Traffic Analyzer - Mitel MiVoice Business Voice Quality And Troubleshooting Manual

- "Configure System for Testing using Loopback" on page 57.
2. Access the Line Measure Quality form.
3. Click Run Test.
4. Select the Test Type. To test a single trunk select Individual Distortion/Echo then select
the PLID of the trunk. To run the test on all the eligible LS trunks in the system, select Batch
Distortion/Echo. The PLID field is disabled.
5. Click Run.
6. If the test is successful, the test results are saved in the "/db/database/LSMeasure" directory.
7. Run a System Diagnostic Report to automatically collect all the echo/distortion files. Then,
send the System Diagnostic Report files to Mitel Technical Support for analysis.

VOICE OVER IP TROUBLESHOOTING WEB SITE

Access the following web site for information on how to troubleshoot VoIP problems, free online
diagnostic tools, and useful information on voice quality and packet statistics:
http://www.voiptroubleshooter.com/about/index.html

NETWORK TRAFFIC ANALYZER

Use a network protocol analyzer (for example Wireshark
on the IP network. You can use a network traffic analyzer to
• capture data "from the wire" on a live network connection or read from a previously captured
file that contains recorded packets.
• read live data from different types of networks
• browse and filter displayed network data
• detect VoIP calls in the captured data
• verify Quality of Service settings on the MiVoice Business platform, layer 2 Switches, and
routers
• listen to problematic calls.
Note: Before using a network traffic analyzer, such as Wireshark, ensure that you disable
voice encryption in the System Options Assignment form of the MiVoice Business
System Administration Tool. After you have finished, using the analyzer, re-enable voice
encryption.
You can download the Wireshark tool from the following site: http://www.wireshark.org/. This
site also provides instructional videos on how to use Wireshark. When capturing the call using
WireShark, you should also record the call using a handset audio tap tool. It is very common
to receive reports of voice quality problems and have traces that do not show any problems.
This could be because the
• audio problems were introduced downstream from the IP network
• problems are sporadic and were not captured, or
• users expectations of call quality are unrealistic.
Using Tests and Diagnostic Tools
®
) to capture and view the traffic running
59