|
|
This appendix describes how to ensure that the Cisco IP/VC 3510 MCU and the embedded gatekeeper register with the Cisco Multimedia Conference Manager (MCM) gatekeeper. Topics include:
The intent of this appendix is to provide the basic MCM configuration steps to ensure that the Cisco IP/VC 3510 MCU can register with the MCM and the basic steps required to ensure that users in the MCM zone can contact users in the embedded gatekeeper zone when zone prefixes are used. Refer to the Multimedia Conference Manager publication for complete instructions on how to install, configure, and use the Cisco MCM.
The Cisco IP/VC3510 MCU must register with a gatekeeper on the network. The Cisco IP/VC3510 MCU version 2 unit can automatically register with H.323 version 2 gatekeepers. This section describes how to create a local MCM zone so that the MCM gatekeeper can recognize the MCU.
The following items are required to register the MCU with the MCM gatekeeper:
If you have not already done so, you must create a local zone on which endpoints, including the gatekeeper, can register.
To create a local zone, perform the following steps:
Step 2 At the prompt, enter
enable
Press Enter.
Step 3 At the Password prompt, enter
Enable password
Step 4 At the prompt, enter
GK#: configure terminal
Press Enter.
Step 5 At the prompt, enter
Press Enter.
Step 6 At the prompt, enter
GK (config-gk) #: zone local gatekeeper-name IP_address
Press Enter.
Where:
gatekeeper-name is the name you assign to the MCM gatekeeper.
IP_address is the IP address assigned to the MCM unit.
Step 7 At the prompt, enter
GK (config-gk) #: zone prefix gatekeeper-name prefix-value.
Where:
prefix-value is the zone prefix assigned to the specified gatekeeper.
Step 8 At the prompt, enter
GK (config-gk) #: no shutdown
Step 9 Press Ctrl-Z to exit configuration mode.
Step 10 To save the configuration to memory, at the prompt, enter
copy running-config startup-config
When the default gatekeeper parameter is set for the MCU, the MCU periodically updates its registration with the specified gatekeeper. After you have created a local zone, you can verify that the MCU has registered its services with the MCM gatekeeper. To verify that MCU has registered with the gatekeeper, perform the following steps:
Step 2 At the prompt, enter
enable
Press Enter.
Step 3 At the Password prompt, enter
Enable password
Step 4 At the prompt, enter
Step 5 At the prompt, enter
In environments where multiple zones are defined, you must register the embedded gatekeeper zone prefix with the MCM if you want the users in the MCM zone to be able to initiate interzone calls with users in the embedded gatekeeper zone. This section describes how to register the embedded gatekeeper zone prefix with the MCM.
The following items are required to register the embedded gatekeeper zone prefix with the MCM gatekeeper:
To register the embedded gatekeeper zone prefix with the MCM, perform the following steps:
Step 2 At the prompt, enter
enable
Press Enter.
Step 3 At the Password prompt, enter
Enable password
Step 4 At the prompt, enter
GK#: configure terminal
Press Enter.
Step 5 At the prompt, enter
Press Enter.
Step 6 At the prompt, enter
GK (config-gk) #: zone remote gatekeeper-name domain name IP_address
Press Enter.
Where:
gatekeeper-name is the name you assign to the embedded gatekeeper.
domain name is the name of the domain the MCM gatekeeper uses for look up. The embedded gatekeeper does not use an external source for this task. We recommend that you use your company domain name.
IP_address is the IP address assigned to the embedded gatekeeper.
Step 7 At the prompt, enter
GK (config-gk) #: zone prefix gatekeeper-name prefix-value.
Where:
gatekeeper-name is the name you assign to the embedded gatekeeper.
prefix-value is the zone prefix assigned to the embedded gatekeeper in the embedded gatekeeper Services Definition Table. See the "Registering Services" section for instructions on how to assign the embedded gatekeeper a
zone prefix.
Step 8 Press Ctrl-Z to exit configuration mode.
Step 9 To save the configuration to memory, at the prompt, enter
copy running-config startup-config
To ensure that there is two-way communication between the MCM gatekeeper and the embedded gatekeeper, be sure to register the MCM gatekeeper with the embedded gatekeeper. You must register the MCM gatekeeper with the embedded gatekeeper as a neighbor gatekeeper. For information on registering neighbor gatekeepers, see "Registering an MCM Gatekeeper as a Neighbor Gatekeeper" section.
Posted: Wed Sep 20 09:05:59 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.