Administer > Administer the NNM iSPI for IP Telephony > Cisco IP Telephony

Cisco IP Telephony

As an administrator, you can configure the attributes for monitoring the Cisco IP telephony infrastructure discovered on the network.

This topic includes the following sections:

To access the administration console for Cisco IP telephony:

  1. Log on to the NNMi console as an administrator.
  2. From the Workspaces navigation pane, click Configuration > iSPI for IP Telephony Configuration > Cisco Configuration. The administration console for Cisco IP telephony appears.

The console displays configuration options for the following attributes:

Attribute Description
Call Monitoring

Allows you to configure the call monitoring options of Cisco IP Telephony devices.

You can also use this option to view the existing call monitoring configurations.
Data Access

Allows you to configure the NNM iSPI for IP Telephony to access the various categories of management data from the Cisco IP Telephony servers in your deployment environment.

You can also use this option to view the existing data access configurations.
Discovery

Allows you to configure the discovery settings for the Cisco H.323 gateways that are configured to a cluster using the H.323 short hostname or the Fully Qualified Domain Name (FQDN).

You can also use this option to view the existing discovery configurations.
IP Phone

Allows you to configure tasks such as specifying the range of IP phones to be excluded from monitoring and enable the custom attributes for the Cisco IP Phones.

You can also use this option to view the existing configurations.
Polling

Allows you to configure the polling options of Cisco IP Telephony device states and statistics.

You can also use this option to view the existing polling configurations.
Reporting

Allows you to configure the CDR reporting of Cisco IP Telephony networks.

You can also use this option to view the existing reporting configurations.

Configure the Call Monitoring

You can use the NNMi Cisco Call Monitoring Configuration form to configure:

  • Monitor the voice QOS metrics and MOS values for calls in the Cisco IP Telephony network
  • The termination cause codes that need to be monitored for a specific call in the Cisco IP Telephony network

Configure the Cisco QOS and MOS Monitoring Threshold Values

The Call Monitoring Configuration link on the Cisco Configuration pane enables you to specify the threshold values for the NNMi to use while monitoring the voice QOS metrics and MOS values for calls in the Cisco IP Telephony network. On a violation of set threshold for any of these parameters for any monitored call, the NNMi generates an incident conveying the resulting values and the set threshold.

To configure the QOS and MOS monitoring threshold values for Cisco IP telephony devices:

  1. On the NNMi Cisco Configuration console, click Call Monitoring Configuration. The NNMi Cisco Call Monitoring Configuration form opens.
  2. Click the Thresholds for QOS/MOS Monitoring tab. The Thresholds for QOS/MOS Monitoring tab page opens.

  3. Specify the required details in the fields provided under the Thresholds for QOS/MOS Monitoring section of the page. By default, no threshold values are set for these parameters and threshold-based monitoring is disabled. The monitoring is enabled when you specify valid threshold values here.

    The following table describes the fields that appear under the section:

    QOS/MOS Monitoring Parameter Description
    1Jitter Specify the jitter threshold to be configured in milliseconds.
    1PPL Specify the Percentage Packet Loss (PPL) threshold to be configured. For example, to specify a percentage packet loss threshold of 50%, type 50 here.
    1Latency Specify the latency threshold to be configured in milliseconds.
    2Avg MOS Specify the average Mean Opinion Source (MOS) value to be configured. This value must be within the range of 0.0 to 5.0.
    2Min MOS Specify the minimum MOS value to be configured. This value must be within the range of 0.0 to 5.0.

    1To disable the monitoring, specify -1.

    2To disable the monitoring, specify 0.0.

  4. Click Apply Changes. The NNMi updates the QOS/MOS monitoring configuration values.

Configure Cluster-specific QOS and MOS Monitoring Threshold Values

The Add Cluster Specific QOS Configuration section on the Thresholds for QOS/MOS Monitoring tab page enables you to configure QOS and MOS monitoring threshold values for a specific clusters of your choice. After you specify threshold values specific to a cluster, the NNMi lists these threshold values in the Current Configuration section and uses them for the cluster, instead of the threshold values specified in the Thresholds for QOS/MOS Monitoring section.

To configure cluster-specific QOS and MOS monitoring threshold values:

  1. On the Thresholds for QOS/MOS Monitoring tab page, go to Cluster Specific Thresholds for QOS/MOS Monitoring pane > Add Cluster Specific QOS Configuration section.

  2. Under the Add Cluster Specific QOS Configuration section, specify the required details in the fields provided. The following table describes the fields under the section:

    Field NameDescription
    TenantSelect the name of the tenant from the drop-down list.
    Cluster IDSelect the required cluster for which you want to configure the threshold values.
    JitterSpecify the jitter threshold ( in milliseconds) to be configured for the cluster.
    PPLSpecify the Percentage Packet Loss (PPL) threshold to be configured for the cluster. For example, to specify a percentage packet loss threshold of 50%, type 50 here.
    LatencySpecify the latency threshold to be configured for the cluster.
    Avg MOSSpecify the average Mean Opinion Source (MOS) value to be configured for the cluster. This value must be within the range of 0.0 to 5.0.
    Min MOSSpecify the minimum MOS value to be configured for the cluster. This value must be within the range of 0.0 to 5.0.

    For more information about the QOS and MOS monitoring parameters, see Configuring the QOS and MOS Monitoring Threshold Values for Cisco.

  3. Click Add/Modify. This adds the configuration for the cluster in the Current Configurations section.

To modify cluster-specific QOS and MOS monitoring threshold values:

  1. From the Current Configurations section, select the cluster-specific configuration that you want to modify .
  2. Click Modify. This displays the current threshold values for the cluster in the Add Cluster Specific QOS Configuration section.
  3. Specify the new values.
  4. Click Add/Modify. This updates the cluster-specific configuration with the new values.

To delete cluster-specific QOS and MOS monitoring threshold values:

  1. From the Current Configurations section, select the cluster-specific configuration that you want to delete.
  2. Click Delete. This deletes the cluster-specific threshold values for the cluster. After removing the cluster-specific threshold value configuration, the NNMi uses the values you provided in the Thresholds for QOS/MOS Monitoring section.

