Troubleshooting Partial Service on CM telephony Subsystem
Easy way of Troubleshooting Partial Service on CM telephony Subsystem:
Just thought of putting this across as it has been very helpful in lot of cases.
We have seen many cases where the CM Telephony subsystem is in partial service. The main reasons for this could be:
- Some of the triggers go unregistered.
- Some of the CTI ports go unregistered.
- Misconfiguration of the triggers or the CCG.
The common solutions to this may be Data Resync, CTI Manager Restart, etc. Sometimes it does become that all this would fail and we need to check the MIVR and JTAPI logs for finding the fault.
RTMT is a very good tool in case we need to check which trigger or port is unregistered or Out Of Service.
Login to the RTMT of the UCCX:
Click on the Cisco Unified CCX in the left pane below:
Choose CUCM Telephony Data and then you will get the option of choosing the Triggers, Call Control Groups as a whole, CTI ports individually, and a Summary section:
Select Triggers and it will prompt you for the server. In case of HA, both the servers will be listed:
It will then display the status of the triggers in the system. It will show the status, etc and the recommended action will be listed if there are any triggers which has issues.
Same goes for CTI ports as well:
This is easier than pulling out the logs to find which trigger or port is causing the partial service status.
Note: If you do not have access to the RTMT, then you can always reset the username and password from the CLI using:
Utils reset_application_ui_administrator_name
Utils reset_application_ui_administrator_password
This will also reset the Fresh install username and password. The initial AppAdmin username and password is the same as the username and password for the RTMT.
Please rate the documents if it is helpful!
Regards,
Arundeep N
