Hi Team,
Recently, we performed a CUCM failover activity at one of our customer premises. After the failover, users attempted to log in to Jabber and noticed a weird behaviour: it only worked on their laptops (Windows) within the BCP network(during the failover, the production network switched to the BCP site and Jabber registered with CUCM SUB)and it did not work on any other laptop (Windows) within the BCP network, resulting in an error message: "The telephony configuration settings are invalid".
Users attempted to log in to their Jabber client from multiple systems when the production network came online(Jabber registered with CUCM PUB) after the BCP drill activity, and it worked seamlessly without any issues.
Note :
- CUCM cluster consists of 2 nodes, CUCM PUB and CUCM SUB
- Deployed CUCM PUB in production network and CUCM SUB in BCP site.
- CUCM Group having CUCM PUB as primary node and CUCM SUB as secondary node.
Can anyone suggest if anything need to check or make change in configuration wise on CUCM end in this scenario?
I hope this needs to be checked from both network ends, not at the CUCM level.
Comments or suggestions will be greatly appreciated!