To export configurations to the Global Manager:

  • Click Export Config to Global Manager. This sends all the available configuration information listed in the Current Configurations section, irrespective of the check boxes selected, to the Global Manager.

Configure Call Termination Cause Codes to be Monitored

You can configure the NNMi to monitor only specific call termination cause codes. You can specify the following types of call termination cause codes:

  • Call failure cause codes as defined by the International Telecommunication Union (ITU) Q.850: This listing lists the call termination cause codes if a call failure was the reason for the call termination.
  • Non failure cause codes as defined by ITU Q.850: This listing lists the call termination cause codes if the call termination occurred normally without a call failure.
  • Cisco-specific cause codes: This listing lists call termination cause codes specific to Cisco.

After you specify the codes that you want to be monitored, the NNMi generates the CallTerminationReason incident only when the call termination occurs due to any of the call termination cause codes that you specified.

To configure monitoring of call termination cause codes:

  1. On the NNMi Cisco Configuration console, click Call Monitoring Configuration. The NNMi Cisco Call Monitoring Configuration form opens.
  2. Click the Call Termination Cause Monitoring tab.

  3. You can select the call termination cause codes that you want to monitor from the following sections and click (Move Items to Selected List) to specify the cause codes that you want the NNMi to monitor:

    • Failure Cause Codes (Q.850)
    • Non Failure Cause Codes (Q.850)
    • Cause Codes (Cisco Specific)
    • To select multiple random cause codes, you can press the Ctrl (Control) key and select the required codes
    • To select a series of cause codes, you can press the Shift key and the select the series of cause codes.
    • To move a selected cause code from the monitored cause code list back to the cause code selection list, select the cause code and click (Move Items to Non Selected List).

    The default version of the property file—CiscoCDRTerminationCauseCodes.properties—is available in the following directory:

    • %NNMDataDir%\\shared\\ipt\\conf\cisco

    The property file can be used to add new termination cause codes that are not listed in the types of call termination cause codes section. After you add a new termination cause code, make sure to restart the IPT jboss application server to reflect the change.

  4. Click Apply Changes to complete the configuration.

Configure Data Access

You can use the Data Access Configuration form to configure the NNMi to access the following types of data from the Cisco Unified Communications Manager clusters in your deployment environment:
  • AVVID XML Layer (AXL) API exposed data
  • Call Details Record (CDR) data
  • Secure Shell (SSH) data

You can use the AXL and CDR related forms to add a configuration for a cluster, modify the configuration for an existing cluster, or delete an existing configuration for a cluster. You can use the SSH related form for UCM specific configurations.

Access the AXL Data

Configuring the data access for Cisco with AXL enables the NNMi to provide the following features:

  • Discover whether or not theUCM node is a Publisher.
    If the role of the UCM is that of a Publisher, the NNMi discovers and monitors the device pools and the devices associated with each device pool.
  • Discover the Publisher UCM for which the CallManager service is deactivated or stopped.
    If the CallManager service for a Publisher UCM is deactivated or stopped, the NNMi discovers the UCMs, CM groups, and the UCMs associated with each CM group.
  • Provide the Registered Device count of the number of registered IP phones for each of the device pools.
  • Monitor the count of registered CTI and VM devices for each device pool.
  • Discover the device pools associated with IP phones, H.323 gateways, MGCP gateways, IC trunks, and Media Devices.
  • Provide the accurate number of the H.323 Gateway Boxes count of the Registered Devices.
  • Monitor the Route List and Hunt List configurations.
  • Provide the Route List and Route Group usage reports.
  • Provide the P.01 GoS Summary for Route Groups report and the P.01 GoS Summary for Route Lists report.
  • Discover the Cisco SRST routers.
  • Discover the device pool associated with an SRST router.
  • Discover the Locations of a Cisco Unified Communications Manager cluster.
  • Map the Call Manager ID from CDR records to the actual CM IP Address or hostname while processing the CDR records.
  • Provide the Cisco IP Telephony CDR reports.
    If you do not configure the data access for Cisco with AXL, the Cisco IP Telephony CDR reports show 'NO DATA' for the Call Manager Name and Call Manager IP Address fields.

To configure the AXL data access for Cisco:

  1. On the NNMi Cisco configuration console, click Data Access Configuration. The NNMi Cisco Data Access Configuration form opens.
  2. Click the AXL Access tab.
  3. In the Add/Modify AXL Access Configuration for a Cluster section, specify the required details in the fields provided on the page. The following table describes the fields on the page:
    Field NameDescription
    Tenant

    Select the name of the tenant from the drop-down list.

    Cluster ID

    Indicates the cluster identifier. You can retrieve this information from the administration web page of the Cisco Unified Communications Manager.

    CM IP AddressIndicates the management IP address (public address) of the publisher Cisco Unified Communications Manager in this cluster. The NNMi uses this IP address to obtain the AXL data for this cluster.
    AXL User NameIndicates the AXL user name to be used for invoking the AXL Web Services.
    AXL Password

    Indicates the port number on the primary Communication Manager server to which SSH connections can be established from the NNMi server.

  4. Click Add/Modify to complete the configuration. The Current Configurations section lists all the clusters configured for AXL access.

To modify an AXL access configuration for Cisco:

  1. On the NNMi Data Access Configuration form of Cisco Configuration, from the Current Configurations section of the AXL Access tab, select the configuration that you want to modify.
  2. Click Modify.

  3. In the Add/Modify AXL Access Configuration for a Cluster section, make the required changes.

      You cannot modify the name of the tenant and the cluster ID. If you want to modify the name of the tenant and the cluster ID, you must delete the configuration and create a new configuration with the required changes.
  4. Click Add/Modify. The modified configuration is listed in the Current Configurations section.

To delete an AXL access configuration for Cisco:

  1. On the NNMi Data Access Configuration form of Cisco Configuration, from the Current Configurations section of the AXL Access tab, select the configuration that you want to delete.
  2. Click Delete. The selected configuration is deleted from the Current Configurations section.

Access the CDR Data

You can use the NNMi Data Access Configuration form to configure the CDR data access for Cisco. The NNMi enables you to collect the CDR data in one of the following modes:

  • CDRonDemand Web Service mode
  • Billing server mode

Configuring the data access for Cisco with CDR enables the NNMi to provide the following reports:

  • Cisco IP Telephony CDR reports
  • Cisco IP Telephony Gateway Call reports
  • Cisco IP Telephony Trunk Calls reports
  • Cisco IP Telephony Call Types and Call Termination Reasons reports

Prerequisites

To access the CDR data for Cisco, you must configure an FTP server on the NNMi management server (where the NNMi is installed).

To configure the FTP server on a standalone NNMi management server (a server that is not installed in an HA cluster):

  1. Set up an FTP server on the NNMi management server.

  2. Create a user on the NNMi management server with the read/write access to the following location:

    • Windows:%NnmDataDir%\shared\ipt\IPTCiscoCDRCollection
    • Linux:var/opt/OV/shared/ipt/IPTCiscoCDRCollection

  3. Set up the home directory for the FTP server.

    • For Windows: Configure the %NnmDataDir%\shared\ipt\IPTCiscoCDRCollection directory as the home directory of the FTP server.
    • For Linux: Make sure that the / (root) directory is configured as the home directory of the FTP server.
  4. Perform this step only if you want to use SFTP for downloading CDR files from the Cisco Unified Communications Manager server through CDRonDemand Web Service. Establish a trust relationship for Secure File Transfer Protocol (SFTP) from the Cisco Unified Communications Manager server (CDR Repository Server) to NNMi server.

To configure the FTP server on the NNMi management server in an HA cluster:

  1. Set up an FTP server on each NNMi management server in the HA cluster.

  2. Create a user on the NNMi management server with the read/write access to the following location:

    For the NNMi installed on Windows, the shared drive must be online when you create this new user.

    • Windows:<Shared_Drive>\NNM\dataDir\shared\ipt\IPTCiscoCDRCollection
    • Linux: /nnm_mount_point/NNM/dataDir/shared/ipt/IPTCiscoCDRCollection

    In this instance, <Shared_Drive> is the drive that is shared among the systems in the HA cluster.

    If required, create the IPTCiscoCDRCollection directory manually.

  3. Set up the home directory for the FTP server.

    • For Windows: Configure the <Shared_Drive>\NNM\dataDir\shared\ipt\IPTCiscoCDRCollection directory as the home directory of the FTP server.
    • For Linux: Make sure that the / (root) directory is configured as the home directory of the FTP server.
  4. Establish a trust relationship for Secure File Transfer Protocol (SFTP) from the Cisco Unified Communications Manager server (CDR Repository Server) to NNMi server. Perform this step only if you want to use SFTP for downloading CDR files from the Cisco Unified Communications Manager server through CDRonDemand Web Service.

Additional prerequisites to use the billing server mode

You can configure the NNMi management server as a billing server and export the CDR data from the repository server to the NNMi management server. For this purpose, you must perform the following tasks:

  1. Create a directory on the NNMi management server to place all the CDR data. You must create this directory under the following directory:

    • For a standalone NNMi management server (a server that is not installed in an HA cluster):

      • For Windows: %NnmDataDir%\shared\ipt\IPTCiscoCDRCollection
      • For Linux:/var/opt/OV/shared/ipt/IPTCiscoCDRCollection

    • For an NNMi management server in an HA cluster:

      • For Windows: Configure the <Shared_Drive>\NNM\dataDir\shared\ipt\IPTCiscoCDRCollection
      • For Linux: /nnm_mount_point/NNM/dataDir/shared/ipt/IPTCiscoCDRCollection
  2. Configure the Cisco Unified Communications Manager to export CDR files into the newly created directory on the NNMi management server. This configuration task is performed in the Cisco Unified Serviceability console by specifying the Billing Application Server parameters.
  3. In the list of parameters, specify the FTP user credentials created.

  4. For Directory Path, specify the complete path of the newly created directory if NNMi is installed on a Linux server (/var/opt/OV/shared/ipt/IPTCiscoCDRCollection/); specify only the name of the newly created directory if NNMi is installed on a Windows server (/IPTCiscoCDRCollection/).

You must configure an FTP or SFTP server on the NNMi management server (where you installed the NNMi).

For a standalone NNMi management server (a server that is not installed in an HA cluster), do the following:

  1. Set up an FTP or SFTP server on the NNMi management server.

  2. Create a user on the NNMi management server with the read/write access to the following location:

    • Windows:%NnmDataDir%\shared\ipt\IPTCiscoCDRCollection
    • Linux: /var/opt/OV/shared/ipt/IPTCiscoCDRCollection

  3. Set up the home directory for the FTP or SFTP server.

    • For Windows:Configure the %NnmDataDir%\shared\ipt\IPTCiscoCDRCollection directory as the home directory of the FTP or SFTP server.
    • For Linux: Make sure that the / (root) directory is configured as the home directory of the FTP or SFTP server

For an NNMi management server in an HA cluster, do the following:

  1. Set up an FTP or SFTP server on each NNMi management server in the HA cluster.

  2. Create a user on the NNMi management server with the read/write access to the following location:

    For the NNMi installed on Windows, the shared drive must be online when you create this new user.

    • Windows:<Shared_Drive>\NNM\dataDir\shared\ipt\IPTCiscoCDRCollection
    • Linux: /nnm_mount_point/NNM/dataDir/shared/ipt/IPTCiscoCDRCollection

    In this instance, <Shared_Drive> is the drive that is shared among the systems in the HA cluster.

    If required, create the IPTCiscoCDRCollection directory manually.

  3. Set up the home directory for the FTP or SFTP server.

    • For Windows:Configure the <Shared_Drive>\NNM\dataDir\shared\ipt\IPTCiscoCDRCollection directory as the home directory of the FTP or SFTP server.
    • For Linux: Make sure that the / (root) directory is configured as the home directory of the FTP or SFTP server.

To configure CDR access for Cisco:

  1. On the NNMi Cisco Configuration console, click Data Access Configuration. The NNMi Cisco Data Access Configuration form opens.
  2. Click the CDR Access tab.
  3. In the Add/Modify Configuration for Accessing CDR from Cisco Unified Communications Manager Clusters section, specify the required details in the fields provided on the page. The following table describes the fields on the page:
    Field NameDescription
    Tenant

    Indicates the name of the tenant. You can select the name of the tenant from the drop-down list.

    Cluster ID

    Indicates the cluster identifier. You can retrieve this information from the administration web page of the Cisco Unified Communications Manager.

    CDR Polling IntervalIndicates the interval at which the NNMi polls for new CDR files from the configured FTP path or invokes the CDRonDemand Web Service to collect the CDR files. For best results, set this interval in the range of 2 minutes to 60 minutes.
    Is CDR onDemand WS Based Collection?

    Indicates if the CDRonDemand Web Service is used to collect the CDR files or not.

    Select True if you want the NNMi to use the CDRonDemand Web Service to collect the CDR files.

    If you select True, specify the following details:

    • Server IP: The IP address of the Cisco CDR Repository server. If the server uses overlapping private and public IP addresses in a NAT environment, you must specify the public IP address only.
    • SOAP User Name: Simple Object Access Protocol (SOAP) user name of the CDRonDemand WebService.
    • SOAP Password: Password for the SOAP user name.
    • Port: CDR on demand web service port

    If you select False, specify the complete path to the newly created directory in the CDR Files Download Path box. Cisco Unified Communications Manager considers the NNMi management server as a billing server and exports the CDR data to the path specified in the CDR Files Download Path box.

    In an Application Failover environment, recommends that you select the CDRonDemand Web Service mode of data transfer. Otherwise, you must configure two different NNMi servers as billing servers in the Cisco Unified Serviceability console.

    While specifying the CDR Files Download Path, make sure that you do not include the folder (directory) separators (\) backslash for Windows platforms or (/) forward slash for non Windows platforms at the beginning of the path. For example, you can specify the path as follows if you want the CDR files to be downloaded to \CDRFiles\CCMFiles: CDRFiles\CCMFiles.

  4. Click Add/Modify. The Current Configurations section lists the details of the Cisco Unified Communications Manager configured for CDR access.

To configure SFTP or FTP credentials to be used by CDRonDemand Web Service to send the CDR files to the NNMi:

  1. On the NNMi Cisco Data Access Configuration form, click the CDR Access tab.
  2. In the (S)FTP Server Information to be used by iSPI for IP Telephony section, of the specify the required details in the fields provided on the page. The following table describes the fields on the page:
    Field NameDescription
    Is it a Secure FTP (SFTP) ?

    Select True if you want to provide an SFTP user name and password. Select False if you want to provide an FTP user name and password.

    User Name

    Indicates a valid SFTP or FTP user name with write privileges on the NNMi server.

    PasswordIndicates the password for the SFTP or FTP user name.
    Use (S)FTP server FQDN instead of IP Address?

    Select True if you want the CDR Repository servers to use the FQDN of NNMi to send the CDR files through FTP or SFTP. Select False if you want the CDR Repository servers to use the IP address of NNMi to send the CDR files.

    Select False only if the CDR Repository servers in the Cisco Unified Communications Manager clusters are not able to reach the NNMi, using the FQDN of NNMi server.

    If you select False, provide the following details:

    • Server FQDN: The fully qualified domain name of NNMi.
    • Server IP Address: One of the IP addresses of the NNMi server. Make sure that this IP address is reachable from the CDR repository nodes in the Cisco Unified Communications Manager clusters.
    • Application Failover?: Select True if you have Application Failover setup in your environment or else select False.

      • If you select True, provide the following details:

      • Second Server FQDN: FQDN of the second NNMi server in Application Failover setup.
      • Second Server IP Address: One of the IP addresses of the second NNMi server. Make sure that this IP address is reachable from CDR repository servers in Cisco Unified Communications Manager clusters.
  3. Click Apply Changes. This procedure restarts the NNMi task that monitors the QOS/MOS for IP Telephony calls. The Current Configurations section lists the configured cluster details from which the NNMi accesses the CDR data.

The NNMi uses the following directory as the (S)FTP home directory for CDR onDemand Web Service for CDR files collection:

  • Windows:<Shared_Drive>\NNM\dataDir\shared\ipt\ IPTCiscoCDRCollection
  • UNIX/Linux: /nnm_mount_point/NNM/dataDir/shared/ipt/IPTCiscoCDRCollection

To modify the configuration for the CDRonDemand Web Service access for a Cisco Unified Communications Manager Cluster:

  1. On the NNMi Data Access Configuration form, from the Current Configurations section of the CDR Access tab, select the configuration that you want to modify.
  2. Click Modify.

  3. In the Add/Modify Configuration for Accessing CDR from Cisco Unified Communications Manager Clusters section, make the required changes. You cannot modify the name of the tenant and the cluster ID. If you want to modify the name of the tenant and the cluster ID, you must delete the configuration and create a new configuration with the required changes.

  4. Click Add/Modify. This procedure restarts the NNMi task that monitors the QOS/MOS for IP Telephony calls. The Current Configurations section lists the modified configurations.

To delete the configuration for the CDRonDemand Web Service access for a Cisco Unified Communications Manager Cluster:

  1. On the NNMi Data Access Configuration form, from the Current Configurations section of the CDR Access tab, select the configuration that you want to delete.
  2. Click Delete. This procedure restarts the NNMi task that monitors the QOS/MOS for IP Telephony calls. The selected configuration is deleted from the Current Configurations section.

Access the Cisco Unified Communications Manager with SSH

You must configure the required Secure Shell (SSH) access details using the Data Access Configuration form of Cisco Configuration provided by the NNMi. You must configure these details for all the call manager servers in your deployment environment. When a managed call manager is not configured for SSH data access, it is excluded from the aggregate value that is displayed on the Analysis Pane.

