Alcatel-Lucent OmniPCX Enterprise

Communication Server

ABC-IP Logical Link

Legal notice:

Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of

Alcatel-Lucent. All other trademarks are the property of their respective
owners.

The information presented is subject to change without notice.

Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.

Copyright © 2012 Alcatel-Lucent. All rights reserved.

The CE mark indicates that this product conforms to the following Council
Directives:
- 2004/108/EC (concerning electro-magnetic compatibility)
- 2006/95/EC (concerning electrical safety)
- 1999/5/EC (R&TTE)

  
 
 


Chapter 1
Overview

 Overview .................................................................................................... 1.1

Chapter 2
Detailed description

 Calls Supported by an ABC-F Logical Link on IP ....................... 2.1

 Setting Up an ABC-F Logical Link on IP ........................................ 2.1
 Operation of the VPN Overflow on IP .............................................. 2.1
 Calls to RSI: Private to Public Overflow Strategy in case of
Failure or Saturation of the ABC Link (via IP) .............................. 2.2
 ABC Link through IP between Nodes with Duplicated Com
Server ......................................................................................................... 2.4

Chapter 3
Configuration procedure

 Configuring an ABC Link through IP .............................................. 3.1

 Other Configuration Operations ....................................................... 3.1


 
 0-1

 


 Configuring IP Parameters ................................................................. 3.1

 Configuring the Type of IP Address Used ..................................................... 3.1
 Transit on IP Boards ...................................................................................... 3.2
 H.323 Inter-node Protocol ............................................................................. 3.2
 Inter-node Call if GK not Reachable .............................................................. 3.2

Chapter 4
Configuration procedure - GA, GD, INT-IP boards

 Overview .................................................................................................... 4.1

 Creating a GA or INT-IP A Board ...................................................... 4.1
 Modifying Board Parameters ............................................................. 4.2
 Configuring the Ethernet Parameters ............................................. 4.2

Chapter 5
Configuration procedure - IP Trunk Group

 Overview .................................................................................................... 5.1

 Configuring the IP Trunk Group for an ABC-F Logical Link on
IP .................................................................................................................. 5.1
 Configuring the Global Parameters of the Trunk Group ................................ 5.1
 Configuring the Local Parameters of the Trunk Group .................................. 5.1
 Declaring Trunk Group Access/Accesses ..................................................... 5.2

Chapter 6
Configuration examples

 Example Overview ................................................................................. 6.1

0-2 
 

 
 


 Configuring the System Parameters ............................................... 6.2

 Configuring the IP Boards .................................................................. 6.2

 Declaring the Boards ..................................................................................... 6.2

 Configuring the Ethernet Parameters ............................................................ 6.3

 Configuring the Hybrid Link ............................................................... 6.3

 Declaring the Hybrid Link .............................................................................. 6.3

 Declaring the Hybrid Link Access .................................................................. 6.4

 Configuring Broadcast ................................................................................... 6.5

 Creating the IP Trunk Group .............................................................. 6.6

  Declaring the Global Data ............................................................................. 6.6

  Declaring the Local Data ............................................................................... 6.7

  Declaring Trunk Group Access/Accesses ..................................................... 6.7

 Configuring the VPN Hop .................................................................... 6.8


 Declaring the VPN Hop ................................................................................. 6.8


 Enabling the VPN Service ............................................................................. 6.9
 Configuring ARS ..................................................................................... 6.9

 Declaring the ARS Route List ........................................................................ 6.9

 Declaring the two ARS Routes ...................................................................... 6.9

 Declaring the Time-based Routes ................................................................6.11

 Configuring User COS ......................................................................... 6.11
 Configuring the Dialing Plan Description ..................................... 6.12
 Creating the Prefixes ........................................................................... 6.12

 Declaring the Local VPN Prefix ....................................................................6.12

 Declaring the Remote VPN Prefix ................................................................6.13

Chapter 7
Maintenance

 compvisu Command ............................................................................. 7.1

 compvisu lio Command ................................................................................. 7.1
 compvisu ip add Command ........................................................................... 7.1
 compvisu IP Command ................................................................................. 7.1
 compvisu sys Command ............................................................................... 7.2


 
 0-3

 


 compvisu -r visu Command ........................................................................... 7.2


compvisu ras Command ................................................................................ 7.2
 cmdcpl Command .................................................................................. 7.3
 lookvpn Command ................................................................................. 7.4
 Trkstat Command ................................................................................... 7.4
 Trkvisu Command .................................................................................. 7.4
 Incidents .................................................................................................... 7.4

 Incident 4102 ................................................................................................. 7.4

 Incident 4103 ................................................................................................. 7.4

 Incident 4104 ................................................................................................. 7.5

 Incident 4108 ................................................................................................. 7.5

 Examples ....................................................................................................... 7.5

0-4 
 

 

 

1.1 Overview
An ABC link through IP is an ABC link where both the signaling and voice channels use the IP
network.
Hybrid logical links with VPN overflow on IP (i.e. ABC-F logical links on IP) are used to connect
two nodes located on the same ABC-F network or on the same ABC-F sub-network (in a
network configuration with several ABC-F sub-networks).

Figure 1.1: Representation of ABC-F Logical Links on IP within an ABC-F Network or

Sub-Network

    !!!"   #$!"$ !% 1-1

Chapter 1 #$!"$ !%

1-2     !!!"   #$!"$ !%

 


  

2.1 Calls Supported by an ABC-F Logical Link on IP

A hybrid logical link with VPN overflow on IP (i.e. ABC-F Logical Link on IP) supports the
following types of calls:
- Voice calls.
- Group 3 fax calls using Fax Relay over IP. Two protocols are used:
• Proprietary T.38 protocol for calls between OmniPCX 4400 or Alcatel-Lucent OmniPCX
Enterprise Communication Server nodes.
• Standard T.38 protocol for fax over IP calls with non-Alcatel-Lucent OmniPCX
Enterprise CS H.323 gateways, such as the OmniPCX Office, and H.323 and SIP
terminals from other manufacturers.
Maximum speed for fax relay over IP calls is 9600 bits/s. For more information, see module
Fax over IP - Overview.
- Data calls (from R5.1.2): see the module Modem, fax and data transparency over IP -
Detailed description - Conditions for Setting up a Data Call.
Caution:
Modem calls are not supported on ABC-F Logical Link on IP.

2.2 Setting Up an ABC-F Logical Link on IP

The ABC-F Logical Link on IP is based on a hybrid logical link with VPN overflow on IP.
Signaling is exchanged between the Ethernet interfaces of the Com Servers. Voice flows are
exchanged between IP boards (GD, GA or INT-IP A) using the H.323 gateway feature of these
boards.
The principle is as follows:
- The two nodes are connected by a hybrid logical link:
• With an IP signaling channel between the Ethernet interfaces of the Com Servers,
From the local node, the IP signaling channel activation requires configuration of the
hybrid logical link access with the remote node IP address. In case of a remote node
with one single Com Server, the IP address to declare is the physical IP address of the
Com Server or its main IP address. In case of a remote node with Com Server
duplicated, see ABC Link through IP between Nodes with Duplicated Com Server .
• With no B channels.
- On each node, an IP trunk group is declared on the H.323 gateway of a GD, GA or
INT-IP A board.
- Using VPN overflow and ARS, voice flows are directed to the IP trunk group.
The IP support is used in the same way as any other voice resource. Supports other than IP
can therefore be selected for ARS.

