This is a complete gatekeeper.ini file for an organisation wishing to connect to the JVCS-IP or a similar H.323 network. The file can be copied and pasted, edited, then saved in the openh323gk\bin folder. Comments can be added by preceding them with a # character for each line of comment. Where a value has ‘x’s substitute your own local details.

This configuration allows dial-out from the central JVCS-IP MCUs using E.164 (GDS) addressing and IP address. It also allows terminals in this gatekeeper’s zone to dial direct (out-of-service) using E.164 or IP. Remote terminals can dial in using IP address, but not using E.164 (assuming firewall configuration allows this).

# start of file
[Gatekeeper::Main]
Fourtytwo=42
# name your gatekeeper
Name=xxxxxx

[Gatekeeper::Auth]
# Specify authentication method – necessary for next section
AliasAuth=required;RRQ
default=allow

[RasSrv::RRQAuth]
# list of terminals that will register with this gatekeeper
# endpoint E164 alias and IP must match
100=sigip:xxx.xxx.xxx.xxx:1720
101=sigip:xxx.xxx.xxx.xxx:1720
102=sigip:xxx.xxx.xxx.xxx:1720
default=reject

[GkStatus::Auth]
# list of machines allowed to telnet to status port
rule=explicit
xxx.xxx.xxx.xxx=1
xxx.xxx.xxx.xxx=1

[RasSrv::Neighbors]
# specify the national directory gatekeepers for address resolution
# use the names and addresses supplied by jvcs-mc
gatekeeper-name1.ja.net=aaa.bbb.ccc.ddd:1719;*
gatekeeper-name2.ja.net=zzz.yyy.xxx.www:1719;*

[RasSrv::LRQFeatures]
# parameters of Location Requests
AlwaysForwardLR Q=1
IncludeDestinationInfoInLCF=0
ForwardHopCount=9
CiscoGKCompatible=1
AcceptForwardedLR Q=1

[RasSrv::RewriteE164]
# local zone prefix to strip from long E.164 addresses
0044xxxxx=
#end of file