We have a testbed setup with follwing components...
icm - 7.2 (duplexed)
cucm - 6.1 ( cluster of 3, 1 pub & 2 sub )
crs - 5.0 (load balancing)
During the failover testing if we stop sub1 and PG1B the contact centre is down. In the configuration the PG1A pointed to sub1 and PG1B pointed to sub2. Please tell me any additional configuration is there or this is limitation of cisco architecture.
If i fail the sub1 the PG1B is active and if i fail sub2 the PG1A is active and if i create any user in the cluster it immediately reflecting in all the CUCM. so it seems no issue with pguser & CUCM database.
>In the configuration the PG1A pointed to sub1 and PG1B pointed to sub2.
This is correctly setup.
>During the failover testing if we stop sub1 and PG1B the contact centre is down.
So you are stopping two of the components, and expecting this to work correctly?
Fault tolerance is designed to avoid single points of failure, through redundancy and fail over.
As the name implies, it provide tolerance for a fault - not necessarily tolerance for multiple simultaneous faults. ICM provides extremely good fault tolerance, but it will not survive what amounts to a catastrophic failure of multiple components.
Based on the information provided, your setup has two communications paths between the CM cluster and ICM:
1. Sub 1 -> PG1A
2. Sub 2 -> PG1b
The solution will be able to continue operation if you lose EITHER a single subscriber, or a single PG side - NOT BOTH (unless you lose both components from the same communication path).
We made a configuration change in the PIM configuration, we added the another CUCM IP seperated by comma(,) during the failover its working as expected, but is this affect any other component and system behaviour.
Since this is not document by cisco we had reverted back to the existing setup.
Please suggest can we proceed on above configuration.
Unfortunately not. This used to be supported in earlier releases of IPCC, but I understand it was removed because the multiple JTAPI connections resulted in to synchronisation issues between the PG sides and the CTI Manager processes on Call Manager.
As such, Cisco now only support one PIM connection for each CTI Manager, and one CTI Manager connection for each PIM.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...