Alcatel OmniPCX Enterprise

INTOF and RT2 Connections

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

 INTOF Connection ................................................................................. 1.1

 RT2 Connection ...................................................................................... 1.1

Chapter 2
Detailed description

 Connecting a Peripheral ACT by INTOF/INTOF2 Boards ......... 2.1

 Connecting a Remote ACT by RT2 Boards ................................... 2.2
 Commissioning ....................................................................................... 2.3
 Duplicating the Inter-ACT Link .......................................................... 2.4
 Reserving B Channels .......................................................................... 2.5

Mixing INTOF/INTOF2 and RT2 ......................................................... 2.5
 Synchronization ...................................................................................... 2.6
 INTOF/INTOF2 Board ................................................................................... 2.6
 RT2 Board .................................................................................................... 2.6
 Tones, Voice Guides, and On-hold Music ..................................... 2.6
 Trunks ........................................................................................................ 2.6
 Attendant ................................................................................................... 2.7
 Voice mail .................................................................................................. 2.7
 Callbacks ................................................................................................... 2.7


  


 0-1

  




Chapter 3
Installation procedure

 Installation Procedure .......................................................................... 3.1

Chapter 4
Configuration procedure

 Principle ..................................................................................................... 4.1

 Reserving B Channels .......................................................................... 4.1
 Declaring the Peripheral ACT ............................................................ 4.1
 Declaring the Peripheral ACT on INTOF .................................................... 4.1
 Declaring the Remote ACT on RT2 ............................................................ 4.2
 Declaring an INTOF or RT2 Board on a Main ACT ..................... 4.2
 Declaring a INTOF/INTOF2 or RT2 Board on a Peripheral ACT
........................................................................................................................ 4.2

Declaring Duplicate Links ................................................................... 4.3
 Consulting Board Status ..................................................................... 4.3

Chapter 5
Maintenance

 Flashing and Downloading Procedure ........................................... 5.1

 Maintenance Commands ..................................................................... 5.1

0-2 
  



 

1 

1.1 INTOF Connection

The INTOF connection is used to connect a main ACT to a peripheral ACT. It has a capacity of
four PCMs (eight Mbps), and its length is limited (depending on the physical support used).

1.2 RT2 Connection

The RT2 connection is used to connect a main ACT to a remote ACT. It has a capacity of one
PCM (maximum of 30 simultaneous communications), and its length is not limited.

     !"# $  %#%& 1-1

Chapter 1 %#%&

1-2      !"# $  %#%&

 

2
  

2.1 Connecting a Peripheral ACT by INTOF/INTOF2 Boards

The INTOF/INTOF2 board enables a main ACT to be connected to a peripheral ACT. The
inter-ACT link is composed of four PCMs (eight Mbps). The length of a link is limited,
depending on the physical support used:
- Copper line: maximum = 600m
- Multimode optic fiber: maximum = 5km
- Monomode optic fiber: maximum = 40km.
The INTOF link is possible behind:
- The main ACT with CPU
- Any other ACT on the INTOF/INTOF2 board, as long as it is behind the main ACT with
CPU.
___change-begin___
___change-end___
Figure 2.1: Peripheral ACTs on INTOF Behind the Main ACT with CPU
- The figure above displays an ACT Media Gateway in the main zone, with an IOIP board
behind Appliance Server. Refer to the module INTOF 4x64kbps signaling - Overview .
___change-begin___
      !"# $  '  #"
2-1
Chapter 2 '  #"

___change-end___
Figure 2.2: Peripheral ACT on INTOF Behind an ACT Media Gateway and Appliance Server

2.2 Connecting a Remote ACT by RT2 Boards

The RT2 board performs a similar function to that of the INTOF/INTOF2 board. However, the
RT2 link allows an unlimited distance (leased or private line with repeaters) between the main
ACT and the remote ACT. In addition, the capacity of this link is weaker (2048 kbit/s T2 type
link [PCM], permitting a maximum of 30 simultaneous communications).
The physical support of the link can be:
- A leased PCM link
- An optic fiber via the TNLO (optical line digital transmitter) board.
The RT2 link is possible behind:
- The main ACT with CPU
- Any other ACT on the INTOF/INTOF2 board, as long as it is behind the main ACT with
CPU.
___change-begin___
2-2       !"# $  '  #"

 '  #"

