- Advisory services
- Consultations
- Network and technology policies
- Network and technology service docs
- Using Jisc community
- Network and technology service docs
- Domain name registration
- How to sign up
- Janet Support Manual
- Janet CSIRT
- Back-up services
- eduroam
- Backup Web Hosting
- Certificate Service
- Connection timeline
- Eligibility
- Janet 3G Buyer's Guide
- Janet 3G eduroam interoperablity authentication methods
- Janet Mail Services
- Janet Network Charges
- Janet Reach
- Janet Videoconferencing Feedback results
- Primary connections
- Supporting Business Continuity
- Business and Community Engagement (BCE) using Janet
- Cost
- Interconnect connections
- Connecting student accommodation
- Customer-owned routing equipment
- Obtaining a Janet IP Address Range
- Terms for the Provision of the Janet Service
- Upgrading your existing bandwidth and Janet router
- Fault reporting
- IP address assignment
- Janet Aurora
- Janet Netsight
- Janet txt
- Routers
- Network set-up
- Guest access
- Network time service
- Training
- Contact
- Primary Nameserver Service
- Secondary Nameserver Service
- Vscene
- Vscene
- Vscene updates and revisions
- Login Options
- Jisc and Ajenta partnership FAQ
- Learn more about Vscene
- Vscene Help and user guides
- Videoconferencing service policies
- ISDN
- Content providers
- Technical documentation
- Technical details
- Technical details
- Ports, IP addresses and Firewall information for Vscene
- Products
- Videoconferencing standards
- Data Sharing within Videoconferencing
- IP Videoconferencing
- Gatekeepers
- Videoconferencing equipment
- Security
- Videoconferencing safety
- Gatekeepers
- Configuring an H.323 Gatekeeper for use with JANET Videoconferencing
- Registering a Gatekeeper on the Global Dialing Scheme
- Configuring an H.323 Gatekeeper for use with JANET Videoconferencing
- The Role of the Gatekeeper in an H.323 Deployment
- The Global Dialling Scheme
- Pre-requisites
- Tasks
- Configuration Examples
- Cisco Multimedia Conference Manager
- Gnu-gk - The Open Gatekeeper
- Radvision ViaIP Enhanced Communications Server
- Polycom PathNavigator
- Appendix A – Cisco MCM Configuration Summary
- Appendix B – Gnu-gk Configuration Summary
- Appendix C – Radvision ECS Configuration Summary
- Appendix D – Polycom PathNavigator Configuration Summary
Appendix B – Gnu-gk Configuration Summary
Download as PDFThis 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 gatekeeperName=xxxxxx
[Gatekeeper::Auth]# Specify authentication method – necessary for next sectionAliasAuth=required;RRQdefault=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:1720101=sigip:xxx.xxx.xxx.xxx:1720102=sigip:xxx.xxx.xxx.xxx:1720default=reject
[GkStatus::Auth]# list of machines allowed to telnet to status portrule=explicitxxx.xxx.xxx.xxx=1xxx.xxx.xxx.xxx=1
[RasSrv::Neighbors]# specify the national directory gatekeepers for address resolution# use the names and addresses supplied by jvcs-mcgatekeeper-name1.ja.net=aaa.bbb.ccc.ddd:1719;*gatekeeper-name2.ja.net=zzz.yyy.xxx.www:1719;*
[RasSrv::LRQFeatures]# parameters of Location RequestsAlwaysForwardLRQ=1IncludeDestinationInfoInLCF=0ForwardHopCount=9CiscoGKCompatible=1 AcceptForwardedLRQ=1
[RasSrv::RewriteE164]# local zone prefix to strip from long E.164 addresses0044xxxxx=
#end of file
