Library items tagged:

The following configuration is for a session that sets up a Cisco® router as a gatekeeper and H.323 proxy. It is minimally commented, so for further explanation please refer to the Cisco® information in Section 7. In this example, a single physical port has been used between the endpoint and the college’s site access router. The commands would have to be altered slightly in a different topology.
Polycom PathNavigator™ The Polycom® gatekeeper product supplied was PathNavigator™ 5.1. This is dedicated software that offers a gatekeeper and additional services such as logging and billing. Before installing, check the minimum hardware and software system requirements for the version that you wish to install.
The ECS (Enhanced Communications Server) is dedicated software that offers a gatekeeper and a number of additional associated services, such as logging and billing. Figure 2. A gnu-gk status port telnet sessionTesting was carried out using ECS version 3.2.2. Check the documentation for the version you are supplied with for system hardware and software requirements.
There are a few open-source gatekeeper implementations available on the Internet. This one was selected as it appears to be the most mature, and also because it has been tested at a limited number of Universities in the UK (and overseas) and has been found to inter-work with the GDS. The source code and the binary executables for a number of operating systems are available at:http://www.gnugk.org
The test Cisco® gatekeeper was a Cisco® MCM, running on a Cisco® 3662 router, using Cisco IOS® version 12.2(17). Gatekeeper configuration should be done by persons with experience of the Cisco® Command Line Interface, if possible. Gatekeeper configuration Enter gatekeeper configuration mode Before entering commands it is necessary to be at the correct administration level. This is reached by logging on to the router running the gatekeeper software, and entering the following commands:
The following pages describe the steps necessary for the configuration of:
Irrespective of the particular gatekeeper that is used, the same generic tasks need to be performed for every configuration.These are summarised here, but please note that they are not necessarily done in the same order for every configuration, and the details may vary. The individual gatekeeper configuration guides in sections 7-10 give fuller details of these steps.
It 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....
An essential part of the configuration of the campus gatekeeper relates to the implementation of the GDS (Global Dialling Scheme). E.164 is an ITU-T (International Telecommunication Union – Technical) recommendation (or standard) which defines the international public telecommunication numbering plan used in the PSTN (public subscriber telephone network), and some other data networks.
A gatekeeper is an H.323 service component that supports the deployment of an H.323 service. A gatekeeper provides management functions to terminals. These include address translation, call set-up, service access control, and call logging. These services are accessed by a terminal ‘registering’ with a particular gatekeeper. All terminals registered with a particular gatekeeper are in its ‘zone’. Gatekeepers are usually deployed on the network to reflect organisational or geographical network topology.