0% found this document useful (0 votes)
164 views80 pages

Alcatel Omnipcx Enterprise: Hybrid Logical Links

Uploaded by

Ariel Becerra
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
164 views80 pages

Alcatel Omnipcx Enterprise: Hybrid Logical Links

Uploaded by

Ariel Becerra
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 80

Alcatel OmniPCX Enterprise

Hybrid Logical Links


NOTE:

Product specifications contained in this document are subject to change


without notice. Products and services described in this document may not be
offered in every country. For the most current information, please contact
your Alcatel representative or your Alcatel equipment provider.

Copyright (c) 2006 Alcatel. All rights reserved for all countries. This
document may not be reproduced in whole or in part without the express
written permission of Alcatel.

Alcatel® and the Alcatel logo are registered trademarks of Alcatel. All other
trademarks are the property of their respective owners.

The CE mark indicates that this product conforms to the following Council
Directives:
- 89/336/CEE (concerning electro-magnetic compatibility)
- 73/23/CEE (concerning electrical safety)
- 1999/5/CE (R&TTE)


 

 


Chapter 1
Overview

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

Chapter 2
Basic description

 Principle ..................................................................................................... 2.1


 Signaling ................................................................................................... 2.1
 Voice channels ........................................................................................ 2.1
 Hybrid local link ...................................................................................... 2.2

Chapter 3
Detailed description

 Routing Type ............................................................................................ 3.1


 Setting up the Logical Link ................................................................. 3.1
 Logical Link "on Request" .......................................................................... 3.1
 Permanent Logical Link .............................................................................. 3.2


 
 0-1

 


 Backup Signaling ................................................................................... 3.2


 Multiplexer ................................................................................................ 3.2
 Creating the Digital Access of the Support .................................. 3.4
 Compressed Access ............................................................................. 3.4
 Hybrid Logical Link with Signaling over IP ................................... 3.4

Chapter 4
Configuration procedure

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


 Declaring the Logical Link .................................................................. 4.1
 Declaring the Hybrid Logical Link Access .................................... 4.2
 Create ........................................................................................................... 4.2
 Enable - Disable ........................................................................................... 4.4
 Creating the Digital Access of the Support .................................. 4.4
 Voice Channels ....................................................................................... 4.6

Chapter 5
Configuring access without signaling

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


 Declaring the Access ............................................................................ 5.1
 Requirements ............................................................................................... 5.1
 Principle ....................................................................................................... 5.1
 Creating the Access .................................................................................... 5.2
 Deleting the Access .................................................................................... 5.3
 Declaring Voice Channels ................................................................... 5.3

0-2 
 


 


Chapter 6
Configuring IP signaling

 Overview .................................................................................................... 6.1


 Prerequisites ............................................................................................ 6.1
 Basic Principles ...................................................................................... 6.1
 Checking X25 System Parameters ................................................... 6.1
 Declaring the Hybrid Logical Link Access with Signaling over
IP .................................................................................................................. 6.1

Chapter 7
Configuring D channel signaling

 Overview .................................................................................................... 7.1


 Declaring the Access ............................................................................ 7.1
 Requirements ............................................................................................... 7.1
 Principle ....................................................................................................... 7.1
 Creating the Access .................................................................................... 7.2
 Declaring Voice Channels ................................................................... 7.2

Chapter 8
Configuring switched T1 - T2 B channel signaling

 Overview .................................................................................................... 8.1


 Declaring the Access ............................................................................ 8.1
 Requirements ............................................................................................... 8.1
 Principle ....................................................................................................... 8.1


 
 0-3

 


 Creating the Access .................................................................................... 8.2


 Declaring Voice Channels ................................................................... 8.3

Chapter 9
Configuring leased T1 - T2 B channel signaling

 Overview .................................................................................................... 9.1


 Declaring the Access ............................................................................ 9.1
 Requirements ............................................................................................... 9.1
 Principle ....................................................................................................... 9.1
 Creating the Access .................................................................................... 9.2
 Declaring the Hybrid Trunk Group Address Prefix .................................. 9.2
 Creating the Digital Access of the Support .............................................. 9.3
 Declaring Voice Channels ................................................................... 9.3

Chapter 10
Configuring leased PCM B channel signaling

 Overview ................................................................................................... 10.1


 Declaring the Access ........................................................................... 10.1
 Requirements .............................................................................................. 10.1
 Principle ...................................................................................................... 10.1
 Creating the Access ................................................................................... 10.2
 Declaring Voice Channels .................................................................. 10.3

Chapter 11
Configuring synchronous modem signaling

0-4 
 


 


 Overview ................................................................................................... 11.1


 Declaring the Access ........................................................................... 11.1
 Requirements .............................................................................................. 11.1
 Principle ...................................................................................................... 11.1
 Create the Local TA .................................................................................... 11.1
 Creating the Access ................................................................................... 11.3
 Deleting the Access ................................................................................... 11.3
 Declaring Voice Channels .................................................................. 11.3

Chapter 12
Configuring leased virtual voice signaling

 Overview ................................................................................................... 12.1


 Declaring the Access ........................................................................... 12.1
 Requirements .............................................................................................. 12.1
 Principle ...................................................................................................... 12.1
 Creating the Access ................................................................................... 12.2
 Creating the Digital Access of the Support ............................................. 12.3
 Declaring Voice Channels .................................................................. 12.3

Chapter 13
Configuring switched virtual voice signaling

 Overview ................................................................................................... 13.1


 Declaring the Access ........................................................................... 13.1
 Requirements .............................................................................................. 13.1
 Principle ...................................................................................................... 13.1
 Creating the Access ................................................................................... 13.2
 Declaring Voice Channels .................................................................. 13.2


 
 0-5

 


Chapter 14
Configuring virtual Transfix leased signaling

 Overview ................................................................................................... 14.1


 Declaring the Access ........................................................................... 14.1
 Requirements .............................................................................................. 14.1
 Principle ...................................................................................................... 14.1
 Modifying the Transfix Access .................................................................. 14.2
 Creating the Access ................................................................................... 14.3
 Declaring Voice Channels .................................................................. 14.3

Chapter 15
Configuring virtual frame relay signaling

 Overview ................................................................................................... 15.1


 Declaring the Access ........................................................................... 15.1
 Requirements .............................................................................................. 15.1
 Principle ...................................................................................................... 15.1
 Modifying the Transfix Access .................................................................. 15.2
 Creating the Access ................................................................................... 15.3
 Declaring Voice Channels .................................................................. 15.3

Chapter 16
Configuring non-compressed voice channels

 Principle .................................................................................................... 16.1


 Declaring the Access ........................................................................... 16.1

0-6 
 


 


 Requirements .............................................................................................. 16.1


 Principle ...................................................................................................... 16.1
 Creating a Hybrid Link Trunk .................................................................... 16.2

Chapter 17
Configuring compressed voice channels

 Overview ................................................................................................... 17.1


 Declaring Voice Channels .................................................................. 17.1
 Requirements .............................................................................................. 17.1
 Creating Compressed Voice Channels .................................................... 17.1

Chapter 18
Configuring hybrid local links

 Overview ................................................................................................... 18.1


 Declaring the Local Hybrid Logical Link ....................................... 18.1
 Principle ...................................................................................................... 18.1
 Creating the Local Hybrid Logical Link .................................................... 18.1
 Creating the Hybrid Logical Link Access ................................................. 18.2
 Creating the Access Prefix ........................................................................ 18.2
 Creating the Network Routing List/Table ................................................. 18.3

Chapter 19
Maintenance

 Resetting a Hybrid Logical Link ....................................................... 19.1


 Trunk Supervision ................................................................................ 19.1


 
 0-7

 


 Hybrid Access Display ........................................................................ 19.2


 Traces on the Hybrid Link .................................................................. 19.3
 Malfunctions ........................................................................................... 19.3
 The Hybrid Logical Link is not Established ............................................. 19.3
 The Hybrid Logical Link is Established but there is no Communication ...
19.4

0-8 
 


 

1 

