Cisco Cisco TelePresence MCU 4510 Installation Guide
Summary of procedure
The process consists of:
1. Designing the dial plan.
2. Configuring zones and a domain in the Cisco VCS for the MCU.
3. Installing and configuring the MCU.
4. Configuring Cisco TMS for management and scheduling of the MCU.
Configuration Tasks
Task 1: Dial plan
The dial plan of a video deployment should be considered early on to ensure that a scalable easy-to-use
solution is deployed. This dial plan is a conceptual one that is not defined in any one place but on a variety of
systems: therefore it is important to follow the same guidelines throughout a deployment. Recommendations
that fulfill these core requirements are provided; however some deployments may have specific requirements
that require a different implementation.
solution is deployed. This dial plan is a conceptual one that is not defined in any one place but on a variety of
systems: therefore it is important to follow the same guidelines throughout a deployment. Recommendations
that fulfill these core requirements are provided; however some deployments may have specific requirements
that require a different implementation.
Each conference has a numeric identifier. When a conference is booked using Cisco TMS, Cisco TMS uses
a pre-configured number range to create the conference. This registers numeric identifiers on the Cisco VCS,
so that participants can dial into the conference. For a scheduled conference, Cisco TMS can configure the
MCU to initiate calls to the participants (through the Cisco VCS); this is most commonly done as a dial out
call from the MCU to the endpoint.
a pre-configured number range to create the conference. This registers numeric identifiers on the Cisco VCS,
so that participants can dial into the conference. For a scheduled conference, Cisco TMS can configure the
MCU to initiate calls to the participants (through the Cisco VCS); this is most commonly done as a dial out
call from the MCU to the endpoint.
All the conferences running on a specific MCU can be addressed using a number with a prefix assigned from
the address plan, for example: 81xxx, where 8 is the reserved prefix for data centre resources and 1 is the
prefix for a specific MCU. The same conference can also be reached using a Unified Resource Identifier
(URI), for example, xxx@mcu1.cisco.com, both on SIP and H.323 (interworked) signaling protocols. (It is
also possible to register multiple MCUs using the same prefix in order to provide load balancing for non-
scheduled MCU conferences.)
the address plan, for example: 81xxx, where 8 is the reserved prefix for data centre resources and 1 is the
prefix for a specific MCU. The same conference can also be reached using a Unified Resource Identifier
(URI), for example, xxx@mcu1.cisco.com, both on SIP and H.323 (interworked) signaling protocols. (It is
also possible to register multiple MCUs using the same prefix in order to provide load balancing for non-
scheduled MCU conferences.)
Using a prefix allows a simplified dial plan where users need only dial <prefix><conference
number>@domain, whether using SIP or H.323.
number>@domain, whether using SIP or H.323.
The table below shows an example of an address plan for conferencing services. The range allocated to ad
hoc and permanent conferences can be divided as required. In both cases, a conference address can be
used across multiple sessions; for example, 81555 can be used for a specific team’s shared meetings. Pre-
registering a conference allows persistent tailoring of layouts/settings across sessions.
hoc and permanent conferences can be divided as required. In both cases, a conference address can be
used across multiple sessions; for example, 81555 can be used for a specific team’s shared meetings. Pre-
registering a conference allows persistent tailoring of layouts/settings across sessions.
Cisco TelePresence MCU Deployment Guide 4.4
Page 19 of 53
Deploying an MCU registered to Cisco VCS