Cisco Cisco TelePresence Video Communication Server Expressway
■
IOS: Trust store
■
Android: Location & Security settings
Jabber client configuration details for mobile and remote access is contained within the relevant installation and
configuration for that Jabber client:
configuration for that Jabber client:
■
■
■
■
DNS Records
This section summarizes the public (external) and local (internal) DNS requirements. For more information, see the
Cisco Jabber Planning Guide (for your version) on the
Cisco Jabber Planning Guide (for your version) on the
Public DNS
The public (external) DNS must be configured with
_collab-edge._tls.<domain>
SRV records so that endpoints can
discover the VCS Expressways to use for mobile and remote access. SIP service records are also required (for
general deployment, not specifically for mobile and remote access). For example, for a cluster of 2 VCS Expressway
systems:
general deployment, not specifically for mobile and remote access). For example, for a cluster of 2 VCS Expressway
systems:
Domain
Service
Protocol
Priority
Weight
Port
Target host
example.com
collab-edge
tls
10
10
8443
vcse1.example.com
example.com
collab-edge
tls
10
10
8443
vcse2.example.com
example.com
sips
tcp
10
10
5061
vcse1.example.com
example.com
sips
tcp
10
10
5061
vcse2.example.com
Local DNS
The local (internal) DNS requires
_cisco-uds._tcp.<domain>
SRV records. For example:
Domain
Service
Protocol
Priority
Weight
Port
Target host
example.com
cisco-uds
tcp
10
10
8443
cucmserver1.example.com
example.com
cisco-uds
tcp
10
10
8443
cucmserver2.example.com
Notes:
■
Ensure that the
cisco-uds
SRV records are NOT resolvable outside of the internal network, otherwise the
Jabber client will not start mobile and remote access negotiation via the VCS Expressway.
■
You must create internal DNS records, for both forward and reverse lookups, for all Unified Communications
nodes used with Mobile and Remote Access. This allows VCS Control to find the nodes when IP addresses or
hostnames are used instead of FQDNs.
nodes used with Mobile and Remote Access. This allows VCS Control to find the nodes when IP addresses or
hostnames are used instead of FQDNs.
Firewall
■
Ensure that the relevant ports have been configured on your firewalls between your internal network (where
the VCS Control is located) and the DMZ (where the VCS Expressway is located) and between the DMZ and
the public internet. See
the VCS Control is located) and the DMZ (where the VCS Expressway is located) and between the DMZ and
the public internet. See
for more information.
9
Mobile and Remote Access Through Cisco Video Communication Server Deployment Guide
Configuration Overview