2.3 Operation of the VPN Overflow on IP

The operation of the VPN overflow on IP differs slightly to an overflow on another type of
support.

&    '"(   !) ! !*" +)  2-1

Chapter 2 !) ! !*" +) 

Figure 2.1: Inter-node Link

1. Set 3100 calls set 3200 on node 2. As the hybrid link has no voice resources, it is
considered to be saturated. The VPN overflow is therefore requested.
2. Node 1 sends a request to node 2 to obtain the VPN overflow number.
3. Node 2 responds by sending a free VPN overflow number and the IP address of the IP
board.
4. Node 1 then checks its prefix table to see if the VPN overflow number sent by node 2
exists. This number, which is present in node 1, must correspond to a remote VPN
overflow type.
5. When this number is read, node 1 obtains the ARS route number to be used. In the route,
node 1 obtains the number of the trunk group to be used. In the present case, this is an IP
trunk group (trunk group 4).
6. The VPN call leaves for the IP trunk group with the IP address received in step 3. The call
is then set up between trunk group 4 of node 1 and trunk group 5 of node 2.

2.4 Calls to RSI: Private to Public Overflow Strategy in case of

Failure or Saturation of the ABC Link (via IP)
As of R8.0.1, the private to public overflow feature can be used by the Routing Service
Intelligence (RSI) interface for call processing in the event of IP link congestion or failure.
The right to private to public overflow is defined in the RSI feature class of service and not in
the set's phone feature class of service of the calling party.
Incoming Call routing in the RSI can be interrupted, when the ABC link through IP with the
called party fails or is satured. When this situation occurs and the RSI enables private to public
overflow, call can be redirected to the called party using the public network. The called party
can be a business set, a hunting group, an attendant, or an attendant group.

2-2 &    '"(   !) ! !*" +) 

 !) ! !*" +) 

Figure 2.2: Example of Call Overflow to the Public Network

In this example, a user A from IP domain 1 calls a local RSI. A route request is sent to the
CTI application, which returns a route select message to RSI. RSI, in turn, routes the call to a
user B belonging to IP domain 2. In the mean time, a failure or saturation is detected between
IP domains 1 and 2.
Two scenarios can occur:
- The RSI does not authorize private to public overflow. In this case, the call is not
distributed to user B.
According to the call routing strategy applied within the RSI, a reroute request or an end
of service notification is sent to the CTI application. This message includes the reason
for network call failure
- The RSI authorizes private to public overflow. In this case, the call is routed from the RSI
to user B through the public network, using the same mechanisms as described in: module
ABC-F homogeneous private network - Available features - Overflow on Public Network
If the local private to public overflow succeeds, an end of service notification is sent to
the CTI application. If this is not the case, according to the call routing strategy applied
within the RSI, a reroute request or an end of service notification is sent to the CTI
application with the reason for call failure
In a network configuration, when a call routed by the RSI requires routing on the public
network, private to public overflow is processed only from the RSI node to the destination
node, and not from the calling party node to the destination node.
Note:
For more information on the RSI routing mechanisms and messages exchanged, see the Routing

&    '"(   !) ! !*" +)  2-3

Chapter 2 !) ! !*" +) 

Service Intelligence - Standard Edition documentation.

2.5 ABC Link through IP between Nodes with Duplicated Com

Server
From the local node, the IP signaling channel activation requires configuration of the ABC link
through IP access with the remote node IP address. In case of a remote node with Com
Server duplicated, the IP address to declare depends on Com Servers position:
- The two Com Servers are on the same IP subnetwork. The IP address to declare is the
main IP address used for both Com Servers
- The two Com Servers are on different IP subnetworks (available from R6.1). Each Com
Server is identified by its own main IP address. Each main IP address of Com Server must
be declared in the hybrid logical link access
In this configuration, the IP signaling set up is as follows:

Figure 2.3: IP Signaling Channel Set up to a Remote Node with both Com Servers on Different IP
Subnetworks
Principle:
a. A connection request is sent towards the main IP addresses of Com Servers on the
remote node
b. Only the main Com Server answers. The IP signaling channel is set up between the
two nodes
In case of Com Server switchover on one of the nodes linked by an ABC-F logical link on IP:
- Up to R10.0, communications established via the ABC-F logical link on IP are released
- As of R10.1, communications established via the ABC-F logical link on IP can be
maintained: for more information, see module Call Server duplication - Switchover
Caution:

2-4 &    '"(   !) ! !*" +) 

 !) ! !*" +) 

A node with a duplicated Com Server and both Com Servers on different IP subnetworks cannot
be connected to R6.0 nodes (or lower) via an ABC link through IP.

&    '"(   !) ! !*" +)  2-5

Chapter 2 !) ! !*" +) 

2-6 &    '"(   !) ! !*" +) 

 

  

3.1 Configuring an ABC Link through IP

To set up an ABC-F logical link on IP:
1. Declare and configure an IP board (GA, GD or INT-IP A).
For more information, see the module ABC-IP Logical Link - Configuration procedure - GA,
GD, INT-IP boards .
2. Create an IP trunk group on this board.
For more information, see the module ABC-IP Logical Link - Configuration procedure - IP
Trunk Group .
3. Configure the hybrid link with overflow on IP.
For an example, see the module ABC-IP Logical Link - Configuration examples .
IP boards (GA, GD or INT-IP A) are used to provide compression resources for call
establishment, even if direct RTP is used after call establishment.
Caution:
Signalization packets of an ABC link through IP are not fragmentable and their size cannot be
configured. This means that the maximum size of IP packets accepted by IP devices of the client
network must be superior or equal to the size of signalization packets.

3.2 Other Configuration Operations

Other configuration operations concern aspects that are not required to set up an ABC link
through IP, but that affect calls using the link.
- System parameters.
For more information, see Configuring IP Parameters .
- Coding (compression, silence suppression (VAD), etc.).
For more information, see the module Direct RTP in network - Coding configuration.
- IP Quality of Service (QoS).
For more information, see the module 802.1p/Q and VLAN - Configuration procedure.
- Call Admission Control (CAC) restrictions.
For more information, see the module Voice over IP - Call restriction configuration and
module VPN overflow - Detailed description - Limiting VPN calls.
- Use of a gatekeeper.
For more information, see the module H323 : terminals, gateway, gatekeeper -
Configuration procedure.

3.3 Configuring IP Parameters

The parameters described in this section can be used for all IP links on the node.