Configuring the data access for Cisco with SSH enables the NNMi to monitor the following features:

  • UCM Call Activity
  • Gateway Call Activity
  • Media Resource Activity
  • Locations
  • Cisco TFTP Server
  • System Health
  • Services

To configure SSH access for a Cisco Unified Communications Manager cluster:

You must complete this task as a prerequisite to start monitoring call attempts handled by a cluster or a call manager. This helps in collecting the required details from the call manager using SSH.

  1. On the
    NNMi Cisco configuration console, click Data Access Configuration. The NNMi Cisco Data Access Configuration form opens.
  2. Click the SSH tab.
  3. On the SSH Access tab page, under the Add/Modify SSH Configuration section, specify the required details in the fields provided on the page. The following table describes the fields on the page:
    Field NameDescription
    CM IP Address

    Indicates the IP address of the call manager for which you want to configure SSH access.

    If your network supports Network Address Translation (NAT) or Port Address Translation (PAT), you must specify the external IP address (public address) here.

    SSH Type

    Indicates the type of SSH application to be used to collect the call details. The NNMi uses the CISCO_UCM_UCOS_DEFAULT application by default.

    User NameIndicates the user name to be used to establish an SSH connection.
    PasswordIndicates the password to be used for the user name.
    SSH Port

    Indicates the port number to be used for the SSH connection.

    SSH TimeoutIndicates the number of seconds to wait while attempting to execute a command before canceling the attempt.
    Host Key

    Indicates the SSH host key for the Cisco Unified Communications Manager.

  4. Click Add/Modify to complete the configuration. The NNMi lists the added configuration in the Current Configuration section.

To modify an existing SSH configuration for Cisco:

  1. Select an existing SSH configuration from the Current Configurations section.
  2. Click Modify.
  3. In the Add/modify SSH Configuration section, make the required changes.You cannot modify the CM IP Address and the SSH Port values.
  4. Click Add/Modify to complete the configuration. The NNMi lists the modified configuration in the Current Configurations section.

To delete an existing configuration for Cisco:

  1. Select an SSH Configuration from the Current Configurations section.
  2. Click Delete. The selected configuration is deleted from the Current Configurations section.

Configure Discovery Settings for Cisco H.323 Gateways

You can use the NNM iSPI for IP Telephony Cisco Discovery Configuration form to configure the discovery settings for the Cisco H.323 gateways that are configured to a cluster using the H.323 short hostname or the FQDN. The configuration settings ensure that a short hostname or an FQDN is mapped to the H.323 Gateway Bind IP Address to avoid duplicate entries of the gateways during discovery. Without this configuration, an H.323 gateway registered to a cluster (using the Device Name as either a short hostname or an FQDN), does not get discovered by the NNM iSPI for IP Telephony.

To configure the discovery settings for Cisco H.323 gateways:

  1. On the NNM iSPI for IP Telephony Cisco configuration console, click Discovery Configuration. The NNM iSPI for IP Telephony Cisco Discovery Configuration form opens.
  2. In the H.323 Gateway Configuration > Add/Modify H.323 Gateway Bind IP Address Configuration section, specify the required details in the fields provided on the page. The following table describes the fields on the page:
    Field NameDescription
    Tenant

    Select the name of the tenant from the drop-down list.

    Device Name

    Indicates the short hostname or the FQDN of the H.323 gateway.

    Make sure that the Device Name of the H.323 gateway is the same as the one that you specified while configuring the gateway to a cluster.

    IP AddressIndicates the bind IP address of the H.323 gateway.
  3. Click Add/Modify to complete the configuration. The configuration is displayed in the Current Configuration section.

To modify an H.323 discovery configuration setting:

  1. On the NNM iSPI for IP Telephony Cisco Discovery Configuration form, from the Current Configurations section, select the configuration that you want to modify.
  2. Click Modify.
  3. In the Add/Modify H.323 Gateway Bind IP Address Configuration section, make the required changes.
  4. Click Add/Modify. The modified configuration is listed in the Current Configurations section.

To delete an H.323 discovery configuration setting:

  1. On the NNM iSPI for IP Telephony Cisco Discovery Configuration form, from the Current Configurations section, select the configuration that you want to delete.
  2. Click Delete. The selected configuration is deleted from the Current Configurations section.

Configure IP Phones

You can use the NNM iSPI for IP Telephony Cisco IP Phone Configuration form to configure the following:

  • The range of IP Phone extensions to be excluded from monitoring
  • The list of IP Phones to be included for generating incidents at the Registration State Change
  • The custom attribute settings for the IP Phones

You can also use this form to modify or delete an existing configuration.

Exclude Cisco Phones from Monitoring

You can specify the range of extensions for phones to be excluded from being monitored for Cisco IP telephony network. After you specify the range of extensions, the NNM iSPI for IP Telephony stops monitoring the specified phones. These phones are still discovered in the subsequent discovery cycles, but not shown on the inventory views.

To specify the range of extensions for Cisco IP phones to be excluded:

  1. On the NNM iSPI for IP Telephony Cisco configuration console, click IP Phone Configuration. The NNM iSPI for IP Telephony Cisco IP Phone Configuration form opens.
  2. In the Exclusion Configuration > Add/Modify IP Phone Exclusion Filter section, specify the required details in the fields provided on the page. The following table describes the fields on the page:
    Field NameDescription
    TenantSelect the name of the tenant that contains the list of IP phones that you want to exclude.
    Cluster ID

    Indicates the ID of the cluster that contains the list of IP phones that you want to exclude.

    Filter

    Indicates the IP phones extension range to be excluded.

    To specify the range of phones to be excluded, follow these points:

    • Use the hyphen (-) to specify a range of extensions to be excluded. For example, if you want to exclude extensions from 8000 to 8005, you can specify as 8000-8005 in the Filter field.
    • Use asterisk (*), the wildcard character, to specify a set of extensions. For example, if you want to exclude all the extensions that start with 8, you can specify as 8* in the Filter field.
    • Use question mark (?), the wildcard character, to specify extensions that contain specific numerals at specific locations in the extension. For example, if you want to exclude all the extensions that end with 00, you can specify as ???00 in the Filter field.
  3. Click Add/Modify. The Current Configurations section lists the configurations that you created to exclude the list of phones to be monitored and discovered.

