TECHNICAL COMMUNICATION No. TC0622 Ed.

01

OmniPCX Enterprise Nb of pages : 11 Date : 29 December 2004

URGENT

NOT URGENT TEMPORARY PERMANENT

SUBJECT : GAKEEPER IN OmniPCX Enterprise ENVIRONMENT

Please find hereafter information regarding the internal and external Gatekeeper in an OmniPCX
Enterprise environment.

1
 OmniPCX Enterprise
GAKEEPER IN OmniPCX Enterprise
ENVIRONMENT

CONTENTS

1. DESCRIPTION ..............................................................................3
1.1. Reminder about Gatekeeper..................................................................... 3
1.2. Gatekeeper in OmniPCX environment ...................................................... 3

2. INTERNAL GATEKEEPER (IGK) ......................................................3

2.1. IGK restrictions ......................................................................................... 3
2.2. IGK management ..................................................................................... 3
2.2.1. IGK with Stand-Alone system............................................................................4
2.2.2. IGK with Network System .................................................................................6
2.3. External H.323 Endpoints ......................................................................... 7

3. EXTERNAL GATEKEEPER ...............................................................8

4. MAINTENANCE ...........................................................................8

Ed. 01 / 29 December 2004 1 TC0622

 OmniPCX Enterprise
GAKEEPER IN OmniPCX Enterprise
ENVIRONMENT

TC0622 2 Ed. 01 / 29 December 2004

 OmniPCX Enterprise
GAKEEPER IN OmniPCX Enterprise
ENVIRONMENT

1. DESCRIPTION

1.1. Reminder about Gatekeeper

A Gatekeeper is an H.323 device on a H.323 network that provides address translation (IP@ <=>
E164@) and control access to the network for H.323 terminals and Gateways.
A Gatekeeper can provide other services to the H.323 terminals and Gateways, such as call
signaling routing, bandwidth management, terminals authentication for example.
A Gatekeeper maintains a list of H.323 devices called "endpoints" in the network. The endpoints are
registered with the Gatekeeper at startup and have to request admission to a call from the
Gatekeeper to join others H.323 endpoints.

1.2. Gatekeeper in OmniPCX environment

In a OmniPCX environment, we can use 2 types of Gatekeeper: external Gatekeeper, which could
be hardware or software, or we can use the internal Gatekeeper of the Call Server since Release
5.0. Lx.

2. INTERNAL GATEKEEPER (IGK)

2.1. IGK restrictions

For the moment, the IGK doesn’t provide:
− call routing,
− bandwidth control,
− exchanges with other Gatekeepers,
− terminal authentication,
− static registration.

2.2. IGK management

Depending on if the OmniPCX Entreprise system is in Stand-Alone or in network configuration, there
are some points to take care of.

Ed. 01 / 29 December 2004 3 TC0622

 OmniPCX Enterprise
GAKEEPER IN OmniPCX Enterprise
ENVIRONMENT

2.2.1. IGK with Stand-Alone system

For a Stand-Alone OmniPCX Entreprise system, here are the parameters to set for the IGK:

2.2.1.1. IGK creation

Access path: mgr/IP/Gatekeeper Parameter/Create or Consult/Modify

Create : Gatekeeper Parameters

Node Number (reserved) : 3903

Instance (reserved) : 1
Gatekeeper Id : 0

Used + YES
Gatekeeper Name : IGK
Gatekeeper IP Address : 10.39.3.3
Gatekeeper Is WECC + NO
Alternative GK IP address :-------------

Name the IGK and for the IP@, give the address of the Call Server which will act as an IGK.
We can also indicate a backup GK if the primary GK doesn’t respond.
After, go to mgr/IP/IP Parameters/Internal Gatekeeper Number

Consult/Modify: IP Parameters

Node Number (reserved) : 3903

Instance (reserved) : 1
System_Option + Internal Gatekeeper number
Internal Gatekeeper number : 0

Indicate the number of the Gatekeeper created above that will work as IGK.

2.2.1.2. E164 list configuration