3.3.1 Configuring the Type of IP Address Used

    !!!"   , -")  +"!-"! 3-1

Chapter 3 , -")  +"!-"!

Here, the manager specifies the IP address format that the boards use by default.
1. Select IP > IP Parameters
2. Review/modify the following attributes:
System Option Select Type IP Address.
Type IP Address Select the IP address format to be used:
• IPv4: addresses on 4 bytes, for example:
168.158.2.322.
• IPv6: addresses on 16 bytes.

3. Confirm your entries

3.3.2 Transit on IP Boards

1. Select IP > IP Parameters
2. Review/modify the following attributes:
System Option
Transit on IP Boards
Select Transit on IP Boards.
• True: voice flow on an IP board does not require
a decompression/compression step to be
performed.
• False: voice flow transit on an IP board requires
a decompression/compression step to be
performed.

3. Confirm your entries

Note:
The transit function depends on the board type:
- INT-IP: transit available
- GA/GD: transit not available
- INT-IP2: transit available
- GA2/GD2: transit not available
- INT-IP3: transit not available
- GA-3/GD-3: transit not available

3.3.3 H.323 Inter-node Protocol

See the module Direct RTP in network - Coding configuration - VPN Overflow on IP.

3.3.4 Inter-node Call if GK not Reachable

This parameter is used if a gatekeeper is used for inter-node links (IP board Interworking
with Gatekeeper parameter set to True).
1. Select IP > IP Parameters
2. Review/modify the following attributes:

3-2     !!!"   , -")  +"!-"!

 , -")  +"!-"!

System Option Select Internode call if GK not reachable.

Internode call if GK not reachable
True: inter-node calls are allowed, even if the
gatekeeper cannot be accessed.
Note:
The first call made before the gatekeeper is detected as
unreachable fails (linked with the Time to live Timer, 180s
by default)

3. Confirm your entries

    !!!"   , -")  +"!-"! 3-3

Chapter 3 , -")  +"!-"!

3-4     !!!"   , -")  +"!-"!

 

    


  
4.1 Overview
This document describes the IP board configuration procedure (GA, GD and INT-IP boards).
Note:
From R6.0, LIOE boards are no longer supported and must be replaced by INT-IP boards.
To configure a board:
1. Create the board (GA or INT-IP A only).
2. Modify board parameters.
3. Configure the Ethernet parameters.

4.2 Creating a GA or INT-IP A Board

This section describes how to create a GA or INT-IP A board.
This step is not required for a GD board. The GD (or GD3) board is automatically created
when the Media Gateway is initialized: see the module Common Hardware Media Gateway -
Commissioning.
1. Select: Shelf > Boards
2. Review/modify the following attributes:
Shelf Address Enter the shelf number.
Board Address Enter the board number.
Interface Type Select: GA, GA3, INTIPA or INTIP3A.
IP Compression Daughterboards on GA and GD:
Daughter board or • MCV24: 21 compressors maximum.
GD/GA Daughterboard • MCV8: 7 compressors maximum.
(according to the board From R6.0:
type) • MADA1: 8 compressors maximum.
• MADA3: 24 compressors maximum.
Daughterboards on INT-IP A:
• GIP6x1: one GIP6 daughterboard.
• GIP6x2: two GIP6 daughterboards.
• 1 GIP6A: one GIP6A daughterboard.
• 2 GIP6A: two GIP6A daughterboards.
From R6.0:
• 1 GIP4-4: 32 compressors.
• 2 GIP4-4: 60 compressors.
• 1 GIP4-1: 8 compressors.
• 2 GIP4-1: 16 compressors.
Daughterboards on INT-IP3, GD-3 or GA-3:
As of R9.1:
ARMADA: 30 compressors.

  .  !!!"   , -")  +"!-"!  /0 / 0 12 4-1
"*
Chapter 4 , -")  +"!-"!  /0 / 0 12 "*

Board IP Version Select the addressing type to be used:

• IP Default: addressing is the type indicated by the IP
Address Type IP parameter.
• IP version 4: addressing is IPv4 type.
• IP version 6: addressing is IPv6 type (for Alcatel-Lucent
support only).
Note:
This parameter can only be modified when creating the board. For
subsequent modification, the board has to be deleted then recreated.

3. Confirm your entries

4.3 Modifying Board Parameters

1. Select Shelf > Boards
2. Review/modify the following attributes:
Shelf Address Enter the shelf number.
Board Address Enter the board number.
Interface Type GA, GD, GA3, GD3, INTIP3A or INTIPA.
IP Compression See above.
Daughter board or
GD/GA Daughterboard
(according to the board
type)
No. of Compressors for Enter the number of compressors to be assigned to the gateway
Gateway function: link with H.323 terminals, H.323 gateways, and remote
nodes via IP.
No. of Compressors for Enter the number of compressors used for IP-Phones, PC-MM2s
IP Devices and inter-MG calls.

3. Confirm your entries

Note:
The two parameters No. of Compressors for Gateway and No. of Compressors for IP Devices are
not used if the direct RTP in network service is not enabled.
If the direct RTP in network service is enabled, the compressors are not dedicated to gateways or IP
devices, they are dynamically assigned. In this case, only the total of the two parameters is used. This
corresponds to the number of compressors that can be used (see the module Direct RTP in network -
Detailed description - Assigning Compressors and IP Trunks).
As of R9.1, direct RTP in network service must be enabled.

4.4 Configuring the Ethernet Parameters

Creating an IP board results in automatic creation of an Ethernet Parameters object.
1. Select Shelf > Boards > Ethernet Parameters
2. Review/modify the following attributes:

4-2   .  !!!"   ,
-")
 +"!-"!  /0 / 0 12
"*
 ,
-")
 +"!-"!  /0 / 0 12 "*
Shelf Address
Board Address
Interface Type
Board IP Address
IP NetMask
Default Gateway IP Address
IP Quality of Service
Cryptographic box address
Board Ethernet Address
Interworking with Gatekeeper
Gatekeeper ID
Numb. of sig. channels IP Phones
Numb. of sig. channels inter-ACT
IP Domain Number
E164 Number List Index
  .  !!!"   ,