To modify a specified range of Cisco extensions to be excluded:

  1. On the Exclusion Configuration section of the NNM iSPI for IP Telephony Cisco IP Phone Configuration form, from the Current Configurations section, select the configuration that want to modify.
  2. Click Modify.
  3. In the Add/Modify IP Phone Exclusion Filter section, make the required changes.You cannot modify the Tenant and the Cluster ID values.
  4. Click Add/Modify. The modified configuration is listed in the Current Configurations section.

To delete a specified range of Cisco extensions to be excluded:

  1. On the Exclusion Configuration section of the NNM iSPI for IP Telephony Cisco IP Phone Configuration form, from the Current Configurations section, select the configuration that want to modify.
  2. Click Delete. The selected configuration is deleted from the Current Configurations section.

IP Phones for Registration State Change Incident Generation

You can specify a list of IP phones, based on the cluster that includes the IP phones, for which the registration state change incident must be generated.

To specify the list of Cisco IP phones for registration state change incident generation:

  1. From the Workspaces navigation pane, select Configuration, and the click iSPI for IP Telephony Configuration > Cisco Configuration. The NNM iSPI for IP Telephony Cisco Configuration Console opens.
  2. Click IP Phone Configuration. The NNM iSPI for IP Telephony Cisco IP Phone Configuration form opens.
  3. In the Inclusion Configuration > Add/Modify Filters for IP Phones for which Registration State Change Incidents are to be Generated section, specify the required details in the fields provided on the page. The following table describes the fields on the page:
    Field NameDescription
    Tenant

    Select the name of the tenant that contains the IP phones, for which the registration state change incidents are to be generated.

    Cluster ID

    Indicates the ID of the cluster that includes the list of phones for which the registration state change incident must be generated .

    FilterIndicates the extension range to be included. For more information, see Specifying the Range of Extensions for Cisco Phones to be Excluded from Monitoring.
  4. Click Add/Modify. The Current Configurations section lists the configured clusters for which you want to generate the incident for registration state changes.

You can select a configuration from the list and click Modify to modify the configuration. However, you cannot modify the Tenant and Cluster ID values.

You can select a configuration and click Delete to delete the configuration.

Configure Custom Attributes Settings for Cisco IP Phones

You can use the NNM iSPI for IP Telephony Configuration form to configure the custom attributes settings for the Cisco IP Phones. You may enable the custom attributes for the Cisco IP Phones only if these phones are already discovered and stored in the NNMi database. If you enable the custom attributes for Cisco IP Phones, you can see the phone icons for all the Cisco IP Phones in the NNMi topology maps.

To enable custom attributes for Cisco IP Phones:

  1. From the Workspaces navigation pane, select Configuration, and then click iSPI for IP Telephony Configuration... > Cisco Configuration. The NNM iSPI for IP Telephony Cisco configuration console opens.
  2. Click IP Phone Configuration. The NNM iSPI for IP Telephony Cisco IP Phone Configuration form opens.
  3. In the Discovery Configuration section, select the Enable Phone Custom Attribute Setting check box.You must not enable the custom attributes for Cisco IP Phones if these phones are not discovered in NNMi database.
  4. Click Apply Changes.

Configure Polling

You can use the NNM iSPI for IP Telephony Cisco Polling Configuration form to enable polling and set intervals for various pollers that are grouped based on the target to be polled. The pollers are grouped as follows:

  • Call Manager Specific Polling to poll the Cisco Unified Communications Manager (CUCM)
  • Survivable Remote Site Telephony (SRST) Specific Polling to poll the Cisco SRST routers
  • Gatekeeper Specific Polling to poll the Cisco gatekeeper devices
  • Unity and Unity Connection Specific Polling to poll their license consumption and port utilization
  • Voice Gateway Specific Polling to poll the Cisco voice gateways

Configure Cisco Unified Communications Manager Polling

To configure the polling specific to Cisco Unified Communications Manager:

  1. On the NNM iSPI for IP Telephony Cisco configuration console, click Polling Configuration. The NNM iSPI for IP Telephony Cisco Polling Configuration form opens.
  2. In the Call Manager Specific Polling Configuration section, specify the required details in the fields provided on the page. The following table describes the fields on the page:
    Field NameDescription
    Monitoring IP Phone Registration State Changes and IP Phone to Call Manager Associations

    Allows you to configure the continuous polling of the registration state and controller association of IP Phones. The available options are as follows:

    • Enable Polling: Select this check box to enable the polling of the Cisco IP Phones.
    • Interval: Indicates the interval (in seconds) to poll the Cisco IP Phones. The default value is 900 seconds.

    Internally, the NNM iSPI for IP Telephony also runs a light-weight poller to detect changes in the registration states of Cisco IP Phones within 5 minutes of change on the network. However, the interval of this internal poller cannot be configured. Also note that this internal poller collects incremental registration state change data from each cluster rather than information about all the IP Phones in the Cluster.

    Call Manager State Monitoring

    Allows you to configure the continuous polling of the state of the CUCM servers. The available options are as follows:

    • Enable Polling: Select this check box to enable the polling of the state of the CUCM servers.
    • Interval: Indicates the interval (in seconds) to poll the state of the CUCM servers. The default value is 300 seconds.
    Registration State & Controller-Association of Voice Gateway Interfaces Monitoring (MGCP Only)

    Allows you to configure the continuous polling of the registration state and controller association of voice gateway interfaces. The available options are as follows:

    • Enable Polling: Select this check box to enable the polling of the registration state and controller association of voice gateway interfaces.
    • Interval: Indicates the interval (in seconds) to poll the registration state and controller association of voice gateway interfaces. The default value is 300 seconds.
    Monitoring Registration State of Gatekeeper Controlled Inter Cluster Trunks

    Allows you to configure the continuous polling of the registration states of Cisco gatekeeper-controlled inter-cluster trunks. The available options are as follows:

    • Enable Polling: Select this check box to enable the polling of the registration states of Cisco gatekeeper-controlled inter-cluster trunks.
    • Interval: Indicates the interval (in seconds) to poll the registration states of Cisco gatekeeper-controlled inter-cluster trunks. The default value is 300 seconds.
    Registration State of Voice Mail Devices Monitoring

    Allows you to configure the continuous polling of the state of the discovered voice mail devices. The available options are as follows:

    • Enable Polling: Select this check box to enable the polling of the state of the discovered voice mail devices.
    • Interval: Indicates the interval (in seconds) to poll the state of the discovered voice mail devices. The default value is 300 seconds.
  3. Click Apply Changes.

Configure Cisco Survivable Remote Site Telephony (SRST) Routers Polling

To configure the polling specific to SRST:

  1. From the Workspaces navigation pane, click Configuration > iSPI for IP Telephony Configuration... > Cisco Configuration. The NNM iSPI for IP Telephony Cisco Configuration Console opens.
  2. Click Polling Configuration. The NNM iSPI for IP Telephony Cisco Polling Configuration form opens.
  3. In the Survivable Remote Site Telephony (SRST) Specific Polling Configuration section, specify the required details in the fields provided on the page. The following table describes the fields on the page:
    Field NameDescription
    Survivable Remote Site Telephony (SRST) State Monitoring

    Allows you to configure the continuous polling of the available Cisco SRST routers on the network. The available options are as follows:

    • Enable Polling: Select this check box to enable the polling of the Cisco SRST routers.
    • Interval: Indicates the interval (in seconds) to poll the Cisco SRST routers. The default value is 300 seconds.
  4. Click Apply Changes.

Configure Cisco Gatekeepers Polling

To configure the polling specific to gatekeepers:

  1. From the Workspaces navigation pane, click Configuration > iSPI for IP Telephony Configuration... > Cisco Configuration. The NNM iSPI for IP Telephony Cisco Configuration Console opens.
  2. Click Polling Configuration. The NNM iSPI for IP Telephony Cisco Polling Configuration form opens.
  3. In the Gatekeeper Specific Polling Configuration section, specify the required details in the fields provided on the page. The following table describes the fields on the page:
    Field NameDescription
    Monitoring Gatekeepers' Count of Registered Endpoints

    Allows you to configure the continuous polling of the number of endpoints registered with every gatekeeper. The available options are as follows:

    • Enable Polling: Select this check box to enable the polling of the number of endpoints registered with every gatekeeper.
    • Interval: Indicates the interval (in seconds) to poll the number of endpoints registered with every gatekeeper. The default value is 300 seconds.
  4. Click Apply Changes.

Configure Unity Devices and Unity Connection Servers Polling

To configure the polling specific to unity devices and unity connection servers:

  1. From the Workspaces navigation pane, click Configuration > iSPI for IP Telephony Configuration... > Cisco Configuration. The NNM iSPI for IP Telephony Cisco Configuration Console opens.
  2. Click Polling Configuration. The NNM iSPI for IP Telephony Cisco Polling Configuration form opens.
  3. In the Unity and Unity Connection Specific Polling Configuration section, specify the required details in the fields provided on the page. The following table describes the fields on the page:
    Field NameDescription
    Unity and Unity Connection related License Consumption and Port Utilization Monitoring

    Allows you to configure the continuous polling of the license points consumed by the Cisco Unity devices and Unity Connection servers along with the polling of the port utilization. The available options are as follows:

    • Enable Polling: Select this check box to enable the polling of the consumed license points.
    • Interval: Indicates the interval (in seconds) to poll the consumed license points. The default value is 300 seconds.
  4. Click Apply Changes.

Configure Cisco Voice Gateways Polling

To configure the polling specific to voice gateways:

  1. From the Workspaces navigation pane, click Configuration > iSPI for IP Telephony Configuration... > Cisco Configuration. The NNM iSPI for IP Telephony Cisco Configuration Console opens.
  2. Click Polling Configuration. The NNM iSPI for IP Telephony Cisco Polling Configuration form opens.
  3. In the Voice Gateway Specific Polling Configuration section, specify the required details in the fields provided on the page. The following table describes the fields on the page:
    Field NameDescription
    Gateway Interface Operational State Monitoring

    Allows you to configure the continuous polling of the operational states of voice gateway interfaces. The available options are as follows:

    • Enable Polling: Select this check box to enable the polling of the operational states of voice gateway interfaces.
    • Interval: Indicates the interval (in seconds) to poll the operational states of voice gateway interfaces. The default value is 300 seconds.
    Voice Gateway Channel Usage State Monitoring

    Allows you to configure the continuous polling of the usage states of voice gateway channels. The available options are as follows:

    • Enable Polling: Select this check box to enable the polling of the usage states of voice gateway channels..
    • Interval: Indicates the interval (in seconds) to poll the usage states of voice gateway channels. The default value is 300 seconds.
    Voice Gateway Channel Usage Monitoring (Wait Time to Declare Idle)

    Allows you to configure the time for which the NNM iSPI for IP Telephony waits, before declaring a channel as idle. The available option is as follows:

    • Interval: Indicates the interval (in seconds) for which the NNM iSPI for IP Telephony must wait before marking the usage state of a channel to Idle. For example, for a waiting time specified as 300 seconds and the period of the usage state monitoring for channels as 150 seconds, during the monitoring of usage state for channels, if the NNM iSPI for IP Telephony finds the usage state to be idle, it waits for two subsequent periodic usage state monitoring cycles. If it still finds the usage in idle state, it declares the state as Idle. When the usage state is not Idle, the waiting period is not applicable and is abandoned. The default interval is 300 seconds.
  4. Click Apply Changes.

Configure Reporting

