Specifications
MultiVOIP Gatekeeper Software Guide 7 Services Window
44
Gatekeeper Defined Services
You can either define your own Gatekeeper services, or use any of the built-in
services, which are predefined internally and supported by the Gatekeeper.
Example of a Gatekeeper Service
You can define a service named TECHSUPP and register five different terminals that
provide technical support. Any call directed to TECHSUPP can connect to one of the
five terminals.
To do so:
1. Add a service with a prefix TECHSUPP.
2. Make sure the terminals register with the additional alias TECHSUPP.
3. When a call for TECHSUPP arrives, the Gatekeeper automatically routes the call
to one of terminals that provides the TECHSUPP Service.
Endpoints must be registered with the service name to receive calls for the service.
This is achieved using one of the following methods:
• The endpoint is pre-configured using its own configuration. Then, using RAS
messages, the endpoint is registered with a name or a phone number identical to
the service prefix.
• The service prefix is predefined for the endpoint, using the configuration
application of the Gatekeeper as an ID or phone number, and the Alias Giving
option is activated. See the description of the Alias Giving option in the
Parameters window chapter.
Built-in Gatekeeper-Defined Services
The current version of the Gatekeeper software supports the following services:
• Forward
• Zone Prefix 1 and 2
• Exit Zone
Forward
The Gatekeeper provides a Call Forwarding service, for which you define a prefix.
When a terminal wishes to notify the Gatekeeper to forward its calls, it requests the
Forward service using this prefix together with the new destination endpoint.
Subsequently, when the Gatekeeper receives a call for that terminal, it transfers the
call to the new endpoint (until the terminal deactivates the Forward service request).
Note: This Forwarding service does not rely on H.450.3 Forwarding procedures.