1.1 Overview
A hybrid logical link is used to connect two nodes of an ABC network.
A hybrid logical link is composed of one or more accesses. Each access includes:
- A signaling channel.
- Voice channels (0 to 30 maximum).
Compared to a standard logical link, a hybrid logical link has the following advantages:
- Several accesses of different types can be used.
- For all accesses used, there may be more than thirty voice channels.
Only one logical link between two nodes can be used on an ABC network.
This manual includes:
- A common section for all types of hybrid logical links.
- A specific section on each type of signaling:
• Without signaling, see module Hybrid logical links - Configuring access without
signaling .
• IP signaling, see module Hybrid logical links - Configuring IP signaling .
• D channel signaling on a T2 or T1 link, see module Hybrid logical links - Configuring D
channel signaling .
• B channel signaling on a:
• Switched T2 or T1 support, see module Hybrid logical links - Configuring switched
T1 - T2 B channel signaling .
• Leased T2 or T1 support, see module Hybrid logical links - Configuring leased T1 -
T2 B channel signaling .
• Leased PCM support, see module Hybrid logical links - Configuring leased PCM B
channel signaling .
• Synchronous modem signaling, see module Hybrid logical links - Configuring
synchronous modem signaling .
• Virtual (compressed) signaling on a:
• Leased support, see module Hybrid logical links - Configuring leased virtual voice
signaling .
• Switched support, see module Hybrid logical links - Configuring switched virtual
voice signaling .
• Transfix support, see module Hybrid logical links - Configuring virtual Transfix
leased signaling .
• Frame Relay support, see module Hybrid logical links - Configuring virtual frame
relay signaling .
- A specific section on each type of voice support:
• Non-compressed voice channels, see module Hybrid logical links - Configuring
non-compressed voice channels .

      ! "  #$$% 1-1


Chapter 1 #$$%

• Compressed voice channels, see module Hybrid logical links - Configuring


compressed voice channels .
• VPN overflow, see module VPN overflow - Overview .
- A specific section on the local hybrid logical link, see module Hybrid logical links -
Configuring hybrid local links .

1-2       ! "  #$$%



 

2
  

2.1 Principle
A hybrid logical link is composed of one or more accesses. Each access is composed of a
signaling channel and voice channels. A hybrid logical link may have several accesses, each
with a different support.

2.2 Signaling
ABC type signaling is used. It transports the following information between two nodes:
- Call setup messages.
- Routing information.
- Configuration information broadcasts.
- Accounting information broadcasts.
- ..........
The signaling support is referred to as the "signaling channel". There are several types of
signaling channel:
- IP signaling.
- D channel signaling.
- B channel signaling. Several types of B channel may be used:
• The B channel of a leased T1 or T2.
• The B channel of a switched T1 or T2.
• The B channel of a leased PCM link.
• The B channel of a QSIG-GF network.
- Synchronous modem signaling.
- Signaling on a virtual support (also called "compressed signaling"):
• "Leased virtual voice" channel signaling.
• "Switched virtual voice" channel signaling.
• “Virtual Transfix” signaling.
• “Virtual Frame Relay” signaling.
An access with no signaling channel may also be used. In this case, the signaling for this
access is transferred to another access.

2.3 Voice channels


According to the type of signaling used, the voice channels associated with an access are:
- Supported by non-compressed B channels.
- Supported by compressed B channels.

"       ! "  &   !  2-1


Chapter 2 &   ! 

- Nonexistent, in this case, VPN overflow must be used.

2.4 Hybrid local link


The local hybrid link is a "workaround" solution used for the OmniTouch Contact Center.

2-2 "       ! "  &   ! 



 

3    

3.1 Routing Type


Routing determines the path a call must follow to reach a remote node. Each node has a route
list. For each target node, this list gives the adjacent node to be reached. Routing messages
inform each PCX of network congestion. There are two types of routing:
- Dynamic routing: routing messages are used to update the route lists of each PCX. To limit
the traffic generated by routing information, only 32 nodes can use the "dynamic routing"
feature. These nodes are referred to as “backbone nodes”.
- Static routing: routing information is ignored. Call are always sent to the same node. This
type of routing is only suitable for "end nodes".

Figure 3.1: Example of an ABC Network


- Nodes N1 to N4 are “backbone” nodes. For each node, there are several routing
possibilities. Routing must be dynamic.
- Nodes N5 and N6 are end nodes, static routing may be used on these nodes. Due to the
physical configuration, network calls always transit via node N4, the only adjacent node.

3.2 Setting up the Logical Link

3.2.1 Logical Link "on Request"


A logical link "on request" is a logical link with a switched signaling support. A switched support
is charged by the public operator (carrier). To reduce cost, the support is only set up when a
call is requested.
Setup "on request" is incompatible with dynamic routing. This is because dynamic routing

""   "  '  (  )!   !  3-1


Chapter 3 )!   ! 

continually generates routing messages and these messages are lost when the support is not
set up. Consequently, a logical link set up on request is only suited to end nodes.

3.2.2 Permanent Logical Link


A permanent logical link is set up at initialization. Signaling is never interrupted and can
transport routing, accounting and management information. This type of logical link is suitable
for links that are not charged, leased links for example.

3.3 Backup Signaling


A hybrid logical link is composed of a signaling channel and voice channels. A break in the
physical signaling support results in a loss of signaling. The voice channels associated with
this access can then no longer be used.
In some configurations, the signaling and voice channels do not share the same physical
support. Loss of signaling results in loss of the corresponding voice channels, which would
otherwise remain potentially useable.
In this case, backup (or "standby") signaling allows any voice channels with a faulty main
signaling channel to continue to be used.

Figure 3.2: Example of Backup Signaling


In the above example, there is
- A main signaling channel over IP and 30 voice channels on the T2 link.
- A backup (standby) signaling channel on a TS of the T2 link.
When the IP network is faulty, signaling is directed to the TS on the T2 link.
If signaling fails, a single node is responsible for re-establishing it. If both nodes were to
attempt to re-establish signaling, two signaling channels would be set up simultaneously and
this could cause conflicts.

3.4 Multiplexer
A multiplexer is an external device that is not part of the OmniPCX Enterprise. This device
handles the time slots (TSs) of a T1, T2 or PCM digital link. It optimizes use of leased links.
A multiplexer is used to:
- Transport only certain TSs of a T2 link.

3-2 ""   "  '  (  )!   ! 


)!   ! 

- On the same T2 link, some TSs are transported to one destination and other TSs to a
different destination.
Multiplexer configuration tables are used to determine the destination of each TS.

Figure 3.3: Example of Multiplexer Use


In this example, only three TSs of the T2 link are used. The multiplexer matches TS 1 on node
1 with TS 1 on node 2.

Figure 3.4: Example of a Multiplexer Used between Three Nodes


When a multiplexer is installed:
- its configuration is needed to know which TSs are matched.

""   "  '  (  )!   !  3-3


Chapter 3 )!   ! 

- The D channel is not transmitted.

3.5 Creating the Digital Access of the Support


Creating a digital access allows level 2 of a T2 or T1 support to be enabled. This must be done
before a TS of a leased T2 or T1 support can be used.
This TS can be used for:
- Signaling on a leased B channel (T2 or T1).
- A virtual compressed voice link on a leased B channel (signaling + voice channel).
- A voice channel on a leased B channel.
Even if the same support is used for several different purposes, it only needs to be created
once.
If signaling is on the D channel, the channel automatically enables level 2.

3.6 Compressed Access


A compressed access is composed of six voice channels and a signaling channel on a
64-Kbits B channel. Compression boards (LIOB, LIOP or LIOX) are required. The support for
the B channel may be:
- Leased T0 or T2.
- Switched T0 or T2.
- Leased Transfix.
- Frame relay.

3.7 Hybrid Logical Link with Signaling over IP


For this type of hybrid logical link, signaling is sent on an Ethernet network using the Internet
protocol (IP). Signaling is exchanged between the Ethernet interfaces of the Call Servers.

3-4 ""   "  '  (  )!   ! 


)!   ! 

Figure 3.5: Hybrid Logical Link Representation with Signaling over IP


Signaling is routed on IP datagrams over the IP network. On each node, there is an access
point corresponding to the hybrid application. The hybrid application is responsible for
transferring the datagrams between the two nodes.
This operation involves declaring the remote node IP address in the hybrid logical link access.
The IP address to declare depends on remote node configuration:
- A remote node with one single Call Server. In this configuration, the IP address to declare
is the physical IP address of the Call Server or its main IP address
- A remote node with duplicated Call Server and both Call Servers on the same IP
subnetwork. In this configuration, the IP address to declare is the main IP address used for
both Call Servers
- A remote node with duplicated Call Server and both Call Servers on different IP
subnetworks. In this configuration available from R6.1, each Call Server is identified by its
own main IP address. Each main IP address of Call Server must be declared in the hybrid
logical link access
Caution: A hybrid logical link with signaling over IP cannot be set up between a R6.0 node (or
lower) and a R6.1 node operating in a duplicated Call Server configuration with the two Call
Servers on different IP subnetworks.
In this configuration, the IP signaling set up is as follows:
___change-begin___
""   "  '  (  )!   !  3-5
Chapter 3 )!   ! 
___change-end___
Figure 3.6: IP Signaling Channel Set up to a Remote Node with both Call Servers on Different IP
Subnetworks
Principle:
a. A connection request is sent towards the main IP addresses of Call Servers on the
remote node
b. Only the main Call Server answers. The IP signaling channel is set up between the two
nodes
X25 system parameters are used to configure the retransmission of IP datagrams, as well as
the transmission of the monitoring packets on the hybrid logical links with IP signaling. These
parameters are available for hybrid logical links with signaling over IP only.

