I am trying to hook two of these servers up together. I am installing it like a normal call manager cluster with one publisher and one subsciber, however it is not working. It seems like they need to be hooked up via a "hot-standby server" but I see nowhere to configure this or any documentaion on this. Does anyone know where to find info on this or how these are suppose to be hooked up.
"The Cisco Media Convergence Server 7815-1000 (MCS 7815-1000) is the platform designed to address the needs of locations requiring 200 IP phones or less. The MCS 7815-1000 can be configured to provide N+1 redundancy for a location through the installation of a second MCS 7815-1000 acting as a hot-standby server. "
However I believe we got it working, it seems call manager does not play well connected to a domain, once we disconnected from the domain the installation of the subscriber went well. It just threw me off in the documentation with the new terms such as "hot-standby server" and also saying the 7815 can not cluster. But they can!
Hmmm, interesting. I have not seen the term hot-standby in conjunction with CallManager. This seems to be a marketing term, notice the "acting as". The reality is that you are clustering the two servers, just that one of them will do all of the call processing and the other serves as a backup, thus "acting as" a hot standby.
Not sure where you saw that the 7815 cannot cluster, unless it is this page:
Where it references Max number of phones per cluster and it indicates not applicable for the 7815. I just think that this means, due to processing power, that you can't grow this server into a cluster of more than two servers supporting more than 200 phones. Again, marketing.
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...