Alcatel Omnipcx Enterprise: Voice Compression

Download as pdf or txt
Download as pdf or txt
You are on page 1of 92

Alcatel OmniPCX Enterprise

Voice Compression
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

 Description of the service ................................................................... 1.1


 Definitions ................................................................................................. 1.1
 Restrictions .............................................................................................. 1.2
 Reference to related modules ............................................................ 1.2

Chapter 2
Detailed description

 General principle .................................................................................... 2.1


 Hardware resources .............................................................................. 2.3
 Voice compression ................................................................................ 2.4
 Setting up a compressed channel ................................................... 2.4
 Mutual aid .................................................................................................. 2.4

DATA communication .......................................................................... 2.5
 Applications using T0 or T2 B-Channels as support ................ 2.5
  Logical links on leased B-channels ........................................................... 2.5
  Compressed logical links through the public network ............................ 2.6
  Compressed trunk groups through the public network .......................... 2.7
 Compression and hybrid logical links ............................................ 2.9
 Applications using an analog signalling trunk ............................ 2.9

 
  0-1
 
 

 Applications using Transfix as support ........................................ 2.10


 Interactions .............................................................................................. 2.10
 ARS and compressed trunk groups ......................................................... 2.10
 Metering and compressed links ................................................................ 2.10
 Limits and constraints ......................................................................... 2.11

Chapter 3
Installation procedure

 Transmission on T0 ............................................................................... 3.1


 Transmission on T1 ............................................................................... 3.1
 Transmission on T2 ............................................................................... 3.2
 Transmission on Transfix ................................................................... 3.3
 Additional compressors ...................................................................... 3.3

Chapter 4
Configuration procedure

 Management principle .......................................................................... 4.1


 Objects used by compression ........................................................... 4.1
 Board ............................................................................................................ 4.1
 Transfix access ............................................................................................ 4.1
 Compressed trunk declaration ................................................................... 4.2
 T0/T1/T2 access ........................................................................................... 4.3
 Logical links ................................................................................................. 4.5

Link bus access ........................................................................................... 4.6
 Hybrid Link Access ..................................................................................... 4.7
 Virtual access .............................................................................................. 4.8
 Reference to other modules .............................................................. 4.10

0-2  
 
 
 

Chapter 5
Configuring a trunk group on a leased B channel

 Principle ..................................................................................................... 5.1


 Relationships between objects ......................................................... 5.1
 Rules to observe when creating a compressed trunk .............. 5.2
 Management example ........................................................................... 5.2

Chapter 6
Configuring a trunk group on a public network B channel

 Principle ..................................................................................................... 6.1

 Relationships between objects ......................................................... 6.1

 Rules to be observed ............................................................................ 6.2

 Example of management ..................................................................... 6.3

Chapter 7
Configuring a trunk group on an analog signaling support

 Principle ..................................................................................................... 7.1


 Relationships between objects ......................................................... 7.1
 Rules to be observed ............................................................................ 7.2

Chapter 8
Configuring a logical link on a B channel

 
  0-3
 
 

 Principle ..................................................................................................... 8.1


 Relationships between objects ......................................................... 8.1
 Rules to observe ..................................................................................... 8.2
 Management example ........................................................................... 8.2

Chapter 9
Configuring a logical link on a public network B channel

 Principle ..................................................................................................... 9.1


 Relationships between objects ......................................................... 9.1
 Rules to observe ..................................................................................... 9.2
 management example .......................................................................... 9.3

Chapter 10
Configuring a hybrid logical link on a leased B channel

 Principle .................................................................................................... 10.1


 Relationships between objects ........................................................ 10.1
 Rules to be observed: ......................................................................... 10.2
 Backup signalling ................................................................................. 10.2
 Example of management .................................................................... 10.3

Chapter 11
Configuring a trunk group and logical link on Transfix

 Principle .................................................................................................... 11.1


 Relationships between objects ........................................................ 11.1

0-4  
 
 
 

 Rules to observe .................................................................................... 11.1

Chapter 12
Configuration examples

 Reference to related modules ........................................................... 12.1

Chapter 13
Trunk group on leased B channel example

 Introduction ............................................................................................. 13.1


 Declaring the support trunk group ................................................. 13.1
 Declaring PRA (support) boards and derivatives .................................... 13.1
 Support trunk group and derivatives ....................................................... 13.2
 Declaring compressed trunk groups ............................................. 13.4
 Declaring LIOx compression boards ........................................................ 13.4
 Declaring the virtual access ...................................................................... 13.4
 Declaring the compressed trunk groups and their derivatives ............. 13.5
 Declaring the support trunk group seizure prefix ..................... 13.7

Chapter 14
Trunk group on B channel on public network example

 Introduction ............................................................................................. 14.1


 Declaring support trunk groups to the public network: .......... 14.1
 Declaring PRA boards (suuport) and derivatives .................................... 14.1
 Declaring support trunk groups and derivatives .................................... 14.2
 Declaring compressed trunk groups ............................................. 14.4

 
  0-5
 
 

 Declaring LIOX compression board ......................................................... 14.4


 Declaring the virtual access ...................................................................... 14.4
 Declaring compressed trunk groups and derivatives ............................. 14.4
 Declaring support trunk group seize prefixes ............................ 14.6
 ARS declaration ..................................................................................... 14.7

Chapter 15
Logical link on leased B channel example

  Introduction ............................................................................................. 15.1


  Declaring the physical support ........................................................ 15.1
  Declaring the compressed logical link .......................................... 15.2
  Declaring the LIOX board .......................................................................... 15.2
  Declaring the virtual access ...................................................................... 15.2
  Declaring the logical link ........................................................................... 15.2
  Declaring the logical link access .............................................................. 15.3

Chapter 16
Logical link on B channel on public network example


 Introduction ............................................................................................. 16.1

 Declaration of access trunk groups to the public network .... 16.1

 Declaration of the compressed logical link ................................. 16.1

 Declaration of the LIOX board ................................................................... 16.1

 Declaration of virtual access ..................................................................... 16.1

 Declaration of the logical link .................................................................... 16.2

 Declaration of logical link bus access ...................................................... 16.2

0-6  
 
 
 

Chapter 17
Hybrid logical link with an access on leased B channel example

  Introduction ............................................................................................. 17.1


  Declaring the logical link .................................................................... 17.1
  Declaring the compressed access with its trunks .................... 17.2
  Declaring the first trunk ...................................................................... 17.2
  Declaring the second trunk ............................................................... 17.2
 
Declaring the non-compressed access with its trunk ............. 17.3

Chapter 18
Maintenance

  "compvisu" command ......................................................................... 18.1


  Syntax .......................................................................................................... 18.1
  "lio" option .................................................................................................. 18.1
  "eqt" option ................................................................................................. 18.2
  all" option .................................................................................................... 18.3
  "cr cpl" option ............................................................................................. 18.3
 
"cr cpl" Option ............................................................................................ 18.3
  “trkvisu comp” command .................................................................. 18.4

 
  0-7
 
 

0-8  
 


1 

1.1 Description of the service


The voice compression service is used to optimize resources by throughput of several voice
communications on the same support. This is made possible by the use of a voice
compression technique. This technique can reduce required throughput from 64 kb (or 56 Kb)
to 8 kb for transmission of a voice call, resulting in a reduction of the resources required for a
given traffic flow and consequently a reduction in cost.
Note:
This service is available only between two ACTs.
56 Kb/s supports are notably used in the USA.
This service can be implemented for :
- ABC logical links,
- ABC inter-network trunks.
This service may be used on :
- a permanent leased support (fixed rate metering),
- a support established on request (metering by duration or volume).
This support can be one of the following types :
- sychronous B channel of E1-CCS type (digital signalling),
- sychronous B channel of T1 type (CCS or CAS signalling),
- asynchronous by Frame Relay or Transfix.
The boards used are :
- LIOB with compressors, 4 T0 connections and a Transfix connection,
- LIOP with compressors and one E1-CCS connection,
- LIOX with compressors.
The LIOB, LIOP and LIOX board compressors are mounted on COMP2 daughter boards with
8 compressors.

1.2 Definitions
LIO : (LInk Optimiser) Compression board.
B TS or B channel : 64 kbit (or 56 Kbit) voice channel.
Compressor : Device used to compress a 64 kbit (or 56 Kbit) voice channel into a compressed
voice channel of around 8kbits.
Compressed voice channel : Voice channel at 64 kbits (or 56 Kbits) having undergone signal
processing to become an 8 kbit compressed voice channel.
(Compression) support TS : Voice channels at 64 kbits (or 56 Kbits) transporting x



     
     ! 1-1
Chapter 1   !

compressed voice channels plus 1 signalling channel plus one or two data channels.
(Compression) support trunk group : if the support TS is transmitted on a public trunk group,
the public trunk group is known as "Support trunk group".
Virtual access : Virtual equipment of the compression board. Virtual access corresponds to a
direction in which the number of compressed voice channels of the support TS is defined.
Compressed logical link : Logical link whose channels are compressed channels.
Dynamic compressed logical link : Logical link whose accesses are set up on request.
DLCI : (Data Link Connection Identifier), this identifier enables the remote to be designated in
Transfix frame relay networks.

1.3 Restrictions
Modem or minitel calls are not possible on the compressed links.
Transit is not possible between LIO (P/B/X with COMP2) and INT-IP : one call using B channel
compressed trunks and IP compressed trunks requires one or more
decompression/compression operations.

1.4 Reference to related modules


Voice compression is documented in the following modules :
- Functional description(see module Voice compression - Detailed description ),
- Installation(see module Voice compression - Installation procedure ),
- Management(see module Voice compression - Configuration procedure ),
- Management examples(see module Voice compression - Configuration examples ),
- Maintenance(see module Voice compression - Maintenance ).

1-2 

     
     !


2
    

2.1 General principle


The general principle of compression is to benefit from the throughput rate reduction obtained
by the compression algorithm to encapsulate all data relating to compressed communications
in one TS .
In a composite TS support resource there are:
- the compressed voice channels,
- a signalling channel used to demultiplex the compressed channels,
- one or two HDLC data channels.

Figure 2.1: Contents of a compressed channel support



     
   "#     2-1
Chapter 2 "#    

Figure 2.2: Case of a T2 support

2-2 

     
   "#    
"#    

Figure 2.3: Case of a T1 support

2.2 Hardware resources


The LIO function is performed by one of the following ACT boards:
- LIOX board with:
• 4 virtual accesses,
• 1 compression daughter board,
- LIOP board with:
• 4 virtual accesses,
• 1 compression daughter board,
• 1 T2 physical access,
- LIOB board with:
• 4 virtual accesses,
• 1 compression daughter board,
• 4 T0 physical accesses,
• 1 Frame Relay access.
The compression board is a “COMP2” type compression daughter board. This daughter board
has 8 compressors. These compressors can operate at G723 or G739 standards. The old
“Comp6” daughter board only operates at G723 standard.
The physical accesses (T0 or T2) are independent of the compression function. They are



     
   "#     2-3
Chapter 2 "#    

simply used to reduce the number of boards to be installed.


E.g.: LIOP = LIOX + PRA

2.3 Voice compression


The voice coding used complies with recomendation G723, and is used to compress the voice
from 64kb/s (or 56kb/s) to around 8 kb/s.
Voice channel compression is carried out using a dedicated processor (DSP) called a
compressor. The compressors are installed on LIO (LIink Optimiser) type boards.
Processing time and signal deterioration limit the number of compressors used in cascade to
2. When a communication transits via an intermediate node, this node must be notified so that
no decompression/compression is carried out on this communication.
The compression algorithm used is designed for voice and cannot be applied to signals of fax,
modem and tone type, which are therefore transmitted at the same rate. Consequently,
specific processing is required to detect (differentiate with respect to voice signals) these
signal types and transmit them.

2.4 Setting up a compressed channel


Setting up the first channel:
Set-up of a compressed call takes place as follows:
- exchange of signalling relative to support set-up (if dynamic support),
- support set-up,
- signalling channel set-up,
- exchange of signalling relative to voice channel set-up,
- compressed voice channel set-up.
Setting up the following compressed channels:
Set-up of a second compressed channel takes place as follows:
- exchange of signalling relative to second channel set-up,
- set-up of the additional compressed voice channel.
Call support release:
At the end of the last compressed call, the support, if dynamic, will be released. This release
occurs after a parameterable time-out.

2.5 Mutual aid


Mutual aid allows a virtual access on a LIO board to use compressors located on another LIO
board.
Example of mutual aid use:
A LIO1 board manages 2 virtual accesses, each used by 6 voice communications: this board
needs 12 compressors.
A LIO2 board manages a virtual access used by 4 voice communications: this board needs 4

2-4 

     
   "#    
"#    

compressors.
The “Comp2” board has 8 compressors; the mutual aid function allows the system to allocate
the 4 free LIO2 board compressors to the virtual accesses of the LIO1 board.
The manager can prohibit mutual aid on a board. The compressors on this board are then no
longer available to aid the other LIO boards.

2.6 DATA communication


On the support TS, x compressed voice channels will be multiplexed, 1 signalling channel, and
1 or 2 data channels.
The data function is declared in the LIO board (with Data Compression = Yes/No),
Behaviour and throughput vary according to the operating mode :
- synchronous V120 transmission : this transmission mode is not possible with compressed
links.
- asynchronous V120 transmission : this transmission mode is possible with a throughput
between 0 and 9600 b/s. The throughput varies according to the calls set up and the
signaling traffic.
- transparent HDLC transmission: this transmission mode is possible with a throughput
between 0 and 48 Kb/s when the support is a 64 Kb/s B channel. If the support is a 128
Kb/s Transfix link, the data throughout can be up to 64 Kb/s. In both cases, the throughput
depends on the calls set up and the signaling traffic.
Using data limits the number of virtual accesses via the LIO board to 2.

2.7 Applications using T0 or T2 B-Channels as support

2.7.1 Logical links on leased B-channels


Several PABXs can be interconnected in network by using leased B-channels. Each leased
B-channel allows voice communication.
Compression enables each leased B-channel to transport several compressed voice channels
as well as HDLC channels (signalling + low throughput data).
The value of compression is therefore to reduce, for a given traffic rate, the number of leased
B-channels, which results in reduced operating costs.
The compressed signaling channel transits ABC-F2 compatible signalling; the service offered
between PABXs is therefore level ABC - F2. So the user on a station will not see the difference
between normal and compressed leased logical links.



     
   "#     2-5
Chapter 2 "#    

Figure 2.4: Compressed logical links through leased links


Leased links allow point to point connections, so the carrier therefore needs to lease one link
per logical link.
In logical links of this type, several compressed accesses can be declared to increase the
capacity of the inter node link.

2.7.2 Compressed logical links through the public network


This application is similar to the previous one, however the support B-channel(s) are set up on
request. The network is therefore similar to a private network whose logical links, called
dynamic, only use the TSs of the public network when there is information to be transmitted
(voice, application data), otherwise they are cut.

Figure 2.5: Compressed logical links through the public network (dynamic logical links)
The first communication sets up the support TS between the 2 nodes. A path is then opened
between the 2 LIO boards through the public network. The following compressed

2-6 

     
   "#    
"#    

communications use this support.


The procedure for a private call on a compressed dynamic logical link is as follows:

Figure 2.6: Private call on dynamic logical link


(*) the support communication must be of "digital without restriction" type, also called "digital
from end to end". If certain sections are not digital, the support will be unable to perform this
application.(*)

2.7.3 Compressed trunk groups through the public network


A trunk group connecting 2 OmniPCX 4400 PABX in different networks can be compressed.
This trunk group can be used as support for public network B-channels.
This application is used, for example, to connect two different companies which exchange
telephone calls frequently.



     
   "#     2-7
Chapter 2 "#    

The first communication sets up the support B-channel and the following compressed
communications use the same support.
This is known as free second communication. Up to 8 free communications are possible.

Figure 2.7: Compressed trunks through the public network


The various steps of the trunk group seize on public network are as follows:

2-8 

     
   "#    
"#    

(*) the address present in the set-up request is composed of :


- the ISDN address of the site (main address field),
- the trunk group number (secondary address field).
Thus, on arrival, the system will be able to find the incoming compressed trunk group.

2.8 Compression and hybrid logical links


A hybrid logical link can have compressed accesses amongst its various accesses. These can
be: Switched B-channels, leased B-channels, leased Transfix, or Frame Relay Transfix type
accesses.

2.9 Applications using an analog signalling trunk



     
   "#     2-9
Chapter 2 "#    

Compressed trunks may be used on an analog signalling support transiting on a public


network, e.g. a CAS trunk on DPT1 board. The support board is either a DPT1 or a PCM
board. The analog signalling must be of LIA, SDA/BCA or COMBINED type.
A logical link is not possible on this type of support.

2.10 Applications using Transfix as support


A compressed link can use a leased (fixed-rate metering) Transfix link as a support, or
Transfix Frame relay (metering by volume). As for B channel supports, Transfix supports allow
logical links and compressed trunks.
The type of support can be different at the compressed link ends. On some public networks, it
is possible to lease a link with a TS on T0 or T2 at one end and a leased Transfix link at the
other.
A link can thus be made as follows :

2.11 Interactions

2.11.1 ARS and compressed trunk groups


ARS is not compulsory when using a compressed trunk group. A trunk group seize prefix is
sufficient.
However, the ARS mechanism improves operation. It can be used to redirect a maximum
number of calls to the compressed trunk group while remaining transparent to the user. It can
also be used to optimize the processing of compressed trunk group overflows.
To do this, an initial route to the compressed trunk group, then the overflow routes, must be
declared in the ARS routing table.

2.11.2 Metering and compressed links


2.11.2.1 Metered terminal node (also called an end or final node)

2-10 

     
   "#    
"#    

The public network has no knowledge of compressed calls, since it only processes the support
communication.
The terminal node sets up the support that is metered. Metering duration is counted for the
time during which the support is set up.
Therefore, a terminal node which set up a support for a compressed link takes charge of the
support costs whatever the number and source of calls. In addition, upon call completion it
continues to be metered because of compressed communications in progress or to come
which maintain support set-up.
The manager may bar compressed call set-up by the terminal node which did not set up the
support. Thus only the metered terminal node benefits from free calls.
2.11.2.2 Metering information
Sets cannot use the metering counter during a compressed communication. The only metering
information supplied by the public network concerns the support communication.
Case of a compressed public call
The metering ticket generated by the support communication is the same as for an external
call with the following specific information:
- the metered number field is replaced by the number of the compressed trunk group,
- the name of metered user field is replaced by the name of the compressed trunk group,
- the entity number is that of the compressed trunk group entity,
- the cost center field is set to 255,
- the dialled number field contains the sub-address.
Case of a compressed private call via ISDN
The same fields are used as for a "Full-VPN" application, but the number and name of the
logical link are used.
The ticket generated for each compressed call features:
- a charge unit field set to 0,
- the number of the compressed trunk group used.

2.12 Limits and constraints


The switched network used to enable compression (trunk group or logical link) must be digital
from end to end.
The "support" link must be managed before managing the compressed link.
One end of a compressed dynamic logical link is necessarily a terminal node (also called an
end or final node).
The compressed trunk group must not be distributed.



     
   "#     2-11
Chapter 2 "#    

2-12 

     
   "#    


3   

3.1 Transmission on T0

There are two possible connection methods:


1. Use of the LIOB board. See module LIOB - External connections ,
2. Use of the LIOX and BRA2 or BPRA2 boards:
• LIOX, this board has no connection,
• BRA2. See module BRA2 - External connections ,
• BPRA2. See module BPRA2 - External connections ,
The technician must be careful to check the strapping.

3.2 Transmission on T1


$
     
   % ## &  3-1
Chapter 3 % ## & 

Connection to a T1 link is achieved via the DPT1 board, the LIOX board ensures compression
functions.
- LIOX, this board has no connection,
- DPT1. See module DPT1 - External connections .
The information above is valid for both digital and analog signalling T1s.
The technician must be careful to check the strapping.

3.3 Transmission on T2

3-2 
$
     
   % ## & 
% ## & 

There are two possible connection methods:


1. Use of the LIOP board,
2. Use of LIOX and PRA2 or BPRA2 boards:
• LIOX, this board has no connection,
• PRA2. See module PRA2 - External connections
• BPRA2. See module BPRA2 - External connections ,
The technician must also be careful to check the strapping.

3.4 Transmission on Transfix

The connection to leased or frame relay transfix is achieved via the LIOB board, which
ensures both the compression and connection functions. (See module LIOB - External
connections ).
The technician must also be careful to check the strapping.

3.5 Additional compressors


In all the above configurations, one or several LIOX boards may be added to increase the
number of available compressors on the PABX.


$
     
   % ## &  3-3
Chapter 3 % ## & 

3-4 
$
     
   % ## & 


4   

4.1 Management principle


To create a compressed element proceed as follows :
- create or reuse a support,
- declare the compressed element with its virtual access,
- indicate in the compresed element which support is to be used.

4.2 Objects used by compression

4.2.1 Board
Object name : Shelf > Board
Attributes :
Shelf address : Enter the ACT number
Board address : Enter the board number
Interface type : Select the type of board used:
LIOX, LIOP, LIOB.
Use data compression : Yes : data compression is active.
No : data compression is not active.
Mutual aid : Yes : the compressors on this board can be allocated
to virtual accesses defined on another board.
No : the compressors on this board can only be used
by virtual accesses local to the board.
LIO Daugter board : Select the type of daughter board used :
“6 compressors ” : use of the “Comp6” daughter
board (old 6 compressor board).
“8 compressors ” : use of the “Comp2” daughter
board.
Number of compressors used : Display of the number of compressors used on this
board.

4.2.2 Transfix access


A Transfix access object is created automatically as soon as a LIOB board is created, to be
managed if necessary.
Object name : Shelf > Board > Transfix access
Attributes :


$
     
   '& # &  4-1
Chapter 4 '& # & 

Shelf address : Enter the ACT number


Board address : Enter the board number
T0/T2 access no. : Enter 4 : access 4 is the only Transfix access of LIOB
boards.
Access type : Display of access type :
- “Not used ” : transfix access is not used.
- “Transfix ” : transfix accesss is used.
Network mode : No : the access does not initialize connection.
Yes : the access initializes connection.
In leased transfix mode, one of the link accesses must
have network mode set to Yes, the other to No.
In transfix frame relay mode, both ends of the link
must be set to No.
Access Id : Free number for the manager.
Function : Select the access function mode :
“X24_V11 ” : physically, the X24/V11 standard is used.
“V36 ” : physically, the V36 standard is used.
Access throughput : Enter access throughput.
Information field size : Enter the maximum size of the information field.
Support type : Select the type of support :
- “Leased ” : a leased Transfix support is used.
- “Network no. ” : a Transfix Frame Relay support is
used.
Signalling protocol type : Select the type of signalling :
- “IT ” : for network signalling to Q.933 standard,
Annex A.
- “Ainsi ” : for network signalling to T1.617
standard, Annex D.
This field is only accessible for Transfix Frame relay.
Full state counter interrog : Used only for ITU signalling.
Error threshold : Used only for ITU signalling.
Number of incidents observed : Used only for ITU signalling.
Link check request timer : Used only for ITU signalling.
Interrog. check timer : Used only for ITU signalling.

4.2.3 Compressed trunk declaration


In the "Trunk" object an attribute indicates if the trunk is compressed or not;
Object name : Trunk
Attributes :
Trunk no. : Enter the trunk no.
Trunk type : Select “T2 ” (mandatory) even if T0s are used.
T2 special feature : Select “Compressed “ (mandatory).

4-2 
$
     
   '& # & 
'& # & 

Channel selection type : Select "Channel no. by channel no. " (mandatory).

The other attributes are not relevant to "Voice Compression".

4.2.4 T0/T1/T2 access


Object name : Trunk groups > Trunk group > T0/T1/T2 Access
Attributes :
Trunk group Id : Enter the trunk group number
Physical address : Enter the physical address, in the form ACT
No.-board No.-virtual access used No.,
Access type : Select the support access type :
- "Virtual_Voice_Leased " : if the compression is
made on a leased B-channel,
- "Virtual_Voice_Switched " : if the access is a
switched B-channel (public network),
- "Virtual_Transfix_Leased " : if the access is
leased digital type,
- "Virtual_Transfix_Frame_Relay " : if the access
is made on a Frame Relay network.
Access Id : Display of the value allocated by the system.
Virtual time slots : Set the Booleans designating the time slots which
can be used. TS 0 can never be used, 7 TSs can be
used for the compressed accesses (6 for voice, 1 for
data).
See note below.
ISDN call no. for compression : Enter the number of the remote site; this number is
the concatenation of the public trunk group seize, a
DDI number of the remote site, the characters "*", the
number of the corresponding compressed trunk
group number in the remote site.
This attribute only appears when the "Access type "
is set to "Virtual_Voice_Switched " (see details .
module Voice compression - Configuring a trunk
group on a public network B channel ).


$
     
   '& # &  4-3
Chapter 4 '& # & 

Support time slot address : Enter the physical address of the support TS
(ACT-No. -board No.-equipment No.-junctor No.).
Since the support trunk group junctors are shared,
make sure that the TS designated here is not busy.
In the "T0/T2 Access" object of the support trunk
group, therefore, indicate that this TS cannot be used
(set the corresponding Boolean in the "Time slot"
attribute to 0).
This attribute only appears when the "Access type "
is set to "Virtual_Voice_Leased " (see details
module Voice compression - Configuring a trunk
group on a leased B channel if digital signalling of
T0/T1/T2 type or module Voice compression -
Configuring a trunk group on an analog signaling
support if T1 with analog signalling).
Support release timer (100 ms) : Enter the time during which the system keeps the
support after the end of the last communication. This
time-out is used to limit support communication
closures.
This attribute is only significant when the "Access
type " is set to "Virtual Voice Switched ".
Protection timer (1 mn) : Enter the maximum duration of the support
communication (units in minutes).
DLCI : Enter the DLCI number,
This attribute only appears when the "Access type "
is set to "Virtual Tfx_Frame_Relay " (see details
module Voice compression - Configuring a trunk
group and logical link on Transfix ).
Committed Information Rate (CIR) : This attribute only appears when the "Access type "
is set to "Virtual Tfx_Frame_Relay ".
Extended Information Rate (EIR) : This attribute only appears when the "Access type "
is set to "Virtual Tfx_Frame_Relay ".
CIR measurement interval : This attribute only appears when the "Access type "
is set to "Virtual Tfx_Frame_Relay ".

Note: Time slot:


By default, the following value is obtained on creation
01111110000000000000000000000000
If this value is validated, with the "Use Data Compression" parameter set to No, the following
value is obtained in consultation
02222220000000000000000000000000
If the "Use Data Compression" parameter is set to Yes, the following value is obtained in
consultation
02222221000000000000000000000000
In consultation
- 0 indicates that the channel is not used,

4-4 
$
     
   '& # & 
'& # & 

- 1 indicates that the channel is available for data communication,


- 2 indicates that the channel is available for voice communciation.

4.2.5 Logical links


Object name Inter-Nodes Links > Logical Links (ABC-F)
Attributes
Link name : Enter the link name,
Link type : Select "Compressed " for a compressed logical link,
Signal Establis. Mode : select the setup mode
- “Permanent user ”: the logical link support is set up on
system initialisation,
- “ On request ”: the communication support is set up each
time it is required,
Caution 1: For this attribute, see the note below
B Channel choice : Select whether or not (Yes or No) the local interface selects the
B-Channel. One end must be set to Yes and the other to No.
Routing type : Select whether or not (Yes or No) this logical link is used to
transport the routing information
Yes the logical link transports the routing information. This option
must only be used for a permanent logical link. The system can,
in fact, only request that the logical link be set up to transport
routing information. This may become costly if the logical link
uses a metered switched support.
No : the logical link does not transport routing information, this
option must be used with the logical links set up upon request.
Caution 2: See the note below.
TS distribution : Select No, the support does not need to change in case of
accesses compression.

The other attributes are not relevant to "Voice Compression".


Caution 3:
Routing type and signal establishment mode :
If a compressed dynamic logical link (with static routing) to a node Y is used, then the rest of
the network ignores the potential of the device(s) over the compressed logical link.
Only the following configuration is therefore possible :


$
     
   '& # &  4-5
Chapter 4 '& # & 

Figure 4.1: Configurations with a dynamic logical link

4.2.6 Link bus access


Object name: Inter-Node-Link > Logical Links (ABC-Fx) > Bus-Link Access
Attributes:
Link name : Enter the name of the logical link.
Physical address : Enter the physical address of the virtual access used (in
the form ACT No.-board No.-equipment No.).
Access type : Select the support access type :
- "Virtual_Voice_Leased " if the compression is made
on a leased B-channel,
- "Virtual_Voice_Switched " if the access is a switched
B-channel (public network),
- "Virtual_Transfix_Leased " if the access is leased
digital type,
- "Virtual_Transfix_Frame_Relay " if the access is
made on a Frame Relay network.
Access.Id : Enter the access number. The values must be identical at
both ends of the logical link. Note that the "node No. -
Access.Id " pairs must all be different. (There is a
maximum of 16 "Acces.Id" per direction).
Access cluster Id. : Displays the access group number automatically allocated
by the system. This attribute does not appear during
creation.
Virtual time slots : Set the Booleans designating the time slots which can be
used. TS 0 can never be used, 7 TSs can be used for the
compressed accesses (6 voice + 1 data channel).
The description is identical to that of "T0/T1/T2 Acces".

4-6 
$
     
   '& # & 
'& # & 

Support Time Slot Address : Enter the physical address of the support TS (ACT
No.-board No.-equipment No.-junctor No.). Since the
junctors of the support trunk group are shared, make sure
that the time slot designated here is not busy. In the "T0/T2
Access" object of the support trunk group, therefore,
indicate that this time slot cannot be used (set the
corresponding Boolean in the "Time slot" attribute to 0).
"This attribute only appears when Access type " is set
to"Virtual_Voice_Leased " (see details module Voice
compression - Configuring a logical link on a B channel ).
ISDN adjacent node call : Enter the number of the remote site; this number is the
number concatenation of the public trunk group seize, a DDI
number of the remote site.
"This attribute only appears when"Access type " is set to“
Virtual_Voice_Switched " (see details module Voice
compression - Configuring a logical link on a public
network B channel ).
DLCI : Enter the DLCI number,
This attribute only appears when the "Access type "is set
to "Virtual Tfx_Frame_Relay " (see details module Voice
compression - Configuring a trunk group and logical link on
Transfix ).
Committed Information Rate : Enter the subscribed rate. This attribute only appears when
(CIR) "Access type "is set to "Virtual Tfx_Relais_Trame ".
Extended Information Rate : Enter the additional rate. This attribute only appears when
(EIR) "Access type " is set to "Virtual Tfx_Frame_Relay ".
CIR Measurement Interval : Enter the measurement interval. This attribute only
appears when "Access type " is set to "Virtual
Tfx_Frame_relay ".

4.2.7 Hybrid Link Access


In order to create a compressed access in a hybrid logical link, a "Hybrid logical link access"
attached to the logical link must be created.
Restrictions:
- There can be no standby signaling on a compressed hybrid access.
- A compressed hybrid access cannot be direct backup for another hybrid access.
- Only the TSs of the compressed access can be incorporated to the corresponding hybrid
access.
Object name: Inter-Nodes Links > Logical Links (ABC-Fx) >Hybrid Link Access
Attributes :
Link name : Enter the name of the logical link using this access,
Access number : Enter this access number ( module Hybrid logical
links - Detailed description ),


$
     
   '& # &  4-7
Chapter 4 '& # & 

Signalling type : Select, for a compressed access one of the following


types :
"Virtual-Voice-Switched " : for B-channel on public
network,
"Virtual-Voice-Leased " : for B channels on leased
line,
"Virtual-Transfix-Leased " : when Transfix is used,
"Virtual-Tfx-Frame Relay " : when Frame relay is
used.
Main established tempo :
Has StandBy Signalling : Select "No" (never backup for compressed
signalling),
StandBy Signalling Type : Select "Not used" (mandatory),
Directory Number : Enter the number of the remote site (format : trunk
group seize followed by the directory number of the
remote site),
C "This attribute only appears for
Virtual-Voice-Switched " type signalling.
Main trunk group id. : Display the number of the trunk group given by the
system,
Phys access for main trunk group : Enter the number of the virtual access used (format :
ACT No.-Coupler No.-Equipment No.),
Support time slot address : Enter the address of the support TS (format: ACT
No.-Coupler No.-Equipment No.- Position No.),
This attribute only appears for
"Virtual-Voice-Leased " type signalling.
DLCI : Enter the DLCI,
This attribute only appears for "Virtual-Tfx-Frame
relay " type signalling.
Committed Information Rate (CIR) : Enter the subscribed throughput,
This attribute only appears for "Virtual-Tfx-Frame
Realay " type signalling.
Extended Information Rate (EIR) : Enter the value of the additional throughput,
This attribute only appears for"Virtual-Tfx-Frame
Relay " type signalling.
CIR measurement interval : Enter the value of the measurement interval.
This attribute only appears for "Virtual-Tfx-Frame
Relay " type signalling.

4.2.8 Virtual access


Each virtual access is a digital access with a physical address and specific data.
The following diagram describes positions of the virtual accesses according to the board type :

4-8 
$
     
   '& # & 
'& # & 

Figure 4.2: Virtual access distribution


Example:
An LIOP board is inserted in position 3 in shelf 0. Its virtual accesses have the following
numbers :
0-3-1, 0-3-2, 0-3-3, 0-3-4
Object name : Shelf > Board > Virtual Access
Attributes :
Shelf address : Enter the number of the shelf where the virtual access is,
Board address : Enter the number of the board where the virtual access
is,
No T0/T2 access : Enter the number of the chosen virtual access,
Access type : Display the access type. This attribute is automatically
completed during management of the compressed trunk
group or logical link.
Network Mode : Select whether or not (Yes or No) this virtual access
reacts like a network with respect to compressed
signalling. One end of the virtual link must be Yes and
the other No.
Min Voice Jitter Buffer : Reserved for Alcatel maintenance, Default value : 0 ms
Max Voice Jitter Buffer : Reserved for Alcatel maintenance, default value : 60 ms
Min Fax Jitter Buffer : Reserved for Alcatel maintenance, default value : 60 ms
Max Fax Jitter Buffer : Reserved for Alcatel maintenance, default value : 120 ms


$
     
   '& # &  4-9
Chapter 4 '& # & 

Mux : Reserved for Alcatel maintenance, default value : 100


Information size : Reserved for Alcatel maintenance, Default value : 260
SSCOP UU size : Reserved for Alcatel maintenance, Default value : 260
CC Timer : Reserved for Alcatel maintenance, Default value : 10
POLL Timer : Reserved for Alcatel maintenance, Default value : 5
NO RESPONSE Timer : Reserved for Alcatel maintenance, Default value : 50
KEEP ALIVE Timer : Reserved for Alcatel maintenance, Default value : 20
Inactivity Timer : Reserved for Alcatel maintenance, Default value : 150
Max PDU Control : Reserved for Alcatel maintenance, Default value : 4
Max PDU Data : Reserved for Alcatel maintenance, Default value : 128
N S N R Field Size : Reserved for Alcatel maintenance, Default value : 1
Throughput rate : Select the link throughput :
- “64K ”: if the support is T0 or T2 type,
- “56K ”: if the support is T1 type.

4.3 Reference to other modules


Refer to the following modules according to the compression support you have to manage.
Each of these modules explains the management principles and rules to observe and also
refers to a “Management example” module illustrating the topic in question.
- Trunk groups on leased B channels(see module Voice compression - Configuring a trunk
group on a leased B channel ),
- Trunk groups on public network B channels (see module Voice compression - Configuring
a trunk group on a public network B channel ),
- Trunk groups on T1 connections to public network analog signalling(see module Voice
compression - Configuring a trunk group on an analog signaling support ),
- Logical link on leased B channels(see module Voice compression - Configuring a logical
link on a B channel ),
- Logical on public network B channels(see module Voice compression - Configuring a
logical link on a public network B channel ),
- Hybrid logical link with leased B chanel compressed access(see module Voice
compression - Configuring a hybrid logical link on a leased B channel ).
- Trunk group and logical link on Transfix (see module Voice compression - Configuring a
trunk group and logical link on Transfix ).

4-10 
$
     
   '& # & 


5    


    

5.1 Principle
The manager must proceed as follows:
- declare the LIO (LIOX, LIOP, LIOB) type board, indicating if there is data compression and
mutual aid.
- declare a support trunk (uncompressed) ,
- declare the compressed trunk (only T2 type) with appropriate signalling (RNIS, ABC-Fx,
QSIG ....). One end must be network type, the other, user type. One end must have a
choice of B channel, the other not.

5.2 Relationships between objects


$
     
   '& ' #  &( ' &  # #  ) 5-1
*#
Chapter 5 '& ' #  &( ' &  # #  ) *#

Figure 5.1: Relationship between objects for creation of a compressed trunk on leased
channels

5.3 Rules to observe when creating a compressed trunk


Each rule is illustrated by a number in the figure below:
1. Declare a standard trunk with as many trunk grups as B channels leased from the carrier,
2. Match the trunk group physical addresses, of "T0/T2 Access" and ISDN access,
3. Declare a compressed trunk with as many trunk groups as compressed channels,
4. Match trunk group physical addresses, of "T0/T2 Access" and virtual access,
5. Match the support TS address with the support trunk address.

5.4 Management example


See module Voice compression - Trunk group on leased B channel example

5-2 
$
     
   '& ' #  &( ' &  # #  )
*#


6    


      

6.1 Principle
The manager must proceed as follows:
- declare the LIO type board,
- declare (or reuse) a support trunk group (not compressed) with its global and local data, its
trunks, its T0/T1/T2 access and its ISDN access leading to the public network. This trunk
group can be used by the compressed trunk group but also for all communications to this
public carrier. The compressed trunk group uses only one TS of this public trunk group.
- declare the compressed trunk group with its global and local data, its trunks, its T0/T1/T2
access and its virtual access. The T0/T1/T2 access contains the remote "address".

6.2 Relationships between objects


$#
     
   '& ' #  &( ' &  # & ! ( 6-1
) *#
Chapter 6 '& ' #  &( ' &  # & ! ( )
*#

Figure 6.1: Relationship between objects to create a compressed trunk group on B-channels
on a public network

6.3 Rules to be observed


Each rule is illustrated by one of the numbers of the previous figure.
1. Declare a public trunk group leading to the carrier,
2. Match the physical addresses of the trunks, the "T0/T1/T2 access" and the ISDN access
for the public trunk group,
3. declare a compressed trunk group with one trunk for each compressed channel,
4. enter the address of the destination PABX; this address is composed of the following
fields:
• seize of the public trunk group,
• a DDI number of a set on the destination site (this set will not be called by the
compression),

6-2 
$#
     
   '& ' #  &( ' &  # & ! (
) *#
'& ' #  &( ' &  # & ! ( ) *#

• the character "*" indicating the presence of a sub-address,


• the trunk group number of the destination site that the compression is managed on.
example: 0420155662222*21,
• 042 is the seize prefix of the compressed trunk group or ARS prefix,
• 015566 is the first part of the DDI number of the remote site in the public network,
• 2222 is a DDI set number of the remote site,
• * is a separator,
• 21 is the compressed trunk group number of the remote site.

6.4 Example of management


See module Voice compression - Trunk group on B channel on public network example


$#
     
   '& ' #  &( ' &  # & ! ( 6-3
) *#
Chapter 6 '& ' #  &( ' &  # & ! ( )
*#

6-4 
$#
     
   '& ' #  &( ' &  # & ! (
) *#


7     


    

7.1 Principle
The manager must proceed as follows:
- declaring the LIOx type board,
- declaring (or reuse) a support trunk group (not compressed) with its global and local data,
its trunks, its T0/T1/T2 and ISDN accesses leading to the public network. This trunk group
can be used by the compressed trunk group but also for any communications to this public
operator. The compressed trunk group only takes one TS from this public trunk group.
- declaring the compressed trunk group with its global and local data, its trunks, its T0/T1/T2
and virtual accesses. The T0/T1/T2 access contains the remote "address".

7.2 Relationships between objects


$#
     
   '& ' #  &( ' &  # ##' 7-1
'#' &  
Chapter 7 '& ' #  &( ' &  # ##' '#'
&  

Figure 7.1: Relationship between objects for the creation of a compressed trunk group on an
analog signalling support

7.3 Rules to be observed


Each rule is illustrated by a number in the above figure.
1. Declaring a public trunk group leading to the operator,
2. On the public trunk group, the physical address of the trunks must correspond to the ISDN
access physical address,
3. Declaring a compressed trunk group with one trunk per compressed channel,
4. The physical access of the compressed trunk group must correspond to the virtual access
selected,
5. Enter the called PABX address, this address being composed of the following fields:
• public trunk group seizure,
• one DDI number of the called site. The public part must correspond to the called site.
The private part of this DDI number must correspond, on the remote site, to a prefix
whose meaning is “Analog compression support”. This prefix references the incoming
compressed trunk group.

7-2 
$#
     
   '& ' #  &( ' &  # ##'
'#' &  


8    


  

8.1 Principle
The manager must proceed as follows:
- declare the PRA (or compatible) type board or DPT1, with its ISDN access,
- declare the LIO type board with its virtual access,
- declare a logical link, of compressed type, to the remote network ,
- declare a logical link bus access, of leased virtual type, using a support TS of the leased
link.

8.2 Relationships between objects


$
     
   '& ' # '# (  # ) *# 8-1
Chapter 8 '& ' # '# (  # ) *#

Figure 8.1: Relationships between objects for creation of a compressed logical link on leased
B channel

8.3 Rules to observe


Each rule is illustrated by a number on the figure below.
1. Declare (or reuse) an ISDN access to the leased support,
2. Declare a compressed logical link to a remote node,
3. Declare, attached to this logical link, a "Logical link bus access" of leased type using the
leased TS support. This TS must be on the same remote site.

8.4 Management example


See module Voice compression - Logical link on leased B channel example

8-2 
$
     
   '& ' # '# (  # ) *#


9    


      

9.1 Principle
The manager must proceed as follows:
- declare the LIO type board,
- declare (or use) a support trunk group (uncompressed) with its global and local data, its
trunks, its T0/T1/T2 access and its ISDN access to the public network. This trunk can be
used by the compressed logical link but also for all communications to this public carrier.
- declare the compressed logical link with its Logical link Bus Acces and its vitual access. Its
T0/T2 access contains the destination PABX address in the public network.

