Configuring the Embedded Gatekeeper

You must register the Cisco IP/VC 3520 Video Gateway with a gatekeeper on the network. You can register the unit with a gatekeeper that is already running or you can use the embedded gatekeeper the unit is equipped with. The embedded gatekeeper can provide H.323 gatekeeping functions for the Cisco IP/VC 3520 Video Gateway and for other H.323 endpoints on the LAN.

The unit is shipped with the embedded gatekeeper disabled. Once enabled, the gatekeeper is preconfigured and can be used with the Video Gateway with minimum additional configuration. To use the embedded gatekeeper as shipped, you must do the following:

Enable the gatekeeper
Register the services you want users to be able to use

Endpoints must register with a gatekeeper when a gatekeeper is present on the network. The embedded gatekeeper is preconfigured to register endpoints that support registration, admission, and status (RAS) automatically. Endpoints that do not support RAS can be registered manually.

This chapter provides complete instruction for configuring the embedded gatekeeper. To use the gatekeeper's predefined configuration, perform the following steps:

Step 1 Access the gatekeeper in the Cisco IPVC Configuration Utility (see "Accessing the Gatekeeper in the Configuration Utility").

Step 2 Activate GK On in the Network Control dialog box (see "Enabling the Gatekeeper and Setting Network Controls").

Step 3 Register the services you want to the gatekeeper to use (see "Registering Services").

Access ing the Gatekeeper in the Configuration Utility

To access the gatekeeper parameters in the configuration tool, perform the following steps:

Step 1 Click Start>Programs>Cisco IPVC Tools>Configuration>IPVC> Configuration Utility.

Step 2 Select or enter the IP address of the Cisco IP/VC 3520 Video Gateway on which you want to enable the embedded gatekeeper and click Next.

Caution Make sure Cisco IP/VC Series 3500 units installed on the same segment as the configuration computer have an assigned IP address before you enter the IP address of a unit on a remote segment. This procedure will assign new Cisco IP/VC Series 3500 units this IP address if an address is not already assigned.

Step 3 Enter the units password and click Next.

Step 4 In the Configuration Source dialog box, click Gatekeeper Setup. The Application Parameters dialog box appears (see Figure B-1).

Figure B-1: Application Parameters Dialog Box

Enablin g the Gatekeeper and Setting Network Controls

The switch that enables the embedded gatekeeper is located in the NetWork Controls dialog box. The Network Controls dialog box allows you to set the parameters the gatekeeper uses to manage conference calls on the network. Management parameters you can set include:

Enabling/disabling the gatekeeper
Automatic user registration
Configuring the gatekeeper to route all calls
Setting the maximum number of concurrent calls the gatekeeper allows in the zone
Setting the maximum limit on the amount of network bandwidth the gatekeeper can use
Setting the maximum limit on the amount of network bandwidth the gatekeeper will allow a terminal to use
Assigning the gatekeeper an identifier

To enable the embedded gatekeeper and set network controls, perform the following steps:

Step 1 Click Network Control in the Application Parameter dialog box. The Network Control dialog box appears (see Figure B-2).

Figure B-2: Network Control Dialog Box

Step 2 Click GK On located in the right column of the dialog box. The gatekeeper is enabled when a check mark appears on the button.

Step 3 Enable Everyone Can Register if you want every endpoint that logs in to the network to be able to register with this gatekeeper. The endpoint is registered as long as it is logged onto the network. The feature is enabled when a check mark appears on the button. The unit is shipped with this option enabled.

You can also register endpoints with the gatekeeper permanently. To give an endpoint a permanent registration, enter information about the endpoint in the Zone Definition Table. See "Registering Endpoints with the Gatekeeper" for instructions on how to register an endpoint in the Zone Definition Table.

Step 4 Enable Alias Assignment if you want the gatekeeper to identify an endpoint receiving a call by aliases other than that with which the endpoint registered. The unit is shipped with this option enabled.

Step 5 Enable Call Indirect if you want all incoming conference calls to be routed through the gatekeeper. The unit is shipped with this option enabled.

Step 6 Enable Dynamic IP Environment if you want the gatekeeper to identify predefined endpoints by their aliases rather than their IP address. This feature is designed for environments where the endpoints you predefine use DHCP and are subject to changing IP addresses. Because the alias is being used for call identification, users can receive calls at different endpoints.

