Cisco Cisco TelePresence MCU 4510 Document
Deploying an MCU registered to Cisco TelePresence VCS
Cisco TelePresence MCU Deployment Guide
Page 17 of 32
Prefix/suffix
Range
Purpose
Dialing examples
H.323: 82812
SIP 812@mcu2.cisco.com or 82812@cisco.com
SIP 812@mcu2.cisco.com or 82812@cisco.com
Step 2: Configuring the Cisco VCS
The Cisco VCS Control should be deployed according to the recommendations of the Cisco VCS
Base configuration or the Unified CM with VCS deployment guide (both found at
http://www.cisco.com/en/US/partner/products/ps11337/products_installation_and_configuration_guide
s_list.html). Configuring the Cisco VCS ready for the MCU installation requires the following steps:
Base configuration or the Unified CM with VCS deployment guide (both found at
http://www.cisco.com/en/US/partner/products/ps11337/products_installation_and_configuration_guide
s_list.html). Configuring the Cisco VCS ready for the MCU installation requires the following steps:
1. Configuring the MCU SIP sub domain.
2. Creating an MCU SIP zone.
3. Configuring search rules.
4. Optional: Configuring Multiway.
Note: This section is here in order to configure SIP calls to reach the MCU. H.323 calling is handled
via H.323 prefixes (configured in a subsequent section within the MCU). The configuration for these
steps is described in the tables below.
via H.323 prefixes (configured in a subsequent section within the MCU). The configuration for these
steps is described in the tables below.
Configuring the MCU SIP domain
The MCU registers to the Cisco VCS using a sub-domain, e.g. mcu1.cisco.com. Therefore, the Cisco
VCS has to be configured with a SIP domain name that matches the MCU sub-domain; otherwise the
Cisco VCS rejects the SIP registration request from the MCU.
VCS has to be configured with a SIP domain name that matches the MCU sub-domain; otherwise the
Cisco VCS rejects the SIP registration request from the MCU.
Configure a SIP domain:
1. Go to VCS configuration > Protocols > SIP > Domains.
2. Click New.
3. Enter the domain name into the Name field:
Table 9: Settings for SIP domain
VCS Setting
Value
Comment
Name
MCU fully qualified domain
name (FQDN)
name (FQDN)
Example: mcu1.cisco.com or
mcu1.cisco.net
mcu1.cisco.net
4. Click Create domain.
Creating the MCU SIP zone
To provide the same call behavior for SIP as for H.323, configure the Cisco VCS with a SIP neighbor
zone pointing to the MCU. (When using H.323, the MCU registers a service prefix; the same does not
exist for SIP.) Configure the neighbor zone with a pattern match equal to the H.323 service prefix. To
allow ad hoc calls to the MCU using a URI (for example, <conference ID>@mcu1.cisco.com),
configure the SIP zone with a suffix match with the pattern string @mcu1.cisco.com.
zone pointing to the MCU. (When using H.323, the MCU registers a service prefix; the same does not
exist for SIP.) Configure the neighbor zone with a pattern match equal to the H.323 service prefix. To
allow ad hoc calls to the MCU using a URI (for example, <conference ID>@mcu1.cisco.com),
configure the SIP zone with a suffix match with the pattern string @mcu1.cisco.com.
This guide assumes that all video infrastructure devices that can be dialed use the 8 prefix according
to the address plan. The first MCU in a video network should then be assigned the service prefix 1,
thus giving the MCU prefix 81.
to the address plan. The first MCU in a video network should then be assigned the service prefix 1,
thus giving the MCU prefix 81.
Create a SIP zone on the VCS as follows:
1. Go to VCS configuration > Zones.
2. Click New.
3. Configure the fields on the VCS as follows:
Table 10: Settings for creating a SIP zone on a Cisco VCS
VCS Setting
Value
Comment