9.2 Relationships between objects


$#
     
   '& ' # '# (  # & ! ( ) 9-1
*#
Chapter 9 '& ' # '# (  # & ! ( ) *#

Figure 9.1: Relationship between objects for creation of a compressed logical link on B
channel of a public network.

9.3 Rules to observe


Each rule is illustrated by a number on the figure below.
1. Declare (or reuse) a public trunk to the carrier,
2. Match the trunk group physical addresses, of the "T0/T1/T2 Access" and the ISDN access
for the public trunk,
3. Declare a compressed logical link to the remote node,
4. Declare, attached to this logical link, a switched type "Logical link bus access" with an
ISDN address consisting of the following fields:
• public trunk seize,
• a destination site set DDI number (this set will not be called),
5. In addition the "Access id" fields must be identical on both nodes so that the systems can
make the link.

9-2 
$#
     
   '& ' # '# (  # & ! ( )
*#
'& ' # '# (  # & ! ( ) *#

9.4 management example


See module Voice compression - Logical link on B channel on public network example


$#
     
   '& ' # '# (  # & ! ( ) 9-3
*#
Chapter 9 '& ' # '# (  # & ! ( ) *#

9-4 
$#
     
   '& ' # '# (  # & ! ( )
*#


10   


      

10.1 Principle
The manager must proceed as follows:
- declare the support board(s),
- declare a T2 type support link,
- declare a hybrid logical link,
- declare the accesses with a compressed type signalling,
- declare the compressed access junctors,
- declare the accesses to the other types of signalling and their junctors.
Accesses of compressed type are more cost effective than other accesses; thus they must be
used in priority. These accesses must therefore have the lowest numbers and there must be
no rotation between the accesses.

10.2 Relationships between objects


$
     
   '& ' # *+  '# (  # #  ) 10-1
*#
Chapter 10 '& ' # *+  '# (  # #  ) *#

Figure 10.1: Relationship between objects in a hybrid logical link with a compressed access

10.3 Rules to be observed:


Each rule is illustrated by a number shown in the previous figure.
1. The logical link must be "Hybrid" type.
2. The access number of the compressed access must be the lowest.
3. In the "Hybrid Logical Link Access", the attribute "Tr. gr. No. assoc to main" must
correspond to the address of the virtual access used,
4. The “TS Support address” attribute gives the address (ACT no., Coupler no., Devise no.,
Position no.) of the the leased TS used by this access. This TS must be left free by the
support trunk.
Backup signalling cannot be performed directly (see below).

10.4 Backup signalling


We can get round this backup signaling constraint by using the following method :

10-2 
$
     
   '& ' # *+  '# (  # #  )
*#
'& ' # *+  '# (  # #  ) *#

- declare a second access without signalling. The first access signalling is then used in
nominal operation.
- declare in the second access a backup signalling, on channel B, for example. For a
signalling on channel B, it is necessary to specify the remote PABX call number (trunk
group seize + DDI number in the remote PABX).

10.5 Example of management


See module Voice compression - Hybrid logical link with an access on leased B channel
example


$
     
   '& ' # *+  '# (  # #  ) 10-3
*#
Chapter 10 '& ' # *+  '# (  # #  ) *#

10-4 
$
     
   '& ' # *+  '# (  # #  )
*#


11    


    

11.1 Principle
The manager must proceed as follows:
- declare a LIOB type board with its Transfix access,
- declare the trunk group or compressed logical link referencing a virtual access which must
be located on the same LIOB board as the Transfix access.

11.2 Relationships between objects

11.3 Rules to observe


Each rule is illustrated by a number on the figure above.
1. Declare a Transfix access,
2. Declare a trunk group or compressed logical link,
3. Enter the virtual access address in the ”Link bus access” or the ”T0/T1/T2 access” physical


$
     
   '& ' #  &( ' & # '# (  11-1
, # 
Chapter 11 '& ' #  &( ' & # '# (  , # 

address. The Transfix access must be located on the same LIOB board as the virtual
access.
4. Two cases:
• if leased Transfix: no information expected because the Transfix access is necessarily
that of the LIOB board on which the virtual access is declared.
• if Frame Relay Transfix: Enter the DLCI of the remote PABX given by the carrier.

11-2 
$
     
   '& ' #  &( ' & # '# ( 
, # 


12    ! 

12.1 Reference to related modules


Examples of management are described in the following modules:
- Trunk groups on leased B channel (see module Voice compression - Trunk group on
leased B channel example ),
- Trunk groups on B channel of a public network(see module Voice compression - Trunk
group on B channel on public network example ),
- Logical link on leased B channel(see module Voice compression - Logical link on leased B
channel example ),
- Logical link on B channel of a public network(see module Voice compression - Logical link
on B channel on public network example ),
- Hybrid logical link with leased B channel compressed access(see module Voice
compression - Hybrid logical link with an access on leased B channel example ).


$-
     
   '& # #
 12-1
Chapter 12 '& # #


12-2 
$-
     
   '& # #



13        


 ! 

13.1 Introduction
We want to create compressed trunk groups 54 and 76 to make an optimized link between two
sites A and B.
A PRA board is managed in 0-3 on A and in 0-4 on B. An LIOX board is managed in 0-1 on A
and in 0-2 on B. Virtual access 0 has been chosen in this example.

Figure 13.1: Example of optimized leased links


In the above example, user 3255 on site A will call user 4133 on site B by dialing 0544133. He
will therefore use the compressed trunk group connecting the two sites.
In the above example, user 4133 on site B will call user 3255 on site A by dialing 0763255.

13.2 Declaring the support trunk group

13.2.1 Declaring PRA (support) boards and derivatives


Object name: Shelf > Board
SITE : A : B
Shelf Address : 0 : 0
Board Address : 3 : 4
Interface Type : PRA : PRA

====================================================
Object name: Shelf>Board/>ISDN access
Attributes:
SITE : A : B
Shelf Address : 0 : 0
Board Address : 3 : 4


