Configuring gatekeeper settings

Type a name for the gatekeeper.

This is a useful way of quickly identifying a gatekeeper where you have configured more than one gatekeeper.

Enables the IP gateway to register with an H.323 gatekeeper.

When set to Disabled then no gatekeeper registrations are attempted with this gatekeeper (and existing registrations with this gatekeeper are torn down), regardless of other gatekeeper settings.

When set to Enabled registrations with this gatekeeper are attempted, and this gatekeeper can then be contacted for incoming and outgoing calls. If the gatekeeper does not respond, calls are still connected if possible unless gatekeeper use is set to Required (for the port on which a call arrived) on the Settings > H.323 page.

Identifies the network address of the gatekeeper to which IP gateway registrations should be made.

This can be specified either as a host name or as an IP address.

This field will have no effect if H.323 Gatekeeper usage (see above) is set to Disabled.

The gatekeeper can be either the built-in gatekeeper enabled on the Gatekeeper page (see Displaying the built-in gatekeeper registration list) or an external gatekeeper. To use the built-in gatekeeper enter "127.0.0.1". For an external gatekeeper, enter its host name or IP address.

Controls how the IP gateway identifies itself when registering with its configured gatekeeper.

Codian recommends that you use the Terminal / gateway option unless you are using a service prefix (in this case, use Gateway). Only use a different option if you are:

• having specific problems
• using the Cisco Gatekeeper (with or without a service prefix), in which case use Gateway (Cisco GK compatible)

  Refer to the list of Frequently Asked Questions (FAQ) in the Support section of the web site for more details about interoperability with gatekeepers.

Specify an identifier that the IP gateway can use to register itself with the H.323 gatekeeper.

Before the IP gateway can register any IDs with the H.323 gatekeeper, it must make a unit-wide registration.

This field is required for the gatekeeper registration.

This will have no effect if H.323 gatekeeper usage is disabled.

If the configured gatekeeper required password authentication from registrants, check the Use password box and type the password.

Note that where password authentication is used, the (Mandatory) H.323 ID to register will be used as the username.

Causes the IP gateway to make further registrations with the gatekeeper. The gatekeeper will forward any E.164 numbers starting with prefixes entered here to the IP gateway.

You can enter one or more dial plan prefixes. Use spaces to separate multiple prefixes.

This is an optional field.

Callers using endpoints also registered with the gatekeeper, can dial registered prefixes to access the IP gateway. The IP gateway will then determine what to do with the call depending on the rules in the dial plan. In this way, you can use dial plan rules to enable different types of calls to be handled in different ways by the IP gateway. For example, calls prefixed in one way could be forwarded directly to the operator and calls prefixed in another way could be forwarded to the auto attendant, or transferred directly to a call group.

Select this option if you want the IP gateway to inform the gatekeeper about its availability or non-availability. This information will be used by the gatekeeper when it is selecting where to place calls.

Only use this option where multiple IP gateways are registered with the same IP gateway dial plan prefix on the same gatekeeper.

When selected, the IP gateway will inform the gatekeeper when it is unavailable (that is, all its ports are already in use).

The ability of the IP gateway to send resource availability messages is useful in a network where there are multiple IP gateways or where there are several IP gateway blades in an MSE.

In an environment with multiple IP gateways registered with the same gatekeeper, that gatekeeper should favor devices in the available state when choosing where to place new calls.

For example, when one IP gateway sends the gatekeeper a message indicating that it is not available, the gatekeeper will then attempt to use a different IP gateway for new calls.

When all ports are in use, the IP gateway sends a message to indicate that it is not available; when one or more ports becomes available, the IP gateway sends a message indicating that it is available.

Displays the IP address of the gatekeeper currently being used by the IP gateway.

This information might be useful if the gatekeeper has been specified with a host name rather than with an IP address.

Displays the local IP address and port number that the IP gateway has registered with the gatekeeper.

This information might be useful if the IP gateway has more than one IP address, for instance if both Ethernet interfaces are in use.

The port via which the gatekeeper is connected or in the case of the built-in gatekeeper: Both ports (Internal GK).

If a gatekeeper is on the subnet local to either port, the IP gateway will list that port here. Otherwise, the IP gateway will use the IP routes (configured on the Network > Routes page) to determine on which port the gatekeeper is to be found. For example, there might be a route configured to the gatekeeper's subnet or the IP gateway will use the default route.

Usually, the port with which the gatekeeper is associated will be the same port as the one to which the gatekeeper is connected. The exception to this is the built-in gatekeeper which will both appear to be connected to both ports and can be used to bridge between two networks and associated with both ports.

Displays the number of 'alternate' gatekeepers configured on the H.323 gatekeeper. This figure comes from the gatekeeper itself; if there are any 'alternate' gatekeepers configured, the gatekeeper tells the IP gateway their IP addresses.

Where the configured gatekeeper has told the IP gateway about any configured 'alternate' gatekeepers and if the IP gateway loses contact with the configured gatekeeper, the IP gateway will attempt to register with each of the 'alternates' in turn. If none of the 'alternate' gatekeepers responds, the IP gateway will report that the registration has failed.

If the IP gateway successfully registers with an 'alternate' gatekeeper:

• the H.323 gatekeeper status will indicate that registration is with an 'alternate'
• the list of 'alternates' received from the new gatekeeper will replace the previous list
• the IP gateway will only revert back to the original gatekeeper if the 'alternate' fails and only if the original gatekeeper is configured as an 'alternate' on the current gatekeeper's list of 'alternates'

Note that if the IP gateway registers with an 'alternate' that does not itself supply a list of 'alternates', the IP gateway will retain the original list and if it loses contact with the current gatekeeper, each one will be attempted from the top again as before.

Displays the number of E.164 numbers plus H.323 IDs plus prefixes that the IP gateway has registered with the gatekeeper.

It also shows how many registrations are in progress but are not fully registered yet.