Guest

Cisco Unified Videoconferencing 3500 Series Products

Configuring the Videoconferencing Gateways with the MCM

 Feedback

Reference Guide

Configuring the Cisco IP/VC 3520 and 3525 Videoconferencing Gateways with the Cisco Multimedia Conference Manager

This paper will cover the steps needed to configure IP/VC 3520/3525 videoconferencing gateways to work properly with the Cisco Multimedia Conference Manager (MCM). This paper also gives configuration examples for the MCM.

The Cisco IP/VC 3520 and 3525 Gateways normally ship with the embedded gatekeeper disabled. Use the configuration utility in the Gateway to verify that the internal Gatekeeper is disabled and the default Gatekeeper address is set. It is important to disable the embedded Gatekeeper, as this will ensure that no H.323 terminals register with the embedded gatekeeper by mistake. If an H.323 terminal does register with an embedded gatekeeper that is not configured, all the calls from the H.323 terminal will fail.

In this paper, it is assumed that you are using the following code versions:

1.4 or greater Gateway code

12.0.5.T1 or greater Cisco IOS® Software image

Cisco IP/VC 3520 and 3525 Videoconferencing Gateway configuration:

To verify that the embedded gatekeeper is turned off, perform the following steps:

1) Select "Gatekeeper Setup" in the Cisco IP/VC configuration utility.

In the Configuration Source window, select "Gatekeeper Setup"


2) In the Applications Parameters window, Select "Network Control"


3) Verify that the Gatekeeper is off:


If the box "GK on" is unchecked, then the Gatekeeper is disabled.

After verifying that the embedded Gatekeeper is disabled, exit the Gatekeeper configuration and continue on with the Unit Setup. In the Unit Setup, Network configurations, ISDN configuration, and Service Definitions will be configured. ISDN configuration is not covered in this document.

Exit Gatekeeper Setup, and select "Unit Setup" from the Configuration Source window.

In the Miscellaneous Parameters window, set the Default Gatekeeper by entering the IP address of the MCM:


Verify Service definitions:


You will see a Service Prefix defined on the gateway for each calling speed.

Service Prefixes are used to determine how the gateway will process the call. In the example above, calls with a prefix of 91 will be sent onto the WAN at 384 kbps and calls with a prefix of 92 will be sent at 128 kbps.

MCM Configuration:

On the MCM a gateway type prefix (service prefix) must be added for every service entry added to the gateway.

Example:

gw-type-prefix 91gw ipaddr 11.0.0.2 1820

gw-type-prefix 92 gw ipaddr 11.0.0.2 1820

Example: One zone only (Kirkwood)


Kirkwood_Terminal_A having an E.164 address of 12

Kirkwood_Terminal_B having an E.164 address of 13

Kirkwood_Terminal_C having an E.164 address of 14

Kirkwood_IPVC_35XX having an IP address of 10.0.0.2

Kirkwood_IPVC_35XX having 2 service prefixes, 92 for 128 kbps and 91 for 384 kbps calls

Kirkwood_MCM_GK_Proxy having an IP Address of 10.0.0.1

Domain is cisco.com

Configuration for Kirkwood_MCM_GK_Proxy:

Hostname Kirkwood_MCM_GK_Proxy

Proxy h323

interface Ethernet0/0

ip address 10.0.0.1 255.0.0.0

h323 interface

h323 qos ip-precedence 6

h323 h323-id Kirkwood-proxy

h323 gatekeeper id Kirkwood ipaddr 10.0.0.1

gatekeeper:

zone local Kirkwood cisco.com 10.0.0.1

gw-type-prefix 91 gw ipaddr 10.0.0.2 1820

gw-type-prefix 92 gw ipaddr 10.0.0.2 1820

use-proxy Kirkwood default outbound-from gateway

no shutdown

In this example any of the Kirkwood terminals can access the PSTN over ISDN by dialing a prefix of 92 for 128 kbps calls and a prefix of 91 for 384 kbps calls.

Example call: Kirkwood_Terminal_A makes a 384 kbps call to Denver, Kirkwood _Terminal_A dials 917205687234 and selects a call speed of 384 kbps.

