Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Network Node Manager i Software10.30

Use > Monitor with the NNM iSPI for IP Telephony > Cisco IP Telephony > Monitor Configuration for UCM

Monitor Configuration for Cisco Unified Communications Manager Clusters and Cisco Unified Communications Managers

The Monitoring Configuration feature enables you to monitor the state of additional attributes that indicate the health, performance, and availability of Cisco Unified Communications Managers, their components, and associated devices. This feature also enables you to configure thresholds and generate incidents. This topic includes the following sections:

Guidelines
Monitor UCM Call Activities
Monitor Registered Devices Count
Monitor Gateway Call Activity
Monitor Route List and Hunt List Count Configurations
Monitor Media Resource Activity
Monitor CTIManager Connections Count
Monitor Locations
Monitor SIP Trunk Sessions
Monitor RAID Status
Monitor the Cisco TFTP Server
Monitor the Health of Cisco Unified Communications Managers
Monitor the Availability of the Call Manager Administration Web Page
Monitor the Availability of Services on the UCM

This feature is not available for Cisco Unified Communications ManagerExpress systems (systems listed in the UCMEs inventory).

From each form that you open from the UCM Clusters inventory, you can open the Monitoring Configuration window by clicking Actions > IP Telephony. In the Monitoring Configuration window, you can select additional monitoring attributes for the selected device. You can view the states of these additional attributes in the following formats:

Analysis pane in the inventory views
Reports (If you enable reporting)
If you configure thresholds. Incidents in the incidents inventory

Guidelines

For the monitoring categories that are displayed at the cluster level, you must always configure the monitoring of measurement types for the Cisco Unified Communications Manager cluster, and then for the underlying Cisco Unified Communications Managers and components.
Deleting a measurement type for a Cisco Unified Communications Manager cluster results in automatic deletion of the same measurement type for the underlying Cisco Unified Communications Managers.
Threshold settings of a measurement type on a Cisco Unified Communications Manager cluster can be different from the threshold settings of the same measurement type on an underlying Cisco Unified Communications Manager.
On a newly discovered Cisco Unified Communications Manager, UCM Subscriber Group, or device pool, you must manually enable the monitoring of the same measurement types that are configured for the other devices in the cluster.
You cannot open multiple Monitoring Configuration windows at the same time. Before opening a new Monitoring Configuration window, make sure to click ( the Save icon) in the existing Monitoring Configuration window to prevent loss of configuration data.

In a Global Network Management (GNM) scenario, from the global manager console, you cannot add, delete, or disable the monitoring settings for the entities managed by the regional managers.

Monitor UCM Call Activities

You can configure the NNM iSPI for IP Telephony to monitor call activities for a Cisco Unified Communications Manager. You can monitor the following activities:

Call Activity	Description
Calls in Progress	Indicates the number of voice or video calls currently in progress on the Cisco Unified Communications Manager. This includes the number of active calls as well.
Completed Calls	Indicates the number of calls that were connected and terminated through the Cisco Unified Communications Manager.
Incomplete Calls	Indicates the difference between the attempted calls and the completed calls.
Attempted Calls	Indicates the calls attempted. A call attempt occurs when the phone is taken from the hook and replaced back on the hook. A call attempt gets registered irrespective of the call being made. A call transfer or a conference attempt increments the number of attempted calls.
Attempted System Calls	Indicates the number of calls originating from the Cisco Unified Communications Manager and the attempted calls to the Unity Message Waiting Indicator.
Active Calls	Indicates the number of voice or video calls currently active and connected to the Cisco Unified Communications Manager.

Enable the Monitoring of UCM Call Activity

The Monitoring Configuration for UCM Cluster page of the NNM iSPI for IP Telephony helps you to enable the monitoring of Cisco Unified Communications Manager (CUCM) call activity. The page displays the list of existing UCM call activity configuration settings under the UCM Call Activity tab along with the attributes enabled and the thresholds set for each configured measurement. However, you can configure the UCM Call Activity settings only after configuring the SSH credentials for the Cisco Unified Communication Manager that you want to monitor. For more information about configuring SSH credentials, see Accessing the Cisco Unified Communications Manager with SSH.

To enable the monitoring of UCM Call Activity:

From the NNMi console, click the Cisco IP Telephony workspace in the left pane.
Click UCM Clusters from the list of options. This displays the UCM Clusters view.
From the UCM Clusters view, select a cluster, and then click Actions > IP Telephony > Monitoring Configuration. The Monitoring Configuration for UCM Cluster page opens.

Alternatively, right-click a cluster in the UCM Clusters view, and then click IP Telephony > Monitoring Configuration.

On the left pane of the Monitoring Configuration for UCM Cluster page, select UCM Call Activity from the Area of Monitoring drop-down list.
From the right pane of the page, click (the New icon) to add the Measurement Type. For more information about adding a Measurement Type, see Configuring the UCM Call Activity Settings.
Click (the Refresh icon) to view the newly-added measurement type. To add more measurement types to the Call Activity setting, go to Step 5.

On the left pane of the page, specify the required details in the fields provided on the page. The following table describes the fields on the page:

Field Name	Description
Collection Interval	Select minutes (mins) or hours (hrs) from the drop-down list and specify the value in the respective box. The NNM iSPI for IP Telephony uses this value to monitor the UCM call activity for the cluster periodically.
Apply Configuration Setting to Other UCM Clusters	Select this option if you want the UCM call activity monitoring settings to be applied on other clusters.

Click (the Save icon) to save the monitoring configuration.

You can select a Cisco Unified Communications Manager from the Call Controller Details form and click Actions > IP Telephony > Monitoring Configuration from the menu to launch the Monitoring Configuration for UCM Call Activity page for the selected Cisco Unified Communications Manager. However, you cannot specify the data collection intervals if you launch the Monitoring Configuration form for a particular Cisco Unified Communications Manager—you must always specify the collection intervals at the cluster level. Individual Cisco Unified Communications Managers assume the intervals specified for the corresponding cluster.

To modify an existing UCM Call Activity configuration setting:

Select the UCM Call Activity configuration that you want to modify, and then click Edit. The Add/Update UCM Call Activity page opens.
Make the required changes and click (the Save icon) to save the modified configuration settings.

To delete an existing UCM Call Activity configuration setting:

Select the Call Activity configuration that you want to delete, and then click Delete. You can click Delete All to delete all the existing UCM Call Activity configuration settings.

To disable an existing UCM Call Activity configuration setting:

Select the UCM Call Activity configuration that you want to disable, and then click Disable All.

The Delete, Delete All, and Disable All buttons are enabled only at the UCM Cluster level.

Configure the UCM Call Activity Settings

The Add/Update UCM Call Activity page enables you to define the attributes for configuring the UCM Call Activity settings specifying threshold settings to generate incidents, and enabling monitoring and reporting for UCM call activity.

To configure the UCM Call Activity settings:

On the Add/Update UCM Call Activity page, specify the required details in the fields provided on the page. The following table describes the fields on the page:

Field Name	Description
Measurement Type	Indicates the UCM Call Activity type that is to be monitored. You can select one of the following types of measurement: Calls in Progress Completed Calls Incomplete Calls Attempted Calls Attempted System Calls Active Calls The Measurement Type list also provides the All option that enables you to select the Enable Collection and Enable Reporting check boxes to enable collection and reporting respectively, for all the available measurement types for this category. However, you must not configure any thresholds if you have selected All, as the threshold value for measurement types vary. You must always set the threshold values separately for each measurement type.
Enable Collection	Select the check box to enable collection of the selected Measurement Type.
Enable Reporting	Select the check box to enable reporting for the selected Measurement Type.
Generate Incident	Select the check box to generate incident in the incident inventory.
Threshold Severity	Indicates the severity of the incident that is generated during a threshold violation. You can select one of the following types: Critical: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachCrirtical) incident. Major: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachMajor) incident. Minor: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachMinor) incident. Warning: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachWarning) incident. The NNM iSPI for IP Telephony generates the MonitoredAttributeThresholdBreachClear incident after you resolve the cause for the generation of any of the four incidents.
Lower Base	Specify the lower base value for the UCM Call Activity type threshold.
% Lower Deviation	Specify the acceptable percentage of deviation from the lower base threshold value before generating an incident.
Abs Lower Deviation	Specify the acceptable absolute value of deviation for the lower base threshold value before generating the incident.
Lower Trigger Count	Specify the number of times the threshold deviation should be permitted for the lower base before generating the incident. Specifying the trigger count is mandatory for generating incidents.
Higher Base	Specify the higher base value for the UCM Call Activity type threshold.
% Higher Deviation	Specify the acceptable percentage of deviation from the higher base threshold value before generating an incident.
Abs Higher Deviation	Specify the acceptable absolute value of deviation for the higher base threshold value before generating the incident.
Higher Trigger Count	Specify the number of times the threshold deviation should be permitted for the higher base before generating the incident. Specifying the trigger count is mandatory for generating incidents.

Click (the Save icon) to save the UCM call activity configuration settings.

Monitor Registered Devices Count

You can monitor the count of various registered devices based in a cluster. When you configure the monitoring of registered devices counts for a cluster, the configuration settings are automatically applied to all the UCM subscriber groups, Cisco Unified Communications Managers, and the device pools in the cluster. The NNM iSPI for IP Telephony enables you to monitor the count of the following registered devices:

Analog Access Gateway Boxes
CTI Ports
CTI Route Points
H.323 Gateway Boxes
Hardware Phones
Media Resources
MGCP/SCCP EANDM
MGCP/SCCP FXO
MGCP/SCCP FXS
MGCP/SCCP Gateway Endpoints
MGCP/SCCP T1/E1 CAS
MGCP/SCCP T1/E1 PRI
Other IP Phones
Other Station Devices The counts of the Soft IP Phones, VM Ports, CTI Route Points, and CTI Ports are summed up to calculate the count of Other Station Devices.
VM Ports

