|
|
This chapter describes how to enable and configure the embedded gatekeeper. The topics include:
The Cisco IP/VC 3520 Gateway is equipped with an embedded gatekeeper. The default status of the gatekeeper is disable. You can enabled the embedded gatekeeper to provide H.323-gatekeeper functions for the local Cisco IP/VC 3525 Gateway 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 call simultaneously. H.323 terminals can register automatically with the embedded gatekeeper when they come online. Gateways and MCUs must be registered 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 Cisco IP/VC 3520 Gateway. 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 Cisco IP/VC 3520 Gateway and 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 gateway 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.
This chapter provides complete instruction for configuring the embedded gatekeeper. If you want to use the predefined configuration of the gatekeeper, perform the following steps:
Step 2 Activate GK On in the Network Control window (see the "Enabling the Gatekeeper and Setting Network Controls" section later in this chapter).
Step 3 Register the services you want to the gatekeeper to use (see the "Registering Services" section later in this chapter).
To access the gatekeeper parameters in the configuration tool, perform the following steps:
Step 2 Select or enter the IP address of the Cisco IP/VC 3520 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 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 button located in the right hand column of the window to enable the 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 "Registering Endpoints with the Gatekeeper" 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.
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.
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 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 If you want the gatekeeper to be assessable to multicast traffic, set the following parameters.
a. Enter the multicast IP channel address in the Discovery Multicast Address field.
b. In the Port field, enter the port number the gatekeeper will use to listen for multicast traffic.
Step 15 To save the changes, you can:
a. Click Apply to save without exiting the window.
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.
c. Click OK to save the settings and exit the window.
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).
The Advanced Settings parameters are:
Factory Default allows you to restore the embedded gatekeeper factory default settings.
|
Caution Factory Default takes precedence over any ongoing activity on the Cisco IP/VC 3520 Gateway. 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 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 are:
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.
To register services created on endpoints, perform the following steps:
Step 2 Click Add. The Service Definitions 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:
a. If you want the service to be available to only predefined endpoints in this zone and to all endpoints from other zones, check the Public check box.
b. If you want only endpoints registered in this zone to use the service, check the Default check box.
c. If you want the service to be available to everyone, check Public and Default.
Step 6 Click OK to save your changes. The Services Definition Table appears.
Step 7 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 window 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.
c. Click OK to save the settings and exit the window.
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 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 zone, check the Public check box.
Step 5 If you want the service to be available to only users registered with the embedded gatekeeper, check the Default check box.
Step 6 If you want the service to be available to all users, check Public and Default.
Step 7 Click OK to save your changes. The Service Zone 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 simultaneously. Endpoints can register automatically or be registered manually. Endpoint that supports RAS protocol can register automatically.
The gatekeeper 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 window. |
To access the Zone Definition Table, click Zone Definition in the Application Parameter window. The Zone Definition Table appears (see Figure B-6).
To manually register an endpoint, perform the following steps:
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 If you want to use the Distance parameters of the embedded gatekeeper to restrict user access to remote zones, you must set the Max.Distance parameter. Enter a value between 0 to 255, inclusive, in the Max.Distance field. This value is compared to the Neighbor Distance value you assign to gatekeepers in the Neighbor Gatekeeper window. 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 that 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 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 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, perform the following steps:
a. Choose the service you want to enable.
b. Click Enable. A check mark appears in the Enable column of the services that are enabled.
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, you can:
a. Click Apply to save without exiting the window.
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 window 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.
c. After you have enabled all of the services you want the endpoint to use, click OK.
You can view and edit parameters of all endpoints registered in the zone. To view or edit an endpoint zone parameter, 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.
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 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 2 Click Add.
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 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.
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 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 a neighboring gatekeeper.
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.
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 window 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.
c. Click OK to save and exit the dialog box.
To edit a neighboring gatekeeper parameters, perform the following steps:
Step 2 Make the changes and then click OK.
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.
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 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 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.
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 window 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.
c. Click OK to save and exit the window.
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 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:
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.
You can modify the file for the specific Cisco IP/VC 3500 gatekeeper you want to configure or use it as is. The parameters are written to the units Flash memory after you complete setting all of the configuration parameters and run the upload software.
This section describes how to configure the embedded gatekeeper to use Cisco MCM proxy. Proxy can provide quality of service (QoS) and security for H.323 videoconference calls.
For the embedded gatekeeper to use proxy, the proxy service must register with the embedded gatekeeper. However, 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 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 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 setup a new proxy to register with the embedded gatekeeper, perform the following steps:
Step 2 At the prompt, type enable and press Enter.
Step 3 At the Password prompt, type the password required to obtain privileged access.
Step 4 At the privilege prompt, type config t and press Enter.
Step 5 At the prompt, type proxy h323 and press Enter. This command globally enable the proxy commands.
Step 6 At the prompt, specify the interface inside the router that you want to configure the proxy on. To specify the interface, type interface and press Enter.
Where:
interface is the interface type you want to install the proxy on. FastEthernet or serial interfaces are generally used for 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.
# is the physical location of the port that you want to use for the proxy.
Step 8 At the prompt type, h323 <H323 ID name> and press Enter.
Where H323 ID name is the name you assign to the proxy.
Step 9 At the prompt, type h323 gatekeeper ipaddr <embedded gatekeeper ipaddress> and press Enter.
Step 10 At the prompt, type h323 qos <ip-prec | rsvp> and press Enter.
Where ip-prec (ip precedence) and rsvp are mode of QoS.
|
Note If you configure the proxy to use RSVP, the WAN port must be set with RSVP parameters. |
Step 11 Issue a write command to write the configuration to MCM memory. At the prompt, type write and 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 in the looking in the Zone Definition table for the embedded gatekeeper in the Cisco IP/VC Configuration Utility.
To setup the embedded gatekeeper to use proxy services, perform the following steps:
Step 2 Select or enter the IP address of the current Cisco IP/VC 3525 Gateway and click Next.
Step 3 Enter the units 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 Gatekeeper. 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, type proxy.
Step 14 Click OK. The Neighbor Gatekeeper Table appears.
Step 15 Click OK. The Application Parameters window appears.
Step 16 Click Exit.
Posted: Mon Jun 5 12:29:15 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.