Alcatel OmniPCX Enterprise

Twin Sets
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

 Purpose ...................................................................................................... 1.1

 Principle ..................................................................................................... 1.1
 Reference to related modules ............................................................ 1.2

Chapter 2
Detailed description

 Calling a user who has a tandem ..................................................... 2.1

 Call modes ................................................................................................... 2.1
 Call processing ............................................................................................ 2.2
 Displaying tandem calls on the secondary set ......................................... 2.5
 Network mobility relative to a secondary mobile set (roaming).
........................................................................................................................ 2.5
 Call in network ............................................................................................. 2.6
 Services offered ........................................................................................... 2.6
 Features not provided when roaming ....................................................... 2.6
 Features offered in a tandem ............................................................. 2.6
 Features independent of the mobile set location ..................................... 2.6
 Features dependent on the mobile set location ....................................... 2.8
 Manager/Assistant assembly ............................................................ 2.10

 
 0-1
 


 Unavailable keys and functions on a mobile secondary set .................. 2.11
 Functions offered ....................................................................................... 2.11
 Features not offered by the tandem ............................................... 2.11
 Features specific to each set .................................................................... 2.11
 Unauthorized features ................................................................................ 2.12
 Supervision ............................................................................................. 2.13
 Deactivated specific supervision .............................................................. 2.13
 Activated specific supervision (from R4.1) .............................................. 2.14

Chapter 3
Configuration procedure

 Principle ..................................................................................................... 3.1

 Declaration ............................................................................................... 3.1
 Main set ........................................................................................................ 3.1
 Secondary set .............................................................................................. 3.2

0-2  

 
 

1 

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

1.1 Purpose
The tandem is a logical association between two sets, one called “main set” and the other
“secondary set”.
Up to R3.2, the tandem associated a main wired set, which allowed greater phone comfort,
with a secondary DECT (or PWT for the USA) allowing greater mobility.
From R4.1, the function applies to all UA dedicated sets.
The tandem function is defined so that the telephone services are provided homogeneously on
the two sets.

1.2 Principle
The tandem user has:
- a main wired digital set of UA type.
- a secondary set that can be:
• a dedicated UA wired set,
• a DECT type mobile set (or PWT for the USA).
By grouping them under a single directory number (that of the main set), they form a tandem.
Note:
- A set can belong to only one tandem.
- the wired set can be connected behind a TSC-DECT or it can also be an IP-Phone.

Figure 1.1: Configuration tandem

Remark: For clarity purposes, secondary set will be represented as mobile set in the graphics shown in
the entire documentation concerning the tandem.

        
       1-1
Chapter 1   

The two sets of the tandem must be managed in multiline mode and cannot be:
- analog type,
- S0 type,
- attendant sets,
- distribution agent sets (ACD, CCD),
- sets of a PABX hunt group,
- sets declared as night forwarding,
- sets declared as room or booth for the hotel/hospital application.
The services activated on one of the sets are automatically reflected onto the other.
Telephone operations carried out from the secondary set are taken into account as though
they were made from the main set.
The two tandem sets are preferably on the same node (home node).

1.3 Reference to related modules

The DECT TANDEM is described in the following modules:
- Functional description(see module Twin sets - Detailed description ),
- Management(see module Twin sets - Configuration procedure ).

1-2         

      
 
 

2
  

In this document, the term "mobile set" means DECT set (or PWT for the USA).

2.1 Calling a user who has a tandem

2.1.1 Call modes

The user is known by the directory number of his main set, main or secondary MCDU.
Calls intended for the main set (i.e. for the tandem), main or secondary MCDU, are presented
simultaneously on the secondary set.
2.1.1.1 Calling via the tandem number
In this case, the two sets ring simultaneously. The call can be answered by either of them.

Figure 2.1: Calling by the tandem's directory number

2.1.1.2 Calling the secondary set directly

The secondary set can nevertheless be called by its own directory number. In this case, the
operation is identical to that of an ordinary set and does not take into account the association
in tandem.

Figure 2.2: Calling by the directory number of the secondary set

       
    
   !
" 2-1
Chapter 2 
   !
"

2.1.2 Call processing

2.1.2.1 Call presentation
The main set presents the calls from the tandem, taking into account its occupation status and
within the limits of available resources.
If the call can be presented on the main set, it is also presented simultaneously on the
secondary set. When one of the sets takes the call, the other stops ringing.

Figure 2.3: Call processing

