This topic provides an overview of how IP Video Telephony was configured for Cisco IP
Communications Release 5.1(1) testing. This topic does not include detailed installation and
configuration instructions. Rather, it is intended to provide you with guidance and serve as a reference
as you set up video devices in your IP telephony solution.
For additional information and guidelines for implementing Cisco IP Video Telephony, refer to the
documents listed Table 12-1. You can also refer to documentation provided by the vendors of Tandberg
video endpoints and Polycom video endpoints.
Table 12-1IP Video Telephony Related Documentation
DocumentReference
Cisco Unified CallManager System Guide
“Understanding Video Telephony” chapter
IP Video Telephony Solution Reference
Network Design (SRND) for
Cisco Unified CallManager
Cisco UnifiedVideoconferencing3500 Series
video conferencing products documentation
Cisco Unified Video Advantage
documentation
Deploying Video Telephonyhttp://cco/en/US/partner/about/ac123/ac114/ac173/
NoteCisco Unified CallManager 5.1 supports security on the Cisco Unified IP Phone 7940G/7941G/7960G/
Call Routing
OL-11591-01
7961G/ 7970G/7971G running SCCP. These phone models also have video capabilities when associated
with Cisco Unified Video Advantage. If two secure video-capable endpoints call each other, the SCCP
signaling and audio media path will be encrypted. Video will work, however signaling and the video
media path to Cisco Unified Video Advantage will not be encrypted.
The IP Video Telephony deployment supports the following call routings. SCCP endpoints include
SCCP Tandberg T1000, and Cisco Unified Video Advantage associated with Cisco IP Phone models
7940G/7960G/7970G. H.323 endpoints include H.323 Tandberg T1000 and Polycom VSX 7000.
The call routing for video calls functions just as the call routing for audio calls. For more information,
refer to the “Understanding Video Telephony” chapter in Cisco Unified CallManager System Guide.
Cisco Unified CallManager supports the Dynamic H.323 Addressing call routing feature. This feature
allowsH.323 endpoints with DHCP addressing to remain registered to a Gatekeeper while Cisco Unified
CallManager controls call routing. For more information, refer to the “Understanding VideoTelephony”
section in Cisco Unified CallManager System Guide. (Table 12-1 provides a link to this document.)
Gatekeeper Configuration for IP Video Telephony
Gatekeeper Configuration for IP Video Telephony
The following sections provide a general description of how gatekeepers were configured for IP Video
Telephony:
• Gatekeeper Configuration Overview, page 12-7
• Gatekeeper Call Routing, page 12-9
Gatekeeper Configuration Overview
Gatekeepers were configured in pairs to create gatekeeper clusters that provide gatekeeper-based Call
Admission Control and call routing redundancy. The endpoints must provide alternate gatekeeper
registration so that the endpoints can utilize both gatekeepers in the cluster.
Three local gatekeeper zones were created, one for Cisco Unified CallManager, one for Cisco Unified
VideoconferencingMCUs,and one for the H.323 endpoints. Zones for Cisco Unified Videoconferencing
MCUs and H.323 endpoints were configured with Invia and Outvia parameters. This configuration
allows gatekeepers to route incoming and outgoing calls to and from these zones to
Cisco Unified CallManager.
The Send Product ID And VersionID Cisco Unified CallManager service parameter must be set to True
to allow the Dynamic H.323 Addressing feature to work and to allow the gatekeeper to route incoming
or outgoing calls to the Cisco Unified CallManager in a given zone.
After the Cisco Unified CallManager service parameter Send Product ID And Version ID is set to True,
the endpoint type of Cisco Unified CallManager H.225 trunks will change to H323-GW.
The following partial output from the Show Gatekeeper Endpoints command shows a single
Cisco Unified CallManager H.225 trunk that is registered to a gatekeeper:
SJC-RFD-GK-1#show gatekeeper endpoints
GATEKEEPER ENDPOINT REGISTRATION
OL-11591-01
System Test Architecture Reference Manual for IP Telephony
12-7
Gatekeeper Configuration for IP Video Telephony
CallSignalAddr Port RASSignalAddrPort Zone NameTypeFlags
Zone prefixes were configured in the Cisco Unified CallManager zone for intercluster call flows. This
configuration is required for intercluster gatekeeper-controlled call routing. The other two zones do not
require a local zone prefix to be configured. The endpoints and MCUs are directed to these zones by the
Zone Subnet command in the gatekeeper configuration.
The Cisco Unified CallManager cluster uses the default technology prefix 1#* to register its
gatekeeper-controlled intercluster trunks in the Cisco Unified CallManager zone. Then,
Cisco Unified CallManager cluster registers a dedicated H.225 gatekeeper-controlled trunk to the MCU
zone. The trunk and the MCU zone are used for invites initiated from the MCU Conference control web
pages. Finally, the Cisco Unified CallManager cluster registers a special trunk called RasAggregator to
the H.323 endpoints zone. This trunk is dynamically created and registered as a result of the H.323
endpoints device pool configuration in Cisco Unified CallManager.
The following partial output from the Show Gatekeeper Endpoints command shows a single
Cisco Unified CallManager RasAggregator trunk that is registered to a gatekeeper:
SJC-RFD-GK-1#show gatekeeper endpoints
CallSignalAddr Port RASSignalAddrPort Zone NameType
A single RasAggregator trunk was created for all gatekeeper-controlled H.323 endpoints that share the
same gatekeeper zone and Cisco UnifiedCallManager group. All gatekeeper-controlledH.323 endpoints
within the same gatekeeper endpoint zone must be configured as part of the same Cisco Unified
CallManager group and device pool, otherwise Cisco Unified CallManager will register multiple
RasAggregator trunks to a single gatekeeper endpoint zone. In this situation, some incoming calls from
the H.323 endpoints will fail.
NoteThis configuration prevents gatekeeper-controlled H.323 endpoints from being load balanced across
multiple Cisco Unified CallManager servers by using device pools and Cisco Unified CallManager
groups. One way to accomplish such load balancing is to create multiple gatekeeper zones dedicated to
H.323 endpoints for each device pool or Cisco Unified CallManager group.
For an example of a video gatekeeper configuration, see the >>>>>>>
12-8
System Test Architecture Reference Manual for IP Telephony
OL-11591-01
Chapter 12 IP Video Telephony Configuration
Gatekeeper Call Routing
Calls are routed through the gatekeeper as follows:
• Inbound call to Cisco Unified CallManager zone from other gatekeepers—Routed to the registered
Cisco Unified CallManager Gatekeeper-controlled H.225 intercluster trunks within the Cisco
Unified CallManager zone in a Round Robin distribution algorithm using the Default Technology
prefix.
• Outbound call from Cisco Unified CallManager zone to other gatekeepers—Normal gatekeeper call
routing using location request.
• Inbound Call to MCU zone from other gatekeepers—Routed out to the registered Cisco Unified
CallManager gatekeeper-controlled H.225 intercluster trunks within the Cisco UnifiedCallManager
zone in a round robin distribution algorithm using the Default Technology prefix. Then routed by
Cisco Unified CallManager directly to the MCU via its H.323 gateway.
• Outbound call from MCU—Routed to Cisco Unified CallManager via the MCU dedicated H.225
gatekeeper-controlled trunks that are registered to the MCU zone.
• Outbound call from H.323 endpoints—Routed to Cisco Unified CallManager via RasAggregator
H.225 trunk.
• Inbound call from other Gatekeepers to H.323 endpoints—Call is first routed out the Registered
Cisco Unified CallManager gatekeeper-controlled H.225 trunk within the Cisco Unified
CallManager zone in a round robin distribution algorithm using the Default Technology prefix. It is
then routed back to the gatekeeper video endpoint zone via the RasAggregator trunk.
• Inbound call from MCUs to H.323 endpoints—Call is first routed to Cisco Unified CallManager via
the MCU dedicated H.225 gatekeeper-controlled trunks that are registered to the MCU zone. It is
then routed back to the Gatekeeper Video endpoint zone via the RasAggregator trunk.
• Inbound call from Cisco Unified Videoconferencing gateway—Call is routed to the registered
Cisco Unified CallManager gatekeeper. The gatekeeper receives an admission request from the
Cisco Unified Videoconferencinggateway, and the gatekeeper replies with an admission confirm to
send the call to Cisco Unified CallManager via the RasAggregator trunk.
Cisco Unified Videoconferencing 3540 MCU Conference Bridge Configuration for IP Video Telephony
Cisco Unified Videoconferencing 3540 MCU Conference Bridge
Configuration for IP Video Telephony
This section provides basic information about configuring the Cisco Unified Videoconferencing 3540
for IP video telephony.
For related information, refer to Administrator's Guide for Cisco Unified Videoconferencing 3511 MCUand Cisco Unified Videoconferencing 3540 MCU Module Releases, which are available at this URL: