|
|
This chapter describes how to enable and configure the embedded gatekeeper. The topics include:
The Cisco IP/VC 3510 MCU is equipped with an embedded gatekeeper. The default status of the gatekeeper is disabled. You can enabled the embedded gatekeeper to provide H.323-gatekeeper functions for the MCU and other H.323-endpoints on the network.
The embedded gatekeeper is designed for small- to medium-size networks. It can have up to 100 endpoints registered concurrently and handle up to 30 calls simultaneously. H.323 terminals can register automatically with the embedded gatekeeper when they come online. You must register MCUs and gateways with the embedded gatekeeper manually.
The embedded gatekeeper has the following features:
To use the embedded gatekeeper, you must enable it. The user interface that is used to enable the embedded gatekeeper is accessed through the user interface for the MCU. Once enabled, the embedded gatekeeper can register terminal endpoints and manage basic videoconference calls with minimum additional configuration. However, if you want the embedded gatekeeper to use the current MCU, other MCUs and gateways, you must register them manually. You can also configure the gatekeeper for your environment.
The unit is shipped with the embedded gatekeeper disabled. Once enabled, the gatekeeper is preconfigured and can be used with the local MCU with minimum additional configuration. To use the embedded gatekeeper as shipped, you must do the following:
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.
To use the gatekeeper using the predefined configuration, perform the following steps:
Step 2 Check GK On in the Network Control window (see the "Enabling the Gatekeeper and Setting Network Controls" section).
Step 3 Register the services you want the gatekeeper to use (see the "Registering Services" section).
To access the user interface to enable and configure the embedded gatekeeper, perform the following steps:
Step 2 Choose or enter the IP address of the current MCU and click Next.
 |
