You are on page 1of 22

Alcatel OmniPCX Enterprise

S0 Sets and Terminals


NOTE:

Product specifications contained in this document are subject to change


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

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

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

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

 

 
 


Chapter 1
Overview

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


 Information on the S0 bus ................................................................... 1.2
 Overview ....................................................................................................... 1.2
 Incoming calls on the S0 bus ..................................................................... 1.2
 Outgoing calls on the S0 bus ..................................................................... 1.3
 Support and teleservice ....................................................................... 1.3
 Support (media) compatibility .................................................................... 1.3
 Teleservice ................................................................................................... 1.4
 Multi B channel terminals ........................................................................... 1.4
 S0 bus forwarding .................................................................................. 1.5
 Related modules ..................................................................................... 1.6

Chapter 2
Installation procedure

 Connection ............................................................................................... 2.1


 Connection maximum length ............................................................. 2.1
 Specific features .......................................................................................... 2.2
 Known cables .............................................................................................. 2.2
 Other cable ................................................................................................... 2.3

 
 
 0-1
 
 


Chapter 3
Configuration procedure

 Implementation ....................................................................................... 3.1


 S0 bus behind a UA set ........................................................................ 3.1
 Object organization ..................................................................................... 3.1
 Creating the board that supports the UA link ........................................... 3.1
 Creating the UA set ..................................................................................... 3.1
 Creating the S0 bus ..................................................................................... 3.2
 Declaring the S0 set(s) ................................................................................ 3.3
 Teleservice compatibility tables ................................................................ 3.4
 S0 bus behind a TA ............................................................................... 3.5
 Object organization ..................................................................................... 3.5
 Teleservice compatibility tables ................................................................ 3.6
 Native S0 bus ........................................................................................... 3.6
 Object organization ..................................................................................... 3.6
 Creating the board that supports the S0 link ............................................ 3.7
 Creating the S0 bus ..................................................................................... 3.7
 Declaring the S0 set .................................................................................... 3.7
 Teleservice compatibility tables ................................................................ 3.8

0-2  
 

 

1 

1.1 Overview
S0 sets and S0 terminals are standard digital transmission equipment. They are connected to
a standard S0 bus.
Example of S0 devices that can be connected to an S0 bus:
- S0 sets.
- Group IV fax machines.
- Video sets.
- PC equipped with an S0 board (specific information on connection of these devices is
given in the "Data communication" manual).
There are several possible configurations for connection of an S0 bus to the OmniPCX
Enterprise:
- Native S0 bus.

Figure 1.1: S0 sets connected to a native S0 bus


The bus is connected to the PCX by an ACT BRA or BPRA board.
- TA CTI S0. In this configuration, the S0 bus is connected to the system via the TA-CTI-S0
4094.

Figure 1.2: S0 sets and terminals connected via a TA

          1-1


Chapter 1  

Note 1: The Terminal Adapter used is the TA-CTI-S0 (4094) configured as “Stand alone”.
- TA-CTI-S0 associated with a UA set. In this configuration, the S0 bus is connected to the
system by the TA-CTI-S0 4094 also supporting an S0 set.

Figure 1.3: S0 sets and terminals connected via a UA set

Note 2: The Terminal Adapter used is the TA-CTI-S0 (4094) configured with “Associated UA set”.

1.2 Information on the S0 bus

1.2.1 Overview
A S0 bus is composed of three channels:
- Two 64-Kbit B channels for communication.
- One 16-Kbit channel for signaling.
An S0 bus thus allows two calls to be handled simultaneously.
An S0 bus may be "supplying" (supply power) or not. It is "supplying" when it supplies power to
the terminal(s) it supports. The power transmitted on the bus is limited to 4 Watts and, in
practice, is only suitable for S0 sets. Other devices require a local mains power supply.
Electrical power is transmitted by a DC voltage (48V) on the bus cables.
The length of the bus and arrangement of devices on the bus must comply with the installation
instructions.

1.2.2 Incoming calls on the S0 bus


The PCX controlling the S0 bus sends a call setup request for a determined address. The
set(s) programmed to answer the call start to ring. In the case of multiple ringing, the first set to
unhook takes the call.
Sets can be programmed to answer:
- All call requests sent on the bus.
- A specific address.
- A specific address plus a sub-address.

1-2          


 

It is the manager's responsibility to program each set.


Sub-address:
A sub-address allows the same user (declared on the PCX) to have several physical sets.
Each of these sets may be called separately. The sub-address is internal data on each set, the
PCX does not know the different possible sub-addresses.
To call a set with a sub-address, the '*' character must be added between the address and the
sub-address.
Example: To call set 4000 with sub-address 10, dial: 4000*10# (the '#' indicates end of dialing).

1.2.3 Outgoing calls on the S0 bus


For outgoing calls, each S0 set (or S0 terminal) that wants to make a call sends a call request
via the bus. This call request may include the set identifier. S0 set identifier is the number
programmed for the set by the manager.
There are two cases:
- The PCX has a user matching the identifier received. The call is then identified and the
PCX transmits the call request according to user rights. Accounting records for the call are
then assigned to this user.
- The PCX does not have a matching user for the identifier received or no identifier is
received. The PCX then transmits the call on the "Default user" account. These user
rights are used for call routing. Accounting records are assigned to the "default user". If
there is no "default user", the call is refused.

1.3 Support and teleservice


These two characteristics allow the setup of calls between incompatible terminals to be barred.
For example, a voice set must not be able to call a fax machine.

1.3.1 Support (media) compatibility


There are three types of support (media):
- "Voice" for voice sets.
- "3.7 KHz audio" for Group 3 fax machines.
- "Data" for PCs, videophones, and Group 4 fax machines.
The type of support/medium is given in the call setup message. For incoming calls, the PCX
checks that the support requested is compatible with that of the destination set.
There are several different cases:
- The destination set is a UA or Z set, only "Voice" or 3.1 Khz audio supports are accepted.
- The destination set is a data terminal, only "Data" supports are accepted.
- The destination set is external to the PCX, the call is sent and accepted or refused by the
destination network.
- The destination set is an S0 bus, the call is sent on the bus and accepted or refused by the
destination set or terminal.

          1-3


Chapter 1  

The PCX implicitly recognizes (there is no support parameter in user data) the support of each
device according to device type:
- A "User" type subscriber corresponds to a telephone set and thus a "Voice" or 3.1KHz
audio support.
- A "Data terminal" type subscriber corresponds to a PC and thus a "Data" support.
Set and terminals on an S0 bus explicitly declare the requested support in the call request.

1.3.2 Teleservice
The teleservice is a user parameter for each device.
The teleservice is part of the setup request:
- For outgoing calls:
The S0 set or terminal specifies the desired teleservice in its call setup request. Before
transmitting this call, the PCX checks that the request is compatible with the requested user.
Compatibility between teleservices is configured by the manager for the entire PCX in
compatibility tables.
- For incoming calls:
The PCX checks whether the teleservice received by the call setup message is compatible
with the teleservice declared for the user. If this is not the case, the system refuses the call.

1.3.3 Multi B channel terminals


Some terminals, such as videophones or PCs for example, require several B channels for their
application to operate. Two B channels are generally sufficient, however, some videophones
require up to six B channels (three S0 buses).
The operating mode of this type of terminal may be summarized as follows:
- The caller sets up an initial call on two B channels of an access.
- When required, the called party sends a request for setup of an additional channel
(specifying destination address) to the caller.
- The caller sets up the additional channel. The address used for the additional channel is
the address of the initial call modified, on the least significant digits, by the address of the
additional channel.
Information on address modification:
Example 1:
- The main address of the videophone is 0155667100.
- The address sent by the called videophone for the additional channel is 7101,
- The additional channel address seen by the calling device is 0155667101.
This procedure offers the following advantages:
- The calling device only needs to know a single address; the device called knows the
addresses of its additional channels.
- If there is no DID translation, internal and external calls can be made without
reprogramming the videophone.

1-4          


 

If there is no DID translation:


If a 6-channel videophone has internal addresses 7100, 7101 and 7102 and the company can
be called on 015568xxxx, the following numbers must be programmed on the videophone
called:
- 7100 for the first S0 bus (2 channels).
- 7101 for the second S0 bus (2 channels).
- 7102 for the third S0 bus (2 channels).
An internal caller dials 7100 for the first call, then the modification mechanism (described
above) dials 7101 for the second call and 7102 for the third call.
An external caller dials 0155687100 for the first call, then the modification mechanism
(described above) dials 0155687101 for the second call and 0155687102 for the third call.
If there is DID translation:
Example 2:
- The internal addresses of a 6-channel videophone are 65300, 65301 and 65302.
- The company can be called on 015568xxxx.
- DID translation converts xxxx (external number) to 6xxxx (internal number).
The external call number of the videophone is therefore 0155685300.
The following numbers must be programmed on the videophone called:
- 5300 for the first S0 bus (2 channels).
- 5301 for the second S0 bus (2 channels).
- 5302 for the third S0 bus (2 channels).
An external caller dials 0155685300 for the first call, then the modification mechanism
(described above) dials 0155685301 for the second call and 0155685302 for the third call.
Following DID translation, the PCX sends call setup requests for addresses 65300, 65301, and
65302 on the S0 bus. If the videophone is programmed to answer all addresses, the calls are
accepted.

Figure 1.4: Videophone and PCX programming with DID translation


Note that, with DID translation, with the same videophone programming, operation for internal
and external calls is not ensured.

1.4 S0 bus forwarding

          1-5


Chapter 1  

A user (subscriber) can program immediate forwarding of the bus to which he is connected
from his set or terminal. All calls to the bus are then redirected to the specified number if the
supports or teleservices are compatible. If forwarding is to a user with an incompatible support
or teleservice, the call is refused.
S0 bus forwarding rights are granted in the "Telephone features COS" for the bus.

1.5 Related modules


S0 sets and terminals are documented in the following modules:
- Installation (see the module S0 sets and terminals - Installation procedure ).
- Management (see the module S0 sets and terminals - Configuration procedure ).

1-6          


 

2
  

2.1 Connection
S0 buses are connected with RJ45 connectors. A line termination resistance R=100 Ohms is
necessary.

Figure 2.1: Termination resistance


The S0 bus termination resistance is made of two resistances (100 Ohms - ½ W - 5 %) located
on the last bus female plug. The resistances are connected between RxA and RxB wires on
one hand and between TxA and TxB on the other hand.
The bus head is a male RJ45 connector.
Pinouts:
Pin number PCX side Set side Power supply
polarity
1 Unused Unused
2 Unused Unused
3 RxA Rx Tx +
4 TxA Tx Rx +
5 TxB Tx Rx -
6 RxB Rx Tx -
7 Unused Unused
8 Unused Unused

2.2 Connection maximum length

         !


  "
 "# $  2-1
Chapter 2 !
  "
 "# $ 

2.2.1 Specific features


S0 links or bus can be of different types:
- point-to-point link:

d1 is the maximum distance of the point-to-point line.


- short passive bus:

d2 is the maximum distance of the short bus.


- extended passive bus:

d3 is the maximum distance for the set grouping (all the sets must be grouped within the
d3 interval),
d4 is the maximum distance of the extended bus.

2.2.2 Known cables


The following table gives the maximum length in relation with the cable type:
Provider cable type diameter d1 (m) d2 (m) d3 (m) d4 (m)
(mm)
Alcatel Cables
1AC 0079 (SYT 0,5 670 170 40 440
0.5 @ 700 kHz)
ACS multipair with 0,5 750 170 40 500
overall foil
ACS multipair with 0,5 750 170 40 570
overall foil

2-2          !


  "
 "# $ 
!
  "
 "# $ 

Provider cable type diameter d1 (m) d2 (m) d3 (m) d4 (m)


(mm)
French Telco
Cables9
SYT 0.5 0,5 600 170 40 400
L121- type 278 0,6 400 170 40 270

Cables data:
Provider cable type diameter A sys (dB/km) delay (us/km)
(mm) at 96 kHz
Alcatel Cables
1AC 0079 (SYT 0.5 @ 0,5 9 6
700kHz)
ACS multipair with 0,5 8 6
overall foil
ACS multipair with 0,5 7 6
overall foil
French Telco
Cables
SYT 0.5 0,5 10 6
L121- type 278 0,6 15 6

2.2.3 Other cable


See module Connection maximum length - S0 link - S0 links .

         !


  "
 "# $  2-3
Chapter 2 !
  "
 "# $ 

2-4          !


  "
 "# $ 
 

3    

3.1 Implementation
Implementation of S0 sets depends on the type of connection selected (S0 bus "behind" a UA
or TA set or "behind" a BRA2 or BPRA2 board).
Implementing S0 terminals consists in:
- Declaring the S0 bus to which the S0 sets are to be connected.
- Declaring the S0 sets.
- Programming the S0 terminals (see the specific terminal documentation).
It may also be useful to check or modify teleservice compatibility.

3.2 S0 bus behind a UA set


In this case, the TA must be configured as "with associated UA set”, see the module
TA-CTI-S0 (4094) - Hardware configuration .

3.2.1 Object organization

Figure 3.1: Object organization for an S0 bus behind a UA set

3.2.2 Creating the board that supports the UA link


Creation of a UA board with no "S0" feature.

3.2.3 Creating the UA set

        %"


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

Object name: Users.


Attributes:
Directory Number : Enter the directory number of the UA set.
Shelf Address : Enter shelf number.
Board Address : Enter the number of the UA board.
Equipment Address : Enter the number of the equipment/device that
supports the UA set.
Set Type : Select the type of UA set used.
.......... :
S0 Extension : Yes.

The other parameters of this object are not S0 specific.

3.2.4 Creating the S0 bus


Object name: Shelf > Board > S0 Bus
Attributes:
Shelf Address : Enter shelf number.
Board Address : Enter the number of the UA board that supports
the UA user/subscriber.
Equipment Address : Enter the number of the UA set equipment that
supports the S0 bus.
Protocol Type : Select S0 bus terminal protocol:
- VN2: all users of this bus use VN2 protocol
- VN3: all users of this bus use VN3 protocol
- VN4: all users of this bus use VN4 protocol
- ETSI: all users of this bus use ETSI
protocol
Long Passive Bus : Yes: for any of the following cases:
- several sets (5 max.) distributed along a
bus no more than 150m long.
- several sets (5 max.) distributed at the end
of a bus no more than 500m long.
- a single set installed at the end of a bus no
more than 1500m long.
Permanent Layer 1 : - Yes: layer 1 (physical) is permanently set
up.
- No: layer 1 is only set up during calls.
Note 1: See note (below).
S0_FV : - Yes: for Germany only.
- No: standard for other countries.

3-2         %"


&$ "
 "# $ 
%"
&$ "
 "# $ 

Tel. Features COS ID : Enter the number of the "Telephone features


COS" associated with the bus. In this Class of
Service, only the "Immediate forward" and
"Forward cancellation" fields are used. The
other fields are not significant.
Default No. : Enter default user/subscriber number. Default
number is unique.

Caution: After the S0 bus has been created, the UA board must be reset using the 
command to apply changes.

Note 2: Additional information on permanent layer 1:


In all cases, layer 1 is not set up at system startup. It is set up when the first call is made, but
with an important difference compared to S0 behind BRA2 and BPRA2 boards.
On BRA2 and BPRA2 boards, layer 1 is permanent once it has been activated by a request
from an S0 terminal initiating an outgoing call or by the system when an incoming call to the
S0 terminal is received. In both cases, layer 1 remains active until the S0 terminal is physically
disconnected. Even if layer 2 is disconnected, layer 1 remains active.
On TA CTI-S0 (4094) , layer 1 is activated as above but does only remains permanantly active
if an incoming call to the S0 terminal is received. If activated by an outgoing call from an S0
terminal, layer 1 does not remain active when layer 2 is disconnected. The solution to maintain
permanent layer 1 is to either maintain layer 2, or to make a call to the S0 bus (the call does
not need to be set up).

3.2.5 Declaring the S0 set(s)


Object name: Users.
Attributes:
Directory Number : Enter the directory number of the S0 set.
Shelf Address : Enter shelf number.
Board Address : Enter the number of the UA board.
Equipment Address : Enter the number of the UA set equipment that
supports the S0 bus.
Set Type : Select: S0 Set.
.......... :
ISDN Teleservice : Select the appropriate teleservice for the
user/subscriber.
.......... :
SO Feature :
User By Default : Yes: this set is the default user.
No: this set is not the default user.
Sub-address Use : Yes: UA or analog sets must dial a sub-address
to reach this user.
No: User number is direct.

        %"


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

3.2.6 Teleservice compatibility tables


Object name: Specific Telephone Services
Attributes:
Phone Compatibility :
Phone : 1: a call request with a "Phone" teleservice is
compatible with a called "Phone" teleservice.
0: not compatible.
Fax Group 3 : 1: a call request with a "Fax Group 3 "
teleservice is compatible with a called "Phone"
teleservice.
0: not compatible.
Mixed Teletex : Idem.
Fax Group 4 : Idem.
Teletex character : Idem.
Videotex Mosaic : Idem.
Videotex Inter : Idem.
NPI/TON: Telex : Idem.
Msg.Handler Syst.(X400) : Idem.
ISO Application : Idem.
Audiovisual : Idem.
Unknown Teleservice : Idem.
Audiography : Idem.
Audio-videotex : Idem.
Non-standard Application : Idem.
Teletex Base : Idem.
Reserved Maintenance : Idem.
Reserved System : Idem.
:
Fax Group 3 Compatibility : Idem "Phone" teleservice.
Mixed Teletex Compatibility : Idem "Phone" teleservice.
Fax Group 4 Compatibility : Idem "Phone" teleservice.
Teletex Char Compatibility : Idem "Phone" teleservice.
Videotex Mosaic Compatibility : Idem "Phone" teleservice.
Telex Compatibility : Idem "Phone" teleservice.
STM Compatibility : Idem "Phone" teleservice.
Appli ISO Compatibility : Idem "Phone" teleservice.
Unknown Teleservice : Idem "Phone" teleservice.
Compatibility
Audiography Compatibility : Idem "Phone" teleservice.

3-4         %"


&$ "
 "# $ 
%"
&$ "
 "# $ 

AudioVideotex Compatibility : Idem "Phone" teleservice.


Non-standard appli.Compatibility : Idem "Phone" teleservice.

The modification of the compatibility tables is reserved to Alcatel support.

3.3 S0 bus behind a TA


In this case, the TA must be configured as "Stand alone”, see the module TA-CTI-S0 (4094) -
Hardware configuration .

3.3.1 Object organization

Figure 3.2: Object organization with an S0 bus behind a TA

3.3.1.1 Creating the interface board that supports the UA link


Creation of a UA board with no "S0" feature.
3.3.1.2 Creating the TA
The terminal adaptor connects to a UA link behind a UA board.
Object name: Shelf > Board > TA adaptor
Attributes:
Shelf Address : Enter shelf number.
Board Address : Enter the number of the UA board.
Equipment Address : Enter the number of the equipment which
supports the TA.

        %"


&$ "
 "# $  3-5
Chapter 3 %"
&$ "
 "# $ 

S0 Adapter : Yes.

The other parameters of this object are not "S0" specific.


3.3.1.3 Creating the S0 bus
Object name: Shelf > Board > S0 Bus
Attributes:
Shelf Address : Enter shelf number.
Board Address : Enter the number of the UA board which
supports the TA.
Equipment Address : Enter the number of the equipment which
supports the TA.

For the other parameters, see "S0 bus behind UA set" ( § Creating the S0 bus ).
3.3.1.4 Declaring the S0 set(s)
Object name: Users.
Attributes:
Directory Number : Enter the directory number of the S0 set.
Shelf Address : Enter the shelf number of the TA which
supports the S0 bus.
Board Address : Enter the board number of the TA which
supports the S0 bus.
Equipment Address : Enter the equipment number of the TA which
supports the S0 bus.

For the other parameters, see "S0 bus behind UA set" ( § Declaring the S0 set(s) ).

3.3.2 Teleservice compatibility tables


See § Teleservice compatibility tables .

3.4 Native S0 bus

3.4.1 Object organization

3-6         %"


&$ "
 "# $ 
%"
&$ "
 "# $ 

Figure 3.3: Object organization for a native S0 bus

3.4.2 Creating the board that supports the S0 link


Object name: Shelf > Board
Attributes:
Shelf Address : Enter shelf number.
Board Address : Enter the position of the board in the shelf.
Interface Type : Select BRA or BPRA according to the board used.

3.4.3 Creating the S0 bus


Object name: Shelf > Board > S0 Bus
Attributes:
Shelf Address : Enter the number for the shelf that supports the S0 bus
Board Address : Enter the number of the board that supports the S0 bus.
Equipment Address : Enter the number of the equipment that suppports the
S0 bus.

For the other parameters, see "S0 bus behind UA set" ( § Creating the S0 bus ).
Caution: After the bus has been created, the BRA or BPRA board must be reset with the "rstcpl"
command for changes to be applied.

3.4.4 Declaring the S0 set


Object name: Users
Attributes:

        %"


&$ "
 "# $  3-7
Chapter 3 %"
&$ "
 "# $ 

Directory Number : Enter the directory number of the S0 set.


Shelf Address : Enter the number for the shelf that supports the S0 bus
Board Address : Enter the number of the board that supports the S0 bus.
Equipment Address : Enter the number of the equipment that suppports the
S0 bus.

For the other parameters, see "S0 bus behind UA set" ( § Declaring the S0 set(s) ).

3.4.5 Teleservice compatibility tables


See § Teleservice compatibility tables .

3-8         %"


&$ "
 "# $ 

You might also like