Enter the shelf number.
Enter the board number.
GA, GD, GA3, GD3, INTIPA, or INTIP3A.
• GA and INT-IP A boards: these boards start in
static mode. Their IP parameters must be entered
here.
• GD board: these three parameters are
automatically completed when the Media Gateway
is initialized (see the module Common Hardware
Media Gateway - Commissioning).
Enter the number of the IP Quality of Service COS to
be used for calls transiting via this access (see the
module 802.1p/Q and VLAN - Configuration
procedure).
Displays the IP Touch Security Module IP address
which protects the board (only if the IP Touch Security
service is implemented on the node). For more
information, see: module IP Touch Security -
Configuration procedure.
• GA and INT-IP A boards: Ethernet address is
automatically entered during board initialization.
• GD board: Ethernet address must be entered
manually.
• Yes: a gatekeeper is used.
• No: no gatekeeper used, translation is performed
internally.
See the module H323 : terminals, gateway, gatekeeper
- Configuration procedure - Gatekeeper.
To be completed if the previous parameter is set to
Yes.
Enter gatekeeper number (between 0 and 7).
If this attribute is set to –1 or if the specified
gatekeeper's parameters are blank, the board emits a
multicast request to find a gatekeeper.
Note 1:
• If the gatekeeper is separated from the board by a
router, the router must allow multicast.
• If there are several gatekeepers, the board may be
linked to any gatekeeper.
Displays the number of IP-Phones connected with
signaling terminating at this board.
Displays the number of channels used for the GD
board link with the Com Server.
This parameter is always null for a GA or INT-IP A
board.
Displays board domain number.
Enter the number of the E164 number list.
-")
 +"!-"!  /0 / 0 12 4-3
"*
Chapter 4 ,
-")
 +"!-"!  /0 / 0 12 "*

Full duplex From R5.1, INT-IP A board only:

• Yes: transmission and reception are performed
simultaneously.
• No: operates in half duplex, transmission and
reception are not performed simultaneously.
Gateway H323 name Enter the name of the H.323 gateway (32 characters
maximum). This name is sent by the H.323 gateway to
the gatekeeper in a registration message.
If no entry, the H.323 gateway default name sent is as
follows: GW_<shelf address>_<board
address>_<board IP address>.
Example:
GW_3_0_192.40.50.23.

3. Confirm your entries

4. If the Gateway H323 name parameter is modified, reset the board (GD, GA or INT-IP)
Note 2:
If other parameters are modified, the board is automatically reset.

4-4   .  !!!"   , -")  +"!-"!  /0 / 0 12
"*
 

   

! 
5.1 Overview
This section describes the different configurations to put into service an IP trunk group used
both for an ABC-F logical link on IP and connection of H.323 terminals.
For ABC-F logical link on IP, the trunk group can be supported by a GD, GA or INT-IP A board.
Note:
A GD, GA or INT-IP A board can only support one trunk group.
To configure an IP trunk group:
1. Declare the trunk group.
2. Configure the local parameters of the trunk group
3. Declare trunk group access/accesses.

5.2 Configuring the IP Trunk Group for an ABC-F Logical Link on

IP

5.2.1 Configuring the Global Parameters of the Trunk Group

1. Select Trunk Groups
2. Review/modify the following attributes:
Trunk Group ID Enter trunk group number.
Trunk Group Type T2 (mandatory).
Number Compatible With -1
Remote Network Enter the remote network number. Remote network
number, used for VPN hops, must be identical to the
network number declared in VPN overflow.
Node number Enter the local network number.
Q931 Signal variant Select ISDN all countries (mandatory).
Channel selection type Select Quantified (mandatory).
auto.DTMF dialing on outgoing call No (mandatory).
T2 Specification Select IP (mandatory).

3. Confirm your entries

The other parameters are not specific to “Voice over IP”.

5.2.2 Configuring the Local Parameters of the Trunk Group

1. Select Trunk Groups > Trunk Group
2. Review/modify the following attributes:

  .  !!!"   , -")  +"!-"!   2"- /"-+ 5-1
Chapter 5 , -")  +"!-"!   2"- /"-+

Trunk Group ID Enter trunk group number.

Supervised by Routing Select Yes (mandatory) to enable VPN hops to be
used.
May be left at No, if the trunk group is used only for
H.323 terminals.
Immediate Trk Listening if VPNCall Yes for VPN hops.
VPN TS % Enter the maximum percentage of TSs that can be
assigned to the VPN hop (by default 50%, the rest
are available for calls to H.323 terminals). If all the
trunk group TSs are to be used for a VPN hop, enter
100%.
Quality profile for voice over IP Not used.
IP Compression Type This parameter specifies the compression type used
by H.323 terminals using this trunk group:
• Default: the system default algorithm is chosen in
priority.
• G711: the G711 coding algorithm is chosen in
priority.
Note:
For inter-node calls, compression type is specified in the
VPN Overflow object.
See the module Direct RTP in network - Coding
configuration.
B Channel Choice Yes, mandatory at both ends of the link.
Trunk COS Leave the default value at “19”. Trunk category (19)
parameters must not be modified.

3. Confirm your entries

The other parameters are not specific to “Voice over IP”.

5.2.3 Declaring Trunk Group Access/Accesses

Caution:
Do not configure the TSs of the T2 accesses of the IP trunk group. Leave the default values, that
is, with 30 trunks.
The number of compressors available on this trunk group is configured on the board: see the
module ABC-IP Logical Link - Configuration procedure - GA, GD, INT-IP boards .

5.2.3.1 T0/T1/T2 Access on a GA or GD Board

Declare the trunk group access on access 0 of the GA or GD board
- Select Trunk Groups > Trunk Group > T2/T1/T0 Access
- Review/modify the following attributes:

5-2   .  !!!"   , -")  +"!-"!   2"- /"-+
 , -")  +"!-"!   2"- /"-+

Trunk Group ID Enter trunk group number.

Physical Address Enter the address of the access on the board in the
format, Shelf No.-Board No.-Access No.
Access Type T2.
Access Cluster ID Displays this (system configured) parameter.
Time Slots T2 01111111111111110111111111111111
DO NOT MODIFY

- Confirm your entries

Caution:
Creating the T0/T1/T2 access resets the board that supports the trunk group. Exception: From
R6.0, if the board is a GD board, the access is put into service without resetting the board.

5.2.3.2 T0/T1/T2 Access on an INT-IP Board

An INT-IP board has two digital accesses. The GIP6 and GIP4-4 daughter boards uses TSs on
both accesses, as shown in table: Compressor Distribution on GIP Boards .
table 5.4: Compressor Distribution on GIP Boards
Access 0 Access 1
1 GIP6A or 1 GIP4-1 8 compressors 0
2 GIP6A or 2 GIP4-1 16 compressors 0
GIP6x1 or 1 GIP4-4 16 compressors 16 compressors
GIP6x2 or 2 GIP4-4 32 compressors 32 compressors

For all compressors on the GIP6 and GIP4-4 boards to be useable, two accesses must be
declared on the IP trunk group.
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.

Note:
Do not configure the TSs of the T2 accesses of the IP trunk group. Leave the default values, that is, with
30 trunks. If the number of compressors is lower, the system only sees TSs that are effectively assigned
as being in service. For example, if there is only one GIP6 board, the TRKSTAT or SUPROUTAGE
commands show 30 TSs declared per access, but only 16 and 14 TSs in service.
Declare the first trunk group access on access 0 of the board:
1. Select Trunk Groups > Trunk Group > T0/T1/T2 Access
2. Review/modify the following attributes:
Trunk Group ID Enter trunk group number.
Physical Address Enter the address of access 0 on the board in the
format, Shelf No.-Board No.-0.
Access Type T2.
Access Cluster ID Displays this (system configured) parameter.

  .  !!!"   , -")  +"!-"!   2"- /"-+ 5-3
Chapter 5 , -")  +"!-"!   2"- /"-+

Time Slots T2 01111111111111110111111111111111

DO NOT MODIFY

3. Confirm your entries

Declare the second trunk group access on access 1 of the board:
1. Select Trunk Groups > Trunk Group > T0/T1/T2 Access
2. Review/modify the following attributes:
Trunk Group ID Enter trunk group number.
Physical Address Enter the address of access 1 on the board in the
format, Shelf No.-Board No.-1.
Access Type T2.
Access Cluster ID Displays this (system configured) parameter.
Time Slots T2 01111111111111110111111111111111
DO NOT MODIFY

3. Confirm your entries

5-4   .  !!!"   , -")  +"!-"!   2"- /"-+
 

 "# 

6.1 Example Overview

In the following example we want to set up an inter-node link (i.e. ABC-F logical link on IP) via
the IP network. A backup link is provided on the public network.

Figure 6.1: Set up Diagram

To create an ABC-F logical link on IP:
1. Configure the system parameters.
2. Configure the IP boards.
3. Configure the hybrid link,
4. Create the IP trunk group.

  .  #)!"   , -")  !+!* 6-1

Chapter 6 , -")  !+!*

5. Configure the VPN hop.

6. Configure ARS.
7. Configure user COS.
8. Configure the dialing plan description.
9. Create the prefixes.

6.2 Configuring the System Parameters

Object name: IP > Parameters
Attribute N4 N5 Comments
IP addresses of type X.X.X.X
Type IP Address IPV4 IPV4
are used.
Must be set to "True" on all
H323 Internode Protocol True True
network nodes.
Must be homogeneous on the
entire network: see the module
Direct RTP True True
Direct RTP in network -
Configuration procedure.

Object name: System > Other System Param. > Compression Parameters
Attribute N4 N5 Comments
Voice Activity Detect Homogeneous on the ABC
True True
(Comp Bds) network.
Homogeneous on the ABC
Compression Type G723 G723
network.

6.3 Configuring the IP Boards

6.3.1 Declaring the Boards

Object name: Shelf > Board
Attribute N4 N5 Comments
Shelf Address 3 3
Board Address 0 0
Interface Type GD GD
GD/GA Daughterboard MCV24 MCV24 21 compressors available
IPv4 has been specified in the
Board IP Version IP Default IP Default
system parameters.
No. of Compressors for All compressors are used for
21 21
Gateway the gateway function

6-2   .  #)!"   , -")  !+!*

 , -")  !+!*

No IP-phones on these boards

No. of Compressors for
0 0 and no communication with the
IP Devices
other Media Gateways

6.3.2 Configuring the Ethernet Parameters

Object name: Shelf > Board > Ethernet Parameters
Attribute N4 N5 Comments
Shelf Address 3 3
Board Address 0 0
IPv4 type addressing has been
Board IP Address 10.253.4.20 10.253.5.20
selected.
Dependent on client network
IP NetMask 255.255.0.0 255.255.0.0
configuration.
In this case, both Media
Default Gateway IP Gateways are on the same IP
X.X.X.X X.X.X.X
Address subnet. A router is not
compulsory.
IP Quality of Service 0 0
Cryptographic box Only if the IP Touch Security
address X.X.X.X X.X.X.X service is implemented on the
node.
Interworking with No gatekeeper used in this
No No
Gatekeeper example.
Gatekeeper ID –1 –1
E164 Number List Index –1 –1

The IP configuration may be tested by the "ping" command, that is applied to the CS and
GA/GD boards.
Important:
The GD/GA board must be reset to apply any modifications made to it. Reset is not necessary
when a board is created.

6.4 Configuring the Hybrid Link

6.4.1 Declaring the Hybrid Link

Object name: Inter-Node Links > Logical Links (ABC-F)
Attribute N4 N5 Comments
Link Name N4N5 N5N4
Link Type Hybrid Hybrid
Adjacent Node 5 4

  .  #)!"   , -")  !+!* 6-3

Chapter 6 , -")  !+!*

Adjacent Network 0 0
Trunk COS 18 18
B Channel Choice Yes No Yes on one side.
TS Overflow Yes Yes
Monitored by CSTA False False
Incidents Teleservice Yes Yes
Permanent Permanent
Signal Establis.Mode
User User
Dynamic Dynamic
Routing Type
Routing Routing
TS Distribution on
Yes Yes
Accesses
Multi access hybrid link Yes Yes
MUX presence No No

6.4.2 Declaring the Hybrid Link Access

Declare the link signaling channel between the two Com Servers.
Object name: Inter Node Links > Logical Links (ABC-F) > Hybrid Link Access
Attribute N4 N5 Comments
Link Name N4N5 N5N4
Access number 1 1
Physical address main 19 is the number of the hybrid
19–0–0 19–0–0
access rack
Signaling Type IP IP
Main established tempo 30 30
Access Cluster ID 1. 1.
Has StandBy Signaling False False
StandBy Signaling Type Unused Unused
Network Date Time
No No
Update

6-4   .  #)!"   , -")  !+!*

 , -")  !+!*

Called Number or main 10.253.5.3 10.253.4.3 Enter the IP address of the

CPUa IP addr remote node. The IP address to
enter depends on the remote
node configuration:
- Remote node with one
single Com Server: enter
the physical IP address of
the Com Server or its main
IP address
- Remote node with
duplicated Com Server and
the two Com Servers on the
same IP subnetwork: enter
the main IP address used
for both Com Servers
- Remote node with
duplicated Com Server and
the two Com Servers on
different IP subnetworks:
enter the main IP address
of the Com Server declared
in 'a' position in the remote
node.
Note:
This action must be combined
with entry of the main IP
address for the second Com
Server (attribute Main CPUb IP
address below)
Caution:
In the last configuration, the
local node must be a R6.1
node or later.
Main CPUb IP address 10.253.5.4 Not used If the remote node is in a
duplicated Com Server
configuration with the two Com
Server on different IP
subnetworks, enter the main IP
address of the Com Server
declared in 'b' position in the
remote node.

Check that the signaling of the hybrid logical link is indeed operational with the suproutage
command.

6.4.3 Configuring Broadcast

This logical link has signaling over IP. This IP link should be requested for the "Broadcast"
process.
Caution 1:
From R6.1, the IP/X25 tunnel must be used as communication medium when one of the nodes,

  .  #)!"   , -")  !+!* 6-5

Chapter 6 , -")  !+!*

interconnected by the hybrid logical link, is a node with duplicated Com Server and both Com
Servers on different IP subnetworks.
Object name: X25 > Network nodes
Attribute N4 N5 Comments
Local node number–Remote
Node number 0–5 0–4
node number
IP/X25 Addressing mode Default Default
Yes as logical link signaling is
over IP
Not used when one of the
IP Addressing mode Not used Not used nodes, interconnected by the
hybrid logical link, is a node
with duplicated Com Server
and both Com Servers on
different IP subnetworks.
Yes for this link to be used for
Valid for broadcast Yes Yes
broadcast.
IP/X25 Address 172.30.253.5 172.30.253.4
IP/X25 Name X000002_tun x000001_tun

