Monitoring On-Prem and non-pingable VoIP servers in MI

Nikitha
Meraki Employee

VoIP On-Prem 

 

As the name suggests, VoIP health will now have the capability to monitor VoIP servers with Private IP addresses in DC’s that are accessible over VPN. 

 

You can add the private IP address using the “Configure VoIP servers” option and once saved the VoIP stats to the given VoIP server will be monitored. The “Private IP” field can be selected from the dropdown box under Interface, to view VoIP stats for On-Prem or private IP address server.

 

VoIP on prem .png

 

Best Effort Monitoring

 

There are some VoIP servers that do not allow or drop the ICMP pings used to monitor VoIP services such as MOS, loss, latency, and jitter. However, as VoIP services are critical and hard to identify the exact issue, we have integrated the Best Effort monitoring to VoIP Health to give a “nearest” best estimation on VoIP performance for a given link.

This tool will measure the performance of the “nearest hop” that responds to ICMP. By enabling 'Ping Nearest Hop' under the Configure VoIP server option, the MX will start pinging to the nearest best available hop to the configured VoIP server and show the MOS, loss latency, and jitter stats to it. By enabling this, the process of elimination of faulty hops becomes easy and hence reducing the Mean Time Resolution for the problem at hand.  

 

Screen Shot 2020-09-16 at 2.28.05 PM.png

 

 

For more information on how to enable VoIP On-Prem and Best Effort Monitoring and the working of each component, please refer to the KB Article.

 

This will require no firmware upgrade and organizations with SDW+ or MI license can use this feature.