Cisco Video Communications Server Release 9.0(1)
Applicable to UC System Release 9.0(1)
This page provides a reference configuration for Cisco TelePresence Video Communication Server (Cisco VCS) integrated with the Cisco Unified Communications deployment. The configuration information is based primarily on testing performed on Cisco Unified Communications system release test beds with Cisco VCS.
IP Phones and the various videophones like the Cisco 9900 series phones, the Cisco IP Video Phone E20 (E20), the Cisco TelePresence System EX series and their deployments in a Cisco Unified Communications Manager (Unified CM) environment are not only capable of communicating with voice but also video. Video is widely used with the advent of High Definition TV and many online services through the Internet. Enterprises deploying Video within their networks often have Voice over IP systems deployed to provide Voice services. The main focus of this article is on integration of Cisco TelePresence Video Communication Server (VCS) Video networks with Cisco Unified Communications Manager (Unified CM), providing an optimum video experience for Enterprise users.
The intended audiences for this article are system administrators and implementers who are planning to integrate Cisco VCS with the Cisco Unified Communications deployment. Also, it is intended for those who want to deploy Cisco Video IP phones and endpoints with Cisco Unified Communications Manager systems interworking with Cisco VCS in their Unified Communications environment. TIP: Use <Use Video Communication Server, Cisco VCS> as a keyword to search for related test cases in System Test Results System Test Results for IP Telephony.
This topic does not contain detailed step-by-step procedures; for detailed information about configuring Cisco VCS, refer to the Cisco VCS Deployment Guide documentation.
This section provides the functionality of the Cisco VCS when integrated with the Cisco Unified Communications deployments. Also, it discusses the design criteria that should be considered for deploying videophones with Cisco Unified Communications Server, and best practices for interworking these Cisco Unified Communications systems with Cisco VCS. The Cisco IP Video Phone E20 (E20) and Cisco TelePresence System EX series are popular devices for Enterprise Video telephony along with the 9900 series phones.
When deploying Cisco Video phones in a network with Cisco Unified Communications Manager and Cisco VCS, consider the following design recommendations:
- Configure Cisco IP Video Phone E20 as a native phone on the Cisco Unified Communications Manager.
- Register the Cisco TelePresence System EX series endpoints to the Cisco VCS.
- Manage the dial-plan for the devices registered to Cisco Unified Communications Manager.
- Use dn@domain-name for URI in the Cisco VCS.
- Register the deployments that need secure video calls to Cisco IP Video Phone E20 with Cisco VCS.
- When Email Address is used as URI with the Cisco VCS, transform Email Address to DN for calls to Cisco Unified Communications Manager.
- If number normalization for Email Address to number is desired, perform it on Cisco VCS with FindMe functionality, for both outgoing and incoming calls.
- Dial-plan should be in contiguous blocks for Video endpoints across the trunk to simplify call routing.
- Configure a SIP trunk from the Cisco Unified Communications Manager to the Cisco VCS with Presence, Out-of-dialog REFER, and unsolicited notify enabled on the SIP trunk profile.
- Use TCP or TCP UDP for the Trunk Transport type.
- Configure the Cisco VCS zones with Cisco Unified Communications Manager zone profile as neighbor with TCP to SIP 5060 port.
- Use Cisco Unified Communications Manager route groups to provide trunk redundancy to all servers in the cluster.
- Enable "run on all servers" on the Cisco Unified Communications Manager for the route lists and trunks to optimize calls processing.
- Use multiple Cisco VCS search rules with different priorities to provide neighbor redundancy to all servers in the cluster.
- If interworking is needed for SIP to H.323 calls, then the interworking is done through the Cisco VCS.
- Use SIP trunk to connect Multipoint Control Units as scheduled conference bridges with the Cisco Unified Communications Manager.
- Use Diffserv marking for QoS on Cisco IP Video Phone E20 and EX series. Configure the audio and video and signaling as per the enterprise QoS policy.
- Configure WAN bandwidth based on the highest desired resolution for video calls.
For information on Cisco VCS specific deployments and sites where system testing was performed, see Tested Deployments and Site Models for IP telephony at: TIS Modules.
This section provides information about Cisco TelePresence Video Communication Server (Cisco VCS) deployment scenario and call flows. Various call control components including Cisco Unified Communications Manager, the Cisco 9900 series phones, the Cisco IP Video Phone E20, the Cisco TelePresence System EX series and their deployments in a Cisco Unified Communications Manager environment, integrated with Cisco VCS networks are tested to verify the ability to provide an optimum video experience for Enterprise users.
One of the main points of consideration while interworking the videophones and other components of the Unified Communication System with Cisco VCS is to decide the call control type that is better suited for the type of phone under consideration. The features considered for this endpoint registration include Cisco TelePresence Movi client, Cisco Unified IP Phone 79xx, 99xx series phone registration, Cisco IP Video Phone E20 registration, Cisco EX series endpoints registration, On-board conference bridge for Video, phone administration, and single administration control.
The video endpoints deployed in a Cisco TelePresence Video Communication Server integrated with Unified Communication systems is designed to support functionalities such as:
- Ad Hoc conferencing
- Supplementary services (Hold, Transfer, Resume)
- Softkey support
- NAT traversal
- H.239 (H.323 based additional media channel for desktop sharing)
- H.235 (H.323 based encryption token passing)
- Binary Floor Control Protocol (SIP based additional media channel for desktop sharing)
- SRTP support for audio and video, multiple line, shared line
- Single Number Reach (SNR)
- Survivable Remote Site Telephony
- Call bandwidth
During Cisco Unified Communications Solution Integration testing for Cisco VCS integrated with Unified CM, features and functionalities tested include identifying call agent capabilities and types based on dial-plan, choosing video call resolutions and bandwidths, the ability to support voicemail, conferencing, dual-tone multi-frequency signaling, and Unified CM trunks. Redundancy, SRST, and Failover are some of the other functionalities tested, apart from support for supplementary services such as call hold, resume, and transfer.
During Cisco Unified Communications 9.0(1) release system testing, the Cisco VCS deployment and testing scenarios covered inter-working with Unified 9900 series IP Phones, Cisco IP Video Phone E20 series, other video endpoints and SIP trunks terminating on a Unified Communications Manager cluster. The Cisco VCS is deployed in a medium site model, consisting of one centralized site with three Survivable Remote Site Telephony remote sites called Geneva (GVA).
Figure 1: Cisco Unified CM VCS Configuration
In Figure 1, the Cisco Unified Communications Manager cluster serves 2000 phones. The Cisco Unified Communications Manager cluster connects to the rest of the network through MPLS WAN networks. It consists of one centralized site with three SRST remote sites. The Cisco VCS is deployed in the GVA VCS cluster and consists of Cisco TelePresence Server, Conference conductor, Cisco C40 and C20 endpoints.
A local Cisco Unity Connection provides voice messaging services for local PBX and Cisco Unified Communications Manager users. Access to the PSTN for normal off-net calls is provided by five E1 RTSI PRI links to the PSTN. Access to other sites and to services such as Cisco Unified MeetingPlace Express is provided by H.323 gatekeeper controlled trunks and an IP-to-IP gateway. Access to the SIP network is through a SIP trunk to a remotely located Cisco Unified SIP Proxy (Unified SIP Proxy). Third-party operator consoles are provided on Cisco Unified Communications Manager to serve local phones and to provide backup to the operator console.
The Cisco Unified Communications Manager cluster in this deployment model is designed for redundancy and system scaling. Some of the other design characteristics of this deployment model include inline power to IP phones, SIP and SCCP phones, Quality of service from the desktop, locally connected third-party applications for attendant console, billing, and voice recording, Cisco Unified Communications Integration™ for Microsoft Office Communicator with Microsoft OCS 2007 R2 version with Microsoft Office Communicator clients, Cisco Unified Personal Communicator, Cisco IME server to transport all Cisco IME calls over Cisco IME SIP trunks. Testing is done on all call flows between central site to central site, central site to remote site and remote site to remote site.
For more information on Cisco VCS tested functionality, see System Test Results for IP telephony.
You can see the Cisco VCS test results in Tested Feature column “Video” grouped under Unified Communications Manager test results.
Call Flow Diagram
This section provides example call flows for Cisco VCS inter-worked with the Cisco Unified Communications Manager.
Figure 2: Cisco Unified 9900 Series Phone Call Flow
Figure 3: Cisco Unified Personal Communicator Call Flow
Figure 4: Cisco Unified Communications Manager Call Flow
This section provides the high-level tasks and related information for configuring a Cisco VCS deployment inter-worked with Cisco Unified Communications Manager. Default and recommended values specified in the product documentation were used during system testing, except as noted.
Configuration Tasks: List of high-level configuration tasks.
System Test Specifics: System test variations from default values documented in the product documentation.
More Information: Links to product documentation for detailed configuration information related to the high-level tasks.
Note: Default and recommended values specified in the product documentation were used during system testing, unless otherwise noted in the System Test Specifics column.
Table 1: Cisco VCS setup and configuration in Unified Communications Manager Deployment
|Configuration Tasks||System Test Specifics||More Information|
|1. Enabling calls between endpoints registered on Cisco VCS Control||See Cisco Unified Communications Manager with Cisco VCS Deployment Guide|
|2. Enabling calls between endpoints registered on Cisco Unified Communications Manager||See Cisco Unified Communications Manager with Cisco VCS Deployment Guide|
|3. Enabling endpoints registered on Cisco VCS Control to call endpoints registered on Cisco Unified Communications Manager||See Cisco Unified Communications Manager with Cisco VCS Deployment Guide|
|4. Advanced Configurations||See Cisco Unified Communications Manager with Cisco VCS Deployment Guide|
For related information about Cisco VCS deployment, see Cisco Unified Communications Manager Documentation at:
For information on the results obtained from the system testing, see Cisco System Test Results for IP Telephony Release 9.0(1).