Cisco Cisco TelePresence Video Communication Server Expressway
The Deployment field does not show if you have not created multiple deployments. All nodes belong
to the default deployment if you choose not to use multiple deployments.
to the default deployment if you choose not to use multiple deployments.
f. Click Add address.
If you enabled TLS verify mode, then the VCS tests whether a secure connection can be established.
It does this so you can find any TLS configuration errors before it continues the discovery process.
If the secure connection test was successful, or if you did not enable TLS verify mode, then the
system attempts to contact the publisher and retrieve details of its associated nodes.
It does this so you can find any TLS configuration errors before it continues the discovery process.
If the secure connection test was successful, or if you did not enable TLS verify mode, then the
system attempts to contact the publisher and retrieve details of its associated nodes.
Note: The status of the discovered node will be Inactive unless a valid traversal zone connection
exists between the VCS Control and the VCS Expressway (may not yet be configured).
exists between the VCS Control and the VCS Expressway (may not yet be configured).
3. Repeat the discovery procedure for other IM and Presence Service nodes/clusters, if required.
4. Click Refresh servers to refresh all the node details after configuring multiple publisher addresses.
Discovering Unified CM Servers
1. On VCS Control, go to
Configuration > Unified Communications > Unified CM servers
.
The page lists any Unified CM nodes that have already been discovered.
2. Add the details of a Unified CM publisher node:
a. Click New.
b. Enter the Unified CM publisher address.
b. Enter the Unified CM publisher address.
You can enter an FQDN or an IP address, but we recommend using the FQDN when TLS verify
mode is On.
mode is On.
c. Enter the Username and Password of an account that can access this server.
Note: These credentials are stored permanently in the VCS database. The corresponding Unified CM
user must have the Standard AXL API Access role.
user must have the Standard AXL API Access role.
d. [Recommended] Leave TLS verify mode switched On to ensure VCS verifies the node's certificates.
The Unified CM node presents its tomcat certificate for AXL and UDS queries, and its CallManager
certificate for subsequent SIP traffic. If the Unified CM server is using self-signed certificates, the
VCS Control's trusted CA list must include a copy of the tomcat certificate and the CallManager
certificate from every Unified CM server.
certificate for subsequent SIP traffic. If the Unified CM server is using self-signed certificates, the
VCS Control's trusted CA list must include a copy of the tomcat certificate and the CallManager
certificate from every Unified CM server.
e. [Optional] Select which deployment this node/cluster will belong to.
The Deployment field does not show if you have not created multiple deployments. All nodes belong
to the default deployment if you choose not to use multiple deployments.
to the default deployment if you choose not to use multiple deployments.
f. Click Add address.
If you enabled TLS verify mode, then the VCS tests whether a secure connection can be established.
It does this so you can find any TLS configuration errors before it continues the discovery process.
If the secure connection test was successful, or if you did not enable TLS verify mode, then the
It does this so you can find any TLS configuration errors before it continues the discovery process.
If the secure connection test was successful, or if you did not enable TLS verify mode, then the
Unified Communications Mobile and Remote Access via Cisco VCS Deployment Guide (X8.6)
Page 25 of 55
Configuring Mobile and Remote Access on VCS