You can get the exact counts of the newly configured hardware phones and other IP phones immediately after they are added to the network. The exact counts of all other devices, which are configured newly, will be available only after the next scheduled discovery of theNNM iSPI for IP Telephony.

Enable the Monitoring of Registered Devices Count

The Monitoring Configuration for UCM Cluster page of the NNM iSPI for IP Telephony helps you to enable the monitoring the counts of Cisco Unified Communications Managerregistered devices. The page displays the list of existing registered device count configuration settings under the Registered Devices Count tab along with the measurement types enabled and the thresholds set for each configured measurement. However, you can configure the Registered Devices Count settings only after configuring the SSH credentials for the Cisco Unified Communication Manager that you want to monitor. For more information about configuring SSH credentials, see Configuring SSH Access for a Cisco Unified Communications Manager Cluster.

To enable the monitoring of Registered Device Count:

From the NNMi console, click the Cisco IP Telephony workspace in the left pane.
Click UCM Clusters from the list of options listed. This displays the UCM Clusters view.
From the UCM Clusters view, select a cluster, and then click Actions > IP Telephony > Monitoring Configuration. The Monitoring Configuration for UCM Cluster page opens.

Alternatively, right-click a cluster in the UCM Clusters view, and then click IP Telephony > Monitoring Configuration.
On the left pane of the Monitoring Configuration for UCM Cluster page, select Registered Devices Count from the Area of Monitoring drop-down list.
From the right pane of the page, click (the New icon) to add the Measurement Type. For more information about adding a Measurement Type, see Configuring the Registered Devices Count Settings.
Click (the Refresh icon) to view the newly-added measurement type. To add more measurement types to the Registered Devices Count setting, go to Step 5.

On the left pane of the page, specify the required details in the fields provided on the page. The following table describes the fields on the page:

Field Name	Description
Collection Interval	Select minutes (mins) or hours (hrs) from the drop-down list and specify the value in the respective box. The NNM iSPI for IP Telephony uses this value to monitor the counts of the registered devices for the cluster periodically.
CSV Export Interval	Select minutes (mins) or hours (hrs) from the drop-down list and specify the value in the respective box. The NNM iSPI for IP Telephony uses this value to export the counts of the monitored devices for the cluster periodically.
Apply Configuration Setting to Other UCM Clusters	Select this option if you want the registered device count monitoring settings to be applied on other clusters.

Click (the Save icon) to save the monitoring configuration.

You can also launch Monitoring Configuration form for a UCM subscriber group, UCM, or device pool from the details forms of a UCM subscriber group, UCM, or device pool. If you launch the Monitoring Configuration form for a UCM subscriber group, UCM, or device pool, you cannot add a new registered device count monitoring configuration or delete an existing registered device count monitoring configuration, and you cannot enable or disable monitoring. However, you can modify the threshold settings from these forms, and enable or disable CSV export.

To modify an existing Registered Device Count configuration setting:

Select the registered device count configuration that you want to modify, and then click Edit. The Add/Update Registered Devices Count page opens.
Make the required changes and click (the Save icon) to save the modified configuration settings.

To delete an existing Registered Device Count configuration setting:

Select the registered device count configuration that you want to delete, and then click Delete. You can click Delete All to delete all the existing registered device count configuration settings.

To disable an existing Registered Device Count configuration setting:

Select the registered device count configuration that you want to disable, and then click Disable All.

The Delete, Delete All, and Disable All buttons are enabled only at the UCM Cluster level.

Configure the Registered Devices Count Settings

The Add/Update Registered Devices Count page enables you to define the attributes for configuring the Registered Devices Count settings specifying threshold settings to generate incidents, enabling monitoring for the counts of Cisco Unified Communications Managerregistered devices, and enabling CSV export for the registered devices. When you configure the monitoring of registered device count for a cluster, the configuration settings are automatically applied to all Cisco Unified Communications Manager subscriber groups, Cisco Unified Communications Managers, and device pools in the cluster.

To configure the Registered Devices Count settings:

On the Add/Update Registered Devices Count page, specify the required details in the fields provided on the page. The following table describes the fields on the page:

Field Name	Description
Measurement Type	Indicates the Device type that is to be monitored. You can select one of the following types of measurement: Analog Access Gateway Boxes CTI Ports CTI Route Points H.323 Gateway Boxes Hardware Phones Media Resources MGCP/SCCP EANDM MGCP/SCCP FXO MGCP/SCCP FXS MGCP/SCCP Gateway Endpoints MGCP/SCCP T1/E1 CAS MGCP/SCCP T1/E1 PRI Other IP Phones Other Station Devices The counts of the Soft IP Phones, VM Ports, CTI Route Points, and CTI Ports are summed up to calculate the count of Other Station Devices. VM Ports The Measurement Type list also provides the All option that enables you to select the Enable Collection and Enable Reporting check boxes to enable collection and reporting respectively, for all the available measurement types for this category. However, you must not configure any thresholds if you have selected All, as the threshold value for measurement types vary. You must always set the threshold values separately for each measurement type.
Enable Collection	Select the check box to enable collection of the selected Measurement Type.
Enable CSV Export	Select the check box to enable CSV export for the selected Measurement Type. The NNM iSPI for IP Telephony places the CSV files into the following directory on the NNMi management server: On Windows: `%nnmdatadir%\shared\ipt\CSVExport\Cisco\RegisteredDevicesCount` On UNIX/Linux: `/var/opt/OV/shared/ipt/CSVExport/Cisco/RegisteredDevicesCount` To use the CSV files, you must have sufficient privilege to access the above location.
Generate Incident	Select the check box to generate incident in the incident inventory.
Threshold Severity	Indicates the severity of the incident that is generated during a threshold violation. You can select one of the following types: Critical: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachCrirtical) incident. Major: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachMajor) incident. Minor: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachMinor) incident. Warning: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachWarning) incident. The NNM iSPI for IP Telephony generates the MonitoredAttributeThresholdBreachClear incident after you resolve the cause for the generation of any of the four incidents.
Lower Base	Specify the lower base value for the Device type threshold.
% Lower Deviation	Specify the acceptable percentage of deviation from the lower base threshold value before generating an incident.
Abs Lower Deviation	Specify the acceptable absolute value of deviation for the lower base threshold value before generating the incident.
Lower Trigger Count	Specify the number of times the threshold deviation should be permitted for the lower base before generating the incident. Specifying the trigger count is mandatory for generating incidents.
Higher Base	Specify the higher base value for the Device type threshold.
% Higher Deviation	Specify the acceptable percentage of deviation from the higher base threshold value before generating an incident.
Abs Higher Deviation	Specify the acceptable absolute value of deviation for the higher base threshold value before generating the incident.
Higher Trigger Count	Specify the number of times the threshold deviation should be permitted for the higher base before generating the incident. Specifying the trigger count is mandatory for generating incidents.

Click (the Save icon) to save the registered devices count configuration settings.

Monitor Gateway Call Activity

You can configure the NNM iSPI for IP Telephony to monitor gateway call activities of a Cisco Unified Communications Manager and the following types of gateway entities:

H.323 Gateway Box
MGCP/SCCP Gateway Interfaces

You can configure the following measurement types for monitoring the Gateway Call Activity:

Gateway Active Calls: Indicates the active calls handled by the gateways in your network.
Gateway Current Active Calls: Indicates the channels that are currently active in the H.323 gateways and the MGCP gateway interfaces in your network.

Enable the Monitoring of Gateway Call Activity

The Monitoring Configuration for UCM Cluster page of the NNM iSPI for IP Telephony helps you to enable the monitoring of Cisco Unified Communications Managergateway call activity. The page displays the list of existing gateway call activity configuration settings under the Gateway Call Activity tab along with the attributes enabled and the thresholds set for each configured measurement. However, you can configure the Gateway Call Activity settings only after configuring the SSH credentials for the Cisco Unified Communication Manager that you want to monitor. For more information about configuring SSH credentials, see Configuring SSH Access for a Cisco Unified Communications Manager Cluster.

To enable the monitoring of Gateway Call Activity:

From the NNMi console, click the Cisco IP Telephony workspace in the left pane.
Click UCM Clusters from the list of options listed. This displays the UCM Clusters view.
From the UCM Clusters view, select a cluster, and then click Actions > IP Telephony > Monitoring Configuration. The Monitoring Configuration for UCM Cluster page opens.

Alternatively, right-click a cluster in the UCM Clusters view, and then click IP Telephony > Monitoring Configuration.

On the left pane of the Monitoring Configuration for UCM Cluster page, select Gateway Call Activity from the Area of Monitoring drop-down list.
From the right pane of the page, click (the New icon) to add the Measurement Type. For more information about adding a Measurement Type, see Configuring the Gateway Call Activity Settings.
Click (the Refresh icon) to view the newly-added measurement type. To add more measurement types to the gateway call activity settings, go to Step 5.

On the left pane of the page, specify the required details in the fields provided on the page. The following table describes the fields on the page:

Field Name	Description
Collection Interval	Select minutes (mins) or hours (hrs) from the drop-down list and specify the value in the respective box. The NNM iSPI for IP Telephony uses this value to monitor the gateway call activity for the cluster periodically.
Apply Configuration Setting to Other UCM Clusters	Select this option if you want the gateway call activity monitoring settings to be applied on other clusters.

Click (the Saveicon) to save the monitoring configuration.

An H.323 gateway that is associated to more than one cluster, assumes the data collection intervals specified for the corresponding cluster to which it is associated. You cannot specify the data collection intervals for a gateway by launching the Monitoring Configuration form from the Voice Gateway Details form.

To modify an existing Gateway Call Activity configuration setting:

Select the Gateway Call Activity configuration that you want to modify, and then click Edit. The Add/Update Gateway Call Activity page opens.
Make the required changes and click (the Save icon) to save the modified configuration settings.

To delete an existing Gateway Call Activity configuration setting:

Select the Gateway Call Activity configuration that you want to delete, and then click Delete. You can click Delete All to delete all the existing Gateway Call Activity configuration settings.

To disable an existing Gateway Call Activity configuration setting:

Select the Gateway Call Activity configuration that you want to disable, and then click Disable All.

The Delete, Delete All, and Disable All buttons are enabled only at the cluster level.

You can select a gateway interface from the Voice Interfaces Gateway form to configure the monitoring of active calls on the selected gateway interface. You can configure the active call monitoring at the gateway interface level only if you have configured the same at the cluster level.

To configure the monitoring of Gateway Call Activity for a gateway interface:

From the Workspaces navigation pane, click Cisco IP Telephony > UCM Clusters. The UCM Clusters view opens in the right pane.
Select the cluster for which you want to launch the Voice Interfaces Gateway form, and then click . The UCM Cluster Details form opens.
On the right pane of the form, click the H.323 Gateways or the MGCP/SCCP Gateways tab based on your requirement to monitor the active calls. The respective view opens.
Select the gateway interface for which you want to enable the monitoring, and then click . The Voice Interfaces Gateway form opens.
Click Actions > IP Telephony > Monitoring Configuration. The Monitoring Configuration for Cisco Voice Gateway Interface, with the page opens.
From the right pane of the page, click (the New icon) to add the Measurement Type. For more information about adding a Measurement Type, see Configuring the Gateway Call Activity Settings.At the gateway interface level, you can configure active call monitoring only for those interfaces that were configured for the same at the cluster level.
Click (the Refresh icon) to view the newly-added measurement type.
Click (the Saveicon) to save the monitoring configuration.

Configure the Gateway Call Activity Settings

The Add/Update Gateway Call Activity page enables you to define the attributes for configuring the Gateway Call Activity settings such as specifying threshold settings to generate incidents and enabling monitoring for gateway call activity. When you configure the monitoring of gateway call activity for a cluster, the configuration settings are automatically applied to all the H.323 and MGCP/SCCP gateway interfaces in the cluster.

To configure the Gateway Call Activity settings:

On the Add/Update Gateway Call Activity page, specify the required details in the fields provided on the page. The following table describes the fields on the page:

Field Name	Description
Measurement Type	Indicates the Gateway Call Activity type that is to be monitored. You can select one of the following types of measurement: Gateway Active Calls Gateway Current Active Calls
Enable Collection	Select the check box to enable collection of the selected measurement type.
Enable Reporting	Select the check box to enable reporting of the selected measurement type.
Generate Incident	Select the check box to generate incident in the incident inventory.
Threshold Severity	Indicates the severity of the incident that is generated during a threshold violation. You can select one of the following types: Critical: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachCrirtical) incident. Major: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachMajor) incident. Minor: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachMinor) incident. Warning: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachWarning) incident. The NNM iSPI for IP Telephony generates the MonitoredAttributeThresholdBreachClear incident after you resolve the cause for the generation of any of the four incidents.
Lower Base	Specify the lower base value for the Gateway Call Activity type threshold.
% Lower Deviation	Specify the acceptable percentage of deviation from the lower base threshold value before generating an incident.
Abs Lower Deviation	Specify the acceptable absolute value of deviation for the lower base threshold value before generating the incident.
Lower Trigger Count	Specify the number of times the threshold deviation should be permitted for the lower base before generating the incident. Specifying the trigger count is mandatory for generating incidents.
Higher Base	Specify the higher base value for the Gateway Call Activity type threshold.
% Higher Deviation	Specify the acceptable percentage of deviation from the higher base threshold value before generating an incident.
Abs Higher Deviation	Specify the acceptable absolute value of deviation for the higher base threshold value before generating the incident.
Higher Trigger Count	Specify the number of times the threshold deviation should be permitted for the higher base before generating the incident. Specifying the trigger count is mandatory for generating incidents.

Click (the Save icon) to save the gateway call activity configuration settings.

Monitor Route List and Hunt List Count Configurations

You can configure the NNM iSPI for IP Telephony to monitor the route list and hunt list counts for a Cisco Unified Communications Manager. A route list is a set of route groups arranged in a specific order responsible for regulating the available devices for outgoing calls. A hunt list is a set of line groups arranged in a specific order responsible for regulating the available directory numbers for incoming calls.

Enable the Monitoring of Route List and Hunt List Count Configurations

The Monitoring Configuration for UCM Cluster page of the NNM iSPI for IP Telephony helps you to enable the monitoring the counts of Cisco Unified Communications Managerroute list and hunt list configurations. The page displays the list of existing route list and hunt list count configuration settings under the Configurations tab along with the attributes enabled and the thresholds set for each configured measurement. However, you can configure the route list and hunt list count settings only after configuring the AXL credentials for the cluster that you want to monitor. For more information about configuring AXL credentials, see Configuring AXL Data Access for a Cisco Unified Communications Manager Cluster.

Monitoring of the count of route lists and hunt lists enables you to configure thresholds for the monitored devices. The NNM iSPI for IP Telephony generates the MonitoredAttributeThresholdBreach incidents when the thresholds are violated.

To enable the monitoring of route list or hunt list count:

From the NNMi console, click the Cisco IP Telephony workspace in the left pane.
Click UCM Clusters from the list of options listed. This displays the UCM Clusters view.
From the UCM Clusters view, select a cluster, and then click Actions > IP Telephony > Monitoring Configuration. The Monitoring Configuration for UCM Cluster page opens.

Alternatively, right-click a cluster in the UCM Clusters view, and then click IP Telephony > Monitoring Configuration.
On the left pane of the Monitoring Configuration for UCM Cluster page, select Configurations from the Area of Monitoring drop-down list.
From the right pane of the page, click (the New icon) to add the Measurement Type. For more information about adding a Measurement Type, see Configuring the Route List and Hunt List Count Settings.
Click (the Refresh icon) to view the newly-added measurement type. To add more measurement types to the route list and hunt list count setting, go to Step 5.

On the left pane of the page, specify the required details in the fields provided on the page. The following table describes the fields on the page:

Field Name	Description
Collection Interval	Select minutes (mins) or hours (hrs) from the drop-down list and specify the value in the respective box. The NNM iSPI for IP Telephony uses this value to monitor the counts of the route lists and hunt lists for the cluster periodically.
CSV Export Interval	Select minutes (mins) or hours (hrs) from the drop-down list and specify the value in the respective box. The NNM iSPI for IP Telephony uses this value to export the counts of the route lists and hunt lists for the cluster periodically.
Apply Configuration Setting to Other UCM Clusters	Select this option if you want the route lists and hunt lists count monitoring settings to be applied on other clusters.

Click (the Save icon) to save the monitoring configuration.

To modify an existing route list or hunt list count configuration setting:

Select the route list or hunt list count configuration that you want to modify, and then click Edit. The Add/Update Configurations page opens.
Make the required changes and click (the Save icon) to save the modified configuration settings.

To delete an existing route list or hunt list count configuration setting:

Select the route list or hunt list count configuration that you want to delete, and then click Delete. You can click Delete All to delete all the existing registered device count configuration settings.

To disable an existing route list or hunt list count configuration setting:

Select the route list or hunt list count configuration that you want to disable, and then click Disable All.

The Delete, Delete All, and Disable All buttons are enabled only at the UCM Cluster level.

Configure the Route List and Hunt List Count Settings

The Add/Update Configurations page enables you to define the attributes for configuring the route list count or hunt list count settings specifying threshold settings to generate incidents, enabling monitoring for the counts of Cisco Unified Communications Managerroute list and hunt list, and enabling CSV export for the route list and hunt list.

To configure the route list count or hunt list count settings:

On the Add/Update Configurations page, specify the required details in the fields provided on the page. The following table describes the fields on the page:

Field Name	Description
Measurement Type	Indicates the Configuration type that is to be monitored. You can select one of the following types of measurement: Route List Hunt List The Measurement Type list also provides the All option that enables you to select the Enable Collection and Enable CSV Export check boxes to enable collection and csv exporting respectively, for all the available measurement types for this category. However, you must not configure any thresholds if you have selected All, as the threshold value for measurement types vary. You must always set the threshold values separately for each measurement type.
Enable Collection	Select the check box to enable collection of the selected Measurement Type.
Enable CSV Export	Select the check box to enable CSV export for the selected Measurement Type. The NNM iSPI for IP Telephony places the CSV files into the following directory on the NNMi management server: On Windows: `%nnmdatadir%\shared\ipt\CSVExport\Cisco\RegisteredDevicesCount` On UNIX/Linux: `/var/opt/OV/shared/ipt/CSVExport/Cisco/RegisteredDevicesCount` To use the CSV files, you must have sufficient privilege to access the above location.
Generate Incident	Select the check box to generate incident in the incident inventory.
Threshold Severity	Indicates the severity of the incident that is generated during a threshold violation. You can select one of the following types: Critical: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachCrirtical) incident. Major: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachMajor) incident. Minor: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachMinor) incident. Warning: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachWarning) incident. The NNM iSPI for IP Telephony generates the MonitoredAttributeThresholdBreachClear incident after you resolve the cause for the generation of any of the four incidents.
Lower Base	Specify the lower base value for the Configuration type threshold.
% Lower Deviation	Specify the acceptable percentage of deviation from the lower base threshold value before generating an incident.
Abs Lower Deviation	Specify the acceptable absolute value of deviation for the lower base threshold value before generating the incident.
Lower Trigger Count	Specify the number of times the threshold deviation should be permitted for the lower base before generating the incident. Specifying the trigger count is mandatory for generating incidents.
Higher Base	Specify the higher base value for the Configuration type threshold.
% Higher Deviation	Specify the acceptable percentage of deviation from the higher base threshold value before generating an incident.
Abs Higher Deviation	Specify the acceptable absolute value of deviation for the higher base threshold value before generating the incident.
Higher Trigger Count	Specify the number of times the threshold deviation should be permitted for the higher base before generating the incident. Specifying the trigger count is mandatory for generating incidents.

