TC0027

TROUBLESHOOTING GUIDE No. TG0027 Ed.
01
OmniPCX Enterprise Nb of pages : 54 Date : 12 July 2005
SUBJECT : H323 ISSUES
This troubleshooting guide deals specifically with H323 issues.
1
OmniPCX Enterprise
TROUBLESHOOTING GUIDE No. 27 H323 ISSUES
CONTENTS
1. INTRODUCTION ..........................................................................5
2. REFERENCES................................................................................5
3. HISTORY......................................................................................5
4. THE BASICS OF H.323 .................................................................6

4.1. H323 Protocol Stack.................................................................................. 6
4.2. H.323 Short Description............................................................................ 6
4.3. RAS protocol Description........................................................................... 7
4.3.1. General Format of RAS .....................................................................................7
4.3.2. RAS Port............................................................................................................8
4.3.3. RAS Messages Description ................................................................................8
4.4. H.225.0 Call Signaling............................................................................ 10
4.4.1. H.225.0 Call Signaling Message Body ............................................................10
4.4.2. Basic Call Setup Signaling...............................................................................11
4.5. H.245 ..................................................................................................... 11
4.5.1. H.245 Message Body ......................................................................................12
4.5.2. H.245 Tunneling Mode ...................................................................................12
4.5.3. H.245 Message Types .....................................................................................12
4.6. “Fast Connect” (Fast Start) Mode ............................................................ 13
4.6.1. Initiating Fast Connect ....................................................................................13
4.6.2. Responding to a Fast Connect.........................................................................14
4.7. Third Party Pause and Rerouting (EmptyCapabilitySet)............................ 14
5. AVAILABLE H323 CONFIGURATION PARAMETERS IN OMNIPCX

ENTERPRISE ...............................................................................15
5.1. H323 Parameters into MAO database..................................................... 15
Ed. 01 / 12 July 2005 1 TG0027

OmniPCX Enterprise
H323 ISSUES TROUBLESHOOTING GUIDE No. 27
5.1.1. Object name: IP>IP Parameters>Fast Start.....................................................15

5.1.2. Object name: IP> IP Parameters>H323 Internode Protocol............................17
5.1.3. Object name: IP> Internode call if GK not reachable .....................................17
5.1.4. Object name: IP> RAS only with H323 term ...................................................17
5.1.5. Object name: IP> DTMF_mode_H245.............................................................18
5.1.6. Object name: IP> Inhibit the T38 negociation ................................................18
5.1.7. Object name: IP> Round trip delay request ....................................................19
5.1.8. Object name: IP> Direct RTP For H323 Terminals...........................................19
5.1.9. Object name: IP> Time To Live Timer (sec) .....................................................20
5.1.10. Object name: IP> Internal Gatekeeper number ..........................................21
5.1.11. Object name: IP> Direct RTP .......................................................................21
5.2. Checking the H323 Configuration from coupler online commands......... 23
5.2.1. How to enter in online command on an INTIP board......................................23
5.2.2. How to enter in online command on GD/GA board........................................23
5.2.3. How to Check H323 Configuration .................................................................23
5.2.4. How to Check RAS Information.......................................................................24
5.2.5. How to check RAS Statistics.............................................................................25
5.2.6. How to check registered endpoints in internal gatekeeper .............................25
6. TROUBLESHOOTING H323 ISSUES: FIRST LEVEL ANALYSIS .......26

6.1. No connection establishment.................................................................. 26
6.2. Call failure in case of ABC-F H323 inter-node calls ................................ 27
6.3. Call failure with H323 Netmeeting ......................................................... 27
6.4. Communication aborted ......................................................................... 28
6.5. Call Cut because of no answer to Round Trip delay Request................... 28
6.6. DTMF issue ............................................................................................. 28
6.7. Compressors declared on the H323 trunk group availability .................. 28
7. TROUBLESHOOTING: MORE IN DEPTH ANALYSIS......................29

7.1. Network investigation............................................................................. 29
7.1.1. Investigations with a network protocol analyzer .............................................29
7.1.2. Example of network traces..............................................................................29
7.1.3. Information in frames .....................................................................................34
TG0027 2 Ed. 01 / 12 July 2005

OmniPCX Enterprise
7.2. Procedures to capture Traces .................................................................. 38

7.2.1. H323 traces on INTIP coupler .........................................................................38
7.2.2. H323 traces on GD/GA coupler ......................................................................40
7.2.3. T3 traces on Call Server .................................................................................41
8. BEFORE CALLING ALCATEL’S SUPPORT CENTER ........................42
ANNEX A. H323 ISSUE DESCRIPTION.............................................43
ANNEX B. H.323 CONFIGURATION EXAMPLE ................................45
1. CONFIGURATION PART TO INTER-WORK WITHOUT GATEKEEPER45

1.1.1. GD or INTIP configuration ..............................................................................45
1.2. Configuration part to inter-work with gatekeeper .................................. 46
1.2.1. Configuration for external gatekeeper ...........................................................46
1.2.2. Configuration for internal gatekeeper ............................................................46
1.2.3. E164 number list configuration.......................................................................47
1.2.4. Gatekeeper E164 Number configuration ........................................................47
1.2.5. GD or INTIP configuration ..............................................................................47
1.2.6. Check configurations related to gatekeeper ...................................................48
1.3. Configuration part not related to gatekeeper use ................................... 50
1.3.1. Configuration of the IP trunk group and of the trunk group prefix .................50
1.3.2. Declaration of abreviated numbers (H323 device number).............................52
Ed. 01 / 12 July 2005 3 TG0027

OmniPCX Enterprise
TG0027 4 Ed. 01 / 12 July 2005

OmniPCX Enterprise
1. INTRODUCTION
This troubleshooting guide deals specifically with H323 issues.
It is assumed that the OmniPCX Enterprise Technical Documentation available on the Business
Partner Web Site in the section “e-Support>Technical Support>Communication Server>Technical
Documentation” has been read before. As the Technical Documentation describes the H323
subjects , this document will focus on H323 parameters and H323 issues troubleshooting.
INTIP and GD H323 gateways are compatible with H323 Version 2. In case of inter-working with
an external gateways running an higher version (example Version 4), the gateway running the
higher version has to fall back into lower version mode.
H.323 Version 1 and 2 supports H.245 over TCP, Q.931 over TCP and RAS over UDP.
H450 supplementary services (call forwarding, transfer,…) are not supported by the OmniPCX
Enterprise.
2. REFERENCES
[1] OmniPCX Enterprise Technical Documentation
Available on the Business Partner Web Site in the section “e-Support>Technical
Support>Communication Server>Technical Documentation”
[2] Technical Communication TC0584 : H323 Interoperability between OmniPCX Enterprise and
OmniPCX Office Test Report
[3] Form for description of H323 issue.
Available in the annex of this document : “Annex A: H323 Issue Description”
3. HISTORY
Ed 01: Creation of the document.
Ed. 01 / 12 July 2005 5 TG0027

OmniPCX Enterprise
4. THE BASICS OF H.323
4.1. H323 Protocol Stack
H 323User Interface
Multimedia Applications
90
80Data Media Control Terminal Control and
70
V.150 T.120 T.38 Audio Video RTCP H.225 H.245 H.225
60 .0 .0
Code Code
50 cs cs Call RAS
Est
40 G.71 H.26 Signal
1 1 ing Ouest
30
Nord
20 RTP
10
0
1er 2e trim.3e trim.4e trim.
trim.
4.2. H.323 Short Description
• What is H.323?
H.323 is a multimedia conferencing protocol, which includes voice, video, and
data conferencing, for use over packet-switched networks
• Elements of an H.323 System

• Terminals
− Telephones
− Video phones
− IVR devices
TG0027 6 Ed. 01 / 12 July 2005