After broadcast configuration:

- Check that signaling on this logical link is operational by using the suproutage tool
- Check that audit and broadcast are operational on the logical link
Caution 2:
The "gated" process (IP routing protocol that can be run from the netadmin tool) must not be
launched on a node with a hybrid logical link on IP (in the case of inter-Media Gateway VoIP,
signaling is made through a hybrid logical link on IP).

6.5 Creating the IP Trunk Group

6.5.1 Declaring the Global Data

Object name: Trunk Groups
Attribute N4 N5 Comments
Trunk Group ID 45 54
Trunk Group Type T2 T2 Mandatory.
Trunk Group Name IP IP
Number Compatible
–1 –1
With
Remote Network 7 7 Enter a value other than 255
Shared Trunk Group False False

6-6   .  #)!"   , -")  !+!*

 , -")  !+!*

ISDN all ISDN all

Q931 Signal variant Mandatory.
countries countries
Channel selection type Quantity Quantity Mandatory.
Auto.DTMF dialing on
No No Mandatory.
outgoing call
T2 Specification IP IP Mandatory.
Can support UUS in
False False
SETUP

The other parameters can be left with their default values.

6.5.2 Declaring the Local Data

Object name: Trunk Groups > Trunk Group
Attribute N4 N5 Comments
Trunk Group ID 45 54
Trunk Group Type T2 T2
Supervised by Routing Yes Yes Mandatory for use of VPN hop
VPN Cost Limit for
0 0
Incom. Calls
Immediate Trk Listening
Yes Yes
if VPNCall
Enter 100% if the trunk group is
VPN TS % 100 100 dedicated to VPN hop on IP
only.
Quality profile for voice
Not used Not used
over IP
In the example, the G723
compressors will be used
IP Compression Type Default Default
(configured in system
parameters).
Trunk COS 19 19
B Channel Choice Yes Yes
Logical Channel 1_15 & 17_31 1_15 & 17_31

The other parameters can be left with their default values.

6.5.3 Declaring Trunk Group Access/Accesses

6.5.3.1 Example for a GD Board:
Object name: Trunk Groups > Trunk Group > T0/T1/T2 Access
Attribute N4 N5 Comments
Trunk Group ID 45 54

  .  #)!"   , -")  !+!* 6-7

Chapter 6 , -")  !+!*

Physical Address 3–0–0 3–0–0 GD/GA board access address.

Access Type T2 T2
Time Slots T2 01111111 01111111 DO NOT MODIFY
11111111 11111111 The number of compressors
01111111 01111111 available on the trunk group is
11111111 11111111 configured on the board.

Note:
From R6.0, the access is put into service without resetting the GD board.

6.5.3.2 Example for an INT-IP Board

1st trunk group access on access 0 of the board:
Object name: Trunk Groups > Trunk Group > T0/T1/T2 Access
Attribute N4 N5 Comments
Trunk Group ID 45 54
Physical Address 0–19–0 0–19–0 Address of the 1st access of the
INTIP board.
Access Type T2 T2
Time Slots T2 01111111 01111111 DO NOT MODIFY
11111111 11111111 The number of compressors
01111111 01111111 available on the trunk group is
11111111 11111111 configured on the board.

2nd access of the trunk group on access 1 of the board:

Object name: Trunk Groups > Trunk Group > T0/T1/T2 Access
Attribute N4 N5 Comments
Trunk Group ID 45 54
Physical Address 0–19–1 0–19–1 Address of the 2nd access of
the INTIP board.
Access Type T2 T2
Time Slots T2 01111111 01111111 DO NOT MODIFY
11111111 11111111 The number of compressors
01111111 01111111 available on the trunk group is
11111111 11111111 configured on the board.

Note:
When the access has been created, the INT-IP board is reset.

6.6 Configuring the VPN Hop

6.6.1 Declaring the VPN Hop

Object name: Inter-Node Links > VPN Overflow

6-8   .  #)!"   , -")  !+!*

 , -")  !+!*

Attribute N4 N5 Comments
The first number must be lower than the
Node X - Node Y 4–5 4–5
second.
Must be identical to the "Remote
Network 1 7 7 Network" attribute in the "Trunk Groups"
object.
Network 2 7 7
This value must be lower than "VPN Cost
VPN Hop cost 1 1 Limit" in the "Access COS" specified for
telephone sets.
Mandatory VPN hop in
True True
quality 0
Mandatory VPN hop in
True True
quality 1
The type of compression used is that
specified in system data (here G723).
Caution:
IP Compression Type Default Default
The manager must make sure that the two
ends of a "VoIP" link use the same
algorithm.

6.6.2 Enabling the VPN Service

This parameter must be enabled on all network nodes.
Object name: System > Other System Param.
Attribute N4 N5 Comments
VPN service True True Required to perform VPN hops.

The other parameters do not concern the VPN hop.

6.7 Configuring ARS

6.7.1 Declaring the ARS Route List

Object name: Translator > Automatic Route Selection > ARS Route list
Attribute N4 N5 Comments
ARS Route list 2 2
Name VPN VPN

6.7.2 Declaring the two ARS Routes

Declaration of the backup route to the public network. Trunk groups to the public network are

  .  #)!"   , -")  !+!* 6-9

Chapter 6 , -")  !+!*

not described in this document. They have no specific "VoIP" features.

Object name: Translator > Automatic Route Selection > ARS Route list > ARS Route
Attribute N4 N5 Comments
ARS Route list 2 2
Route 1 1
VPN FT Trunk VPN FT Trunk
Name
Group Group
Trunk Group 4 5
No.Digits To Be
0 0
Removed
Digits To Add 01411 01411
Numbering Command
0 0
Tabl. ID
VPN Cost Limit 0 0
Dependent on Dependent on
Protocol Type Trunk Group Trunk Group
Type Type
NPD identifier 0 0
Route Type Public Public
The "Fax" value must be added
Quality Speech Speech if fax communications are to be
made on this link.

Declaring the route on the IP network

Object name: Translator > Automatic Route Selection > ARS Route list > ARS Route
Attribute N4 N5 Comments
ARS Route list 2 2
Route 2 2
Name VPN IP VPN IP
Trunk Group 45 54
No.Digits To Be
0 0
Removed
Digits To Add No digit to be added.
Numbering Command
0 0
Tabl. ID
VPN Cost Limit 0 0
Dependent on Dependent on
Protocol Type Trunk Group Trunk Group
Type Type
NPD identifier 0 0
Route Type Public Public

6-10   .  #)!"   , -")  !+!*

 , -")  !+!*

The "Fax" value must be added

Quality Speech Speech if fax communications are to be
made on this link.

