Displaying the built-in gatekeeper registration list

The IP gateway contains a built-in gatekeeper with which devices can register multiple IDs. IDs can be numbers, H.323 IDs (e.g. Fredsendpoint) or prefixes.

Up to 25 devices can be registered without a feature key. Feature keys can be purchased to increase this number.

Note: The IP gateway can register with its own built-in gatekeeper. The IP gateway then counts as one registered device. See Configuring gatekeeper settings.

Configuring the built-in gatekeeper

To start the gatekeeper, go to Network > Services and select the H.323 gatekeeper check box to open a port for the gatekeeper. (On the IP gateway, ports are not open by default for security reasons.) Then go to Gatekeeper, select Enabled in the Status field and click Apply changes. If you attempt to enable the built-in gatekeeper without opening the port, an error message is displayed.

Configuring neighboring gatekeepers

You can optionally configure the built-in gatekeeper with up to two neighboring gatekeepers. This means that if the built-in gatekeeper receives a request (known as an Admission Request or ARQ) to resolve an ID to an IP address and that ID is not currently registered with it then it will forward that request to its neighbor gatekeeper(s), as a Location Request (LRQ). The built-in gatekeeper will then use the information received from the neighbor(s) to reply to the original request.

You can also configure the behavior of the built-in gatekeeper on receipt of LRQs from another gatekeeper. It can:

send LRQs regarding unknown IDs to its neighbor(s)
reply to LRQs from other gatekeepers
accept LCFs (Locations Confirms) from non-neighboring gatekeepers

Refer to this table for assistance when configuring the built-in gatekeeper:

Field	Field description	Usage tips
Status	Enables or disables the built-in gatekeeper.	To use the built-in gatekeeper, you must enable it here.
Full proxy (Port A/Port B)	Controls the behavior of the built-in gatekeeper on receiving a directly-dialed (that is, not via the auto attendant or operator) call from a registered endpoint to an IP address or E.164 number. The options are: Disabled: The gatekeeper will check whether or not the call is allowed, but will not proxy the call through itself. The call will still be able to take place if the two endpoints are on the same network or if there is an explicit route between the endpoints' networks. Between ports (to registered aliases): This option allows calls dialed by E.164 number from a registered endpoint on one port to a registered endpoint on the other port. (The endpoints must be registered with either the built-in gatekeeper or with a neighbored gatekeeper.) The built-in gatekeeper will proxy the signaling and media for allowed calls through itself. Calls dialed by IP address will not be allowed. Between ports (any destination): For calls from a registered endpoint on one port to an endpoint on the other port, the built-in gatekeeper will proxy the signaling and media for allowed calls through itself. Note that for calls dialed by E.164 numbers, both endpoints must be registered with the built-in gatekeeper (or a neighbored gatekeeper). For calls dialed by IP address, only the calling endpoint must be registered.	To control gatekeeper behavior for calls into Port A, use the Full proxy (Port A) control. To control the proxy mode of gatekeeper behavior for calls into Port B, use the Full proxy (Port B) control. Options for Port B are not available if Port B is disabled (to enable Port B go to Network > Port B). For Port A, Between ports is not available as an option if Port B is disabled.
Neighbor gatekeeper 1 and 2	Enter the IP address(es), or hostname(s) (or <host>:<port number> to specify a port other than the default of 1719 on the neighboring gatekeeper), of the neighboring gatekeeper(s).	These are the gatekeepers to which the built-in gatekeeper will send an LRQ if it has received an ARQ to resolve an ID which it does not currently have registered. The built-in gatekeeper will then use the information received from the neighbor(s) to reply to the original request.
Accept LRQs	Configures the built-in gatekeeper to reply to LRQs from other gatekeepers.	These requests can come from any gatekeeper which has the IP gateway's built-in gatekeeper configured as one of its neighbors.
Forward LRQs for unknown IDs	Configures the built-in gatekeeper to send (or not to send) LRQs regarding unknown IDs to its neighbor(s). Choose from the options: Disabled: The IP gateway will only respond to LRQs about IDs registered with itself. It will not forward LRQs about IDs that are not registered with itself to neighboring gatekeepers. Enabled, using local return address: The IP gateway will put, in the LRQ, its own address as the return address for the LCF. Enabled, using received return address: The IP gateway will put, in the LRQ, the address of the gatekeeper that originated the request as the return address for the LCF. Use this option only if you are configuring the IP gateway to operate in an environment with a multiple-level gatekeeper hierarchy. For example, the 'received address' is required by the national gatekeepers connected to the Global Dialing Scheme (GDS).	Unless you have selected to Accept LRQs, you cannot configure the IP gateway to forward any LRQs. Enabling using received return address can be a significant security risk. Only use this setting with proper cause.
Accept LCFs from non-neighbors	This setting enables the built-in gatekeeper to accept LCF message responses from any IP address.	This setting is for use in environments with a multiple-level gatekeeper hierarchy. For example, this feature is required by the national gatekeepers connected to the Global Dialing Scheme (GDS). Enabling this setting can be a significant security risk. Only use this setting with proper cause.

Gatekeeper status

The number of registered devices is shown in the format X / Y where Y is the number of registered devices that your built-in gatekeeper is licensed for. Equally, the total number of registered IDs is shown as Z / 1000, where 1000 is the maximum number of registrations allowed over all registered devices.

