TC0027
TC0027
TC0027
01
1
OmniPCX Enterprise
TROUBLESHOOTING GUIDE No. 27 H323 ISSUES
CONTENTS
1. INTRODUCTION ..........................................................................5
2. REFERENCES................................................................................5
3. HISTORY......................................................................................5
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.
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.
• What is H.323?
H.323 is a multimedia conferencing protocol, which includes voice, video, and
data conferencing, for use over packet-switched networks
• 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.
• RAS signaling is required when a Gatekeeper is present in the network (i.e., the use
of a Gatekeeper is conditionally mandatory)
− Reject (xRJ)
− Confirm (xCF)
• Typically, RAS communications is carried out via UDP through port 1719 (unicast)
and 1718 (multicast)
• GRQ and LRQ may be send Multicast, but are generally sent unicast, all other RAS
messages are sent unicast.
• 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.
• 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.
GRQ 5 2
RRQ 3 2
ARQ 5 2
BRQ 3 2
LRQ 5 2
DRQ 3 2
IRQ 3 1
• 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
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.
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
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.
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
• 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
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)
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.
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)
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)
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
• 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.
− 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.
• 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.
• 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.
• 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.
• 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)
• Description
− 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.
• 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.
− FALSE
The round-trip delay mechanism is disabled.
• 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.
• 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.
• 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.
• 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.
EI_RTP_INFO Information
Element
T3 Trace Example: The same call with DIRECT RTP Parameter set to False
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
INTIP:
Log on the GD with telnet. When you are logged on the GD, type the following commands:
Trying 155.132.130.10...
Connected to 155.132.130.10.
MG:
+-----------------------------------------------------------------+
| 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 |
+----------------------------------------------------+
| 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 |
| Ras Address :172.25.33.46: port 1719 |
| 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 005 e164 number(s) |
| 208 |
| 305 |
| 100 |
| 700390677151 |
| 34500 |
+----------------------------------------------------+
00000003-00005C80: End of command execution
MG:RAS
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
MG:rasstat
RRQ Message(s): 1
lightweight RRQ Message(s): 1
RCF Message(s): 2
RRJ Message(s): 0
• 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>
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
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)
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.
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
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
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
• 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
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.
VoIP devices should use out of band DTMF signalling for greater reliability and lower computational
requirements.
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.
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 “).
REMARK: a “normal” call will always be initiated without H245 tunneling mode
Called set is ringing; off hook: Start of H245 negotiation through same TCP socket as H225
RTP Flow
7.1.2.2.Call with GK
In that frame we can see the H323 version, the binary version of the H323 gateway.
H323:Version 2
7.1.3.3.RAS: RegistrationConfirm
7.1.3.5.RAS: AdmissionConfirm
7.1.3.6.RAS: DisengageRequest
7.1.3.7.RAS: DisengageConfirm
(145)xa000045> su - mtch
Password:
(145)xa000045> cpl_online xx yy
INTIP:tr
Trace:f H323ipleg
(4) Trace : 0
Your choice ? :4 6
Trace:f h323scnleg
(4) Trace : 0
Your choice ? :4 6
Trace:f h245cc
(4) Trace : 0
Your choice ? :4 6
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.
Trace:q
INTIP:
1) Log on the GD with telnet. When you are logged on the GD, type the following commands: to capture H323 traces::
Trying 192.168.65.93...
Connected to 192.168.65.93.
Note : Do not Forget to unset traces after the capture. To unset traces: select (0) to Clear flags.
MG:tr
Trace:f h323scnleg
(4) Trace : 0
Your choice ? :4 6
Trace:f h323ipleg
(4) Trace : 0
Your choice ? :4 6
Trace:f h245cc
(4) Trace : 0
Your choice ? :4 6
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.
Trace:q
MG:
> tuner km
> trc i
// If there is not a lot of traffic on site when you make the test, set the cnx=on
// If there is a lot of traffic on site when you make the test, don't set cnx=on
> tuner km
Note: modem or Telnet access is also desirable to help with effective problem resolution
In case of H323 Issues, please fill-in this template with a maximum of accuracy.
Date:………. Site:……………………….
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
…………………………………………………………………………………………………………………………….
………………………………………………………………………………………………………………………………
………………………………………………………………………………………………………………………………
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)
…………………………………………………………………………………………………………………………….
Systematically Occasionally
% of case error per day : ....
Other Precisions:..........
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.
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
Used + YES
Gatekeeper Name : Cisco_2600
Gatekeeper IP Address : 192.168.65.84
Gatekeeper Is WECC + NO
Alternative GK IP address : ------------------------------------
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
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
E164 Number List Index : 1
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.
(1)maskali>
− To verify that the GD is registered to the gatekeeper, type the following command:
mtch> cpl_online 0 2 (in our example 0 is the shelf address and 2 is the board address)
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
End of command execution
INTIP:h323
+-------------------------------------------------------+
| H323 Informations sent by the CPU |
+-------------------------------------------------------+
| Inter-Node Protocol H323 Boolean :0 |
| Fast_Start Boolean :1 |
| Fax T38 Boolean :1 |
| Channel Number :16 |
| Ras Address :192.168.65.84: port 1719 |
| Alternate Ras Address :0.0.0.0: port 0 |
| H323 Identifier : Cisco_2600 |
| GK_is_WECC Boolean :0 |
| Internode_calls_when_GK_not_reachable Boolean :0 |
| GK must register 002 e164 number(s) |
| 34500 |
| 34520 |
+-------------------------------------------------------+
End of command execution
INTIP:^D
1.3.1. Configuration of the IP trunk group and of the trunk group prefix
Access path: mgr/Trunk Group
Consult/Modify: Trunk Groups
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.
Access Type + T2
Access Cluster Id : 4
Time Slots T2 : 01111111111111110111111111111111
Note
“IP Address” is the IP address of the remote H323 gateway.