6.7.3 Declaring the Time-based Routes

Object name: Translator > Automatic Route Selection > ARS Route list > Time-based
Route List
Attribute N4 N5 Comments
ARS Route list 2 2
Time-Based Route List
1 1
ID
Time Based Route
Route Number 2 2 Route 2 on IP is selected by preference.
This route is always available, whatever
Waiting Cost Limit –1 –1 the "ARS privilege" of the party who
initiated the call.
This route is always available, whatever
Stopping Cost Limit –1 –1 the "ARS privilege" of the party who
initiated the call.
Route 1, on the public network, is chosen
Route Number 1 1
as backup.
This route is always available, whatever
Waiting Cost Limit –1 –1 the "ARS privilege" of the party who
initiated the call.
This route is always available, whatever
Stopping Cost Limit –1 –1 the "ARS privilege" of the party who
initiated the call.

6.8 Configuring User COS

The maximum cost of VPN hops authorized for a user is specified in the user's access COS.
Object name: Classes of Service > Access COS
Attribute N4 N5 Comments
This COS must be assigned to
Public Network COS 2 2
the user.
ARS privilege
Night 20 20
Day 20 20
Mode 1 20 20
Mode 2 20 20
VPN Cost Limit

  .  #)!"   , -")  !+!* 6-11

Chapter 6 , -")  !+!*

Night 30 30 Must be different from –1.

Day 30 30 Must be different from –1.
Mode 1 30 30 Must be different from –1.
Mode 2 30 30 Must be different from –1.

The other attributes are not related to VPN overflow.

6.9 Configuring the Dialing Plan Description

Object name: Translator > External Numbering Plan > Numbering Plan Description (NPD)
Attribute N4 N5 Comments
Description identifier 33 33
Name VPN VPN
Calling Numbering plan
Unknown Unknown
ident.
Called Numbering plan
Unknown Unknown
ident.
Authorize personal
False False
calling num use
Install. number source NPD source NPD source
Default number source NPD source NPD source
Called DID identifier –1 –1
Calling/Connected DID
–1 –1
identifier
Installation number 014111 014111
Default number (num.
3400 3500
inst. sup.)

6.10 Creating the Prefixes

6.10.1 Declaring the Local VPN Prefix

Object name: Translator > Prefix Plan
Attribute N4 N5 Comments
Number 34099 35099
Prefix Meaning VPN Overflow VPN Overflow
Must correspond to the NPD
Prefix information 33 33
declared previously.
Local (NPD
VPN Type Local (NPD No.)
No.)

6-12   .  #)!"   , -")  !+!*

 , -")  !+!*

6.10.2 Declaring the Remote VPN Prefix

These prefixes are created automatically if broadcast is enabled. However, the "Prefix
Information" attribute must be modified (broadcast with the value –1) so that it references the
local ARS route list which corresponds to the ARS VPN IP route.
Object name: Translator > Prefix Plan
Attribute N4 N5 Comments
Number 35099 34099
Prefix Meaning VPN Overflow VPN Overflow
Must correspond to the ARS
Prefix information 2 2 Route list ID declared for "Voice
over IP".
Distant(List Distant(List
VPN Type
route No.) route No.)

  .  #)!"   , -")  !+!* 6-13

Chapter 6 , -")  !+!*

6-14   .  #)!"   , -")  !+!*

 

 $

7.1 compvisu Command

The following commands are used to control the ABC-F logical link on IP activity.

7.1.1 compvisu lio Command

This command gives IP board state and the number of compressors available on them.
> compvisu lio
+==============================================================================+
| C O M P V I S U |
+==============================================================================+
| cr | cp | type dsp | coupler state | H323 Gateway | IP device |
| | | | | free/max | free/max |
|----|----|------------------|--------------------|--------------|-------------|
| 3 | 0 | GD MCV24*| IN SERVICE | 0/12 | 12/12 |
| 19 | 1 | INTIPA 1GIP6*| IN SERVICE | no | 0/0 |
| 19 | 2 | INTIPA 1GIP6*| OUT OF SERVICE | no | 0/0 |
|------------------------------------------------------------------------------|
| '*' mean : transit is not provided on this board. |
+==============================================================================+

7.1.2 compvisu ip add Command

This command displays the configuration of:
- IP trunk groups.
- IP boards.
> compvisu ip add
+==============================================================================+
| C O M P V I S U |
+==============================================================================+
| TG | Name | IP address | Pos, IP Parameters |
|------|------------|-----------------|----------------------------------------|
| 998 | VOIP_N99 | remote TG | node 99 |
| 999 | VOIP_N9 | 192.1.101.55 | 3-0 , 21 comp, G723, QoS inferior |
+==============================================================================+
| Ouput of IP boards parameters |
+==============================================================================+
|cr-cp| board address | netmask | gateway | gatekeeper |sed|comp|
|-----|---------------|---------------|---------------|---------------|---|----|
| 3-0 | 192.1.101. 55| 255.255.255.0| 192.1.101.254|no interworking|ynn| 21 |
|-----+---------------+---------------+---------------+---------------+---+----|
| s:in service e:embedded interface d:daughter board |
+==============================================================================+

7.1.3 compvisu IP Command

This command displays a list of:
- IP trunk groups.
- IP abbreviated numbers.

!    !!!"   ' )!! 7-1

Chapter 7 ' )!!

> compvisu ip
+==============================================================================+
| C O M P V I S U |
+==============================================================================+
| TG | Name | IP address | Pos, IP Parameters |
|------|------------|-----------------|----------------------------------------|
| 998 | VOIP_N99 | remote TG | node 99 |
| 999 | VOIP_N9 | 192.1.101.55 | 3-0 , 21 comp, G723, QoS inferior |
+==============================================================================+
| IP abbrev numb. | Prefix | User | IP address |
|-----------------|--------------|----------------|----------------------------|
| 3556 | 12 | Da Silva Manuel| 165.142.65.169:12 |
|-----------------|--------------|----------------|----------------------------|
+==============================================================================+

7.1.4 compvisu sys Command

This command displays VoIP "system" parameters.
+==============================================================================+
| C O M P V I S U |
+==============================================================================+
| RTP Direct..................... yes |
| RTP Direct for H323 terminals.. no |
| Fast Start..................... yes |
| VAD (Voice Activity Detection): |
|- G723/G729 ...... no |
|- G711 ........... no |
| ECE (Echo Canceller)........... yes |
| PFE (Post Filter).............. yes |
| Volume ........................ 8 |
| Volume for IP Phone ........... 0dB |
| Volume for other device. ...... 0dB |
| VRE ........................... no |
| Law (Except Media Gateway)..... A law |
| Global compression type ....... G723 |
| Multi-algorithm (for H323) .... no |
| Transit on IP Boards ...........yes |
| ticket Stat IP................. no |
| IP version..................... IPv4 |
| Enhanced voice quality......... yes |
| IP QoS Data Life Time.......... 10 min |
| profile packet loss jitter delay |
| * Profile #1 (#1) 5% 75ms 600ms |
| * Profile #2 (#2) 3% 50ms 400ms |
| * Profile #3 (#3) 1% 20ms 150ms |
+==============================================================================+