Click (the Save icon) to save the route list or hunt list count configuration settings.

Monitor Media Resource Activity

You can configure the NNM iSPI for IP Telephony to monitor the media resources in each cluster. You can configure media resource activity monitoring for a cluster as well as for a media device.When you configure the monitoring for media resources of a cluster, the configuration settings are automatically applied to all the media devices in the cluster. You can monitor the following activities:

Media Resource Activity	Description
Active Resources	Indicates the number of resources that are currently in use.
Unavailable Resources	Indicates the number of unsuccessful attempts made to allocate a media resource from the device. The unsuccessful attempts occur when all media resources in the device are in use.
Available Resources	Indicates the number of resources that are available to be used. These resources are not in use at the current time.
Total Resources	Indicates the total number of media resources.

Enable the Monitoring of Media Resource Activity

The Monitoring Configuration for UCM Cluster page of the NNM iSPI for IP Telephony helps you to enable the monitoring of the media resource activity in each cluster. The page displays the list of existing media resource activity configuration settings under the Media Resource Activity tab along with the attributes enabled and the thresholds set for each configured measurement. However, you can configure the Media Resource Activity settings only after configuring the SSH credentials for the Cisco Unified Communication Manager that you want to monitor. For more information about configuring SSH credentials, see Configuring SSH Access for a Cisco Unified Communications Manager Cluster.

To enable the monitoring of media resource activity:

From the NNMi console, click the Cisco IP Telephony workspace in the left pane.
Click UCM Clusters from the list of options listed. This displays the UCM Clusters view.
From the UCM Clusters view, select a cluster, and then click Actions > IP Telephony > Monitoring Configuration. The Monitoring Configuration for UCM Cluster page opens.

Alternatively, right-click a cluster in the UCM Clusters view, and then click IP Telephony > Monitoring Configuration.
On the left pane of the Monitoring Configuration for UCM Cluster page, select Media Resource Activity from the Area of Monitoring drop-down list.
From the right pane of the page, click (the New icon) to add the Measurement Type. For more information about adding a Measurement Type, see Configuring the Media Resource Activity Settings.
Click (the Refresh icon) to view the newly-added measurement type. To add more measurement types to the Media Resource Activity setting, go to Step 5.

On the left pane of the page, specify the required details in the fields provided on the page. The following table describes the fields on the page:

Field Name	Description
Collection Interval	Select minutes (mins) or hours (hrs) from the drop-down list and specify the value in the respective box. The NNM iSPI for IP Telephony uses this value to monitor the media resource activity for the cluster periodically.
Apply Configuration Setting to Other UCM Clusters	Select this option if you want the media resource activity monitoring settings to be applied on other clusters.

Click (the Save icon) to save the monitoring configuration.

You can select a media device from the Media Device Details form and click Actions > IP Telephony > Monitoring Configuration from the menu to launch the Monitoring Configuration for Cisco Media Device page for the selected media device. You can add a new Media Resource Activity monitoring configuration for a media device from the Media Device Details form only if you have added the same configuration at the cluster level. However, you can add monitoring configurations for the new media devices added to the topology after you configured the Media Resource Activity monitoring for the cluster.

To modify an existing Media Resource Activity configuration setting:

Select the Media Resource Activity configuration that you want to modify, and then click Edit. The Add/Update Media Resource Activity page opens.
Make the required changes and click (the Save icon) to save the modified configuration settings.

To delete an existing Media Resource Activity configuration setting:

Select the Media Resource Activity configuration that you want to delete, and then click Delete. You can click Delete All to delete all the existing Media Resource Activity configuration settings.

To disable an existing Media Resource Activity configuration setting:

Select the Media Resource Activity configuration that you want to disable, and then click Disable All.

The Delete, Delete All, and Disable All buttons are enabled only at the UCM Cluster level.

Configure the Media Resource Activity Settings

The Add/Update Media Resource Activity page enables you to define the attributes for configuring the media resource activity settings specifying threshold settings to generate incidents, enabling monitoring, and enabling reporting for the media devices.

To configure the media resource activity settings:

On the Add/Update Media Resource Activity page, specify the required details in the fields provided on the page. The following table describes the fields on the page:

Field Name	Description
Measurement Type	Indicates the Media Resource type that is to be monitored. You can select one of the following types of measurement: Active Resources Unavailable Resources Available Resources Total Resources The Measurement Type list also provides the All option that enables you to select the Enable Collection and Enable Reporting check boxes to enable collection and reporting respectively, for all the available measurement types for this category. However, you must not configure any thresholds if you have selected All, as the threshold value for measurement types vary. You must always set the threshold values separately for each measurement type.
Enable Collection	Select the check box to enable collection of the selected Measurement Type.
Enable Reporting	Select the check box to enable reporting for the selected Measurement Type.
Generate Incident	Select the check box to generate incident in the incident inventory. The Generate Incident check box is disabled at the cluster level. You can set thresholds to generate incidents for a device at the media device level. You can select a media device from the Media Device Details form and click Actions > IP Telephony > Monitoring Configuration from the menu to launch the Monitoring Configuration for Cisco Media Device page for the selected media device.
Threshold Severity	Indicates the severity of the incident that is generated during a threshold violation. You can select one of the following types: Critical: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachCrirtical) incident. Major: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachMajor) incident. Minor: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachMinor) incident. Warning: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachWarning) incident. The NNM iSPI for IP Telephony generates the MonitoredAttributeThresholdBreachClear incident after you resolve the cause for the generation of any of the four incidents.
Lower Base	Specify the lower base value for the Media Resource type threshold.
% Lower Deviation	Specify the acceptable percentage of deviation from the lower base threshold value before generating an incident.
Abs Lower Deviation	Specify the acceptable absolute value of deviation for the lower base threshold value before generating the incident.
Lower Trigger Count	Specify the number of times the threshold deviation should be permitted for the lower base before generating the incident. Specifying the trigger count is mandatory for generating incidents.
Higher Base	Specify the higher base value for the Media Resource type threshold.
% Higher Deviation	Specify the acceptable percentage of deviation from the higher base threshold value before generating an incident.
Abs Higher Deviation	Specify the acceptable absolute value of deviation for the higher base threshold value before generating the incident.
Higher Trigger Count	Specify the number of times the threshold deviation should be permitted for the higher base before generating the incident. Specifying the trigger count is mandatory for generating incidents.

Click (the Save icon) to save the media resource activity configuration settings.

Monitor CTIManager Connections Count

You can configure the NNM iSPI for IP Telephony to monitor the active connections count of the AXL CTIManager for a Cisco Unified Communications Manager (CUCM). You can monitor the following activities:

CTIManager Connections Count	Description
CTIConnectionActive	Indicates the total number of CTI clients that are currently connected to the CTIManager. While the CTIConnectionActive count increases by one when a new connection is established, the count decreases by one when a connection is released.
Ccm LinkActive	Indicates the total number of active CUCM links. The CTIManager maintains links to all the active CUCM in the cluster.
Devices Open	Indicates the total number of devices such as hardware IP phones, CTI ports, and CTI route points that are configured in the CUCM that the CTI applications control and monitor.
Lines Open	Indicates the total number of lines that are configured in the CUCM that control and monitor the CTI applications.

To enable the monitoring of these attributes, you must also turn on the CTIManager service on the CUCMs.

Enable the Monitoring of CTIManager Connections Count

The Monitoring Configuration for UCM Cluster page of the NNM iSPI for IP Telephony helps you to enable the monitoring of the CTIManager Connections Count. The page displays the list of the existing configuration settings under the CTIManager Connections Count tab along with the attributes enabled and the thresholds set for each configured measurement.

To enable the monitoring of CTIManager Connections Count:

From the NNMi console, click the Cisco IP Telephony workspace in the left pane.
Click UCM Clusters from the list of options listed. This displays the UCM Clusters view.
From the UCM Clusters view, select a cluster, and then click Actions > IP Telephony > Monitoring Configuration. The Monitoring Configuration for UCM Cluster page opens.

Alternatively, right-click a cluster in the UCM Clusters view, and then click IP Telephony > Monitoring Configuration.

On the left pane of the Monitoring Configuration for UCM Cluster page, select CTIManager Connections Count from the Area of Monitoring drop-down list.
From the right pane of the page, click (the New icon) to add the Measurement Type. For more information about adding a Measurement Type, see Configuring the CTIManager Connections Count Settings.
Click (the Refresh icon) to view the newly-added measurement type. To add more measurement types to the CTIManager Connections Count setting, go to Step 5.

On the left pane of the page, specify the required details in the fields provided on the page. The following table describes the fields on the page:

Field Name	Description
Collection Interval	Select minutes (mins) or hours (hrs) from the drop-down list and specify the value in the respective box. The NNM iSPI for IP Telephony uses this value to monitor the connections count for the CTIManager periodically.
Apply Configuration Setting to Other UCM Clusters	Select this option if you want the CTIManager connections count monitoring settings to be applied on other clusters.

Click (the Save icon) to save the monitoring configuration.

You can select a Cisco Unified Communications Manager from the Call Controller Details form and click Actions > IP Telephony > Monitoring Configuration from the menu to launch the Monitoring Configuration for the CTIManager Connections Count page for the selected Cisco Unified Communications Manager. However, you cannot specify the data collection intervals if you launch the Monitoring Configuration form for a particular Cisco Unified Communications Manager—you must always specify the collection intervals at the cluster level. Individual Cisco Unified Communications Managers assume the intervals specified for the corresponding cluster.

To modify an existing CTIManager Connections Count configuration setting:

Select the CTIManager Connections Count configuration that you want to modify, and then click Edit. The Add/Update CTIManager Connections Count page opens.
Make the required changes and click (the Save icon) to save the modified configuration settings.

