You should only be using the Administration pages on the Publisher CallManager - no matter how many CMs are in your cluster. The Subscribers get SQL and LDAP replication from the Publisher, so changes made on the Publisher propagate to the Subscribers.
For the IVR issue - in your JTAPI Provider setup, do you have both CallManagers listed there by hostname or IP, separated by commas?
That's fine - either method should work. Do you get any errors if you edit the JTAPI provider information? Also, do you have a CallManager Group set up which includes both the Publisher and Subscriber? If so, then try moving the Subscriber up to the top of the list - this will cause all devices to attempt to register with it first.
yes , of course .. i have both publisher and subscriber in call manager group
if first CCM fails . all phones work via secondary ..
but .. one add question ..
is it important what address (first or second ccm ) to use when i setup IVR and initialise profile via http:////cammmanage_subscriber/appadmin .. directory configuration .. i used ip address of second ccm when initialised prfile for subscriber's IVR
it works .. but when i disconnect publisher from network .. IVR profile on second CCM can't be initialiised
The IVR Directory Services can only initialize with 1 CallManager. It would make sense that you would not be able to re-initialize to the Subscriber if the Publisher is down, because the initialization depends on LDAP. If the Publisher is down, then LDAP authentication/replication between the Pub and Sub can't take place, so the Sub can't service the initialize request from the IVR at that point.
That doesn't mean the IVR is *down* if the Pub is down, it just means you can't switch profiles or create new profiles.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...