7.1.5 compvisu -r visu Command

This command displays calls in progress on IP trunk groups and the resources used. The “-r”
option ensures periodic “Refresh”.
+==============================================================================+
| C O M P V I S U |
+==============================================================================+
| Coupler | address | TG/LK | neqt | cpr | connected with : |
|----------+---------+-------+------+-----+------------------------------------|
| GD | 3-0-0-1 | 23 | 258 | no | eqt 321, 3000 : Martin Antoine |
+==============================================================================+

7.1.6 compvisu ras Command

This command displays the gatekeeper parameters and E164 numbers used for the INT-IP
board in its configuration parameters.

7-2 !    !!!"   ' )!!

 ' )!!

(56)pabx56> compvisu ras 3 0

+==============================================================================+
| C O M P V I S U |
+------------------------------------------------------------------------------+
| Output of INTIP board declared on 3-0 |
+==============================================================================+
| BOARDS PARAMETERS |
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+
| Cr-Cp | Gatekeeper used | Gatekeeper number | e164 list number |
+------------------------------------------------------------------------------+
| 3-0 | yes | 0 | 1 |
+==============================================================================+
+==============================================================================+
| GATEKEEPERS PARAMETERS |
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+
|no GK| GK IP address | Gatekeeper name |GK WECC|Alternative GK|
+------------------------------------------------------------------------------+
| 0 |10.253.4.80 | GK1| no | |
+==============================================================================+
+==============================================================================+
| E164 NUMBERS |
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+
| list number : 1 |
+------------------------------------------------------------------------------+
| 3001 | 3002 |
| 3003 | 3004 |
+==============================================================================+

7.2 cmdcpl Command

The command cmdcpl <Cr_Nbr> <Cpl_Nbr> MNGT is used to check the configuration of
an INT-IP board.
Note 1:
This command is not available on the INT-IP3 board.
The command cmdcpl <Cr_Nbr> <Cpl_Nbr> H323 displays data transmitted to the
gateway by the CPU.
(3)BCastill> cmdcpl 0 2 H323
Del to exit tool
You have selected a board with type : INTIPA
execution from 'H323'
(00,02) +-------------------------------------------------------+
(00,02) | H323 Informations sent by the CPU |
(00,02) +-------------------------------------------------------+
(00,02) | Inter-Node Protocol H323 Boolean :0 |
(00,02) | Fast_Start Boolean :0 |
(00,02) | Channel Number :30 |
(00,02) | Ras Address : 172.26.18.100 : port 1719 |
(00,02) | Alternate Ras Address : 0.0.0.0 : port 0 |
(00,02) | H323 Identifier : Central |
(00,02) | GK_is_WECC Boolean :0 |
(00,02) | Internode_calls_when_GK_not_reachable Boolean :0 |
(00,02) | GK must register 001 e164 number(s) |
(00,02) | 5 4 0 0 |
(00,02) +-------------------------------------------------------+
Normal exit.
The command cmdcpl <Cr_Nbr> <Cpl_Nbr> RAS displays gatekeeper parameters
effectively used by the board.

!    !!!"   ' )!! 7-3

Chapter 7 ' )!!

(2)BPgetafe> cmdcpl 0 17 RAS

Del to exit tool
You have selected a board with type : INTIPA
execution from 'RAS'
(00,17) GK parameters:
(00,17) State: GK is chosen and GW is registered
(00,17) RasAddress : 172.26.18.100 : port 1719
(00,17) Identifier: Central
(00,17) GK is not a WECC
(00,17) used banddwidth: 0 bits/s
(00,17) ongoing calls: 0
(00,17) GW seen by GK
(00,17) H323 Id: GW_0_17_172.26.144.232
(00,17) Identifier: 6137D9E800000002Normal exit.

Note 2:
This command is dedicated to the ABC-F ligical link on IP activity.

7.3 lookvpn Command

The command lookvpn -test is used to display the entire VPN hop configuration.
Note:
This command is dedicated to the ABC-F ligical link on IP activity.

7.4 Trkstat Command

The Trkstat command is used to display the busy status of trunks in the selected ABC link
through IP.

7.5 Trkvisu Command

The Trkvisu command is used to give certain data on the selected ABC link through IP.

7.6 Incidents
These incidents documented below are dedicated to the ABC-F ligical link on IP activity.

7.6.1 Incident 4102

Label: Insufficient VPN resources
Explanation: indicates a lack of local VPN prefixes. This incident is output on the node of
arrival.
For each call, the local prefix is "reserved" until the expected DID call arrives. If the call fails
(wrong outgoing number or other reason), there may be a lack of prefixes to handle traffic:
therefore, some prefixes must be added.

7.6.2 Incident 4103

Label: Incoming VPN call interrupted N° C 8399
Explanation: the VPN call expected on the 8399 never arrived. However, the call was
successful on the caller side.

7-4 !    !!!"   ' )!!

 ' )!!

The 30 sec. timer on the arrival node has elapsed.

7.6.3 Incident 4104

Label: Outgoing VPN overflow call failed N° XX Number
Explanation: the call failed on the departure node where:
- N° XX = Cause of failure according to link used: ISDN, VoIP.
Cause corresponds to the real causes for decimal (rotary) disconnection received by the
public or private carrier.
On VoIP, the causes are directly generated by the IP coupler board.
The following causes are specific to the IP coupler board:
• 49 = Invalid quality of service (linked with the IP network).
• 100 = invalid EI reception
• 42 = network congestion
• 41 = temporarily out of service
- Number = External number dialed to call the remote (distant) VPN prefix: this is either a
public number or the VPN prefix directly if it is a VoIP trunk group.
Example:
- Incident 4104: Outgoing VPN overflow call failed N° 34 015667000 => reception of "No channel
available" on T2 if call from 015667000
- Incident 4104: Outgoing VPN overflow call failed N° 49 8399 => reception of a poor QoS on IP on the
prefix 8399 message.

7.6.4 Incident 4108

Label: VPN call failed: err 143N NL 1 > 9
Explanation: this incident does not concern the node on which it is output. It is linked with
incident 4103 or 4104 and indicates that the destination node never received the VPN call.
<1> is the calling (originating) node and <9> the called (destination) node.
In the example, N9 was released when the timer elapsed as it did not receive the expected call
transmitted from N1.

7.6.5 Examples
- Incorrect outgoing number => incident 4104 on the departure node.
- Wrong public number but another destination is rung => incident 4103 on the arrival node
and incident 4108 on the departure node.
- No free channels => incident 4104 on the departure node.
- Too much VPN traffic for the number of prefixes => incident 4102.

!    !!!"   ' )!! 7-5

Chapter 7 ' )!!

7-6 !    !!!"   ' )!!