Up to the R3.2 version, the occupation status of the tandem reflected that of the main set.
From R4.1 , a "Partial busy " option has been added in the set parameters (see module Twin
sets - Configuration procedure § Main set ). .
The table below presents the global status of the tandem according to that of the main and
secondary sets, whether the "Partial busy" option is validated or not:

Remark: When the " Partial busy" function is validated in management, the tandem is seen as busy as
soon as one of the sets is busy.

2-2        

    
   !
"
 
   !
"

Whenever the tandem is partially busy (especially when the main set is free and the secondary
set is busy), this results in:
- network call: the calling set displays the busy status and broadcasts the multiline busy
tone,
- external call: broadcast of the appropriate menu-guide (if the AVI is managed),
- operating set reserving the tandem (local and network calls): display of the internal and
external busy statuses.
Caution:
1. if an attendant calls a tandem when the "Partial busy" option is validated, the intrusion is not
proposed when the main set is free and the secondary set is busy.
2. waiting right on the main set modifies the status of the set and therefore that of the tandem.
2.1.2.2 Management of incoming calls on the secondary set
The resources available on a secondary set vary depending on the type of set:
- mono-MCDU set: number of “multiline" keys of the set,
- multi-MCDU set: number of “multiline" keys managed with the associated MCDU in the
tandem.
The calls are allocated a priority depending on their origin (e.g.: a call on the privileged
manager/assistant line has higher priority than a normal call).
The calls coming in on the tandem are presented on the secondary set, according to line
availability and the call priority:
- if the set has at least one free line, it rings,
- if the set is totally busy:
• if there are no more lines ringing, this call is not presented.
• if there is at least one line ringing:
• if all calls on the lines ringing have greater priority than the incoming call, then this
new call is not presented.
• if the call on a line ringing has lower priority than the incoming call, then the new
call is presented in place of the previous one.
- As soon as a resource is released, the PABX presents, in decreasing order of priority and
according to its line availability, one of the calls which could not be presented previously
and which is still ringing on the main set.
The following algorithm is applied:

       
    
   !
" 2-3
Chapter 2 
   !
"

Figure 2.5: Processing of calls ringing on the secondary set

2.1.2.3 Ringing in partial busy

From R4.1, this function allows the user to choose the ringing type of the free set in case one
of the sets is free and the other one is partial busy.
Two ringing types are possible: "Long Ring" or "Short Ring ". These parameters are validated
in management in the set parameters (see module Twin sets - Configuration procedure § Main
set )..
The "Long Ring" value is the default value. The ringing types corresponding to this value are
those used in all versions up to R3.2.

2-4        

    
   !
"
 
   !
"

The table below shows the different rings of each of the sets during an incoming call when the
" Ringing in partial busy" function is validated in " Long Ring" or in "Short Ring ":

1
- : long ring, whatever the type of ringing parameter,
2
- : according to the ringing parameter (long or short ) chosen in management
Remarks:
- (* ): call priority, see § Management of incoming calls on the secondary set ,
- (** ): if the set is not protected against multiline ringing.

2.1.3 Displaying tandem calls on the secondary set

The display on the set of the ringing tandem varies depending on the type of call:
- call on the “main MCDU" of the main set:

- call on one of the “secondary MCDUs" of the main set:

- call on the privileged “manager call" or “assistant call" line of the main set:

2.2 Network mobility relative to a secondary mobile set (roaming).

       
    
   !
" 2-5
Chapter 2 
   !
"

2.2.1 Call in network

If the secondary mobile set has the roaming right, it benefits throughout the network from most
of the telephone features that it is entitled to locally. The data for this set is temporarily
transferred to the visited node.
If the secondary mobile set is localized by a node other than its declaration node, the system
considers that the user is roaming and the call is immediately directly to the secondary set.

2.2.2 Services offered

In addition to the services offered to a “non tandem" mobile set, there are:
- Simultaneous presentation of “tandem" calls on both sets,
- Display of the type of “tandem" call on the roaming set (main and secondary directory
numbers, or privileged manager/assistant line),
- Reciprocity of activated services (validation/cancelation of forwarding or “Do not disturb",
status changes (notification /denotification of voice mails), modified data (secret code, etc).

2.2.3 Features not provided when roaming

Certain features cannot be accessed by a mobile set when roaming:
- reading the tandem's metering counter,
- call parking,
- call transfer within the tandem,
- notification and consultation of the text mail,
- access to to the tandem's ISDN unanswered call directory.

2.3 Features offered in a tandem

The features of one of the tandem's sets or of the tandem itself may follow special rules due to
the association of two sets. Modifying a feature may afffect the tandem's other set.
Caution: When the secondary set is a mobile set, its location on a visit node affects certain
features of the tandem (see § Features not provided when roaming and § Features dependent on
the mobile set location ).

2.3.1 Features independent of the mobile set location

When the secondary set is a mobile set, its location on a visit node does not affect the
following features of the tandem.
Whatever the type of secondary set (UA or mobile), the features quoted in the paragraph allow
a common management of data or functions by both sets .
2.3.1.1 Identical data and operation on both tandem sets
Unique data for both tandem sets

2-6        

    
   !
"
 
   !
"

Modification on one set leads to modification on the other tandem set; the following functions
are concerned:
- secret code,
- associate,
- categories (features, connection...),
- language.
Joint activation of services
This concerns data or services specific to the tandem. If a service is activated on one set, it is
automatically reflected onto the second. The following functions are concerned:
- secret identity,
- “do not disturb",
- camp-on control,
Caution 1: the waiting right is validated when the tandem is seen as busy. Even if waiting is
forbidden on the tandem, calls towards the tandem will be presented when it will be seen as
free, that is to say:
• when the "Partial busy " function is not validated: when the main set will be seen as
free (see table § Call presentation ),
• "Partial busy " function is validated: when both sets will be seen as free (see table §
Call presentation ).
Caution 2: in the case where the secondary set is a mobile set, and if the "Partial busy "
function is validated, when the secondary set is roaming and changes its waiting right, the
main set is not warned about the change. Consequently, an incoming call to the tandem can
be presented even if waiting is forbidden.
- calling set identification: the set called always displays the name of the main set
irrespective of which tandem set is calling,
- call back:
• if a set (free or busy) receives a call back request by one of the tandem sets, it takes
into account the call number of the tandem,
• if a set makes a “call back" on the tandem, the message lamps on both sets of the
tandem are lit.

- wake-up/cancel wake-up - appointment reminder: it can be activated on either set, but

rings both sets by the tandem's call number,
- forwarding: any forwarding action made on a tandem set automatically forwards the other
set in the same way:

       
    
   !
" 2-7
Chapter 2 
   !
"

• immediate forwarding,
• forwarding on occupation
• forwarding on no reply,
• forwarding on busy or no reply,
• cancellation of forwarding,
• cancellation of forwarding by the called party,
• cancellation of overflow to associate,
• overflow to associate on no reply,
• overflow to associate on busy,
• overflow to associate on busy or no reply,
• programming remote forwarding,
• cancellation of remote forwarding
Caution 3: the multiline overflow-on-no-answer and overflow-on-busy options are valid when
the set is seen as busy:
• The "“Partial busy " function is not validated: when at least one line of the main set is
seen as busy (see table § Call presentation ),
• The "“Partial busy " function is validated: as soon as either set is seen as busy (see table
§ Call presentation ).
Note: Mutual forwarding within the tandem is prohibited.
Independent activation on each set
- putting a set out of service: each set of the tandem can be put out of service separately.
However, the main set is necessary to the tandem; consequently:
• If the secondary set is out of service, the tandem is reduced to the main set.
• If the main set is out of service, the tandem is out of service.

Caution 4: it is impossible to move one of the tandem sets to another network node.
- substitution: if a set is totally substituted for a tandem set, it reacts like the main or
secondary set that it is substituted for.
2.3.1.2 Different data and operation on the two tandem sets
Last caller call back: the call number of the last caller of the tandem is common to both tandem
sets.
However, the number of the last set calling the secondary set directly by its own directory
number is only stored in the secondary set.

2.3.2 Features dependent on the mobile set location

These features are common to the two sets of the tandem. However, some are not able to be
accessed from the secondary set when it is a mobile set in visit on a different node than the
declaration node.
2.3.2.1 Metering
When one of the two tandem sets makes an outgoing call to the exterior, the metering ticket is
always recorded on the main set's account.

2-8        

    
   !
"
 
   !
"

Reading the metering counter on either tandem set reads the tandem's charge units.
Caution: The charge counter can only be read from a secondary mobile set roaming on a visit
node.

2.3.2.2 Parking
Sets beside each other
When one of the sets of the tandem is busy, the other (or the same) one can retrieve the call.
Caution 1: except if the secondary set is a mobile set roaming on a visit node.
From the set making the call, the user places the call on hold:
- by pressing the "OK" key of the mobile set if the mobile set is a secondary set, use the
"parking prefix" programmed key of the main set or of the secondary set if it is a UA set.
- the call is resumed simply by off-hooking the main set or by dialling the parking prefix on
the secondary set.
Remote sets roaming
Transfer is carried out in the usual way, by making an enquiry call/transfer on the MCDU of the
(main or secondary) set, from the set making the call.
Caution 2: parking is impossible when the secondary set is a mobile set visiting a node different
from the declaration node (the parking does not operate in network).

2.3.2.3 Message Function

Principle
The following types of message can be received:
- telex,
- text,
- fax,
- voice mail,
- image.
The voice mailbox and the data concerning the messages are common to both sets.
Consequently, if a set deposits a message on the tandem, both tandem sets light their
message lamps.
Similarly, each of the two tandem sets can perform operations on the voice mailbox which will
be reflected on the other set.
Simultaneous access
Simultaneous access by both tandem sets to the message functions (text or voice) or call back
using keys, prefixes or suffixes is impossible.
Roaming
If the secondary set is a mobile set roaming on a visit node, the light and consultation functions
of the message lamp are unavailable, except in the case of a call request.
Activating the message lamp

       
    
   !
" 2-9
Chapter 2 
   !
"

The two tandem sets light their message lamps:

- if either tandem set requests call recording during the call,
- if another set deposits a message on ring back tone on the tandem (busy or not).
Switching off the message lamp
Deleting a message on the tandem
Both tandem sets switch off their message lamps, if there are no more messages, when either
of the tandem sets performs one of the following operations:
- message deletion,
- consultation,
- of a call back (in case of call back or call back cancellation),
- of the text mail (after reading the text or in case of call back request).
Deleting a message deposited by the tandem
If one of the tandem sets deposited a message on another set, either tandem set can request
deletion.
Excuse message
When one of the tandem sets switches into excuse message mode, the associated tandem set
is also in excuse message mode.
Caution: except if the secondary set is a mobile set roaming on a visit node.
Message deposit by the tandem
The following message types are available:
- telex,
- text,
- fax,
- voice mail,
- image.
The call number recorded by a set after a message has been deposited on it by either tandem
set is that of the tandem.
2.3.2.4 ISDN key
The ISDN key icons on both tandem sets are activated simultaneously on both sets, so that:
- the icon is displayed if an external call is presented on the tandem and it does not reply,
- the icon is deleted if either tandem set consults an ISDN call back (if there are no more
unanswered calls), in case of call back or cancellation of call back.
Caution: If the secondary set is a mobile set roaming on a visit node, it cannot access the
directory of ISDN calls unanswered by the tandem.

2.4 Manager/Assistant assembly

The main set of a tandem may be part of a manager/assistant assembly.

2-10        

    
   !
"
 
   !
"

Figure 2.11: Manager/Assistant tandem

When the assistant's secondary set is a mobile set, its features are limited to the available
keys (see § Unavailable keys and functions on a mobile secondary set ).

2.4.1 Unavailable keys and functions on a mobile secondary set

Certain keys specific to the manager/assistant assemblies (“Manager call" or “Assistant call")
may be programmed on the secondary mobile sets of the manager and the assistant. This
programming involves creating manager/assistant assemblies separate from those existing
between the main sets, which results in operating restrictions:
- the RISO and PRISO keys on the mobile set only allow filtering on individual number,
- the “Filtering supervision" and “Assistant absent" keys of the mobile set only concern the
associated manager/assistant assembly and not the tandem assembly.
Note: These specific keys are not available in network.
Certain functions are not available on the assistant's secondary set:
- the manager-assistant mail,
- immediate forwarding of the manager from the assistant.

2.4.2 Functions offered

The functions offered on the assistant's secondary set can be used to:
- transfer the filtered calls, even when the manager is in filtering position,
- privilege the display of “privileged line" calls from the manager: when no lines are free on
the secondary set , the calls of the Manager/Assistant “privileged line" are presented in
priority on lines possibly ringing and replace a call of lower priority,
- differentiate between the manager's filtered calls and his personal calls (shown on the
display).

2.5 Features not offered by the tandem

These features are managed identically, whether or not the set belongs to a tandem.

2.5.1 Features specific to each set

       
    
   !
" 2-11
Chapter 2 
   !
"

Set locking (padlock)

Each tandem set must be locked separately.
Group call pick-up

Figure 2.12: Features

Call pick-up is possible within a pick-up group. The two tandem sets may belong to:
- the same pick-up group,
- different pick-up groups:
• if the tandem is called, only a set which belongs to the same pick-up group as the main
set can take the call.
• if the secondary set is called directly, only a set which belongs to the same pick-up
group as the secondary set can take the call.
Picking up a directed call (number of the ringing set)
A tandem call can only be picked up by dialling the directory number of the main set.
The secondary set can only be picked up when it is called directly by its own number.
Call back via the “Redial" key
Redial is specific to the (main or secondary) set that was used to dial.
Call back via the “memory" keys
The memory keys are specific to the tandem set that was used to dial.
Malicious call
The malicious call is allocated to the physical set.

2.5.2 Unauthorized features

2-12        

    
   !
"
 
   !
"

These features are incompatible with a set part of a tandem.

Group
The tandem cannot be included in an automatic call distribution group (ACD). However, it may
belong to a hunt group.
Night forwarding
This feature is incompatible with the multiline nature of the two tandem sets. However, they
may be placed in a call distribution table.
Forwarding between the two sets
Overflow between the two sets

2.6 Supervision

Figure 2.13: Supervision

A set supervising a tandem has in its supervision key the main directory number of the
tandem's main set.

2.6.1 Deactivated specific supervision

The supervisor set is warned about the tandem ringing.
The busy status of a tandem takes account of the status of each tandem set:
Busy statuses of the supervision key
1. Free

2. Partially busy

       
    
   !
" 2-13
Chapter 2 
   !
"

3. Totally busy

4. Ringing

The ringing status has greater priority than the others: if a line is rung on the tandem, the
ringing icon is displayed to enable call pick-up.

2.6.2 Activated specific supervision (from R4.1)

The supervisor set is not warned about the tandem ringing, but only about its status changes.
Busy statuses of the supervision key.
1. Free

2. Busy

When the tandem is seen as “busy”, the supervision kay does not allow a call to be made.
The supervisor uses it to know the exact status of the tandem:
• the main set is the only one busy, the supervisor set displays the indication “MAIN
BUSY”.
• the secondary set is the only one busy, the supervisor set displays the indication
“SECONDARY BUSY”.
• both sets are busy, the supervisor set displays the indication “TOTAL BUSY”.

2-14        

    
   !
"
 
 

3  

3.1 Principle
To create a tandem, proceed as follows:
- check that the chosen secondary set is not already part of a tandem,
- check that the tandem's secondary set has no associated voice mail, which would prevent
creation of the tandem with this set. If there is a voice mail, delete this association before
creating the tandem,
- create a multiline wired main set,
- create a wired main set and declare it multiline,
- create a secondary wired set or mobile in the same node as that of the main set and
declare it multiline,
- modify the main set to create a tandem.
Note: the wired phone can be of TSC DECT or IP Phones type.
Caution: on creation of the tandem, all data (forwards, call backs, message deposits, etc.) are
cancelled on both sets.
Certain data on the secondary set is then modified to match the main set. The main data
copied is:
- the tandem's directory number,
- the tandem's displayed name,
- the connection, public network access, feature and metering categories,
- the voice mail, associate, entity, cost center, secret code and language numbers.
The data copied into the secondary set cannot be modified.

3.2 Declaration
Management of the options globally partial occupation, ringing-on-partially-busy, and specific
supervision is only performed on the main set. The system copies the information on the
secondary set.

3.2.1 Main set

The user is supposed to be already created and declared multiline (for further details on
multiline declaration, see module Multiline sets - Multiline Sets Configuration Presentation ).
Object name : Users
Attributes:
Tandem :
Tandem Directory Number : Enter the directory number of the secondary set.

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

Main set in the tandem : Select Yes .

Partial busy
Ringing in partial busy
Specific supervision
: No : (by default) the status of the tandem reflects the
occupation status of the main set.
Yes : Yes : the tandem is seen as busy as soon as one
of the sets of the tandem is busy.
: Long Ringing : (by default) long ringing for all ringing
sets.
Short Ringing : short ringing for free set (if the second
is busy).
: No : the supervision performed by this set is of normal
type.
Yes : the supervision performed by this set is of tandem
type.

3.2.2 Secondary set

The user is supposed to be already created and declared multiline (for further details on
multiline declaration, see module Multiline sets - Multiline Sets Configuration Presentation ).
Object name: Users
Attributes:
Tandem :
Tandem Directory Number : Leave blank.
Main set in the tandem : Automatically set at No when the tandem was created.

3-2  #      

    $"%&
" "! &