Below these summary figures is a table showing individual registrations. Registrations can be viewed by registered ID (the "ID view") or by device (the "Registration view"), giving complete and easily searchable lists. Switch between the views by clicking on the appropriate button.

The Registration view shows the summary per device (also known as the registrant), while the ID view shows individual registrations. This means that registrations from the same device are not necessarily listed together in the ID view but the view can be sorted by Registrant or Index to help you identify IDs belonging to the same registrant.

ID view

Field	Field description	Usage tips
ID	The ID which the registrant has registered with the gatekeeper.	IDs can be numbers, H.323 IDs or prefixes.
Type	The type of registration.	One of: E.164 (digits), H.323 ID or Prefix.
Index	This registrations index within the total number of registrations that this registrant has made with the gatekeeper.	In the format X / Y where Y is the number of registrations that this registrant has made with the built-in gatekeeper, and X is this particular registration's position within the total. Therefore, if a device registered 3 IDs with the gatekeeper and this was the second registration to be made, the Index would be 2 / 3.
Registrant	The IP address of the device that this registration was made from.	If the remote device has indicated via the RAI (Resource Availability Indication) mechanism that it is close to its resource limit, the Registrant will be labeled as "almost out of resources".

Registration view

This view shows a one-line summary for each device registered with the built-in gatekeeper.

To deregister one or more devices (and all registrations for these devices), select the check boxes for the appropriate entries and then click Deregister selected.

Field	Field description	Usage tips
Registrant	The IP address of the device.	If the remote device has indicated via the RAI (Resource Availability Indication) mechanism that it is close to its resource limit, the Registrant will be labeled as "almost out of resources".
H.323 ID	The registered H.323 ID of the device.	To help identify registering devices, if the registrant has registered a H.323 ID (which will typically be its device name) that H.323 ID is shown here. If the device has registered multiple H.323 IDs, only the first is displayed.
Registered IDs	The number of registrations that this device has made with the built-in gatekeeper.	Click (view) to display individual registrations for the selected device. (The format is the same as the ID view, but the table only includes entries for one device.)
Registration time	The time today or date and time of the last registration.

Using the built-in gatekeeper to bridge between two networks

In some configurations, you might want callers on the Port A network to be able to dial directly to endpoints on the Port B network and/or vice versa (as opposed to using the operator or auto attendant). For endpoints registered with the built-in gatekeeper calls can be transparently routed through the IP gateway. For calls dialed by E.164 number, the dial plan must be correctly configured and both endpoints must be registered with the built-in gatekeeper. For calls dialed by IP address, only the calling endpoint must be registered with the IP gateway. Firstly, you must configure the built-in gatekeeper as follows:

Go to Network > Services and check H.323 gatekeeper for Port A and Port B.
Go to Gatekeeper and enable the built-in gatekeeper. Click Apply changes.
Set the IP gateway to use its built-in gatekeeper. Go to Settings > H.323 and click Add gatekeeper:
1. Type a name for the gatekeeper.
2. Enable H.323 gatekeeper usage.
3. For H.323 gatekeeper address, enter the IP address of the IP gateway (set the address to 127.0.0.1 or localhost).
4. For Gatekeeper registration type, select Gateway.
5. Type an H.323 ID for the IP gateway and if required, enter a dial plan prefix (or prefixes). Use of a dial plan prefix causes the IP gateway to make a second registration with the gatekeeper. The gatekeeper will forward any E.164 numbers starting with this prefix to the IP gateway.
6. Click Apply changes.
In the Settings > H.323 page, associate the gatekeeper that you have just created with both Port A and Port B.

For registered endpoints dialing by E.164 number:

When dialing an E.164 number, endpoints registered with the built-in gatekeeper can call endpoints on the same network directly, but when calling to an endpoint on the other side of the IP gateway, the IP gateway can detect this and the connection can be transparently routed through it. To use the built-in gatekeeper in this way, the dial plan must be correctly configured.

For the port or ports for which you want to allow calls to be bridged to endpoints on the other port, create an entry in the dial plan. For example, if you want to allow calls coming in on Port A to be bridged to endpoints on Port B, create a entry in the Port A dial plan as follows:

In the web interface, go to Dial plan > Port A and click Add rule.
Type a name for the rule.
For Condition, select Match any called number.
For Action, select Call this number $A using the built-in gatekeeper.
Click Add rule to add the rule to the dial plan.
Ensure that this rule will be matched - that is, make sure that it does not come after another 'Match any called number' rule in the dial plan.
Go to Gatekeeper and set Full proxy (Port A/Port B) to Between ports (to registered aliases).

When using the built-in gatekeeper in this way, you can configure the same dial plan for each port if you require callers on both ports to have this functionality.

For registered endpoints dialing by IP address:

When dialing an IP address, endpoints registered with the built-in gatekeeper can call endpoints on the same network directly, but when calling to an endpoint on the other side of the IP gateway, the IP gateway can detect this and the connection will be transparently routed through it. Only the calling endpoint must be registered with the IP gateway. To use the built-in gatekeeper in this way, the Full proxy (Port A/Port B) setting on the Gatekeeper page must be set to Between ports (any destination).

	IP GW 3510
	host: IPGW