Troubleshooting Cisco CallManager

This section will guide you to overcome the various issues faced by you during the use of Cisco CallManager and its various functionalities.

Issues in Server Addition using AppViewX UI

Error Message Possible Cause Possible Solution
Device Name already exists. A Cisco CallManager device exists in inventory with the same name. Check the Device name, it should be unique.
Details incorrect Some of the mandatory fields might be missing or might be invalid. Add all the valid information in the mandatory section.

Issues in Device communication

Error Message Possible Cause Possible Solution
Communication to <hostname name> has failed.

  1. Device unreachable.

  2. Invalid credential.

  3. Invalid port.

  1. Kindly check if the given IP/FQDN is reachable.

  2. Kindly check the credentials provided.

  3. Kindly check the port and firewall settings.
Cisco Tomcat service is not active Cisco Tomcat service is not in an up and running state.

Kindly restart the Cisco Tomcat Service.

Command to verify the status of services is:

utils service list

Issues in Discovery

Error Message Possible Cause Possible Solution
Received failed response from batch Required Services may not be in an up and running state.

Please ensure the supported services are up and running state and services are associated with SSL configs.

Services supported by AppViewX :

Cisco tomcat

Command to verify the status of services is:

utils service list

Issues in CSR generation at Endpoint

Error Message Possible Cause Possible Solution
CUCM CSR gen command failed Command execution may fail. Kindly ensure all CSR gen commands are executed properly.

Issues in Certificate Push

Error Message Possible Cause Possible Solution
Cert push got failed due to Error while importing server certificate.

  1. The certificate should be issued from CSR generated by device.

  2. CUCM will not allow to push the same cert again.

  1. Kindly ensure the certificate issued by the CSR generated from Device.CUCM will not support to push any other certs.

  2. CUCM will delete the CSR information from the device on successful cert push. Kindly ensure you are pushing the newly issued certificate and respective CSR information for the same should be available in the device.
Cert push got failed due to Error while importing trust certificate. CA/Intermediate cert with the same name may already exist in the device. AppViewX will not overwrite the existing CA configurations. Kindly delete/rename the old certificates to proceed with push.

Issues in Certificate Bind

Error Message Possible Cause Possible Solution
Cert bind got failed.Cause : Service restart failure. Connection timeout or Invalid Services Kindly check if the device is in a reachable state to execute the command.