Step 7 Enable Accept Registration to allow new endpoints to register with the gatekeeper. The gatekeeper can have up to 100 registrations at one time. You can stop new registration at any time by disabling this option. The unit is shipped with this option enabled.

If you want to clear all current registrations, click Unregister All.

Step 8 Enable Accept Calls to allow the gatekeeper to receive incoming calls. Disable the option to prevent the gatekeeper from receiving new calls. The unit is shipped with this option enabled.

You can disconnect calls in progress by clicking Disconnect All.

Step 9 In the Unregistration Timeout (Hours) field, enter a value for the amount of time between calls that the gatekeeper will allow a dynamically registered endpoint to remain registered. Registration of endpoints not used within the allotted time are dropped, and the endpoint will have to reregister. The default value is 168 hours.

Step 10 In the Max. Number of Calls field, enter the number of concurrent calls the gatekeeper will allow in the zone. The default value is 25 calls.

Step 11 In the Max. Bandwidth (Kbps) field, enter a value for the maximum amount of bandwidth you will allow the gatekeeper to appropriate for making conference calls. This value is a subset of the total amount of bandwidth you have to handle telephone and network traffic. The default value is 1,000,000 Kbps.

Step 12 In the Max. Bandwidth per Terminal field, enter a value for the maximum amount of bandwidth the gatekeeper will allow a terminal to use. This value applies only to terminals. The default value is 1,000,000 Kbps.

Step 13 In the GK Identifier field, enter a name for the gatekeeper. Terminals use this name to identify the gatekeeper during the discovery process. The name also appears on the Unit Identification dialog box.

Step 14 To save the changes, you can

(a) Click Apply to save without exiting the dialog box.

(b) Click Save to save these parameter settings in a file that can be used by other Cisco IP/VC embedded gatekeepers. The Save As dialog box appears. The file you save can be accessed through the configuration utility to restore these parameters to the unit or to configure other Cisco IP/VC embedded gatekeepers.

Advanced Settings

Advanced Settings lets you set default parameters for endpoints registered with the gatekeeper. This section describes the parameters you can set.

To set Advanced Settings parameters, click Advanced Settings. The Advance Settings dialog box appears (see Figure B-3).

Figure B-3: Advanced Settings Dialog Box for Network Control

The Advanced Settings parameters are:

Default Distance---The Distance parameters are used to restrict access local gatekeeper users have to neighboring gatekeeper zones. This parameter is used in conjunction with the Neighbor Distance parameter you assign for other gatekeepers in Neighbor Gatekeeper. You can assign a default value between 0 and 255 in the Default Distance field. When an automatically registered endpoint attempts to place a call to another zone, this value is compared to the Neighbor Distance value. If the Default Distance value is larger than the Neighbor Distance value, the call is rejected.
Multicast Distance---This Distance parameter is used to restrict multicast access the local gatekeeper has to neighboring gatekeepers. This parameter is used in conjunction with the Neighbor Distance parameter you assign for other gatekeepers in Neighbor Gatekeeper. You can assign a default value between 0 and 255 in the Multicast Distance field. When local gatekeeper attempts a multicast, this value is compared to the Neighbor Distance values. If the Multicast Distance value is larger than a Neighbor Distance value, the multicast is not sent to that gatekeeper.
Unresponsive Timeout (Sec)---This value sets in seconds how long the gatekeeper waits for an endpoint response to a status inquiry. The gatekeeper makes four status inquiry attempts before deciding that the endpoint is no longer available. The gatekeeper removes the endpoint's from Online status, and the endpoint must reregister to receive calls.

Factory Defaults

Factory Default allows you to restore the embedded gatekeeper's factory default settings.

Caution Factory Default takes precedence over any ongoing activity on the Cisco IP/VC 3520 Video Gateway. Ongoing calls are disconnected and parameters on flash memory are restored to the default configuration.

Regist ering Services

Endpoints such as MCUs and gateways provide and perform the conferencing services that conference users can use. Each service an endpoint provides is defined at the endpoint and assigned a calling prefix. These services must be registered with the gatekeeper for users in its zone to use them. To register a service with the embedded gatekeeper, you need the assigned calling prefix and a brief description of the service.

In addition to the services provided by endpoints, the embedded gatekeeper provides five predefined services. These services include:

Zone prefix 1
Zone prefix 2
Forward
Forward on no answer
Exit Zone

If other gatekeepers on your network are assigned a dialing prefix, you must assign a value to Zone prefix 1. Zone prefix 1 sets the dialing prefix for the gatekeeper. Calls coming from outside the zone must include the prefix in their string to reach the recipients within the zone. All other services are optional.

This section describes how to register services provided by endpoints and how to enable and edit predefined services.

Registering Services Provided by Endpoints

To register services created on endpoints, perform the following steps:

Step 1 In the Application Parameters dialog box, click Service Definitions. The Service Definition Table appears (see Figure B-4).

Figure B-4: Service Definitions Table

Step 2 Click Add. The Service Definitions dialog box appears (see Figure B-5).

Figure B-5: Service Definitions Dialog Box

Step 3 In the Description field, enter a description that describes the service.

Step 4 In the Prefix field, enter the dial code assigned to the service. Users must include this code in the dial string to use this service.

Step 5 Set access parameters for the service.

(a) If you want the service to be available to only predefined endpoints in this zone and to all endpoints from other zones, click the Public field (an X indicates that the feature is enabled).

(b) If you want only endpoints registered in this zone to use the service, click the Default field.

Step 6 Click OK to save your changes. The Service Definition Table appears.

Step 7 To save the changes, you can:

(a) Click Apply to save without exiting the dialog box.

Editing and Enabling Predefined Services

This section describes how to edit and enable the predefined services available in the Cisco IP/VC embedded gatekeeper services. The predefined services are listed and defined as follows:

Forward---Allows an endpoint to forward calls.
Forward on no-answer---N/A
Zone prefix 1---Allows you to set a dialing prefix for the gatekeeper. This parameter must be set in environments that use zone prefixes. The zone prefix serves as the gatekeeper's area code. In environments using zone prefixes, all calls originating from outside of the zone must include the zone prefix. This service must be enabled for all registered endpoints that are to receive calls from outside of the zone.
Zone prefix 2---Allows you to set a second dialing prefix for the gatekeeper. You must enable this service in the profiles of the registered users you want to associate with this prefix.
Exit Zone---Allows you to restrict access to zones outside the endpoints current zone. The Exit Zone prefix must be dial to dial out of the zone.

Perform the following steps to edit and enable predefined services:

Step 1 Click the predefine service you want to edit and enable in the Service Definitions Table.

Step 2 Click Edit. The Service Definitions dialog box appears.

Step 3 In the Prefix field, enter the dial code you want to assigned to the service. Users must include this code in the dial string to signal that they want to make this kind of call.

Step 4 If you want the service to be available to only predefined users in the embedded gatekeepers zone and to users who are not registered in the embedded gatekeeper's zone, click the Public field (this should place an X in the box).

Step 5 If you want the service to be available to only users registered with the embedded gatekeeper, click the Default field.

Step 6 If you want the service to be available to all users, click the Public and Default fields.

Step 7 Click OK to save your changes. The Service Zone Definition Table appears.

Registeri ng Endpoints with the Gatekeeper

The gatekeeper manages conference-call traffic for all the endpoints that register with the gatekeeper. Whenever a gatekeeper is installed on the network endpoints must register with a gatekeeper. Endpoints that register with a gatekeeper populate the gatekeeper's zone.

The Cisco IP/VC embedded gatekeeper's zone can contain up to 100 endpoints. Endpoints can register automatically or be registered manually. Endpoint that supports RAS protocol can register automatically.

The gatekeeper's Zone Definition Table list the endpoints registered to the gatekeeper. You can use the table to view a list of the endpoints currently registered, to manually register new endpoints, and to edit endpoint registration profiles.

This section describes how to access the Zone Definition Table, how to manually register new endpoints, and how to edit the registration profiles of currently registered endpoints.

Note The parameter that allows automatic registration is set in the Network Control dialog box.

Accessing the Zone Definition Table

To access the Zone Definition Table, click Zone Definition in the Application Parameter dialog box. The Zone Definition Table appears (see Figure B-6).

Figure B-6: Zone Definition Table

Manually Registering an Endpoint

Follow these steps to manually register an endpoint:

Step 1 Click Add in the Zone Definition Table. The Predefined Properties dialog box appears (see Figure B-7).

Figure B-7: Predefined Properties Dialog Box

