Cisco Cisco TelePresence Video Communication Server Expressway
VCS Control will verify the CallManager certificate for subsequent SIP communications. Each zone is
created with a name in the format 'CEtcp-<node name>' or 'CEtls-<node name>'.
created with a name in the format 'CEtcp-<node name>' or 'CEtls-<node name>'.
A non-configurable search rule, following the same naming convention, is also created automatically for each
zone. The rules are created with a priority of 45. If the Unified CM node that is targeted by the search rule has
a long name, the search rule will use a regex for its address pattern match.
zone. The rules are created with a priority of 45. If the Unified CM node that is targeted by the search rule has
a long name, the search rule will use a regex for its address pattern match.
Note that load balancing is managed by Unified CM when it passes routing information back to the registering
endpoints.
endpoints.
Why should I refresh the discovered nodes?
When the VCS Control "discovers" a Unified Communications node, it establishes a connection to read the
information required to create zones and search rules to proxy requests originating from outside of the
network in towards that node.
information required to create zones and search rules to proxy requests originating from outside of the
network in towards that node.
This configuration information is static. That is, the VCS only reads it when you manually initiate
discovery of a new node, or when you refresh the configuration of previously discovered nodes. If any related
configuration has changed on a node after you discover it, the mismatch between the new configuration and
what the VCS Control knows of that node will probably cause some kind of failure.
discovery of a new node, or when you refresh the configuration of previously discovered nodes. If any related
configuration has changed on a node after you discover it, the mismatch between the new configuration and
what the VCS Control knows of that node will probably cause some kind of failure.
The information that the VCS Control reads from the Unified Communications node is different for each node
type and its role. The following list contains examples of UC configuration that you can expect to require a
refresh from the VCS. The list is not exhaustive; if you suspect that a configuration change on a node is
affecting MRA services, you should refresh those nodes to eliminate one known source of potential
problems.
type and its role. The following list contains examples of UC configuration that you can expect to require a
refresh from the VCS. The list is not exhaustive; if you suspect that a configuration change on a node is
affecting MRA services, you should refresh those nodes to eliminate one known source of potential
problems.
n
Changing cluster (e.g. adding or removing a node)
n
Changing security parameters (e.g. Enabling Mixed Mode)
n
Changing connection sockets (e.g. SIP port configuration)
n
Changing TFTP server configuration
n
Upgrading the software on the node
Configuring the HTTP server allow list (whitelist) on VCS
Control
Control
Jabber client endpoints may need to access additional web services inside the enterprise. This requires an
"allow list" of servers to be configured to which the VCS will grant access for HTTP traffic originating from
outside the enterprise.
"allow list" of servers to be configured to which the VCS will grant access for HTTP traffic originating from
outside the enterprise.
The features and services that may be required, and would need whitelisting, include:
n
Visual Voicemail
n
Jabber Update Server
n
Custom HTML tabs / icons
n
Directory Photo Host
n
Advanced File Transfer (AFT)
n
Problem Report Tool server
Unified Communications Mobile and Remote Access via Cisco VCS Deployment Guide (X8.5.3)
Page 26 of 54
Configuring mobile and remote access on VCS