I'm trying to integrate a CCX and CUCM version 10. I also have a IM&Presence Server. When I've done the CCX installation, in dialog Unified CM Telephony Subsystem and RmCm Subsystem window I only have as Available CTI Manager the IM&Presence Server. I've selected it as cti manager and apparently, the rmcm user and cmteluser have been created in CUCM correctly. Anfortunately, in CCX Serviceability, inside CCX Engine> Subsystem Manager, the 'Unified CM Telephony Subsystem' is out of service and RmCm Subsystem is 'initializing'. I've try to create an application, but the Router point doesn't registered in the CUCM. I've tried to reboot CUCM and CCX twice and check that CUCM services are running. Any idea of what happens?
This is a known defect on 10.0. The reason this occurs because in CUCM 10.x onwards, CUPS node is not added as an Application Server but rather a Server node itself and the query the UCCX Sends is based on AXL and retrieves all the CUCM nodes.
This is an internal defect, but you can find the summary below:
When we are installing CUCM, CUPS and UCCX 10.x, the CUPS ip address shows as an available CTI manager causing many issues with the UCCX integration also leading to a loss of the actual CTI managers available.
This is because of the architectural change in the CUCM 10.x onwards, where CUPS is added as a separate node on the System -- Server page with the Server Type -- CUCM IM and Presence.
Prior to 10.x in CUCM, this was added as an application Server.
This leads to a lot of issues as the UCCX sees the node as an available CTI manager. The AXL request sent to the CUCM needs to be based on the Server Type as the current query returns both the CUCM and the presence nodes in the cluster.
I've deleted the CUPS from the server page in CUCM and shutdown the CUPS. After that, the CUCM appears in CCX as CTI Manager server. I've selected it and I've create again the CUPS and start it. It seems to work, although I haven't had time to test any script yet, but all UCCX service are 'In service'. I'm trying to look for UCCX 10.5 but I couldn't find. Is it released? Do you know any workaround to solve the intergration issues?
That is a correct workaround procedure and the fact that the UCCX is IN SERVICE ensures correct JTAPI and RMCM integrations with CUCM.
UCCX 10.5 is scheduled for mid June (tentative) and still in the development phase. We actually found the issue in 10.0 and worked on the above defect. We have also modified the guide to reflect this and can be found under the defect CSCun67553
Again this being internal would not be visible in the bug tool kit, but here is the note that is added to the guide:
The following needs to be added as a Caution:
In case of fresh deployments of CUCM, CUPS and UCCX, ensure that the DNS is configured for CUCM, UCCX and CUPS as a best practice.
If DNS is configured only for UCCX (bypassed for CUCM) and CUPS is already added on the CUCM, then we will face issues when the integration of the CUCM and the UCCX is carried out.
To avoid this, we have 2 options:
1. Delete the CUPS node from Presence Redundancy Groups and the System -- Server page and proceed with the integration of the CUCM and UCCX. Add the CUPS node after this integration is successful.
2. Define the CUCM and other CTI nodes (subscribers) by ip address under System -- Server page for the proper integration between CUCM and UCCX.
Note: Replacing the hostname to ip and vice-versa on the System -- Server should not cause any issues, though a warning is received on the webpage. The certificates will have to be regenerated.
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...
This document describe how DST changes and how time changes are
implemented in DST. Daylight Saving Time (DST) is the practice of
setting the clocks forward 1 hour from standard time during the summer
months, and back again in the fall, in order to make b...