Version 1

    VoIP and Network Quality Manager Manager version 4.6 builds on the SIP trunk monitoring work we introduced in the previous release. In the last release, we introduced SIP trunk health and availability metrics monitored from the Cisco Unified Call Manager element. In this release, VNQM delivers SIP trunk call metrics - with on-demand polling - and SIP trunk utilization from the Cisco Unified Border Element. It's comprehensive visibility throughout the CUCM environment.


    Monitoring the CUBE


    You'll notice there's a new resource available on the VoIP Summary Page - "VoIP Gateways." These are the border gateway elements where SIP trunks terminate.



    The Call Manager hosts in the VoIP CallManagers resource drill-down into details pages for each call manager, but the VoIP Gateways expand directly into SIP trunks:



    At this level, you can see a quick status for each trunk. Drilling into one of the trunks provides this view:



    The SIP Trunk Details view provides resources for monitoring status over time, metrics for inbound and outbound call activity, and for SIP trunk utilization.  Each of these metrics can be individually opened in a new PerfStack project, or the collection of status and call metrics for this trunk can be opened from the summary resource. In PerfStack, the "Performance Analyzer" view looks like this:



    Pulling these metrics into PerfStack allows you visibility on the same timescale for other related metrics - resources on the CUBE device for example:



    Or, perhaps the active inbound and outbound calls for several trunks:




    PerfStack gives you the flexibility to compose views that can save and use for monitoring or troubleshooting in the future.


    Immediate on-demand polling

    Note that the Inbound and Outbound call metrics from the CUBE have the "rocketship" icon next to them! This means we can enable real-time polling of these metrics from the CUBE when we're troubleshooting issues, and we need to see the current call metrics from the perspective of the CUBE. This a valuable insight into the key utilization metrics for each SIP trunk.


    SIP Trunk Utilization

    Tracking SIP trunk utilization is complex; there are several different ways to consider utilization. In this release, we're using maximum concurrent calls as the primary indicator of utilization, and calculating and presenting a percentage value that is useful for capacity planning.


    To establish the maximum concurrent calls we'll use in the utilization calculation, you'll need to visit global settings for "VoIP and Network Quality (VNQM) Settings", and select "Edit VoIP and Network Quality Settings" to see these global values for "Gateway" settings:


    In addition to the "Maximum Concurrent Calls", you can also set thresholds, polling intervals, and retention period for these metrics here.


    CLI credentials are configured at the CUBE level by selecting "Manage Gateways" and providing credentials for one or all gateway devices:


    You can also override the maximum concurrent call value in the CUBE properties:



    The default out of the box value is 100 concurrent calls. You'll want to confirm this for your environment with your SIP trunk provider.


    We're excited to provide comprehensive health, availability, and utilization monitoring for SIP trunks in the Cisco CUCM environment. Visit your Customer Portal to review the Release Notes, verify the System Requirements, and download this release. We're looking forward to you feedback and questions in the forum below.