1. Specifying a different domain under "Cluster Topology" seems to break things (unable to connect to database).
2. Even if I could fix issue #1, SSL certificates seem to be generated based on the hostname -- CSRs as well. Meaning Jabber will not connect because the name it is connecting to does not match the certificates "CN" field.
Not really - it seems best to just use your public email domain for the IM/P server(s): im.companydomain.com
Technically on IM/P 10.0 you can specify a different domain for end users than the one assigned to the server... however just putting it in the public company domain seems to be the option least likely to create problems.
I am pretty sure putting it in a .local domain can cause some problems with Collaboration Edge as well..
Cisco Finesse Not Ready - Call Overlap status is very a very common issue seen on Finesse desktop. Agents miss two calls and they are put in Not Ready - Call Overlap status. This is very likely related to CVP server and it's unreachabl...
Lab 1: Cisco Meeting Server Standalone CertificatesLab 2: Cisco Meeting Server Cluster Certificates with Multi-SANLab 3: Multiple Certificates with Multiple CA ServersLab 4: Cisco Meeting Server Cluster Certificates Advanced ScenarioLab 5: Streamer Servic...
Certificates are the first step to deploy Cisco Meeting Server, preparing certificate are very important to enable different services. As a VOIP administrator, mastering the concept of certificates is unavoidable
Using multiple CA servers, instead of a si...
I just finished to write a comprehensive certificates preparation for Cisco Meeting Server Clustering. Through 60 pages I explained in detail, how to create certificates for database cluster, callbridge cluster, certificate chain for webbridge3, certifica...