___change-end___
Figure 2.3: Remote ACT on RT2 Behind the main ACT with CPU
- The figure above displays an ACT Media Gateway in the main zone, behind Appliance
Server.
___change-begin___
___change-end___
Figure 2.4: Remote ACT on RT2 Behind an ACT Media Gateway and Appliance Server

2.3 Commissioning

      !"# $  '  #"

2-3
Chapter 2 '  #"

The inter-ACT link is created using two boards. One is installed in the main shelf and acts as a
coupler (feature A). The other is installed in the peripheral shelf and acts as a CPU (feature B).
The board which has feature A is called INTOF-A (INTOF2-A or RT2-A), and the board which
has feature B is called INTOF-B (INTOF2-B or RT2-B).
The remote ACT is sometimes called URAD.
___change-begin___
___change-end___
Figure 2.5: Main ACT and Peripheral ACT Linked by INTOF

2.4 Duplicating the Inter-ACT Link

___change-begin___
2-4       !"# $  '  #"

 '  #"

___change-end___
Figure 2.6: Principle of the Duplicated Inter-ACT link
For security reasons, the inter-ACT link can be duplicated. Four INTOF (INTOF2 or RT2)
boards are necessary for this. In the peripheral ACT, the boards are situated in the same place
as for the main CPU and the backup CPU.
When both links are valid, the system uses the resources of both connections (the
communication capacity is doubled).
If the link with the board which provides the master CPU feature fails, the other link takes over
and the CPU feature switches over from one link to the other.
The capacity of the INTOF type link can be further increased by adding INTOF pairs declared
as INTOF A on both ACTs.

2.5 Reserving B Channels

The inter-ACT link has two operating modes, either with or without B channel reservation.
- Without B channel reservation:
Signaling is operational even when all B channels are busy.
- With B channel reservation:
Signaling is not operational unless there are free B channels.
The operating mode is defined in configuration.

2.6 Mixing INTOF/INTOF2 and RT2

An INTOF/INTOF2 or RT2 ACT can be installed behind a peripheral INTOF ACT, which is
itself situated behind the main ACT with the CPU.
There are therefore three possible levels of architecture.
___change-begin___
      !"# $  '  #"
2-5
Chapter 2 '  #"

___change-end___
Figure 2.7: Three-Level Architecture
Level 3 peripheral ACTs may not be connected to RT2 ACTs.
Level 4 peripheral ACTs are not possible.
For a configuration with Appliance Server, this type of cascaded connection is not possible.
There can only be two ACT levels.

2.7 Synchronization

2.7.1 INTOF/INTOF2 Board

An INTOF link transports the synchronization signal, either from the main ACT to the
peripheral ACT, or vice versa.
This synchronization is compatible with the DECT/PWT handover. In a DECT/PWT multi-ACT
configuration, the INTOF/INTOF2 board allows DECT/PWT mobiles to benefit from the
handover when they move from one ACT to another (see the module Multi-ACT DECT -
Overview ). In this case, the length of the link is limited to 12km.

2.7.2 RT2 Board

An RT2 link transports the synchronization signal, either from the main ACT to the remote
ACT, or vice versa. The clock extracted from this link is taken into account in the remote ACT
or in the main ACT depending on the "Synchronization priority" which is defined in
configuration.
Caution:
- The transported synchronization on the RT2 link is not compatible with the DECT/PWT han-
dover.
- Some RT2 links may be equipped with TNLs or multiplexers which only transmit the clock
when a call is in progress on this link. The System Administrator must ensure that such links
are not synchronizing. In this case, use synchronization by domain. The RT2 board can gen-
erate the synchronization signal which remains local to the remote ACT.

2.8 Tones, Voice Guides, and On-hold Music

