Cisco Cisco TelePresence Video Communication Server Expressway
Note that performing the DNS lookup from the VCS Control will return the view from within the enterprise, and that
performing it on the VCS Expressway will return what is visible from within the DMZ which is not necessarily the same
set of records available to endpoints in the public internet.
performing it on the VCS Expressway will return what is visible from within the DMZ which is not necessarily the same
set of records available to endpoints in the public internet.
The DNS lookup includes the following SRV services that are used for Unified Communications:
■
_collab-edge._tls
■
_cisco-uds._tcp
Note:
the following SRV records may be queried by the lookup tool or the client, but they are not required. You can
ignore name errors related to these:
■
_cisco-phone-tftp._tcp
■
_cisco-phone-http._tcp
■
_cuplogin._tcp
Checking Reachability of the VCS Expressway
Ensure that the FQDN of the VCS Expressway is resolvable in public DNS.
The FQDN is configured at System > DNS and is built as <System host name>.<Domain name>.
Checking Call Status
Call status information can be displayed for both current and completed calls:
■
Current calls: the Call status page (Status > Calls > Calls) lists all the calls currently taking place to or from
devices registered with the VCS, or that are passing through the VCS.
devices registered with the VCS, or that are passing through the VCS.
■
Completed calls: the Call history page (Status > Calls > History) lists all the calls that are no longer active.
The list is limited to the most recent 500 calls, and only includes calls that have taken place since the VCS
was last restarted.
The list is limited to the most recent 500 calls, and only includes calls that have taken place since the VCS
was last restarted.
The same set of call status information is also shown on the Calls by registration page (accessed via the
Registration details page).
Registration details page).
If the VCS is part of a cluster, all calls that apply to any peer in the cluster are shown, although the list is limited to the
most recent 500 calls per peer.
most recent 500 calls per peer.
Identifying mobile and remote access calls
The call status and call history pages show all call types: Unified CM remote sessions (if mobile and remote access is
enabled) as well as VCS traversal and non-traversal calls.
enabled) as well as VCS traversal and non-traversal calls.
To distinguish between the call types you must drill down into the call components. Mobile and remote access calls
have different component characteristics depending on whether the call is being viewed on the VCS Control or VCS
Expressway:
have different component characteristics depending on whether the call is being viewed on the VCS Control or VCS
Expressway:
■
On a VCS-C, a Unified CM remote session will have 3 components (as it uses the B2BUA to enforce media
encryption). One of the VCS components will route the call through one of the automatically generated
neighbor zones (with a name prefixed by either CEtcp or CEtls) between VCS and Unified CM.
encryption). One of the VCS components will route the call through one of the automatically generated
neighbor zones (with a name prefixed by either CEtcp or CEtls) between VCS and Unified CM.
■
On a VCS-E, there will be one component and that will route the call through the CollaborationEdgeZone.
Note that if both endpoints are outside of the enterprise (i.e. off premises), you will see this treated as 2 separate
calls.
calls.
Checking Devices Registered to Unified CM via VCS
Identifying devices in Unified CM
To identify devices registered to Unified CM via VCS:
43
Mobile and Remote Access Through Cisco Video Communication Server Deployment Guide
Appendix 1: Troubleshooting