OmniPCX Enterprise
− Voice Mail Systems

− Soft phones (e.g. Netmeeting®)
• Multipoint Control Units (MCU)
− Responsible for managing multipoint conferences (two or more endpoints
engaged in a conference). The MCU contains a Multipoint Controller (MC)
that manages the call signaling and may optionally have Multipoint
Processors (MPs) to handle media mixing, switching, or other media
processing.
• Gateways
− Gateways interface H.323 to other networks, including the PSTN, H.320
systems, and other H.323 networks (INTIPs, GA and GD boards can act as
H.323 Gateways)
• Gatekeeper
− The Gatekeeper is an optional component in the H.323 system which is
primarily used for admission control and address resolution. The gatekeeper
may allow calls to be placed directly between endpoints or it may route the
call signaling through itself to perform functions such as follow-me/find-me
and forward on busy (INTIPs, GA and GD boards act as H.323 Gateways)
• Border Elements
− Border Elements, which are often co-located with a Gatekeeper, exchange
addressing information and participate in call authorization between
administrative domains. Border elements may assist in call
authorization/authentication directly between two administrative domains or
via a clearinghouse.
4.3. RAS protocol Description
• Registration, Admission, and Status
• Used between the endpoint and its Gatekeeper in order to

− Allow the Gatekeeper to manage the endpoint
− Allow the endpoint to request admission for a call
− Allow the Gatekeeper to provide address resolution functionality for the
endpoint
• RAS signaling is required when a Gatekeeper is present in the network (i.e., the use
of a Gatekeeper is conditionally mandatory)
4.3.1. General Format of RAS
• RAS messages generally have three types

− Request (xRQ)
Ed. 01 / 12 July 2005 7 TG0027

OmniPCX Enterprise
− Reject (xRJ)
− Confirm (xCF)
4.3.2. RAS Port
• Typically, RAS communications is carried out via UDP through port 1719 (unicast)
and 1718 (multicast)
• Only UDP is defined for RAS Communications
• GRQ and LRQ may be send Multicast, but are generally sent unicast, all other RAS
messages are sent unicast.
4.3.3. RAS Messages Description
4.3.3.1. Gatekeeper Discovery Messages
• Gatekeeper Request (GRQ), Gatekeeper Reject (GRJ) and Gatekeeper Confirm

(GCF).
− When an endpoint comes to life, it should try to “discover” a gatekeeper by
sending a GRQ message to a Gatekeeper. If a Gatekeeper wishes to provide
service to the endpoint, it will send a GCF message to the endpoint,if not it
will send a GRJ message
4.3.3.2. Gatekeeper Registration Messages
• Registration Request (RRQ), Registration Reject (RRJ) and Registration Confirm

(RCF).
− Once a Gatekeeper has been “discovered”, the endpoint will then register with
the Gatekeeper in order to receive services. Endpoint will send an RRQ and
expect to receive either an RCF or RRJ.
− During the registration process, the Gatekeeper will assign an “endpoint
identifier” to the endpoint, which is to be used during subsequent
communications with the Gatekeeper. The endpoint will supply a list of
endpoint alias addresses and the Gatekeeper will indicate which ones it
accepts. The endpoint will indicate a “time to live” and the Gatekeeper may
accept that or a lower TTL value.
• Lightweight RRQs
− The “time to live” indicated in the RRQ tells the Gatekeeper when it may freely
unregister the endpoint due to inactivity. The endpoint may renew its
registration by sending either a full RRQ message or a “lightweight RRQ” (LW
RRQ). The LW RRQ message only contains a few elements and is only
intended to refresh the endpoint’s registration.
TG0027 8 Ed. 01 / 12 July 2005

OmniPCX Enterprise
4.3.3.3. Gatekeeper Admission Messages
• Admission Request (ARQ), Admission Reject (ARJ) and Admission Confirm (ACF)
− Once registered with a Gatekeeper, the endpoint may only initiate or accept a
call after first requesting “admission” to the Gatekeeper via the ARQ message
− The Gatekeeper may may accept (ACF) or reject (ARJ) the request to place
or accept a call.
4.3.3.4. Other RAS Messages
• Location Request (LRQ)

− The LRQ message is sent by either an endpoint or a Gatekeeper to a
Gatekeeper in order to resolve the address of an alias address (e.g., to turn a
telephone number into an IP address)
• Bandwidth Request (BRQ)

− An endpoint must send a BRQ subsequent to initial call establishment if the
actual bandwidth utilized is less than initially requested
• Disengage Request (DRQ)

− Once a call completes, the endpoint sends a DRQ message to the
Gatekeeper. The Gatekeeper may send a DRJ, but this is strongly
discouraged… if an endpoint is sending a DRQ, it means the call is over and
cannot be “rejected”!
− The DRQ is an opportunity for the endpoint to report information useful for
billing
− The Gatekeeper may also send a DRQ to force the endpoint to disconnect the
call
• Information Request (IRQ)

− The IRQ is sent by the Gatekeeper to the endpoint to request information
about one or all calls.
4.3.3.5. RAS Timers and Retries
RAS message Time-out value Retry count
GRQ 5 2
RRQ 3 2
ARQ 5 2
Ed. 01 / 12 July 2005 9 TG0027

OmniPCX Enterprise
BRQ 3 2
LRQ 5 2
DRQ 3 2
IRQ 3 1
4.4. H.225.0 Call Signaling
• H.225.0 Call Signaling is used to establish calls between two H.323 entities
• It was derived from Q.931 (ISDN call signaling), but was modified to be suitable for
use on a packet based network. ASN.1 was added to augment to Q.931 information
and is stored in the “User to User” Information Element from Q.931
4.4.1. H.225.0 Call Signaling Message Body
TPKT Header Q.931 Header IE IE ................................. IE UUIE
The UUIE refer to the “User-User Information Element”.

It should be the last octet in the chain, but some
implementations do not properly order IEs. It is
comprised of 0x7E, HH, LL, PD, and DATA. 0x7E is the
identifier for the User-User IE, HH and LL are the length
of DATA in network byte order, PD is a protocol
discriminator for ASN.1 (0x05) and DATA is the ASN.1
PER encoded “H323-UserInformation”.
Various Information Elements (IEs) that are appropriate for the

message type. These are listed in H.225.0, but note that any valid
Q.931 IE may be transmitted and should not result in a protocol
failure by the endpoint.
All messages have a Q.931 header that includes a single octet called the “protocol
discriminator” (0x08), three octets for the CRV (0x02, HH, LL, where 0x02 is the length
of the CRV and HH and LL are the two octets of the CRV in network byte order), and
single octet for the message type (specified in respective sections in Q.931).
Four octets that separate messages on the wire (necessary for TCP). They are defined in section 6 of
RFC 1006. There are 0x03, 0x00, HH, LL. HH and LL represent the entire message length,
including the TPKT header, in network byte order.
TG0027 10 Ed. 01 / 12 July 2005

OmniPCX Enterprise
4.4.2. Basic Call Setup Signaling
Setup
Call Proceeding
Optional
Progress
Alerting
GW Connect GW
Release Complete
4.5. H.245
H.245 is a protocol shared by a number of H.32x series protocols, including H.324M, which is used
for multimedia conferencing within 3GPP wireless networks.
Like Q.931, not everything inside H.245 is applicable to H.323
H.245 signaling is intended to be carried out in parallel to H.225.0 signaling and preferably
before the CONNECT message… waiting for the CONNECT will delay media establishment
and result in media clipping
H.245 provides “control” to the multimedia session that has been established
− Terminal capability exchange

− Master/Slave determinations
− Logical Channel Signaling
− Conference Control
Ed. 01 / 12 July 2005 11 TG0027

