We have our UCCX primary,cucm pub,cucm sub1 in data centre-1. Agents are also working only out of date center-1 using cisco hard phones. UCCX secondary and cucm sub2 are available in data center-2. In the event of a power failure in data centre-1 which means that uccx primary,cucm pub,cucm sub1 and agent hard phones/computers are down, some of the agents will move out of the data centre-1 to data centre-2.
In the above scenario, we have to give these relocated agents new cisco phones at data centre-2. However the agent ID will have to remain the same. Because the cucm pub is down, we cannot do an ipcc extension/device remapping on the end user page.
Is there a feature that can address the above situation
Objective is to have the same agent login with his ID, however the hard phone will be different
1. EM can work without the publisher. You can provision a load balancer to direct connections to EM to the active/local subscriber in each DC (rather than the publisher) even in normal operation.
If you don't do this users can log in to a phone (probably with help from IT) in an emergency by calling a URL on the subscribers that are available : e.g. http://subscriber1/emapp/EMAppServlet?device=SEP000011112222&userid=harrison&seq=2468 (where seq is the pin).
Or a third option would be to use an application to log the users in such as my Phone Operations Manager which you can use to log users in and out of phones (http://www.ipcommute.co.uk/5-current-products/11-phone-operations-manager.html)
2. Another option would be to use Jabber as the phone client. That doesn't require EM; the agent's line will move whenever they log in to the app.
Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!
As mentioned previously in my previous article and following the same idea of certificate pinning in Cisco Meeting Server, to demonstrate this concept added since version 3.0. I used two different CA to sign :1-The WebBridge certificate with CA's certific...
Certificate pinning is introduced on cisco meeting server starting in CMS 3.0 to help prevent man in the middle attack.But what is the Certificate Pinning?Traditionally, SSL Handshake consists on the validation of the server's certificate, let's say colla...
In a Clustering over the WAN deployment, securing the ICCS (Intra-Cluster Communication Signaling) traversing the WAN can be a requirement. The IPSEC VPN Policy between nodes can be configured to secure the ICCS Traffic.To quickly verify that the IPSEC is...
Attracted by the concept of dial plan and the passion of writing, I launched a challenge to write a workbook with practical scenarios covering in details this concept, the result is a workbook with 30 practice labs treating many components such route patt...