$.
     
   , &( ' &  #  ) *# #
 13-1
Chapter 13 , &( ' &  #  ) *# #


T0/T2 Access No. : 0 : 0


Access Type : T2 : T2
Max Nb of Used B Channels : 30 : 30
Synchronisation Priority : 255 : 255
Network Mode : Yes : No CAUTION!
TieLine Mode : No : No
With Alarm : No : No
Reserved1 : Yes : Yes
Reserved2 : Yes : Yes
Network Date Time Update : No : No
CRC4 : No : No

13.2.2 Support trunk group and derivatives


object name: Trunk group
Attributes:
SITE : A : B
Trunk Group Id. : 44 : 75
Trunk Group Type : T2 : T2
Trunk Group Name : Fx-A-B : Fx-B-A
Number Compatible With : 0 : 0
Adjacent network : 255 : 255
Shared Trunk Group : No : No
DDI transcoding : No : No
Transcom Trunk Group : No : No
Auto.reserv.by Attendant : No : No
Overflow trunk group No. : No : No
Tone on seizure : Yes : Yes
Private Trunk Group : No : No
Q931 signal variant : ISDN FRANCE : ISDN FRANCE
Number Of Digits To Send : according to dialing : according to dialing
plan plan
Channel type selection : Channel No. by : Channel No. by
Channel No. Channel No.
(imperative) (imperative) CAUTION!
DTMF dialing on outgoing call : No (imperative) : No (imperative)
T2 specificity : Without (imperative) : Without (imperative)

====================================================
Object name: Trunk Groups >Trunk Group

13-2 
$.
     
   , &( ' &  #  ) *# #

, &( ' &  #  ) *# #


Attributes:
SITE : A : B
Trunk Group No. : 44 : 75
Trunk Group Type : T2 : T2
Public Network Ref. : F-A-B : F-B-A
VG for non-existent No. : Yes : Yes
Entity No. : 0 : 0
Supervised by Routing : No : No
VPN cost circuit for Incom. Calls : 9 : 9
Immediat Trk Listening For VPN Call : Yes : Yes
VPN TS% : 0 : 0
Csta Monitored : No : No
Max% of trunks out CCD : 0 : 0
Ratio analog to ISDN tax : 0.000 : 0.000
Turn In Access : Yes : Yes
Dialling end to end : No : No
DTMF end to end signal. : No : No
Trunk group used in DISA : No : No
DISA secret code : ---- : ----
Rerouting to Executive : No : No
Trunk Category Id. : 16 : 16
Nb of digits Unused (ISDN) : 0 : 0
B Channel Choice : Yes : No CAUTION!
Channels Reserved By Attend. : 0 : 0
Dissuasion For ACD : No : No
DTO joining : No : No
Enquiry Call on B-channel : No : No
Automated Attendant : No : No
Calling party Rights category : 0 : 0
TS Overflow : Yes : Yes
Number To Be Added : ----- : -----
Charge Calling And ADN Creation : No : No
Logical Channel : 1_15_17_31 : 1_15_17_31
(consultation only) (Consultation only)

====================================================
Object name: Trunk groups > Trunk group > T0/T1/T2 access
Attributes:


$.
     
   , &( ' &  #  ) *# #
 13-3
Chapter 13 , &( ' &  #  ) *# #


SITE : A : B
Trunk Group Id. : 44 : 75
Physical Address : 0-3-0 : 0-4-0
T2 Time Slots : 01000000 00000000 : 01000000 00000000
00000000 00000000 00000000 00000000
(assume that only TS 1
is leased)

====================================================
Object name: Trunk Groups>Trunk Group>Trunks
Attributes:
SITE : A : B
Trunk Group No. : 44 : 75
Physical address : 0-3-0-1 : 0-4-0-1
Trunk Category Id. : 16 : 16
Directory Name : t2-1 : t2-1
Trunk Routing Number : ---- : ----
Channel specialization : Mixed : Mixed
Trunk Number : value given by the : value given by the
system system
Data Transparency : Yes : Yes

13.3 Declaring compressed trunk groups

13.3.1 Declaring LIOx compression boards


Object name: Shelf > Board
SITE : A : B
Shelf Address : 0 : 0
Board Address : 1 : 2
Interface Type : LIOX : LIOX
Use Data Compression : No : No
Mutual Aid : Yes : Yes
LIO coupler daughter : 8 Compressors : 8 Compressors
board

13.3.2 Declaring the virtual access


Object name: Shelf > Board > Virtual Access
Attributes:

13-4 
$.
     
   , &( ' &  #  ) *# #

, &( ' &  #  ) *# #


Shelf Address : 0 : 0
Board Address : 1 : 2
T0/T2 access No. : 0 : 0
Access Type : Virtual Voice Leased : Virtual Voice Leased (set
when creating the "T0/T1/T2
access")
Network Mode : Yes : No CAUTION!

The other attributes of this object are not to be managed.

13.3.3 Declaring the compressed trunk groups and their derivatives


object name: Trunk Groups
Attributes:
SITE : A : B
Trunk Group Id. : 54 : 76
Trunk Group Type : T2 : T2
Trunk Group Name : Fx-A-BComp : Fx-B-AComp
Number Compatible With : 0 : 0
Adjacent network : Leave the default : Leave the default
value value
Shared Trunk Group : No : No CAUTION!
DDI transcoding : No : No
Node No. : A : B
Transcom trunk group : No : No
auto.reserv.by Attendant : No : No
Overflow trunk group No. : No : No
Tone on seizure : Yes : Yes
Private trunk group : No : No
Q931 signal variant : ISDN FRANCE : ISDN FRANCE
Number Of Digits To Send : According to : According to
numbering plan numbering plan
Channel type selection : Channel No. by : Channel No. by
Channel No Channel No
DTMF dialling outgoing call : No (imperative) : No (imperative)
CAUTION!
T2 specificity : Without (imperative) : Without (imperative)
CAUTION!
Public network access category : 0 : 0

====================================================
Object name: Trunk Groups>Trunk Group


$.
     
   , &( ' &  #  ) *# #
 13-5
Chapter 13 , &( ' &  #  ) *# #


Attributes:
SITE : A : B
Trunk Group No. : 54 : 76
Trunk Group Type : T2 : T2
Public network ref. : FA-BComp : FB-AComp
VG for non-existent No. : No : No
Entity No. : 0 : 0
Supervised by Routing : No : No
VPN cost Limit for Incom. Calls : 9 : 9
Immediat Trk Listening for VPN Call : Yes : Yes
VPN TS% : 0 : 0
Csta Monitored : No : No
Max% of trunks out CCD : 0 : 0
Ratio analog to ISDN tax : 0.000 : 0.000
Turn In Access : Yes : Yes
Dialling end to end : No : No
DTMF end to end signal. : No : No
Trunk Group used in DISA : No : No
DISA secret code : ---- : ----
Rerouting to Executive : No : No
Trunk Category Id. : 16 : 16
Nb of digits unused (ISDN) : According to numbering : According to numbering
plan plan
B Channel Choice : Yes : No CAUTION!
Channels Reserved By Attend. : 0 : 0
Dissuasion For ACD : No : No
DTO joining : No : No
Enquiry Call on B-channel : No : No
Automated Attendant : No : No
Calling party - auto attend. category : 0 : 0
TS Overflow : Yes : Yes
Number To Be Added : ----- : -----
Charge Calling And ADN Creation : No : No
Logical Channel : 1_15_17_31 : 1_15_17_31

====================================================
Object name: Trunk Groups>Trunk Group>T0/T1/T2 access
Attributes:

13-6 
$.
     
   , &( ' &  #  ) *# #

, &( ' &  #  ) *# #


SITE : A : B
Trunk Group Id. : 54 : 76
Physical Address : 0-1-0 : 0-2-0
Access Type : Virtual Voice Leased : Virtual Voice Leased
T2 Time Slots : 02222220 00000000 : 02222220 00000000
00000000 00000000 00000000 00000000
Support Time Slot Address : 0-3-0-1 : 0-4-0-1
Release Support Timer (100ms) : 20 : 20
Protection Timer (1min) : 1 : 1

The trunks are then declared automatically.

13.4 Declaring the support trunk group seizure prefix


A trunk group seizure prefix is required to access the compressed trunk group.
Object name: Translator>Prefix Plan
Attributes:
SITE : A : B
Number : 054 : 076
Prefix Meaning : Professional trunk : Professional trunk
group seizure group seizure
Prefix Information : 54 (Trunk group No.) : 76 (Trunk group No.)


$.
     
   , &( ' &  #  ) *# #
 13-7
Chapter 13 , &( ' &  #  ) *# #


13-8 
$.
     
   , &( ' &  #  ) *# #



14       


     ! 

14.1 Introduction
We wish to create a compressed trunk group between two sites A and B connected by a public
network.
Sites A and B are connected to the same public network by trunk groups 42 and 70. The
compressed trunk groups 52 and 71 enable an optimized link between the two sites.

Figure 14.1: Example of optimized link on public network


A PRA board is managed in 0-3 on A and in 0-4 on B. A LIOX board is managed in 0-1 on A
and in 0-2 on B. Virtual access 0 has been chosen for this example.
In the above example, user 3255 of site A will call user 4133 of site B by dialing
0520298144133. He will then use the compressed trunk group connecting the two sites.
In the above example, user 4133 of site B will call user 3255 of site A by dialing
0710155663255.

14.2 Declaring support trunk groups to the public network:

14.2.1 Declaring PRA boards (suuport) and derivatives


Object: Shelf > Board
SITE : A : B
Shelf Address : 0 : 0
Board Address : 3 : 4
Interface Type : PRA : PRA

=============================================
Object: Shelf > Board > ISDN access
Attributes:
SITE : A : B
Shelf Address : 0 : 0


$
     
   , &( ' &  ) *#  & ! ( 14-1
#

Chapter 14 , &( ' &  ) *#  & ! ( #


Board Address : 3 : 4
T0/T2 Access No. : 0 : 0
Access type : T2 : T2
Max Nb of Used B Channels : 30 : 30
Synchronization priority : 255 : 255
Network Mode : No : No CAUTION!
TieLine Mode : No : No
With Alarm : No : No
Reserved1 : Yes : Yes
Reserved2 : Yes : Yes
Network Date Time Update : No : No
CRC4 : No : No

14.2.2 Declaring support trunk groups and derivatives


Object: Trunk Groups
Attributes:
SITE : A : B
Trunk Group Id. : 42 : 70
Trunk Group Type : T2 : T2
Trunk Group Name : Site_A pub net : Site_B pub net
Number Compatible With : 0 : 0
Remote Network : 255 : 255
Shared trunk group : No : No CAUTION!
DDI transcoding : No : No
Transcom trunk group : No : No
auto.reserv.by Attend : No : No
Overflow Trunk Group No. : No : No
Tone on seizure : Yes : Yes
Private Trunk Group : No : No
Q931 signal variant : ISDN FRANCE : ISDN FRANCE
Number Of Digits To Send : (According to : (According to
numbering plan) numbering plan)
Channel type selection : Channel No. by : Channel No. by
Channel No. Channel No.
(imperative) (imperative)
DTMF dialing on outgoing call : no (imperative) : no (imperative)
Compressed : no (imperative) : no (imperative)

=============================================

14-2 
$
     
   , &( ' &  ) *#  & ! (
#

, &( ' &  ) *#  & ! ( #


Object: trunk Groups > trunk group


Attributes:
SITE : A : B
Trunk Group Id. : 42 : 70
Trunk Group Type : T2 : T2
Public network ref. : SiteA-pub net : SiteB-pub net
VG for non-existent No. : Yes : Yes
Entity No. : 0 : 0
Supervised by Routing : No : No
VPN Cost Circuit for Incom. Calls : 9 : 9
Junct. immediate mon. if VPN skip : Yes : Yes
VPN TS% : 0 : 0
Csta Monitored : No : No
Max% of trunks out CCD : 0 : 0
Ratio analog to ISDN tax : 0.000 : 0.000
Turn In Access : Yes : Yes
Dialling end to end : No : No
DTMF end to end signal. : No : No
Trunk Group used in DISA : No : No
DISA secret code : ---- : ----
Rerouting to Executive : No : No
Trunk Category Id. : 16 : 16
Nb of digits unused (ISDN) : 4 : 4
B Channel Choice : No : No CAUTION!
Channels Reserved By Attend. : 0 : 0
Dissuasion For ACD : No : No
DTO joining : No : No
Enquiry Call on B channel : No : No
Automated Attendant : No : No
Calling party Rights category : 0 : 0
TS Overflow : Yes : Yes
Number To Be Added : ----- : -----
Charge Calling And ADN Creation : No : No
Logical Channel : 1_15_17_31 : 1_15_17_31

=============================================
Object: Trunk Groups > Trunk Group > T0/T1/T2 access
Attributes:


$
     
   , &( ' &  ) *#  & ! ( 14-3
#

Chapter 14 , &( ' &  ) *#  & ! ( #


SITE : A : B
Trunk Group Id. : 42 : 70
Time Slots : 01111111 11111111 : 01111111 11111111
01111111 11111111 01111111 11111111

The trunks are then declared automatically.

14.3 Declaring compressed trunk groups

14.3.1 Declaring LIOX compression board


Object: Shelf > Board
SITE : A : B
Shelf Address : 0 : 0
Board Address : 1 : 2
Interface Type : LIOX : LIOX
Use Data Compression : No. : No.
Mutual Aid : Yes. : Yes.
Ident DSP LIO : 8 Compressors. : 8 Compressors (in this
example “Comp2” daughter
boards are used.

14.3.2 Declaring the virtual access


Object name Shelf > Board > Virtual Access
Attributes:
Shelf Address : 0 : 0
Board Address : 1 : 2
T0/T2 access No. : 0 : 0
Access type : Virtual Voice Switched : Virtual Voice Switched
(display)
Network Mode : Yes : No CAUTION!

The other attributes are not to be managed.

14.3.3 Declaring compressed trunk groups and derivatives


Object: Trunk Groups
Attributes:
SITE : A : B
Trunk Group Id. : 52 : 71

14-4 
$
     
   , &( ' &  ) *#  & ! (
#

, &( ' &  ) *#  & ! ( #


Trunk Group Type : T2 : T2


Trunk Group Name : SB/Comp : SA/Comp
Number Compatible With : 0 : 0
Remote Network : Leave the default value : Leave the default value
Shared Trunk Group : No : No CAUTION!
DDI transcoding : No : No
Node No. : A : B
Transcom trunk group : No : No
auto.reserv.by Attendant : No : No
Overflow Trunk Group No. : No : No
Tone on seizure : Yes : Yes
Private Trunk Group : No : No
Q931 signal variant : ISDN FRANCE : ISDN FRANCE
Number Of Digits To Send : According to numbering : According to numbering
plan plan
Channel type selection : Channel No. by : Channel No. by
Channel No. Channel No.
DTMF dialling on outgoing call : No (imperative) : No (imperative)
CAUTION!
Compressed : Compressed : Compressed
(imperative) (imperative) CAUTION!
Public net. access category : 0 : 0

=============================================
Object: Trunk Groups > Trunk Group
Attributes:
SITE : A : B
Trunk Group Id. : 52 : 71
Trunk Group Type : T2 : T2
Public network ref. : SiteA-pub net : SiteB-pub net
VG for non-existent No. : No : No
Entity No. : 0 : 0
Supervised by Routing : No : No
VPN Cost Circuit for Incom. Calls : 9 : 9
Junct. immediate mon. if VPN skip : Yes : Yes
VPN TS% : 0 : 0
Csta Monitored : No : No
Max% of trunks out CCD : 0 : 0
Ratio analog to ISDN tax : 0.000 : 0.000
Turn In Access : Yes : Yes


$
     
   , &( ' &  ) *#  & ! ( 14-5
#

Chapter 14 , &( ' &  ) *#  & ! ( #


Dialling end to end : No : No


DTMF end to end signal. : No : No
Trunk Group used in DISA : No : No
DISA secret code : ---- : ----
Rerouting to Executive : No : No
Trunk Category Id. : 16 : 16
Nb of digits unused (ISDN) : 4 : 4
B Channel Choice : Yes : No CAUTION!
Channels Reserved By Attend. : 0 : 0
Dissuasion For ACD : No : No
DTO joining : No : No
Enquiry Call on B channel : No : No
Automated Attendant : No : No
Calling party Rights category : 0 : 0
TS Overflow : Yes : Yes
Number To Be Added : ----- : -----
Charge Calling And ADN Creation : No : No
Logical Channel : 1_15_17_31 : 1_15_17_31
(consultation only) (consultation only)

=============================================
Object: Trunk Groups > Trunk Group > T0/T2 access
Attributes:
SITE : A : B
Trunk Group No. : 52 : 71
Physical Address : 0-1-0 : 0-2-0
Access type : Virtual Voice Switched : Virtual Voice Switched
Time Slots : 02222220 00000000 : 02222220 00000000
00000000 00000000 00000000 00000000
ISDN Compression Call No. : 0420298142222*71 : 0700155662222*52
Release Support Timer (100ms) : 20 : 20
Protection Timer (1mn) : 1 : 1

The trunks are declared automatically.

14.4 Declaring support trunk group seize prefixes


Object: Translator > Prefix Plan
Attributes:

14-6 
$
     
   , &( ' &  ) *#  & ! (
#

, &( ' &  ) *#  & ! ( #


SITE : A : B
Numbe : 042 : 070
Prefix Meaning : Professional trunk : Professional trunk
group seize group seize
Prefix Information : 42 : 70

14.5 ARS declaration


Object: Translator > Prefix Plan
Attributes:
SITE : A : B
Number : 052 : 071
Prefix Meaning : Professional trunk : Professional trunk
group seize group seize
Discriminator_Id : 52 : 71

=============================================
Object: Translator > External numbering plan > numbering discrimination >
Discriminator_Rule
Attributes:
SITE : A : B
Discriminator id : 0 : 0
Call Number : 015566 : 029814
Numbering Area : 1 : 1
ARS Route List Number : 0 : 0
Schedule Number : -1 : -1
Number of Digits : 30 : 30

=============================================
Object: Translator > Automatic Route Selection > ARS Route List
Attributes:
SITE : A : B
Table No. : 0 : 0
Name : to compr. tr. gr. : to compr. tr. gr.
ARS routing : :
Number : 1 : 1
Name : T2/Comp : T2/Comp
Trunk Group : 52 : 71
Nb. Digits To Be Removed : 6 : 6


$
     
   , &( ' &  ) *#  & ! ( 14-7
#

Chapter 14 , &( ' &  ) *#  & ! ( #


Digits To Add : --- : ---


Dialling Command Tabl.Id. : 0 : 0
VPN Cost Limit : 0 : 0
Protocol Type : According to tr. group : According to tr. group
type type
NPD Identifier : 15 : 15
Route Type : Public type : Public Type
Quality : Speech : Speech

14-8 
$
     
   , &( ' &  ) *#  & ! (
#



15 "       


 ! 

15.1 Introduction
We wish to create a compressed logical link on a leased support between nodes N1 and N2.

Figure 15.1: Example of logical link on a leased B-channel


In the above example, nodes 1 and 2 form an ABC network, the compressed aspect of the
logical link is transparent to users.
A PRA board is managed in 0-3 on node 1 and 0-4 on node 2. A LIOX board is managed in
0-1 on node 1 and in 0-2 on node 2. Virtual access 0 is chosen in this example.

15.2 Declaring the physical support


Declaring the PRA boards (support) and the derivatives:
Object: Shelf > Board
Attributes:
NODE : 1 : 2
Shelf Address : 0 : 0
Board Address : 3 : 4
Interface Type : PRA : PRA

==============================
Object: Shelf > Board > ISDN access
Attributes:
NODE : 1 : 2
Shelf Address : 0 : 0
Board Address : 3 : 4
Access type : T2 : T2
T0/T2 Access No. : 0 : 0


$.
     
   /'# (  #  ) *# #
 15-1
Chapter 15 /'# (  #  ) *# #


Max Nb of Used B Channels : 30 : 30


Synchronization priority : 255 : 255
Network Mode : Yes : No CAUTION!
TieLine Mode : No : No
With Alarm : No : No
Reserved1 : Yes : Yes
Reserved2 : Yes : Yes
Network Date Time Update : No : No
CRC4 : No : No

15.3 Declaring the compressed logical link

15.3.1 Declaring the LIOX board


Object name: Shelf > Board
NODE : 1 : 2
Shelf Address : 0 : 0
Board Address : 1 : 2
Interface Type : LIOX : LIOX
Use Data Compression : No : No
Mutual Aid : Yes : Yes
LIO coupler daughter : 8 Compressers : 8 Compressers
board

15.3.2 Declaring the virtual access


Object name: Shelf > Board - Interface > Virtual Access
Attributes:
NODE : 1 : 2
Shelf Address : 0 : 0
Board Address : 1 : 2
T0/T2 access No. : 0 : 0
Access Type : Virtual Voice Leased : Virtual Voice Leased (display
only)
Network Mode : Yes : No CAUTION!

The other attributes are not to be managed.

15.3.3 Declaring the logical link


Object name: Inter-Nodes Links > Logical Links (ABC-Fx)

15-2 
$.
     
   /'# (  #  ) *# #

/'# (  #  ) *# #


Attributes:
NODE : 1 : 2
Link Name : N1-N2C : N2-N1C
Link Type : Compressed, : Compressed,
Adjacent Node : 2 : 1 CAUTION!
Adjacent Network : 0 : 0
Trunk Category : 18 : 18
B-channel choice : Yes : No CAUTION!
Voice Compression : Yes : Yes
TS Overflow : No : No
Csta Monitored : No : No
Teleservice incidents : No : No
Signal setup mode : Permanent, : Permanent,
Routing type : Dynamic routing, : Dynamic routing,
TS distribution accesses : No, : No (do not modify this
default value)

15.3.4 Declaring the logical link access


Object name: Inter-Nodes Links > Logical Links (ABC-F) > Link Bus Access
Attributes:
NODE : 1 : 2
Link Name : N1-N2C : N2-N1C
Physical Address : 0-1-1 : 0-2-1
Access Type : Virtual Voice Leased : Virtual Voice Leased
Access Id. : 1 : 1 CAUTION
Access Cluster Id. : 3 : 4
Time Slots : 02222220 00000000 : 02222220 00000000
00000000 00000000 00000000 0000000
Support Time Slot Address : 0-3-0-1 (depending on the : 0-4-0-1 (depending on the
number of the leased TS) number of the leased TS)


$.
     
   /'# (  #  ) *# #
 15-3
Chapter 15 /'# (  #  ) *# #


15-4 
$.
     
   /'# (  #  ) *# #



16 "      


     ! 

16.1 Introduction
We wish to create a compressed logical link between two nodes, 1 (site A) and 2 (site B),
linked by a public network.

Figure 16.1: Example of a compressed logical link on public network


In the above example, nodes 1 and 2 form an ABC network, the compressed and virtual
aspect of the logical link is transparent to users.
A PRA board is managed in 0-3 on node 1 and 0-4 on node 2. A LIOX board is managed in
0-1 on node 1 and in 0-2 on node 2. Virtual access 0 is chosen in this example.

16.2 Declaration of access trunk groups to the public network


The declaration of public trunk groups is exactly the same as that described previously for
compressed trunk groups on the public network. This holds true for the trunk seize prefixes.

16.3 Declaration of the compressed logical link

16.3.1 Declaration of the LIOX board


Object name: Shelf > Board
NODE : 1 : 2
Shelf address : 0 : 0
Board address : 1 : 2
Interface type : LIOX : LIOX
Use data compression : No : No
Mutual aid : Yes : Yes
Ident DSP LIO : 8 Compressors : 8 Compressors

16.3.2 Declaration of virtual access


Object name: Shelf > Board > Virtual Access


$
     
   /'# (  ) *#  & ! ( 16-1
#

Chapter 16 /'# (  ) *#  & ! ( #


Attributes:
NODE : 1 : 2
Shelf address : 0 : 0
Board address : 1 : 2
T0/T2 access no. : 1 : 1
Access type : Virtual voice switched : Virtual voice switched
(display)
Network mode : Yes : No CAUTION!

The other attributes are not to be managed.

16.3.3 Declaration of the logical link


Object name: Inter-node link > Logical link (ABC-Fx)
NODE : 1 : 2
Link name : N1-N2C : N2-N1C
Link type : Compressed, : Compressed,
Adjacent node : 2 : 1 CAUTION!
Adjacent network : 0 : 0
trunk category : 18 : 18
B-channel choice : Yes : No CAUTION!
TS overflow : No : No
CSTA monitored : No : No
Teleservice incidents : No : No
Signal Establis. Mode : On request : On request CAUTION!
Routing Type : Static routing : Static routing CAUTION!
TS distribution accesses : No, : No (do not change this
default value)

16.3.4 Declaration of logical link bus access


Object name: Inter-node link > Logical link (ABC-Fx) > Link bus access
Attributes:
NODE : 1 : 2
Link name : N1-N2C : N2-N1C
Physical address : 0-1-0 : 0-2-0
Access type : Virtual voice switched : Virtual voice switched
Access Id. : 1 : 1 CAUTION!
Access cluster Id. : 3 : 4 (managed automatically)

16-2 
$
     
   /'# (  ) *#  & ! (
#

/'# (  ) *#  & ! ( #


Time slots : 02222220 00000000 : 02222220 00000000


00000000 00000000 00000000 0000000
ISDN Compression : 0420298142222 : 0700155662222 CAUTION!
Number


$
     
   /'# (  ) *#  & ! ( 16-3
#

Chapter 16 /'# (  ) *#  & ! ( #


16-4 
$
     
   /'# (  ) *#  & ! (
#



17 #      


        
! 
17.1 Introduction
We want to create a hybrid logical link with two accesses, one on B-channels with
compression, the other on B-channels without compression. The logical link connects nodes
N1 and N2.

Figure 17.1: Example of logical link on leased B-channel


In the above example, nodes 1 and 2 form an ABC network; the hybrid aspect of the logical
link is transparent to users.
AN LIOP board is managed in 0-4 on node 1 and node 2. Virtual access 1 is chosen in this
example.

17.2 Declaring the logical link


Object name: Inter-Nodes Links > Logical Link (ABC-F)
NODE : 1 : 2
Link Name : N1-N2C : N2-N1C
Link Type : Hybrid : Hybrid
Adjacent Node : 2 : 1 CAUTION!
Adjacent Network : 0 : 0
Trunk Category : 18 : 18
B-channel choice : Yes : No CAUTION!
TS Overflow : No : No
Csta Monitored : No : No
Teleservice incidents : No : No
Signal Establis. Mode : Permanent : Permanent CAUTION!
Routing Type : Dynamic : Dynamic CAUTION!
TS Distribution on : No : No CAUTION!
Accesses
Release Support Timer : 10 : 10


$.
     
   0+  '# ( !* # #  #  ) 17-1
*# #

Chapter 17 0+  '# ( !* # #  #  ) *#
#


Protection Timer (1min) : 1 : 1


Multi-access hybrid logical : Yes : Yes
link
Mux : No : No

17.3 Declaring the compressed access with its trunks


Object name: Inter-Nodes Links > Logical Links (ABC-F) > Hybrid Link Access
NODE : 1 : 2
Link Name : N1-N2C : N2-N1C
Access number : 1 : 1
Signalling type : Virtual-Voice-Leased : Virtual-Voice-Leased
Main established tempo : 30 : 30
Has StandBy Signalling : No : No
StandBy Signalling Type : Not used : Not used
Main Trunk Group Id. : 25 : 25 Caution trunk group 2
must not be used
Phys Access for Main : 0-4-1 : 0-4-1
Trunk Group
Support Time Slot Address : 0-4-0-1 : 0-4-0-1

17.4 Declaring the first trunk


Object name: Inter-Nodes Links > Logical Link (ABC-F) > Hybrid Link Access > Trunk
NODE : 1 : 2
Link Name : N1-N2C : N2-N1C
Access number : 1 : 2
Physical Address : 0-4-1-1 : 0-4-1-1
TS No. : 1 : 1
Directory Name : completed by the system : completed by the system
Trunk Routing Number : None : None
Data Transparency : No : No CAUTION!
TrunK Category Id. : 18 : 18
Real Trunk Category Id. : 18 : 18

17.5 Declaring the second trunk


Object name: Inter-Nodes Links > Logical Link (ABC-F) > Hybrid Link Access> Trunk

17-2 
$.
     
   0+  '# ( !* # #  #  )
*# #

0+  '# ( !* # #  #  ) *# #


NODE : 1 : 2
Link Name : N1-N2C : N2-N1C
Access number : 1 : 1
Physical Address : 0-4-1-2 : 0-4-1-2
TS No. : 2 : 2
Directory Name : completed by the system : completed by the system
Trunk Routing Id. : None : None
Data Transparency : No : No CAUTION!
Trunk Category Id. : 18 : 18
Real Trunk Category Id. : 18 : 18

The other trunks are declared in the same way.

17.6 Declaring the non-compressed access with its trunk


Object name: Inter-Nodes Links > Logical Link (ABC-F) > Hybrid Link Access
NODE : 1 : 2
Link Name : N1-N2C : N2-N1C
Access number : 2 : 2
Signalling type : No signalling : No signalling
Main established tempo : 30 : 30
Directory Number : None : None
Has StandBy Signalling : No : No
StandBy Signalling Type : Not used : Not used
Access No. supplied for : 1 : 1
main sig

Object name: Inter-Nodes Links > Logical Link (ABC-F) > Hybrid Link Access> Trunk
NODE : 1 : 2
Link Name : N1-N2C : N2-N1C
Access number : 2 : 2
Physical Address : 0-4-0-2 : 0-4-0-2
TS No. : 1 : 1
Directory Name : Completed by the system : Completed by the system
Trunk Routing Id. : None : None
Data Transparency : No : No CAUTION!
Trunk Category Id. : 18 : 18
Real Trunk Category Id. : 18 : 18


$.
     
   0+  '# ( !* # #  #  ) 17-3
*# #

Chapter 17 0+  '# ( !* # #  #  ) *#
#


17-4 
$.
     
   0+  '# ( !* # #  #  )
*# #



18 $   

18.1 "compvisu" command

18.1.1 Syntax

         

Parameters:
lio: display information concerning the LIO boards,
eqt: display information concerning the LIO equipment only,
all: display information concerning all equipment (LIO equipment or not LIO),
cr cpl: display information on the TSs of a board defined by its ACT No. and its coupler No.,
-r : periodic screen refreshing. When used, this option must be placed at the front of the
options.
All information supplied by the "compvisu" command is information local to the node.

18.1.2 "lio" option


"compvisu lio" example

       
!
     "  #    
    $     % $
     &'(  &'(  &'(

 )  *  #  + ,-,  .'/  0  *')
!

The response to the command "compvisu lio" presents one line per LIO type board declared.
The following details are shown on each line:
"cr" and "cpl": these columns give the ACT and Coupler numbers,
"type": this column gives the LIO board type,
"lio coupler state": This column gives the coupler state, i.e.:
- "IN SERVICE": ready to operate,
- "OUT OF SERVICE": out of service or missing,
- "REGISTERED NOT INITIALISED": the board is being initialised.
Compr: this column gives the ratio of the number of free compressors to the number of
compressors available.
data: this column gives the ratio of the number of free data channels to the number of data
channels available. "no" means that data transmission is not authorized.


$1
     
   2## 18-1
Chapter 18 2##

"mutual_aid": this column gives the ratio of the number of compressors free for mutual aid to
the number of compressors available for mutual aid. "no" means that mutual aid is not
authorized.

18.1.3 "eqt" option


"compvisu eqt" example

       

 0 1 23  .4.
 50% 6 1 5236  5.476
    " 1 84*  #
 5 6 1 5)2))6  5)*)6
 "  1 3)43 5-*69 $ 3:;:  <+=
 0 &
9 ">9  1  :*.9 =*9 ?+9 :*
 

$ 1  "
9 =  . 5.6
 0& 1  $

9 *4
 0@ ' 

 1  ' )  2 ' 2



 0 1 3);  .4.
 50% 6 1 53246  5.436
    " 1 #  #
 5 6 1 5)*)6  5)**6
 "  1 <+=  A8+==*
 0 &
9 ">9  1 :**9 =*9 +9 =*:* 
 

$ 1 0  0
 

$ 1 0  0

 1 
B C$ @C00
 1  +?%%0@):**3*))D*:.
 0@ ' 

 1  ' )  2 ' 2




The response to the "compvisu eqt" command presents a group of lines for each link between
equipment. In this option, only links with equipment concerned by compression are shown.
Each group of lines is separated into two parts:
- the right hand side concerns the initiating equipment
- the left hand side concerns the requested equipment.
Meaning of lines:
"neqt": gives the numbers of the equipment present,
"coupler type": gives the type of the coupler the equipment is declared on,
"(cr-cpl-term)": gives the physical position of the equipment,
"type term": gives the termination type.
If the termination is a set, the set type is given , plus the directory number of the set.
"numfais, typjo, var": If the termination is a trunk group, this line gives the trunk group number,
the trunk type, the signaling used, and the trunk group name.
"compressed": This line indicates whether the equipment uses compression, and if Yes, which
channel is compressed.

18-2 
$1
     
   2##
2##

"TS map=--3-5- (5)": means that channels 2 and 5 of the compression composite TS are busy
and that the equipment uses the 5th position (shown by the "(5)").
"support": This line gives the support type and the ISDN call number for compression.
"nbcomp / compresse": this line is reserved for Alcatel maintenance.

18.1.4 all" option


This option is similar to the previous one, but displays information on all node equipment.

18.1.5 "cr cpl" option


,( 1

     - ,    -  = 8 = ,    " 1 #9 5)*6
   
1 + ,-,
   E
" 1 +9 8
1 )*

 = 1 ) 2 * 4 3 . / ; : 7 2)
 + 1 .47
 =" 1 (          
  1 F G G G G  G H H H H

 = 1 22 2* 24 23 2. 2/ 2; 2: 27 *) *2
 + 1
 =" 1   ( ( ( ( (    
  1 H H F F F F F H H G G

 = 1 ** *4 *3 *. */ *; *: *7 4) 42
 + 1
 =" 1     ( ( $ $ ( (
  1 G G G G F F G GF F

 = =" 1 (  0
$9   '9    $%09 $  $
 =  1 F  0
@ 9   '9 ,   $%09 ?  $ G  &
!

Meaning:
Header:
"Coupler type (0-2)": indicates the coupler type and its position (ACT No. - Board No.),
"Coupler state": indicates the coupler state, identical to the state given with the "compvisu lio"
command,
"Busy": indicates whether the coupler is busy. An LIO coupler is busy if a physical access is
busy or if a virtual access is busy.
"Access": indicates the access(es) busy (physical and virtual accesses). A number or a "-" per
access with the physical accesses first. "0-2--" indicates that access T2 is busy and that virtual
access 2 is busy. This table shows the declaration of virtual accesses made in the
Management chapter.

18.1.6 "cr cpl" Option


$1
     
   2## 18-3
Chapter 18 2##

,( 1 

"


       

 8? 5  8  " ? 06 G "

 ,, 5,C 0 6GGGGGGGGGGGG "

 A, 5
 A 6GGGGGGGGGGGGGGG "

  GGGGGGGGGGGGGGGGGGGGGGGGGG :
 -,GGGGGGGGGGGGGGGGGGGGGGGGGGGGG 0
 #BGGGGGGGGGGGGGGGGGGGGGGGGGGGGG 8 B
 I @ 

0 "GGGGGGGGG I;*4
  
0 GGGGGGGGGGGGGGGGGGGGG 3
  J ? # & = GGGGGGGGGGG 2)  0
 &  K 

>  $ "


 D &  L2 5L26 *)M *))
:))

 D &  L* 5L*6 2)M 2))


3))

 D &  L4 5L46 .M *)


2.)

!

18.2 “trkvisu comp” command


   &  

$ = 0K%I 
0$ # 0K

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+ @  +  G  +$  
5+6  
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
=I :.  %):%  ?+  )  
=I 2).  %2)%+  =*  2  
=I 2:.  %2:%+  +  2  
=I *:.  %*:%  ?+  *  
=I :).  %:)%+  ?+  :   )N*N2 53;36 E1 ):)/3)::
=I :2.  %:2%  +  :   )N.N2 5.776 #E1 )N24N)N*;
=I :*.  %:*%+  ?+  :   )N*N* 53776 E1 ):**37))D7:.
=I :74  %:7%  ?+  :   )N:N) 57*36 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
#O *))* :)  +  = 0%0$ )N)  )N*N3 5.376 E1 ):)*3))) 5-6
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

18-4 
$1
     
   2##

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy