- 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 documentation
- Archive
- NAT, Firewalls and videoconferencing - H.323 Border Traversals
- Security guide for H.323
- Guide to reliable campus H.323 networks
- Configuring a Gatekeeper to use with Janet VideoConferencing
- Videoconferencing standards
- Video Displays, Signals and Formats
- Videoconferencing Quality
- Janet Videoconferencing Service check
- ISDN Dialup
- IP Videoconferencing
- Datasharing on Janet VideoConferencing Service
- Global Dialing Scheme explained
- Registering a Gatekeeper with the Global Dialing Service
- Joining a Vscene session to a 3rd party MCU
- Configuring a Gatekeeper to 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
- References
Pre-requisites
Download as PDFIt is advisable to read the JVCS-IP documentation before implementing an IP videoconferencing system or gatekeeper. This can be found at:
https://community.ja.net/library/janet-services-documentation/ip-videoco... and https://community.ja.net/library/janet-services-documentation/registerin....
Before configuring a gatekeeper it is necessary to inform the JVCS-MC of your intention to do so. This can be done on a web form found at
http://www.jvcs.ja.net/cgi-bin/vcng/mailform.cgi?cfg=gatekeeper
You will need to supply the name and contact details of a primary and alternative technical contact. You will also need to supply the IP address and DNS name of the gatekeeper host. The JVCS-MC needs these details in order to integrate your gatekeeper with the JVCS. They will respond with an e-mail to inform you when these details have been configured on the national directory gatekeeper. At this point they will supply you with a unique five-digit zone number for your gatekeeper’s zone.
You will need to refer back to all of this information when you come to configure your gatekeeper.
When your gatekeeper has been configured, it is suggested that you first test that it will resolve calls across the campus (between two endpoints which are both currently registered in the local zone). If possible, test also that endpoints registered can dial using E.164 numbers to an endpoint in another zone – and vice versa. There is no discrete gatekeeper testing available from the JVCS-MC, but when an H.323 endpoint is registered to use the service it will require a QA (Quality Assurance) test before being able to do so. This QA test will also prove that the gatekeeper has been configured correctly for compatibility with the JVCS.