An E164 list contains E164 numbers which are the phone numbers of the OmniPCX Enterprise, and
so they can be joined via the INTIP/GD/GA that work with the IGK.
During the recording phase between an INTIP/GD/GA board and the IGK, the INTIP/GD/GA
supplies a list of E164 numbers that will be recorded by the IGK. The Gatekeeper makes a static
association between these numbers and the IP address of the INTIP/GD/GA board.
This means that each time an H.323 device addresses this Gatekeeper, asking for one of the
numbers associated with the INTIP/GD/GA, the Gatekeeper will return the INTIP/GD/GA IP address
to this device.

TC0622 4 Ed. 01 / 29 December 2004

 OmniPCX Enterprise
GAKEEPER IN OmniPCX Enterprise
ENVIRONMENT

So , in order to create the E164 list, go to mgr/IP/Gatekeeper E164 Number List/Create

Create: Gatekeeper E164 Number List

Node Number (reserved) : 1

Instance (reserved) : 1
E164 Number List Index : 0

Indicate the E164 list Number (integer value from 0 to 31).

Then, go to mgr/IP/Gatekeeper E164 Number List/Gatekeeper E164 Number/Create

Create: Gatekeeper E164 Number

Node Number (reserved) : 1

Instance (reserved) : 1
E164 Number List Index :0
E164 Number : 3000 (or 30 for a range of "30xx" sets)

In this menu, we create the phone numbers (E164 numbers) associated to the E164 list number.
One can put the full number or at least the 2 first digits of the number in order to create "a range" of
numbers.
Then one has to associate the IGK and E164 list number with the INTIP/GD/GA.

2.2.1.3. INTIP/GD/GA configuration

Go to mgr/Shelf/Board/Ethernet Parameters/Consult/Modify

Consult/Modify: Ethernet

Node Number (reserved) : 3903

Shelf Address : 1
Board Address : 0
Shelf - Board Address : 1-0

Interface Type + GD
Board IP Address : 10.39.3.100
NetMask IP : 255.255.0.0
Default Gateway IP Address : 10.39.254.254
IP Quality of service : 0
Board Ethernet Address : 00:80:9f:2f:f0:9c
Interworking with Gatekeeper + YES
Gatekeeper Id : 0
Numb. of sig. channels IP Phones : 0
Numb. of sig. channels inter ACT : 1
IP Domain Number : 0
E164 Number List Index : 0

Ed. 01 / 29 December 2004 5 TC0622

 OmniPCX Enterprise
GAKEEPER IN OmniPCX Enterprise
ENVIRONMENT

Tthere are 3 parameters to set:

• Internetworking with Gatekeeper = YES
• Gatekeeper ID
• E164 Number List Index
Then, in order for the INTIP/GD/GA to interwork with the IGK, the reboot of the INTIP/GD/GA is
mandatory.

2.2.2. IGK with Network System

In case of a OmniPCX Enterprise in networking configuration, there are additional parameters to
look at in order to have a good behavior between IGK and INTIP/GD/GA.
Consider a network of 2 nodes N1 and N2, IGK running on N1, with Hybrid/VoIP InterNode Link.
− On both N1 & N2, an INTIP/GD/GA interworks with an IGK
• If we only have one INTIP/GD/GA used for H.323 calls and inter-node calls, when we
activate "Interworking with Gatekeeper" both H.323 calls and inter-node calls will be
processed by the Gatekeeper.
Then an E164 list of each INTIP/GD/GA needs to contain the local VPN number(s) of the
node in order that the VPN overflow (VoIP inter-node calls) works.
Go to mgr/IP/IP Parameters

[ 27 ] Instances: IP Parameters

-> IP Address Type

Volume in dB for not IP phones
Transit on IP Boards
H323 Internode Protocol
IP TOS Sig
Fast Start
Internode call if GK not reachable => TRUE
DTMF_mode_H245
VoIP reserved1
RAS only with H323 term. => TRUE
VoIP reserved3
Direct RTP
Round trip delay request
Direct RTP For H323 Terminals
Time To Live Timer (sec)
Internal Gatekeeper number