Caution Make sure Cisco IP/VC 3500 products installed on the same segment as the configuration computer are assigned a valid IP address for the segment before you enter the IP address of a unit on a remote segment. This procedure will assign new Cisco IP/VC 3500 products the IP address you enter if the unit has no IP address or its IP address is not valid for the segment. |
Step 3 Enter the unit password and click Next.
Step 4 In the Configuration Source window, click Gatekeeper Setup. The Application Parameters window appears. (See Figure B-1.)
The switch that enables the embedded gatekeeper is located in the Network Controls window. The Network Controls window allows you to set the parameters the gatekeeper uses to manage videoconference calls on the network. Management parameters you can set include:
To enable the embedded gatekeeper and set network controls, perform the following steps:
Step 2 Check the GK On check box located in the right column of the window to enable the embedded gatekeeper.
Step 3 Check the Everyone Can Register check box 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 the "Registering Endpoints with the Gatekeeper" section for instructions on how to register an endpoint in the Zone Definition Table.
Step 4 Check the Alias Assignment check box 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 Check the Call Indirect check box if you want all incoming videoconference calls to be routed through the gatekeeper.
The unit is shipped with this option enabled.
Step 6 Check the Dynamic IP Environment check box if you want the gatekeeper to identify predefined endpoints by their aliases rather than their IP addresses.
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 Check the Accept Registration check box 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 Check the Accept Calls check box 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.
The default value is 168 hours. Registration is dropped for endpoints that are not used within the allotted time, and the endpoint will have to reregister.
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.
This value is a subset of the total amount of bandwidth available 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 window.
Step 14 To save the changes, do one of the following:
The Advanced Settings option in the Network Control window lets you do the following:
The parameters that are used to manage access rights between embedded gatekeepers are used in conjunction with parameters set in the Neighbor Gatekeeper window. When the Advanced Settings parameters and the relevant Neighbor Gatekeeper parameters are set, the gatekeeper initiating the call and the target gatekeeper determine whether the initiating gatekeeper has access rights for the type of call proposed during the call negotiation phase. If the gatekeeper has access rights, the call can be attempted. If the gatekeeper does not have access rights, the call is rejected.
The parameter that sets a timeout interval allows the embedded gatekeeper to automatically drop endpoints that autoregister when the endpoint fails to respond to a status inquiry. When an endpoint is dropped, it must reregister with the gatekeeper before it can place or receive videoconference calls. The timeout interval does not apply to endpoints that are registered manually.
This section describes how to configure the advanced settings options to use the call restriction feature and to set the timeout. To configure the relevant Neighbor Gatekeeper parameters, see the "Registering Neighbor Gatekeepers" section . Both sets of parameters must be set for all embedded gatekeepers that you want to participate in the access restriction program.
To set advanced settings parameters, perform the following steps:
Step 2 In the Default Distance field, enter a value between 0 and 255.
The Default Distance parameter applies to endpoints dialing endpoints in neighboring embedded-gatekeeper zones. This value is compared to the value of the Neighbor Distance parameter (set in the Neighbor Gatekeeper window) of the gatekeeper to which the call is placed. If the Default Distance value is less than the Neighbor Distance value, access rights are granted and the call is attempted. If the value is larger than the Neighbor Distance value, access is denied and the call is rejected.
Step 3 In the Multicast Distance field, enter a value between 0 and 255.
The Multicast Distance parameter applies to multicast the embedded gatekeeper attempts to send to neighboring embedded gatekeepers. This value is compared to the value of the Neighbor Distance parameter (set in the Neighbor Gatekeeper window) of the gatekeeper to which the call is placed. If the Multicast Distance value is less than the Neighbor Distance value of the neighboring gatekeeper, access rights are granted and the multicast is attempted. If the value is larger than the Neighbor Distance value, access is denied and the multicast is rejected.
The gatekeeper makes four status inquiry attempts before deciding that the endpoint is no longer available. The gatekeeper removes the Online status from the endpoint, and the endpoint must reregister to receive calls.
|
Caution Clicking the Factory Defaults button takes precedence over any ongoing activity on the Cisco IP/VC 3510 MCU. Ongoing calls are disconnected and parameters on Flash memory are restored to the default configuration. |
Endpoints such as MCUs and gateways provide and perform the videoconferencing services that videoconference 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 in order 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:
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.
This section describes how to register services provided by endpoints and how to enable and edit predefined services.
To register services created on endpoints, perform the following steps:
Step 2 Click Add. The Services Definition dialog box appears. (See Figure B-5.)
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:
Step 6 Click OK to save your changes. The Services Definition Table appears.
Step 7 To save the changes, you can:
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.
To edit and enable predefined services, perform the following steps:
Step 2 Click Edit. The Services Definition dialog box appears. (See Figure B-5.)
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 Set the zone access parameter as follows:
Step 5 Click OK to save your changes. The Services Definition Table appears.
The gatekeeper manages videoconference-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 zone.
The Cisco IP/VC embedded gatekeeper zone can contain up to 100 endpoints. Endpoints can register automatically or be registered manually. Endpoints that support RAS protocol can register automatically.
The gatekeeper Zone Definition Table (see Figure B-6) lists the endpoints registered to the gatekeeper. You can use the table to view a list of the endpoints currently registered, manually register new endpoints, and 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 window. |
To access the Zone Definition Table, click Zone Definition in the Application Parameters window. The Zone Definition Table appears. (See Figure B-6.)
To manually register an endpoint, perform the following steps:
Step 2 From the Unit Type field, choose the description that describes the endpoint you want to register.
Step 3 You can use the Distance parameters to restrict the access that the endpoint has to endpoints registered to neighboring gatekeeper. To use this feature, assign a value from 0 to 255 to the endpoint in the Max.Distance field.
The value is compared to the Neighbor Distance value configured in the Neighbor Gatekeepers window of the target gatekeeper. If the endpoint attempts to call to a gatekeeper with a Neighbor Distance value greater than the Max.Distance value, the call is rejected.
Step 4 In the Registration IP field, enter the IP address of 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 videoconference groups. To add this endpoint to the group, enter the group prefix as registered in the Services 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 Dynamic Host Configuration Protocol (DHCP) and can dynamically register with the gatekeeper, at least one of the aliases must also correspond to one of the online aliases of the endpoint. This allows the gatekeeper to match the predefined properties to the endpoint. |
Step 8 Click Allowed Services. The Allowed Services dialog box appears.
Step 9 The Allowed Services dialog box lists 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, perform the following steps:
a. Select the service you want to enable.
b. Check Enable.
c. After you have enabled all of the services you want the endpoint to use,
click OK.
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, perform one of the following steps:
You can view and edit parameters of all endpoints registered in the zone. To view or edit the zone parameters of an endpoint, select the endpoint in the Zone Definition Table 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.
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.
You can delete endpoints from the Zone Definition Table. Deleted endpoints must reregister with the gatekeeper to make and receive videoconference calls. To delete an endpoint, select the endpoint and click Delete.
The embedded gatekeeper supports group hunting. Group hunting is a gatekeeper service in which several terminals are associated with a single service prefix. The service prefix is assigned to each terminal as an E.164 address. When the service prefix is dialed, the gatekeeper routes the call to the first available terminal that is associated with the service prefix.
To create a Group Hunting service, perform the following steps:
Step 2 Click Add. The Services Definition dialog box appears. (See Figure B-4.)
Step 3 In the Description field, enter a description for the group.
Step 4 In the Prefix field, enter the value you want to use for the group hunting service prefix.
Step 5 Set the access parameters you want the group to have and click OK. The Services Definition Table appears.
Step 6 Close the Services Definition Table.
Step 7 In the Applications Parameters window, click Zone Definition. The Zone Definition Table appears. (See Figure B-6.)
Step 8 In the Zone Definition Table, do one of the following:
Step 9 In the Phone Number column, enter the group hunting service prefix.
Step 10 Click OK.
Step 11 Repeat Step 7 through Step 10 for each endpoint that you want to include in the group.
Step 12 Close the dialog box when you have finished.
A gatekeeper and all of the endpoints registered to it constitute a zone. (Some gatekeepers allow you to create multiple subzones.) The H.323 protocol requires that gatekeepers handle the initiation cycle for all calls that are dialed in to and out of the zone.You can facilitate the process that 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 a remote gatekeeper with the Cisco IP/VC embedded gatekeeper, perform the following steps:
Step 2 Click Add. The Neighbor GK Parameters dialog box appears. (See Figure B-9.)
Step 3 In the Neighbor IP field, enter the IP address of the remote gatekeeper.
The default port for Cisco IP/VC embedded gatekeepers is 1719.
Step 5 In the Neighbor Prefix field, enter the zone prefix if one has been defined for the remote gatekeeper.
Step 6 If your network of Cisco IP/VC 3500 embedded gatekeepers is using access control, enter a value between 0 and 255 in the Neighbor Distance field.
The Neighbor Distance value is compared to the Max.Distance value assigned to manually registered endpoints in the Zone Definition Table and to the Default Distance and Multicast Distance values assigned in the Advanced Settings option of Network Controls window for automatically registered endpoints. For endpoint-to-endpoints calls, access is granted if the Neighbor Distance value is less than the Default Distance value. For calls that require multicast distribution, the access is granted if the Neighbor Distance value is less than the Multicast Distance value.
Step 7 In the Description field, enter an identifying description for the neighboring gatekeeper.
Step 8 To save the changes, perform one of the following steps:
To edit neighboring gatekeeper parameters, perform the following steps:
Step 2 Make the changes and then click OK.
To delete a 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.
To ensure two-way communication between the embedded gatekeeper and the MCM gatekeeper, you must register the MCM gatekeeper with the embedded gatekeeper in the Neighbor Gatekeeper window. To register the MCM gatekeeper with the embedded gatekeeper, perform the following steps:
Step 2 In the Neighbor IP field, enter the IP address of the MCM gatekeeper.
The default port for MCM gatekeepers is 1719.
Step 4 In the Neighbor Prefix field, enter the zone prefix if one has been defined for the MCM gatekeeper.
Step 5 In the Description field, enter an identifying description for the MCM gatekeeper.
Step 6 To save the changes, perform one of the following steps:
Step 7 Click OK to save changes and exit the dialog box.
For networks that have several endpoints offering the same services within a zone, the Network Topology feature allows the gatekeeper to subdivide the network to optimize use of service providers. The gatekeeper normally sends a call to the first available service provider for processing. When routers are placed between the caller and the service provider, bottlenecks can occur. You can create subnet islands that the gatekeeper can use to route calls to service providers closer to
the caller.
To create an island, perform the following steps:
Step 2 Click Add. The Subnet Parameters dialog box appears. (See Figure B-11.)
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 of the island.
Step 7 Click OK. The island parameters appear in the Network Topology Table.
Step 8 To save the changes, perform one of the following steps:
The parameters set in each Cisco IP/VC embedded gatekeeper definition table can be saved as a file and used to restore or configure the table parameters of an embedded gatekeeper. This section describes how to load the save parameters into Cisco IP/VC Configuration Utility.
To load a file into a Definition Table, perform the following steps:
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:
Step 2 Select the file you want to load.
Step 3 Click OK.
After the file loads into the Cisco IP/VC Configuration Utility, you can modify the parameters or use them as they are to configure the embedded gatekeeper.
This section describes how to configure the embedded gatekeeper to use the Cisco MCM proxy. The proxy can provide quality of service (QoS) and security for H.323 videoconference calls.
For the embedded gatekeeper to use the proxy, the proxy service must register with the embedded gatekeeper. However, the proxy can only register with one gatekeeper. If the proxy is configured to register with the MCM gatekeeper, you must delete the current configuration and reconfigure the proxy to register with the embedded gatekeeper.
The embedded gatekeeper uses the proxy in conjunction with remote gatekeepers that have proxy capability. You must configure the embedded gatekeeper to use remote gatekeepers that have proxy capability.
This section describes how to configure a new installation of the proxy to use the embedded gatekeeper. If you want to reconfigure an existing proxy to use the embedded gatekeeper, refer to the proxy documentation for instructions on how to disable the current proxy gatekeeper configuration. To set up a new proxy to register with the embedded gatekeeper, perform the following steps:
Step 2 At the prompt, enter
enable
Press Enter.
Step 3 At the password prompt, enter
password
Press Enter.
Step 4 At the privilege prompt, enter
config t
Press Enter.
Step 5 At the prompt, enter
proxy h323
Press Enter.
This command globally enables the proxy commands.
Step 6 At the prompt, enter
interface
Press Enter.
where interface is the interface on which you want to install the proxy. FastEthernet or serial interfaces are generally used for the proxy.
Step 7 At the prompt, specify the location of the port you want to use for the proxy. To specify the port, type interface # and press Enter.
where # is the physical location of the port that you want to use for the proxy.
Step 8 At the prompt enter,
h323 H323 ID name
Press Enter.
where H323 ID name is the name you assign to the proxy.
Step 9 At the prompt, enter
h323 gatekeeper ipaddr embedded gatekeeper ipaddress
Press Enter.
Step 10 At the prompt, enter
ip-prec | rsvp
Press Enter.
where ip-prec (IP precedence) and rsvp are QoS modes.
|
Note If you configure the proxy to use RSVP, the WAN port must be configured with RSVP parameters. |
Step 11 At the prompt, enter
write
Press Enter.
Step 12 At the prompt, press Ctrl Z to end the configuration session.
Verify that the proxy registers with the embedded gatekeeper. You can verify the registration by the looking in the Zone Definition table for the embedded gatekeeper in the Cisco IP/VC Configuration Utility.
To set up the embedded gatekeeper to use proxy services, perform the following steps:
Step 2 Select or enter the IP address of the current IP/VC 3510 MCU and click Next.
Step 3 Enter the unit password and click Next.
Step 4 In the Configuration Source window, click Gatekeeper Setup.
The Application Parameters window appears.
Step 5 Click Network Control.
The Network Control window appears.
Step 6 Uncheck Call Indirect.
Step 7 Click OK.
The Application Parameters window appears.
Step 8 Click Neighbor Gatekeepers.
The Neighbor Gatekeepers Table appears.
Step 9 Click Add. The Neighbor GK Parameters dialog box appears.
Step 10 In the Neighbor IP field, enter the IP address of a remote gatekeeper with proxy capabilities that you want the embedded gatekeeper to use.
Step 11 In the Neighbor Port field, enter the port number that the remote gatekeeper uses to listen.
The default port is 1719.
Step 12 In the Neighbor Prefix field, enter the zone prefix that the remote gatekeeper uses.
Step 13 In the Description field, enter proxy.
Step 14 Click OK.
The Neighbor Gatekeeper Table appears.
Step 15 Click OK.
The Application Parameters window appears.
Step 16 Click Exit.
Posted: Wed Sep 20 09:05:52 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.