Alcatel OmniPCX Enterprise

Radio Interphony Link

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
Detailed description

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

 Ergonomic factors ................................................................................. 1.2
 Single and multi-channel modes ...................................................... 1.3
 Activity detection ................................................................................... 1.4
 Network operation ................................................................................. 1.4

Activating the service ........................................................................... 1.4
 Interoperation .......................................................................................... 1.5
 Direct routing on off-hook .......................................................................... 1.5
 Substitution (Replacement) ........................................................................ 1.5
 Three party conference ............................................................................... 1.5
 Automatic callback on busy trunk group .................................................. 1.5
 PBX groups .................................................................................................. 1.5

Guide mode .................................................................................................. 1.5
 Voice Mail ..................................................................................................... 1.6
 Manager/assistant groups .......................................................................... 1.6
 Mail services ................................................................................................ 1.6
 DECT ............................................................................................................. 1.6
 IP-Phones ..................................................................................................... 1.6
 Mastered conference ................................................................................... 1.6


 
 
 0-1

 
 


Chapter 2
Configuration procedure

 System parameters ................................................................................ 2.1

 Timers ......................................................................................................... 2.2
 Creating the prefix ................................................................................. 2.3
 Managing users ...................................................................................... 2.3
 Managing the set ......................................................................................... 2.3
 Phone facilities categories ......................................................................... 2.3
 Managing monitoring circuits on a GPA board ........................... 2.4

Managing profiles .................................................................................. 2.4

 Intercom profiles ......................................................................................... 2.5

 Intercom lists ............................................................................................... 2.5
 Managing radio channels .................................................................... 2.5
 Trunk seize prefix ........................................................................................ 2.5
 Managing trunk category ............................................................................ 2.6
 Creating a trunk group ................................................................................ 2.6
 Radio server ............................................................................................. 2.7
 Creation ........................................................................................................ 2.7
 Modifying and removing a server .............................................................. 2.7
 Managing conference circuits on GPA boards ......................................... 2.7
 Managing CMP boards ......................................................................... 2.8

Chapter 3
Maintenance

 CPU switchover ...................................................................................... 3.1

 Radio server ............................................................................................. 3.1
 Not enough monitoring circuits ........................................................ 3.1

0-2 
 
 

 
 
 


 List of incidents ...................................................................................... 3.1

Chapter 4
Operation

 Activating the service ........................................................................... 4.1

 Activating radio channels ................................................................... 4.2
 Activating a channel in monitoring mode. ................................................ 4.3
 Speaking ....................................................................................................... 4.4
 Disconnecting from a channel ................................................................... 4.5
 Interaction between channels .................................................................... 4.5
 Interaction between point-to-point calls and channels ............ 4.6
 Subscriber in monitoring mode ................................................................. 4.6
 Subscriber in traffic mode .......................................................................... 4.6
 Overview of point-to-point calls ................................................................. 4.8
 Point-to-point call release ........................................................................... 4.9


 
 
 0-3

 
 


0-4 
 
 

 

1  

 

Caution: This topic has not been updated for OmniPCX Enterprise as neither the operating
principle or implementation has been significantly modified.

1.1 Overview
The radio intercom service allows several users located on the same ABC network and
grouped on a loop (radio server), to communicate with an external radio channel.
The radio intercom service enables a user to:
- activate permanent monitoring on the channel(s) he subscribes to: he then hears all
channel activity and users speaking on the channel, but is not heard,
- view, via a pictogram, loops on which there is voice activity (voice activity on the radio
channel or a connected user speaking),
- speak on a channel,
- make or receive point-to-point calls (calls other than the radio channel link).
The user must have a 4035 or 4037 (IP-Phone) type set declared as multiline, either with or
without an extension keypad. The handset of a 4035 set may be equipped with a PTT (Push
To Talk) button, used to speak on a channel. In this case, the set must be equipped with an
adapter. On 4035 sets with no PTT button and on 4037 sets, the “Secret” button of the set is
used to speak.
When he activates the service, the user selects one of the profiles defined in the list allocated
to him in his subscription parameters. He can then connect to the channels given in this profile.
A profile can contain up to 27 channels.
Point-to-point calls are made using the multiline keys. A user can make or receive a
point-to-point call with monitoring activated on one or more channels. However, he cannot
speak on a channel at the same time.
To activate radio channels, the user uses a monitoring circuit. This is connected to the radio
servers and ensures mixing of calls from the different servers and any point-to-point call. The
monitoring circuit is supported by a GPA board DSP belonging to the same node as the user.
The radio server (that ensures radio channel connection to the monitoring circuits of the
different users on-line) is also supported by a GPA board DSP belonging to the node on which
the radio server is declared.
Radio channels are supported by EMTL board trunks.

    !   " #$ 

1-1
Chapter 1 " #$ 

A flow separation system parameter enables users with a 4035 set (when not in hands-free
mode) to hear:
- in the handset, the point-to-point conversation or the traffic mode loop.
- from the loudspeaker, monitored loops.
Another system parameter enables users, when speaking on a loop, to no longer hear the
other loops.
Note: These two parameters cannot be used with 4037 sets: flow separation is only possible on 4035
sets.

1.2 Ergonomic factors

Each channel has a corresponding pair of keys: a "monitoring" key and a "traffic" key. The
number of key pairs available for interphony (the intercom) depends on whether there is an
extension keypad or not (if the set has an extension keypad, only the keys of this keypad are
used for channel monitoring):
- 4035 set with no extension keypad: 6 pairs (provided that the first 12 set keys are
programmable keys),

1-2     !   " #$ 

 " #$ 

- 4035 set with 20-key extension keypad: the 10 pairs of the extension keypad (if they are
programmable keys),
- 4035 set with 40-key extension keypad: the 20 pairs of the extension keypad (if they are
programmable keys),
- 4035 set with 60-key extension keypad: the first 27 pairs of the extension keypad (if they
are programmable keys).
If the set profile has less channels than there are key pairs available, only some keys are used
for channel monitoring. Keys located after the last loop keep their initial configuration as
programmable keys.

1.3 Single and multi-channel modes

The service can operate in two modes: single or multi-channel mode
In single channel mode, a trunk gives access to a single radio channel.
In multi-channel mode, a trunk allows several radio channels to be accessed. In this case, the
user first connects to a radio server by pressing the corresponding monitoring key, then
selects the channel by entering his number (1 or 2 digits, depending on the management
parameter) on the set's numeric keypad .

    !   " #$ 

1-3
Chapter 1 " #$ 

Multi-channel mode is exclusive: when a user activates traffic mode on a channel, other users
can only monitor this channel: they cannot switch to traffic mode or switch to monitoring mode
on another channel.
Example: If user A activates monitoring on channel 1, user B can activate monitoring on channel 1 but
cannot activate traffic mode on this channel. Neither can he activate monitoring on channels 2 or 3.
To avoid a user blocking access to a channel, he is automatically switched to monitoring mode
if he has not spoken for a certain time. This time is set in management.
Single or multi-channel mode is selected in trunk management.

1.4 Activity detection

To simplify simultaneous management of several channels, a pictogram allows users to see
voice activity on each radio loop.
Activity is detected by the CMP board. This board has 32 equipments. On the PBX side, it is
seen as a UA 32 board.
Each server uses two board equipments to monitor activity. The first, with a number 'n',
between 0 and 14, is connected to the radio server and permanently analyzed. When activity
is detected on the server, the board generates a call from the second equipment, number
n+15. This is monitored by channel subscribers. When this equipment is busy (i.e. there is
activity on the server), a pictogram is displayed on the sets.

1.5 Network operation

The radio server, GPA board circuit, radio channel and CMP board must be declared on the
same node.
Radio channel subscribers can be located on one of the ABC network nodes.
A user uses a monitoring circuit of the same node.

1.6 Activating the service

Depending on user settings, activation mode can be:

1-4     !   " #$ 

 " #$ 

- implicit: the service is activated when the set is started up,

- explicit: the service is activated by dialing a prefix.
When the service is activated, the system checks that:
- the user has service rights (telephone facilities category + user parameter),
- the user has a multiline 4035 or 4037 set with intercom keys that are programmable keys,
- the user has a list of profiles,
- the first profile in the list has a number of channels that does not exceed the number of key
pairs available on the set,
- a monitoring circuit is available on a GPA board of the same node.
When activating the service, the first profile in the list is activated by default. The user can
subsequently select another profile.

1.7 Interoperation

1.7.1 Direct routing on off-hook

Direct routing on off-hook can only be performed if the set is in the idle state.
If the set is monitoring a loop, off hooking the handset results in hands-free mode switching to
handset mode.

1.7.2 Substitution (Replacement)

The radio intercom service cannot be activated in a substitution context.
A radio intercom set cannot perform a substitution operation.

1.7.3 Three party conference

A set monitoring a loop can be used to set up a three party conference .
The "Traffic" key has no effect in the context of a three party conference .

1.7.4 Automatic callback on busy trunk group

A radio intercom set can request, or be subject to, automatic callback on busy trunk group.
The set is called back when it returns to idle or loop monitoring mode.

1.7.5 PBX groups

An intercom set can belong to a PBX group.

1.7.6 Guide mode

Guide mode can be accessed if the set is at idle or monitoring a loop.

    !   " #$ 

1-5
Chapter 1 " #$ 

1.7.7 Voice Mail

A radio intercom set can activate forwarding to voice mail.
Messages can be consulted if the set is at idle or in loop monitoring mode.

1.7.8 Manager/assistant groups

A radio intercom set cannot belong to a manager/assistant group.

1.7.9 Mail services

Mini-messages can be sent if the set is at idle or in loop monitoring mode.

1.7.10 DECT
A DECT terminal cannot be a radio intercom terminal.

1.7.11 IP-Phones
Audio flow separation is not offered on IP-Phones.

1.7.12 Mastered conference

An intercom set cannot lead a conference.

1-6     !   " #$ 

 

2    
 

Implementation of this service requires the following items to be managed:

- system parameters,
- timers,
- the interphony prefix,
- CMP boards,
- radio channels,
- users,
- radio servers.

2.1 System parameters

Two system parameters specify audio transmission on 4035 sets. These two parameters are
not used with 4037 IP-Phones.
Object name: System > Other System Param. > Spec. Customer Features Parameters
Attributes:
Ith Radio/Phone Audio Flux : True: if the handset is off hooked, the channel
Separ. activated in traffic mode or private call is heard in the
handset and the other channels are heard on the
loudspeaker (see table below).
Muted Channels During PTT : True: When speaking on a channel, the user does not
Activat. hear the other channels

table 2.2: Function of the flow separation parameter

Flow separation No flow separation
Loudspeaker Loudspeaker
Handset audio Handset audio
audio audio
Hands-free # channels — # channels —
Monitoring Handset # channels if # channels if
off loudspeaker # channels loudspeaker # channels
hooked activated activated
# channels + # channels +
Hands-free — —
private call private call
Monitoring
& private Handset # channels +
call private call, if # channels +
off # channels Private call
loudspeaker private call
hooked
activated

%    !   &

'() 
 $)  2-1
Chapter 2 &
'() 
 $) 

Flow separation No flow separation

Loudspeaker Loudspeaker
Handset audio Handset audio
audio audio
Hands-free # channels — # channels —
Monitoring Handset # channels – # channels if
& traffic Selected
off selected loudspeaker # channels
channel
hooked channel activated
# channels if
system
parameter Muted
Selected
Hands-free — Channels —
channel
During PTT
Activat. is set to
Monitoring No.
& # channels if
speaking loudspeaker
# channels if
activated and
Handset # channels – parameter Muted
Selected parameter Muted
off selected Channels During
channel Channels
hooked channel PTT Activat. is
During PTT
set to No.
Activat. is set to
No.

Note: In the case of a half duplex radio transmission, when speaking (PTT button activated), there is no
audio transmission on the selected channel.

2.2 Timers
Object name: System > Timers
Attributes:
Timer No. : 289
Timer units : Time between two successive attempts by the
intercom server to reconnect to the EMTL or CMP
board.
Default value: 100 (10 sec.).

Attributes:
Timer No. : 290
Timer units : Time the activity pictogram continues to be displayed
after end of activity on the channel.
Default value: 50 (5 sec.).

Attributes:

2-2 %    !   &

'() 
 $) 
 &
'() 
 $) 

Timer No. : 291

Timer units : - in multi-channel mode, time without speaking
(without pressing the PTT button) that results in
automatic release of traffic mode and switchover
to monitoring mode.
- time a menu continues to be displayed after
selecting a channel. When this time elapses with
no user action, the main menu is displayed again.
Default value: 30 (3 sec.).

2.3 Creating the prefix

An intercom prefix must be created for users with explicit activation mode.
Object name: Translator -> Prefix plan
Attributes:
Prefix meaning : Local features
Local features : Intercom Service Loop

2.4 Managing users

User management consists in:
- creating a multiline 4035 set with radio intercom service,
- allocating a list of profiles,
- allocating intercom service rights in the user's phone facilities category.

2.4.1 Managing the set

Object name: Users
Attributes:
Directory No. : Enter the directory number of the set.
Set Type : 4035T or 4037 (4035 & TSC IP)
Ith (= Voice Intercom/VI) : Ith radio service
service
Ith activation mode : - Ith explicit: the user must dial a prefix to activate
the intercom service,
- Ith implicit: the intercom service is activated at
set initialization.
Ith profile list : Enter the number of the user's profile list.

2.4.2 Phone facilities categories

Object name: Categories > Phone Facilities Categories

%    !   &

'() 
 $)  2-3
Chapter 2 &
'() 
 $) 

Attributes:
Local features
Intercom Service Loop : 1

2.5 Managing monitoring circuits on a GPA board

On each node with radio intercom subscribers, conference circuits must be used to support the
monitoring loops.
Circuit size can be set. A DSP can support either one circuit of 30, or two circuits of 15, or
three circuits of 10.
Monitoring circuits are allocated dynamically. A monitoring circuit is allocated to the user as
soon as he leaves the idle state (i.e. the intercom service is activated on the set and the user
connects to a channel or makes/receives a point-to-point call). The circuit is released when the
terminal returns to idle.
Object name: Shelf > Board > Gpa Dsp program > Modular conference
Attributes:
Shelf address : Enter shelf address.
Board Address : Enter board address.
GPA : 1
DSP number : Enter DSP number (0, 1or 2).
Conference size : Possible choices for a DSP configured as Ith or Ith
flow:
- 3x10
- 2x15
- 1x30
Mapping : The type of circuit to be created depends on the flow
separation system parameter:
- Ith: monitoring circuit for radio intercom user.
- Ith flux: monitoring circuit with radio
intercom/telephony separation.

Note: Modifying this object automatically results in the GPA board being reset.

2.6 Managing profiles

Profile management is a two step process:
- manage intercom profiles,
- manage the list of profiles.
An intercom profile contains the directory numbers of the radio servers to which a user can
connect. A profile can contain up to 27 numbers (maximum).
A user may have several profiles (12 maximum), each profile corresponding to a key on the
numeric keypad. The profiles that can be used by a user are specified in a profile list.
The same profile can be used by several lists. The same list can be used by several users.

2-4 %    !   &

'() 
 $) 
 &
'() 
 $) 

Modifications made to profiles or to a user's list are not applied until the set switches to the idle
state (all channels disconnected and no point-to-point call). There is no impact on calls already
in progress.

2.6.1 Intercom profiles

Object name: Specific Telephone Services > Intercom > Ith Profiles
Attributes:
Profile Id : Enter the profile number (between 0 and 383).
Directory Loop 1 : Enter the loop directory numbers.
Directory Loop 2
...
Directory Loop 27

When defining profiles, the physical factors of sets that can activate the profile must be taken
into account.
Example: for a 4035 set with no extension keypad, the profile should have no more than 6 loops. If one of
loops 7 to 27 is entered, the set will refuse to select this profile.

2.6.2 Intercom lists

A list can contain up to 12 profiles, each profile corresponding to a key on the numeric keypad.
Object name: Specific Telephone Services > Intercom > Ith User List
Attributes:
List Id : Enter list number (between 0 and 31).
Profile Id 1 : Enter the number of the profile corresponding to key 1.
Profile Id 2 : Enter the number of the profile corresponding to key 2.
...
Profile Id 12 : Enter the number of the profile corresponding to key #.

2.7 Managing radio channels

Managing radio channels consists in:
- creating a direct trunk seize prefix,
- managing the IA Radio channel trunk category,
- declaring EMTL boards,
- creating LIA trunk groups and creating trunks.

2.7.1 Trunk seize prefix

Object name: Translator > Prefix Plan
Attributes:

%    !   &

'() 
 $)  2-5
Chapter 2 &
'() 
 $) 

Number : Enter the prefix number.

Prefix Meaning : External Features
External Features : Direct trunk seizure

2.7.2 Managing trunk category

The trunks belong to the category IA Radio Channel. By default, this is not configured on the
PBX. An unused category must therefore be selected and modified by using the CHANGE
TRUNK TYPE command and then entering parameters as shown below.
Object name: External Services > Trunk Category
Attributes:
Trunk Category Id : Enter the number of the modified category.
Trunk Type : IA Radio Channel
Signalling Type : Not Applicable
Radio channel trunk
2 or 4 Voice Wires : 4 Wires
Multi channel : - True: multi-channel operation,
- False: single channel operation
PTT DTMF : False
Incoming DTMF Received : False
Wait for Reply Timer : 0

2.7.3 Creating a trunk group

Object name: Trunk Groups
Attributes:
Trunk Group Type
Number Of Digits To Send
: LIA
: Only applicable in multi-channel mode.
Enter the number of digits used for channel selection
(1 or 2).

Object name: Trunk Groups > Trunk Group > Trunk

Attributes:
Trunk Group Id : Enter the number of the trunk group.
Physical Address : Enter the physical address (EMTL board device).
Trunk Category Id : Enter the category number of IA Radio Channel
trunks.
Trunk Number : Automatically allocated number used to call trunk
directly.

2-6 %    !   &

'() 
 $) 
 &
'() 
 $) 

2.8 Radio server

The radio server must be created on the same node as the channel.

2.8.1 Creation
Object name: Specific Telephone Services > Intercom > Intercom Server
Attributes:
Server Directory Number : Enter the server directory number.
Server name : Enter server name.
Radio Channel Number : Enter the number in the following form:
Prefix for Direct trunk seizure + Trunk Number (on 3
digits).
Detection Number : Directory number of the CMP board equipment used
to detect activity on the radio channel (equipment n
between 0 and 14).
Activity Number : Directory number of the CMP board equipment used
to signal activity on the radio channel (equipment
n+15)
Record Number : To be completed if you wish to record the loop. Enter
the number for the recorder.
Circuit size : Select size with respect to DSP configuration (see
below). The sizes possible are: 4, 5, 6, 7, 10, 15, 30
inputs.
Call Restriction Category : Enter the call restriction category This is used for the
server-radio channel link.
Implicit Priority
Activation mode : Enter server priority parameters These are used to set
Priority Level up the call from the server to the radio channel.
Subscriber #1 : Enter the directory numbers of subscribers who can
Subscriber #2 connect.
... The maximum number of subscribers depends on
circuit size.
Subscriber #27

2.8.2 Modifying and removing a server

To remove a radio server or to modify certain of its characteristics, it must first be taken out of
service. To do this, select Intercom server action on working state, and set the Enable
parameter to No.
Taking a radio server out of service results in release of all connections to subscribers.

2.8.3 Managing conference circuits on GPA boards

%    !   &

'() 
 $)  2-7
Chapter 2 &
'() 
 $) 

For each radio server, a conference circuit of the same size must be used. This circuit must be
located on the same node as the server.
Object name: Shelf > Board > Gpa Dsp program > Modular conference
Attributes:
Shelf address : Enter shelf address.
Board Address : Enter board address.
GPA : 1
DSP number : enter DSP number (this DSP must be configured for
conference).
Conference size : The DSP can be used for either one server with 30
devices, or several servers with less than 30 devices.
The sizes possible are: 7x4, 6x5, 5x6, 4x7, 3x10,
2x15, 1x30.
Mapping : Select Loop.

Note: Modifying this object automatically results in the GPA board being reset.

2.9 Managing CMP boards

A CMP board is declared by creating a new instance of the Board object with the Interface
Type attribute set to UA 32. The CMP board must be located on the same node as the server.
CMP board equipments are declared as UA 4034 sets. It is advisable to allocate equipments
with numbers that cannot be dialed as they must never be called by users.
Managing detection levels
Detection levels are managed directly on the CMP board using a VT100 console connected
via V24 link. Proceed as follows:
- configure the VT100 console:
• 19200 bds,
• 7 bits,
• even parity,
• 1 stop bit.
- connect the VT100 console to the CMP board as shown in the figure below,

2-8 %    !   &

'() 
 $) 
 &
'() 
 $) 

- on the console, type  , then complete the levels:

   

   

   

    
- to confirm, answer  to the question    .

%    !   &

'() 
 $)  2-9
Chapter 2 &
'() 
 $) 

2-10 %    !   &

'() 
 $) 
 

3 

3.1 CPU switchover

On CPU switchover, node monitoring circuits are released, this results in the following types of
call being released:
- between monitoring circuits and the telephone terminals relying on them,
- between these monitoring circuits and the intercom loops to which they are connected.
Node radio loops are released, resulting in release of calls with users connected to them.
EMTL boards are reset.

3.2 Radio server

If an access to the CMP or EMTL board is lost, the server attempts to reconnect at regular
intervals. The time between attempts is specified by timer n° 289.
If a radio server is taken out of service (in management for example), all calls with users are
released and an incident (n° 2403) is transmitted.

3.3 Not enough monitoring circuits

If there is a shortage of monitoring circuits, the user cannot use the service. An incident (n°
2424) is transmitted each time the user attempts to use the service or to activate a channel.

3.4 List of incidents

2403 : incident generated when an intercom server switches to out of service,
2405: failed to connect to server,
2406: subscriber to server connection broken,
2424: failed to launch service as not enough monitoring circuits available,
5701 : failed to launch service due to incompatibility between the profile requested and the
number of keys available on the set.

%    !   *



$ 3-1
Chapter 3 *


$

3-2 %    !   *



$
 

4  

4.1 Activating the service

In implicit mode, the service is activated when the set is started.

In explicit mode, the service is activated by dialing the intercom prefix or pressing the dynamic
key created for this purpose. The service can only be activated if the terminal is idle.

When the service is activated, the first profile in the user's profile list is selected. To select
another profile, press the dynamic profile key, the display shows:

+    !   , 

4-1
Chapter 4 , 

Select a profile by pressing one of the twelve keys on the set's numeric keypad. The display
shows the number of the profile selected.

When the service is activated, a pair of keys is reserved to monitor each radio channel:
- the left key is used to activate monitoring on a channel,
- the right key is used to speak and to monitor activity on the channel.

4.2 Activating radio channels

4-2 +    !   , 

 , 

4.2.1 Activating a channel in monitoring mode.

4.2.1.1 Single channel mode
To activate this, press the "Monitoring" key:

The display shows:

Press the On key. The pictogram changes to:

4.2.1.2 Multi-channel mode

Initially proceed in the same way as for single channel mode: press the "Monitoring" key, the
number of the channel activated is then shown on the set display, then press the function key,
On. To select another channel, press the Monitoring key again. The display shows:

+    !   , 

4-3
Chapter 4 , 

Press the Channel key, then enter the channel number on the set's numeric keypad.

Remarks:
- A channel can only be selected in monitoring mode.
- The channel cannot be changed if another user has activated traffic mode on the channel.

4.2.2 Speaking
To speak on a channel:
1. activate monitoring mode on the channel,
2. switch to traffic mode on the channel. To do this, press the channel's "Traffic" key.

The pictogram changes to:

Remarks 1:
• To switch back to monitoring mode, press the "Traffic" key again.
• In multi-channel mode, if another user has already activated traffic mode on the channel, you
cannot switch to traffic mode.
• In multi-channel mode, if the user does not speak (by pressing the PTT or "Secret" button) for a
certain time (timer 291), the channel automatically switches to monitoring mode.
3. Contine to hold down the handset's Push To Talk button (if available) or the set's "Secret"
button (depending on configuration).

4-4 +    !   , 

 , 

The pictogram changes to:

Remarks 2:
• This action has no effect if the user has not activated the channel in traffic mode.
• The button must be held depressed while speaking.

4.2.3 Disconnecting from a channel

A subscriber in monitoring or traffic mode can disconnect from the channel by pressing the
channel's Monitoring key then the Off function key.

The pictograms change to:

4.2.4 Interaction between channels

It is possible to activate monitoring on several loops simultaneously, but only one channel at a
time can be activated in traffic mode. If a user tries to change to traffic mode on a channel but
is already in traffic mode on another channel, he is automatically switched to monitoring mode
on the initial channel.

+    !   , 

4-5
Chapter 4 , 

Example:

4.3 Interaction between point-to-point calls and channels

4.3.1 Subscriber in monitoring mode

The use of point-to-point links has no effect on channel monitoring. A user monitoring a
channel can make or receive point-to-point calls.
A user making a point-to-point call can activate monitoring on a channel and disconnect from a
channel.

4.3.2 Subscriber in traffic mode

Setting up a point-to-point link results in traffic mode connection to a channel reverting to
monitoring mode.

4-6 +    !   , 

 , 

Example 1:

Switching to traffic mode on a channel results in the current point-to-point call being put on
hold.
Example 2:

+    !   , 

4-7
Chapter 4 , 

4.3.3 Overview of point-to-point calls

- The radio intercom service is not activated: standard operation,
- The radio intercom service is activated:
• no point-to-point link set up, no channel activated: ringing informs the user of the call,
• no point-to-point link set up, monitoring mode activated on one or more channels: a
beep informs the user of the call.

4-8 +    !   , 

 , 

• one or more point-to-point links set up: a beep informs the user of the call.

4.3.4 Point-to-point call release

If the user is not in monitoring mode, a point-to-point call is released by pressing the "Release"
key or on-hooking the handset.
If the user is not in monitoring mode, a point-to-point call can only be released by pressing the
"Release" key.

+    !   , 

4-9
Chapter 4 , 

4-10 +    !   ,