You can use the NNM iSPI for IP Telephony Cisco Reporting Configuration form to configure the following types of reports for Cisco:

  • CDR
  • B-channel Activity
  • Phone Media Access Control (MAC)
  • Voice Mail

Configure CDR Reporting

You can use the NNM iSPI for IP Telephony Cisco Reporting Configuration form to configure CDR reporting for Cisco IP Telephony networks. However, you have to install and enable the iSPI Performance for Metrics to enable CDR reporting by the NNM iSPI for IP Telephony.

To configure the Cisco CDR reporting:

  1. On the NNM iSPI for IP Telephony Cisco configuration console, click Reporting Configuration. The NNM iSPI for IP Telephony Cisco Reporting Configuration form opens.
  2. In the Reports Using CDR Data section, specify the required details in the fields provided on the page. The following table describes the fields on the page:
    Field NameDescription
    Enable Reporting

    Select this check box to enable the Cisco CDR reporting.

    Number of Calls to Write

    Indicates the number of processed calls to be sent to NPS or the Global Manager in an instance in the field. The default value is 5000.

    Calling and Called party Numbers in ReportsSelect this check box to display the calling party number and the called party numbers in the Call Details reports.
    Forward to Global ManagerSelect this check box if you want the processed call information to be sent from the current management server to the global manager. This option is enabled by default.
  3. Click Apply Changes.

Enable Cisco B-Channel Activity Reports

You can use the NNM iSPI for IP Telephony Reporting Configuration form to enable or disable Cisco B-Channel activity reports.

To configure Cisco B-Channel activity reporting:

  1. From the Workspaces navigation pane, select Configuration, and then click iSPI for IP Telephony Configuration... > Cisco Configuration. The NNM iSPI for IP Telephony Cisco configuration console opens.
  2. Click Reporting Configuration. The NNM iSPI for IP Telephony Cisco Reporting Configuration form opens.
  3. In the B-Channel Activity Reports section, select the Enable Reporting check box.
  4. Click Apply Changes.

Enable Phone MAC Reports

You can use the NNM iSPI for IP Telephony Reporting Configuration form to enable or disable IP phone (MAC) comma-separated value reports. These reports include information about the IP phones that are added, deleted, or shifted (moved) in the network. After you enable this report, the NNM iSPI for IP Telephony generates this report when a phone is added, removed, or moved on the network.

You must make sure that IP phone discovery is enabled in NNMi for this reporting to work. Also, this reporting feature does not work in the NAT environment with overlapping IP addresses.

To configure IP Phone MAC reporting:

  1. From the Workspaces navigation pane, select Configuration, and then click iSPI for IP Telephony Configuration... > Cisco Configuration. The NNM iSPI for IP Telephony Cisco configuration console opens.
  2. Click Reporting Configuration. The NNM iSPI for IP Telephony Cisco Reporting Configuration form opens.
  3. In the Phone MAC Reports section, specify the required details in the fields provided on the page. The following table describes the fields on the page:
    Field NameDescription
    Enable Reporting

    Select this check box to enable the Cisco IP phone MAC reporting.

    Access Switches

    Indicates the name of the configuration file that contains the comma-separated list of access switch IP addresses.

    This field is mandatory if you want the phone MAC reports to include the details regarding the phone shifting in the network. The file is present at the following location:

    • Windows platforms: nnmDataDir\shared\ipt\PhoneMacReports\conf
    • UNIX/Linux platforms: /var/opt/OV/shared/ipt/PhoneMacReports/conf
    Forward to Global ManagerSelect this check box if you want the phone MAC reporting information to be sent from the current management server to the global manager. This option is enabled by default.
  4. Click Apply Changes.

You can access the phone MAC reports from the following location:

  • Windows Platforms: nnmDataDir\shared\ipt\PhoneMacReports\reports
  • UNIX/Linux Platforms: /var/opt/OV/shared/ipt/PhoneMacReports/reports

In High Availability environments, you can access these reports from the following location:

  • On Windows

    <Shared_Drive>\NNM\dataDir\ipt\PhoneMacReports\reports

  • On UNIX/Linux

    /nnm_mount_point/NNM/dataDir/ipt/PhoneMacReports/reports

    In this instance, <Shared_Drive> (Windows) or /nnm_mount_point (UNIX/Linux) is the

    directory location for mounting the NNMi shared disk.

The reports follow the following nomenclature standard: <ipt_server_name>_<vendor name>_AddPhones_<date>.csv. The file that is currently being updated displays a csv.lck extension name in the file name.

  • ipt_server_name: indicates the name of the NNM iSPI for IP Telephony server if the server is a remote server and the report is generated at the global manager. For local servers, this value gets replaced by the identifier Local.
  • vendor name: indicates the name of the vendor, Cisco or Avaya.
  • date: indicates the date in mmddyy format when the report was generated.

You can identify if the report is generated for a phone added, moved, or removed by the following identifier in the report name:

  • AddPhones: generated for phones added.
  • RemovePhones: generated for phones removed from the network.
  • MovePhones: generated for phones moved in the network.

The report displays the following details as comma-separated values for a phone addition, removal, or a move.

Report Data Description
detected timestamp The time at which the change was detected.
phoneextn The phone extension that was added, removed, or moved.
phonemacaddr The MAC address of the IP phone.
phoneipaddr The IP address of the phone.
cmipaddr The IP address of the call manager associated with the phone.
clusterid The ID of the cluster that includes the phone.

Enable Voice Mail Reports

You can use the NNM iSPI for IP Telephony Reporting Configuration form to enable or disable voice mail reports.

To configure voice mail reporting:

  1. From the Workspaces navigation pane, select Configuration, and then click iSPI for IP Telephony Configuration... > Cisco Configuration. The NNM iSPI for IP Telephony Cisco configuration console opens.
  2. Click Reporting Configuration. The NNM iSPI for IP Telephony Cisco Reporting Configuration form opens.
  3. In the Voice Mail Reports section, select the Enable Reporting check box.
  4. Click Apply Changes.

Send Help Center feedback