To delete an existing CTIManager Connections Count configuration setting:

Select the CTIManager Connections Count configuration that you want to delete, and then click Delete. You can click Delete All to delete all the existing CTIManager Connections Count configuration settings.

To disable an existing CTIManager Connections Count configuration setting:

Select the CTIManager Connections Count configuration that you want to disable, and then click Disable All.

The Delete, Delete All, and Disable All buttons are enabled only at the UCM Cluster level.

Configure the CTIManager Connections Count Settings

The Add/Update CTIManager Connections Count page enables you to define the attributes for configuring the CTIManager Connections Count settings specifying threshold settings to generate incidents, and enabling monitoring and reporting for the active connections of the CTIManager.

To configure the CTIManager Connections Count settings:

On the Add/Update CTIManager Connections Count page, specify the required details in the fields provided on the page. The following table describes the fields on the page:

Field Name	Description
Measurement Type	Indicates the CTIManager Connections Count type that is to be monitored. You can select one of the following types of measurement: CTIConnectionActive Ccm LinkActive Devices Open Lines Open The Measurement Type list also provides the All option that enables you to select the Enable Collection and Enable Reporting check boxes to enable collection and reporting respectively, for all the available measurement types for this category. However, you must not configure any thresholds if you have selected All, as the threshold value for measurement types vary. You must always set the threshold values separately for each measurement type.
Enable Collection	Select the check box to enable collection of the selected Measurement Type.
Enable Reporting	Select the check box to enable reporting for the selected Measurement Type.
Generate Incident	Select the check box to generate incident in the incident inventory.
Threshold Severity	Indicates the severity of the incident that is generated during a threshold violation. You can select one of the following types: Critical: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachCrirtical) incident. Major: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachMajor) incident. Minor: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachMinor) incident. Warning: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachWarning) incident. The NNM iSPI for IP Telephony generates the MonitoredAttributeThresholdBreachClear incident after you resolve the cause for the generation of any of the four incidents.
Lower Base	Specify the lower base value for the CTIManager Connections Count type threshold.
% Lower Deviation	Specify the acceptable percentage of deviation from the lower base threshold value before generating an incident.
Abs Lower Deviation	Specify the acceptable absolute value of deviation for the lower base threshold value before generating the incident.
Lower Trigger Count	Specify the number of times the threshold deviation should be permitted for the lower base before generating the incident. Specifying the trigger count is mandatory for generating incidents.
Higher Base	Specify the higher base value for the CTIManager Connections Count type threshold.
% Higher Deviation	Specify the acceptable percentage of deviation from the higher base threshold value before generating an incident.
Abs Higher Deviation	Specify the acceptable absolute value of deviation for the higher base threshold value before generating the incident.
Higher Trigger Count	Specify the number of times the threshold deviation should be permitted for the higher base before generating the incident. Specifying the trigger count is mandatory for generating incidents.

Click (the Save icon) to save the configuration settings.

Monitor Locations

You can configure the NNM iSPI for IP Telephony to monitor the Cisco Locations at the UCM Cluster and Locations levels. You can configure the following type of measurement attribute for monitoring Locations:

Out Of Resources: Indicates the total number of times that a call on a particular Cisco Unified Communications Manager (CUCM) through the location failed due to lack of bandwidth.

In a CUCM 9x cluster, the Out Of Resources measurement attribute is not available for the pre-configured Cisco Locations such as Phantom and Shadow.

Enable the Monitoring of Locations

The Monitoring Configuration for UCM Cluster page of the NNM iSPI for IP Telephony helps you to enable the monitoring of Locations. The page displays the list of existing Locations configuration settings under the Locations tab along with the attributes enabled and the thresholds set for each configured measurement. However, you can configure the Locations settings only after configuring the SSH credentials for the Cisco Unified Communication Manager that you want to monitor. For more information about configuring SSH credentials, see Configuring SSH Access for a Cisco Unified Communications Manager Cluster.

To enable the monitoring of Locations:

From the NNMi console, click the Cisco IP Telephony workspace in the left pane.
Click UCM Clusters. The UCM Clusters view opens.
Select a UCM Cluster of your interest and click Actions > IP Telephony > Monitoring Configuration. The Monitoring Configuration for UCM Cluster page opens. Alternatively, you can also launch the Monitoring Configuration page for locations from the Location Details form. If you launch the Monitoring Configuration page for locations, you cannot do the following:
- Add a new location monitoring configuration
- Delete an existing location monitoring configuration
- Enable or disable monitoring
However, you can add the threshold settings only at the Location Details form level.
On the left pane of the Monitoring Configuration for UCM Cluster page, select Locations from the Area of Monitoring drop-down list.
From the right pane of the page, click (the New icon) to add the Measurement Type. For more information about adding a Measurement Type, see Configuring the Locations Settings.
Click (the Refresh icon) to view the newly-added measurement type. To add more measurement types to the Locations setting, go to Step 5.
On the left pane of the page, select minutes (mins) or hours (hrs) from the Collection Interval drop-down list and specify the value in the respective box. The NNM iSPI for IP Telephony uses this value to periodically monitor the Locations for the UCM Cluster. The default value is five minutes. You can select only a value that is greater than the default value.
Click (the Save icon ) to save the monitoring configuration.

To modify an existing Locations configuration setting:

Select the Location configuration that you want to modify, and then click Edit. The Add/Update Location page opens.
Make the required changes and click (the Save icon) to save the modified configuration settings.

To delete an existing Locations configuration setting:

Select the Location configuration that you want to delete, and then click Delete. You can click Delete All to delete all the existing Location configuration settings.

To disable an existing Locations configuration setting:

Select the Location configuration that you want to disable, and then click Disable All.

The Delete, Delete All, and Disable All buttons are enabled only at the UCM Cluster level.

Configure the Locations Settings

The Add/Update Location page enables you to define the attributes for configuring Locations.

To configure Locations settings:

On the Add/Update Location page, specify the required details in the fields provided on the page. The following table describes the fields on the page:

Field Name	Description
Measurement Type	Indicates the Location type that is to be monitored. The following type is available: Out Of Resources
Enable Collection	Select the check box to enable collection of the selected Measurement Type.
The following fields are enabled only at the Location Details form level:
Generate Incident	Select the check box to generate incident in the incident inventory.
Threshold Severity	Indicates the severity of the incident that is generated during a threshold violation. You can select one of the following types: Critical: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachCrirtical) incident. Major: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachMajor) incident. Minor: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachMinor) incident. Warning: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachWarning) incident. The NNM iSPI for IP Telephony generates the MonitoredAttributeThresholdBreachClear incident after you resolve the cause for the generation of any of the four incidents.
Lower Base	Specify the lower base value for the Locations type threshold.
% Lower Deviation	Specify the acceptable percentage of deviation from the lower base threshold value before generating an incident.
Abs Lower Deviation	Specify the acceptable absolute value of deviation for the lower base threshold value before generating the incident.
Lower Trigger Count	Specify the number of times the threshold deviation should be permitted for the lower base before generating the incident. Specifying the trigger count is mandatory for generating incidents.
Higher Base	Specify the higher base value for the Locations type threshold.
% Higher Deviation	Specify the acceptable percentage of deviation from the higher base threshold value before generating an incident.
Abs Higher Deviation	Specify the acceptable absolute value of deviation for the higher base threshold value before generating the incident.
Higher Trigger Count	Specify the number of times the threshold deviation should be permitted for the higher base before generating the incident. Specifying the trigger count is mandatory for generating incidents.

Click (the Save icon ) to save the configuration settings.

Monitor SIP Trunk Sessions

You can configure the NNM iSPI for IP Telephony to monitor the SIP trunk sessions for a Cisco Unified Communications Manager (CUCM). You can monitor the following activities:

SIP Trunk Sessions	Description
Active Calls	Indicates the total number of active calls on the SIP Trunk Session.
Attempted Calls	Indicates the total number of attempted calls on the SIP Trunk Session.
Calls in Progress	Indicates the total number of calls in progress on the SIP Trunk Session.
Completed Calls	Indicates the total number of completed calls on the SIP Trunk Session.

Enable the Monitoring of SIP Trunk Sessions

The Monitoring Configuration for UCM Cluster page of the NNM iSPI for IP Telephony helps you to enable the monitoring of SIP Trunk Sessions. The page displays the list of existing SIP trunk session configuration settings under the SIP Trunk Sessions tab along with the attributes enabled and the thresholds set for each configured measurement. However, you can configure the SIP trunk sessions settings only after configuring the SSH credentials for the Cisco Unified Communication Manager that you want to monitor. For more information about configuring SSH credentials, see Accessing the Cisco Unified Communications Manager with SSH.

To enable the monitoring of SIP trunk sessions:

From the NNMi console, click the Cisco IP Telephony workspace in the left pane.
Click UCM Clusters. The UCM Clusters view opens.
Select a UCM Cluster of your interest and click Actions > IP Telephony > Monitoring Configuration. The Monitoring Configuration for UCM Cluster page opens. Alternatively, you can also launch the Monitoring Configuration page for the SIP trunk sessions from the SIP Trunk Details and the Call Controller Details forms. When you launch the page using the SIP Trunk Details and the Call Controller Details forms, you cannot do the following:
- Add a new SIP trunk sessions monitoring configuration
- Delete an existing SIP trunk sessions monitoring configuration
- Enable or disable monitoring
However, you can add the threshold settings only at the SIP Trunk Details form level.
On the left pane of the Monitoring Configuration for UCM Cluster page, select SIP Trunk Sessions from the Area of Monitoring drop-down list.
From the right pane of the page, click (the New icon) to add the Measurement Type. For more information about adding a Measurement Type, see Configuring the SIP Trunk Sessions Settings.
Click (the Refresh icon) to view the newly-added measurement type. To add more measurement types to the SIP Trunk Sessions setting, go to Step 5.
On the left pane of the page, select minutes (mins) or hours (hrs) from the Collection Interval drop-down list and specify the value in the respective box. The NNM iSPI for IP Telephony uses this value to periodically monitor the SIP Trunk Sessions for the UCM Cluster. The default value is five minutes. You can select only a value that is greater than the default value.
Click (the Save icon ) to save the monitoring configuration.