OmniPCX Enterprise
4.5.1. H.245 Message Body
TPKT Header H.245 PDU H.245 PDU ................................. H.245 PDU
Additional H.245 PDUs may be encoded following the first one.

However, many implementations cannot handle this and, as such, it
is ill-advised to place them end-to-end like this. It is strongly
recommended to place only one between each TPKT header, but do
be prepared for the case that more than one PDU does exist
following TPKT
H.245 messages are encoded in ASN.1 PER and follow the TPKT header in the H.245
Control Channel
Four octets that separate messages on the wire (necessary for TCP). They are defined in section 6 of
RFC 1006. There are 0x03, 0x00, HH, LL. HH and LL represent the entire message length,
including the TPKT header, in network byte order.
4.5.2. H.245 Tunneling Mode
H.245 is generally transmitted on a separate TCP connections by most older endpoints
Newer endpoints generally support “H.245 Tunneling”, which is the ability to place the H.245 PDUs
inside the H.225.0 Call Signaling channel
When tunneling, TPKT is not used
Multiple H.245 PDUs may be tunneled in a single H.225.0 message
4.5.3. H.245 Message Types
• Request
− terminalCapabilitySet (TCS)
The capability exchange (or “caps exchange”) allows two endpoints to
exchange information about what media capabilities they possess, such as
G.711, G.723, H.261, and H.263
TG0027 12 Ed. 01 / 12 July 2005

OmniPCX Enterprise
Along with the type of media, specific details about the maximum number of
audio frames or samples per packet is exchanged, information about support
for silence suppression (VAD), etc. are exchanged
The terminalCapabilitySet (TCS) must be the first message transmitted on
the H.245 Control Channel
− masterSlaveDetermination (MSD)
The slave device must yield to the requests of the master device and
reconfigure channels appropriately
− openLogicalChannel (OLC)
The OLC will contain one of the capabilities that was previously advertised by
the other endpoint
Voice and video channels are “unidirectional”, so each end must transmit an
OLC to open a logical channel
Within the OLC, a “session ID” is assigned
Session 1 is the default audio session, 2 is the default video session, and 3 is
the default data session
Additional session IDs may be used, but are assigned by the master in the
call
There is a relationship between H.245 sessions IDs and RTP: OLCs with the
same session ID are considered to be part of the same RTP/RTCP session
• Response
− terminalCapabilitySetAck
− masterSlaveDeterminationAck
− openLogicalChannelAck
• Command
− sendTerminalCapabilitySet
• Indication
− UserInput (to send DTMF)
4.6. “Fast Connect” (Fast Start) Mode
Fast Connect is a means of establishing an H.323 call with as few as two messages. With the use of
Fast Connect, there is no need to open an H.245 channel, as long as all needed media can be
negotiated via Fast Connect.
4.6.1. Initiating Fast Connect
Ed. 01 / 12 July 2005 13 TG0027

OmniPCX Enterprise
When transmitting a SETUP message, the endpoint will populate the fastStart element with
OpenLogicalChannel messages from H.245 (Note: these are just the data structures, not the entire
H.245 “message”).
Each OLC represents a proposed channel in either the “forward” (transmitting from the caller to the
called party) or the “reverse” (transmitting from the called to the calling party) direction.
Each OLC with the same session ID number is considered alternate “proposals” (i.e., if two
proposals are made for session ID 1, only one of the two may be selected)
4.6.2. Responding to a Fast Connect
To “accept” Fast Connect, an endpoint may select any fastStart element in the SETUP message,
populate the necessary data fields (as specified in H.323), and return a fastStart element in any
message to the caller.
An endpoint “rejects” Fast Connect by either explicitly indicating so (there is a flag for this), initiating
any H.245 communications, or providing an H.245 address for the purposes of initiating H.245
communications.
Until Fast Connect is accepted or rejected, the calling endpoint may not initiate H.245 procedures
(there is a exception to this rule in H.323v4 designed to avoid race conditions that would otherwise
exist)
4.7. Third Party Pause and Rerouting (EmptyCapabilitySet)
H.323v2 defined a mechanism whereby a third party may “pause” an endpoint and then re-route
the call.
This is done be sending an “empty capability set” (TCS=0 or ECS).
The reception of this results in the receiver closing its transmit channels and awaiting to be awoken.
While it is “paused” the re-routing entity may re-route the call
This mechanism is not initiated by the OmniPCX Enterprise (“Direct RTP for H323
Terminals” always set to NO), but supported if initiated by the end point.
Once re-routed, the re-routing entity will transmit a non-empty capability set, which indicates the
capabilities of the new remote endpoint.
Upon leaving the paused state, the endpoint shall “reset” its H.245 state machine and re-negotiate
master/slave, open channels, etc.
When leaving the paused state, a TCS message is not sent, as it is considered the responsibility of
the re-routing entity
TG0027 14 Ed. 01 / 12 July 2005

OmniPCX Enterprise
5. Available H323 Configuration Parameters in OmniPCX Enterprise

H323 communications are impacted by the configuration parameters. This chapter describes the
H323 parameters values and explain how to check the configured values.
5.1. H323 Parameters into MAO database
5.1.1. Object name: IP>IP Parameters>Fast Start
This parameter is set to TRUE by default.
Fast Start & Tunneling mode TRUE or FALSE
• Description:
− FALSE
all the H323 calls will be initiated in normal start or “slow start” mode, that
means the following channel parameters, Port number and IP address to
which the RTP packets must be sent and the used Codec are exchanged in
H245 messages. Moreover in “slow start” mode the OmniPCX Enterprise will
always act without H245 Tunneling, thus the H245 messages are exchanged
in a new TCP session.
Network Trace Example: tunneling mode information in Setup message
The tunneling mode information must be

sent in each H.225.0 signaling message
Network Trace Example: H.245 Transport Address exchange if “tunneling=False”
Ed. 01 / 12 July 2005 15 TG0027

OmniPCX Enterprise
@IP & port number to be used for the new

TCP session over which the H.245 PDUs will
be exchanged. Frame 13, 14 & 15 shows
the new TCP session establishment
− TRUE:
all the H323 calls will be initiated in “Fast Connect” mode , that means
following channel parameters, Port number and IP address to which the RTP
packets must be sent and the used Codec are sent in the setup message for
the caller and in the “Alerting” or “Connect” message for the called side.
Note: Fast Start is an option of H323v2. Thus a H323 gateway can be

compliant H323v2 without supporting Fast Start
Network Trace Example: “Faststar”t information available in the Setup message
Ethereal detects the « Faststart” element

Codec & framing
Voice session ID(1)
@IP & port number to which the other end

should send the RTP packets
@IP & port number to which the other end

should send the RTCP packets
TG0027 16 Ed. 01 / 12 July 2005

OmniPCX Enterprise
5.1.2. Object name: IP> IP Parameters>H323 Internode Protocol
H323 Internode Protocol TRUE or FALSE
• Description:
− FALSE
Proprietary messages are used for the Internode protocol.
− TRUE
Standard H323 messages are used in a non standard H323 implementation
for the Internode protocol; in this mode, we use Fast start with tunneling, but
“Terminal capabilities Set” and “Master/Slave determination” messages are
not exchanged.
Note: This parameter has to be set to false if an LIOE board is involved in the internode
communication.
5.1.3. Object name: IP> Internode call if GK not reachable
This parameter is set to FALSE by default.
Internode call if GK not reachable TRUE or FALSE
• Description
− FALSE
if the Gatekeeper is not reachable, the internode calls are not authorized.
− TRUE
Even if the Gatekeeper is not reachable, the internode calls are authorized.
5.1.4. Object name: IP> RAS only with H323 term
This parameter is set to FALSE by default.
RAS only with H323 term TRUE or FALSE
• Description
− FALSE
The Gatekeeper is used only for communication with external H323
gateways, it is not used for internode communications.
− TRUE
The Gatekeeper is used for communications with external H323 gateways
and for internode communications.
Note: if the “RAS only with H323 term “parameter is set to TRUE, then the
“Internode call if GK not reachable “parameter must also be set to TRUE.
Ed. 01 / 12 July 2005 17 TG0027

