Setup guide

Gatekeeper
ip telephony gatekeeper
Description
For each H.323 endpoint gatekeeper stores its telephone numbers. So, gatekeeper knows all
telephone numbers for all registered endpoints. And it knows which telephone number is handled
by which endpoint. Mapping between endpoints and their telephone numbers is the main
functionality of gatekeepers.
If endpoint is registered to endpoint, it does not have to know every single endpoint and every
single telephone number, which can be called. Instead, every time some number is dialed, endpoint
asks gatekeeper for destination endpoint to call by providing called telephone number to it.
Wandy IP telephony package includes a very simple gatekeeper. This gatekeeper can be activated
by setting gatekeeper parameter to local. In this case the local endpoint automatically is registered
to the local gatekeeper. And any other endpoint can register to this gatekeeper too.
Registered endpoints are added to the /ip telephony voice-port voip table. Those entries are
marked as dynamic and can not be removed or changed. If there already was an voip entry with the
same IP address, it is marked as registred. Remote-address can not be changed for these entries too,
but registered voip voice ports can be removed - they will stay as dynamic ones. If there already is a
dynamic voip voice port and a static one with the same IP address is added, then instead of dynamic
entry, registered will appear.
Dynamic entries disappear when corresponding endpoint unregisters itself from the gatekeeper.
Registered entries are static and will stay even after that endpoint will be unregistered from this
gatekeeper.
Registered telephone numbers are added to /ip telephony numbers table. Here is exactly the same
idea behind dynamic and registered telephone numbers as it is with voip voice ports.
When an endpoint registers to the gatekeeper, it sends its own telephone numbers (aliases and
prefixes) within this registration request. /ip telephony numbers entry is registered to the endpoint
only if voice-port for that entry is local (not voip). If dst-pattern contains '.' or '_', it is sent as
prefix, otherwise - as alias. The known part of the dst-pattern is sent as prefix. If there is no known
part (dst-pattern is "_" or "...", for example), then this entry is not sent at all.
Property Description
gatekeeper (none | local | remote; default: none) - Gatekeeper type to use
• none - don't use any gatekeeper at all
• local - start and use local gatekeeper
• remote - use some other gatekeeper
remote-address (IP address; default: 0.0.0.0) - IP address of remote gatekeeper to use. If set to
0.0.0.0, broadcast gatekeeper discovery is used
remote-id (name) - name of remote gatekeeper to use. If left empty, first available gatekeeper will
be used. Name of locally started gatekeeper is the same as system identity
registered (read-only: yes | no) - shows whether local H.323 endpoint is registered to any
gatekeeper
registered-with (read-only: name) - name of gatekeeper to which local H.323 endpoint is