To modify an existing SIP Trunk Sessions configuration setting:

Select the SIP Trunk Sessions configuration that you want to modify, and then click Edit. The Add/Update SIP Trunk Sessions page opens.
Make the required changes and click (the Save icon) to save the modified configuration settings.

To delete an existing SIP Trunk Sessions configuration setting:

Select the SIP Trunk Sessions configuration that you want to delete, and then click Delete. You can click Delete All to delete all the existing SIP Trunk Sessions configuration settings.

To disable an existing SIP Trunk Sessions configuration setting:

Select the SIP Trunk Sessions configuration that you want to disable, and then click Disable All.

The Delete, Delete All, and Disable All buttons are enabled only at the UCM Cluster level.

Configure the SIP Trunk Sessions Settings

The Add/Update SIP Trunk Sessions page enables you to define the attributes for configuring SIP Trunk Sessions.

To configure SIP Trunk Sessions settings:

On the Add/Update SIP Trunk Sessions page, specify the required details in the fields provided on the page. The following table describes the fields on the page:

Field Name	Description
Measurement Type	Indicates the SIP Trunk Sessions type that is to be monitored. You can select one of the following types of measurement: Active Calls Attempted Calls Calls in Progress Completed Calls The Measurement Type list also provides the All option that enables you to select the Enable Collection check box to enable collection for all the available measurement types for this category. However, you must not configure any thresholds if you have selected All, as the threshold value for measurement types vary. You must always set the threshold values separately for each measurement type.
Enable Collection	Select the check box to enable collection of the selected Measurement Type.
Generate Incident	Select the check box to generate incident in the incident inventory.
Threshold Severity	Indicates the severity of the incident that is generated during a threshold violation. You can select one of the following types: Critical: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachCrirtical) incident. Major: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachMajor) incident. Minor: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachMinor) incident. Warning: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachWarning) incident. The NNM iSPI for IP Telephony generates the MonitoredAttributeThresholdBreachClear incident after you resolve the cause for the generation of any of the four incidents.
Lower Base	Specify the lower base value for the SIP Trunk Sessions type threshold.
% Lower Deviation	Specify the acceptable percentage of deviation from the lower base threshold value before generating an incident.
Abs Lower Deviation	Specify the acceptable absolute value of deviation for the lower base threshold value before generating the incident.
Lower Trigger Count	Specify the number of times the threshold deviation should be permitted for the lower base before generating the incident. Specifying the trigger count is mandatory for generating incidents.
Higher Base	Specify the higher base value for the SIP Trunk Sessions type threshold.
% Higher Deviation	Specify the acceptable percentage of deviation from the higher base threshold value before generating an incident.
Abs Higher Deviation	Specify the acceptable absolute value of deviation for the higher base threshold value before generating the incident.
Higher Trigger Count	Specify the number of times the threshold deviation should be permitted for the higher base before generating the incident. Specifying the trigger count is mandatory for generating incidents.

Click (the Save icon ) to save the configuration settings.

Monitor RAID Status

You can configure the NNM iSPI for IP Telephony to monitor the status of the various attributes of the Redundant Array of Independent Disks (RAID) of a Cisco Unified Communications Manager (CUCM). You can monitor the following activities:

RAID Status	Description
Critical Disks	Indicates the total number of critical disks on the RAID of the CUCM.
Disks	Indicates the total number of disks on the RAID of the CUCM.
Failed Disks	Indicates the total number of failed disks on the RAID of the CUCM.
Media Error Count	Indicates the total number of media errors on all the slots of the RAID.
Other Error Count	Indicates the total number of other errors on all the slots of the RAID.
Physical Devices	Indicates the total number of physical devices on the RAID of the CUCM.

Enable the Monitoring of RAID Status

The Monitoring Configuration for UCM Cluster page of the NNM iSPI for IP Telephony helps you to enable the monitoring of RAID status. The page displays the list of existing RAID status configuration settings under the RAID Status tab, along with the attributes enabled and the thresholds set for each configured measurement. However, you can configure the RAID status settings only after configuring the SSH credentials for the Cisco Unified Communication Manager that you want to monitor. For more information about configuring SSH credentials, see Accessing the Cisco Unified Communications Manager with SSH.

To enable the monitoring of RAID status:

From the NNMi console, click the Cisco IP Telephony workspace in the left pane.
Click UCM Clusters. The UCM Clusters view opens.
Select the cluster for which you want to launch the Cisco Call Controller Details form, and then click . The UCM Cluster Details form opens.
On the right pane of the form click the UCMs tab. The UCMs view opens.
From the list of UCMs, select the Cisco Unified Communications Manager for which you want to enable the monitoring of the RAID status, and then click . The Cisco Call Controller Details form opens.
Click Actions > IP Telephony > Monitoring Configuration. The Monitoring Configuration for UCM page opens.
On the left pane of the Monitoring Configuration for UCM Cluster page, select RAID Status from the Area of Monitoring drop-down list.
From the right pane of the page, click (the New icon) to add the Measurement Type. For more information about adding a Measurement Type, see Configuring the RAID Status Settings.
Click (the Refresh icon) to view the newly-added measurement type. To add more measurement types to the RAID Status setting, go to Step 8.
On the left pane of the page, select minutes (mins) or hours (hrs) from the Collection Interval drop-down list and specify the value in the respective box. The NNM iSPI for IP Telephony uses this value to periodically monitor the RAID Status for the UCM Cluster. The default value is five minutes. You can select only a value that is greater than the default value.
Click (the Save icon ) to save the monitoring configuration.

To modify an existing RAID Status configuration setting:

Select the RAID Status configuration that you want to modify, and then click Edit. The Add/Update RAID Status page opens.
Make the required changes and click (the Save icon) to save the modified configuration settings.

To delete an existing RAID Status configuration setting:

Select the RAID Status configuration that you want to delete, and then click Delete. You can click Delete All to delete all the existing RAID Status configuration settings.

To disable an existing RAID Status configuration setting:

Select the RAID Status configuration that you want to disable, and then click Disable All.

Configure the RAID Status Settings

The Add/Update RAID Status page enables you to define the attributes for configuring RAID Status.

To configure RAID Status settings:

On the Add/Update RAID Status page, specify the required details in the fields provided on the page. The following table describes the fields on the page:

Field Name	Description
Measurement Type	Indicates the RAID Status type that is to be monitored. You can select one of the following types of measurement: Critical Disks Disks Failed Disks Media Error Count Other Error Count Physical Devices The Measurement Type list also provides the All option that enables you to select the Enable Collection and Enable Reporting check boxes to enable collection and reporting respectively, for all the available measurement types for this category. However, you must not configure any thresholds if you have selected All, as the threshold value for measurement types vary. You must always set the threshold values separately for each measurement type. You cannot configure values for the threshold violation of the Disks and Physical Devices measurement types.
Enable Collection	Select the check box to enable collection of the selected Measurement Type.
Enable Reporting	Select the check box to enable reporting for the selected Measurement Type.
Generate Incident	Select the check box to generate incident in the incident inventory.
Threshold Severity	Indicates the severity of the incident that is generated during a threshold violation. You can select one of the following types: Critical: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachCrirtical) incident. Major: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachMajor) incident. Minor: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachMinor) incident. Warning: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachWarning) incident. The NNM iSPI for IP Telephony generates the MonitoredAttributeThresholdBreachClear incident after you resolve the cause for the generation of any of the four incidents.
Lower Base	Specify the lower base value for the RAID status type threshold.
% Lower Deviation	Specify the acceptable percentage of deviation from the lower base threshold value before generating an incident.
Abs Lower Deviation	Specify the acceptable absolute value of deviation for the lower base threshold value before generating the incident.
Lower Trigger Count	Specify the number of times the threshold deviation should be permitted for the lower base before generating the incident. Specifying the trigger count is mandatory for generating incidents.
Higher Base	Specify the higher base value for the RAID status type threshold.
% Higher Deviation	Specify the acceptable percentage of deviation from the higher base threshold value before generating an incident.
Abs Higher Deviation	Specify the acceptable absolute value of deviation for the higher base threshold value before generating the incident.
Higher Trigger Count	Specify the number of times the threshold deviation should be permitted for the higher base before generating the incident. Specifying the trigger count is mandatory for generating incidents.

Click (the Save icon ) to save the configuration settings.

Monitor the Cisco TFTP Server

You can configure the NNM iSPI for IP Telephony to monitor the configuration file builds performed by the Cisco TFTP server for a UCM. You can monitor the following activities:

Configuration File Build Activity	Description
BuildAbortCount	Indicates the number of times the configuration file build process was aborted. The count increases when the build process for devices, soft keys, units, and dial rules get aborted due to group-level change notifications.
BuildCount	Indicates the number of times the TFTP server performed a new build of all the configuration files in response to a database change notification affecting all the devices. The count starts from the time the TFTP service started.
BuildDeviceCount	Indicates the number of devices that were processed during the last configuration build. This count increases when processing device change notifications. The count increases when new devices get added and reduces when existing devices are removed.
BuildDialRuleCount	Indicates the number of dial rules that were processed during the last configuration build. This count increases when processing dial rule change notifications. The count increases when new dial rules get added and reduces when existing dial rules are removed.
BuildSignCount	Indicates the number of security-enabled phones for which the configuration file was digitally signed with the Cisco UCM server key during the last configuration build. The count increases when processing security-enabled phone change notifications.
BuildSoftKeyCount	Indicates the number of soft keys that were processed during the last configuration build. The count increases when new soft keys get added and reduces when existing soft keys are removed.
BuildUnitCount	Indicates the number of gateways that were processed during the last configuration build. The count increases when processing gateway change notifications. The count increases when new gateways get added and reduces when existing gateways are removed.
ChangeNotifications	Indicates the total number of all the Cisco UCM database change notifications received by the TFTP server. This count increases every time a device configuration is updated using the Cisco UCM Administration interface. This update triggers a database change notification to the TFTP server to rebuild the configuration files.
DeviceChangeNotifications	Indicates the number of times the TFTP server received database change notifications to create, update, or delete configuration files for devices.
DialRuleChangeNotifications	Indicates the number of times the TFTP server received database change notifications to create, update, or delete configuration files for dial rules.
HTTPRequestsAborted	Indicates the total number of HTTP requests canceled by the HTTP server unexpectedly. An HTTP request cancellation occurs when the requested device cannot be located on the network or when the file transfer gets interrupted due to network connectivity issues.
HTTPRequestsProcessed	Indicates the total number of HTTP requests successfully processed by the HTTP server.
RequestsAborted	Indicates the total number of TFTP requests canceled by the TFTP server unexpectedly. A TFTP request cancellation occurs when the requested device cannot be located on the network or when the file transfer gets interrupted due to network connectivity issues.
RequestsProcessed	Indicates the total number of TFTP requests successfully processed by the TFTP server.

Enable the Monitoring of Cisco TFTP Server

The Monitoring Configuration for UCM page of the NNM iSPI for IP Telephony helps you to enable the monitoring of the TFTP server activity. The page displays the list of existing TFTP server activity configuration settings under the Cisco TFTP Server tab along with the attributes enabled and the thresholds set for each configured measurement. However, you can configure the TFTP Server activity settings only after configuring the SSH credentials for the Cisco Unified Communication Manager that you want to monitor. For more information about configuring SSH credentials, see Configuring SSH Access for a Cisco Unified Communications Manager Cluster.

You can launch the Monitoring Configuration for UCM page from the Cisco Call Controller Details form of a UCM.

To enable the monitoring of Cisco TFTP server:

From the NNMi console, click the Cisco IP Telephony workspace in the left pane.
Click UCM Clusters. The UCM Clusters view opens.
Select the cluster for which you want to launch the Cisco Call Controller Details form, and then click . The UCM Cluster Details form opens.
On the right pane of the form click the UCMs tab. The UCMs view opens.
From the list of UCMs, select the Cisco Unified Communications Manager for which you want to enable the TFTP server monitoring, and then click . The Cisco Call Controller Details form opens.
Click Actions > IP Telephony > Monitoring Configuration. The Monitoring Configuration for UCM page opens.

On the left pane of the Monitoring Configuration for UCM page, select Cisco TFTP Server from the Area of Monitoring drop-down list.
From the right pane of the page, click (the New icon) to add the Measurement Type. For more information about adding a Measurement Type, see Configuring the Cisco TFTP Server Settings.
Click (the Refresh icon) to view the newly-added measurement type. To add more measurement types to the TFTP Server setting, go to Step 8.
On the left pane of the page, select minutes (mins) or hours (hrs) from the Collection Interval drop-down list and specify the value in the respective box. The NNM iSPI for IP Telephony uses this value to monitor the configuration file build activities performed by the Cisco TFTP server periodically.
Click (the Save icon) to save the monitoring configuration.

To modify an existing TFTP Server configuration setting:

Select the TFTP Server activity configuration that you want to modify, and then click Edit. The Add/Update Cisco TFTP Server page opens.
Make the required changes and click (the Save icon) to save the modified configuration settings.

To delete an existing TFTP Server configuration setting:

Select the TFTP Server activity configuration that you want to delete, and then click Delete. You can click Delete All to delete all the existing TFTP Server activity configuration settings.

To disable an existing TFTP Server configuration setting:

Select the TFTP Server activity configuration that you want to disable, and then click Disable All.

Configure the Cisco TFTP Server Settings

The Add/Update Cisco TFTP Server page enables you to define the attributes for configuring the Cisco TFTP server settings such as specifying threshold settings to generate incidents based on the TFTP server activity, and enable monitoring and reporting for the TFTP server activity.

To configure the Cisco TFTP Server settings:

On the Add/Update Cisco TFTP Server page, specify the required details in the fields provided on the page. The following table describes the fields on the page:

Field Name	Description
Measurement Type	Indicates the TFTP Server type activity that is to be monitored. You can select one of the following types of measurement: RequestsProcessed BuildAbortCount BuildCount BuildDeviceCount BuildDialRuleCount BuildSignCount BuildSoftKeyCount BuildUnitCount ChangeNotifications DeviceChangeNotifications DialRuleChangeNotifications HTTPRequestsAborted HTTPRequestsProcessed RequestsAborted The Measurement Type list also provides the All option that enables you to select the Enable Collection and Enable Reporting check boxes to enable collection and reporting respectively, for all the available measurement types for this category. However, you must not configure any thresholds if you have selected All, as the threshold value for measurement types vary. You must always set the threshold values separately for each measurement type.
Enable Collection	Select the check box to enable collection of the selected Measurement Type.
Enable Reporting	Select the check box to enable reporting of the selected Measurement Type.
Generate Incident	Select the check box to generate incident in the incident inventory.
Threshold Severity	Indicates the severity of the incident that is generated during a threshold violation. You can select one of the following types: Critical: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachCrirtical) incident. Major: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachMajor) incident. Minor: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachMinor) incident. Warning: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachWarning) incident. The NNM iSPI for IP Telephony generates the MonitoredAttributeThresholdBreachClear incident after you resolve the cause for the generation of any of the four incidents.
Lower Base	Specify the lower base value for the selected TFTP Server threshold.
% Lower Deviation	Specify the acceptable percentage of deviation from the lower base threshold value before generating an incident.
Abs Lower Deviation	Specify the acceptable absolute value of deviation for the lower base threshold value before generating the incident.
Lower Trigger Count	Specify the number of times the threshold deviation should be permitted for the lower base before generating the incident. Specifying the trigger count is mandatory for generating incidents.
Higher Base	Specify the higher base value for the TFTP Server threshold.
% Higher Deviation	Specify the acceptable percentage of deviation from the higher base threshold value before generating an incident.
Abs Higher Deviation	Specify the acceptable absolute value of deviation for the higher base threshold value before generating the incident.
Higher Trigger Count	Specify the number of times the threshold deviation should be permitted for the higher base before generating the incident. Specifying the trigger count is mandatory for generating incidents.

Click (the Save icon) to save the TFTP Server activity configuration settings.

Monitor the Health of Cisco Unified Communications Managers

You can configure the NNM iSPI for IP Telephony to monitor the UCM parameters that indicate the health of the system. You can monitor the following activities:

System Health Parameter	Description
Active Partition Used	Indicates the total space in use by the active partition.
Common Partition Used	Indicates the total space in use by the common partition.
CPU Time	Indicates the CPU utilization of the Cisco Unified Communications Manager.
Memory Used	Indicates the memory utilization of the Cisco Unified Communications Manager.
Process: ccm - CPU Time	Indicates the CPU utilization of the `ccm` process.
Process: ccm - Memory Used	Indicates the memory utilization of the `ccm` process.
Swap Partition Used	Indicates the total space in use by the swap partition.
Swap Space Used	Indicates the total swap space used by the Cisco Unified Communications Manager.
System Reboot	Indicates whether there was a reboot during the last polling cycle.
System Uptime	Indicates the time elapsed since the last reboot.
Total Processes	Indicates the total number of processes on the Cisco Unified Communications Manager.
Total Threads	Indicates the total number of threads on the Cisco Unified Communications Manager.
VM Used	Indicates the total virtual memory in use.

Enable the Monitoring of System Health Parameters

The Monitoring Configuration for UCM page enables you to configure monitoring of system health parameters of Cisco Unified Communications Managers.

To enable the monitoring of system health parameters:

Log on to the NNMi console as an administrator.
Navigate to the Monitoring Configuration for UCM page.
1. From the NNMi workspace, click Cisco IP Telephony > UCM Clusters. The UCM Clusters view opens.
2. Select the cluster for which you want to launch the Cisco Call Controller Details form, and then click . The UCM Cluster Details form opens.
3. On the right pane of the form click the UCMs tab. The UCMs view opens.
4. From the list of UCMs, select the Cisco Unified Communications Manager for which you want to enable the system health parameter monitoring, and then click . The Cisco Call Controller Details form opens.
5. In the Cisco Call Controller Details form, click Actions > IP Telephony > Monitoring Configuration. The Monitoring Configuration for UCM page opens.
On the left pane of the Monitoring Configuration for UCM page, select System Health from the Area of Monitoring drop-down list.
From the right pane of the page, click (the New icon) to add the Measurement Type. For more information about adding a Measurement Type, see Configuring the System Health Parameter Settings.
Click (the Refresh icon) to view the newly-added measurement type. To add more measurement types to the System health Parameter setting, go to Step 4.
On the left pane of the page, select minutes (mins) or hours (hrs) from the Collection Interval drop-down list and specify the value in the respective box. The NNM iSPI for IP Telephony uses this value to monitor the system health parameters periodically.
Click (the Save icon) to save the monitoring configuration.

To modify an existing System Health parameter configuration setting:

Select the System Health parameter configuration that you want to modify, and then click Edit. The Add/Update System Health page opens.
Make the required changes and click (the Save icon) to save the modified configuration settings.

To delete an existing System Health parameter configuration setting:

Select the System Health parameter configuration that you want to delete, and then click Delete. You can click Delete All to delete all the existing System Health parameter configuration settings.

To disable an existing System Health parameter configuration setting:

Select the System Health parameter configuration that you want to disable, and then click Disable All.

Configure the System Health Parameter Settings

The Add/Update System Health page enables you to define the attributes for configuring the system health parameters such as specifying threshold settings to generate incidents, and enable monitoring and reporting for the system health.

To configure the system health parameters settings:

On the Add/Update System Health page, specify the required details in the fields provided on the page. The following table describes the fields on the page:

Field Name	Description
Measurement Type	Indicates the System Health parameter type that is to be monitored. You can select one of the following types of measurement: Active Partition Used Common Partition Used CPU Time Memory Used Process: ccm - CPU Time Process: ccm - Memory Used Swap Partition Used Swap Space Used System Reboot System Uptime Total Processes Total Threads VM Used The Measurement Type list also provides the All option that enables you to select the Enable Collection and Enable Reporting check boxes to enable collection and reporting respectively, for all the available measurement types for this category. However, you must not configure any thresholds if you have selected All, as the threshold value for measurement types vary. You must always set the threshold values separately for each measurement type.
Enable Collection	Select the check box to enable collection of the selected Measurement Type.
Enable Reporting	Select the check box to enable reporting of the selected Measurement Type.
Generate Incident	Select the check box to generate incident in the incident inventory.
Threshold Severity	Indicates the severity of the incident that is generated during a threshold violation. You can select one of the following types: Critical: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachCrirtical) incident. Major: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachMajor) incident. Minor: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachMinor) incident. Warning: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachWarning) incident. The NNM iSPI for IP Telephony generates the MonitoredAttributeThresholdBreachClear incident after you resolve the cause for the generation of any of the four incidents.
Lower Base	Specify the lower base value for the selected System Health parameter threshold.
% Lower Deviation	Specify the acceptable percentage of deviation from the lower base threshold value before generating an incident.
Abs Lower Deviation	Specify the acceptable absolute value of deviation for the lower base threshold value before generating the incident.
Lower Trigger Count	Specify the number of times the threshold deviation should be permitted for the lower base before generating the incident. Specifying the trigger count is mandatory for generating incidents.
Higher Base	Specify the higher base value for the System Health parameter threshold.
% Higher Deviation	Specify the acceptable percentage of deviation from the higher base threshold value before generating an incident.
Abs Higher Deviation	Specify the acceptable absolute value of deviation for the higher base threshold value before generating the incident.
Higher Trigger Count	Specify the number of times the threshold deviation should be permitted for the higher base before generating the incident. Specifying the trigger count is mandatory for generating incidents.

Click (the Save icon) to save the System Health parameter configuration settings.

Monitor the Availability of the Call Manager Administration Web Page

You can configure the NNM iSPI for IP Telephony to monitor the following activity:

CCMAdmin Web Page: Indicates the availability of the administration web page for a Cisco Unified Communications Manager

Enable the Monitoring of the Call Manager Administration Web Page State

The Monitoring Configuration for UCM page of the NNM iSPI for IP Telephony helps you to enable the monitoring of the availability of the administration web page for a CUCM. The page displays the list of existing administration web page state configuration settings under the Availability tab along with the attributes enabled and the thresholds set for each configured measurement.

To enable the monitoring of the administration web page state for a CUCM:

From the NNMi console, click the Cisco IP Telephony workspace in the left pane.
Click UCM Clusters. The UCM Clusters view opens.
Select the cluster for which you want to launch the Cisco Call Controller Details form, and then click . The UCM Cluster Details form opens.
On the right pane of the form click the UCMs tab. The UCMs view opens.
From the list of UCMs, select the Cisco Unified Communications Manager for which you want to enable the monitoring of the administration web page state for the CUCM, and then click . The Cisco Call Controller Details form opens.
Click Actions > IP Telephony > Monitoring Configuration. The Monitoring Configuration for UCM page opens.

On the left pane of the Monitoring Configuration for UCM page, select Availability from the Area of Monitoring drop-down list.
From the right pane of the page, click (the New icon) to add the Measurement Type. For more information about adding a Measurement Type, see Configuring the Call Manager Administration Web Page State Settings.
Click (the Refresh icon) to view the newly-added measurement type.
On the left pane of the page, select minutes (mins) or hours (hrs) from the Collection Interval drop-down list and specify the value in the respective box. The NNM iSPI for IP Telephony uses this value to monitor the availability of the administration web page for the CUCM periodically.
Click (the Save icon) to save the monitoring configuration.

To modify an existing call manager administration web page state configuration setting:

Select the call manager administration web page state configuration that you want to modify, and then click Edit. The Add/Update Availability page opens.
Make the required changes and click (the Save icon) to save the modified configuration settings.

To delete an existing call manager administration web page state configuration setting:

Select the call manager administration web page state configuration that you want to delete, and then click Delete. You can click Delete All to delete all the existing call manager administration web page state configuration settings.

To disable an existing call manager administration web page state configuration setting:

Select the call manager administration web page state configuration that you want to disable, and then click Disable All.

Configure the Call Manager Administration Web Page State Settings

The Add/Update Availability page enables you to define the attributes for the availability of the administration web page for a CUCM, such as specifying threshold settings to generate incidents, and enable monitoring for the availability.

To configure the availability of the administration web page for a CUCM settings:

On the Add/Update Availability page, specify the required details in the fields provided on the page. The following table describes the fields on the page:

Field Name	Description
Measurement Type	Indicates the Availability type that is to be monitored. The following measurement type is available: CCMAdmin Web Page
Enable Collection	Select the check box to enable collection of the availability of administration web page for the call manager.
Generate Incident	Select the check box to generate incident in the incident inventory.
Threshold Severity	Indicates the severity of the incident that is generated during a threshold violation. You can select one of the following types: Critical: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachCrirtical) incident. Major: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachMajor) incident. Minor: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachMinor) incident. Warning: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachWarning) incident. The NNM iSPI for IP Telephony generates the MonitoredAttributeThresholdBreachClear incident after you resolve the cause for the generation of any of the four incidents.
Threshold State	Select one of the following options to specify the threshold state: Available: Indicates the administration web page for the call manager is available. Not Available: Indicates the administration web page for the call manager is not available.

Click (the Save icon) to save the call manager administration web page state configuration settings.

Monitor the Availability of Services on the UCM

You can configure the NNM iSPI for IP Telephony to monitor the availability of the services on a UCM. You can configure the NNM iSPI for IP Telephony to generate incidents based on the state of the services. You can configure the NNM iSPI for IP Telephony to generate incidents if the state of the service changes from Started to Stopped, or Deactivated or in the reverse scenarios.

The NNM iSPI for IP Telephony allows you to monitor the availability of the services currently on the discovered UCM.

Enable the Monitoring of the Availability of Services on the UCM

The Monitoring Configuration for UCM page of the NNM iSPI for IP Telephony helps you to enable the monitoring of the state of the services on a UCM. The page displays the list of existing configuration settings under the Services tab along with the attributes enabled and the thresholds set for each configured measurement. However, you can configure the state of available services settings only after configuring the SSH credentials for the Cisco Unified Communication Manager that you want to monitor. For more information about configuring SSH credentials, see Configuring SSH Access for a Cisco Unified Communications Manager Cluster.

Note: After configuring the SSH credentials, you must perform a discovery on the CUCM node for all the measurements to be displayed in the Measurement Type list.

To enable the monitoring of the availability of the services:

From the NNMi console, click the Cisco IP Telephony workspace in the left pane.
Click UCM Clusters. The UCM Clusters view opens.
Select the cluster for which you want to launch the Cisco Call Controller Details form, and then click . The UCM Cluster Details form opens.
On the right pane of the form click the UCMs tab. The UCMs view opens.
From the list of UCMs, select the Cisco Unified Communications Manager for which you want to enable the monitoring of the availability of services, and then click . The Cisco Call Controller Details form opens.
Click Actions > IP Telephony > Monitoring Configuration. The Monitoring Configuration for UCM page opens.

On the left pane of the Monitoring Configuration for UCM page, select Services from the Area of Monitoring drop-down list.
From the right pane of the page, click (the New icon) to add the Measurement Type. For more information about adding a Measurement Type, see Configuring the Availability of Services on the UCM Settings.
Click (the Refresh icon) to view the newly-added measurement type.
On the left pane of the page, select minutes (mins) or hours (hrs) from the Collection Interval drop-down list and specify the value in the respective box. The NNM iSPI for IP Telephony uses this value to monitor the state of the services on a UCM periodically.
Click (the Save icon) to save the monitoring configuration.

To modify an existing availability of Services setting:

Select the Service Availability configuration that you want to modify, and then click Edit. The Add/Update UCOS Service Availability page opens.
Make the required changes and click (the Save icon) to save the modified configuration settings.

To delete an existing availability of Services setting:

Select the Service Availability configuration that you want to delete, and then click Delete. You can click Delete All to delete all the existing Service Availability configuration settings.

To disable an existing availability of Services setting:

Select the Service Availability configuration that you want to disable, and then click Disable All.

Configure the Availability of Services on the UCM Settings

The Add/Update UCOS Service Availability page enables you to define the attributes to monitor the service availability settings such as specifying threshold settings to generate incidents, enabling monitoring for service state changes, and enabling reporting for service availability and service state changes.

To configure the service availability settings:

On the Add/Update UCOS Service Availability page, specify the required details in the fields provided on the page. The following table describes the fields on the page:

Field Name	Description
Measurement Type	Indicates the Services that are to be monitored.
Enable Collection	Select the check box to enable collection of the services.
Generate Incident	Select the check box to generate incident in the incident inventory.
State	Select one of the following options to specify the state: Started Stopped De-Activated
Threshold Severity	Indicates the severity of the incident that is generated during a threshold violation. You can select one of the following types: Critical: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachCrirtical) incident. Major: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachMajor) incident. Minor: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachMinor) incident. Warning: The NNM iSPI for IP Telephony generates a (MonitoredAttributeThresholdBreachWarning) incident. The NNM iSPI for IP Telephony generates the MonitoredAttributeThresholdBreachClear incident after you resolve the cause for the generation of any of the four incidents.

Click (the Save icon) to save the service availability configuration settings.

Send Help Center feedback