OmniPCX Enterprise
5.1.5. Object name: IP> DTMF_mode_H245
H245_DTMF_mode TRUE or FALSE
• Description
− TRUE
DTMF has to be transmit by remote gateway in “Code ASCII” mode. In this
mode, only the ASCII code of key is transmitted.
− FALSE
DTMF has to be transmit by remote gateway in “Signal” mode. In this mode,
the ASCII code of key is transmitted with the signal duration information.
Network Trace Example: DTMF sent in “signal” type mode (parameter set to FALSE)
UserInput Indication sent in « signal » type

mode.
5.1.6. Object name: IP> Inhibit the T38 negociation
This parameter is set to FALSE by default to enable T38 use.
Inhibit the T38 negotiation TRUE or FALSE
• Description
TG0027 18 Ed. 01 / 12 July 2005

OmniPCX Enterprise
− TRUE
The fax T38 capability is disabled
− FALSE
The capabilities exchanges will contain the T38 capability.
Note: In some case of H323 inter-working trouble, it could be necessary to set this parameter to
TRUE; but in that case T38 can’t be used.
Network Traces Example: Fax T38 Capability sent in TCS
5.1.7. Object name: IP> Round trip delay request
Round trip delay request TRUE or FALSE
• Description
− TRUE
The round-trip delay mechanism is enabled. The gateway send every 5 -7
seconds a round trip delay request and the remote gateway has to answer to
this message. This mechanism allows to check that the link is always up.
Network Traces Example: RTDRequest and RDTResponse during a call
− FALSE
The round-trip delay mechanism is disabled.
5.1.8. Object name: IP> Direct RTP For H323 Terminals
This parameter if present has to be set to FALSE.
Direct RTP For H323 Terminals TRUE or FALSE
Ed. 01 / 12 July 2005 19 TG0027

OmniPCX Enterprise
• Description
Currently, the “Direct RTP for H323 terminals” feature is partially implemented,
so until the feature is not fully implemented, this parameter must be set to FALSE.
5.1.9. Object name: IP> Time To Live Timer (sec)
This parameter is set to 180 by default.
Time To Live Timer (sec) -1 to 3600
• Description
Enter an integer value within the following ranges: 1 to 3600
Time to live Timer (sec)
This attribute is used to set the monitoring timer value between the INTIP/GD
board and the gatekeeper.
Values -1 and 0 = no timer: the value is set by the Gatekeeper.
The “time to live” indicated in the RRQ and Lightweight RRQs tells the
Gatekeeper when it may freely unregister the endpoint due to inactivity.
Network Traces Example: TimeToLive Timer sent in RRQ message by the H323 EndPoint and Response
sent by the Gatekeeper. The EndPoint sensd a TTL Timer of 60s, this is the value configured in the PBX, and the
Gatekeeper sends back a value of 300s, this value will now be taken in account by the PBX to send the next
LightWeight RRQ.
60s TTL Timer
300s TTL Timer
TG0027 20 Ed. 01 / 12 July 2005

OmniPCX Enterprise
5.1.10.Object name: IP> Internal Gatekeeper number
This parameter is set to “-1” by default.
Internal Gatekeeper number -1 to 7
• Description
Enter an integer value within the following ranges: -1 to 7
This is the Internal Gatekeeper number which, if used should be declared in the
GATEKEEPER PARAMETERS object.
-1 means none of the managed Gatekeepers is an internal Gatekeeper.
WARNING : Check in the GATEKEEPER PARAMETERS object that the
Gatekeeper parameters are correct.
5.1.11. Object name: IP> Direct RTP
Direct RTP TRUE or FALSE
• Description
− FALSE
The voice is compressed/decompressed at caller and called party level, but
also on each passage of the intermediate gateway. Compressor resources
are taken on the board which manage the trunk.
− TRUE
The Direct RTP in network is a functionality allowing a direct RTP flow (voice
flow) to be set up during a network call (IP trunk group seizure) between the
compressors nearest to the caller and called party equipment (compressors of
the set or of the associated gateway). So in other words the voice is not
decompressed/recompressed at intermediate compressor level in this case,
but only on those placed nearest to the caller and called party equipment.
This allows a minimum of compression/decompression.
Warning: When the parameter is set to TRUE: for UA or Analog sets, the call
Handling chooses a compressor on the nearest GD or INTIP board to the
caller into the shelf; this board could be different of the board managing the
trunk.
To check if a call has been initiated in DIRECT RTP Mode, run “t3” traces on
the PBX and start a call. If the Q931 Information Element “EI_RTP_INFO” is
present in the Setup message then the call is initiated in DIRECT RTP Mode.
T3 Trace Example: Call initiated in DIRECT RTP Mode
Ed. 01 / 12 July 2005 21 TG0027

OmniPCX Enterprise
EI_RTP_INFO Information
Element
T3 Trace Example: The same call with DIRECT RTP Parameter set to False
TG0027 22 Ed. 01 / 12 July 2005

OmniPCX Enterprise
5.2. Checking the H323 Configuration from coupler online commands

Some information on H323 configuration can be checked from coupler online commands.
5.2.1. How to enter in online command on an INTIP board
With mtch account (before R5.1.2) and mtcl account (from R5.1.2), you can access to coupler online
commands with the following command: (xx=Crystal Id; yy=Coupler id) :
(145)xa000045> cpl_online xx yy
000066F4-13965E14: Connected to Crystal 0 Coupler 2
Escape character is '^D'
INTIP:
5.2.2. How to enter in online command on GD/GA board
Log on the GD with telnet. When you are logged on the GD, type the following commands:
b)log on H323 trace port 4560
[admin@eMGD admin]$ telnet 155.132.130.10 4560
Trying 155.132.130.10...
Connected to 155.132.130.10.
Escape character is '^]'.
TRACE redirected to TELNET
0001856D-180DD6A0: Telnet_user ev EST_IND from ip
MG:
5.2.3. How to Check H323 Configuration
Hereafter an example of H323 information obtained when gatekeeper is not configured.

MG:H323
+-----------------------------------------------------------------+
| H323 Informations sent by the CPU |
+-----------------------------------------------------------------+
| Inter-Node Protocol H323 : 1 |
| Fast_Start : 1 |
| Rtp direct global : 1 |
| Rtp direct H323 : 0 |
| Fax T38 : 1 |
| Channel Number :06 |
| Only_H323_World_With_RAS Boolean : 0 |
Ed. 01 / 12 July 2005 23 TG0027

OmniPCX Enterprise
| Ras Address :0.0.0.0: port 0 |

| Alternate Ras Address :0.0.0.0: port 0 |
| the H323 Identifier GateKeeper: |
| GK_is_WECC Boolean :0 |
| Internode_calls_when_GK_not_reachable Boolean :0 |
| GK must register 000 e164 number(s) |
+-----------------------------------------------------------------+
000001BE-0060E535: End of command execution
MG:
Hereafter an example of H323 information obtained when gatekeeper is configured.

MG:H323
+----------------------------------------------------+
+----------------------------------------------------+
| Inter-Node Protocol H323 : 1 |
| Fast_Start : 1 |
| Rtp direct global : 1 |
| Rtp direct H323 : 0 |
| Fax T38 : 1 |
| Only_H323_World_With_RAS Boolean : 0 |
| Ras Address :172.25.33.46: port 1719 |
| the H323 Identifier GateKeeper: |
| 208 |
| 305 |
| 100 |
| 700390677151 |
| 34500 |
+----------------------------------------------------+
00000003-00005C80: End of command execution
5.2.4. How to Check RAS Information
RAS information is available when a gatekeeper is used.
Hereafter an example of information obtained when gatekeeper is not configured.
MG:RAS
This GW doesn't interwork with GK
000001BF-00610D87: End of command execution
Hereafter an example of information obtained when gatekeeper is configured.
TG0027 24 Ed. 01 / 12 July 2005