Step 2 Click the Unit Type field to display the drop-down list. Select the description that describes the endpoint you want to register.

Step 3 You can use the Distance parameters to restrict access local gatekeeper users have to neighboring gatekeeper zones. To use this feature, assign a value between 0 and 255 to the endpoint in the Max.Distance field. This value is compared to the Neighbor Distance value you assign to gatekeepers in Neighbor Gatekeepers. If an endpoint attempts to call to a zone with a Neighbor Distance value greater than its Max.Distance value, the call is rejected.

Step 4 In the Registration IP field, enter the IP address on the endpoint you want to register in this zone.

Step 5 In the Port field, enter the port the endpoint will use to communicate with the gatekeeper.

Step 6 In the Terminal IDs field, enter an alias you want to associate with the endpoint you are registering. You can associate up to five aliases with the endpoint. Aliases should be unique for endpoints in the zone.

Step 7 In the Phone Numbers field, enter a dialing number you want to associate with the endpoint.

You can use this field to create conference groups. To add this endpoint to the group, enter the group prefix as registered in the Service Definition Table. When the prefix is used to place a call, every endpoint having the prefix in this field is contacted for the call.

Note If the endpoint uses DHCP and can dynamically register with the gatekeeper, at least one of the aliases must also correspond to one of the endpoint's online aliases. This allows the gatekeeper to match the predefined properties to the endpoint.

Step 8 Click Allowed Services. The Allowed Services dialog box appears (Figure B-8).

Figure B-8: Allowed Services Dialog Box

Step 9 The Allowed Services dialog box list all of the services registered with the current embedded gatekeeper. Enable those services you want the endpoint to have access to. Only services having a prefix can be enabled. To enable a service

(a) Click the service you want to enable.

(b) Click Enable. A check mark appears in the Enable column of the services that are enabled.

Step 10 Click OK. An entry for the endpoint you have just registered appears in the Zone Definition Table.

Step 11 To save the changes, you can

(a) Click Apply to save without exiting the dialog box.

Viewing and Editing a Registered Endpoint

You can view and edit parameters of all endpoints registered in the zone. To view or edit an endpoint's zone parameters highlight the endpoint and click Edit. For endpoints that are manually registered the Predefined Properties dialog box appears. For endpoints that register automatically the Online Properties dialog box appears.

Setting Parameters for Automatically Registered Endpoints

The parameters displayed in the Online Properties dialog box are fixed and cannot be altered through the gatekeeper. For endpoints that register automatically, only the Make Predefined option is configurable.

Deleting Endpoints

You can delete endpoints from the Zone Definition Table. Deleted endpoints must reregister with the gatekeeper to make and receive conference calls. To delete an endpoint, select the endpoint and click Delete.

Sett ing Up Group Hunting Services

The embedded gatekeeper supports a service where it will route a call to one of several endpoints. This service is known as Group Hunting. Group Hunting involves using a service prefix as an endpoint phone number. When the endpoint registers with the gatekeeper, the gatekeeper recognizes the prefix/phone number and duly routes calls to the endpoint. You can assign the prefix as a phone number to several endpoints. The gatekeeper will route the call to the first available endpoint.

To create a Group Hunting service, perform the following steps:.

Step 1 Click Service Definition.

Step 2 Click Add.

Step 3 In the Description text box, enter a description for the group.

Step 4 In the Prefix text box, enter the value you want to use for the Group Hunting prefix/phone number.

Step 5 Set the access parameters you want the group to have and click OK.

Step 6 Click Zone Definition.

Step 7 Highlight an existing endpoint entry and click Edit. If you want to register an endpoint manually, click Add.

Step 8 In the Phone Number column, enter the Group Hunting service prefix.

Step 9 Click OK.

Step 10 Repeat Steps 7 through 9 for each endpoint you want to include in the group. Exit the dialog box when you are finished.

Registerin g Neighbor Gatekeepers

A gatekeeper and all of the endpoints registered to it constitute a zone. (Some gatekeepers allow you to create multiple subzone.) H.323 protocol requires that gatekeepers handle the initiation cycle for all calls that are dialed into and out of the zone. You can facilitate the process the Cisco IP/VC embedded gatekeeper uses to contact users in remote zones by registering remote gatekeepers with the Cisco IP/VC embedded gatekeeper.