The parameter Internode call if GK not reachable is used when the Gatekeeper
is no longer operational: basically all H.323 calls would failed but also VoIP internode calls.
Then when set to True , VoIP internode calls are treated as there was no IGK.
In case we don’t want to have VoIP internode call processed by the GK, the parameter RAS
only with H323 term. should be set to True. Like that, only calls from H323 devices
will be processed by the IGK. Moreover, we no longer need to put the local VPN number(s)
in the E164 lists.

TC0622 6 Ed. 01 / 29 December 2004

 OmniPCX Enterprise
GAKEEPER IN OmniPCX Enterprise
ENVIRONMENT

• In case there is more than 1 INTIP/GD/GA on the node, it’s possible to dedicate one
INTIP/GD/GA for H.323 calls, then the parameters Internode call if GK not
reachable and RAS only with H323 term. are not needed.

The parameter RAS only with H323 term. comes with the version E2.504.1.k but is
not the good one. For the moment the parameter VoIP reserved2 is the one to be used.
The parameter RAS only with H323 term. can be used since version E2.504.1.L.

− Only one node interworks with the IGK

In case we have only one INTIP/GD/GA on the node which should interwork with the IGK, the
parameter RAS only with H323 term. is mandatory and should be set to True.
If more than one INTIP/GD/GA is available on the system, one can be dedicated to H.323 calls.

2.3. External H.323 Endpoints

In order that the OmniPCX Enterprise can join H.323 endpoints (like PCs with netmeeting, ...), direct
abbreviated number must be created.
Since a gatekeeper is used, the parameter Call Type must be set to Normal.
Access path: mgr/Abbreviated Numbering/Direct Abbrev. Numbers/Direct Abbrev.
No Pref./Create

Create : Direct Abbrev.No Pref

Node Number (reserved) : 3903

Instance (reserved) : 1
Instance (reserved) : 1
Direct Abbr.No Prefix : 34

Call Number : #03234

Directory name : H323 Sets
Directory First Name : ------------
Barring + False
Overfl.Dir.Abbrev.No Pref. : --------
Auto.Attendant Calling Right : 0
Call Type + Normal
Timed Forward.Dir.Abbrev.No. : -------
Range Number : 255
Can Be Called By Name + NO
Displayed Name : H323 Sets
External DISA Dir.No. : --------

