I was running 6.1 and i migrated to 9.1 successfully with no issues, i have 2 questions, i have tried that but i want experts confirmation.
the service of EM has been changed automaticaaly as per the below.but the users are able to login should i changed to previous 6.1 URL or i shld keep the new URL. I hope these extra (#&EMCC=#EMCC#) are for EM cross cluster.
I am increasing the CUCM till 3 nos in each group, so i plan to have a redundant EM service i created service for subscriber in HO and it is working fine, i will create one more EM service for 2nd subscriber which will be in DR incase HO PUB and SUB fails all phone shld register to DR and they shld sble to login.
I have read many threads of EM service and the best design is to have a load balancer but unfortunately i dont have so i m planning to go with 3 No's of EM service.Is it will create a problem in the future for this type of setup
I have never used DHCP on CUCM and would never recommand it to anyone, leave DHCP to dedicated MSFT server to Cisco router/switch. If you insist on using DHCP on CUCM, I belive there is a section on it in CUCM SRND that should provide you the answer.
Assume if i have only one service and If in the Enterprise parameters in the phone URL parameters i am pointing URL to subscriber addresses and in the EM phone service i am pointing to publisher ip address, the EM service will hit to subscriber or publisher.???
Though the publisher is up can we point the EM service to subscriber, user will be able to login.
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...