Cisco Cisco TelePresence Video Communication Server Expressway
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.
access is 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:
access calls have different component characteristics depending on whether the call is being viewed on the
VCS Control or VCS Expressway:
n
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.
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.
n
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.
separate calls.
Checking devices registered to Unified CM via VCS
Identifying devices in Unified CM
To identify devices registered to Unified CM via VCS:
1. In Unified CM, go to
Device > Phone
and click Find.
2. Check the IP Address column. Devices that are registered via VCS will display an IP Address of the
VCS Control it is registered through.
Identifying provisioned sessions in VCS Control
To identify sessions that have been provisioned via VCS Control:
1. In VCS Control, go to
Status > Unified Communications
.
2. In the
Advanced status information
section, click
View provisioning sessions
.
This shows a list of all current and recent (shown in red) provisioning sessions.
Ensuring that VCS Control is synchronized to Unified CM
Changes to Unified CM cluster or node configuration can lead to communication problems between Unified
CM and VCS Control. This includes changes to:
CM and VCS Control. This includes changes to:
n
the number of nodes within a Unified CM cluster
n
the host name or IP address of an existing node
n
listening port numbers
n
security parameters
n
phone security profiles
You must ensure that any such changes are reflected in the VCS Control. To do this you must rediscover all
Unified CM and IM & Presence nodes (on VCS go to
Unified CM and IM & Presence nodes (on VCS go to
Configuration > Unified Communications
).
VCS certificate / TLS connectivity issues
If the VCS's server certificate or trusted CA certificates have been modified, you must restart the VCS
before those changes will take effect.
before those changes will take effect.
Unified Communications Mobile and Remote Access via Cisco VCS Deployment Guide (X8.2)
Page 36 of 40
Appendix 1: Troubleshooting