3-6 ""   "  '  (  )!   ! 



 

4    

4.1 Overview
To configure a hybrid logical link:
- Declare a “hybrid” logical link.
- Declare the access/accesses (and their respective signaling channels) for this hybrid link.
- Declare the voice channels for each access.
Declare a VPN hop (if required). For more information on VPN hops, see module VPN
overflow - Overview .

4.2 Declaring the Logical Link


1. Select Inter-Node Links > Logical Links (ABC-F)
2. Review/modify the following attributes:
Link Name Enter the name of the logical link. This name may be freely
chosen (10 characters max.).
Usually, the name assigned indicates the names of the
nodes connected. The logical link between N2 and N3 is
named "N2–N3".
Link Type Select Hybrid.
Adjacent Node Enter the number of the remote node.
Adjacent Network Enter the ABC subnetwork number of the remote node.
Trunk COS Category 18 is recommended.
B Channel Choice YES: exclusive channel requested.
NO: preferred channel requested.
TS Overflow YES: voice calls can overflow to the B channels reserved for
data calls.
NO: no overflow.
Monitored by CSTA True: the logical link is controlled by the CSTA application.
False: the logical link is independent from CSTA.
Incidents Teleservice YES: incidents generated by the logical link are sent to the
RMA application.
NO: the RMA is not informed of incidents on the logical link.
Signal Establis. Mode Select:
• Permanent User: the logical link is always established.
• On Request: the logical link is only established when a
call is made.

"      ! "  * + ,!    , 4-1


Chapter 4 * + ,!    ,

Routing Type Select:


• Dynamic Routing: for dynamic routing.
Note: This type of routing is incompatible with On Request link
setup.
• Static Routing: for static routing.
TS Distribution on Accesses YES: the first B channel is on the first access, the second on
the second access, etc. .
NO: the second access is only used if the first access is
saturated or cannot be used.
Multi access hybrid link YES: the remote node accepts several accesses on a hybrid
link.
NO: the remote node only accepts a single access on a
hybrid link. This is the case for earlier releases (R3 and
lower).
Release Support Timer (1s) This parameter is only displayed when "On Request"
setup/establishment is selected.
Enter time (in seconds) between release of the last call and
disconnection of the support.
Protection Timer (1mn) This parameter is only displayed when "On Request"
setup/establishment is selected.
Enter maximum call duration (in minutes). The value 0
represents an indefinite time.
MUX presence YES: a multiplexer is used. It is not necessary to establish
level 2 for a leased T2 (or T1) before using the TSs.
NO: no multiplexer. It is necessary to establish level 2 for a
leased T2 (or T1) before using TSs.

3. Confirm your entries

4.3 Declaring the Hybrid Logical Link Access

4.3.1 Create
Each access is configured with its signaling.
1. Select Inter-Node Links > Logical Links (ABC-F) > Hybrid Link Access
2. Review/modify the following attributes:
Link Name Enter the name of the hybrid logical link.
Access number Enter the number of the access. This must be the same on
both nodes.
Signaling type Select signaling type. See note 1 (below).
Main established tempo Enter the time required for this type of signaling to be set up.
When this time elapses, the system attempts to set up
backup signaling.

4-2 "      ! "  * + ,!    ,


* + ,!    ,

Has StandBy Signaling True: backup signaling is used when the main signaling
channel is faulty.
False: no backup signaling.
StandBy Signaling Type Select backup signaling type:
• Unused: no backup signaling.
• Other cases, see Note 2 (below).
Network Date Time Update YES: the access is used to transmit time.
NO: time is not transmitted on this access.
StandBy Established Tempo Enter wait time before backup signaling is set up.
StandBy Signal Always True: backup signaling is permanently established.
Established False: backup signaling is established on request.
Tempo Max for StandBy Enter max. duration for backup signaling setup. When this
Established timer elapses, the hybrid access is declared to be out of
service.
StandBy Switch Tempo Enter time before the first attempt to set up backup signaling
is made.
Main Switch Tempo Enter time before re-establishment of the main signaling
channel is attempted.

3. Confirm your entries


Note 1: Main signaling channel:
For each type of signaling, the system requests additional information. Each possible case is
covered in a specific section:
- Without signaling, see module Hybrid logical links - Configuring access without signaling
.
- IP signaling, see module Hybrid logical links - Configuring IP signaling .
- D channel signaling, see module Hybrid logical links - Configuring D channel signaling ,
- B channel signaling. Several types of B channel may be used:
• The B channel of a switched T1 or T2, see module Hybrid logical links - Configuring
switched T1 - T2 B channel signaling .
• The B channel of a leased T1 or T2, see module Hybrid logical links - Configuring
leased T1 - T2 B channel signaling ,
• The B channel of a leased PCM link, see module Hybrid logical links - Configuring
leased PCM B channel signaling .
• The B channel of a GSIG-GF network. Configuration is the same as for a switched
T2 logical link, see module Hybrid logical links - Configuring switched T1 - T2 B
channel signaling .
- Synchronous modem signaling, see module Hybrid logical links - Configuring
synchronous modem signaling ,
- Signaling on a virtual support (compressed signaling):
• Leased virtual voice channel signaling, see module Hybrid logical links -
Configuring leased virtual voice signaling .
• Switched virtual voice channel signaling, see module Hybrid logical links -
Configuring switched virtual voice signaling .
• Virtual Transfix signaling, see module Hybrid logical links - Configuring virtual

"      ! "  * + ,!    , 4-3


Chapter 4 * + ,!    ,

Transfix leased signaling .


• Virtual Frame Relay signaling, see module Hybrid logical links - Configuring virtual
frame relay signaling .
Note 2: Backup signaling:
As for main signaling, the system requires the same additional information. Refer to the
sections indicated in Note 1 (above).

4.3.2 Enable - Disable


Each hybrid logical link is associated with an X25 access cluster. This cluster is assigned
when the logical hybrid link is created. The hybrid logical link functions if the corresponding
X25 access cluster is operational. The hybrid logical link may only be modified if the X25
access cluster is disabled. The X25 access cluster is enabled/disabled via the following object:
1. Select Inter-Node Links > Logical Links (ABC-F) > Hybrid Link Access > X25
Synchronization Hybrid Link Access
2. Review/modify the following attributes:
Link Name Enter the name of the hybrid logical link.
Access number Enter the number of the access.
ACTION/INFORMATION
X25 Cluster access Select:
• Enable: to enable the X25 cluster.
• Disable: to disable the X25 cluster.

3. Confirm your entries

4.4 Creating the Digital Access of the Support


Creating a digital access allows level 2 of a T2 or T1 support to be enabled. The creation
operation must be performed on both nodes.
Depending on the type of signaling used, it may or may not be necessary to create a digital
access.

4-4 "      ! "  * + ,!    ,


* + ,!    ,

Figure 4.1: Objects Required to Create a Digital Access


Physical address is expressed in the format: “Shelf number” - ”Board number” - ”Digital access
number”.
Time Slots: do not create any TSs on this access.
Declare the trunk group:
1. Select Trunk Groups
2. Review/modify the following attributes:
Trunk Group ID Enter trunk group number.
Trunk Group Type Select: T2, T1CCS or T0 according to the support used.

3. Confirm your entries


Declare the trunk group access:
1. Select Trunk Groups > Trunk Group > T2/T1/T0 Access
2. Review/modify the following attributes:
Trunk Group ID Enter trunk group number.
Access Type Select the type of access corresponding to the support: T0,
T1CCS, T2.
Physical Address Enter the physical address of the support in the format:
“Shelf number” - ”Board number” - ”Digital access number”.
Time Slots T2 Set all TS for this support to 0: 00000000000000000...... .

3. Confirm your entries

"      ! "  * + ,!    , 4-5


Chapter 4 * + ,!    ,

4.5 Voice Channels


There are several possible solutions:
- Non-compressed support, see module Hybrid logical links - Configuring non-compressed
voice channels .
- Compressed support, see module Hybrid logical links - Configuring compressed voice
channels .
- VPN overflow, see module VPN overflow - Configuration procedure .