OmniPCX Enterprise
MG:RAS
GK MAIN
State: GK is chosen and GW is registered
The H323 Identifier Gateway from the CH: GW_0_0_172.25.33.41
The H323 Identifier Gateway from the GK: IGK_end2
The H323 Identifier GateKeeper:
calls: 0
TTL value: 180
PregrantedARQ:
preGranted_makeCall flag 0
useGKCallSignalAddressToMakeCall flag 0
preGranted_answerCall flag 0
useGKCallSignalAddressToAnswer flag 0
RasAddress :172.25.33.46: port 1719
GK Identifier:
No alternate GK list received from the GK
00000004-00005DFA: End of command execution
5.2.5. How to check RAS Statistics
MG:rasstat
RRQ Message(s): 1
lightweight RRQ Message(s): 1
RCF Message(s): 2
RRJ Message(s): 0
00000005-0000609D: End of command execution
MG:Connection closed by foreign host.
5.2.6. How to check registered endpoints in internal gatekeeper
(1)maskali> more /usr2/com/Trace_Database.txt

Endpoint: 1 @IP = 192.168.65.86
alias: e164 : 10100
e164 : 10101
h323-ID : 10100
h323-ID : 10101
Endpoint: 2 @IP = 192.168.65.93

alias: e164 : 208
e164 : 305
h323-ID : GW_2_0_192.168.65.93
Ed. 01 / 12 July 2005 25 TG0027

OmniPCX Enterprise
6. Troubleshooting H323 issues: First Level Analysis
6.1. No connection establishment
• Run t3 traces and check following Information Elements in the setup message
− EI_IP_TYPE_TERM
This IE must be present, if not the trunk is not an H323 IP trunk
− EI_IP_INFOS
Check if the codec used is in accordance with the remote H323 end point.
− EI_RTP_INFO
IE not present in the Setup message means the parameter “Direct RTP” is set to
False
− CALLED_NUMBER
Check if the called number is in accordance with the end point numbering
plan.
If t3 traces show that the call handling release the call immediately after it receives the setup;
example of traces in R5.1.2 hereafter:
mtracer started ...
______________________________________________________________________________
| (754038:000210) Physical-Event :
| long: 52 desti: 0 source: 0 cryst: 1 cpl: 0 us: 0 term: 0 type a5
| tei: 0 >>>> message received : SETUP [05] Call ref : 00 0d
| SENDING COMPLETE
|______________________________________________________________________________
|
| IE:[04] BEARER_CAPABILITY (l=3) 80 90 a3
| IE:[18] CHANNEL (l=1) a3 -> T2 : Any B channel
| IE:[6c] CALLING_NUMBER (l=12) -> 00 81 Num : 3127624036
| IE:[70] CALLED_NUMBER (l=5) -> 80 Num : 8660
| IE:[7d] HLC (l=2) 91 81
|______________________________________________________________________________
______________________________________________________________________________
| (754038:000211) 907: Send_IO1 (link-nbr=2, sapi=0, tei=0) :
| long: 23 desti: 0 source: 15 cryst: 1 cpl: 0 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : REL COMP [5a] Call ref : 80 0d
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=3) 81 81 80 -> [81] UNALLOCATED NUMBER
|______________________________________________________________________________
(1)xa000000>
TG0027 26 Ed. 01 / 12 July 2005

OmniPCX Enterprise
Check that the number of digits received in H323 setup message minus the value set in the
parameter “mgr>Trunk Groups >Trunk Group >Nb of digits unused (ISDN):” match with the
number of digit processed by the call handling:
• Try to establish the call in Slow Start instead of Fast Start (see section 5.1.1 for the
configuration in Slow Start)
• In case of an interoperability issue with Omni PCX Office, refer to the Technical
Communication TC0584 to check the configuration
6.2. Call failure in case of ABC-F H323 inter-node calls
In case of inter-node call failures or reset of the IP interface board, check the consistency over all
nodes of the network of the parameter “H323 Internode Protocol” (see section 5.1.2).
This parameter must be set to false if an LIOE board is involved in the inter-node communication.
To check the configuration of that parameter in the IP interface boards, use the command H323
(see section 5.2.3)
6.3. Call failure with H323 Netmeeting
Issue: H323 Call from Netmeeting to an OmniPCX Enterprise set doesn't work. The called set rings
and after off-hook, the call is released.
This issue is related to the winsock stack used on the PC . The analysis of the network traces
shows that Netmeeting rejects the frame "OpenLogicalChannel", but Netmeeting doesn't indicate
the reason of the reject.
Note: the frame "OpenLogicalChannel" sent by the OmniPCX Enterprise is correct.
Correction: On the PC running Netmeeting, modify the registry to deactivate

Winsock2 like hereafter:
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\Software\Microsoft\Internet
Audio\NacObject\DisableWinsock2]
"DisableWinsock2"=dword:00000001
[HKEY_LOCAL_MACHINE\Software\Microsoft\Conferencing\RRCM]
"DisableWinsock2"=dword:00000001
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Ed. 01 / 12 July 2005 27 TG0027

OmniPCX Enterprise
6.4. Communication aborted
• Run t3 traces and check the cause of the call aborting in the “Disconnect” or “Release”
message
• If the reason of disconnect is not relevant, start deeper investigation if possible using
an Network Sniffer as described in section 7.1 or the H323 traces on the Gateway
itself (INTIP or GD/GA) as described in section 7.2
6.5. Call Cut because of no answer to Round Trip delay Request

The H323 communication is cut because the Cisco Gateway doesn’t answer to the "Round Trip
Delay” Request:
- Cisco does not comply to the standard because it is mandatory to answer to a "Round Trip Delay
request".
The following work around can be applied: set the parameter IP>Round Trip Delay Request to
FALSE.
NOTE : if the mechanism is enabled on the PBX side and if the remote doesn’t answer, the H323
communication will be cut off when a timeout (near 30 seconds) has elapsed.
Some external gateways doesn’t comply to the standard, in that case the work around must be
applied.
The Coupler must be restarted to take into account the parameter change.
6.6. DTMF issue

DTMF are send through H245 Signalling.( Commands to the OmniPCX Enterprise are not sent in
Q23 but with H245 protocol. DTMF tone detectors are therefore not required.)
VoIP devices should use out of band DTMF signalling for greater reliability and lower computational
requirements.
See section 5.1.5 for an example of DTMF Network Traces
6.7. Compressors declared on the H323 trunk group availability

In case of compressors availability issue , check the accesses declared on the H323 trunk
group (see System Documentation: ABC link through IP \Configuration procedure – IP Trunk
Group)
For all compressors on the GIP6 and GIP4-4 boards to be useable, two accesses must be
declared on the IP trunk group.
TG0027 28 Ed. 01 / 12 July 2005

OmniPCX Enterprise
The following table gives the compressors distribution on GIP boards:
Access 0 Access 1
1 GIP6A or 1 GIP4-1 8 compressors 0
2 GIP6A or 2 GIP4-1 16 0
compressors
1 GIP6 or 1 GIP4-4 16 16
compressors compressors
2 GIP6 or 2 GIP4-4 32 32
compressors compressors
Caution: There is no message requiring these two accesses to be created. If only one
access is created, only half the compressors will be available.
7. Troubleshooting: More in depth Analysis
7.1. Network investigation
7.1.1. Investigations with a network protocol analyzer
Network traces can be captured with a "network protocol analyzer" like ethereal. (ethereal tool is
available on the web site: www.ethereal.com )
With this tool you can check the captured H323 frames. (see description and example in section :
“H323 Frames Examples “).
7.1.2. Example of network traces
Ed. 01 / 12 July 2005 29 TG0027

