I have been told be TAC on several ocassions that only the publisher node needs to be in the list, and if you were to specify another server on top of the pub, UCCX, via AXL, will determine the pub and only connect to it anyway.
What's the main role of the pub: db and cluster master, right? And AXL is DB modifications, right? Then only use the pub in the list.
Please use the star ratings to help drive great content to the top of searches.
I don't agree... If you don't have multiple AXL servers configured in UCCX, try turning off the publisher.
- No one will be able to log in
- Stuff will go out of service within a short period of time
Yes, the publisher is the DB master and is the only fully writeable server, but the other servers are still able to perform authentication and respond to other queries.
You can write changes via AXL to any server; it's similar to configuring the system via CCMAdmin on a subscriber. Can you do it? Yep. Does it actually write changes to the subscriber? Nope, they get written to the pub and replicated back.
Configuring multiple AXL providers is the only way to have real CUCM resilience. In my opinion Cisco should have modified the appadmin initial install wizard to allow multiple servers to be configured for this (as with the RM/JT services) as no one ever goes back and properly reconfigures this setting - the wizard just asks for a the publisher details.
I think a lot of the confusion around this is throwback from the dark days of Windows CUCM with DC Directory. With those systems the pub HAD to be first, and you would usually add a sub as a secondary.
Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!
"In my opinion Cisco should have modified the appadmin initial install wizard to allow multiple servers to be configured for this (as with the RM/JT services) as no one ever goes back and properly reconfigures this setting - the wizard just asks for a the publisher details."
I am fairly certain this can be done on version 8.x and 5.x/7.x once you get to the Jtapi/RMCM user setup page.
Anyhow I don't believe the rule of homing it to the PUB is applicable any more assuming that was in the guides at all, don't recall too well.
As Aaron stated without getting a backup AXL, assuming your PUB goes down the system is usless and dead in the water as there is no user authentication and RP/CTI ports would all be unregistered.
If you refer to the HAoWAN guide it acutally states to point each respective node to their local CUCM box.
So that rule alone would break the assumption it has to be pointed at the PUB.
Long story short, yes home it to its respective call manager depending on your setup, PUB or SUB are fine.
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...