Cisco Cisco TelePresence Video Communication Server Expressway
Date
Change
Reason
April 2010
Updated for VCS X5.1. Added additional troubleshooting information.
January
2010
2010
Initial release.
Table 1 Deployment Guide Change History (continued)
Introduction
This deployment guide provides guidelines on how to configure the Cisco TelePresence Video Communication Server
(VCS) version X8.8 and Cisco Unified Communications Manager (Unified CM) versions 8.6.x and later to interwork via
a SIP trunk.
(VCS) version X8.8 and Cisco Unified Communications Manager (Unified CM) versions 8.6.x and later to interwork via
a SIP trunk.
Deployment Scenario
A company already has Unified CM running their telephone/video system. They want to integrate this with a VCS
Control which connects their existing (or new) video conferencing systems, so that voice and video terminals can
communicate with one another across one unified network.
Control which connects their existing (or new) video conferencing systems, so that voice and video terminals can
communicate with one another across one unified network.
The existing telephone system uses telephone (digit-only) numbers to specify who to call. This functionality is to be
extended into the video system, so that all endpoints will be contactable by telephone numbers.
extended into the video system, so that all endpoints will be contactable by telephone numbers.
For the purposes of this example, endpoints connected to the Unified CM are identified by 3xxx extension numbers
and endpoints connected to the VCS Control are identified by 4xxx extension numbers. (Note that more complicated
dial plans can also be supported, including alphanumeric dialing; they would require additional transforms/routing
configuration).
and endpoints connected to the VCS Control are identified by 4xxx extension numbers. (Note that more complicated
dial plans can also be supported, including alphanumeric dialing; they would require additional transforms/routing
configuration).
Unified CM and the VCS Control are connected together using a SIP trunk across an IP network; the VCS Control
domain is vcs.domain. Calls sent to Unified CM will have the domain portion set to the VCS domain; calls from Unified
CM to VCS will arrive with the domain portion set as <FQDN of VCS>:5060 for TCP and <FQDN of VCS>:5061 for TLS.
domain is vcs.domain. Calls sent to Unified CM will have the domain portion set to the VCS domain; calls from Unified
CM to VCS will arrive with the domain portion set as <FQDN of VCS>:5060 for TCP and <FQDN of VCS>:5061 for TLS.
It is assumed that the VCS Control is running version X7 or later code and has at least the following option keys
installed:
installed:
■
Traversal calls
■
Non-traversal calls
Summary of Configuration Process
This document specifies how to configure both the Unified CM and the VCS Control so that calls can be made:
6
Cisco VCS SIP Trunk to Unified CM Deployment Guide
Introduction