OmniPCX Enterprise
Call Normal Start without H245 tunneling
The call was made in following context: Normal start

Call from « set 34500 »/172.25.33.50---to---172.25.33.62/ « set 10100 »
Called set is ringing; off hook:
Start of H245 negotiation
Start of RTP flow
On hook on « set 3500 »/172.25.33.50; this lead to End of H323 Session
TG0027 30 Ed. 01 / 12 July 2005

OmniPCX Enterprise
REMARK: a “normal” call will always be initiated without H245 tunneling mode
Ed. 01 / 12 July 2005 31 TG0027

OmniPCX Enterprise
7.1.2.1.Call Fast Start
The call was made in following context: Fastl start
Called set is ringing; off hook: Start of H245 negotiation through same TCP socket as H225
RTP Flow
On hook on « set 3500 »/172.25.33.50; this lead to End of H323 Session
TG0027 32 Ed. 01 / 12 July 2005

OmniPCX Enterprise
7.1.2.2.Call with GK

Gatekeeper IP address is 172.25.33.46
Ed. 01 / 12 July 2005 33 TG0027

OmniPCX Enterprise
7.1.3. Information in frames
7.1.3.1. H225: Setup
In that frame we can see the H323 version, the binary version of the H323 gateway.
H323:Version 2
H323 Gateway Name
And Gateway Binary version
TG0027 34 Ed. 01 / 12 July 2005

OmniPCX Enterprise
7.1.3.2. RAS: RegistrationRequest
Ed. 01 / 12 July 2005 35 TG0027

OmniPCX Enterprise
7.1.3.3.RAS: RegistrationConfirm
7.1.3.4. RAS: AdmissionRequest
TG0027 36 Ed. 01 / 12 July 2005

OmniPCX Enterprise
7.1.3.5.RAS: AdmissionConfirm
7.1.3.6.RAS: DisengageRequest
Ed. 01 / 12 July 2005 37 TG0027

OmniPCX Enterprise
7.1.3.7.RAS: DisengageConfirm
7.2. Procedures to capture Traces
7.2.1. H323 traces on INTIP coupler

1) log on mtch account (from R5.1.2, use mtcl account):
(145)xa000045> su - mtch
Password:
2) Set Traces on : (xx=Crystal Id; yy=Coupler id)
(145)xa000045> cpl_online xx yy
000066F4-13965E14: Connected to Crystal 0 Coupler 2
INTIP:tr
Trace:f H323ipleg
(0) Clear flag
(1) Discard reception : Not implemented
(2) Discard transmission: Not implemented
(3) Loopback (up) : Not implemented
(4) Trace : 0
(5) Extended trace : 0
(6) Debug mode : 0
Your choice ? :4 6
000066F5-13966A83: End of command execution
TG0027 38 Ed. 01 / 12 July 2005

OmniPCX Enterprise
Trace:f h323scnleg
(0) Clear flag
(4) Trace : 0
(6) Debug mode : 0
Your choice ? :4 6
000066F6-139671B7: End of command execution
Trace:f h245cc
(0) Clear flag
(4) Trace : 0
(6) Debug mode : 0
Your choice ? :4 6
000066F7-13967A55: End of command execution
3) Make one call and capture into a file generated traces.
After the capture: Do not Forget to unset traces. To unset traces: select again traces H323ipleg,
H323scnleg, h245cc and on each trace, select (0) to Clear flags.
4) To quit the cpl_online command:
Trace:q
INTIP:
Press « Control D » to quit the cpl_online command.
Ed. 01 / 12 July 2005 39 TG0027

OmniPCX Enterprise
7.2.2. H323 traces on GD/GA coupler

As on GD/GA, H323 traces are not managed in the same way, the H323 traces captures are different.
1) Log on the GD with telnet. When you are logged on the GD, type the following commands: to capture H323 traces::
a)log on H323 traces port:
[admin@eMGD admin]$ telnet 192.168.65.93 4560
Trying 192.168.65.93...
Connected to 192.168.65.93.
Escape character is '^]'.
TRACE redirected to TELNET
00000006-008B12D8: Telnet_user ev EST_IND from ip
b) Set H323 Traces:
Note : Do not Forget to unset traces after the capture. To unset traces: select (0) to Clear flags.
MG:tr
Trace:f h323scnleg
(0) Clear flag
(4) Trace : 0
(6) Debug mode : 0
Your choice ? :4 6
End of command execution
Trace:f h323ipleg
(0) Clear flag
(4) Trace : 0
(6) Debug mode : 0
TG0027 40 Ed. 01 / 12 July 2005

OmniPCX Enterprise
Your choice ? :4 6
Trace:f h245cc
(0) Clear flag
(4) Trace : 0
(6) Debug mode : 0
Your choice ? :4 6
2) Make one call and capture into a file generated traces.
After the capture: Do not Forget to unset traces. To unset traces: select again traces H323ipleg,
H323scnleg, h245cc and on each trace, select (0) to Clear flags.
3) To quit the session:
Trace:q
MG:
Press « Control D » to quit the session.
7.2.3. T3 traces on Call Server
//to kill old traces and initialise the traces:
> tuner km
> trc i
//to configure traces:
> tuner all=off cpu cpl at
Ed. 01 / 12 July 2005 41 TG0027

OmniPCX Enterprise
// If there is not a lot of traffic on site when you make the test, set the cnx=on
> actdbg all=off rtp=on cnx=on
// If there is a lot of traffic on site when you make the test, don't set cnx=on
> actdbg all=off rtp=on
//to start traces
> mtracer -a&
//to stop traces
> tuner km
8. Before Calling Alcatel’s Support Center

Before calling Alcatel’s Business Partner Support Center (ABPSC), make sure that you have read
through :
− the Release Notes which lists features available, restrictions etc …
− the Problem Report data base available on the BPWS under the eSupport section
− this chapter and completed the actions suggested for your system’s problem
Additionally, do the following and document the results so that the Alcatel Technical Support can
better assist you:
− Fill-in the form in “Annex A:H323 Issue Description”in order to collect the primary
information.
− Have any information that you gathered while troubleshooting the issue to this point available to
provide to the TAC engineer (such as requested traces, etc…)
− Have a data network diagram ready. Make sure that relevant information is listed such as
bandwidth of the links, equipments like firewalls, PSTN connections, etc…
Note: modem or Telnet access is also desirable to help with effective problem resolution
TG0027 42 Ed. 01 / 12 July 2005

OmniPCX Enterprise
Annex A. H323 Issue Description
In case of H323 Issues, please fill-in this template with a maximum of accuracy.
Date:………. Site:……………………….
Description of the configuration:

Software release: R5.0Ux R5.0Lx R5.1.2 R6.0 Others: …….
Software version CPU: ……………….
IP Interface board LIOE binlioe: ……. bincomplioeker: ….. bincomplioeapp: …..

And binary version: INT-IP bintip: ……... binintip-appli: …….. bindspintip: …………
GD/GA binmg: ……….. binmcv: …………….
External H323 gateway Type of H323 Gateway: ………….

And binaries versions: Binaries Version: ………….
H323 calling: Type of Gateway: …………. IP Address: ………….

Calling Set Number: ………….
H323 Called: Type of Gateway: …………. IP Address: ………….
Called Set Number: ………….
LAN: 10 Mbits/s 100 Mbits/s Others: ………..

WAN: Type of link: …………. Bandwidth of link: ………..
Type of codec used: G711 G723 G729
Remote Access: Modem Number: ………….

Login: …………. Password: ………….
Please, provide us:

Topology of the site (including PSTN accesses with their location)
Ed. 01 / 12 July 2005 43 TG0027

OmniPCX Enterprise
If no remote access available, please provide us the result of following commands on the concerned node(s):
compvisu sys
compvisu ip
config all
incvisu
If possible, please provide us::

configuration of the H323 gateway.
Description of the Issue :

In which direction ? (Examples: Receiving a fax on a remote ACT from an external site;
Transmitting a fax from remote ACT to an external site; in both cases, when receiving or transmitting a fax)
…………………………………………………………………………………………………………………………….
Describe the complete path followed by the call. (Examples:

FaxA/Z/Node1/INTIP-->--IP-->--INTIP/RACT/Z/FaxB
FaxA --->--PSTN-->--T2/Node1/GD-----IP----GD/Node2/SLI/FaxB )
………………………………………………………………………………………………………………………………
………………………………………………………………………………………………………………………………
When did the issue appeared ? (if the issue appeared after a software update, indicate the previous version)
…………………………………………………………………………………………………………………………….
What did changed in the context ? (Example: new binaries, new network environment)
…………………………………………………………………………………………………………………………….
How often does the Issue arrived ?
Systematically Occasionally
% of case error per day : ....
Other Precisions:..........
Other comments on the Issue:

………………………………………………………………………………………………………………………………
………………………………………………………………………………………………………………………………
………………………………………………………………………………………………………………………………
TG0027 44 Ed. 01 / 12 July 2005

OmniPCX Enterprise
Annex B. H.323 Configuration Example
The following mgr screens show an example of the configuration of OmniPCX Enterprise to allow
H323 communications.
Sections “1:Configuration part to inter-work without gatekeeper” and “1.3:Configuration part not
related to gatekeeper use” show a configuration for H323 without gatekeeper use.
Sections “1.2:Configuration part to inter-work with gatekeeper” and “1.3:Configuration part not
related to gatekeeper use” show a configuration for H323 with gatekeeper use.
1. Configuration part to inter-work without gatekeeper

The “Interworking with Gatekeeper” parameter of the coupler which will be used for H.323
transmissions has to be configured.
1.1.1. GD or INTIP configuration
Access path: mgr/Shelf/Go down hierarchy/Go down hierarchy/Ethernet Parameters

Consult/Modify: Ethernet Parameters
Node Number (reserved) : 1
Shelf Address : 1
Board Address : 0
Shelf - Board Address : 1-0
Interface Type + GD
Board IP Address : 192.168.65.93
NetMask IP : 255.255.255.0
Default Gateway IP Address : 192.168.65.87
IP Quality of service : 0
Board Ethernet Address : 00:80:9f:2E:25:FB
Interworking with Gatekeeper + NO
Gatekeeper Id : -1
Numb. of sig. channels IP Phones : 0
Numb. of sig. channels inter ACT : 1
IP Domain Number : 0
E164 Number List Index : -1
Ed. 01 / 12 July 2005 45 TG0027

OmniPCX Enterprise
1.2. Configuration part to inter-work with gatekeeper
1.2.1. Configuration for external gatekeeper

Access path: mgr/IP/Go down hierarchy/Gatekeeper Parameters
Consult/Modify: Gatekeeper Parameters

Instance (reserved) : 1
Gatekeeper Id : 1
Used + YES
Gatekeeper Name : Cisco_2600
Gatekeeper IP Address : 192.168.65.84
Gatekeeper Is WECC + NO
Alternative GK IP address : ------------------------------------
1.2.2. Configuration for internal gatekeeper
Note: Internal gatekeeper is available from R5.0.Lx

Access path: mgr/IP/Go down hierarchy/Gatekeeper Parameters
Consult/Modify: Gatekeeper Parameters

Gatekeeper Id : 1
Used + YES
Gatekeeper Name : OXE_GK
Gatekeeper IP Address : 192.168.65.87
Gatekeeper Is WECC + NO
Alternative GK IP address : ------------------------------------
To define an internal Gatekeeper, you must assign to it the Gatekeeper Id included between 0 and 7
(in our example : number 1).
The internal Gatekeeper will be active if the software lock "Integrated gatekeeper" is on Yes.
Access path: mgr/IP/Go down hierarchy/IP Parameters/Internal Gatekeeper Number
Consult/Modify: IP Parameters

System_Option + Internal Gatekeeper number
Internal Gatekeeper number : 1
TG0027 46 Ed. 01 / 12 July 2005

OmniPCX Enterprise
1.2.3. E164 number list configuration

This list contains E164 numbers of the OmniPCX Enterprise.
Access path: mgr/IP/Go down hierarchy/Gatekeeper E164 Number List/Create
Create: Gatekeeper E164 Number List

E164 Number List Index : 1
1.2.4. Gatekeeper E164 Number configuration

Access path: mgr/IP/Go down hierarchy/Gatekeeper E164 Number List/Go down hierarchy/
Create
Create: Gatekeeper E164 Number

E164 Number : 34500
1.2.5. GD or INTIP configuration

Access path: mgr/Shelf/Go down hierarchy/Go down hierarchy/Ethernet Parameters
Consult/Modify: Ethernet Parameters

Shelf Address : 1
Board Address : 0
Shelf - Board Address : 1-0
Interface Type + GD
Board IP Address : 192.168.65.93
NetMask IP : 255.255.255.0
Default Gateway IP Address : 192.168.65.87
IP Quality of service : 0
Board Ethernet Address : 00:80:9f:2E:25:FB
Interworking with Gatekeeper + YES
Gatekeeper Id : 1
Numb. of sig. channels IP Phones : 0
Numb. of sig. channels inter ACT : 1
IP Domain Number : 0
Note
− To allow the GD or INTIP board to register itself to the gatekeeper:
a reset of the GD or INTIP board must be done.
Ed. 01 / 12 July 2005 47 TG0027

OmniPCX Enterprise
1.2.6. Check configurations related to gatekeeper

− To verify endpoints that are registered to the internal gatekeeper, type the following command:
(1)maskali> more /usr2/com/Trace_Database.txt
Endpoint: 1 @IP = 192.168.65.86

alias: e164 : 10100
e164 : 10101
h323-ID : 10100
h323-ID : 10101
Endpoint: 2 @IP = 192.168.65.93

alias: e164 : 208
e164 : 305
h323-ID : GW_2_0_192.168.65.93
(1)maskali>
− To verify that the GD is registered to the gatekeeper, type the following command:
(1)maskali> 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 | 1 | 1 |
+==============================================================================+
+==============================================================================+
| GATEKEEPERS PARAMETERS |
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+
|no GK| GK IP address | Gatekeeper name |GK WECC|Alternative GK|
+------------------------------------------------------------------------------+
| 1 | 192.168.65.84 | Cisco_2600 |No | Unused |
+==============================================================================+
+==============================================================================+
| E164 NUMBERS |
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+
| list number : 1 |
+------------------------------------------------------------------------------+
| 208 || 305 |
+==============================================================================+
TG0027 48 Ed. 01 / 12 July 2005

OmniPCX Enterprise
− To verify that the INTIP is registered to the gatekeeper:

Under “mtch” login before R.5.1or under “mtcl” login after R.5.1:
Type the following commands:
mtch> cpl_online 0 2 (in our example 0 is the shelf address and 2 is the board address)
Connected to Crystal 0 Coupler 2

