Home > Meraki Insight > MI VoIP Health

MI VoIP Health

VoIP Health Overview

The VoIP Health feature is designed to monitor network links for the performance of the uplink for VoIP. This feature will monitor the path from each ISP uplink to the VoIP servers (i.e. PBX or SIP server) configured by the admin.  Monitoring occurs via ICMP Probes every second to the endpoint.  The admin can use this information to estimate the call quality along each path. VoIP Health is an active monitoring tool utilizing probes from the MX to measure VoIP performance parameters and provide results based on the MOS (mean opinion score) of the link. 

 

VoIP Health solves two use cases for users:

  1. Is the link causing poor call quality?

  2. If the link is not causing poor call quality, what is the issue and who should I reach out to, to fix the problem?

Activate VoIP Health

VoIP Health is a part of the Meraki Insight product line. If your organization has Meraki Insight licenses added to the dashboard, VoIP Health should be enabled by default. For more information about Meraki Insight please refer to our Introduction to Meraki Insight article.

Configuration

To get the most out of VoIP Health, you will require the IP address of the servers or URL from your service providers. 

 

Note: IP addresses may be available on your service provider’s portal or you can find out the address by contacting your service provider's support.

Note: The URL will be resolved based on the local network’s DNS response. Once resolved, VoIP Health will start monitoring those endpoints. It also resolves on a regular basis to make sure local networks are resolving to the same IP or different. If it detects different IP, VoIP Health will automatically start monitoring the new endpoint.

 

Once you have the IP address available, try pinging it by using the ping tool on Security Appliance > Appliance Status > Tools to make sure it is reachable. After the successful ping responses, you can navigate to the Insight > VoIP Health page.

For the first time configuration, the landing page will direct you to the configuration wizard:

 

Config_1.png

 

To configure your servers, click on “Configure VoIP Servers” and it will lead you to the Add VoIP Servers screen as shown below:

 

Config_option_1.png

 

Here you can add the provider’s name for your reference and the corresponding IP address of provider’s SIP servers or a URL. If your provider has multiple SIP servers, you can add them under the same provider by clicking on Add more VoIP servers. If you use multiple providers and would like to track all of them, you can add them by clicking Add more VoIP providers. Once all the providers and servers are added, hit Save. After adding the servers, it may take up to 15 minutes for VoIP performance to populate in the dashboard.

 

Overview Page

 

Landing Page.png

 

Once MI starts collecting the data, it will show an overview of your organization links and the performance of the links for the provider’s SIP server. VoIP Health measures Loss, Latency, Jitter and MOS (mean opinion score) based on the provider's responses to the probes sent to the provider's SIP servers. Each uplink will send probes to each SIP server and give the performance analysis of the link. Depending on the MOS threshold, VoIP health will highlight the uplink in 3 different categories. The category and corresponding MOS thresholds are listed below:

 

MOS

Uplink

> 4

Good

3.5 - 4

Moderate

< 3.5

Bad

Note: We probe with ICMP pings to the server from the MX WAN interface.

 

Detailed View

By clicking on the individual link, it will show a detailed view of each of the four parameters. The graphs can be expanded for the last 2 hours, last day and last week. The MOS graph highlights time periods during which MOS dipped below the acceptable threshold, indicating that call quality may have been impacted during that time.

 

Detailed View.png

 

The detailed view also provides a network name, SIP server details, link details, and a traceroute tool to confirm the behavior and find the root cause. By clicking on hop-by-hop analysis, it will show details of each hop.

 

TraceRoute_Updated.png

 

Hop by Hop detail.png

 

How the traceroute Tool Works

VoIP Health will use traceroute to repeatedly probe each hop along the path between the MX and the VoIP server. The tool uses these probes to calculate the MOS at each hop.  If the MOS meets the threshold defined above, it will mark the hop as ‘Good’. If it violates the thresholds, it will mark the hop as ‘Bad’.

Limitations

  • VoIP Health gives performance details between two endpoints (i.e. MX and SIP server)

    • It does proactive monitoring only - it does not monitor the call quality of any calls themselves

    • VoIP Health does have metrics between MX and SIP servers. It does not have metrics between MX and any particular phones

  • The current solution is supported only for cloud-based VoIP providers who have dedicated SIP servers assigned for the network.

  • VoIP Health only works for VoIP servers that respond to ICMP pings. Please ensure that your VoIP server responds to ICMP pings before configuring VoIP Health to monitor your server

  • VoIP Health can only be configured with IPs and domains. Subnets are not currently supported

 

Last modified

Tags

Classifications

This page has no classifications.

Explore the Product

Click to Learn More

Article ID

ID: 9238

Explore Meraki

You can find out more about Cisco Meraki on our main site, including information on products, contacting sales and finding a vendor.

Explore Meraki

Contact Support

Most questions can be answered by reviewing our documentation, but if you need more help, Cisco Meraki Support is ready to work with you.

Open a Case

Ask the Community

In the Meraki Community, you can keep track of the latest announcements, find answers provided by fellow Meraki users and ask questions of your own.

Visit the Community