4-6 "      ! "  * + ,!    ,



 

5    


 

5.1 Overview
An access without a signaling channel uses the signaling channel of another access.
This feature is used to declare an access intended only to add voice channels. As a physical
support is already used for signaling, it is not necessary to use another.

Figure 5.1: Example Configuration with an Access without Signaling


Accesses 1 and 2 have signaling channels.
Access 3 is used only to provide more B channels (that can be used for data calls) and uses
the signaling channel on access 1. The fact that it does not have its own signaling channel
means that access 3 saves on the TS normally dedicated to signaling.
This type of access uses non-compressed voice channels.

5.2 Declaring the Access

5.2.1 Requirements
The hybrid logical link must already have been created before the access can be created (see,
module Hybrid logical links - Configuration procedure ).

5.2.2 Principle

(      ! "  * + ,   %!- ,!   5-1
Chapter 5 * + ,   %!- ,!  

The access providing signaling must already have been configured before an "access without
signaling" can be created.
On both nodes, the access providing signaling must be the same (see figure below).

Figure 5.2: Example Configuration of an Access without Signaling

5.2.3 Creating the Access


1. Select Inter-Node Links > Logical Links (ABC-F) > Hybrid Link Access
2. Review/modify the following attributes:

5-2 (      ! "  * + ,   %!- ,!  
* + ,   %!- ,!  

Link Name Enter the name of the hybrid logical link.


Access number Enter the number of the access.
Signaling type Select: Without signaling.
Sig Provider Access No. for Enter the number of the access providing signaling. (identical
Main on both nodes).

3. Confirm your entries

5.2.4 Deleting the Access


An access with a signaling channel that is used by another access cannot be deleted. The
access without signaling must be deleted first, the access providing signaling can then be
deleted.

5.3 Declaring Voice Channels


This type of access uses non-compressed voice channels. For more information on how to
declare this type of channel, see module Hybrid logical links - Configuring non-compressed
voice channels .

(      ! "  * + ,   %!- ,!   5-3
Chapter 5 * + ,   %!- ,!  

5-4 (      ! "  * + ,   %!- ,!  

 

6    

6.1 Overview
This chapter describes the configuration of signaling link over IP.

6.2 Prerequisites
The hybrid logical link must already be declared. See: module Hybrid logical links -
Configuration procedure .

6.3 Basic Principles


The IP signaling channel configuration is performed as follows:
1. Check X25 system parameters
2. Declare the hybrid logical link access with signaling over IP

6.4 Checking X25 System Parameters


1. Select X25 > X25 Systems parameters
2. Review/modify the following attributes:
Max. Number of Rerouting IP Packet This attribute defines the maximum number of
retransmissions of a packet (between 2 and 30)
on a hybrid logical link with IP signaling access
in the event of packet loss
Default value: 15
IP Flow Control Timer This attribute defines the time-out on which the
decision to send again an unacknowledged IP
packet is made (multiple value of 100 ms)
Default value: 10

3. Confirm your entries


Note: When the Call Servers are included in a client IP network, you must:
- Deactivate the dynamic IP routing ("routed" or "gated" process)
- Configure the IP routers correctly

6.5 Declaring the Hybrid Logical Link Access with Signaling over
IP
1. Select Inter-Node Links > Logical Links (ABC-F) > Hybrid Link Access
2. Review/modify the following attributes:

(+   "  '  (  * + , ./   6-1


Chapter 6 * + , ./  

Link Name Enter the name of the hybrid logical link created previously
Access number Enter the number of the hybrid logical link access. This
number must be the same on both nodes (local and remote)
Signaling type Select IP

3. Confirm your entries


The system displays a new screen:
Called Number or main CPUa Enter the IP address of the remote node. The IP address to
IP addr enter depends on the remote node configuration:
• Remote node with one single Call Server: enter the
physical IP address of the Call Server or its main IP
address
• Remote node with duplicated Call Server and the two
Call Servers on the same IP subnetwork: enter the main
IP address used for both Call Servers
• Remote node with duplicated Call Server and the two
Call Servers on different IP subnetworks: enter the main
IP address of the Call 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 Call 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 If the remote node is in a duplicated Call Server
configuration, with the two Call Server on different IP
subnetworks, enter the main IP address of the Call Server
declared in 'b' position.

4. Confirm your entries

6-2 (+   "  '  (  * + , ./  



 

7      

7.1 Overview
An access with D channel signaling uses the D channel of a leased T2 or T1 link to transport
signaling. The D channel is also referred to as the "signaling channel".
An access with D channel signaling usually has non-compressed voice channels located on
the same physical support.
This type of access is incompatible with use of a multiplexer as the multiplexer cannot transmit
on the D channel.

7.2 Declaring the Access

7.2.1 Requirements
The hybrid logical link must already have been created before the access can be created (see,
module Hybrid logical links - Configuration procedure ).

7.2.2 Principle
The signaling support is the D channel of a T1 or T2 link. The link is defined by its physical
position. This configuration requires a service trunk group for the hybrid logical link to operate
correctly.

0(      ! "  * + , ) -   7-1


Chapter 7 * + , ) -  

Figure 7.1: Configuration with D Channel Access

7.2.3 Creating the Access


1. Select Inter-Node Links > Logical Links (ABC-F) > Hybrid Link Access
2. Review/modify the following attributes:
Link Name Enter the name of the hybrid logical link.
Access number Enter the number of the access. This must be the same on
both nodes.
Signaling type Select: D channel.
Main Trunk Group ID Enter a free number for a trunk group. This is automatically
declared by the system.
Phys Access for Main Trunk Enter the physical address of the support in the format:
Group “Shelf” - “Board” - “Digital access”.

3. Confirm your entries

7.3 Declaring Voice Channels


This type of access uses non-compressed voice channels. For more information on how to

7-2 0(      ! "  * + , ) -  


* + , ) -  

declare this type of channel, see module Hybrid logical links - Configuring non-compressed
voice channels .

0(      ! "  * + , ) -   7-3


Chapter 7 * + , ) -  

7-4 0(      ! "  * + , ) -  



 

8      

   

8.1 Overview
An access with switched B channel signaling on a T2 or T1 link is a hybrid logical link that uses
a switched B channel to transport signaling. This type of support is usually charged by call
duration. This type of access has two operating modes:
- The logical link is permanently set up (established). Communication (signaling support) is
set up at system startup.
- The logical link is set up (established) on request. Communication (signaling support) is set
up when the first call request is made on this logical link. Subsequent calls use the same
signaling channel. When the last call has been made, the support is suppressed. This
operating mode is recommended when duration charging is used for the support.

8.2 Declaring the Access

8.2.1 Requirements
The hybrid logical link must already have been created before the access can be created (see,
module Hybrid logical links - Configuration procedure ).

8.2.2 Principle
For the configuration shown below, it is assumed that both nodes have a trunk group for public
network calls.

0      ! "  * + , %! - 1  1 & - 8-1
 
Chapter 8 * + , %! - 1  1 & -  

Figure 8.1: Example Configuration

8.2.3 Creating the Access


1. Select Inter-Node Links > Logical Links (ABC-F) > Hybrid Link Access
2. Review/modify the following attributes:
Link Name Enter the name of the hybrid logical link.
Access number Enter the number of the access. This must be the same on
both nodes.
Signaling type Select: B Channel.
Called Number See note below.

3. Confirm your entries


Note: There are several different cases:
- The logical link is permanent. To avoid any conflicts, calls should only be made in one direction. On
one node, enter the call number of a DID user on the remote node (trunk group seize prefix + DID
number). On the other node: leave this field blank.
- The logical link is set up (established) on request. Either node can call, calls can be made in either
direction. On each node, enter the call number of a DID user on the remote node (trunk group seize
prefix + DID number).
In all cases, the DID number entered here will not be disturbed by the hybrid logical link feature. The

8-2 0      ! "  * + , %! - 1  1 & -
 
* + , %! - 1  1 & -  

system differentiates between DID calls for logical link setup and DID calls for phone calls.

8.3 Declaring Voice Channels


This type of access uses VPN overflow for its voice channels. For more information on how to
declare a VPN overflow, see module VPN overflow - Overview .

0      ! "  * + , %! - 1  1 & - 8-3
 
Chapter 8 * + , %! - 1  1 & -  

8-4 0      ! "  * + , %! - 1  1 & -
 

 

9      

   

9.1 Overview
An access with signaling on the B channel of a leased T2 (or T1) link uses a leased B channel
to transport signaling. The designated B channel cannot be used to transport voice calls.
An access with leased B channel signaling usually has non-compressed voice channels
located in other TSs of the same support.
A multiplexer maybe used on this type of link.

9.2 Declaring the Access

9.2.1 Requirements
The hybrid logical link must already have been created before the access can be created (see,
module Hybrid logical links - Configuration procedure ).

9.2.2 Principle
The hybrid logical link refers to a prefix that gives the position of the TS used.
For it to be useable, the digital access of this support must have been created previously.

2      ! "  * + ,  1  1 & -   9-1
Chapter 9 * + ,  1  1 & -  

Figure 9.1: Example Configuration

9.2.3 Creating the Access


1. Select Inter-Node Links > Logical Links (ABC-F) > Hybrid Link Access
2. Review/modify the following attributes:
Link Name Enter the name of the hybrid logical link.
Access number Enter the number of the access. This must be the same on
both nodes.
Signaling type Select: B Channel.
Called Number Enter the number of the Hybrid TG Address prefix.

3. Confirm your entries

9.2.4 Declaring the Hybrid Trunk Group Address Prefix


1. Select Translator > Prefix Plan
2. Review/modify the following attributes:

9-2 2      ! "  * + ,  1  1 & -  
* + ,  1  1 & -  

Number Enter prefix number. This number must be compatible with


the dialing plan.
Prefix Meaning Select: Hybrid TG Address.
Hybrid TG ACT No. Enter shelf address.
Hybrid TG Board No. Enter board address.
Hybrid TG Trunk No. Enter the number of the T2 access.
See "Caution" below.
Hybrid TG Access (T0/T2) Enter the number of the TS (trunk).
No. See "Caution" below.

3. Confirm your entries


Caution: For T2, unlike PCM, item names do not correspond to the configuration requested.
Therefore, access must be specified in the parameter Hybrid TG Trunk No., and the trunk in the
parameter Hybrid TG Access (T0/T2) No..

Note: If a multiplexer is used, the TS numbers on the two nodes are different. The multiplexer
configuration gives the matching TS numbers. For more information on multiplexer operation, see module
Hybrid logical links - Detailed description § Backup Signaling .

9.2.5 Creating the Digital Access of the Support


This type of access requires the digital access of the support to be created. For more
information on this topic, see module Hybrid logical links - Configuration procedure § Declaring
the Hybrid Logical Link Access .

9.3 Declaring Voice Channels


This type of access uses non-compressed voice channels. For more information on how to
declare this type of channel, see module Hybrid logical links - Configuring non-compressed
voice channels .

2      ! "  * + ,  1  1 & -   9-3
Chapter 9 * + ,  1  1 & -  

9-4 2      ! "  * + ,  1  1 & -  

 

10    

   

10.1 Overview
An access with signaling on a PCM B channel uses a B channel of a PCM to transport
signaling.
A PCM link is a link with 30 B channels and no D channel. A PCM link is also referred to as a
“channel by channel" link.
An access with PCM B channel signaling usually has voice channels on the same PCM.

10.2 Declaring the Access

10.2.1 Requirements
The hybrid logical link must already have been created before the access can be created (see,
module Hybrid logical links - Configuration procedure ).

10.2.2 Principle
The hybrid logical link refers to a prefix that gives the position of the TS used.

22      ! "  * + ,  /*3 & -   10-1
Chapter 10 * + ,  /*3 & -  

Figure 10.1: Configuration with PCM B Channel Signaling

10.2.3 Creating the Access


Declaring the hybrid link access:
1. Select Inter-Node Links > Logical Links (ABC-F) > Hybrid Link Access
2. Review/modify the following attributes:
Link Name Enter the name of the hybrid logical link.
Access number Enter the number of the access. This must be the same on
both nodes.
Signaling type Select: B Channel.
Called Number Enter the number of the “Hybrid TG Address” prefix.

3. Confirm your entries


This must be declared on each node. It specifies the hybrid access to be used on the B
channel.
1. Select Translator > Prefix Plan
2. Review/modify the following attributes:

10-2 22      ! "  * + ,  /*3 & -  
* + ,  /*3 & -  

Number Enter prefix number. This number must be compatible with


the dialing plan.
Prefix Meaning Select: Hybrid TG Address.
Hybrid TG ACT No. Enter shelf address.
Hybrid TG Board No. Enter board address.
Hybrid TG Trunk No. Enter the number of the TS (trunk) used.
See note below.
Hybrid TG Access (T0/T2) No. Enter '0' (the PCM board only has one access).
See note below.

3. Confirm your entries


Note: Unlike the B channel of a leased T2 link, item name corresponds to the configuration requested. In
the parameter Hybrid TG Trunk No., enter the number of the trunk, and, in the parameter Hybrid TG
Access (T0/T2) No., enter 0 (access number).

10.3 Declaring Voice Channels


This type of access uses non-compressed voice channels. For more information on how to
declare this type of channel, see module Hybrid logical links - Configuring non-compressed
voice channels .

22      ! "  * + ,  /*3 & -   10-3
Chapter 10 * + ,  /*3 & -  

10-4 22      ! "  * + ,  /*3 & -  

 

11  !  "


"  

11.1 Overview
An access with synchronous modem signaling uses a leased line between the two modems.
B channel signaling via TA/synchronous modem requires an IO2, IO2N or OBCA board.

Figure 11.1: Signaling via TA/Synchronous Modem


Transfer speed is imposed by the modem that provides the clock signal to the TA.
The voice channels for this type of access are located on another support. VPN overflow may
be used.

11.2 Declaring the Access

11.2.1 Requirements
The hybrid logical link must already have been created before the access can be created (see,
module Hybrid logical links - Configuration procedure ).

11.2.2 Principle
The following operations must be performed on each node to create an access with modem
signaling:
- Create a TA.
- Create a hybrid link access referring to this TA.

11.2.3 Create the Local TA


1. Select DATA > Data Terminal

2       ! "  * + ,  -  ,     11-1
Chapter 11 * + ,  -  ,    

2. Review/modify the following attributes:


Directory Number Enter TA call number.
Shelf Address Enter shelf number.
Board Address Enter board number.
Equipment Address Enter the number of the equipment to which the TA is
connected.
Domain Identifier Leave the default value.
Specialization Select: Hybrid.
Selecting this option sets the other parameters to their
default values.
Language ID Not used.
Secret Code: Not used.
Confirm Not used.
Public Network COS Not used.
Charging COS Not used.
Connection COS ID Not used.
Call Restriction COS Not used.
Cost Center ID Not used.
B Channel: 2 Not used.
Data Group Dir. No: Not used, leave this field blank.
ISDN Teleservice Select: Non-standard Application.
Adapter type Select: V110 + V120 Synchronous.
Terminal Type Select: VT100.
Use Select: Set.
Setup ID Leave the default value: 49.
Flow Control ID Leave the default value: 15.
Output Config. ID Leave the default value: 0.
Input Config. ID Leave the default value: 0.
V120 No. Leave the default value: 15.
Associated DATA station Leave the default value.
V24 configuration Leave the default value.
Semi-permanent Leave the default value.
Adaptation protocol Select: Transparent HDLC.
Synchronous Select: Synchronous.
Cost Center Name Leave the default value.
Incidents Teleservice Leave the default value.
Caller COS Leave the default value.

3. Confirm your entries

11-2 2       ! "  * + ,  -  ,    
* + ,  -  ,    

11.2.4 Creating the Access


1. Select Inter-Node Links > Logical Links (ABC-F) > Hybrid Link Access
2. Review/modify the following attributes:
Link Name Enter the name of the hybrid logical link.
Access number Enter the number of the access. This must be the same on
both nodes.
Signaling type Select: B Channel.
Called Number Enter the number of the local TA. This must already have
been declared.

3. Confirm your entries


The remote node must be declared in the same way.

11.2.5 Deleting the Access


The hybrid link access must be deleted before the TA can be deleted.

11.3 Declaring Voice Channels


This type of access uses VPN overflow for its voice channels. For more information on how to
declare a VPN overflow, see module VPN overflow - Overview .

2       ! "  * + ,  -  ,     11-3
Chapter 11 * + ,  -  ,    

11-4 2       ! "  * + ,  -  ,    

 

12       


 

12.1 Overview
A "Leased virtual voice access" is a hybrid link access that uses the signaling channel of a
compressed link. The compressed link is supported by the TS of a leased T2 link. This TS
supports the signaling channel and six compressed voice channels.
Backup signaling cannot be used with this type of access. On this type of link, if signaling is
lost, the associated voice channels are also lost.
A multiplexer that compresses the B channel supporting the "leased virtual voice access" must
not be used. The channel must be transparent.

12.2 Declaring the Access

12.2.1 Requirements
The hybrid logical link must already have been created before the access can be created (see,
module Hybrid logical links - Configuration procedure ).

12.2.2 Principle
The hybrid access refers to:
- A service trunk group. This is automatically created by the system.
- The position of the virtual access on a compression board.
- The position of the support TS.
The digital access must have been created to enable level 2 of the support.
The support B channel must not be created in a trunk group. The TS must be free.

      ! "  * + ,  $!, $     12-1
Chapter 12 * + ,  $!, $    

Figure 12.1: Configuration with "Leased virtual voice" Signaling

12.2.3 Creating the Access


Declaring the hybrid link access:
Declaring the access:
1. Select Inter-Node Links > Logical Links (ABC-F) > Hybrid Link Access
2. Review/modify the following attributes:
Link Name Enter the name of the hybrid logical link.
Access number Enter the number of the access. This must be the same on
both nodes.
Signaling type Select: Virtual-Voice-Leased.
Main Trunk Group ID Enter a free number for the service trunk group.
The service trunk group is created automatically.
Phys Access for Main Trunk Enter the number of the virtual access used on the
Group compression board (format: ACT number-Board
number-Equipment number),

12-2       ! "  * + ,  $!, $    
* + ,  $!, $    

Support Time Slot address Enter the number of the physical support TS in the format:
“Shelf number” - ”Board number” - ”Equipment number” - ”TS
number".
For TS number, see the note below.

3. Confirm your entries


Note: If a multiplexer is used, the TS numbers on the two nodes are different. Multiplexer configuration
gives the matching TS numbers. For more information on multiplexer operation, see module Hybrid
logical links - Detailed description § Backup Signaling .

12.2.4 Creating the Digital Access of the Support


This type of access requires the digital access of the support to be created. For more
information on this topic, see module Hybrid logical links - Configuration procedure § Declaring
the Hybrid Logical Link Access .

12.3 Declaring Voice Channels


This type of access uses compressed voice channels. For more information on how to declare
this type of channel, see module Hybrid logical links - Configuring compressed voice channels
.

      ! "  * + ,  $!, $     12-3
Chapter 12 * + ,  $!, $    

12-4       ! "  * + ,  $!, $    

 

13     


   

13.1 Overview
A "Switched virtual voice access" is a hybrid link access that uses a TS to the remote node
that is set up on request. This TS supports the signaling channel and six compressed voice
channels.
Backup signaling cannot be used with this type of access. On this type of link, if signaling is
lost, the associated voice channels are also lost.

13.2 Declaring the Access

13.2.1 Requirements
The hybrid logical link must already have been created before the access can be created (see,
module Hybrid logical links - Configuration procedure ).

13.2.2 Principle
For the configuration shown below, it is assumed that both nodes have a trunk group for public
network calls.

      ! "  * + , %! - $!, $     13-1
Chapter 13 * + , %! - $!, $    

Figure 13.1: Configuration with "Switched virtual voice" Signaling

13.2.3 Creating the Access


This declaration must be the same on both nodes.
1. Select Inter-Node Links > Logical Links (ABC-F) > Hybrid Link Access
2. Review/modify the following attributes:
Link Name Enter the name of the hybrid logical link.
Access number Enter the number of the access. This must be the same on
both nodes.
Signaling type Select: Virtual-Voice-Switched.
Called Number See note below.
Main Trunk Group ID Enter a free number for the service trunk group.
The service trunk group is created automatically.
Phys Access for Main Trunk Enter the address of a free virtual access on the
Group compression board. This address is expressed in the format:
“Shelf number” - ”Board number” - ”Virtual access number”

3. Confirm your entries


Note: There are several different cases:
- The logical link is permanent. On one node, enter the call number of any DID user on the remote
node (trunk group seize prefix + DID number). On the other node, leave this field blank.
- The logical link is set up (established) on request. On each node, enter the call number of a DID user
on the remote node (trunk group seize prefix + DID number).
In all cases, the DID number entered here will not be disturbed by the hybrid logical link feature.

13.3 Declaring Voice Channels


This type of access uses compressed voice channels. For more information on how to declare
this type of channel, see module Hybrid logical links - Configuring compressed voice channels
.

13-2       ! "  * + , %! - $!, $    

 

14      #


   

14.1 Overview
A "Transfix virtual access" is a hybrid link access that uses a leased Transfix link. This link
supports the signaling channel and six compressed voice channels.
It is not necessary to configure backup signaling for virtual accesses. On this type of link, if
signaling is lost, the associated voice channels are also lost.

14.2 Declaring the Access

14.2.1 Requirements
The hybrid logical link must already have been created before the access can be created (see,
module Hybrid logical links - Configuration procedure ).

14.2.2 Principle
The hybrid access refers to:
- A service trunk group. This is automatically created by the system.
- The position of the Transfix support.

+      ! "  * + , $!, 1+    14-1
Chapter 14 * + , $!, 1+   

Figure 14.1: Configuration with "Virtual Transfix" Signaling

14.2.3 Modifying the Transfix Access


Modification is the same on both nodes.
1. Select Shelf > Board > Transfix Access
2. Review/modify the following attributes:
Shelf Address Enter shelf number.
Board Address Enter the number of the LIOB interface board.
T0/T2 Access No. Enter the number of the digital access: '4' (mandatory for a
Transfix access).
Access Type Access type display: always Transfix in this case.
Network Mode Select: Network Node on both sides.
Access ID Leave this field blank.

14-2 +      ! "  * + , $!, 1+   
* + , $!, 1+   

Function Select:
• X24_V11 according to the connection used.
• V36 according to the connection used.
Access Rate Select: 64K or 128K depending on the Transfix link.
Maximum Information Field Leave the default value: 1600.
Size
Support Type Select: Leased.

3. Confirm your entries

14.2.4 Creating the Access


Declaration is the same on both nodes.
1. Select Inter-Node Links > Logical Links (ABC-F) > Hybrid Link Access
2. Review/modify the following attributes:
Link Name Enter the name of the hybrid logical link.
Access number Enter access number. This must be the same on both nodes.
Signaling type Select: Virtual-Transfix-Leased.
Main Trunk Group ID Enter a free number for a trunk group.
The service trunk group is created automatically.
Phys Access for Main Trunk Enter the address of the access (on the LIOB board) in the
Group format:
“Shelf number” - ”Board number” - ”8”
The value "8" is mandatory.

3. Confirm your entries

14.3 Declaring Voice Channels


This type of access uses compressed voice channels. For more information on how to declare
this type of channel, see module Hybrid logical links - Configuring compressed voice channels
.

+      ! "  * + , $!, 1+    14-3
Chapter 14 * + , $!, 1+   

14-4 +      ! "  * + , $!, 1+   

 

15     "  !


 

15.1 Overview
A “Virtual Frame Relay access” is a hybrid link access that uses a Frame Relay network as
support. The Frame Relay link supports the signaling channel and six compressed voice
channels.
It is not necessary to configure backup signaling for virtual accesses. On this type of link, if
signaling is lost, the associated voice channels are also lost.

15.2 Declaring the Access

15.2.1 Requirements
The hybrid logical link must already have been created before the access can be created (see,
module Hybrid logical links - Configuration procedure ).

15.2.2 Principle
The hybrid access refers to:
- A service trunk group. This is automatically created by the system.
- The position of the virtual access on a compression board.
- The position of the support TS.
- The DLCI allowing the remote node to be reached.

(      ! "  * + , $!, +    15-1
Chapter 15 * + , $!, +   

Figure 15.1: Configuration with “Virtual Frame Relay” Signaling

15.2.3 Modifying the Transfix Access


1. Select Shelf > Board > Transfix Access
2. Review/modify the following attributes:
Shelf Address Enter shelf number.
Board Address Enter the number of the LIOB interface board.
T0/T2 Access No. Enter the number of the digital access: '4' (mandatory for a
Frame Relay access).
Access Type Access type display: always Transfix in this case.
Network Mode Select: Network Node on both sides.
Access ID Leave this field blank.

15-2 (      ! "  * + , $!, +   
* + , $!, +   

Function Select:
• X24_V11 according to the connection used.
• V36 according to the connection used.
Access Rate Irrelevant; rate is set by the modem clock.
Maximum Information Field Leave the default value: 1600.
Size
Support Type Select: Network (mandatory).

3. Confirm your entries

15.2.4 Creating the Access


Declaring the access:
1. Select Inter-Node Links > Logical Links (ABC-F) > Hybrid Link Access
2. Review/modify the following attributes:
Link Name Enter the name of the hybrid logical link.
Access number Enter access number. This must be the same on both nodes.
Signaling type Select: Frame Relay.
Main Trunk Group ID Enter a free number for a trunk group.
The service trunk group is created automatically.
Phys Access for Main Trunk Enter the address of the compression access (LIOB board)
Group in the format:
“Shelf number” - ”Board number” - ”8”
8 : mandatory
DLCI Enter the value provided by the carrier.
Committed Information Rate Enter the value provided by the carrier.
Extended Information Rate Enter the value provided by the carrier.
EIR: maximum rate supported. This must be equal to or
more than CIR.
CIR Measurement Interval Enter the value provided by the carrier.

3. Confirm your entries

15.3 Declaring Voice Channels


This type of access uses compressed voice channels. For more information on how to declare
this type of channel, see module Hybrid logical links - Configuring compressed voice channels
.

(      ! "  * + , $!, +    15-3
Chapter 15 * + , $!, +   

15-4 (      ! "  * + , $!, +   

 

16   " 


   

16.1 Principle
Voice channels may use the following physical supports:
- Digital support: The B channel of a T0, T1, T2 or PCM link.
- Analog support: A tie line link.

16.2 Declaring the Access

16.2.1 Requirements
The hybrid logical link (and associated signaling) must already have been created before the
access can be created (see, module Hybrid logical links - Configuration procedure ).

16.2.2 Principle
A voice channel is identified by:
- “Hybrid link access”: this indicates to which access it belongs and with which signaling it is
associated.
- “Hybrid link TS”: indicates the position of the voice channel in this access.
The Call Servers on both nodes use the “Hybrid link access” and “Hybrid link TS” pair to
designate a voice channel.
For correct operation, each voice channel must be connected to two trunks (one on each side)
corresponding to the same physical support (see following figure):

Figure 16.1: Hybrid Link TS and Trunk


TS 0 and TS 16 cannot be used as voice channels.
The position of a trunk is defined by:

+      ! "  * + ,     $   - 16-1


Chapter 16 * + ,     $   -

- Its shelf, its board, and its equipment as defined by wiring.


- Its TS number (for digital supports only). There are two possible cases:
• No multiplexer: TS number is the same at both ends.
• Multiplexer used: the number of the end TSs is defined by multiplexer configuration.
The following figure shows an example of use with and without a multiplexer.

Figure 16.2: Example of Hybrid Link TS Configuration


The following table shows the correspondence between the hybrid link TS and the trunk for the
above example.
table 16.1: Correspondence between TSs with and without a Multiplexer
Access Hybrid link TS N1 N2
Trunk Trunk
1 1 0–1–0–1 0–3–0–1
1 2 0–1–0–2 0–3–0–2
... ... ... ...
1 30 0–1–0–30 0–3–0–30
________ __________ _________ _________
2 1 0–2–0–1 0–5–0–11
2 2 0–2–0–2 0–5–0–12
2 3 0–2–0–3 0–5–0–13

16.2.3 Creating a Hybrid Link Trunk


To declare a voice channel you must declare a Hybrid Link Trunk on each end node of the
link.

16-2 +      ! "  * + ,     $   -


* + ,     $   -

1. Select Inter-Node Links > Logical Links (ABC-F) > Hybrid Link Access > Hybrid Link
Trunk
2. Review/modify the following attributes:
Link Name Enter the name of the hybrid logical link.
Access number Enter access number (must be identical for both nodes).
Physical Address Enter the physical address of the equipment. This address
must correspond to the same voice channel on both nodes.
Physical address is expressed in the format:
• Digital support: “Shelf number” - ”Board number” -
”Physical access number” - ”TS number”.
• Analog support: “Shelf number” - ”Board number” -
”Physical access number”.
TS number Enter the number of the hybrid link TS (must be identical for
both nodes).
Directory Name Enter a trunk name (optional).
Trunk Routing Number (not used).
Trunk Number (not used).
Data Transparency True: for digital supports.
False: for analog supports.
Trunk COS ID 18 for T2, T1, T0 trunk groups.
Real Trunk COS ID This attribute applies to analog trunks only. It it he number of
the real COS. It will be used instead of trunk COS (the
preceding attribute) after reset.
7 for LIA (2 wire) trunk groups (EMTL, ACEM).
15 for LIA (4 wire) trunk groups (EMTL, ACEM).

3. Confirm your entries


Note: For digital supports, the digital access must already have been created (see module Hybrid logical
links - Configuration procedure § Declaring the Hybrid Logical Link Access ).

+      ! "  * + ,     $   - 16-3


Chapter 16 * + ,     $   -

16-4 +      ! "  * + ,     $   -



 

17  "   


 

17.1 Overview
When "virtual" signaling is used, six associated compressed voice channels are always used.
These compressed channels can be created in one operation.

17.2 Declaring Voice Channels

17.2.1 Requirements
The hybrid logical link (and associated signaling) must already have been created before the
access can be created (see, module Hybrid logical links - Configuration procedure ).

17.2.2 Creating Compressed Voice Channels


1. Select Inter-Node Links > Logical Links (ABC-F) > Hybrid Link Access >
Create/Delete global trunk
2. Review/modify the following attributes:
Link Name Enter the name of the hybrid logical link.
Access number Enter the number of the virtual hybrid link access (must be
identical for both nodes).
ACTION/INFORMATION
Operation on Trunks Select:
• Create global for SigD/Comp: to create the six trunks.
• Delete global for SigD/Comp: to delete the six trunks.
Note: The service trunk group is created automatically.
Trunk COS Leave the default value: 18.
Real Trunk COS Leave the default value: 18.
List of Time Slots to create Select the position of the six trunks.
01111110000000000000000000000000
(0+6 x 1+25 x 0)

3. Confirm your entries

      ! "  * + ,   $   - 17-1


Chapter 17 * + ,   $   -

17-2       ! "  * + ,   $   -



 

18  !$   %

18.1 Overview
The local hybrid logical link is a "workaround" solution used for the OmniTouch Call Center. It
is used because a Call Center can only handle external calls. Local calls to the Call Center are
not allowed.
The hybrid logical link is used to convert a local call into a remote call. The local hybrid logical
link is a "workaround "solution. No physical equipment is required.
Use :
A local user who wants to reach the local Call Center dials:
The routing prefix of the hybrid logical link + the number of the Call Center.
The routing prefix is used to direct the call to the local logical link.
The routing list deletes the prefix and the call is presented to the Call Center as an external
call.

18.2 Declaring the Local Hybrid Logical Link

18.2.1 Principle
To create a local hybrid logical link:
- Declare the hybrid logical link.
- Declare as many accesses as required.
- Declare a routing prefix for use of this logical link.
- Declare a routing list.

18.2.2 Creating the Local Hybrid Logical Link


Creating the local hybrid logical link and its accesses.
- Select Inter-Node Links > Logical Links (ABC-F)
- Review/modify the following attributes:
Link Name Enter the name of the logical link.
Link Type Select Hybrid.
Adjacent Node Enter the number of the local node.
Adjacent Network Enter an unused subnetwork number.
Multi access hybrid link Select: YES.

- Confirm your entries


Leave the other settings at the default values.

      ! "  * + , -    18-1


Chapter 18 * + , -   

18.2.3 Creating the Hybrid Logical Link Access


The accesses for this hybrid link must now be declared. At leas two accesses per link are
required (one for the outgoing access, the other for the incoming access). Each pair of
accesses can support up to 30 calls. It may be necessary to create additional pairs of
accesses for increased capacity.
1. Select Inter-Node Links > Logical Links (ABC-F) > Hybrid Link Access
2. Review/modify the following attributes:
Link Name Enter the name of the hybrid logical link.
Access number Enter access number.
Signaling type Select: B Channel.
Called Number Leave this field blank.

3. Confirm your entries


Leave the other settings at the default values.

18.2.4 Creating the Access Prefix


1. Select Translator > Prefix Plan
2. Review/modify the following attributes:
Number Enter prefix number.
This number must be compatible with the dialing plan.
Prefix Meaning Select: Routing No..
Signaling type Select: B Channel.
Network Number Enter the number of the Adjacent Network specified for the
local hybrid link.
Node Number/ABC-F Trunk Enter the number of the local hybrid link (see note, below).
Group
Number of Digits Enter the number of digits to send.
Prefix + Call Center call number.

3. Confirm your entries


Leave the other settings at the default values.
Note:
To obtain the number of the hybrid link, run the 
command followed by local node
number. The following information is displayed:
Example:

18-2       ! "  * + , -   


* + , -   

          


!""""!"""""""""""""""""""""""""""""""""!"""""""""""""""""""""""""!"""""!
#  $ %&& 
!""""!"""""""""""""""""""""""""""""""""!"""""""""""""""""""""""""!"""""!
' ' % (%(
  ' ) (%(
  '  '
'  ' * )%   )
  ' * )% )
  '   '
!""""!"""""""""""""""""""""""""""""""""!""""""""""""""""""""""+""!"""""!
'  ' , - . .  / 0% ' '  '
'  ' , - . .  / 0% ' '  '
!""""!"""""""""""""""""""""""""""""""""!"""""""""""""""""""""""""!"""""!

The first line gives link number (2001) for the local node requested (2).
Remark: This information is also available using the 
command, followed by the "all" option.

18.2.5 Creating the Network Routing List/Table


1. Select Translator > Network Routing Table
2. Review/modify the following attributes:
Network Number Enter the name of the logical link.
Rank of First Digit to be Sent Enter the rank of the first digit to be sent. This parameter is
used to delete the routing prefix.
If the prefix is on two digits, enter '3'.
Protocol Type Select: ABC-F.
Multi access hybrid link Select: YES.

3. Confirm your entries

      ! "  * + , -    18-3


Chapter 18 * + , -   

18-4       ! "  * + , -   



 

19   

19.1 Resetting a Hybrid Logical Link


The  command is used to reset a hybrid logical link. This cannot be done with the
“rstcpl" command since the coupler is a dummy coupler.
Syntax:
 num-node [ num-access] type
where:
- num-node: number of the node to which the hybrid logical link is declared.
- num-access: access number.
- type: can take the following values: main, stdby and kill.
If the type is main, only the main signaling is reset.
If the type is stdby, only the standby (backup) signaling is reset.
If the type is kill, the entire access is reset (main signaling, standby signaling and trunks are
reset).
Examples of use:
Reset all hybrid logical links of a node:
1&2334   %
 ( % %&&  5%   
  2% ( $   %&& .  67899

Reset executed by default:


1&2334 
  %&&  %&&
- %( :  ;  %  4 ;%&& 
2 4 ;4
7 2% ""4  $  2% (%(
7   ""4  $  %  (%(
7  ""4 ( &%(
,
  % %&& 
- %( :  ;  %  4 %

19.2 Trunk Supervision


A supervision mechanism for the trunks used as voice channels on the hybrid logical links is
used to detect any disappearance or anomaly which may occur during operation (for example:
unplugged boards or cables).
For each trunk, the supervision mechanism consists in sending a Q23 signal at one end of the
link and detecting this signal at the other end.
Where appropriate, an incident message is sent to signal the occurrence of a problem on a
trunk:

"+   "  '  (  3!  19-1


Chapter 19 3! 

- Incident 5068 signals the problem.


- Incident 4109 indicates a return to normal.
Supervision is run automatically as soon as the logical link is declared. A system parameter is
used to halt supervision.
1. Select System > Other System Param
2. Review/modify the following attribute:
Stop Tie Line Supervision True.

3. Confirm your entry


To stop the supervision:
1. Set the Stop Tie Line Supervision parameter to True on each terminal node of the hybrid
logical link.
2. Reset the hybrid logical link using the  command.

19.3 Hybrid Access Display


To display a hybrid access at a given moment and to check its declaration, use the command:

.

%: displays the logical links.

 +<<: displays the accesses of a selected link.

  "<<: displays the accesses of the node concerned.

 +<< %&& "8=%: detailed description of the access of
a selected link.

  "<< %&& "8=%: detailed description of the access of a
selected node.
Example of use of the 
% command:
&&  $      
""""""""""""""""""""""""""""""""
)- % : 0 >? , >
% (%(
  : @A
/ &% % 
 ( 
 . &% 
2 : 18
#% 8 % : 0 >? @
6 %2 %2 899
6 %2 18B 0,0 
   . .  % 
> & 
 &
C& 
!"""""!"""""""!"""""!""""""!"""""""!"""""""!""""""""""""!"""""!""""""!"""""!
'  ' 6 '  ' && '  % ' 6D ' %  ' &% '  ' * '
!"""""!"""""""!"""""!""""""!"""""""!"""""""!""""""""""""!"""""!""""""!"""""!
'  ' 189 ' >) ' E ' %% ' 39 ' 1"3"" ' F '  ' 1 '
'  ' 18F ' >) ' E ' %% ' 3F ' 1"B"" ' F '  ' 1 '
!"""""!"""""""!"""""!""""""!"""""""!"""""""!""""""""""""!"""""!""""""!"""""!

In the above case, the fields correspond to the following:


-  : representative position of logical link trunk.

19-2 "+   "  '  (  3! 


3! 

- 6: hybrid logical link equipment/device number.


- : >) for In Service, or ,,) for Out Of Service.
- &&: E for free, @ for outgoing, and  for incoming call.
-  % : type of call that can be carried on the logical link (data or voice).
- 6D : real equipment number.
- %  : real equipment position.
- &%: equipment trunk category.
- : type of board supporting the real equipment.
- *: number of the Trunk Group containing the real equipment.

19.4 Traces on the Hybrid Link


It is possible to obtain telephone traces using the 2 %& "% tool as for a normal link. To do
this, you must set the 
   attribute to .
You need only activate  & with “ACT number - coupler (board) number - access number" to
filter the traces.

19.5 Malfunctions

19.5.1 The Hybrid Logical Link is not Established


19.5.1.1 For all Types of Signaling Support
For releases lower than R6.1, the X25 access point number 1, located behind access point
group number 510, must be operational and have X25 profile number 73.
For R6.1 or higher:
- For hybrid logical links with signaling over IP, the X25 access point number 3, located
behind access point group number 510, must be operational and have X25 profile number
80.
- For other hybrid logical links, the X25 access point number 1, located behind access point
group number 510, must be operational and have X25 profile number 73.
Note: Normally, this access point group 510 and these access points are created correctly by default in
MAO.

19.5.1.2 The Signaling Support is an X25 Virtual Circuit


- See whether X25 incidents occur.
- Check the X25 addresses of access points 183 and the management of these X25
addresses in the translator. Check that the X25 access points 183 are operational.
- Check the packet sizes of the X25 profiles. The packet size of the X25 profile of the hybrid
logical link must be smaller than the packet size of the X25 profile of the physical support
of the hybrid logical link.
- In the case where an X25 packet public network is used, check that the physical support is

"+   "  '  (  3!  19-3


Chapter 19 3! 

declared. The X25 parameters declared for this physical support must be exactly the same
as those in the subscription with the public packet network (check the packet and window
sizes, X25 facilities, throughputs, number of logical channels).
19.5.1.3 The Signaling Support is a Connection via IP
- Check that each node can reach all the other nodes via an IP connection using the (
command with the IP addresses declared in the hybrid access. Check the number of
packets lost and the transmission times reported by the (.
Example: to send 100 packets of 1000 bytes
ping 155.132.32.44 1000 100
The result is:
""""""33G1G1G88 >* )% & """"""
 %&  % 2 .  %& & . H %& 

 "  2  2=%(=2%I 7 ==3

- Use IP addressing by role if the Call Servers are duplicated.


- Check that the X25 access points 183 are operational.
- Check that two Call Servers do not have the same IP number in the network. This can
happen in particular when addressing by role is used and the redundant Call Server is
suddenly changed to another cabinet. If this Call Server is started up in this new cabinet,
then it will have the same IP number as the main Call Server.
- See whether incident 2847 occurs. If yes, there is a configuration problem on the IP
addresses
- Check the values of the X25 system parameters used for the hybrid logical links. The
default values are:
• Maximum number IP packet re-routing: 15.
• IP flow control timeout: 10.

19.5.2 The Hybrid Logical Link is Established but there is no Communication


- Check the number of trunks on each node.
- Check that the same number of trunks is declared on each node by consulting the  
(&%  
 object. Check that each trunk uses the same position on the two
nodes. For each trunk, the ) 
2 attribute must be the same on each node.
- Check the data of the hybrid logical link.
- Using the  
tool, check that:
• The number of trunks created is correct (it must correspond to that declared in MAO.)
• The trunks are free:
The trunks are in #>/ state and that the && $ 7 
• Quality of the trunks.
- Check that the quality of the trunks is correct (transparency) and that the
D  2 field is correct.

19-4 "+   "  '  (  3! 

You might also like