To register remote gatekeepers with the Cisco IP/VC embedded gatekeeper, perform the following steps:

Step 1 In the Application Parameters dialog box click Neighbor Gatekeepers. The Neighbor Gatekeepers Table is displayed (see Figure B-9).

Figure B-9: Neighbor Gatekeepers Table

Step 2 Click Add. The Neighbor GK Parameters dialog box appears (see Figure B-10).

Figure B-10: Neighbor GK Parameters Dialog Box

Step 3 In the Neighbor IP field, enter the IP address of a neighboring gatekeeper.

Step 4 In the Neighbor Port field, specify the RAS port of the neighboring gatekeeper uses. The default port for Cisco IP/VC embedded gatekeepers is 1719.

Step 5 In the Neighbor Prefix field, enter the zone prefix if one is defined for this neighbor gatekeeper.

Step 6 You can use the Distance parameters to restrict access local gatekeeper users have to neighboring gatekeeper zones. To use this feature, assign a value between 0 and 255 to the neighbor gatekeeper in the Neighbor Distance field. This value is compared to the Max.Distance value you assign to endpoints you manually register or edit in the Zone Definition Table, the Default Distance value you assign for automatically registered endpoints in the Advanced Settings option of Network Controls, and the Multicast Distance value you also assign in the Advanced Settings option of Network Controls.

Step 7 In the Description field, enter an identifying description for the neighboring gatekeeper.

Step 8 To save the changes, you can:

(a) Click Apply to save without exiting the dialog box.

Editing an Existing Neighbor Gatekeeper

To edit a neighboring gatekeeper's parameters, perform the following steps:

Step 1 Highlight the gatekeeper you want to edit and click Edit. The Neighbor GK Parameters dialog box appears with the selected gatekeeper's information loaded.

Step 2 Make the changes and then click OK.

Deleting an Existing Neighbor Gatekeeper

To delete an gatekeeper from the Neighbor Gatekeepers Table select the gatekeeper you want to delete and click Delete. The gatekeeper is deleted from the Neighbor Gatekeepers Table.

Configuring Network Topology

For networks that have several endpoints offering the same services within a zone, the Network Topology feature allows the gatekeeper to parcel the network to optimize use of service providers. The gatekeeper normally sends a call to the first available service provider for processing. In environments where there are routers between the caller and the service provider, bottlenecks can occur. You can create subnet islands in Network Topology that the gatekeeper can use to route calls to service providers closer the caller.

To create an island, perform the following steps:.

Step 1 Click Network Topology. The Network Topology Table appears (see Figure B-11).

Figure B-11: Network Topology Table

Step 2 Click Add. The Subnet Parameters dialog box appears (see Figure B-12).

Figure B-12: Subnet Parameters Dialog Box

Step 3 In the Subnet IP field, enter the address of the subnet in which you want to create the island.

Step 4 In the Subnet Mask field, enter the address of the subnet mask in which you want to create the island.

Step 5 In the Island Code field, enter a value that the gatekeeper will use to identify the island. Users must include the island code in the dial string to use this feature.

Step 6 In the Description field, enter a description to describe the island.

Step 7 Click OK. The island parameters appear in the Network Topology Table.

Step 8 To save the changes, you can:

(a) Click Apply to save without exiting the dialog box.

Loading a Data File into a Definition Table

The Cisco IP/VC embedded gatekeeper allows you to save changes you make in the Definition Tables to files. You can use the file to restore the Definition Table's parameters or to set Definition Table parameters for another Cisco IP/VC embedded gatekeeper.

To load a file into a Definition Table, perform the following steps:

Step 1 Click Load in the table in which you want to load the file. The Open dialog box appears.

The Open dialog box lists files in the appropriate Cisco IP/VC directory that you can load. The file type is preselected. The file types are:

.srv for Service Definition Table files.
.zon for Zone Definition Table files.
.nbr for Neighbor Gatekeeper Table files.
.tpl for Network Topology Table files.
.ctr for Network Control Table files.

Step 2 Select the file you want to load.

Step 3 Click OK.

You can modify the file for the specific Cisco IP/VC gatekeeper you want to configure or use it as is. The parameters are written the units flash memory after you complete setting all of the configuration parameters and run the upload software.

Table of Contents

Configuring the Embedded Gatekeeper

B Appendix

C

D