Note: In this example, "91" is the gateway prefix and 720-568-7234 is the phone number. You may need to precede the phone number with the digit `1' for long distance, (e.g., 9117205687234).

Note: It is very important that the port number (in this case 1820) matches the port number of the registered gateway. Not all port numbers will be 1820. To find the registered port of a device enter show ga end on the router, and all the registered endpoints will be displayed.

If H.323 terminals in a local zone need access to a gateway in a remote zone, "hopoff" statements will need to be added into the local gatekeeper.

Example:

gw-type-prefix 91 hopoff Kirkwood

gw-type-prefix 92 hopoff Kirkwood

Example: Inter-Zone Gateway usage configuration: 2 zones defined—Kirkwood and Squaw


Kirkwood Configuration:

Kirkwood_Terminal_A having an E.164 address of 12

Kirkwood_Terminal_B having an E.164 address of 13

Kirkwood_Terminal_C having an E.164 address of 14

Kirkwood having a zone prefix of 408

Kirkwood_IPVC_35XX having an IP address of 10.0.0.2

Kirkwood_IPVC_35XX having 2 service prefixes, 92 for 128 kbps and 91 for 384 kbps calls

Kirkwood_MCM_GK_Proxy having an IP Address of 10.0.0.1

Domain is cisco.com

Squaw Configuration:

Squaw_terminal_A having an E.164 address of 21

Squaw_terminal_B having an E.164 address of 22

Squaw_MCM_GK_Proxy having an IP Address of 11.0.0.1

Squaw having a zone prefix of 831

Domain is cisco.com

Configuration for Kirkwood_MCM_GK_Proxy:

Hostname Kirkwood_MCM_GK_Proxy

Proxy h323

interface Ethernet0/0

ip address 10.0.0.1 255.0.0.0

h323 interface

h323 qos ip-precedence 6

h323 h323-id Kirkwood-proxy

h323 gatekeeper id Kirkwood ipaddr 10.0.0.1

gatekeeper:

zone local Kirkwood cisco.com 10.0.0.1

zone remote Squaw cisco.com 11.0.0.1

zone prefix Kirkwood 408

zone prefix Squaw 831

gw-type-prefix 91 gw ipaddr 10.0.0.2 1820

gw-type-prefix 92 gw ipaddr 10.0.0.2 1820

use-proxy Kirkwood default outbound-from gateway

use-proxy Kirkwood default inbound-to gateway

use-proxy Kirkwood remote-zone Squaw inbound-to terminal

use-proxy Kirkwood remote-zone Squaw outbound-from terminal

no shutdown

Configuration for Squaw_MCM_GK_Proxy:

Hostname Squaw_MCM_GK_Proxy

Proxy h323

interface Ethernet0/0

ip address 11.0.0.1 255.0.0.0

h323 interface

h323 qos ip-precedence 6

h323 h323-id Squaw-proxy

h323 gatekeeper id Squaw ipaddr 11.0.0.1

gatekeeper:

zone local Squaw cisco.com 11.0.0.1

zone remote Kirkwood cisco.com 10.0.0.1

zone prefix Kirkwood 408

zone prefix Squaw 831

gw-type-prefix 91 hopoff Kirkwood

gw-type-prefix 92 hopoff Kirkwood

use-proxy Squaw default inbound-from gateway

use-proxy Squaw default outbound-to gateway

use-proxy Squaw remote-zone Kirkwood inbound-to terminal

use-proxy Squaw remote-zone Kirkwood outbound-from terminal

use-proxy Squaw remote-zone Kirkwood inbound-to gateway

use-proxy Squaw remote-zone Kirkwood outbound-from gateway

no shutdown

In this example, any terminal registered with the Kirkwood or Squaw Gatekeeper may use the gateway in the Kirkwood zone. Example: Kirkwood_terminal_A makes a 128 kbps call to Denver by dialing 927205687234 and selecting 128 kbps as the call speed. At the same time Squaw_Terminal_B makes a 384 kbps call to Columbus by dialing 916143479805 (this is assuming the gateway is PRI and has available channels).

Troubleshooting:

If you have problems getting Gateway calls to work with the MCM, please try the following:

  • Verify that the terminals, Gateway and Proxy (if used) are registered on the appropriate MCM by using the show ga end command.

  • Verify that the terminals can call each other directly via E.164 address. If using multiple zones, verify that terminals can call other terminals in your zone as well as between zones.

  • Verify that the service prefixes are registered in the MCM as E.164 address (show ga end).

  • Attach console to each Gateway and enable RAS debug with the command debug RAS.

  • Verify that call admission requests (ARQ) are seen by the appropriate GK and if it is an inter-zone call, verify that a local GK makes location request (LRQ) to a remote GK.

  • For more debugging information please refer to the Cisco IOS Software documentation on the MCM.