In the above example, with external H.323 sets in 34xx, we configure the abbreviated number 34
with a call number containing the trunk group prefix of the H.323 trunk group used with the IGK
(here #032), and the Call Type is set to Normal.

Ed. 01 / 29 December 2004 7 TC0622

 OmniPCX Enterprise
GAKEEPER IN OmniPCX Enterprise
ENVIRONMENT

3. EXTERNAL GATEKEEPER
In compare with an IGK, the configuration for an external Gatekeeper is the same except that we
don’t use the parameter mgr/IP/IP Parameters/Internal Gatekeeper Number.

4. MAINTENANCE
Here are some maintenance’s commands around the Gatekeeper.
On the Call Server :
− compvisu ras x y
This command allows to see how the INTIP/GD/GA is set regarding the Gatekeeper (x,y are the
crystal/board parameters of the INTIP/GD/GA).
For example, GD in 1-0 interworks with IGK 1 and has a E164 list 0:
compvisu ras 1 0
wait...

+===========================================================================+
| C O M P V I S U |
+---------------------------------------------------------------------------+
| Output of INTIP board declared on 1-0 |
+===========================================================================+
| BOARDS PARAMETERS |
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+
| Cr-Cp | Gatekeeper used | Gatekeeper number | e164 list number|
+---------------------------------------------------------------------------+
| 1-0 | yes | IGK: 1 | 0 |
+===========================================================================+

+===========================================================================+
| GATEKEEPERS PARAMETERS |
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+
|no GK| GK IP address | Gatekeeper name |GK WECC|Alternative GK |
+---------------------------------------------------------------------------+
| 1 |10.39.3.3 | IGK | no | Unused|
+===========================================================================+

+===========================================================================+
| E164 NUMBERS |
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+
| list number : 0 |
+---------------------------------------------------------------------------+
| 3300 || 3301 |
+===========================================================================+

TC0622 8 Ed. 01 / 29 December 2004

 OmniPCX Enterprise
GAKEEPER IN OmniPCX Enterprise
ENVIRONMENT

− Trace_Database.txt
This file contains the H.323 endpoints registered in the IGK.
• the file is under /usr2/com/ repertory,
• do a more or a cat on the Trace_Database file to see the endpoints registered:

(3903)xa039003> more /usr2/com/Trace_Database.txt

Endpoint: 1 @IP = 10.39.3.100 (GD in 1-0)

alias: e164 : 2200
e164 : 3300
e164 : 3301
h323-ID : GW_0_0_10.39.3.100

Endpoint: 2 @IP = 10.39.1.10 (PC with Netmeeting)

alias: e164 : 3400
h323-ID : PC Netmeeting

With INTIP:
On Call Server, command cmdcpl <crystal> <board> with option RAS or H323 .
• RAS => allow to see if INTIP is registered on the Gatekeeper,
• H323 => allow to see parameters linked to H323 on the INTIP.

(3901)xa039001> cmdcpl 0 11 RAS

Del to exit tool
You have selected a board with type : INTIPA
execution from 'RAS'

(00,11) GK MAIN
(00,11) State: GK is chosen and GW is registered
(00,11) The H323 Identifier Gateway from the CH: GW_0_11_10.39.1.101
(00,11) The H323 Identifier Gateway from the GK:
0000151764421468167978762172016945743461719
(00,11) The H323 Identifier GateKeeper: RVGK
(00,11) calls: 0
(00,11) TTL value: 178
(00,11) PregrantedARQ:
(00,11) preGranted_makeCall flag 0
(00,11) useGKCallSignalAddressToMakeCall flag 0
(00,11) preGranted_answerCall flag 0
(00,11) useGKCallSignalAddressToAnswer flag 0
(00,11) RasAddress : 10.39.3.10 : port 1719
(00,11) GK Identifier: RVGK
(00,11) No alternate GK list received from the GK RVGK

(00,11) 00000066-02128C4F: End of command execution

(3901)xa039001> cmdcpl 0 11 H323

Del to exit tool
You have selected a board with type : INTIPA
execution from 'H323'

Ed. 01 / 29 December 2004 9 TC0622

 OmniPCX Enterprise
GAKEEPER IN OmniPCX Enterprise
ENVIRONMENT

(00,11) +-------------------------------------------------------+
(00,11) | H323 Information sent by the CPU |
(00,11) +-------------------------------------------------------+
(00,11) | Inter-Node Protocol H323 : 1 |
(00,11) | Fast_Start : 1 |
(00,11) | Rtp direct global : 0 |
(00,11) | Rtp direct H323 : 0 |
(00,11) | Fax T38 : 0 |
(00,11) | Channel Number :16 |
(00,11) | Only_H323_World_With_RAS Boolean : 0 |
(00,11) | Ras Address : 10.39.3.10 : port 1719 |
(00,11) | Alternate Ras Address : 0.0.0.0 : port 0 |
(00,11) | the H323 Identifier GateKeeper: |
(00,11) | GK_is_WECC Boolean :0 |
(00,11) | Internode_calls_when_GK_not_reachable Boolean :0 |
(00,11) | GK must register 003 e164 number(s) |
(00,11) | 2 1 0 0 |
(00,11) | 2 1 0 1 |
(00,11) | 2 1 9 8 |
(00,11) +-------------------------------------------------------+
(00,11) 00000069-02141764: End of command execution

With GD/GA:
We need to:
• Log on the GD/GA (via config port of the GD/GA or by telnet from the call server).
• Do a telnet on itself by putting the port 4560 :
If @IP GD/GA = 10.39.3.100, from the GD => telnet 10.39.3.100 4560
At prompt MG, choice of the options RAS and H323 => same results as with an INTIP.

TC0622 10 Ed. 01 / 29 December 2004