SevOne logo
You must be logged into the NMS to search.

Table of Contents (Start)

Enable CallManager

This documentation applies to NMS version 5.4. An online version of the software can be found here.

Cisco CallManager

CallManager enables you to monitor the Cisco Unified Communications Manager. CallManager is the IP telephony call processing component of the Cisco Unified Communications solution. The CallManager plugin enables you to monitor the real time performance counter and database information on the Cisco Unified Communications Manager device including statistics such as calls active, attempted, and completed on the cluster. The CallManager plugin also monitors statistics such as the performance of remote gateways, conference calling resources, and system performance counters such as memory, CPU, and disk space.

This topic describes how to enable CallManager devices to send CallManager data to SevOne NMS. This workflow is outside of the SevOne NMS application and may not present all of the steps your network requires to enable devices to send CallManager data. If the following instructions are not applicable for your network please reference the official Cisco documentation.

Related SevOne NMS workflows include the following.

  • The Device Manager provides access to the New Device page and the Edit Device page where you enable the CallManager plugin for a device.

  • The Object Types page enables you to enable or disable the CallManager object types and indicator types you want the CallManager plugin to poll in your network.

  • The Indicator Type Map page enables you to enable or disable the device specific indicators you want the CallManager plugin to poll.

In SevOne NMS, some CallManager object types are enabled by default. The Object Types page enables you to enable additional object types and indicator types. The Object Rules page enables you to define rules to not poll specific CallManager object types. The Indicator Type Map page enables you to enable and disable specific CallManager indicators for each device for which you enable the CallManager plugin.

Send CallManager Data to SevOne NMS

AXL Installation Steps

You start and stop the AXL web service from Cisco Unified Communications Manager Serviceability. The service is disabled by default. You should start the service before you use the AXL APIs.

  1. From the Cisco Unified Communications Manager Administration window, click Navigation then click Cisco Unified Communications Manager Serviceability.

  2. Click Tools then click Service Activation.

  3. From the Server box, select the server and click Go.

  4. From Database and Admin Services, select Cisco AXL Web Service.

  5. Save your changes.

When the AXL service starts, AXL deploys as a web application within Apache Tomcat. The WAR file deploys to Tomcat under:

/usr/local/thirdparty/jakarta-tomcat/webapps/axl.

Troubleshoot CallManager

Use the following check list to avoid common problems and to fine tune your configuration.

  1. Check the following if the AXL client application cannot connect to the AXL service.

    • Is the AXL application configured with the correct IP address for the AXL server?

    • Is the AXL application configured with the appropriate AXL user credentials?

    • Does the application server have HTTPS connectivity to the AXL server? Use the following URL to access AXL:
      https://server-name:port/axl/ (port is 8443)

    • Is HTTPS (secure) configured for AXL?

  2. Perform the following steps to verify basic AXL functionality.

    1. Go to the AXL API URL via a web browser.

      Example: Enter https://servername:8443/axl/ in the Address field.

    2. When prompted for user name and password, use the standard administrator login, or use the user name that is associated with a user group that is assigned the AXL role.

    3. Look for a message that states the AXL listener is working and accepting requests but only communicates via POST.

  3. If the AXL functions or requests fail with the User Authorization message: "Access to the requested resource has been denied" confirm that the user has the permission to the Standard AXL API Access. You can check this from the Permission Information section of the End User Configuration page.

  4. If the AXL functions or requests fail, check the following:

    • AXL logs for AXL or SOAP error responses.

    • For further debugging, view the AXL log files with the RTMT application.

  5. Your browser may not support display of this image. Check that applications in a cluster configuration are connected to the AXL service only on the Cisco Unified Communications Manager Publisher server if the application needs to modify the database.

Created with Scroll Wiki HTML Exporter for Confluence.