INTIP:ras
GK parameters:
State: GK is chosen and GW is registered
RasAddress :192.168.65.84: port 1719
Identifier: Cisco2621
GK is not a WECC
ongoing calls: 0
Time To Live (in seconds): 180
GW seen by GK
H323 Id: GW_0_2_192.168.65.92
Identifier: 814A07F800000002
INTIP:h323
+-------------------------------------------------------+
+-------------------------------------------------------+
| Inter-Node Protocol H323 Boolean :0 |
| Fast_Start Boolean :1 |
| Fax T38 Boolean :1 |
| Ras Address :192.168.65.84: port 1719 |
| H323 Identifier : Cisco_2600 |
| 34500 |
| 34520 |
+-------------------------------------------------------+
INTIP:^D
Ed. 01 / 12 July 2005 49 TG0027

OmniPCX Enterprise
1.3. Configuration part not related to gatekeeper use

The following MGR screens are common to the configuration without gatekeeper and to the
configuration with gatekeeper.
1.3.1. Configuration of the IP trunk group and of the trunk group prefix
Access path: mgr/Trunk Group
Consult/Modify: Trunk Groups

Trunk Group Id : 500
Trunk Group Type + T2

Trunk Group Name : VOIP_N2
Number Compatible With : -1
Remote Network : 15
Shared Trunk Group + False
Special Services + Nothing
Node number : 2
Transcom Trunk Group + False
Auto.reserv.by Attendant + False
Overflow trunk group No. : -1
Tone on seizure + False
Private Trunk Group + False
Q931 signal variant + ISDN all countries
SS7 signal variant + No variant
Number Of Digits To Send : 5
Channel selection type + Quantum
auto.DTMF dialing on outgoing call + NO
T2 Specificity + IP
Public Network Category : 0
DDI transcoding + False
Can support UUS in SETUP + True
Implicit Priority
Activation mode : 0
Priority Level : 0
Preempter + NO
Incoming calls Restriction categ. : 10
Outgoing calls Restriction categ. : 10
mpt1343 callee number + NO
Note: “Number Of Digits To Send” must be compatible with the OmniPCX 4400 / Enterprise numbering plan.
Warning: When IP trunk is created, the involved INTIP or GD reset.
TG0027 50 Ed. 01 / 12 July 2005

OmniPCX Enterprise
Access path: mgr/Trunk Groups/Go down hierarchy/Trunk Group

Consult/Modify: Trunk Group

Trunk Group Type + T2

Public Network Ref. : ------
VG for non-existent No. + YES
Entity Number : 0
Supervised by Routing + No
VPN Cost Limit for Incom.Calls : 0
Immediat Trk Listening For VPNCall + YES
VPN TS % : 50
Csta Monitored + NO
Max.% of trunks out CCD : 0
Ratio analog.to ISDN tax : ------
TS Distribution on Accesses + YES
Quality profile for voice on IP + Always VoIP
IP compression type + Default
Use of volume in system + YES
Announcement for Dialtone + NO
Note : « Supervised by Routing + Yes » If we use same IP trunk for T38 and VPN
overflow.
Access path: mgr/Trunk Groups/Go down hierarchy/Trunk Group/Go down hierarchy/

T2/T1/T0 Access
Consult/Modify: T2/T1/T0 Access

Physical Address : 0-2-0
Access Type + T2
Access Cluster Id : 4
Time Slots T2 : 01111111111111110111111111111111
Access path: mgr/Translator/Prefix Plan

Consult/Modify: Prefix Plan

Number : 777
Prefix Meaning + Professional trunk seize

Prefix Information : 500
Private Route type + False
Ed. 01 / 12 July 2005 51 TG0027

OmniPCX Enterprise
1.3.2. Declaration of abreviated numbers (H323 device number)
Access path: mgr/Abbreviated Numbering/Direct Abbrev.Numbers/Go down hierarchy

Consult/Modify: Direct Abbrev.No Pref.

Direct Abbr.No Prefix : 10100
Call Number : 77710100#

Directory name : H323
Directory First Name : Device
Barring + False
Overfl.Dir.Abbrev.No Pref. : --------
Auto.Attendant Calling Right : 0
Call Type + IP
Timed Forward.Dir.Abbrev.No. : --------
Range Number : 255
Can Be Called By Name + NO
Displayed Name : H323 Device
External DISA Dir.No. : --------
IP Address : 192.168.65.86
Note
“IP Address” is the IP address of the remote H323 gateway.
TG0027 52 Ed. 01 / 12 July 2005

TC0027

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

TC0027

Hochgeladen von

Copyright:

Verfügbare Formate

TROUBLESHOOTING GUIDE No. TG0027 Ed.

OmniPCX Enterprise Nb of pages : 54 Date : 12 July 2005

SUBJECT : H323 ISSUES

This troubleshooting guide deals specifically with H323 issues.

4. THE BASICS OF H.323 .................................................................6

5. AVAILABLE H323 CONFIGURATION PARAMETERS IN OMNIPCX

Ed. 01 / 12 July 2005 1 TG0027

5.1.1. Object name: IP>IP Parameters>Fast Start.....................................................15

6. TROUBLESHOOTING H323 ISSUES: FIRST LEVEL ANALYSIS .......26

7. TROUBLESHOOTING: MORE IN DEPTH ANALYSIS......................29

TG0027 2 Ed. 01 / 12 July 2005

7.2. Procedures to capture Traces .................................................................. 38

8. BEFORE CALLING ALCATEL’S SUPPORT CENTER ........................42

ANNEX A. H323 ISSUE DESCRIPTION.............................................43

ANNEX B. H.323 CONFIGURATION EXAMPLE ................................45

1. CONFIGURATION PART TO INTER-WORK WITHOUT GATEKEEPER45

Ed. 01 / 12 July 2005 3 TG0027

TG0027 4 Ed. 01 / 12 July 2005

Ed. 01 / 12 July 2005 5 TG0027

4. THE BASICS OF H.323

4.1. H323 Protocol Stack

4.2. H.323 Short Description

• Elements of an H.323 System

TG0027 6 Ed. 01 / 12 July 2005

− Voice Mail Systems

4.3. RAS protocol Description

• Registration, Admission, and Status

• Used between the endpoint and its Gatekeeper in order to

4.3.1. General Format of RAS

• RAS messages generally have three types

Ed. 01 / 12 July 2005 7 TG0027

4.3.2. RAS Port

• Only UDP is defined for RAS Communications

4.3.3. RAS Messages Description

4.3.3.1. Gatekeeper Discovery Messages

• Gatekeeper Request (GRQ), Gatekeeper Reject (GRJ) and Gatekeeper Confirm

4.3.3.2. Gatekeeper Registration Messages

• Registration Request (RRQ), Registration Reject (RRJ) and Registration Confirm

TG0027 8 Ed. 01 / 12 July 2005

4.3.3.3. Gatekeeper Admission Messages

4.3.3.4. Other RAS Messages

• Location Request (LRQ)

• Bandwidth Request (BRQ)

• Disengage Request (DRQ)

• Information Request (IRQ)

4.3.3.5. RAS Timers and Retries

RAS message Time-out value Retry count

Ed. 01 / 12 July 2005 9 TG0027

4.4. H.225.0 Call Signaling

4.4.1. H.225.0 Call Signaling Message Body

TPKT Header Q.931 Header IE IE ................................. IE UUIE

The UUIE refer to the “User-User Information Element”.

Various Information Elements (IEs) that are appropriate for the

TG0027 10 Ed. 01 / 12 July 2005

4.4.2. Basic Call Setup Signaling

− Terminal capability exchange

Ed. 01 / 12 July 2005 11 TG0027

4.5.1. H.245 Message Body

TPKT Header H.245 PDU H.245 PDU ................................. H.245 PDU

Additional H.245 PDUs may be encoded following the first one.

4.5.2. H.245 Tunneling Mode

H.245 is generally transmitted on a separate TCP connections by most older endpoints

When tunneling, TPKT is not used

Multiple H.245 PDUs may be tunneled in a single H.225.0 message