The INTOF/INTOF2 board does not have a tone generator. The tones are transmitted by the
main ACT via the inter-ACT link.
The RT2-B board has its own tone generator for local use on the ACT.
To use the voice guides for the peripheral ACT (INTOF or RT2), a specific board is required
(GPA, VG or Z20-VG). If there is no such board, the guides are replaced by tones.
External music can only be connected to the peripheral ACT via an analog link.

2.9 Trunks
The peripheral ACT can support trunk groups. In this case, subscribers of this ACT use the

2-6       !"# $  '  #"

 '  #"

ACT's local trunk groups as a priority.

When dealing with a multi-level architecture, only the level one and two trunks can be
synchronizing (not permitted for level three trunks).
Only the trunks from the main zone (main ACT or peripheral ACT on INTOF) can support the
ABC links (this is prohibited on remote ACTs connected by RT2 link).

2.10 Attendant
The attendant can be connected either on the main ACT or the peripheral ACT.
Incoming calls to the attendant (in transit on the inter-ACT link) do not reserve channels in call
phase. However, four channels are reserved for incoming calls to the attendant.

2.11 Voice mail

The voice mail can only be in the main ACT, but peripheral ACT subscribers can access it. A
time slot is seized on the inter-ACT link when a peripheral ACT subscriber connects.
If no channels are available to contact the voice mail it is declared Unavailable.

2.12 Callbacks
Automatic callback is only offered if the call fails because the inter-ACT link is saturated.
For groups: callback or camp-on is offered if no group members are available, either because
they are all busy or the inter-ACT link is saturated.
Before making a callback, the system reserves the B channels required. The callback is
deferred if the reservation fails.

      !"# $  '  #"

2-7
Chapter 2 '  #"

2-8       !"# $  '  #"

 

3   

3.1 Installation Procedure

To install the boards, refer to the following:
- module INTOF2 - Installation procedure
- module INTOF - Hardware configuration and module INTOF - External connections
- module RT2-1 - Hardware configuration and module RT2-1 - External connections .
Optic fiber connection is carried out using the COST board, which is placed on the backpanel
behind the INTOF/INTOF2 board. Refer to the module INTOF - COST Board .

 (    !"# $  

  
"#)# 3-1
Chapter 3 
  
"#)#

3-2  (    !"# $  

  
"#)#
 

4  

4.1 Principle
To perform an inter-ACT link, it is necessary to:
- Declare the operation mode of the inter-ACT links of the node (concerning B channel
reservation)
- Declare a peripheral ACT
- Declare an INTOF/INTOF2 or an RT2 board in coupler position in the main ACT
- Declare an INTOF/INTOF2 or an RT2 board in CPU position in the peripheral ACT.

4.2 Reserving B Channels

1. Select: System > Other System Param
2. Review/modify the following attribute:
B channel reservation Determines, for all the inter-ACT links of the node, whether or
not B channels need to be reserved in call phase.

3. Confirm your entry

4.3 Declaring the Peripheral ACT

4.3.1 Declaring the Peripheral ACT on INTOF

1. Select: Shelf
2. Review/modify the following attributes:
Shelf Address Enter the ACT number.
Shelf Type Select the type of shelf. All shelf types are suitable.
ACT Type Select Peripheral ACT Shelf.
Stand By CPU No
Signaling Mode Select the signaling mode used on the inter-ACT link:
N64: signaling is transferred on N channels (speed N*64
kbps)
TS16 (default position): signaling is transferred on TS16.
IO2: signaling is transferred on 4*64kbps (see the module
INTOF 4x64kbps signaling - Overview ).
Note: An IO2N board is recommended (for a CPU on ACT).
Signaling Channel N64 If the Signaling Mode is N64, enter the number of channels
Size used for signaling.

 *    !"# $  

+,)# 
"#)# 4-1
Chapter 4 
+,)# 
"#)#

3. Confirm your entries

4.3.2 Declaring the Remote ACT on RT2

1. Select: Shelf
2. Review/modify the following attributes:
Shelf Address Enter the ACT number.
Shelf Type Select the type of shelf. All shelf types are suitable.
ACT Type Select Peripheral ACT Shelf.
Stand By CPU No
Signaling Mode Select TS16 (default position): signaling is transferred on TS16.
It is the only possible mode for a RT2 type link.
Signaling Channel N64 Not significant.
Size

3. Confirm your entries

4.4 Declaring an INTOF or RT2 Board on a Main ACT

1. Select: Shelf > Board
2. Review/modify the following attributes:
Shelf Address
Board Address
Interface Type
Country Protocol Type
Remote Shelf Address
Remote Board Address
Synchronization Priority
Voice-->Data TS
Enter the main ACT number.
Enter the position of the board (the board must be in coupler
position).
Select: INTOFA or INTOF2A or RT2A.
Not significant
Enter the no. of the ACT at the other end of the inter-ACT link.
Enter the no. of the board at the other end of the inter-ACT
link.
Not significant
Not used.

3. Confirm your entries

4.5 Declaring a INTOF/INTOF2 or RT2 Board on a Peripheral ACT

1. Select: Shelf > Board
2. Review/modify the following attributes:
Shelf Address Enter the peripheral ACT number.
Board Address Enter the position of the board (the board must be in CPU
position).

4-2  *    !"# $  

+,)# 
"#)#
 
+,)# 
"#)#

Interface Type Select: INTOFB or INTOF2B or RT2B.

Country Protocol Type
Remote Shelf Address
Remote Board Address
Synchronization Priority
Voice-->Data TS
Not significant
Enter the no. of the ACT at the other end of the inter-ACT link.
Enter the position of the board at the other end of the
inter-ACT link.
To be filled in when using synchronization domains, when the
RT2 board is synchronizing for the remote ACT.
Not used.

3. Confirm your entries

4.6 Declaring Duplicate Links

The two boards on the main ACT as well as on the peripheral ACT must be defined without
making any specific declaration. The system understands whether a main link or a backup link
is used.

4.7 Consulting Board Status

This function allows the System Administrator to determine the status of the boards.
1. Select: Shelf > Board
2. Review/modify the following attributes:
Shelf Address Enter the ACT no.
Board Address Enter the board position.
Interface Type INTOFA, INTOF2A, RT2A,, INTOFB,, INTOF2B or RT2B,
depending on the case.
Usage State Not significant
Operational State Enabled or Disabled depending on the case.
Main/Standby State Main (Master) or Standby (Slave) depending on the case.
Caution: On duplicated links:
In the main ACT, both boards are always seen as Main
(Master) boards.
In the peripheral ACT, only the board which acts as the
main CPU is seen as the Main (Master) board. The other
board is seen as a Standby (Slave).

3. Confirm your entries

 *    !"# $  

+,)# 
"#)# 4-3
Chapter 4 
+,)# 
"#)#

4-4  *    !"# $  

+,)# 
"#)#
 

5 

5.1 Flashing and Downloading Procedure

The INTOF and RT2 boards use, respectively, binintof and binrt2" software which is installed
in the flash memory. When the version is upgraded or in case of accidental destruction, new
software is downloaded from the CPU (whatever the position of the board).
The download is performed automatically.
To perform a download, the board has a boot in the flash memory. This is deleted when the
flash memory is reset to zero (it is impossible to perform a partial reset of the flash memory). It
is restored by the download. However, if a reset occurs during this short period in time, the
boot is lost. It must therefore be restored.
Boot Recovery Procedure
When the boot is lost, it may be recovered by inserting the specific EPROM in the dedicated
motherboard connector.
It is also necessary to position the jumpers in "boot on EPROM" position:
- Jumper X17 on the INTOF board (see the module INTOF - Hardware configuration )
- Jumpers X13/X15 on the RT2 (see the module RT2-1 - Hardware configuration ).
Afterwards, insert the board into the shelf and the boot will automatically duplicate itself.

5.2 Maintenance Commands

The standard maintenance commands are available on the INTOF/INTOF2 and RT2 boards.

 (    !"# $  - 



 5-1
Chapter 5 - 




5-2  (    !"# $  -