Cisco Cisco TelePresence Video Communication Server Expressway
Introduction
Cisco VCS Deployment Guide: CUCM v6.1, 7 and 8 with Cisco VCS X6 using a SIP trunk
Page 6 of 49
Introduction
Objectives and intended audience
This deployment guide provides guidelines on how to configure the Cisco TelePresence Video
Communication Server (Cisco VCS) version X6 and Cisco Unified Communications Manager (CUCM)
versions 6.1, 7 or 8 to interwork via a SIP trunk.
Communication Server (Cisco VCS) version X6 and Cisco Unified Communications Manager (CUCM)
versions 6.1, 7 or 8 to interwork via a SIP trunk.
Other ways that Cisco VCS and CUCM can be connected to allow them to interwork include:
use of an H.323 trunk
configuring CUCM to register to the Cisco VCS as a gateway (typically used with CUCM version
4.1 and earlier)
4.1 and earlier)
Deployment scenario
A company already has CUCM running their telephone system. They want to integrate this with a
Cisco 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.
Cisco 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.
The existing telephone system uses telephone 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.
be 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 CUCM are identified by their extension
numbers 3xxx and endpoints connected to the Cisco VCS Control are identified by telephone
numbers 01189 124 xxx. 4-digit extension number dialing and full 11-digit dialing of endpoints
registered to the Cisco VCS Control are supported.
numbers 3xxx and endpoints connected to the Cisco VCS Control are identified by telephone
numbers 01189 124 xxx. 4-digit extension number dialing and full 11-digit dialing of endpoints
registered to the Cisco VCS Control are supported.
CUCM and the Cisco VCS Control are connected together using a SIP trunk across an IP network; the
Cisco VCS Control domain is vcs.domain. Calls sent to CUCM need the domain portion to be
<ip address of cucm>; calls from CUCM to Cisco VCS will arrive with the domain portion set as
<ip address of vcs>:5060
Cisco VCS Control domain is vcs.domain. Calls sent to CUCM need the domain portion to be
<ip address of cucm>; calls from CUCM to Cisco VCS will arrive with the domain portion set as
<ip address of vcs>:5060
It is assumed that the Cisco VCS Control is running version X6 or later code and has at least the
following option keys installed:
following option keys installed:
H323-SIP interworking
Traversal calls
Non-traversal calls
It is assumed that CUCM is running IOS v6.1, 7 or 8.