PREFACE

This book gives an overview of the:

- system features available with Call@Net 2.11;

- architecture of the ISPBXs of the iS3000 series.

For networking and routing features, please refer to the System and Application
Manual - iSNet.

For SysManager 410, please refer to the System and Application Manual - System
management.

For operator consoles, please refer to the System and Application Manual - Operator
communications.

For all telephone sets, please refer to the System and Application Manual - Business
Telephone Equipment.

For VoiceManagers, please refer to the System and Application Manual - Messaging
Systems.

For DECT features, please refer to the System and Application Manual - iSMobile.

Disclaimer: No rights can be derived from this document. This document is subject
to changes because we continue to develop and improve our products.

For information on required materials, please refer to Prophix. Prophix is a Windows

application that assists in specifying an offered configuration. It helps you to configure
new systems, system expansions or upgrades, spares and PC applications.

1
 1. Standard System Features
The SOPHO iS3000 series is a modular ISPBX system designed for any type and size
of business. The system software of the iS3000 series accommodates a rich set of
standard features and provides a platform for additional applications that can be
integrated into the system.

This chapter describes the standard system features of the iS3000 Series ISPBX,
divided into the following sections:

- Extension Features, including:

- Group Features;
- ACD Group Features;
- Manager/Secretary Features;
- ISDN Extension Features.
- Datacom Features;
- Directory Services;
- Operator Features;
- Night Service Features;
- Paging Features;
- System Management Features, including:
- Accounting management;
- Maintenance.
- General System Features.

This chapter describes all the standard features available with the iS3000 Series
platform. Please note that some of these features are intended to be used in
combination with certain peripheral devices, for example with a particular model of
Business Telephone or operator console.

Note: A number of facilities rely on facility class marks and system options being set.
These items are described further in sections 1.7.2 and 1.7.5.

Some features relate to specific options orboundaries, or they require a licence or

facility class mark. In that case, these items are listed after the description.

1.1. Extension Features

This section describes the standard features that are dependent on the ISPBX
software, features available to members of special groups of extensions and features
available to ISDN extension users. For more enhanced features, that are dependent
on the type of telephone set, please refer to the System and Application Manual -

2
Telephones. Any extension can be used to make a call to an internal destination
provided it has a sufficiently high traffic class. The traffic class is used to determine
the numbers that can be dialled from the extension, for example calls may only be
made to the operator.

Access to an internal or external destination is influenced by the following items:

- traffic class;
- compatibility check;
- number analysis;
- ISDN service compatibility check;
- activated facilities.

Any extension can be used to make a call to an external destination provided it has a
sufficiently high traffic class. The traffic class is also used to determine the external
numbers that can be dialled from the extension.

Extension Related Data

Each extension is identified with a directory number (DNR) which has the following
relations:

- Hardware Relation, known as the Extended HardWare Address (EHWA). This

gives the position of the circuit to which the extension is connected.
- Analysis group. This determines how dialled numbers are analysed.
Compatibility Value (CV). Used to allow or prevent certain connections from being
made.
- Traffic classes. Used to determine the destinations that can be dialled by the user.
- Facility Class Marks (FCM). Used to identify if a party is allowed to initiate certain
facilities.
- Internal Basic Service Category (IBSC). Used to indicate which type of service the
extension is used for.
- Basic Service Profile Type (BSPT). This is used to indicate which IBSCs are
compatible. If the BSPT is combined with the DNR, it is called BSP-ID.

1.1.1. Abbreviated Dialling

This facility provides short codes for dialling frequently used destinations. The user
dials a prefix and an abbreviated number that is converted into the destination number
used for the call set-up. It is possible to dial the first part of the expanded number and
let the user complete the destination number. There are three sorts of abbreviated
dialling:

3
 • Common Pool Abbreviated Dialling
Available to all extensions, operators and callers coming in via DPNSS routes.
• Group Abbreviated Dialling
Available to all extensions in the same analysis group.
• Individual Abbreviated Dialling (IABD)
Available to extensions and operators on an individual basis. IABD can be used
for dialling external numbers.

FCM 01, IABD and LENR, assigned to an extension.

Boundary 36, maximum number of IABD elements 150...12000.

Boundary 30, maximum number of abbreviated numbers, 0...4496.

System option 16, IABD allowed for operators.

1.1.2. Automatic Ring-Back (ARB)

This feature allows an extension user to request to be rung-back when encountering

a busy or not answering extension. The destination party can be another extension or
a party in an opposite exchange connected via DPNSS. In case of DPNSS, ARB is
called Call Back When Free (CBWF). In case of ISDN, ARB is called Completion of
Calls to Busy Subscriber (CCBS).

FCM 48, ARB entitled.

Boundary 68, maximum number of simultaneous ARB relations per initiator.

Timer 106, interval that timed out ARB is checked, 2 minutes.

Timer 179, ARB call setup guarding time, 230 seconds.

• ARB On Don't Answer

The caller presses the enquiry button during ringing. Internal dial tone is sent and
the caller can dial the ARB code. If the request is accepted confirmation tone is
given. When the handset of the destination party has been lifted and replaced the
system starts the ARB. First the ARB initiator is called. After answering the system
automatically dials the destination party.
Timer 182, maximum time that ARB on don't answer is active at initiator, 5...1440
minutes.
Timer 184, maximum time that ARB on don't answer is active at destination,
5...1440 minutes.
• ARB On Busy

4
 A caller encounters a busy extension and dials the ARB code. If the request is
accepted confirmation tone is given. When the 'busy' party replaces the handset
the system starts the ARB (a system option prevents ARB destination extensions
from being used within a certain time after going on hook, to improve the chances
of a successful ARB). First the ARB initiator is called. After answering the system
automatically dials the destination party.
System option 71, block ARB destination for new calls.
Timer 178, time between destination becoming free and initiator being rung-back,
0...10 seconds.
Timer 180, block ARB destination interval time, 10...30 seconds.
Timer 183, maximum time that ARB on busy is active at destination, 5...1440
minutes.
• Cancelling ARB
A pending ARB call can be cancelled by dialling a prefix from the initiating
telephone. A pending ARB is cancelled automatically if the system cannot perform
a successful ARB within a certain time interval. A system option can be chosen to
retain a pending ARB even if the ARB was successful but the called party does not
answer within the ringing time-out time. A system option can be chosen to
automatically cancel a pending ARB call if the two involved parties have reached
each other by a normal call.
Timer 009, maximum time that ARB is active, 5...1440 minutes.
Timer 011, ARB ringing time, 20...60 seconds.
System option 72, keep ARB relation after ring time-out.
System option 73, cancel ARB relation after dialling the same destination.
• ARB Protected
An extension can be protected against being the destination of ARB calls.
FCM 49, ARB protected.
• ARB after Diversion
When the originally called destination party has activated a single call diversion,
for example a follow-me or a call forwarding, then the following rules apply:
- If the called party has activated follow-me, ARB is started on the diversion
destination.
- If the called party has activated call forwarding don't answer or a call
forwarding not reachable, the ARB on free is started on the originally called
party.
- If the called party has activated call forwarding on busy, the ARB on busy is
started on the originally called party.
In case diversions are chained (multiple hop diversions) the rules mentioned
before are also used, by applying them for every single diversion of the chain. So,
first apply the rules to the first diversion, then on the second and so on (if
necessary). As soon as call forwarding is met in a chain of diversions, ARB is

5
 started on the source of that diversion. For example, when the following chain of
diversions is met: party A has activated FM to party B, party B has activated 'call
forwarding don't answer' to party C and party C has activated 'call forwarding on
busy' to party D. ARB is started on party B. Party A wanted the calls to be diverted
to the Follow-me destination.
• Multi ARB per Destination
An extension can be ARB destination for more than one party. The ARB
originators are called back in chronological order as soon as the destination
becomes free (if one originator is busy the next ARB call is established). A party
with different pending ARB calls can cancel each ARB relation separately by
dialling the destination extension.
Boundary 194, maximum number of simultaneous ARB relations per destination.
Boundary 195, maximum number of simultaneous ARB destinations in a unit.

1.1.3. Call Forwarding

Calls made to an extension can be automatically rerouted to an alternative

destination. There are nine types of call forwarding:

1. Call forwarding on don't answer;

2. Call forwarding on busy;
3. Call forwarding on not existing DNR;
4. Call forwarding on out of order extension;
5. Call forwarding on not reachable extension;
6. Call forwarding on absent group member;
7. Call forwarding on empty group;
8. Call forwarding on group overflow;
9. Call forwarding when group in night service.

Call diversion used in groups is described under Group Features Collection.

The destination number for call diversion can be:

- An internal number (individual or group);

- An operator (individual or the M-queue);
- An external destination (trunk access code + external number);
- Real paging equipment;
- A destination reachable via DPNSS;
- Announcement circuits (IAS).

All types of call forwarding are assigned by means of an Operational Maintenance

command. This command sets the selected type of call forwarding relation between

6
an originator and a destination number. For call forwarding on not existing DNR and
on out of order extension, no originator has to be specified because each call will be
routed to the same destination.

Another type of call diversion is follow-me. See section 1.1.11.

• Call Forwarding On Don't Answer

A call is forwarded if it has not been answered within a pre-determined time. This
time can be defined per user.
FCM 16, Call forwarding on don't answer.
Timer 007, call forwarding time, 5...60 seconds.
• Call Forwarding On Busy
This is activated and cancelled by dialling prefixes. A call is forwarded immediately
when activated.
FCM 37, Call forwarding on busy extension.
• Call Forwarding On Not Reachable DNR
"Not Reachable" means: for an ISDN terminal that it is disconnected from the S0
bus; for a DECT terminal that it is switched off, out of reach of a radio or not
subscribed. The alternative destination can be one of the following:
- The called extension's call forwarding on don't answer destination, if assigned.
- The called extension's secretary (if applicable) if no call forwarding on don't
answer destination is defined.
- Another group member if the called extension is a group member. The call can
also be put in the COB queue.
- The call forwarding on absent group member destination, assigned to the
called extensions group, if no call forwarding on don't answer destination is
defined and the extension is not a manager.
If no alternative destination can be found then external callers will be routed to the
operator C-queue, if the trunk route is assisted or the system reroute on no
response option is used. This option does not apply to calls to an ACD group
number.
System option 65, reroute on no response.
The call will be cleared if:
- The call is in enquiry;
- The call is an emergency call;
- The call is an automatic ring-back call; Automatic ring-back will be cancelled.
- The called extension is in an ACD group and the forced absence time is infinity.
If the forced absence time is not infinity then the forced absence feature works
in the normal way.
• Call Forwarding On Not Existing DNR
When the called number is in the range of internal numbers but not known in the

7
 system, the call will be diverted to the call-forwarding destination.
• Call Forwarding On Out Of Order Extension
Calls routed to an extension which is out of order will be diverted to the Call
Forwarding destination. "Out of Order" means that the extension is not in the 'in
service' condition. So it could be not installed, out of service etc. A hardware-less
extension gets the status out of order when no 'call forwarding on not reachable
extension' destination is assigned to it.
• Diversion Chaining
It is possible to create a chain of call diversion. This is also known as multi-hop
diversion. The chain is a combined series of call forwarding and follow-me
settings. All diversions can have more than one occurrence in the chain. The
normal rules for the Follow-Me and Call Forwarding relations apply. This includes
groups, manager/secretary relations etc. Per system a limit can be put on the
number of allowed occurrences in one chain and on the chain length. The
diversion chain may consist of any number of delayed diversions, any number of
direct diversions and one or two specific diversions.
Delayed diversions are:
- Call forwarding on don't answer;
- Call forwarding on not reachable;
- Call forwarding initiated by the CSTA application.
Direct diversions are:
- Follow-me and fixed follow-me;
- Call forwarding when busy;
- Call forwarding when absent;
- Call forwarding on out of order.
Specific diversions are:
- Call forwarding when empty (all group members absent);
- Call forwarding on group overflow;
- Call forwarding when night.
A call could run into more than one diversion. For example, a call is made to a busy
extension which has follow-me and 'call forwarding when busy' on. In this case a
fixed priority list is used to determine which diversion has priority.
Boundary 311, maximum number of chained direct diversions. The chaining may
take place in a single or multi unit environment and in DPNSS networks. The
boundary is used in every ISPBX in a DPNSS Network. Due to this fact, the
projected maximum amount of direct diversions in each ISPBX is allowed. For
example, when in an ISPBX the projected maximum is reached and the last
diversion is to the destination ISPBX (via DPNSS) there is a new maximum
number of direct diversions.

8
1.1.4. Calling Name and Number Display

Calling Name and Number Display (CNND) provides names of calling and called
parties on digital telephone sets with a display, on operator consoles and on DECT
sets.

Software licence 20, Calling Name and Number Display (CNND).

The information for internal parties is retrieved from a database that is located in the
ISPBX itself. This database contains numbers belonging to the ISPBX node. This
functionality is also known as I-CNND. External numbers from incoming calls via
DPNSS or ISDN and QSIG, can be 'translated' using an external database
application, i.e. a SysManager 410 module. This functionality is also known as E-
CNND. (E-CNND can also be used for internal numbers.) The database has to be
maintained by the MAC Manager which is part of the SysManager 410. The OM
terminal can be used as well but is not user-friendly and therefore not advisable for a
system administrator.

See also section "Directory Services".

1.1.5. Camp-On-Busy

Camp-on-busy (COB) can be used when a call is routed to a busy extension. The
calling party is automatically queued and can wait until the connection can be
established, without redialling. A number of calls can be placed in a COB queue to a
busy party at the same time. Callers in the COB queue hear COB tone. The called
party can hear a call waiting indication if calls are present in the COB queue. The
system manager can give an extension a long or short COB queue, from an OM
terminal.

Boundary 216, maximum number of COB cases, short COB queue, 1...5.

Boundary 217, maximum number of COB cases, long COB queue, 1...20.

A call is placed in the COB queue in the following circumstances:

- If a call is made to an extension with the facility class mark 'automatic COB
destination'.
FCM 30, automatic COB destination.
- If a call is made from an extension with the facility class mark 'automatic COB
originator'.
FCM 29, automatic COB originator.
- If a call is made from an extension with the facility class mark 'start COB entitled'

9
 and the start COB prefix is dialled.
FCM 36, automatic COB start COB entitled.
- If the appropriate DDI trunk options are selected then a DDI call is placed in the
COB queue.
- If call waiting is initiated.
- If break-in is initiated.
- If an operator call meets a busy extension.

Calls are placed in the COB queue with the following priority:

- One COB-place with 'highest priority' reserved for call waiting or break-in;
- COB-place(s) with 'operator priority';
- COB-place(s) with 'extension priority'.
• Call Waiting
Call waiting is a variant on COB. It uses a reserved position at the head of the COB
queue. If the reserved position at the head of the COB is occupied then the call is
given extension priority in the COB queue. If the COB cannot be initiated then the
caller hears congestion tone.
FCM 35, call waiting protected.
Call waiting is initiated in the following situations:
- An extension encountering a busy extension can initiate call waiting by dialling
a prefix.
FCM 34, call waiting entitled.
- An incoming DDI call encounters a busy extension. An option for the incoming
route determines if call waiting is initiated.
• Call Waiting Indication
A call waiting tone burst is sent to the busy extension when call waiting is initiated,
when COB is initiated and when break-in does not result in a three party
conversation. A system option determines whether call waiting tone is used and
another option determines if the tone burst is sent once or periodically.
System option 18, call waiting tone after extending to busy extension.
System option 45, periodic call waiting tone.

1.1.6. Central Directory Dialling (or Browsing)

Central Directory Dialling (CDD) enables browsing through a central directory using
ErgoLine 330 and 340 terminals release 1.06. Users no longer have to program their
own name directory. The central directory is located in the ISPBX and is also used by
the feature Calling Name and Number Display (CNND). The name selected by means
of CDD may be different from the name displayed by means of CNND. These
differences only occur when multiple names are associated with a single number, and
the selected name (via CDD) is not the preferred name (of CNND).

10
Software licence 20, CNND (per unit).

Software licence 26, Central Directory Dialling.

Boundary 342, maximum number of internal CDD database entries; 0 ... 65530.

Boundary 343, CDD sorting order; standard international, Danish or Swedish.

See also section "Directory Services".

1.1.7. Desk Sharing

Desk sharing allows users to activate their own telephone number on any telephone
set, including the traffic classes, facilities, group relations, message waiting indication
etc. The function key menu for this telephone number is downloaded to that telephone
set. Of course this works the best if the desk sharing environment makes use of the
same type of telephone set. In offices where people do not have their own desk (and
telephone set) because these people are not always at the office, desk sharing is a
real solution. This reduces costs related to infrastructure. Desk sharing is also useful
in e.g. hospitals where a patient that is moved to another room can keep the same
telephone number.

A user can activate his DNR at any telephone set by means of dialling a prefix, a
password and his related DNR. From that moment, calls for the specified DNR will be
directed to that telephone set. The user can also deactivate desk sharing or move it
to another telephone set. Desk sharing can also be arranged via operational
maintenance (OM). If necessary, telephone sets can be prevented from being used
by desk sharing users by means of a Facility Class Mark. For example because a
telephone set is exclusively used by one person.

Desk sharing uses the features basic DNR and hardware-less DNR.

No desk sharing can be done:

- with operator and group DNRs;

- on special extensions;
- via PVN/DPNSS (but: desk sharing is possible in a multi-unit (IMP) configuration).

Customer engineers can de-activate desk sharing for a complete unit or for the entire
multi unit configuration. By making use of a batch file, this can be done at a predefined
time.

Software licence 19, desk sharing BSPs.

11
 FCM 57, desk sharing entitled.

FCM 66, desk sharing avoidance.

System option 58: automatic download of function key menu for desk sharing.

System option 59: desk sharing automatic de-activate previous.

System option 104: prohibit desk sharing and installation between units.

1.1.8. Do Not Disturb

This facility is used to temporarily block an extension or group for all incoming calls. A
system option can be chosen to reroute calls to the (centralised) operator service or
provide number unobtainable tone when encountering an active do not disturb. For
DDI calls this can be specified per trunk route. The operator or night service extension
can overrule the do not disturb. Do Not Disturb (DND) in a DPNSS network is
supported at the same level as in a single ISPBX.

• Dialled Do Not Disturb

The extension user activates or deactivates do not disturb using prefixes. A
system timer can be set to automatically deactivate do not disturb after a specific
time.
FCM 25, do not disturb entitled.
Boundary 260, do not disturb reset time, 0...65535 minutes.
• Permanent Do Not Disturb
The system manager activates or deactivates do not disturb from an OM terminal.
FCM 24, do not disturb.
• Do Not Disturb via an Automatically Entered Message
This type of DND requires the SysManager 410. The extension user can send an
Automatically Entered Message (AEM) to the (centralised) SysManager 410, in
order to be switched to DND. SysManager 410 can activate (and deactivate) DND
from one place in the network (via the External Application Interface).

1.1.9. Emergency Alarm Extension

An emergency alarm extension is a normal extension to which a connection is always

guaranteed. A caller dials the 'emergency alarm code' and the emergency alarm
extension rings. One of the following situations occur:

- The emergency alarm extension is answered; a normal speech connection is

established.
- The caller hangs up before the emergency alarm extension is answered; the

12
 emergency alarm extension keeps ringing until answered and then the original
caller is rung back.
- The emergency alarm extension is busy; the calling party goes on-hook. As soon
as the emergency extension goes on-hook, the caller is automatically rung back
using the special emergency alarm ring current.

Only the emergency alarm extension can release the call. If the caller releases, the
calling extension immediately starts ringing again. Multiple emergency alarm calls can
be active simultaneously, i.e. a number of people have called the emergency alarm
number and have hung-up because the emergency alarm extension was busy or did
not answer. The emergency number can be dialled from extensions, not from external.
The emergency alarm destination can be an extension or a group.

1.1.10. Enquiry/Shuttle/Transfer

When an extension goes into enquiry, dial tone is given and the user can dial the
number of the second party or the code for a facility request.

• Enquiry
An extension can go into enquiry using one of the following methods:
- Earth button. The a-wire is shorted to earth.
- Calibrated loop button. The loop is opened for a specified time.
- Recall button. For digital extensions, a message is sent in the D channel.
- Impulse enquiry digit. For rotary dial telephones, the user dials a digit.
FCM 44, enquiry by impulse digit (extensions with this facility class mark
cannot use postdialling).
- Keytone enquiry digit. For digital telephones using Dual Tone Multi Frequency
(DTMF), the user presses a key. This facility is normally only applied if there is
no earth connection present at the telephones.
Boundary 34, enquiry digit.
FCM 59, enquiry by keytone digit.
FCM 60, enquiry by keytone digit full.
- Double digit enquiry on trunk.
When pressing the enquiry button during a trunk line call, the enquiry digits are
sent as keytone digits. When the connected party is not an external party, the
enquiry button is rejected. Note: for the ErgoLine and SOPHO-SET terminals,
pressing a function key (such as answer-callwaiting) during conversation is not
supported ! Pressing a function key during conversation is handled as if an
enquiry button was pressed.
Boundary 308, first enquiry on trunk digit.
- Hook flash. For rotary dial telephones, the user presses the hook switch.
• Progressive Enquiry

13
 This allows an extension that is the destination of one enquiry call to initiate
enquiry to another party. The number of extensions involved in an 'enquiry chain'
is unrestricted. If one of the parties involved in the 'enquiry chain', with two other
parties on hold, goes on hook, then this party is removed from the chain and the
two other parties are linked (transfer), i.e. the 'enquiry chain' is not broken.
• Call Clear with Party on Hold
If an extension goes on-hook when in the enquiry situation, with a party on hold,
this may not lead to a successful call transfer. The system option 'recall after clear
in enquiry' determines what happens next:
- If the option is used, the extension immediately starts ringing and the party on
hold is re-connected to the enquiry initiator.
- If the option is not used, then no recall takes place and the situation is handled
as a failed transfer (internal party released, external party rerouted for operator
assistance).
System option 56, recall after clear in enquiry.
• Shuttle
An extension can shuttle between two parties, one party is in speech, the other is
placed on hold. Shuttle is achieved using the enquiry button. A number of system
options can be used to choose the types of shuttle that are allowed.
System option 08, shuttle to internal party with internal party on hold allowed.
System option 09, shuttle to internal party with trunk on hold allowed.
System option 10, shuttle to trunk with internal party on hold allowed.
System option 11, shuttle to trunk with trunk on hold allowed.
• Shuttle with Forced Release (special variant)
An extension can choose whether to shuttle back to the party on hold and release
the connected party (enquiry and dial 1) or to shuttle between the two parties
(enquiry and dial 2).
System option 07, shuttle with forced release, overrides all above mentioned
options.
• Transfer
If an extension goes on-hook with one party on hold and another party in speech
connection then these two parties are connected together. The transfer is only
executed if the transfer initiator is connected with the second opposite party. If the
initiator was connected to the initial opposite party when going on-hook (after
shuttle), the ISPBX does not execute the transfer but releases both opposite
parties.
• Transfer Before Answer
The transfer can be initiated without waiting for the dialled second destination party
to answer the enquiry call of the initiator. This can be chosen with the system
option 'transfer before answer allowed'. If this option is not chosen and the initiator
goes on hook then it is treated as a failed transfer or 'recall after clear in enquiry'

14
 is initiated.
System option 55, transfer before answer allowed.
• Failed Transfer
If an extension goes on-hook when in the enquiry situation, this may not lead to a
successful transfer. In this case the involved parties are released (internal party)
or rerouted for operator assistance (trunk line). This happens if the 'recall after
clear in enquiry' option is not used.
System option 24, recall on hook allowed.

1.1.11. Follow-Me

This facility offers the possibility for direct diversion of all telephone calls to an
alternative number. If an extension has follow-me active, it can still be used to initiate
calls. The user receives a diversion active dial tone, to indicate that a follow-me is
active. A call made from the follow-me destination extension to the follow-me
originator extension is not diverted. There are the following variations of follow-me:

• Follow-Me
Follow-me can be activated from the originating extension by dialling a prefix and
the alternative destination number. Alternatively follow-me can be prepared at the
originating extension (prefix) and activated at the destination extension (prefix
followed by users own extension number). The destination can be any extension/
group or an extension/group in another PABX connected via DPNSS. The
destination can be destination for any number of follow-me relations. The active
follow-me can be cancelled from the originating extension (prefix) or from any
follow-me destination in one of two ways:
- Selectively: a single follow-me relation is cancelled (prefix followed by
originating extension number);
- Collectively: all follow-me relations to the destination are cancelled (prefix).
The current follow-me is overruled if the user activates follow-me at another
destination.
FCM 07, follow-me entitled.
• Fixed Follow-Me
In this case the destination number is fixed by the system manager with an OM
command. Fixed follow-me is activated and cancelled by the user (prefixes).
FCM 39, fixed follow-me entitled, assigned once the originator/destination relation
has been defined.
• Follow-Me Protection
Extensions can be protected against being a follow-me destination. If a user tries
to activate follow-me to a protected extension, number unobtainable tone is given.
FCM 08, follow-me protected.

15
 • Follow-Me Activated by System Manager
The system manager can activate or cancel follow-me for an extension using an
OM command.

1.1.12. General Cancel Facility

This facility allows the user to cancel a number of active facilities at a single request.
The system manager defines which facilities are checked and (if active) cancelled.
The following facilities can be included in the list:

- follow-me;
- automatic ring-back;
- prepared follow-me;
- do not disturb;
- group absence;
- group follow-me;
- manager/secretary absence;
- prepared follow-me;
- night extension absence;
- call forwarding on busy.

1.1.13. Group Features Collection

Introduction

This is a collection of functions and features that allow users to create a working
environment that is tailored to their specific requirements. The group features
collection can be used to compete against dedicated key system solutions. For more
information, please refer to the Voice Facilities - Explained manual.

A group arrangement is usually a number of extensions that belong to people sharing

the same work. For an executive/secretary relation an executive/secretary
arrangement is made next to the group arrangement. An extension can belong to
more than one group arrangement. The extensions still retain their own facilities as
individual extensions.

The group features collection offers the users freedom in call handling:

- The user can, based on his priorities, determine the sequence in which he answers
the incoming calls.
- Business priority may even lead to making an outgoing call first, before answering
the already ringing incoming calls.

16
- Parking/unparking calls enables the user to continue normal work after initial
answer of the call until the caller can be served. The common park position can
also be used for transferring calls within a group.
- Private number provides direct access to a person for a selected number of
important business- or family relations.
- Group members serving a number of DDI numbers can set their priorities in
answering calls. The group members can back each other up during short
absences and still answer calls with the appropriate announcement.

Groups can consist of analogue and digital extensions, freely mixed. However, the
elements of the group features collection are particularly powerful in combination with
Philips' ErgoLine D340, D330 or D325 telephone sets. A number of features require a
telephone set with programmable function keys with lamps.

The following types of group arrangements can be distinguished:

1. Group created with OM command CRGRPA.

2. Executive/secretary pool created with OM command CREXSE.
3. Enhanced executive/secretary group created with OM commands INESGR and
CRESGR. This is also known as the group features collection.

17
 Feature Group Executive/ Enhanced executive/
secretary secretary
Abbreviated access + + +
Absent/present switching + + +
Alternative secretary - - +
Break-in - + -
Call forwarding + + +
Call pick-up + - +
Door lamp * * *
Do not disturb + - -
Executive line position - - +
Group display + - -
Group key * - -
Group ring * - +
Group supervisor + - -
Hunting + - -
Intercom * * *
Line position - - +
Park + - +
Private number * * *
Progressive enquiry - - +
Second bell * * *
Status display * * *

Table 1-1 Overview of groups and features.

*) When an ErgoLine is used.

During creation, characteristics are given to the arrangement:

Group arrangement characteristics:

18
1. Group-DNR
2. Group-properties
- Empty group allowed
- Group Hunting
- Hunting Sequence
- Automatic Camp-on-Busy
- Call Pick-up
- Pick-up to Group only
- Observation Group
An observation group cannot really be considered as a group arrangement. It
is only a way of relating a number of extensions together for traffic
measurement purposes. Traffic measurement only allows the measurement of
the traffic for all extensions or for a specific group of extensions in a unit. If the
measurement on all extensions is not required an observation group is created
with the extensions to be measured. An observation group does not allow any
other group features. The members act as normal stand-alone extensions.
- ACD Group
3. Group-Display
4. Supervisor-DNR
5. Park position
6. Extended properties
- Line position status prevails extension status
- No re-route after transfer
- Hold tone after transfer
- LED based status monitoring (see section: "status monitoring" of chapter 3)
- Inhibit diversion of member-member calls
- Inhibit operator assistance (can only be set for ACD groups)
- Unrestricted call pick-up allowed

Executive/secretary arrangement characteristics:

1. Call forwarding on busy executive to secretary

2. Secretary allowed to switch absent
3. Single executive pool
4. Single secretary pool
5. Busy indication when executive and secretary busy
6. Executive line position pick-up by related executives allowed
7. Executive line position (this feature is used in the enhanced executive/secretary
group)

Enhanced executive/secretary arrangement characteristics:

19
 1. Group-DNR
2. Executive/secretary arrangement characteristics as shown above
3. Switch allowance for all members
4. Line position status prevails extension status
5. Re-routing after transfer prohibited
6. Hold tone after transfer
7. LED based status monitoring
8. Inhibit diversion member-member calls
9. Unrestricted call pick-up allowed
10. Call forwarding on busy executive to secretary
11. Secretary allowed to switch absent
12. Busy indication when executive and secretary busy
13. Common park positions
14. Line position for executives
15. Line positions for secretaries
16. Private park positions for executives
17. Executive line position for executives

Meaning of the Features

This section tells you what the features listed in the previous section mean. Also other
features that can be very useful in a group or executive/secretary arrangement are
mentioned.

Abbreviated access (or Short access code)

Old fashioned facility for rotary dial telephones. Members can call each other using a
short code.

Absent/present switching

To prevent the telephone from receiving calls. Absent group members are excluded
from hunting. Executive do not disturb: An executive wishing to be undisturbed or
wishing to leave the extension, can switch absent. Incoming calls are then re-routed
to the secretary. Secretaries may be prevented from switching absent. If allowed, the
remaining secretaries handle incoming calls. Secretaries can switch the telephone set
of the executive(s) absent or present. First she presses the Show Absent/Present Key
and then she can press the relevant executive's key(s) to change the status.

Alternative secretary

To transfer duties and functionality (break-in and overrule executive absence) to

20
another secretary (or executive).

Auto answer

This is not a group feature but can be very useful within groups. It allows incoming
calls to be automatically answered in handsfree mode.

Break-in (or Intrude)

To break-into another member's telephone conversation. The break-in cannot be

prevented by the break-in protection mark. However an active data protection mark
still prevents the break-in.

Call forwarding when absent or busy

If all members of the group have gone absent or are busy, calls are redirected to
another number. The following relations can be defined:

- Call forwarding on absent group member;

- Call forwarding on empty group;
- Call forwarding on group overflow (ACD group only);
- Call forwarding on group in night service (ACD group only).

The call forwarding destination can be an extension or an operator, a trunk access

code + external number, a paging number or a DPNSS number. In addition, other
redirection facilities are available to the members separately.

Call forwarding when busy

If an executive is busy, incoming calls to the executive are redirected to a secretary.

Call pick-up

Calls to a group member going unanswered may be intercepted by another group

member. A call can be picked up if it is made by dialling the group number (general
call pick-up) or the member number (selective call pick-up). The group display facility
is particularly useful here, since members of a group may not necessarily be able to
hear other group members' extensions ringing. Unrestricted call pick-up: any
extension in the unit can pick-up a call to the group.

'Called by' indication

A key lamp shows the secretary which executive is calling her.

21
 'Calls for' indication

If a secretary receives a call intended for an executive, a key lamp on her telephone
set shows which executive was the intended destination.

Common park key see Group park

Do not disturb (DND)

To (temporarily) block extensions for all incoming calls. A present group member can
activate DND for his/her own extension or for the whole group. To activate DND for
the whole group, the member must dial the "Dial for group prefix" followed by either
the "Set don't disturb" code or the AEM prefix. The group DND condition:

- can only be monitored by Computer Supported Telephony Applications (CSTA);

- is not displayed at an extension LED;
- is not signalled to the group members with the diversion active dial tone.

When DND has been activated on an individual extension in a group arrangement, the
group member is not selected (skipped) when calls are made to the group DNR and
the member presence status of the group member is set to Absent.

Door lamp

To activate a do-not-disturb lamp outside the door. A hardware connection must be

made between the telephone set and the door lamp. A door lamp key can be defined
to control the door directly: press the key and the lamp goes on; press the key again
and the lamp goes off. It is also possible to select the 'follow on/off hook' function from
the ErgoLine menu or by using a function key with this feature. By using this feature
the door lamp goes on when the telephone set is off hook and goes off when the
telephone set is on hook.

Downloading of function key data

A standard executive/secretary arrangement can be defined using Operational

Maintenance commands. This arrangement contains 5 executives and 5 secretaries.
A standard function key menu is defined for downloading the telephone sets. In this
way a 'fixed' function key layout for the telephone sets involved is created. For smaller
groups (i.e. less than 5 executives/secretaries) less of the keys are used, the
remaining keys can be programmed for any other function.

Executive key see Executive line position

22
Executive line position

To answer incoming calls for an absent or busy executive. An executive line position
has the same function as a line position, except that it relates to calls diverted from an
absent (or busy) executive. The status is signalled to all the executives and to all
secretaries.

Follow-me secretary to executive

If a secretary has set a follow-me to the executive, calls for the secretary are routed
to the executive extension. If the executive has switched absent then the calls are not
diverted from the secretary's extension.

Group call respect extension facilities

If a call to a group arrangement is made and the facility class mark 'Group Call
Respect Extension Facilities' is assigned to the individual DNR of the selected
member, then the facilities 'Do Not Disturb' and 'Twinning' are taken into account. This
means that if the selected extension has a local twinning relation (i.e. located in the
same multi unit node), then the status of that relation is checked. So, if the twinned
relation is busy then the selected extension is skipped and the next extension in the
hunting cycle is searched. If the selected extension has a non-local twinning relation,
then the call is set up to both the extensions. In the same way, when a call is made to
a group arrangement and a member of that arrangement has activated 'Do Not
Disturb', then that member is skipped during the hunting cycle.

Note that this only applies to a non-multiple ring group, i.e. a group arrangement with
hunting type Fixed, Cyclic or Longest Idle Member.

Group display

This feature is only used when the group contains SOPHO-SETs of release 1 or
SOPHO-SETs being connected to a DLC-A/B, which must be able to monitor the
status of fellow group members.

Group observation see Status display

Group keys (or Multi-line answering)

Several direct dial in numbers can be allocated to a group. Each number represents
a service offered by that group (e.g. sales enquiries, invoice enquiries etc.). If a group
member uses a feature phone then incoming calls are signalled even if the member
is busy with another call. The user can park the current call and answer the waiting

23
 call. This feature uses 'Status display' functions for presentation, and 'call pick-up' for
answering.

Group park (or Common park or Park and walk)

To park a call which has to be handed over to another member. The group can have
9 park positions. A call placed in a group park position can be picked-up by any
member of the group. Note that group members should have the group park key on
their telephone set.

Group ring see Soft ring

Group supervisor

The supervisor can receive extra information, on the display of the telephone set,
about the group i.e. the number of absent and present members and the number of
calls in the group camp-on-busy queue. The group supervisor can switch group
members present or absent.

Hunting sequence

When a call is made to the group number, the ISPBX 'hunts' for a free group member
to receive the call. The hunting sequence can be fixed, cyclic, multiple ring group or
longest idle.

1. If a fixed sequence is adopted then for each new call, hunting starts at the top of
the list of group members. The consequence of this is that members of the group
at the top of the list tend to receive more calls than those lower down.
2. If a cyclic sequence is adopted each new call is distributed to the next free
extension. This implies that calls are distributed equally to all members of the
group.
3. An incoming call to a multiple ring group causes the telephones of all available
members to ring simultaneously.
4. The longest idle sequence is only used for ACD groups. The ISPBX starts hunting
at the group member that has been idle longest.

Calls made to the group member's personal extension number are not distributed. If
the member is absent and the call forwarding on absent group member number is
defined, the ISPBX forwards the call.

Intercom

To make a call to a member without that member having to lift the handset to answer

24
the call (only if they both have ErgoLines or SOPHO-SETs). If an executive and
secretary are also assigned to a group arrangement they can use this facility.

Line position

Each member of the group can be allocated a Line position. This can be seen as a
fictitious extension of which the status can be monitored and from which a call pick-up
can be done. A function key on the group member's telephone set is used as Personal
key. To answer a call on the line position, the group member presses the Personal key
while its lamp is flashing.

Manager key see Executive line position

Member key

To pick-up an incoming call for a member or to call the member. The key also shows
the call status (idle, busy, ringing) of that member.

Monitoring see Status display

Multi-line answering see Group keys

Park key see Private park or Group park

Personal key

To answer incoming personal calls.

Preferred secretary

When an executive is assigned, this executive is also assigned a preferred secretary.

This secretary extension will be dialled first in the case of re-routed calls. If the
preferred secretary cannot be accessed, then another secretary out of the
arrangement is dialled.

Private number key

An executive can have a second (private) telephone number on which this executive
can be called without being affected by the secretary. This telephone number is not
controlled by the executive/secretary arrangement. Calls can come in, even when the
executive is switched absent. It is possible to give a member a 'private' number by
defining the number as a group member for which no hardware exists. The executive
must have a key on the telephone set for this 'fictitious' number. The executive then

25
 publishes two numbers. The first is the real number which is freely published, the
second is the fictitious number which is only given to a few people, for example special
customers or family members.

Private park key

To temporarily park private calls. Each member of the group can have 2 park
positions. A call placed in a private park position can only be picked-up by the member
that parked the call. The caller receives hold tone or music on hold (if available). The
lamp of the key starts flashing showing that the park position is occupied. The group
member is free to make or answer another call.

Progressive enquiry

To transfer calls to another group member under any circumstances. If a group

member is the destination of an enquiry call, this group member can initiate enquiry to
another group member. An example:

1. Party A is in conversation with party B. Party A goes into enquiry.

2. Party A receives dial tone and party B is placed on hold. Party A dials party C.
3. Party A is now in conversation with party C. Party C can now go into enquiry.
4. Party C receives dial tone and party A is placed on hold. Party C dials party D.
5. Party C is now in conversation with party D.

Now there are the following options:

- If party A goes on hook, then party B will be placed on hold at party C;

- If party B goes on hook then the original call is lost;
- Party C can shuttle between party A and party D. If party C goes on hook, then
party A will be connected to party D;
- Party D is in conversation with party C. If party D goes on hook then party C can
be reconnected with Party A. Party D can go into enquiry and dial another party.

Interaction with Call pick-up: A call made using the Progressive Enquiry facility can be
picked-up if the called extension is in a call pick-up group.

Selective answering

One or more calls can be 'ringing' on the secretary's extension i.e. several key lamps
can flash. The secretary can select which call is answered first.

Second bell

26
If a second bell is connected to the telephone, this remote bell signals an incoming
call. The user can switch this function on and off. The second bell is controlled via the
static interface.

Second line answering

If a call is camped on to a busy executive, a call waiting indication is given. The

executive places the current call on hold and answers the waiting call, which can then
be handled directly or passed to an available secretary. If a call is camped on to a busy
secretary, a call waiting indication is given. The secretary places the current call on
hold and answers the waiting call, which can then be announced to an executive and
passed through.

Short access code see Abbreviated access

Soft ringing

The user can select soft ringing to correspond with a flashing lamp (i.e. a call is waiting
to be answered. This is very useful for call pick-up functions.

Status display (or Group observation or Monitoring)

Visual indication of the status of some or all of the members of the executive/secretary
and group arrangement. A key on the telephone set corresponds with one of the
members of the arrangement. The lamp of that key indicates the status of the
member's extension (idle, ringing or busy). This key is also used for access to the
other member. When the lamp is off, pressing the key sets up a call to the other
member. Another key must be programmed to indicate the absent/present status of
other group members (lamp off: member present; lamp on: member absent). There
are two types of monitoring:

- LED based monitoring

This type of monitoring is restricted to group arrangements, because a LED code
can only identify a fellow group member. SOPHO-SETs of release 1 or SOPHO-
SETs connected to a DLC-A/B only support LED based monitoring.
- DNR based monitoring
This type refers to the items to be monitored by DNRs and can therefore be used
throughout the unit (unrestricted monitoring). Default the ISPBX is set to DNR
based monitoring.

Supervisor see Group supervisor

Unrestricted call pickup

27
 Call-pick up is also possible for extensions outside the group of the ringing extension.
This feature can be a welcome solution for people sitting in one room, who do not
belong to the same group.

Unrestricted status monitoring (or unit wide monitoring)

This feature is not restricted to group arrangements. The ISPBX can send status
information of extensions (and/or trunk lines) to any internal user who wants to monitor
such an item. Status information is sent to a telephone set if a key has been
programmed for an extension (or for a trunk line). If this extension is a group member
and the group allows 'Unrestricted call pickup', then it is also possible to pick up calls
for that group member.

Configuration and Installation Aspects

Some of the features have to be assigned to the terminal via Operational

Maintenance.

FCM 19, group member.

FCM 21, executive.

FCM 22, secretary.

FCM 72, group call respect extension facilities. Must be assigned to group members
that use 'Do Not Disturb' and 'Twinning'

Boundary 15, Maximum number of secretary groups, 01000.

Boundary 17, Maximum number of groups arrangements, 01000.

Boundary 219, Maximum number of members, 25000 (2600 in case of CPU3000).

Boundary 220, Maximum rank number of the group members, 064.

Boundary 291, Maximum number of status monitoring items, 010000.

All secretaries must be located in the same unit in the network. The executives may
be located anywhere in the network.

Users do not have to program their terminals. The function keys of the ErgoLines can
be programmed by downloading the information (facility activate and cancel codes
and LED codes to activate the status lamps). The terminals do not have to be
programmed one by one, they can be programmed in groups (provided they need the

28
same data to be stored under the function keys). A function key menu contains the
data for a terminal's function keys. Function key menus are created and modified
using an OM-command. Another OM command specifies the relations between
terminals and function key menus. The function key menu can be downloaded at
several moments:

1. At activation of the terminal;

2. When the extension user performs a manual download request;
3. Forced with OM;
4. Using the Desksharing or installation facility (system option 58).

For users it is convenient to have the function keys related to fellow group members
programmed with telephone numbers. The name/number expansion will then work as
expected by the user. However, for the system managers it is more convenient to
have the function key menus programmed with the rank numbers which are derived
from the group arrangement. This allows them to use the same function key menu for
similar group arrangements.

To combine these two wishes the ISPBX translates function codes related to rank
numbers, into telephone numbers of the corresponding group members. The function
key menus can be filled based on the rank numbers of the group members. The
corresponding telephone numbers will be used when downloading the contents of the
function keys of the feature phone.

Boundary 96, maximum number of function key menus, 1255.

Boundary 176, system limited number of function key. This should be 2.

Boundary 181, system limited number of level 0 function keys.

Boundary 182, system limited number of level 1 function keys.

Boundary 183, system limited number of softkeys. This defines the maximum number
of entries for prefix data like for example the call pick-up code, break-in code, etc.

System option 58, desksharing automatic download function key menu.

An Example

This section describes how the group features collection can be implemented in a
realistic environment. As an example we took the management department of a
fictitious company, one secretary (Sharon) and two executives (Mr. A and Mr. B).
Each member has an ErgoLine D340 programmed with the following keys:

29
 Figure 1-1 Telephone layout of the secretary and the executives.

Executive key: to answer calls diverted from an absent executive. Diverted

calls are signalled on both the executive's and the secretary's
extension.
Member key: to pick up a call for or from a group member;

to make a call to a member or executive (if the key is also

programmed as intercom key, then the call is automatically
made in handsfree mode);

to show the status of the member's telephone (idle, busy,

ringing);

to show the absent or present state when the Show absent/

present key is pressed.
Personal key: to answer incoming internal and external personal calls.
Private key: to answer incoming calls on the executive's second telephone
number. Only the executive has this key on his telephone.

30
Private park key: to park/retrieve calls. The private park key can only be used by
the person to whom the private park position has been
assigned.
Group park key: to park/retrieve calls. All members to whom the group park key
has been assigned can use this key to park and retrieve their
own and other group member's calls.

A working day

Because of the fact that Mr. A and Mr. B both want Sharon to Switch absent and
handle their calls, their telephone sets are always switched present
absent.

A call for B comes in. Sharon is just reading the mail and she Group ring
hears her phone ringing softly. A three-beep tone indicates
that a call for B is coming in. The lamp in the executive key of
B is blinking. She picks up the handset and presses the key.
It is Mr. C.

While Sharon is talking to Mr. C, a call for Mr. A comes in.

That is indicated by a double soft ring tone and by the blinking
lamp of his executive key. Sharon tells Mr. C that she will put
him through to Mr. B.

Sharon parks Mr. C by pressing the group park key next to Group park key
Mr. B's executive key. She arranged with Mr. B that when the
lamp of that key starts flashing, she has put a call for him
there. From this moment on, Mr. B can pick up the call from
that key (if he notices the flashing lamp or if he activated soft
ringing).

Then Sharon answers the call for Mr. A by pressing his Normal transfer
executive key. It appears to be an important customer who
wants to speak to Mr. A. She puts the customer on hold, calls
Mr. A by pressing his member key and puts the customer
through by replacing the handset.

31
 Sharon sees the lamp of Mr. B's group park key is still Intercom call via
flashing. She makes an intercom call to him by pressing his member key
member key. Sharon tells Mr. B that Mr. C is waiting for him
under his park key. She presses the loudspeaker key to break
off the call.

Mr. B picks up the call by pressing his group park key. Sharon Group park pick-up
sees that the lamp of the group park key is off and the lamp
of Mr. B's member key goes steady on to indicate that he is
busy in a conversation.

At that moment another call for Mr. B comes in. He is still busy Break-in softkey
talking; the lamp of his member key is still on. Sharon picks
up the call and asks the caller to wait. She puts him on hold.

She presses Mr. B's member key and hears busy tone. She
breaks into the conversation. Both Mr. B and Mr. C can hear
her. She tells Mr. B that an important call came in, which she
wants to put through.

Sharon replaces the handset and automatically the call is Automatic camp on
transferred to Mr. B. Because he is busy, the call is put into busy
the call-waiting queue of his phone. At this moment he can
decide for himself which call to finish first.

Mr. A switched his telephone present because Sharon has to Switch absent and
leave early. present

He has just looked up the number of the New York Times in Starting an outgoing
the directory of his telephone and wants to call them. At that call while another call
moment a call for him comes in. His personal key starts comes in
flashing and his phone rings softly. Sharon sees the lamp of
Mr. A's member key flashing. Mr. A decides to make that
planned call first and lifts up the handset. The telephone
starts dialling the number while the personal key keeps
flashing.

32
In spite of the fact that Mr. A is busy, his member key on Call pick up
Sharon's telephone keeps flashing. Now Sharon still sees
that a call is coming in. Because Mr. A does not answer the
call, she decides to pick it up by pressing the key and lifting
her handset. At that moment the lamp of Mr. A's member key
lights to indicate to her that he is busy.

It is Mrs. D. Sharon tells Mrs. D that her boss is busy in a call Hold the call
at the moment and asks her if she wants to wait. Mrs. D, an
influential journalist for the Washington Post, is in a terrible
hurry because she urgently needs information from Mr. A to
put in the evening paper. Sharon knows that this is important
so she tells Mrs. D she will do her best. She puts the call on
hold.

She breaks into Mr. A's conversation by first pressing his Break-in
member key (she gets busy tone) and then pressing the
break-in key. In a three party call she tells Mr. A that she
wants to transfer a very important call to him.

He thanks her for the information. She puts down the Transfer a call to a
handset. Now Mrs. D is transferred to Mr. A and hears busy busy extension
tone. Mr. A parks his first call by means of his private park
key. From that moment on only he can pick up that parked
call. His telephone starts ringing to announce the waiting Mrs.
D.

1.1.14. Hot Line

The system can establish a connection to a predefined destination number when the
handset is lifted. The destination number can be an internal or an external number.

• Direct Hot Line

In this case, the extension user lifts the handset of the telephone, does not receive
dial tone and the system activates the hot line mechanism immediately.
FCM 17, hot line, assigned to an extension once the originator/destination relation
has been defined by the system manager.
• Delayed Hot Line
In this case, the extension user lifts the handset of the telephone and receives
delayed hot line dial tone. The user can now make a normal telephone call.
However, if the user waits for a certain period without keying in any digit, the

33
 system activates the hot line mechanism.
Timer 008, hot line delay time, 3...8 seconds.
FCM 18, delayed hot line, assigned to an extension once the originator/destination
relation has been defined by the system manager.

This facility is available to extensions.

Boundary 13, maximum number of hot lines, 0...512.

1.1.15. Intercom Call

The intercom prefix allows extension users that are not part of a group arrangement,
to make an intercom call. This facility can be very useful in a hospital. A patient alerts
a nurse. Before hurrying to the patient, the nurse can make an intercom call first. The
nurse dials a prefix (or uses the intercom key if available) followed by the DNR of the
patient. The patients' terminal automatically goes to loudspeaking mode. When the
nurse ends the call, the patients' terminal automatically goes on-hook.

The called party must have a feature phone. A feature phone is an ErgoLine D325,
D330, D340 or a SOPHO-SET P370, P375, S375.

An operator can not make or receive intercom calls.

It is not possible to set up an intercom call to a group number.

FCM 67 intercom call entitled, the calling party.

FCM 68 intercom call allowed, the called party.

1.1.16. Last External Number Repetition

The user dials a code and a call is set-up to the external party that was last dialled.

FCM 01, IABD and LENR, assigned to an extension.

System option 16, IABD allowed for operators. Defines whether Individual
Abbreviated Dialling and Last External Number Repetition is available for operators.

1.1.17. Malicious Call Trace

This facility is used to determine the identity of an external call to an extension.

Initiating a malicious call trace request is done by switching to the enquiry state and
dialling the 'malicious call trace' code. The user can then disconnect the call.

34
The identity of the calling party, if known, is noted in a call record together with some
additional information related to the malicious call trace request. In the case of an
incoming call over a trunk or tie line not supporting calling party identity, the route and
line number are noted. If the trunk line supports malicious call tracing, the system also
sends a request to the opposite exchange (via the trunk line) to identify the calling
party connected to the trunk line.

FCM 11, preferent to operator (extensions with this FCM can initiate malicious call
trace).

1.1.18. Multi Line

Users of the ErgoLine D340, D330 or D325 can monitor the status of trunk lines. The
lamp of a dedicated key shows if a line is idle, busy, parked or if a call comes in. By
pressing the key the user performs the required action. In addition to the line statuses
distributed by the ISPBX, the ErgoLine may supplement these with line statuses Busy-
by-me and Parked-by-me.

When a lamp indicates that a line is idle, the user can press this line key and optionally
enter the required (external) number.

When the user is in conversation via a line for which there is a key and that key is
pressed, then the ErgoLine parks the line call and starts enquiry. A line which has
been parked can be picked up again from the terminal that parked the call or from
another terminal (that has the same line key). The lamp of the line key will go on.

When a lamp is flashing fast or slow, there is respectively an incoming or parked call.
The user can press the line key to answer the new call or pick up the parked call.

Other functions provided are:

- Music on hold to a parked caller;

- Diversion to e.g. the operator when an incoming line call is not answered within a
predefined period of time;
- User identity (CLI/COL) send to the ISDN trunk line (can be projected per line);
- Multi line functionality for internal calls (by means of a digital loop).

There are 2 types of line numbers; real line numbers and virtual line numbers. A real
line number is a line number that is directly assigned to a trunk circuit or B-channel of
an ISDN trunk circuit. A virtual line number is a line number that is dynamically
attached to a trunk circuit during a call. A virtual line number offers the multi line
functions for ISDN calls in a way that is independent of specific B-channels and

35
 specific trunk accesses.

It is possible to handle multiple simultaneous DDI calls to the same DDI number. In
this case there should be as many consecutive virtual line numbers assigned for that
particular DDI number as the number of simultaneous DDI calls to this shared DDI
number that must be monitored.

CLI/COL identity:

Line CLI/COL Identity is particularly useful when virtual line numbers are used. In case
of an outgoing call, the CLI/COL-identity of the selected line is used as Calling Line
Identity (CLI), replacing the number of the calling extension. In case of answering an
incoming ISDN trunk call, the CLI/COL-identity of the line is used as Connected Line
Identity (COL). In practice several persons will monitor a line. The number of the
extension on which the call is answered, will most of the time not be the same number
as the called number. Now by assigning a 'CLI/COL identity' to the trunk line, this
identity will be passed on to the caller.

Internal line:

Multi line functionality usually handles trunk lines. However when replacing a network
of iS3000 and satellite multi line systems by an integrated iS3000 solution, it may be
required to use the multi line functionality for internal lines; i.e. ErgoLine-A has a line
key which is exclusively meant for the 'internal line' to ErgoLine-B, and vice versa.
These internal lines are realised by using digital loops.

The following configurations are possible:

1. One-to-one in the same ISPBX unit;

For this configuration the internal line is realised by using 1 digital trunk loop
connecting two trunk lines. Two DTX-I circuits are connected to form 2 digital loops
(2 B-channels per circuit).
2. One-to-one not in the same ISPBX unit;
For this configuration the internal line is realised by using 2 digital trunk-extension
loops; one per line key.
3. One-to-many.
For this configuration a digital trunk-extension loop is required per line key. The
digital trunk-extension loop consists of trunk-line 1 wired to an extension circuit
with DNR-A1. Extension A monitors internal line 1 with line-key 1. Extension B is
one of many simple extensions.

Line access to a fixed number in the PSTN:

36
A line key can be used to call a fixed number in the PSTN. The ISPBX provides the
external number instead of the user.

A line key can be used for line access in one of 2 ways:

1. General line key: the line key is used to communicate with several persons. After
pressing the line key the user dials the required number.
2. Dedicated line key: the line key is used to communicate with only 1 person. The
user only has to press the line key. In this case the configuration of the external
trunk line is relevant:
- The trunk line can be directly connected to the destination, e.g. via a leased
line. Pressing the line key sends a line access prefix including the line number,
and the ISPBX makes an outgoing call on the trunk line.
- The trunk line can be connected to the PSTN. The ISPBX sets up a call to a
specific external number.
Restrictions:
The terminal and trunk circuit must be assigned to the same ISPBX unit. The trunk
circuit can be of signalling type keytone, impulse, ISDN, DASS2, MFC-R2, MFC-
socotel, MFE and MFP. DPNSS and DPNSS-PVN are not supported. Application
of the CLI/COL-identity of a real or virtual line is supported on ISDN trunks only. In
case of line access to a fixed number: the maximum size of the expanded number
is 20 digits, including the line access prefix of 6 (or 5) digits, leaving 14 (or 15)
digits for the external number. If 14 (15) digits is not enough, outgoing digit
conversion can be used to dial a longer external number (up to 32 digits).

FCM 63, Multi line entitled.

System option 119, Unique line numbering.
Boundary 291, maximum number of status monitoring items.
Boundary 357, maximum number of virtual lines.
Timer 221, Line Park Incoming Call Guarding Time.
Software licence 31, Multi Line for ErgoLine D340.
Software licence 32, Multi Line for ErgoLine D340 and D330.
Software licence 33, Multi Line for ErgoLine D340, D330 and D325.

It is strongly advised to have a licence for each ErgoLine that has FCM 63 assigned
to it. The multi line licence is only given to a terminal when it is in-service (and of the
right type of ErgoLine and having FCM 63). This has the following consequences:

- The order in which these ErgoLines come into service e.g. after a warmstart,
determines the order in which the multi line licences are allocated.
- At unplugging an ErgoLine, its multi line licence will be freed and it will be allocated
to another ErgoLine when possible. When the ErgoLine is plugged-in again there

37
 may be no free multi line licence available anymore.
- An autonomous system assurance test may autonomously block the circuit of the
ErgoLine for a short period, thereby freeing the multi line licence, which may then
be allocated to another ErgoLine. When the circuit is put in-service again, there
may be no free multi line licence available.

1.1.19. Multi-Party Calls

• Add-on Conference
This feature enables an extension user to set up a 3-party conversation. During
the add-on conference an add-on ticker tone is sent to all three involved parties.
Ticker tone can be disabled system-wide.
The initiator dials the add-on prefix, when in enquiry, followed by the number of the
second destination party. On answer, the initiator presses the enquiry button
again.
The add-on conference can involve three extensions, two extensions and an
external party or one extension and two external parties. An operator cannot be
involved in an add-on conference.
If one of the parties releases, the add-on conference will be ended and the system
will establish a normal speech connection between the two remaining parties.
FCM 00, add-on entitled, allows an extension to set up an add-on conference.
• Multi Party Conference
This facility allows more than 3 parties to be connected together. A conference
group with up to 8 participants uses 1 conference circuit board. The maximum
number of conference participants or conference groups depends on the number
of conference circuit boards. The boards can be interconnected (via hot lines) to
create a large conference circuit complex. See also section 2.4.14. "Conference
Circuit".
A conference supervisor can be nominated to assemble and monitor a
conference. Conference supervisors have a 'conference key' and a 'conference
initiator/release key' programmed on their telephone set. The conference
supervisor calls each of the participants (in enquiry) and adds them to the
conference by pressing the conference key. The conference supervisor can
remove any or all of the parties.
It is possible to add yourself as conference leader of the conference by pressing
one key.
The participants in a multi party conference can be internal or external parties. An
external participant may be connected via an analogue trunk line. Analogue trunks
do not support a backward release signal. Therefore if this participant goes on-
hook during the conference, the PSTN will send busy tone for some time. This will
be heard by the remaining participants and disturb the conference for a while.

38
 Boundary 311, maximum number of chained direct diversions; 05.
Boundary 349, maximum number of conference group chains; 110.
FCM 64, conference supervisor.
• Break-In
This feature allows an extension user to interrupt a conversation when
encountering a busy extension by dialling the break-in code. If the request is
successful a three party connection is made. If the initial conversation is break-in
protected then call waiting is initiated and the busy party hears call waiting tone
burst.
Party A is in conversation with party B. Party C dials party A and initiates break-in.
This results in a three party connection. If party B now goes on hook then party A
and party C are automatically disconnected. Party C is put in the camp-on-busy
queue of party A. Party C waits on-line for party A to release the current call. If
party A goes on-hook, the telephone set starts ringing immediately and party C is
connected when party A answers. Break-in is not allowed if one of the parties in
the initial conversation is an operator or a trunk line in a route with break-in
protection or data protection.
FCM 02, break-in entitled.
FCM 03, break-in protected, against break-in by another extension, (but not by the
operator).
FCM 04, data protected, provides protection against break-in by another
extension, and by the operator.
FCM 05, data protected entitled, provides protection against break-in by another
extension, and by the operator. This can be switched on and off by dialling
prefixes.

1.1.20. Multiple Subscriber Number

It is possible to have Multiple Subscriber Numbers (MSN) on one and the same
extension interface. In SOPHO terms, this means that multiple directory numbers
(DNRs) can be assigned to one External HardWare Address (EHWA). This
addressing scheme also allows different terminals on the same extension interface to
share one directory number, each with individual user profiles (DNR/service
combination).

A summary of the MSN features:

- Free directory number allocation per terminal or multiple terminals up to 8 per S0-
access;
- Individual user profile per directory number/service combination.

The applications made possible with this new feature are manifold and include:

39
 - Two or more employees sharing one extension interface, each with a separate
directory number.
- Second directory number for private calls (also non-S0 extensions).
- Multi-number help-desk served by one single extension (also non-S0 extensions).
- Multi-group.

The possibility to assign multiple directory numbers to one extension interface is not
only restricted to terminals connected to the S0 as analogue line circuits and the
SOPHO-SET S and K range of business telephones.

The implementation of the MSN concept is explained in the following paragraph. This
description has been generalised as much as possible to ease its comprehension but
is still rather detailed in order to emphasise its potential impact. Given description is
however by no means exhaustive.

• BSPT Addressing Procedure

This procedure makes use of so called Basic Service Profile Identifications (BSP-
ID) instead of directory numbers. Such a BSP-ID combines a directory number and
a Basic Service Profile Type (BSPT) to refer to the entire profile of a user terminal.
A BSPT specifies the basic service supported by the terminal, which can be for
example speech, 64kbps data, audio 3.1kHz, G4 facsimile or videophony.
Next to a directory number and a BSPT, a BSP-ID also contains the user
dependent characteristics such as:
- Traffic classes: day, night, upgraded, downgraded;
- Facility class marks: break-in entitled, data protected, CLI permanently
restricted, call forwarding destination, follow-me entitled etc.;
- MSN mode (only in case of S0 combi-bus terminals).
The logical connection of a user terminal to a physical extension interface, is done
by allocating its BSP to an EHWA. With this addressing procedure, multiple BSPs
can refer to the same physical circuit. This provides the possibility to have multiple
terminals with different characteristics sharing the same interface.
• Terminal Configurations on S0 Combi-bus
Although the addressing mechanism is also applicable on analogue ports, its main
application area is to be found behind the S0 combi-bus. In this case, any
conceivable combination of terminals and services is possible. Some typical
examples are listed and shown in figure Figure 1-2 "Multiple Subscriber Number
(MSN).".
a: Same directory number for multiple terminals supporting different services (e.g.
a user with an ErgoLine, a G4 facsimile and an ISDN PC);
b: Different directory numbers (max. 8) for various terminals supporting the same
service (e.g. 3 telephone users sharing one S0 interface or a user with an

40
 additional private number);
c: Any combination of the above (e.g. a user with an ErgoLine and a fax and a
second user with a telephone set).
• Terminal Addressing Procedure on S0 Combi-bus
Supporting multiple terminals on the same interface requires a special addressing
mechanism to select them individually. The way this is done is, as explained
hereafter, dependent on the configuration used:
a: The terminals are selected by means of their individual service type as specified
in the BSPT (e.g. an incoming "Telefax4" call is only alerted at the G4 fax
machine), or
b: the terminals are selected by using their individual terminal identifier. This is
either a so called TEI in the case of an ErgoLine or SOPHO-SET P37x(D) or a so
called MSN number in the case of an ISDN terminal (e.g. an incoming "speech"
call with TEI=0 will only be alerted at the ErgoLine or SOPHO-SET P375), or
c: the terminals are selected with a combination of the above.
The Terminal Endpoint Identifier (TEI) must be programmed in the ErgoLine/
SOPHO-SET/LAM and determines the B-channel used (i.e. TEI=0 uses B0 and
TEI=1 uses B1). This B-channel is then dedicated to the terminal and cannot be
used by other equipment.
In the case of an ISDN terminal, the MSN number is used as an addressing
mechanism. There are two possibilities:
- The MSN number represents the last digits (up to 6) of the user directory
number (standard ISDN way);
- The MSN number has no relation with the user directory number. It only has a
local significance (formerly called EAZ). The MSN can be up to 6 digits.
In the first case the MSN number must be programmed in the ISDN terminal. This
MSN number can be up to 6 digits long and is read by the terminal to recognise an
incoming call and is sent to the system to specify the source of an outgoing call. It
must be noted that the MSN number is only used to identify the terminal and not,
as in case of a TEI, to select one of the two B-channels. The latter is performed
dynamically at call set-up time.
The second case is the default setting of SOPHO and is used to discern the
terminals with a local addressing mechanism. Each terminal receives an MSN
number (formerly called EAZ), which is added to its BPS-ID and programmed in
the terminal before operation. This procedure is the same as the former EAZ
(Endgerate-AuswahlZiffer) procedure and is therefore downwards compatible with
such installations. This procedure has the advantage that only one digit has to be
programmed in the terminal and that the directory number does not depend on the
other terminals on the same S0 interface. A drawback is that it is less easy to
configure. In case (1), programming the MSN number can be made part of the user
installation procedure of an ISDN terminal since the MSN is the same as (a part

41
 of) the user directory number. In case (2), this is less likely to be possible since the
user does not know which number to program, meaning that this task must be
done by an installation engineer.

Figure 1-2 Multiple Subscriber Number (MSN).

1.1.21. Password Protected Facilities

Access to some features or destinations may be password protected. Password

management can be controlled by the system itself using Integrated Password
Dialling (IPD) or by an external management system. The features offered by IPD and
an external management system are summarised hereafter:

42
FEATURE IPD (ISPBX) SysManager
Budget control - +
Cost Centre dialling + +
Password Up/Downgrading of Traffic class + +
Password DDO + +
PID dialling + +
Password port protection

- direct - +

- call back - +
Number of passwords, PIDs and Cost 6 000 > 10 000
Centre codes
Check on the number of wrong attempts - +

Table 1-2 Password protected features.

• Budget Control
A cost centre or personal account user can be allocated a credit limit for password
dialling of external numbers. If the credit limit is exceeded then no new calls can
be made.
• Cost Centre Dialling
An extension user can make an external call and allocate the call cost to a
particular cost centre number, by dialling a prefix, the cost centre number and then
the external number. The cost centre number can be 1...12 digits. A cost centre
dialling call is always subject to call recording. No traffic class upgrading takes
place.
• Password Dialling
An extension user can initiate a password call by dialling a prefix followed by a
password. The password is validated, and if the validation is correct, the user can
use the password facility. A password call is always subject to call recording.
Software licence 12, integrated password dialling.
Boundary 275, maximum number of integrated passwords, 06000.
- Password Definition
Passwords are defined by the system manager and can be subsequently
changed (and verified) from the users extension, by dialling the appropriate

43
 prefixes. Passwords may be 1...12 digits.
- Password Up/Downgrading of Traffic Class
Each extension has four traffic classes, day, night, upgraded and downgraded.
The user can choose to use the upgraded or downgraded traffic class instead
of the day or night traffic class.
The upgraded or downgraded traffic class is selected using a prefix and a
password. The chosen traffic class remains in effect until cancelled by the
user. At night (when all operators are absent or according to the system night
timer), all upgraded traffic classes can be reset to the night level.
System option 85, upgraded traffic class autonomously to night.
- Password Direct Dial Out from Own Extension
This allows the user to upgrade the traffic class of his own extension to be able
to make one call to an external destination that would normally be restricted.
The user dials a prefix and a password and after validation dial tone is given.
- Password Direct Dial Out from Any Extension
This allows the user to upgrade the traffic class of any extension to be able to
make one call to an external destination that would normally be restricted. The
user dials a prefix, his own extension number and a password and after
validation dial tone is given.
The extension used is given the upgraded traffic class of the user's own
extension for the duration of the call. Call records are registered to the user's
own extension number.
• Personal Identification Dialling
PID dialling is used for the allocation of call costs to a particular person. This can
be either restricted to the person's own extension or available system wide. The
extension user dials a prefix, the PID number and then the external number. The
PID number can be 1...16 digits. A PID dialling call is always subject to call
recording in which the PID number is recorded. A special traffic class, usually a
high one, related to the PID is used for the duration of the call.
It is possible to assign a budget to a PID. When during a call, the budget is almost
zero, a warning tone will be given. When the budget becomes zero, the call is
terminated abruptly. No PID calls can be started anymore when the budget is zero.
The budget can be updated by means of OM commands. The budget is stored in
an iS3000 unit. This 'Call break at zero budget' facility runs in conjunction with
SysManager 410. This call break at zero budget can only be used for trunks with
metering.
There is also the facility 'Time based call break at zero'. This is an extension of the
facility 'Call break at zero budget'. This facility makes it possible to decrease the
budget on regular time intervals. With facility timing it is possible to decrease the
budget with different values on different time periods.
Boundary 354, maximum number of tariff classes, 0254.

44
• Private Call
This facility allows the user to make a call that is subject to call recording, but in
this case the dialled number is not registered in the call record. The extension user
dials a prefix followed by the external number and the call is marked as a private
call.
• Port Protection
In this case an extension is password protected against incoming calls. The caller
(internal party or DDI) dials a prefix, a password and the extension number of the
port to be called. After the password is validated the connection is made between
the calling party and the protected port. The connection can be direct or using
callback, depending on the prefix dialled.
FCM 38, direct access protected.

1.1.22. Post Dialling

Post dialling can be used in the following situations:

• Post Dialling after Busy Tone

If a party encounters a busy extension then the calling party can enter additional
digits, during busy tone, to invoke a facility (such as break-in).
• Post Dialling to Complete a Converted Number
With some facilities a user only needs to dial a certain prefix which is used to route
a call to a pre-defined destination. If the destination number is not complete, the
extension user must post dial additional digits to complete the destination number.
• Post Dialling to Control an Internal Device
When in speech condition with an intelligent device, such as a Voice Mail Server,
a user may need to give the device commands to perform a certain action.
Keytone post dialling is used to give commands to the device. Keytones are re-
generated by the system and sent to the device in the speech channel.
• Post Dialling to External
It is possible to control an external device reached via a trunk or tie line. The post
dialled digits can be transferred from the system to the opposite exchange in
keytone or impulse format. The system regenerates the dialled digits.

1.1.23. Priority Access to Routes and Trunks

This facility allows specific extensions to use reserved trunk routes. A separate route
table can be defined for priority extensions.

FCM 14, trunk priority.

45
 1.1.24. Routing Facilities

• DDI Barred
An extension can be prevented from being connected to specific trunk lines for
DDI. A DDI barred check can be specified for any incoming route.
FCM 09, indialling barred.
A failed DDI call can be routed to the operator. The operator can overrule a DDI
barred connection.
• Trunk Barred Extension
An extension can be prevented from being connected to specific trunk lines for DDI
or DDO. A trunk barred check can be specified for any trunk bundle.
FCM 06, Exchange Line Circuit (ELC) barred.
A failed DDI call can be routed to the operator. The operator cannot overrule a
trunk barred connection.
• Long Line Extension
An extension located at a great distance from the system can be prevented from
being connected to specific trunk lines for DDI or DDO. This is to prevent a loss of
signal quality between a long trunk line and the extension line. A long line check
can be specified for any trunk bundle.
FCM 15, long line.
A failed DDI call can be routed to the operator. The operator cannot overrule a long
line barred connection.
• Permanent Line Extension
A Permanent Line Extension (PLE) is a DNR (extension or group) that is assigned
to one or more incoming or bothway non DDI trunk lines and is used to answer
incoming calls via these trunks, during day and night conditions. The PLE user has
most of the normal voice extension facilities. If call transfer from the PLE is not
successful (no answer or still busy after time period) the call is routed to the
operator C-queue.
Timer 033, call forwarding PLE to operator time, 20...60 seconds.
The permanent line extension can be switched absent or present (by dialling a
prefix). When absent incoming calls are rerouted to the operator or night service.
The rerouting can also be invoked if the PLE does not answer the call within a
predefined time.
Timer 027, night extension ring tone time, 60...240 seconds.
A PLE can be assigned to any number of trunk lines (a trunk line can have only
one PLE assigned).
FCM 23, special extension, once an extension is assigned as PLE to a trunk line.
System option 12, allows calls to be diverted if routed to a busy PLE.

46
1.1.25. Twinning

With Twinning two DNRs or extensions can be combined. If the DNR with the twinning
relation is called, both start ringing.

The dialled destination of a twinning relation can only be an extension, while the
twinning destination can be an extension, a group or an external party.

An extension can have only one twinning destination. However, a destination can be
used as twinning destination in more than one twinning relation. The twinning relation
can be with any terminal, including a terminal in another IMP unit, DPNSS node or a
terminal in the PSTN, ISDN or GSM network. Twinning relations with a terminal in the
public network can only be done uni-directional.

All the DNR related facilities like Call Forwarding, Follow-Me etc. remain DNR
dependent. Of course they can be made equal for twinned DNRs but there is no
necessity.

Figure 1-3 Bi-directional twinning.

This figure gives an example of the most common implementation of twinning; bi-
directional twinning. The desk terminal (3278) is twinned with the DECT terminal
(4240) and the DECT terminal is twinned with the desk terminal. If either 3278 or 4240
is called both terminals start ringing.

When a user does not want the DECT terminal to start ringing, because of a meeting
for example, then e.g. the Do Not Disturb or Follow-me facility can be used.

47
 Figure 1-4 Uni-directional twinning.

This figure shows an example of uni-directional twinning. If 3278 is called both 3278
and 4240 start ringing. If 4240 is called both 4240 and the 4280 start ringing. When
one of the called DNRs is busy, one does not want the other phone(s) start to ring if
one of the DNRs is called. The SOPHO iS3000 monitors both extensions. At the
moment that one of the DNRs is busy it is possible to initiate for example an ARB on
busy or, if projected, a Call Forwarding on Busy of the twinning originator.

For cost accounting twinning should be seen as a follow-me initiation. The charges
only differ if the twinned relation is a terminal in another node of a DPNSS network or
a terminal in the PSTN. The caller will get the cost charges for the cost related to the
call to the terminal (location, network) he made. If the called party answers on e.g. his
GSM these extra cost for the diversion will be billed on the called number.

If twinning is used the other way around it could lead to cost benefits for the customer.
In business environments people using GSM have very often programmed a follow-
me on their normal business telephone (the one on their desk) towards their GSM set.
All telephone calls toward the normal business phone will be forwarded towards the
GSM. The extra costs will be billed to called business phone. Even if the user is in the
office and has forgotten to de-activate the follow-me he is obliged to answer the call
on the GSM set and to accept the extra cost charges. Larger companies very often
have special contracts with GSM providers that ensures that GSM calls in the office
have a special tariff. Such a contract together with the twinning facility can guarantee
a very high level of reachability at a lower price.

1.1.26. ISDN Extension Features

Open EURO-ISDN access for the iS3000 Series is provided on the same extension
interface used by feature-rich business telephones and German 1TR6 terminals.

48
Called S0 combi-bus, this universal extension is open to EURO-ISDN terminals and
offers in addition to basic call various supplementary services, described in this
section.

The introduction of EURO-ISDN on the S0 combi-bus has been implemented next to

the 1TR6 (Germany) and 'TMP' protocols as a 'downloadable' software package.
Besides being unique in the market, this 'trio' approach also provides a smooth
migration for today's S0 combi-bus users. Connecting a EURO-ISDN terminal is thus
only a matter of a software download, without requiring any additional hardware.

All features described in this section are offered to terminals connected to the S0
combi-bus, either directly or behind a Private Network Terminator (PNT). A PNT is
used to convert a 2-wire interface into the required 4-wire interface. The features are
summarised hereafter:

49
 FEATURE ISDN "S0 BUS" EXTENSION
FEATURES
ETSI EURO- 1TR6/DKZE
ISDN
Advice of call charge (AOC, ETS 300 182):

- during the call (AOC-D) + +

- after the call (AOC-E) + +

B-channel allocation:

- dynamic + +

- fixed (for separate access) + +

B-channel bundling + +
B-Channel overflow + +
Call hand-over + +
Call hold (CH, ETS 300 139) + +
Call Transfer (CT) proprietary procedure + +
Call Waiting (CW) proprietary procedure + +
Calling Line Identification presentation (CLIP, ETS + +
300 191)
Calling Line Identification Restriction (CLIR, ETS 300 + +
191)
Connected Line Identification Presentation (COLP, + +
ETS 300 191)
Connected Line Identification Restriction (COLR, + +
ETS 300 191)
Completion of Calls to Busy Subscriber (CCBS, + +
ETS300 357, 358 and 359-1)
In-Call Modification (ICM) - +
Keypad protocol for facility access (ETS 300 190) + +

50
FEATURE ISDN "S0 BUS" EXTENSION
FEATURES
ETSI EURO- 1TR6/DKZE
ISDN
Multiple Subscriber Number (MSN, ETS 300 189)

- 2 directory numbers + +

- 8 directory numbers + +
Subaddressing (SUB, ETS 300 192) + -
Terminal Portability (TP, ETS 300 055) + +

Table 1-3 ISDN features

Advice Of Charge

The supplementary service Advice Of Charge (AOC) enables a user to receive

information about call charges. This supplementary service is provided by the public
ISDN to the ISPBX and by the ISPBX to terminals. The ISPBX supports charging
information during a call (AOC-D) and charging information at the end of a call (AOC-
E).

FCM 10, metering.

Timer 175, charging display refresh time, 5 ... 16383 seconds. Specifies the time after
which new Advice Of Charge information will be displayed during a call with a trunk
with metering.

Basic Call

The ISPBX complies with CCITT Recommendation Q.930 (I.450). The following Basic
Call services are supported:

- Causes, contained in the call signalling information, for example: busy, number
unobtainable.
- Bearer capabilities, 64kbps user channels are used.
- Service Indicator, contained in the call signalling information.
- Date and time, contained in the call signalling information.
- Overlap sending.
- Enblock sending.

51
 B-channel Allocation

The S0 combi-bus can be used to connect several terminals in parallel, which require
capacity on the 2 B-channels. Each S0 combi-bus uses one of the following B-channel
allocation methods:

- Dynamic
The system searches for an available B-channel, when making a connection
involving a particular terminal. This provides the benefit of multiple usage but does
not guarantee user access at an arbitrary time.
- Fixed
"Fixed B-channel" provides a very simple way to prevent such a situation. Each
employee receives his own B-channel for his personal use.

B-channel Bundling

This facility is used by applications which require the 'bandwidth' of two B-channels (2
times 64 kbit/s). Examples are: video conferencing, remote LAN access etc. The user
can initiate or receive two 'identical' calls. A BSP-ID, which is already occupied by one
call, can be selected again for a new call. This new call will seize the other B-channel
in the S0 bus. Both calls have the same calling/called line identity. For facilities like
ARB, COB, Call Forwarding etc. the oldest call will be the reference. B-channel
bundling will not work if the BSP-ID is:

- a group member;
- in an executive/secretary combination;
- a special extension (SCNE, MCNE, INE, PLE or OVE);
- combined with a TMP terminal at the same S0 bus.

FCM 56, B-channel bundling allowed.

B-Channel Overflow

The BSP-ID of a call (incoming and outgoing) determines the B-channel to be taken.
This B-channel might be occupied by another call. The ISPBX then tries the other B-
channel. This facility is particularly useful if the S bus is used by one person. For all
calls (voice, data, fax etc.) it will search for a free B-channel.

FCM 50, overflow allowed.

Call Hand-Over (1TR6 only)

Call Hand-Over allows an S0 user to hand-over a call between two or more terminals.

52
Call Hold

This service allows a user to put a call on hold and make another call if desired. The
user can then shuttle between the two calls by subsequent activation of call hold. See
section 1.1.10. "Enquiry/Shuttle/Transfer".

Call Transfer (proprietary procedure)

With the call transfer feature, a user can connect two callers (one on hold and the
other active in conversation). Transfer occurs when the user goes on hook after an
enquiry action. See section 1.1.10. "Enquiry/Shuttle/Transfer".

Call Waiting (proprietary procedure)

With call waiting, the user receives an indication of an additional incoming caller for
his extension. An incoming call will be indicated with call-waiting tone. See section
1.1.10. "Enquiry/Shuttle/Transfer".

Line Identification

Information about the identity of calling and connected lines can be presented to an
ISPBX user that has a terminal equipped with a display.

• Calling Line Identification Presentation (CLIP)

Provides the calling party number and trunk code to the called party before a
connection is established. This enables personalised answering, call logging in the
case of absence and various computer supported telephony applications and
alike.
As from Call@Net 2.11 the CLIP protocol is selectable by means of a FCM.
FCM 65, CLIP on analogue terminals ETSI.
FCM 74, CLIP on analogue terminals Danish.
• Connected Line Identification Presentation (COLP)
Provides the connected party number and trunk code to the calling party when a
connection is established. This enables an easy check on the dialled extension.
• Calling Line Identification Restriction (CLIR)
By activating CLIR during a call set-up, a calling party can restrict the presentation
of his number at the side of the called party. This allows a caller to preserve privacy
whenever desired. Such a service can also be provided on a permanent basis.
FCM 46, CLI permanently restricted.
FCM 47, overrule CLIR (for the called party).
The per call option is achieved by dialling a prefix.
• Connected Line Identification Restriction (COLR)

53
 By activating COLR during ring-time, a called party can restrict number
presentation at the side of the calling party. This allows for preserving privacy
whenever desired.
FCM 51, COL permanently restricted.
Secret calls (identification restriction) can be used for internal, DPNSS or external
ISDN calls. All "blanks" are displayed at the destination for internal calls. For an
external ISDN call, the information displayed depends on the local ISDN
implementation.

System option 79, send all zeroes over DPNSS connections for CLIR.

System option 74, CLIR implemented for entire ISPBX.

System option 75, overrule CLIR for operators.

System option 76, overrule CLIR for call recording.

System option 77, overrule CLIR prohibited for extensions.

Completion of Calls to Busy Subscriber (CCBS)

This feature is similar to Automatic Ring Back on busy. It works between iS3000
extension users/operators and subscribers in the public ISDN network (when the
public ISDN supports it). It works in both directions but not to a busy operator.
Interworking between CCBS and CBWF (DPNSS) is not supported. Pending CCBS
requests do not occupy any physical resources (like trunk lines, multi unit lines, etc.).
With the Cancel Automatic Ringback dialled facility a user deactivates all outstanding
ARB, CBWF, CBWNU and CCBS requests.

FCM 48, ARB entitled.

FCM 49, ARB protected.

Software license 27, Completion of Call to Busy Subscriber.

Timer 179, ARB call setup guarding time; 30 70 seconds.

In Call Modification (1TR6 only)

In Call Modification (ICM) enables a user to change within an established call from one
ISDN service to another ISDN service without releasing the end-to-end connection.
This specific ISDN supplementary service is implemented according to the 1TR6
standard "Dienstwechsel" and is available for German ISDN terminals supporting this

54
feature. This service is supported at both the trunk and the extension side as well as
in distributed IMP networks. In-call modification can however not be invoked across a
DPNSS link (i.e. no support of DPNSS "service swap").

Keypad protocol

The keypad protocol gives unrestricted access to any of the dialled facilities supported
by the iS3000. A user with a EURO-ISDN terminal is in this way not restricted to the
available set of supplementary services but can also benefit from the multitude of
standard extension features. A user invokes a supplementary service by dialling the
appropriate sequence of digits.

Multiple Subscriber Number

This service allows one extension interface to support a number of subscriber

numbers. The S0 bus can handle up to eight ISDN terminals. The Multiple Subscriber
Number (MSN), allows these terminals to be addressed individually. A terminal
accepts a call if it recognises its own MSN in the call setup message. The 1TR6
protocol, which uses a single digit for this, refers to the MSN as the Endgeräte
Auswahl Ziffer (EAZ). See section 1.1.20. "Multiple Subscriber Number" for further
details.

Sub-addressing

This service allows an ETSI terminal to include extra digits in the call setup message,
which is sent to a destination. These extra digits are used in a situation, where terminal
users want to reach a specific terminal of a Local Area Network (LAN), which is
connected to an ISDN port. The sub-address is included in the call setup message
and is transparently passed through to the destination (end to end), this in
contradistinction with the supplementary service Multiple Subscriber Number (MSN),
which is part of the ISPBX numbering scheme. Sub-addressing does not require
special project parameter settings, it is available at every S0 bus which supports the
ETSI protocol.

Terminal Portability

This service offers a user the possibility to suspend and resume a call on the same S0
interface. Either to move a terminal from one socket to another socket without losing
the call or for transferring calls between two terminals on the same bus.

Secret Call

A secret call suppresses the identity of the caller at the dialled destination as well as

55
 in the call recording output (i.e. FDCR and toll ticketing).

1.2. Datacom Features

The features offered to data port users comprise the extension features described in
section 1.1. "Extension Features", plus a number of dedicated datacom features
which are described in this section.

1.2.1. Introduction

A data terminal connected via a line circuit (terminal connected via modem to an
analogue line or terminal connected via business telephone with data port or terminal
adapter) is regarded by the ISPBX as a normal extension. The ISPBX does not use
any distinction between a data party and a voice party. A summary of data
connections is given hereafter:

Connecting a Data terminal (DTE) to a Digital Line

A V.24 data terminal can be connected to digital lines in the following ways:

- Using a SOPHO Business Telephone, supporting two separate 64 kbps user (B)
channels one of which is used for voice and one for a DTE connection.
- Using a SOPHO Line Adapter Module (LAM), supporting one or two 64 kbps user
(B) channels for DTE connections.
- Using an ISDN Terminal Adapter.

Connecting a DTE to an Analogue Line

A digital peripheral can be connected to analogue line using a modem. The system
treats the line as an analogue line with all the corresponding extension facilities.

Depending on the type of modem, call set-up may be done using a normal telephone
set (rotary dial or keytone), using keyboard dialling from the DTE or automatically
under control of the DTE software (for example, V.25 or V.25bis or AT commands).
The modem transfers the digits to the network as pulses or keytones. If a telephone
set is used for call set-up then the modem is connected to the line after the connection
has been established.

FCM 31, X.21 DTE.

FCM 40, TRANSCOM DTE.

56
1.2.2. Data Protection

A data connection can be prevented from being interrupted (break-in, listen in or call
waiting tone) in the following ways:

- Both incoming and outgoing calls over a route are automatically data protected if
the route has data protection applied.
- An extension can be permanently data protected. Every call made by or routed to
the extension is automatically data protected.
FCM 04, data protected.
- A user can determine if data protection is required for the duration of an individual
call. The extension user dials a prefix prior to dialling the destination to activate
data protection.
FCM 05, data protection entitled.
- If an ISDN service is used that is not for speech then it is impossible for a speech
oriented third party to break-in to the connection.

1.2.3. Downloading

System terminals can be used to program the interface characteristics of a data

terminal, in a business telephone or terminal adapter in the following circumstances:

- When the system is started.

- When the port is put into service.
- On request of the user from the telephone.
- On request of the system manager from an OM terminal.
- On request of the business telephone or terminal Adapter if it has been without
power for a long period and has lost its programming data.

See also section 1.7.2. "Facility Management"

1.2.4. Modem Pool

A pool of modems can be created, for use when a data extension connected via a
digital line sets up a call to a data party connected via an analogue line (or an external
party via an analogue trunk or tie line). A free modem out of the pool is switched into
the connection for the duration of the call. A number of different pools can be created,
each pool contains modems with the same characteristics.

Modems can be connected to a SOPHO Line Adapter Module (LAM). This allows the
V.24 interface of a modem to be connected to a digital line. The analogue modem line
is connected to a standard analogue extension interface. The following selection

57
 mechanisms can be used to select the SOPHO-LAM converter:

- Automatic converter interconnection by Predefined Destination Dialling (PDD)

used for incoming leased line calls. The predefined destination is a fixed internal
destination number stored in the SOPHO LAM. When the SOPHO LAM detects an
incoming call (for example an incoming carrier), it automatically dials the number
which is stored in its memory.
- Automatic converter interconnection by hotline used for incoming leased line calls.
This uses the standard hot-line facility, with originator as the directory number of
the SOPHO LAM.
- Keyboard dialling used for incoming leased line calls. The external calling party
can dial the directory number of the SOPHO LAM. After the connection between
the caller and the SOPHO LAM is established, the SOPHO LAM waits for dial
information. The caller dials the destination directory number from the data
terminal keyboard, after which the SOPHO-LAM sets up the connection.
- Converter pool selection by group number used to access a pool of converters. An
internal party dials a group number and is connected to one of the converters in
the pool. The calling party is now automatically connected to the destination. All
converters must have the same destination.
- Individual converter selection used to access one single converter. This is done by
dialling the SOPHO LAM directory number.

Modems can be configured for modem pool, leased line or switched line operation.

1.2.5. Gateways

An ISPBX data party may wish to be connected with a special type of data network. If
the ISPBX does not support the interface type used within that network then a
gateway is required. The ISPBX party establishes a connection to the gateway server
via which it transfers user information. The gateway server ensures that the user
information is delivered to the data network in the correct format. Connections to the
gateway server can be put into a group arrangement with group hunting. Then the
ISPBX party does not have to dial a specific gateway but only dials the group directory
number. Group hunting ensures that a free gateway circuit is accessed.

1.3. Directory Services

The directory services comprise two main components:

1. Integrated name database in iS3000

- Calling Name and Number Display (CNND) on digital sets, DECT sets and
operator consoles. See section 1.1.4. "Calling Name and Number Display"".

58
 - Browse on digital feature phones. See section 1.1.6. "Central Directory Dialling
(or Browsing)"
2. PhoneWare directory application
- Name database in SysManager and SuperVisor 60E.
- Access to/from external systems (hotel, Web).

The name database in the ISPBX can only contain numbers having up to 6 digits and
is therefore only suited for Internal-CNND.

The database in SysManager is an external server, part of the Directory Services

Module (DSM). This directory can contain numbers of up to 20 digits, both internal and
external numbers. This makes the DSM suited for I-CNND and E-CNND.

The DSM acts as an overflow database for CNND and is only consulted if a name-
number relation is not found in the I-CNND database. The combination of the CNND
and the DSM however points to a weak spot (which will be solved in the near future!):
the DSM has to be maintained by the Phonebook Manager while the CNND database
has to be maintained by the MAC Manager.

Software licence 20, CNND (per unit).

System option 99, access external CNND database for internal translation. Indicates
whether the external database has to be used when the number is not found in the
internal database.

System option 101, local CNND function active.

The maximum number of CNND entries depends on boundary 305 and the type of
ISPBX:

ISPBX TYPE: MAX. NUMBER OF ENTRIES:

CPU3000 system 2360 (typical 1159)
CCS single slice 3431
CCS system 11015

All terminal types listed hereafter are capable of displaying the normal range of
characters, which are 'a''z', 'A''Z', '0''9', ' ', '#' and '*'. For Central Directory Dialling the
supported character set has been extended to the standard ISO 8859 Latin 1
character set. As not all terminals are able to support the Latin 1 set, translation is
executed to convert not supported characters into supported characters.

59
 TERMINAL TYPE NUMBER OF CHARACTERS ON DISPLAY
DECT C311/C322 10
DECT C911 20 (16 on first line + 4 on next line)
DECT C922 20 (3 visual display lines + 17 virtual display lines)
ErgoLine D320 1) see note
2)
ErgoLine D330 20
2
ErgoLine D340 ) 20
ISDN terminals (general) 1) see note
SOPHO-SET P375(D) 20
SOPHO-SET S375(D) 20
SV25 (rel. 1.30 and up) 20
SV35 (rel. 1.30 and up) 20

Table 1-4 Supported terminal types and operators.

Note: - 1) ISDN terminals have to be able to receive and display user to user
messages sent by the ISPBX. Note that DECT extensions also are handled
as ISDN terminals.

- 2) Two version groups (releases) of the ErgoLine D330 and D340 are
available. ErgoLine release 1.5 and higher and the ErgoLine 1.4 and older.
The first group consists of a release that is adapted especially for receiving
and displaying (non-user to user) CNND messages and the release that
only accepts the user to user messages. Distinction between the two
release groups is made within the ISPBX by means a special software
mode.

8 Bits ISO 8859 Latin 1 or 7 Bits ASCII Character Set

System option 112 defines whether CNND uses either 7 bits ASCII or 8 bits ISO 8859
Latin 1. The ErgoLines, the SuperVisor 25 and -30 (and perhaps a high-end DECT
handset) support 8 bits; all other external devices can only handle 7 bits. The
SysManager 410 (i.e. the MAC-Manager) supports 8 bits for the entry of names.
Central Directory Dialling (CDD) only supports 8 bits ISO 8859 Latin 1, and, hence,
the database will contain names in 8 bits.

60
Note that when the system option is set to 7 bits, the representation of the name
entered (and returned) by means of CDD may be different from the one returned by
means of CNND. For example character "Ç" is translated to "C, "ß" to "ss", "ö" to "oe"
etc. (All characters above decimal value 127 will be translated to blank or a character
strongly related to the original character.)

1.4. Operator Features

The system software includes a number of functions dedicated for operators and
operator groups. For the description of these functions please refer to the System and
Application Manual - SuperVisor operator consoles.

- Abbreviated dialling (common pool and individual)

- Automatic repeat to operator
- Break-in
- Call handling
- assisted outgoing calls
- call announcement
- call splitting
- enquiry on trunks
- fast call handling
- general call signalling
- individual monitoring
- listen-in
- transfer with/without announcement
- Camp on busy
- DDO-line reservation for operators
- Display of:
- calling number (internal)
- called number (internal)
- called name
- last called party (ext. caller)
- trunk route and line number
- paging indication
- time
- Flexible operator (DPNSS)
- Give a line
- Hold
- Inter-operator calls (with and without announcement)
- Multi-party conference
- Night service

61
 - Number repetition
- Overflow extension
- Post-dialling
- Queue facilities
- Recall calls
- Repeat calls and suppression of undesired repeat calls
- Series calls
- Symmetrical display
- Taxmetering
- Trunk busy indication

1.5. Night Service Features

The system goes into night service if all operators in a specific assistance group have
switched absent or if the system timer switches to night service. During night service
operator assistance is offered by a series of night extensions.

1.5.1. Night Service Hierarchy

There are four levels of night service extensions:

- Individual Night Extension (INE);

- Sub-Common Night Extension (SCNE);
- Main Common Night Extension (MCNE);
- Common Answering Night Service (CANS).

The relationship between the night extensions is shown in the following figure.

62
Figure 1-5 Night service relations.

Any extension or group arrangement can be defined as a night extension. An

extension/group can only be one type of night extension.

FCM 23, special extension, once an extension is assigned as a night extension.

Extensions with facility class mark "voice mail server" can also be used as night
extension. If a call requires assistance, the voice mailbox of the called party is used.

FCM 33, voice mail server.

A night extension can switch absent and present. For a group arrangement this means
that ALL members of the group must be switched absent before the night extension is

63
 taken absent or one member of the group dials the night extension absent prefix.

A night extension (group) functions as a normal extension (group) when the system is
in day service but is given a special night extension traffic class in enquiry when called
as a night extension.

• Individual Night Extension

An Individual Night Extension (INE) is an extension or group that is assigned to
one or more incoming or bothway non DDI trunk lines and is used to answer
incoming calls via these trunks, during night conditions. The INE offers the A-
queue service, not the C-queue service. C-queue calls are routed to the SCNE.
The INE only offers the initial operator service for the incoming call; the INE user
answers the incoming call, goes into enquiry and dials the destination party. By
going on-hook the trunk line is transferred to the destination party.
If the call set-up is not successful (no answer or still busy after time period) the call
is NOT rerouted back to the INE but to the Sub Common Night Extension which
offers the operator C-queue assistance in night conditions.
Timer 028, call forwarding INE to SCNE time, 20...60 seconds.
If the INE is switched absent then incoming calls are routed to the SCNE of the
corresponding trunk route. If the INE is present and the incoming assistance call
is not answered within a certain time, the call is NOT forwarded to the SCNE, but
the INE is forced absent. Subsequent trunk calls to the INE will be rerouted to the
SCNE immediately.
A trunk line can have only one INE assigned. An INE however can be assigned to
a number of trunk lines. An INE can only be assigned to a trunk line that does not
have a PLE assigned to it.
If the trunk route containing the line to which an INE is assigned supports DDI then
the INE is not used. Incoming DDI calls are NOT routed to the INE but directly to
the required destination. If the dial information of the DDI call indicates an operator
A-queue code dialled prefix the call is routed to the SCNE assigned to the route.
• Sub-Common Night Extension
A Sub Common Night Extension (SCNE) is an extension or group that is assigned
to one or more routes (DDI and non DDI) with incoming calls. The SCNE is used
to answer incoming calls via these routes, during night conditions. The SCNE
offers the A- and the C-queue service; not the M-queue service. M-queue calls are
routed to the MCNE.
The SCNE offers both initial and rerouted operator service for the incoming non
DDI call. The SCNE user answers the incoming call, goes into enquiry and dials
the destination party. By going on hook the trunk line is transferred to the
destination party.
The trunk line may be transferred to the destination party without waiting for

64
 answer. If the destination is busy the transfer results in a COB initiation of the trunk
line in the COB-queue of the busy party.
If the SCNE is switched absent then incoming calls are routed to the MCNE of the
corresponding ISPBX. If the SCNE is present and the incoming assistance call is
not answered within a certain time, the call is NOT forwarded to the MCNE, but the
SCNE is forced absent. Subsequent trunk calls to the SCNE will be rerouted to the
MCNE immediately.
Timer 029, call forwarding SCNE to MCNE time, 20...60 seconds.
A route can have only one SCNE assigned. An SCNE however can be assigned
to a number of trunk routes.
When a SCNE is assigned to a route, outgoing DDO calls are still possible. They
are not routed to the SCNE but directly to the external destination (provided the
initiating party is allowed to use DDO).
If the trunk route to which the SCNE is assigned supports DDI then the SCNE is
not used. Incoming DDI calls are NOT routed to the SCNE but directly to the
required destination. If the dial information of the DDI call indicates an operator A-
queue code dialled prefix the call is routed to the SCNE (!) assigned to the route.
• Main Common Night Extension
The Main Common Night Extension (MCNE) is the ultimate equivalent of the
operator position during night hours. It can offer internal (M-queue), external (A-
queue) and rerouted (C-queue) assistance in an IMP network.
An MCNE can be an extension DNR or a group DNR. It can be assigned per
compatibility value (CV). So in case of a multi tenant usage, up to 254 tenants can
have their own MCNE.
When there is a call for the operator in the night condition, it is routed to the MCNE
with the same CV as the caller. In case of an external incoming call, the CV of the
incoming route is relevant.
Two types of MCNE are possible:
- the general MCNE: per unit (for one or more units);
- the specific MCNE: per assistance group per unit (for one or more assistance
groups for one or more units). Extremely suitable for multi-user/multi-tenant
configurations.
If an MCNE answers a call for assistance, it has the same facilities as an operator
as far as the normal telephone extension allows it. The MCNE only offers the initial
operator service: answering incoming calls, going into enquiry and dialling the
destination.
Non DDI-calls: If the call set-up is not successful, the call comes back to the
MCNE. If the MCNE is switched absent an incoming non DDI-call goes to the
CANS. The MCNE can be switched absent (and present) by the user or
automatically when system timer 030 (call forwarding MCNE to CANS time)
expires. If an ISPBX unit is not assigned to a CANS area, it is not allowed to switch

65
 the MCNE absent. Even if the MCNE is located in another unit.
DDI-Calls: If a DDI-call is not successful then it depends on the route
characteristics whether the call goes to the MCNE during night condition. It is
possible to select whether the call to a specific assistance group in night is passed
immediately to the specific MCNE or is first routed to the general assistance group.
• Common Answering Night Service
The Common Answering Night Service (CANS) is used when all other night
extensions are unable to assist the call. CANS is a way of notifying the presence
of a call that needs assistance. Any person on the premises that hears the call can
offer the assistance by picking up the call at any extension.
The CANS is used when a call is routed to the MCNE for assistance and the MCNE
is not defined or is absent. Only external calls (A-queue service) and unsuccessful
or rerouted calls (C-queue service) will be forwarded to CANS. Internal assistance
requests (M-queue service) will not be forwarded to CANS. A number of calls can
be in the queue for assistance by CANS.
If a call is routed to the MCNE and the MCNE is not defined or is absent, the call
is placed in the CANS queue. The system signals the presence of the call to the
external CANS equipment, for example a hooter on the roof. Any extension can be
used to answer the call by dialling a CANS code. A connection is made between
the party on hold and the extension from which the prefix was dialled. System
timers guard the CANS hooter time and the time during which a CANS call should
be answered.
Timer 23, CANS hooting time-out, 120...300 seconds.
Timer 31, CANS release time, 60...240 seconds.
Each ISPBX unit can be related to one CANS area. A CANS area can contain a
number of ISPBX units. Each CANS area has its own CANS equipment.
CANS requires external equipment to announce the presence of a call. This
equipment can be a bell or hooter which is switched by the CANS relay of the
ISPBX unit.

1.5.2. Night Service Facilities

• Automatic Absent Switching

If a call comes in while in night service, the call is route to the night service
extensions. If the night service extension is not answered within a certain time then
it is automatically switched absent. Incoming calls will subsequently be routed to
the next highest level of the night service hierarchy.
• Automatic Repeat To Night Extension
It is possible to specify that night service assistance is offered to DDI calls that fail
for each of the following reasons:
- Dialled extension is busy;

66
 - DDI dial time-out;
- DDI ringing time-out;
- Dialled number does not exist;
- Any other reason, for example, the dialled party has data protection, DDI
barred mark etc.
The requirement for night service assistance for each of these reasons is related
to trunk routes.
• Call Forwarding to Higher Night Extension
If a night service extension is absent or busy then incoming calls to the extension
are diverted to the next highest level of the night service hierarchy. Diversion on
busy PLE and diversion on busy INE are system options.
• Diversion on Night Extension
When a night watchman attends the Main Common Night Extension (MCNE)
which is a hard-wired telephone, then 'Diversion on Night Extension' allows for a
flexible set-up:
- If the night watchman is unable to answer incoming calls, they can be
redirected to a voice mail, which can inform the caller that the company is
closed and allows the caller to leave a message. The follow-me facility is not
used in that case.
- The night watchman can re-direct calls to his mobile telephone (by the follow-
me) when he has to go on his patrol round and still have the voice mail answer
all calls which he could not answer himself.
- A call not being answered at a night extension can be forwarded to the next
level of the night service hierarchy. The follow-me facility is not used in that
case.
The Follow-Me destination will get the CANS traffic class level as long as the FM
destination resides in the same PBX as the Night Extension. The Follow-Me can
be a fixed FM initiated by means of OM or a normal or prepared FM initiated from
the extension terminals. In fact there is no difference in setting the FM relation as
with normal extensions.
• Night Assistance
Although the night extensions are normal extensions they are assigned the basic
operator facilities when they are called in special assistance situations for
example:
- If a night extension user is busy with a call and another (external) call is routed
to the same night extension then the call is queued. Call waiting burst is sent
to the busy night extension user.
- If a night extension is called in a night assistance situation the extension is
given a night traffic class. Usually this traffic class will be higher, allowing the
extension user to make assistance calls which are not allowed with the normal
extension traffic classes. When the night extension is called by its directory

67
 number or the night extension user initiates a call himself (without a party on
hold) the extension does not have the night extension traffic class but the
normal extension traffic classes. Each level of night extensions within the
ISPBX can be assigned a different night traffic class. Assigning these traffic
classes is done at an OM terminal.
• Special Assistance
Two types of special extensions which are not related to the night service, can be
defined to offer operator assistance:
- The permanent line extension (PLE) is used in day or night service.
- The overflow extension (OVE) is a special extension that is only used when the
operators are present. It is used as an overflow in case the operators cannot
handle the amount of traffic.
• Traffic Class Upgrading and Downgrading
An extension is assigned 4 traffic classes. These are day, night, upgraded and
downgraded traffic class. The day and night traffic class are used when the ISPBX
is in day or night service respectively. This situation is normally determined by the
presence of operators or by facility timing. The upgraded and downgraded traffic
class are selected by password dialling and are used in combination with a
SOPHO SystemManager.
It is also possible to use a test telephone (any extension with a specific facility
class mark) to switch between the day and night traffic classes of the extensions.
If the system manager dials (from the test telephone) a prefix, the system uses the
DAY traffic class. If the system manager dials another prefix, the system uses the
NIGHT traffic class. If the system manager used one of these facilities to force
either of the traffic classes, the system manager can return to the normal day /
night traffic class switching (operator or facility timing) by dialling another prefix (no
traffic class selected). This facility only affects the switching between the traffic
classes, not the rerouting of operator assistance calls to the night extensions.
FCM 13, test call entitled.

1.6. Paging Features

The following types of paging are supported:

• Virtual Meet Me Paging

This paging method does not use radio equipment. A caller asks the operator to
page someone. The operator asks the system for a paging identification number
by dialling a paging code. This number is shown on the operator display. The
operator breaks the connection with the caller who is placed on hold. The operator
uses an announcement system to tell the paged party to dial the paging code, and
transfers the call. The paged party dials the paging code from any extension and

68
 is subsequently connected to the calling party.
Boundary 65, maximum number of virtual paging codes, 0...100.
• Radio Meet Me Paging
A caller dials a paging code followed by a receiver number and additional
information, such as his own directory number and waits off hook. The receiver
number and additional information are transferred to external paging equipment.
The paging equipment signals the required receiver and sends it the additional
information. The paged party dials the paging answer code and is subsequently
connected to the calling party.
• Radio Non-Meet Me Paging
A caller dials a paging code followed by a receiver number and additional
information, such as his own directory number. The receiver number and
additional information are transferred to external paging equipment. The paging
equipment signals the required receiver and sends it the additional information.
Now one of two things can happen depending on the paging receivers used:
- Voice paging receiver. The paged party answers the call using the paging
receiver and is immediately connected to the caller.
- Paging receiver with display only. The caller receives confirmation tone. The
paged party sees the additional information and acts upon it, for example by
dialling the directory number of the caller. This is now a normal call.

The system features offered specifically for paging applications are described further
in this section.

1.6.1. Automatic Number Display on Pager

The system can send the paging receiver identity and additional information to paging
equipment for a paging call. The additional information can be the callers directory
number automatically generated by the system, or some dialled information input by
the caller. The additional information is displayed on the paging receiver.

1.6.2. Camp-on-busy on Paging Call

If a paging call is made to a busy speech paging receiver, then camp-on-busy can be
initiated. Calls in the paging receiver COB queue are retrieved when the paging
receiver becomes free.

Boundary 132, maximum number of calls in COB queue for a meet me paging, 0...30.

Boundary 137, maximum number of calls in COB queue for all paging queues, 0...100.

Boundary 138, maximum number of calls in COB queue for a paging bundle, 0...10.

69
 1.6.3. Repeated Paging Call

A real meet-me paging call is repeated if the call is not answered. For unassisted calls
this is guarded by a timer, for assisted calls no guarding is done. The time interval
between the repeated paging calls can be defined. The initiator of the paging call is
not informed about repetition.

Timer 061, paging wait for answer time, 30...240 seconds.

Timer 098, paging repeat time, 10 seconds...16383 minutes.

1.6.4. Rerouting Unanswered Paging Call to Operator

If the paged party of an assisted real meet-me paging call does not answer within a
certain time then the caller is returned to the operator C queue or night service.

Timer 062, paging return to operator time, 10...40seconds.

This feature is not used for unassisted real meet-me paging or for virtual paging.

1.6.5. Paging Areas

The size of the ISPBX network may require the separation of paging systems because
of the limited reach of the paging equipment. Paging areas are used to group a set of
ISPBX units that share paging equipment. Paging equipment is connected to ONE
ISPBX unit in the paging area. The unit that has the paging interface is called the utility
unit. An ISPBX unit can only be assigned to ONE paging area. If a caller (connected
to a unit in a paging area) initiates a paging call, that call can only be answered using
an extension that is connected to a unit of the same paging area.

1.6.6. Paging Hardware

No additional ISPBX hardware is necessary for virtual paging. Virtual Paging is a

standard feature of the ISPBX unit. An external announcement system is necessary.
Special equipment must be used for real paging. The paging equipment is connected
to a dedicated paging interface. Any type of paging equipment can be used that
supports E& signalling according to the European Selective Paging manufacturers
Association (ESPA) recommendation 4.4.4.

1.6.7. Paging Routes

Paging is a facility that is accessed using routes and lines, so paging also uses a kind
of routing. This routing however, is fully independent of the routing aspects used for

70
normal call routing. There can be a number of paging routes in one paging area, so
that different types of paging can be used. Paging parameters and codes are assigned
to each route which corresponds to a specific paging type: virtual, real-meet-me or
real-non-meet-me.

Boundary 60, maximum number of paging routes in system, 5...200.

Boundary 66, maximum number of paging lines, 0...255.

1.6.8. Mode Digit Support

A mode digit is only used with more sophisticated paging equipment. It is used to pass
information of the initiating call to the paging equipment in order to trigger a specific
action by the paging equipment. This may be, handling the call with high priority
(urgent paging), reserving radio channels for setting-up a speech connection, varying
the bleep-frequency (internal, external or through-connect call) etc. Other equipment
may require the mode digit as a suffix. The mode digits can be assigned to make the
ISPBX compatible with the paging equipment.

1.7. System Management Features

1.7.1. Initial Installation

Customer requirements for the iS3000 series and its peripherals, including information
regarding the required system size and the configuration are defined using a PC
application called Prophix. The program is used to generate a product offer (the price
of the system), a parts list, shelf layouts and input files for the Project Generator
(PG2). Project Generator (PG2) is a software program used to generate the projecting
for an iS3000 series ISPBX. The projecting comprises all the configuration data for the
system, for example, the boundaries, options and timers, the numbering plan, the tone
plan etc.

1.7.2. Facility Management

Facilities are assigned to extensions using Facility Class Marks (FCMs). All facility
class marks can be assigned using OM commands. It is possible for some facility
class marks to be included in a default list, which are subsequently assigned to all
newly created directory numbers. Facility class marks are shown like this in this
manual:

FCM XX, +name of the facility class mark;.

• Downloading Data to Business Telephones

71
 Speed dialling key information, data port parameter settings and business
telephone option settings can be downloaded to business telephones. The same
data can be downloaded to a number of business telephones. Downloading is
done when:
- the business telephone is connected to the telephone line;
- the board to which the business telephone is connected is replaced;
the business telephone is re-connected to the power source after having been
without power for an extended period. Some business telephones are line
powered, so local power loss is not a problem.
- the user enters a code or chooses a menu option to request downloading;
- the ISPBX system manager requests downloading using OM commands.
During downloading the Business Telephone is non-operational. However,
downloading cannot be started until the telephone set is idle; no call is released for
downloading.
• Day / Night Condition
The day/night condition of an ISPBX system determines where the calls for
assistance are routed. During day service calls are routed to the operators, during
night service calls can be routed to special night extensions. The ISPBX switches
to the day condition when at least one operator is present. The ISPBX switches to
the night condition when all operators are absence. The operator absent/present
status can also be used for traffic class switching. Traffic class switching is a
separate facility that is independent of the day/night conditions.

1.7.3. Prefix and Code Management

The system prefixes and codes are defined during software installation and can be
changed in an operational system using OM commands. Prefixes comprise the digits
0...9, * and # and an equivalent can be defined for rotary dial telephones.

Close Sign

The ISPBX waits for a close sign (the dialled digit #) before a dialled facility is
activated.

System option 28, wait for close sign.

1.7.4. Operational Maintenance (OM)

Operational Maintenance (OM) allows maintenance to be done on an operational

iS3000 series ISPBX. OM is normally done from an OM terminal, using Man Machine
Language (MML) commands, and a sub-set of OM functions can be done from an
operator desk, using numerical OM commands. It is possible to maintain any ISPBX

72
in a network from any operator desk or OM terminal in the network. It is also possible
to use the SysManager Maintenance PC application (SMPC) installed on a laptop
computer.

The current configuration of an ISPBX is described in an Office Data Manual (ODM).

This is a paper manual, generated using the configuration database at initial
installation time and kept up to date by hand. Most parts of the ISPBX configuration
database can be read-out using OM commands. If the ODM is not up-to-date any
more or is not available, OM commands are available to display the configuration of
the ISPBX system.

• System Integrity
- Passwords. The execution of a number of vital OM commands is protected by
a password. There are six password groups used for specific groups of OM
commands.
- Authority Classes. This is used to determine which OM commands are allowed
to be executed from a given OM device. Each OM device has authority classes
0...14 and each authority class has the status allowed or not allowed. Each OM
command is related to one of the authority classes.
- Restriction Levels. It is possible to prevent the execution of certain OM
commands for the maintenance of traffic classes and facility classes by
unauthorised persons. The set of unrestricted traffic classes and unrestricted
facility class marks can be defined for the different types of OM device.
• Software Upgrading
A number of printed wiring boards are equipped with Flash-EPROMs (FEPROM)
which enables the on-board software to be upgraded without having to remove the
boards.

1.7.5. System Customisation

When the system software is being configured a number of boundaries, options and
timers are chosen according to the customers' wishes or local requirements. Some
boundaries, options and timers are used throughout the whole ISPBX network, others
are only used for the local ISPBX. These boundaries, options and timers are
subsequently loaded into the system. A short description is given hereafter.

A boundary is used to reserve space in the system memory for the number of a
particular item, for example, the maximum number of night extensions. Boundaries
are shown like this in this manual:

Boundary xxx, <name of the boundary>.

73
 An option is used to determine whether a particular feature is used, for example, are
series calls allowed or prohibited? Options are shown like this in this manual:

System option xxx, <name of the option>.

A timer is used to define the length of time that a particular state can be active. This
is mainly to limit the time that system resources can be involved in a task to reduce
the risk of congestion. For example, the length of time that dial tone is given is limited
to ensure that tone generators remain available for other users. Timers are shown like
this in this manual:

Timer xxx, <name of the timer>.

Boundaries can almost never be changed in an operational system because a change

in a boundary results in a new partition of the system memory. Most of the options and
timers can be changed in an operational system using a Second Line Maintenance
tool, although it may be necessary to re-start the system to adopt the new values.

1.7.6. Performance Management

• Traffic Measurement
A group of resources can be observed to obtain average values (in intervals of 15
minutes) for the traffic handled. For example, the carried load (Erlangs), average
holding time of a resource, the number of seizures of a trunk line etc. This dynamic
traffic information can be used to determine the traffic handled at any moment and
if there are enough resources of a type available to handle this traffic.
Traffic measurement can be used to observe the following resources:
- bundles
- routes
- inter unit bundles
- inter unit routes
- extensions
- groups
- paging routes
- add on circuits
- RKT-SDT circuits
- SKT-RDT circuits
- incoming MFC circuits
- outgoing MFC circuits
- Socotel circuits
- convertors
- specific operators

74
 - queues
- switching network channels
- call data
- interunit traffic dispersion data
- dialled facilities data
- hatches
A traffic measurement session can be started manually or automatically at a pre-
defined date and time.
• Traffic Observation
The instantaneous dynamic and static data of all resources of a specific type can
be observed.
Dynamic data is controlled by the call processing software and can comprise
(depending on the type of resource):
- Number of busy resources.
- Number of ringing resources.
- Number of idle resources.
- Number of congested resources.
- Number of camp on busy situations on resources.
- Number of calls in queue of resource.
etc.
Static data shows the number of circuits, out of a pool of resources, which can
actually be used by the system:
- Number of resources out of service.
- Number of autonomously blocked resources.
- Number of not installed resources.
- Total number of resources in a pool.
• Load Monitoring
The CPU load in an ISPBX unit can be logged during a specified time interval. The
real instantaneous load (as a percentage) for the CPU can be continuously
displayed at an OM terminal.
• Reduced Resources Availability
For certain resources (mostly resources used in a pool) an alarm can be generated
when the remaining number of resources available for call processing drops below
a certain threshold. This gives a good indication of whether system expansion is
required.

1.7.7. Accounting Management

• Metering
Metering pulses are registered for outgoing calls if the extension being used has
the facility class mark for metering and if the trunk bundle used has metering.

75
 Metering results are stored in buffers in the system and can be subsequently read
out from an OM terminal.
FCM 10, metering.
• Taxmetering
Taxmetering allows the cost of an individual external call to be registered. The
operator can mark an assisted outgoing call for taxmetering by pressing a button.
After the call is finished, the extension number and the number of taxmetering
pulses (also known as Tics) are returned to the operator C-queue.
• Cost accounting for transferred callsThis can be used for normal extension
users who mainly have a mediating role. For example a secretary or a hotel desk
clerk. They often set-up external calls on behalf of another party. This facility
allows cost charging on the transferred-to party. If the requesting party is an
external party and the mediating party calls another external party, then after
transfer, the mediating party is still charged for the complete call. Even if FCM 69
is assigned to the mediating party. This is because the requesting party is external
and can not be charged for the call.
FCM 69, cost of call on assisted user.
• Cost Centre Dialling
Cost centres are used to allocate the cost of external calls to specific accounts.
The taxmetering pulses received for an external call can be registered to a specific
cost centre number.
The user dials a cost centre prefix followed by a cost centre number followed by
the external number required. At the end of the call a toll ticketing record is created
and the taxmetering pulses are registered to the cost centre number.
The cost centre number can have a maximum length of 12 digits. The length is
determined when the cost centre prefix is assigned. The cost centre number
'999999' is reserved for Malicious Call Trace requests.
There are three ways to use cost centres:
- Cost Centre Code without Validation
The cost centre number is not validated. Any number with the correct length
(1...12 digits) is accepted.
- Cost Centre Code with Modulo Validation
The cost centre number (6...12 digits) is checked using a calculation (the last
digit is a modulo check over the rest of the cost centre number).
- Cost Centre Code with Table Validation / PID Dialling
These two types of dialling use the same prefix. The number entered after this
prefix is either a cost centre number or a Personal IDentification (PID) code.
The PID can be seen as a personal cost centre number. Furthermore, the PID
code is related to a special (usually a higher) traffic class, which is activated
only for the duration of the call. This special traffic class is not the upgraded
traffic class of an extension but a traffic class assigned to the PID code.

76
 Cost centre numbers range from 1 to 12 digits while PID codes rage from 1 to
16 digits.
The cost centre number or PID code is either administrated and validated by
the ISPBX. This is referred to as Integrated Password Dialling (IPD). If the
system option for IPD is not set then this facility needs a SOPHO
SystemManager (with Access Manager) connected to the ISPBX.
• Toll Ticketing
Toll ticketing registers the details of outgoing calls. A toll ticketing record is created
for each outgoing call in the following cases:
- the extension being used has the facility class mark for toll ticketing;
FCM 26, toll ticketing.
- the trunk has the option for toll ticketing;
System option 60, FDCR instead of toll-ticketing.
- an extension user initiated a malicious call trace;
- an extension user dialled a 'cost centre' prefix preceding the trunk access
code;
- an extension user initiated a password call;
- the external line is transferred to the extension by the operator using the 'give
a line' facility;
- the number of received metering pulses or call duration has reached the
predefined threshold.
The toll ticketing record can be stored within the system or transferred to an
external output device. A toll ticketing record contains the following information:
- Cost centre number (maximum of 12 or 16 digits).
- Cost centre type (0...7).
- Department number.
- Business/private indication.
- Extension (Directory number/Calling Line Identity).
- IBSC of the initiator of the call.
- Preferred or Non-preferred route selected.
- Password indication.
- Number dialled. Number that is sent to opposite exchange (can be
suppressed) malicious call trace prefix+route, line number.
- Date and time.
- Duration.
- Units.
- Route+line number.
• Full Detailed Call Recording
The Full Detailed Call Recording (FDCR) facility provides output reports on all
incoming, outgoing and internal calls.
- incoming call: a call which enters the iSNet network;

77
 - outgoing call: a call which exits the iSNet network;
- internal call: a call inside the iSNet network.
These output reports will be used by an external call logging device for call
accounting and performance statistics. This facility provides an external interface
for complete recording of all incoming, outgoing and internal calls. Full toll-ticketing
functionality is offered by the FDCR facility.
System option 60, FDCR instead of toll-ticketing.
The following types of FDCR records are generated:
- Standard Record
For every call a standard record is made, at call termination, in the ISPBX:
_ of the terminating (connected) party, in case of internal calls;
_ of the terminating (called) party, in case of incoming calls;
_ where the call exits the iSNet network, in case of outgoing calls.
FDCR records will only be made for "real" calls. When a facility is initiated (e.g.
an extension user initiates follow-me or stores an IABD number) no FDCR
record will be produced. The standard record contains party information,
information about the answered/ not answered status and the answer delay
(the alerting/ringing time) and the call duration, the time the call was in the
conversation phase.
- Accounting Record
When toll-ticketing is active on the outgoing route, besides the standard record
an accounting record is also made for outgoing calls. This accounting record
contains the toll-ticketing information. An accounting record will be generated
for the internal party releasing the call if they are to be charged for the call. In
case of enquiry, the enquiry initiator is accounted for a subsequent external
call. When an operator or night-extension goes into enquiry, it is assumed that
assistance is provided. In this case the assisted party will be accounted,
provided that system option 4, call set up to individual metering, is set TRUE.
FDCR records are opened in one of the following situations:
- an extension is selected;
- a trunk is selected (seized);
- a call is queued (operator or COB queue);
- an enquiry (or subsequent) call is set up;
- a call is transferred;
- an add-on conference is started.
FDCR records are closed (transferred to the FDCR output file) when a call is
released, transferred or diverted.
A Standard Record contains the following items:
- Record header and reference number;
- Date and time;
- Party-A and party-B identities, each comprising a local party identity (12 digits)

78
 and a far-end (connected) party identity (20 digits);
- Party-A and party-B type (extension, assistance, PSTN-line, tie-line, paging);
- Answered status;
- Answer delay or ringing/alert time;
- Answer delay type;
- Record release reason (clear/answer/divert/transfer);
- Call duration;
- Internal Basic Service Category.
An Accounting Record contains the following items:
- Record Header and reference number;
- Destination (up to 36 digits of the dialled number);
- Password Indication (normal/password/call back call);
- Private/business call;
- Preferred/non-preferred route indication;
- Cost centre type (none/no validation/modulo-validation/table-validation of cost
centre) or malicious call trace indication;
- Cost centre number (maximum 16 digits);
- Personal identification code (password facility);
- Department code;
- Metering pulses;
- Call duration time.
Accounting records can also be generated at DPNSS transit nodes.
With SOPHO Management@Net, the successor of SOPHO SysManager, you can
have 'real-time' FDCR information over a TCP/IP interface. FDCR information is
also available over a V.24 interface. Either one of the two interfaces (TCP/IP or
V.24) is active. It is not possible to use FDCR on both interfaces at the same time.

1.7.8. File Management

All information in the ISPBX is stored in files. System software is distributed as a

number of files on CD-ROM, floppy disks or can be downloaded via NSOnet (SIR).
These files are initially loaded onto an external computer and then transferred to the
back-up device of the ISPBX. When the ISPBX is started the required files are read
from the back-up device by the CPU and the CPU can then go into normal operation.

OM commands can be used to read, display, delete, create or copy files that are
located on the back-up device.

• File Names
A file is identified by:
- Logical device name (maximum 6 characters), indicating where the file is
stored;

79
 - File name (maximum 6 characters);
- Extension (maximum 3 characters): extensions for CPU system files are fixed;
- Generation (one digit between 1 and 9): of the same file only the last 8
generations are stored. If a new generation is created and already 8
generations of the same filename and extension are present on the device, the
oldest generation is deleted. After generation number 9 is reached, the next file
with the same filename and extension will be assigned generation number 1.
At the moment a file is created or operated on, the ISPBX may add additional
information to the file entry:
- Protection levels of the file (NARD). For each file the protection levels for New,
Append, Read and Delete the file can be assigned one of the levels 1 to 7.
- Date and time of the creation of the file;
- Date and time of the last modification of the file;
- 12 NC number of the file (if the file is part of a software package);
Default and current authority class (if the file represents an OM (sub)command
file);
- Current authority class index of the file (if the file represents an OM (sub)
command file).
- Snapshot Identification Number (SIN) number of the file (for a MIS file or
journal file);
- Reference name: sometimes an OM (sub)command or SAS file does not
contain any software but refers to another file (reference name) that contains
the concerning software program.
- Type and subtype of the file.
- Description field (a short description of up to 40 characters can be added).
• File Storage Devices
- The ISPBX is equipped with a back-up device to retain system data in the
event of power failure.
- The Disk Emulator software program runs on an external computer that allows
the external computer to act as a storage medium for the ISPBX.
• Protection Levels
Each file and each OM device are assigned 4 protection levels. If the system
manager wants to perform an operation on a file, the protection level of the OM
device being used must have the same or higher value as the protection level of
the file being operated upon. The 4 protection levels are :
- New
If a file is being created then it receives the NEW value of the OM device on
which it was made. If a file is being copied then the NEW value for the OM
device must be the same or higher than that of the file.
- Append
This protection level is not used for system manager applications.

80
 - Read
If a file is being displayed or copied then the READ value for the OM device
must be the same or higher than that of the file.
- Delete
If a file is being deleted then the DELETE value for the OM device must be the
same or higher than that of the file.
The protection levels for an OM device can be changed using OM commands.
Upgrading the protection levels of an OM device is password protected.
• Initial Configuration File
During the installation of a new ISPBX system the CPU must be loaded with the
software program needed for the operating system, call processing, operational
maintenance and system assurance. These programs do not contain information
about the configuration of the system itself. The configuration information is stored
in configuration files. These are known as the Project Engineering (PE) file and the
Logical Local (LL) file. The PE and LL files are prepared off-line using the SOPHO
Configurator Package (SCP) and Project Generator 2 (PG2) software tools. The
SCP and PG2 tools are used to enter the customer requirements (size and
configuration) and the country dependent aspects of the ISPBX.
After the system software has been installed the configuration files can be loaded.
These files contain the total configuration of the system in the form of a series of
subcommands (readable format) that are executed when the CPU of the ISPBX is
activated (initial start). The PE file contains the specification of the boundaries,
options and timers for the system. These are used to create the necessary
partitions in the ISPBX CPU memory for the configuration database. Once the
partitions have been created, the necessary information can be stored in them.
This information is stored in the LL file.
When the configuration database is filled, the CPU starts testing all hardware in
the system and setting all hardware into service. Now the ISPBX is fully
operational.
• Instantaneous Configuration File
When an ISPBX system is operational for a while and a lot of changes are made
to the configuration it is possible to generate a readable file containing the
instantaneous configuration.
The instantaneous configuration database in the CPU memory can be converted
into subcommands and stored in PR and OR files (equivalent to the PE and LL
files). These files can be examined and the instantaneous situation can be
determined. It is also possible to note any changes in the original Office Data
Manual.
By generating these instantaneous configuration files it is also possible to change
boundaries in the configuration database. The concerning boundary can be
adapted in the PR file. The files are renamed as PE and LL files and transferred to

81
 the CPU. With a restart the change is effected.
• Memory Image Snapshot File
When the configuration of an ISPBX system is initially loaded, this process
involves executing the initial configuration files, which comprise subcommands, to
build up the configuration database. During the operational phase of an ISPBX
system the configuration can be changed using OM commands. For CCS and
CPU3000 based systems, these changes are written to a journal file, also as
subcommands.
After a power failure the configuration of the system must be restored. One way to
do this would be to execute the initial configuration files and then the journal file.
This could take some time.
The system manager should generate a Memory Image Snapshot file (MIS-file)
immediately after installation, at regular intervals and after a large configuration
change. This generates a bitmap copy of the configuration data. After a power
failure the MIS file can be loaded much quicker than it would take to execute the
initial configuration files and the journal file.
• Journal File (for CCS and CPU3000 based systems)
During the operational phase of an ISPBX system the configuration can be
changed using OM commands. These changes are written to a journal file, as a
series of subcommands. After a power failure the configuration of the system must
be restored. This is done by loading the newest MIS file and then executing the
journal file. For safety reasons it is advisable to make a firecopy of the MIS file on
an external device (for instance to a floppy disk).

1.7.9. Maintenance Mode - CPU3000 Platform only

The CPU3000 can be upgraded using the software and configuration files stored on
the Local BackUp device (LBU). The CPU3000 also supports a specific upgrade
concept that is called Maintenance Mode. The basic principle of Maintenance Mode
is the separation of the "new" software and configuration files on the DBU from the
"original" software and configuration files on the LBU.

82
Figure 1-6 Dual disk principle.

In Maintenance Mode, the system uses the software and configuration files on the
Dual BackUp device (DBU). This gives the CPU3000 platform the possibility to
fallback to its original configuration stored on the LBU when something goes wrong
during the upgrade using the files on the DBU. Before Maintenance Mode is entered
the new CPU software, the new firmware and the original or new configuration files
have to be copied to the DBU. During Maintenance Mode Operational Maintenance
can be performed. Once the new configuration is properly installed, it can be made
definitive by stopping Maintenance Mode.

1.7.10. Dual Mode - CCS Platform only

A CCS system can be split in two separate units called clusters. Each cluster
comprises two of the four CCS boards. It is possible to use one cluster as the
'operational' cluster to run the system and the other one, the 'stand-by' cluster, for
upgrading purposes. This is called Dual Mode. In Dual Mode, the operational cluster
uses the Local BackUp device (LBU) and the stand-by cluster uses the Dual BackUp
device (DBU). In this case the new software and projecting files can be loaded into the
CCS boards which are standby. Switching over takes as long as an operational start.
After switching over, the other CCS boards are standby. When stopping the Dual
Mode, these CCS boards are synchronized with the operational CCS boards. With
Dual Mode, the system down time during upgrade is considerably reduced. Note that
after the split, there is no redundancy in the operational CPU section. If a CCS board
fails in the operational cluster, the system goes down.

1.8. ServicePlus Remote Support

Remote Support interfaces fully support the installed base of SOPHO ISPBXs. The
Remote Support functionality can be found at three locations:

1. Customer Site

83
 The features offered at the customer site are:
- Establishment of password/call-back connection, with 4-level password
protection.
- Interactive remote diagnostics, remote operational maintenance (OM), and
remote configuration.
- Unattended remote alarming (alarm detection and transmission).
- Buffered file transfer (e.g., for transferring emergency load files or traffic data).
- Data recovery, transparency and protocol translation.
- Look-over-the-shoulder (specialist in Remote Support Centre can monitor/
assist field engineer on site via remote "parallel" connection to the engineer's
PC).
- Local language.
- 230 V AC power or no-break 48 V DC power.
- Power relays (optional).
- Integrated solid-state announcer for ISPBX Music On Hold applications
(optional).
2. Central Remote Support Centre (RSC)
In the central Remote Support Centre there are Help Desk PCs used by second
line support staff, for accessing the customer's ISPBX through a remote
connection. The Help Desk PC is a standard MS-DOS, IBM compatible PC. The
application software consists of readily available tools, e.g. Maintenance PC,
Procomm (Terminal Emulator), and miscellaneous "freeware" tools. Help Desk
PCs may be integrated in a local area network. In such a case there is no explicit
requirement to have a dedicated PC for Help Desk tasks, these can in principle be
executed on any PC in the network. Freeware tools include:
- PROCOMM scripts;
These scripts assist the RSC engineer in establishing dial-up connections to
remote ISPBXs, alleviating him from routine tasks.
- A customer database program, written as a FoxPro 4GL MS-DOS application;
All data relevant for providing Remote Support to a particular customer is
available on-line to the RSC engineer. With one keystroke, the RSC engineer
can initiate set-up of the remote connection and start the required maintenance
tool. This program simplifies the engineer's administrative tasks.
- Administrative Text Generator (ATG).
An MS-DOS program that converts SOPHO files into easy-interpretable text
files.
The Remote Support Centre has one dedicated Alarm Receiver PC. This PC -
operational 24 hours per day - receives alarm messages transmitted from the
customer site. Messages are logged on the hard disk, displayed on a screen and
printed on a local or remote printer. Alarms can signalled via paging equipment or
via the serial port of the PC to other external equipment. The Alarm Receiver PC

84
 is a standard MS-DOS, IBM compatible PC. Its application software is the SOPHO
Fault Manager Light.
3. Field Engineer
The engineer in the field (e.g. with out of hours duty) can make a remote
connection to a customer site using a laptop or notebook PC with built-in modem.
From field operations management point of view, it may be desirable for safety
reasons to make such connections through the Help Desk PCs using a two-step
automatic (unattended) connection set-up. In this case the telephone number and
password of the customer's remote support connection would not have to be made
known to the field staff. However, this requires continuously operational Help Desk
PCs.

Remote Support Facilities

- Remote Alarming
This service ensures that a detected alarm will be routed immediately to the Philips
Remote Support Centre, and will be followed up with appropriate action right away.
Features are:
- Continuous, 24 hours a day, 365 year round guarding of the system;
- Automatic alarm routing to the RSC;
- Optional automatic alarm routing to customer's own security or service officers
(requires optional printer).
- Remote Back-up
Ensures that at regular intervals or at specific moments a back-up will be made of
all important ISPBX configuration data. Features are:
- Back-up frequency at Philips recommended intervals or according customer's
wishes;
- Automatic storage of back-up in a safe place.
- Snapshot
Gives the customer a readable and exact description of the actual ISPBX
configuration and programmable system data.
- Personal Telephone Book
Provides the customer with a telephone book containing a usage guide and a
telephone directory specific for his ISPBX configuration. Maintenance of the
telephone directory can be provided as an option.
- Moves and Changes
Allows specialists from the Philips Remote Support Centre to carry out
modifications in the operational ISPBX configuration data, to adapt the system to
moves and changes in the customer's organisation. Features are:
- Modifications can be requested in several formats (bulk or single item) and
media (mail, facsimile);

85
 - Timing of modifications scheduled according customer's wishes;
- Modifications limited to a particular maximum (depending on payment-
scheme);
- Customer receives overview of modifications on regular basis.
- Traffic Measurement
Provides the customer with a report containing a survey of the measured voice
and/or data traffic. Optionally a detailed analysis of the measured data can be
made, which includes recommendations for optimising the ISPBX configuration.

1.9. General System Features

1.9.1. Number Analysis

An ISPBX analyses the numbers it receives; numbers dialled by extensions and

numbers sent to it by incoming trunk lines. A number can be the number of an
extension or a facility code. The following must be analysed:

- Is the number dialled an existing (valid) one?

- Is the dialled digit allowed? Does the extension have the proper traffic class to dial
this destination?
- In case the extension dials a code. Is he allowed to use this code? Does he have
the corresponding facility class mark?
- Is the number an existing one but barred?
- What is the number length the ISPBX can expect after this digit?
- What is the destination (in case a trunk access code was dialled)?
- Where should the ISPBX wait for dial tone (in case of an external number)?

This analysis takes place in the so-called number analysis scheme. A number
analysis scheme consists of trees and the trees consist of tables, present in the
memory of the CPU controlling the ISPBX.

In a table one digit is analysed. Each table (also called a pyramid) has its own unique
number. It has one inlet and 16 outlets: the digits 0 to 9, the * and the # and the letters
A, B, C and D. These 4 letters are not (yet) used, because they are not present as
keys on a normal telephone set. Each outlet has a result identity attached to it. The
following possibilities exist:

- No direct result. The digit(s) dialled so far are valid, but no conclusion can be
drawn yet. Further analysis must take place in another table.
- The selected number or code tells the ISPBX for what it is used.
- Non-existing number. Number unobtainable tone is sent.

86
If more analysis must take place, the combined tables form trees. If a 4 digit number
must be analysed 4 levels of tables are necessary. A number analysis scheme
consists of more than one tree. We make a distinction between an internal numbering
scheme and an external numbering scheme. The internal numbering scheme is used
for internal extensions dialling internal numbers and internal codes. Also the tree for
Direct Dialling In (DDI) belongs in this numbering scheme. The external numbering
scheme is used for Direct Dialling Out (DDO) to analyse everything that is dialled after
a trunk access code. Here it is checked if the internal caller has the minimum required
traffic class.

• Internal Number Analysis Scheme

The internal numbering scheme contains two types of trees:
- The trees to analyse numbers coming from extensions and operators are
divided into Dial Types. The dial type indicates how the start of the analysis
tree is reached.
- The trees for Direct Dialling In (DDI). Each incoming route is linked to a tree for
DDI.
The following dial types exist:
- Initial Extension Dialling (00);
Used for extensions which dial a number directly after going off-hook. There is
one analysis tree per analysis group. In this way analysis groups are used to
split an ISPBX into independent groups.
- Initial Enquiry Dialling (01);
Used to analyse digits dialled directly after pressing the enquiry button on an
extension. There is one analysis tree per analysis group. In this way analysis
groups are used to split an ISPBX into independent groups.
- Initial Operators Dialling (02);
Used for operators directly after pressing PA, PB or B key.
- Post-dialling (03);
Used if digits are dialled by extensions after receiving busy or number
unobtainable tone, e.g. to initiate automatic ring back.
- Alternative Destination Dialling (04);
Used after dialling the "Activate Follow-Me (FM) from Primary" code. This code
is analysed in the tree for Initial Extension Dialling, which points to this tree.
The destination number is analysed in this tree.
- Follow-Me Primary Dialling (05);
The digits dialled after the "Activate Follow-Me from Destination" prefix are
analysed in this tree.
- Pick-Up Destination Dialling (06);
The digits dialled after the call pick-up prefix are analysed in this tree.
- Executive / Secretary Dialling (07);

87
 The digits dialled after the executive / secretary prefix are analysed in this tree.
- Overlay Time Out Dialling (08);
Used when no digits are dialled after the overlay digit within a given time
(system timer 197). This is especially made for hotels.
- Overlay Continue Dialling (09).
Used when more digits are dialled after the overlay digit within a given time
(system timer 197). This is especially made for hotels.
Each of these dial types has one or more (in case of dial types 00 and 01) trees.
Each tree has a unique tree number.
Incoming numbers (internal numbers and codes) are analysed in the trees for DDI,
which are linked to the incoming routes.
Each extension is associated with an analysis group. Each analysis group can
have a number of dedicated analysis trees for initial dialling and enquiry dialling.
Up to 255 analysis groups and up to 255 analysis trees can be defined.
• External Numbering Scheme
The main purpose of the external numbering scheme is to test if the extension user
is allowed to dial an outside number by checking the traffic class. The external
numbering scheme is also used to indicate when the ISPBX should wait for the
second external dial tone. The Direct Dialling Out trees are linked to destinations.
Each connected other exchange has a destination number. If an extension user
wants to make an outside call, first the trunk access code must be dialled. This is
"Initial Extension Dialling" and therefore it is analysed in the internal numbering
analysis scheme. There result identity "Trunk Access Code" refers to the
destination. Then the external number is analysed in the concerning tree for Direct
Dialling Out.
• Free Numbering Scheme
Free numbering offers flexibility in the numbering scheme. It allows free allocation
of DNRs in a complete iSNet network. The number can be moved from one ISPBX
to another while keeping the facility class marks, traffic classes, compatibility value
etc. Free numbering is available for all the variants of iSNet networks. An iSNet
WAN is a wide area network consisting out of two or more PABXs connected via
DPNSS, PVN, ISDN, QSIG or analogue tie lines. Network management is very
important when using Free Numbering. The MAC-Manager module of
SysManager 410 is used to distribute the correct information through the complete
network.
All DNRs in a free numbered network are in the Free Number Database, managed
by the MAC Manager. This database maintains the location of each number in the
network. The location of an ISPBX is identified by its cluster-identity. A free
numbered network can be part of a larger network. A DNR in such a free
numbered sub-network can not be moved outside that sub-network (and vice
versa).

88
 Software licence 25, free numbering.
System option 40, closed number scheme in network. Since Free numbering
requires unique DNRs over the entire network, a closed number scheme is
mandatory.
System option 106, free numbering active.
Boundary 307, maximum number of free numbers. 21700 in cas of CPS and CPU-
ME/MT systems. 65530 in case of CCS systems.
Because each ISPBX in an iSNet network must know the location of each DNR in
the network, the ISPBX with the smallest amount of RAM-memory determines the
maximum number of Free Numbers.
To define the maximum of Free Number database entries that can be projected in
an ISPBX the maintenance engineer can use the tool MEMCAL.
• Open or Closed Numbering Scheme
It is possible to use a closed or open numbering scheme in DPNSS networks.
- Open numbering scheme. The same directory number can be used in different
clusters.
- Closed numbering scheme. All directory numbers in the network are unique.
The directory numbers in one cluster may start with the cluster identity.
- Extended open numbering scheme. Similar to the open number plan, but with
the possibility to create a third identification level:
1. Cluster directory number.
2. Local-cluster directory number, making it possible to identify an ISPBX
within the cluster. iS3000 nodes within a cluster may be connected using
DPNSS links (besides IMP-connected iS3000 systems).
3. Local directory number.
The local-cluster directory number and local directory number together are still
6 digits, and can be freely divided.
All clusters in a DPNSS network are identified by a 1...6 digit cluster identity.
System option 40, closed numbering scheme in network.

89
 Figure 1-7 Example of an open, closed and extended open numbering scheme.

• Direct Dialling In
Number analysis for DDI can be defined for each incoming route. DDI of up to 6
digits can be analysed. The DDI route is also assigned a compatibility value and a
traffic class, which are used by number analysis to determine if the requested
connection is allowed. If DDI fails (destination extension is set for do not disturb or
DDI barred, dialled number not assigned, traffic class of route insufficient,
compatibility connection allowance between route and called party not allowed,
called party busy, called party does not answer) then the call can be rerouted to
operator assistance.

90
• Direct Dialling Out
Number analysis for DDO can be defined for each outgoing destination. DDO of
up to 16 digits can be analysed. DDO numbers can be checked for a number
length of up to 20 digits.
• Multiple Number Lengths
It is possible to define an internal numbering scheme using numbers of different
lengths, provided the initial digit(s) are unique. It is also possible to define an
internal numbering scheme using numbers of different lengths for extension
dialling, where a short number is the same as the initial digits of a longer number.
This is done by using a dialled digit timer.
Timer 197, overlay dialling time, 1...8 seconds.
• Single Digit Dialling
This allows single digits to be used for specific services (e.g. hotel), even though
these digits are the same as the first digits of extension numbers. The system
distinguishes between single digit dialling and normal dialling using a dial time-out
on the first digit.
Timer 197, overlay dialling time, 1...8 seconds.

1.9.2. Audio Functions

• Tones
System tones can be freely defined, using a set of standard tone sources. The
following tones can be defined:
- Add-On Ticker Tone
- Announcement Tone
- ARB Destination Ring Back Tone
- Break-In Ticker Tone
- Busy Tone
- Bypass Tone
- Call Waiting Ticker Tone
- Call Waiting Tone Burst Repeated
- Call Waiting Tone Burst Tone
- Camp on Busy Tone to Caller
- Confirmation Tone
- Congestion Tone
- Delayed Hot Line Dial Tone
- Diversion Active Dial Tone
- Enter Password Tone
- External Ringing Tone
- First External Dial Tone
- Internal Dial Tone

91
 - Internal Ringing Tone
- Music on Hold
- Number Unobtainable Tone
- Paging Absent Tone
- Paging in Progress tone
- Park Tone
- Routing Tone
- Second External Dial Tone
- Through Connect Ring Tone
• Ringing
The following system ringing rhythms can be freely defined:
- Internal Ringing Rhythm
- External Ringing Rhythm
- Automatic Ring Back (ARB) Ringing Rhythm
- Emergency Alarm Ringing Rhythm
- Through Connect Ringing Rhythm
- Message Waiting Ringing Rhythm
Ringing current is sent to analogue telephone sets, messages in the D-channel are
sent to digital telephone sets and line adapters.
• Music On Hold
An internal party or a trunk/tie line that is placed in the hold condition by either an
extension or an operator (including the W-queue) can be sent music on hold. The
source for MOH may be either an external one (continuous) or the integrated
digital announcement server.
• Time Limits on Dialling, Ringing and Tones
The actions of the call set-up phase (dialling the number by the initiator, sending
tone to the initiator, sending ringing current to the destination) are guarded by time
limits. This prevents deadlock situations in the ISPBX CPU. If a timer expires the
call is aborted and the involved resources are released. A summary of the various
timers is given hereafter:
- Making an Initial or Enquiry Call
Timer 000, time limit between off-hook or enquiry and first digit, 4...10 seconds.
Timer 001, time limit between digits, 4...10 seconds.
- Initiating Post Dialling
Timer 004, time limit between busy tone and 1st digit, 4...10 seconds.
- Making a DDO Call
Timer 002, time limit between trunk access code and 1st digit, 4...10 seconds.
Timer 012, time limit between digits when number not complete, 5...16
seconds.
Timer 003, time limit between digits when number may be complete, 3...10
seconds.

92
 - Guarding a DDI Call
Timer 042, time limit between incoming trunk seizure and 1st digit, 5...50
seconds.
Timer 043, DDI time limit between digits, 5...20 seconds.
- Time Limit on Ringing
Timer 005, internal ringing time, 60...180 seconds.
Timer 010, external ring tone time, 60...240 seconds.
Timer 011, automatic ring back ringing time, 20...60 seconds.
Timer 027, night extension ring tone time, 60...240 seconds.
Timer 158, recall ringing time, 20...40 seconds.
- Time Limit on Tones
Timer 006, internal tone limit time, 2 seconds...30 minutes.
Timer 041, DDI tone time, 5...360 seconds.

1.9.3. Connection Management

There are a number of ways in which a connection can be allowed/prohibited:

• Number Analysis Groups

Up to 255 groups of users (extensions, trunks, operators) can be created. Dialled
information is analysed according to the user group of the caller.
• Service Check
Here the 'service' of the caller (for example speech, data, fax) is checked against
different types of information that can be transferred in 64 kbps channels and is
used mainly when referring to Integrated Services Digital Network (ISDN).
• Compatibility Connection Allowance
This can be used to create up to 255 groups of users within the system that are
able to communicate. This applies to extensions and trunks, but not operators.
• Traffic Classes
This determines the destinations that a user may dial and is used mainly for cost
control. There are 8 levels of traffic class, the destinations allowed in each level
can be customised.
- An extension has four traffic classes: day, night, upgraded and downgraded.
- An operator has a day traffic class.
- A night extension has a night extension traffic class.
- Incoming DDI routes have a traffic class that is used in both day and night
condition.
The day and night traffic class are used when the ISPBX is in day or night service
respectively. This situation is normally determined by the presence of operators or
by the time and day of the week. The upgraded and downgraded traffic class are
selected by password dialling.

93
 System option 17, system clock or operator presence determines day/night status.
• Facility Class Marks
Some facility class marks prevent connections being made, for example do not
disturb protects an extension against incoming calls.

1.9.4. Remote Contact Control

An extension user can operate a piece of equipment which is situated at a remote

location. There are two types of remote contact control:

- Intercom and Door Opener

A caller presses the doorbell, which is heard at various points. Any extension can
then be used to dial the door intercom. The extension user can activate the door
opener from the extension.
- Common Answering Emergency Service
Someone dials the alarm number. An acoustic alarm is sounded. A member of the
emergency services hears the alarm, goes to the nearest ISPBX extension and
dials a code. A speech path between the emergency calling party and the
answering party is established. At the same time the alarm is turned off.

1.9.5. Emergency Switchover

It is possible to connect a number of telephone sets directly to trunk lines in the event
of complete system failure. This situation can be simulated for test purposes even if
the ISPBX is functioning normally.

1.9.6. Voice Logging

Internal telephone calls can be tapped. The tapped party is called ' voice Logging
subject' and the log is sent to a 'voice logging destination' (a recorder). The subject
and the destination are both DNRs (no group DNR) in the same ISPBX or the same
multi unit configuration. Voice logging is started by a password protected OM
command. The OM command includes the DNRs of the voice logging subject and
destination. Once a relation between a voice logging subject and a voice logging
destination has been set up, speech channels are offered to the destination each time
that the subject gets involved in a call. The speech paths of all parties that are involved
in the call are tapped. (In case of an add-on call on all three members. In case of an
enquiry call, the active parties when the voice logging subject is active, otherwise
silence or music on hold.)

In the silent monitor (listen-in) function with Call@Net 2.10 the connection with the
tapping party is not built automatically. A tapping party, authorised by a facility class

94
mark, dials a prefix followed by the DNR of the internal party that has to be tapped.
This can not be initiated by the operator or via CSTA. It is possible to initiate listen-in
calls between extension in the FIN/DPNSS/iSNet QSIG network, assuming that both
the tappping and the tapped party have Call@Net 2.10 or higher.

Since Call@Net 2.11, simultaneous listen in calls to the same tapped party is possible.
Upto 16 simultaneous listen in calls to the same tapped party can be made. This can
be either 16 tapping parties or 1 voice logging destination and 15 tapping parties.

The parties are not aware of the fact that they are being logged, no signalling is sent
to the parties. The voice logging call is terminated when the voice logging subject
leaves the call or the voice logging destination terminates the call.

If it should not be possible to call voice logging destinations directly, they can be
protected by means of compatibility values.

Licence 48, voice logging.

Boundary 358, maximum number of voice logging relations.

Restrictions:

Voice logging is realized by using the add-on circuits on the PMC boards. Each PMC
has 10 add-on circuits. The add-on circuits are also used for three party calls and for
the break-in facility. The number of add-on circuits determines the maximum number
of simultaneous voice logging calls.

When the voice logging destination (a recorder) is accessed via an ATU-SS trunk,
then the destination must also support polarity detection to prevent not released trunk
lines.

To log calls of both parties in a twinning relation both extension-DNRs must be

entered as voice logging subject with a voice logging destination.

Voice logging destinations do not allow diversion.

1.9.7. Full Secrecy

In the normal speech condition between two parties the connection is offered full
secrecy. No other party is able to listen in on the connection without being noticed. If
a third party is involved in a speech connection (for instance, an add-on conference
or the operator breaks in) the ISPBX will send a tone to all involved parties to indicate
the loss of privacy.

95
 1.9.8. Alarms

The System Assurance (SAS) software regularly tests system resources (parts of the
hardware or software). If the system detects a problem with a system resource it tries
to pinpoint exactly where the problem lies. Once the problem has been localised SAS
resets any activities affected by the problem. In some cases faulty equipment is
isolated, so that it can no longer be used. SAS then reports the fault as an alarm.
Finally SAS tries to recover operation by trying to bring faulty equipment back into
service.

• Alarm Types
Alarm priority is given as follows:
- Major Alarm. An essential resource has failed. Take action immediately.
- Minor Alarm. Less important resource failure. Take action when convenient.
- Blocked Alarm. Less important resource failure. One or more resources are not
available for call processing any more.
- Silent Alarm. One or more resources in a pool are not available for call
processing any more. A silent alarm is not signalled, however it is possible to
read out the alarm information.
• Alarm Routing
Major, minor and blocked alarms can be signalled to the following destinations:
- Remote Maintenance Centre (RMC). If the RMC is unavailable then the alarms
can be routed to an alternative destination.
System option 49, signalling at distance present.
- Operator desks, by an audible and visual indication. The operator
acknowledges the alarm by switching the audible signal off.
- External alarm device, by an audible and visual indication. It can also be used
to trigger another alarm device, for example a bell or hooter. The alarm can be
acknowledged and the audible signal is switched off.
• Alarm Codes
When an alarm has been signalled a service engineer can read out alarm reports
to gain specific information about the problem and take the appropriate action
required to solve the problem.
• Externally Generated Alarms
It is possible to connect alarm outputs of external equipment to the ISPBX, such
that an external alarm condition is signalled via the same channels as an internally
generated alarm. For example, a smoke detection system can signal a fire in the
ISPBX room.
• History Buffers
Alarms, SAS reports and other events of interest to a maintenance engineer are
logged in a series of history buffers. Each history buffer can hold a specified

96
 number of reports. A history buffer can be read out using OM commands.
• Freeze Function
In exceptional circumstances a part of the software may not be functioning
properly. This would normally result in an operational start of the ISPBX system.
Instead, it is possible to freeze the faulty part of the software and then an
operational start is not done. When this happens some resources are not released
and a degradation of system performance may result. At a convenient time, during
quiet hours, an operational restart can be performed manually to release any
frozen resources and thereby restore a completely operational system.

1.9.9. Test Telephone

A test telephone can be used to dial a specific trunk line and get a connection with that
trunk without any number analysis. The user can then check the correct operation of
the signalling with the distant exchange by dialling directly on that trunk, without any
checks on the dialled number.

FCM 13, test call entitled.

1.9.10. System Load Control

Call processing has the highest priority with regard to CPU capacity. Other
applications (system testing, operational maintenance etc.) have a lower priority.

1.9.11. Terminal Downloading

Terminal downloading enables a maintenance-engineer to download new software

into the ErgoLine D325 (for the time being only this terminal is supported) without
replacing any hardware. Terminal downloading can be done from a centralised
location, for example a remote maintenance centre. It is initiated via an Operational
Maintenance command. The firmware package must be on the Local BackUp device
(LBU). If a network wide upgrade is performed all units must have the file stored on
their LBU.

Only idle terminals are downloaded. After a download action of the terminal, the
maintenance engineer can check whether the download was successful or not.

The ErgoLine D325 is connected to a DTX-I, DLX-U, DLC-U with PNT1 or DLX-L with
NT1. Some boards need a new firmware package to support the specific feature; see
the following table.

97
 BOARD FIRMWARE PACKAGE
PMC F141.05.01 /F151.05.01
DTX-I F203.11.01
DLX-U F300.04.01
DLC-U with PNT1 F213.07.01
DLX-L with NT1 F400.03.01

Table 1-5 Firmware package of boards.

The PPU does not support terminal downloading.

98
2. SOPHO iS3000 Architecture
2.1. Introduction

The SOPHO iS3000 Series is designed to cover the communication needs of small to
very large organisations. This series of ISPBXs comprises a number of models that
have been optimised to different business sizes within the range of 20 to about 65530
extensions. These models are:

- The iS3010, supporting up to 96 ports; 10-80 extensions;

- The iS3030, supporting up to 608 ports; 50-608 extensions;
- The iS3050, supporting up to 1216 ports;200-1000 extensions;
- The iS3070, supporting up to 3300 ports; 500-3000 extensions;
- The iS3090, supporting up to 10000 ports. 2500-10000 extensions.
(In a networked or distributed configuration the number of ports exceeds 65000.)

A port can either be used for a telephone connection or a trunk line connection.

An extension is a telephone set connected to an ISPBX.

Open to standards and new technologies

The iS3000 Series supports all major industry standards. This is due to the continuing
strategy of Philips Business Communications to support and implement industry
standards. Philips Business Communications is also an active member of
standardisation bodies and related user forums. The iS3000 is open to new
technologies and standards through its unique flexible architecture. This also enables
the whole system to grow, both in size and functionality, following the requirements of
changing organisations.

All models of the iS3000 Series have been designed for low power consumption. They
operate under room temperatures thus saving the costs of air-condition equipment.

The different types of line cards (for analogue, digital, ISDN or cordless use) may be
used in all models of the iS3000 Series.

The basis of the open and modular structure of the iS3000 Series is given by three
building blocks, each designed around Euro-ISDN.

- The Switching Network

The iS3000 Series provides a fully transparent and non-blocking switching matrix
for 64 kbit/s Euro-ISDN communications.
- "Intelligent" Universal ISDN Interface Board

99
 The iS3000 uses a universal ISDN interface board that makes no distinction
between internal and external lines. All of the boards' 15 ISDN circuits can be
freely allocated to act as extension lines, trunks, tie-lines or operator lines. Just
one common board for all types of ports, which are configured using software, not
hardware. The software of this board can be downloaded.
- Euro-ISDN Kernel
The SOPHO iS3000 Series is designed for open connectivity, with system
software being structured around the Euro-ISDN kernel. Euro-ISDN forms the
basis of all new business communication standards. These include access to the
public network, on-the-desk multimedia applications, DECT cordless
communications and QSIG multivendor networking.

The iS3000 models are based on a uniform hardware platform and one and the same
system software. They form a series of scalable ISPBXs with a maximum of user
compatibility.

2.2. System Architecture

The uniform hardware platform provided across the different models is based on a
distributed architecture, dividing the platform into the following functional modules:

- the Central control Module (CM);

- the Switching network Module (SM): this module is not required in all models;
- the Peripheral Module (PM).

More details about these modules and the printed circuit boards (PCBs) used are
given in the following sections of this chapter.

100
Figure 2-1 SOPHO iS3000 Series basic design.

The printed circuit boards (PCBs) are installed in shelves. A standard back-panel at
the rear of each shelf interconnects the different PCBs and provides them with power.
The shelves are housed in compact cabinets which may be wall mounted or free
standing. PM, SM and CM shelves are combined in one or more cabinets. To allow a
larger distance, one or more PMs may be installed on a remote location in a separate
cabinet. The difference between a local and a Remote PM (RPM) is the fact that the
links with the local module are longer. To allow this, some special actions have to be
taken. These actions are explained in section 2.3. "Peripheral Modules".

Fault-tolerant capabilities

The ISPBX can use a fault-tolerant Central Module to assure maximum system
availability. Four identical Central Control Slices (CCS) operate in parallel, according
to the Philips patented 4/2 concept. This concept is described in section 2.6.2. "The
CCS". It is also known as redundancy therefore an ISPBX using the 4/2 concept is
called an iS3000-Redundant.

The SM of an iS3070-Redundant has 2 Switching Network Slices (SNS).

For the SM of an iS3050-Redundant it is an option to configure it with one or two SNS

boards. The iS3090 always has redundancy in both CM and SM.

The connection to extensions, external lines and other auxiliary equipment is made at
a Main Distribution Frame (MDF). The MDF may be located within the cabinet, in a

101
 separate MDF cabinet or externally. More details can be found in section 2.8. "Main
Distribution Frame".

The iS3010 and 3030 models can be powered directly from the mains (230 VAC). An
optional battery or Uninterrupted Power Supply (UPS) can be installed to provide
continual operation in the event of a power failure. The other iS3000 models are
powered from an external DC source (42...60 VDC), which can be mounted in a
standard cabinet. More details on the power supply are given in section 2.7. "Power
Supply".

The iS3000 models can be divided into the following groups:

1. CCS based systems;

These systems are equipped with a Control & Switching Module (CSM) shelf,
which comprises the CM, the SM and a PM. These systems are referred to as CCS
systems because the CM consists of Central Control Slice (CCS) boards. CCS
systems are:
- SOPHO iS3090;
- SOPHO iS3070;
- SOPHO iS3070-Redundant;
- SOPHO iS3050-Redundant.
2. CPU3000 based systems.
These systems are referred to as CPU3000 systems because they are equipped
with a Central Processor Unit - 3000. The systems comply with the CM, SM and
PM structure. CPU3000 systems are:
- SOPHO iS3050;
- SOPHO iS3030;
- SOPHO iS3010.

2.2.1. SOPHO iS3010

In this model no physical Switching Network Module (SM) is required since this
system contains only one Peripheral Module. The Switching Network and System
Clock functions are performed by the Peripheral Module Controller - Medium
extended and interConnectable (PMC-MC). The PMC-MC is described in more detail
in section 2.3.

The Central Control Module (CM) of this system consists of a single board; the Central
Processing Unit (CPU).

The iS3010 comprises a single Peripheral Module (PM), called the PM55. The PM55
is only used by the iS3010. It consists of two shelves. The upper shelf has 4 card slots

102
for peripheral circuit (PCT) boards and the lower shelf 2. Card slots 3 and 4 of the
lower shelf are for the PMC-MC and for the CPU3000 respectively. Position 5 of the
upper shelf holds the PSU.

A pair of PCT card slots forms a unit group. Every unit group has a 2Mb/s connection
to the switching network. The three unit groups are connected via the back panel to
the PMC-MC using the standard PM Bus, thus providing a maximum of 96 ports
(exclusive the optional AOC/DOC port(s) on the PMC).

This model's cabinet is a composite of a back panel, a frame of two shelves, an overall
cover and cables to connect the (optional) Emergency Battery Unit (EBU). The cabinet
can be wall mounted or, using a floor stand, free standing. Connections to the Main
Distribution Frame (MDF) are made via front connectors on the PCT boards.

Figure 2-2 iS3010 Cabinet and Shelf Layout.

103
 2.2.2. SOPHO iS3030

In this model no physical Switching System Module (SM) is required. The Switching
Network and System Clock functions are performed by the primary PMC-MC (see
section 2.3. "Peripheral Modules").

The Central Control Module (CM) of this system consists of a single board; the Central
Processing Unit (CPU).

The system contains a maximum of two Peripheral Modules (PM). The PMC-MCs of
both PMs are interconnected via six bi-directional 4 Mbit/s links, thus creating a 100%
non-blocking operation.

The iS3030 uses the PM255 locally and the RPM255 or RPM1100 remotely. It can
appear in the following configurations:

- 1 PM255;
In a single PM configuration, the iS3030 operates identically to the model iS3010
but with a larger capacity.
- 2 PM255s;
The 2 PMC-MCs are interconnected by means of 2 (shielded) front cables with a
maximum length of 10 metres. The PMC-MC in the primary PM255 (the one
containing the CPU) delivers the system clock.
- 1 PM255 plus 1 RPM (RPM1100 or RPM255);
This configuration requires a CSN-BC in slot 9 of the lower shelf (next to the CPU).
The PMC-MC is connected by 2 cables to the CSN-BC.
- 2 PM255s plus 2 RPMs (RPM1100 or RPM255).
This configuration requires a CSN-BC in slot 9 of the lower shelf (next to the CPU).
Both PMC-MCs are connected by 2 cables (each) to the CSN-BC.
An iS3030 with two RPMs has about the capacity of the SOPHO iS3050.

Each cabinet is a composite of a back panel, a frame of two shelves, an overall cover
and cables to connect the (optional) Emergency Battery Unit (EBU). The cabinets can
be wall mounted or free standing when a floor stand is used. Connections to the Main
Distribution Frame (MDF) are made via front connectors on the PCT boards.

104
Figure 2-3 iS3030 cabinet and shelf layout.

The single or primary cabinet contains 9 unit groups (UG 0...7 with two board positions
each and UG9 with one board position), two board positions for control boards (CPU,
PMC-MC) and one position for the Power Supply Unit (PSU). The transformer and the
external rectifier are located at the lower shelf. The 2 Mbit/s line for Unit Group 8 is
used to connect the CPU3000 which controls the establishing of paths between the
Unit Groups. In the secondary cabinet (if present) an additional unit group is available
(UG 8 with one board position). The shelves are controlled by the CPU in the primary
cabinet. The two PMs are interconnected fully non-blocking via 4 Mbit/s lines between
the PMC-MCs.

Unit groups 0...7 are connected to the PMC-MC via the PM Bus. Each of them
provides a maximum of 32 ports. They may be used for all kinds of peripheral boards.
Unit groups 8 and 9 provide a maximum of 30 digital ports each (two slots in the 2 Mbit/
s lines are used for communication purposes). A single cabinet iS3030 system
provides a maximum of 286 ports (exclusive the optional AOC/DOC port(s) on the
PMC). A double cabinet iS3030 system provides a maximum of (286+316=) 602 ports
(exclusive the AOC/DOC ports).

105
 Note: If an iS3030 without CSN-BC needs to be expanded to a system which does
need a CSN-BC, then take a complicated maintenance action into account.

2.2.3. SOPHO iS3050

This model contains a maximum of four Peripheral Modules, either local or remote.
When three or four PMs are needed or when a Remote PM is connected, then the
Switching Network has to be expanded with a Central Switching Network - Battery
backup and Clock regeneration (CSN-BC) board. The System Clock function is also
performed by the CSN-BC. The functions of the CSN-BC board are described in
section 2.6.3. "Switching Units - The CSN-BC".

Note: If an iS3050 without CSN-BC needs to be expanded to a system which does

need a CSN-BC, then take a complicated maintenance action into account.

The system cabinets for the iS3050 are free standing and can be placed side by side
or back to back. There are two types of cabinet, one with and one without an internal
Main Distribution Frame (see section 2.8 for more details). Connections to the Main
Distribution Frame (MDF) are made via front connectors on the PCT boards. Each
cabinet can house up to four identical PM (Peripheral Module) shelves. The top shelf
contains the primary PM. The remaining shelves are for the secondary PMs.

An iS3050 uses the PM1100 locally and the PM1100 or PM255 remotely. The
PM1100 and PM255 applied as remote PM are called RPM1100 and RPM255. Since
they have equal capacity, they are generally referred to as RPM. One RPM can be
connected to a PM.

The primary PM shelf contains 8 unit groups (UG 0...7 with two board positions each),
two board positions for control boards (CPU, PMC-MC), one position for the Switching
Network (CSN-BC) and one position for the Power Supply Unit. The CSN-BC
connects via four 4Mbit/s lines to the PMCs thus creating a fully non-blocking
Switching Network. The CSN-BC is only necessary in systems with three or four
shelves. In one or two shelf systems its position may be used as a unit group (UG 9
with one board position). In the secondary shelves two additional unit groups are
available (UG 8 and 9, both with one board position). These shelves are controlled by
the CPU in the primary shelf via the interconnection of the PMC-MCs (and, if
necessary, via the CSN-BC).

The unit groups 0...7 (analogue or digital) are connected to the PMC-MC via the PM
Bus, so each of these UGs provides a maximum of 32 ports. Unit groups 8 and 9
(digital only), with one board position each, are connected via the reduced PM Bus,
providing a maximum of 30 ports (two channels in the 2 Mbit/s lines are used for

106
communication purposes).

In a single shelf iS3050 system, therefore, the maximum number of available ports is
(8x32+1x30=) 286.

A two-shelf system offers a maximum of {(8x32+1x30)+(8x32+2x30)=} 602 ports.

A three-shelf system offers a maximum of {(8x32)+2x(8x32+2x30)=} 888 ports.

A four-shelf system offers a maximum of {(8x32)+3x(8x32+2x30)=} 1204 ports.

These figures are all exclusive the optional AOC/DOC port(s) on the PMC-MC.

The iS3050-Redundant uses the CSM with 4 CCS boards in 4/2 mode. The SM can
be configured in two ways: 1 SNS(-2T) card or 2 SNS(-2T) cards. The option with a
single SNS offers sufficient switching network capacity for this type of system but
gives no redundancy.

107
 Figure 2-4 iS3050 cabinet layout (4PMs).

108
2.2.4. SOPHO iS3070 and iS3090

In the SOPHO iS3070 and the iS3090 the Central Module (CM), the Switching
Network Module (SM) and one Peripheral Module (PM) have been combined in one
shelf, the CSM (Central Switching Module) shelf. The iS3070 and the iS3090 may
contain a maximum of 14 and 31 Peripheral Modules respectively (incl. the one of the
CSM shelf). The CPU within the CM part consists of four Central Control Slices
(CCSs) working in a 4/2-concept. See further section 2.6.2. "The CCS".

Figure 2-5 CSM shelf layout.

The Communication Interface External (CIE) board, which is part of the CM, provides
an Ethernet interface to a Backup and Interface Module (BIM). This board also
contains the Switch and Sense points. Ten switch points and 13 sense points are
available for the user. A BIM supports disk access, boot server, alarm handler
authorisation, logging of remote access and alarm functions and provides the
interfaces for a local or remote OM terminal, PCs, printers, (Multi-site)
SystemManager, CallManager etc.

The Switching Network part of this system is made from independent microprocessor
controlled parts, called 'slices', facilitating a modular growth and a high reliability. If a
slice fails, the other slices are not affected in their operation. There will just be a
reduction in traffic capacity. The Switching Network part of the SM contains the
Switching Network Slice (SNS) board: the SNS-2T for the SOPHO iS3070 and the
SNS-6T for the iS3090. With the SNS-2T boards a non-blocking time switch of 2048
paths is built and with the SNS-6T a non-blocking time switch of 6144 paths is built.
The Interface Network Card (INC) is also part of the SM. The INC adapts the interface
from the SNS into four 2 Mbit/s links all including a clock and a frame synchronisation
signal for connections to PMs with a PSC.

109
 The PM part of the CSM shelf provides eight PCT board positions, forming eight Unit
Groups (UG0 up to 7), and a position for the PMC-HR. One Unit Group in the CSM
shelf corresponds to one slot (32 channels). The structure is equal to the standard PM,
but in a standard PM each Unit Group has two slots available. Details on positioning
PCT boards in various PM shelves can be found in section 2.4.16. "Board Location
Rules".

Note that in the iS3090, in case six SNS-6T and one CIE board are used, the CIE
board takes the slot of the first Unit Group.

The following types of PMs are available:

- CSM PM (part of the CSM shelf);

- PM1100;
- RPM1100;
- RPM255;
- PM2500;
- RPM2500.

For new projects the CSM shelf and (R)PM1100 and RPM255 shelves are used. For
general information on PMs please refer to the next chapter.

The clock synchronisation of the system is provided by means of a 2 MHz clock signal.
This signal may be generated locally or is provided from an external source such as
a digital trunk interface. The clock circuit is duplicated on the two first SNS slices, the
second one is operating in hot stand-by mode. Each SNS slice contains four clock
reference inputs and can be connected to an external clock source. The operational
clock source can be selected by command.

Note: It is possible to configure an iS3070/3090 system in 'Single Slice mode'. In

such a system the CSM shelf contains one (instead of four) CCS boards (with
a Memory Extension Board). There is no processor redundancy and dual
mode is not possible.

2.3. Peripheral Modules

The Peripheral Module (PM) provides the interface between analogue and digital
telecommunication lines and the digital switching system. It can handle many kinds of
signalling systems of different line types and therefore discharges the Central Control
Module (CM) from activities that are either very time critical (such as call detection and
digit reception) or circuit dependent (such as national and local variants). This makes
it possible to place a PM 'outside' the system and to use it as a remote switching stage

110
acting as a line concentrator. The following figure shows the relevant Shelf
terminology. The PM1100 shelf is chosen as an example.

Figure 2-6 Shelf terminology.

Shelf position: the physical position of a board in the shelf.

PCT: a circuit dedicated to one line interface. Usually, a PCT board contains several
PCTs. A PCT position is a shelf position that is intended for PCT boards, but other
types of boards may be inserted in a PCT position equally well.

Unit Group: a set of PCT boards using one and the same 2Mbit/s link. A Unit Group
may consist of one, two, or four boards, depending on the type of shelf and PCT
position. PM55, PM255 and PM1100 are compact shelves, in which a UG covers two
PCT board positions.

Key code: indication of the available functionality at a particular shelf position.

There are two main functional parts within the Peripheral Module:

- The Unit Group;

- The Peripheral Module Controller.

A Peripheral Module consists of maximum 10 Unit Groups (UGs). Each UG has 32

ports (one 2 Mbit/s link) thus making the maximum number of ports: 320. They contain
the analogue and digital Peripheral Circuits (PCTs), such as analogue and digital line
circuits, analogue and digital trunk units, operator interfaces, etc. A brief description
of the various types of PCTs is given in section 2.4. "Peripheral Boards".

The Peripheral Module Controller (PMC) performs the real-time functions for the
PCTs. The line type dependent line signals are converted into messages for the CPU
and vice versa. There are two types of Peripheral Module Controller: the PMC-MC and

111
 the PMC-HR.

The PMC-MC

The Peripheral Module Controller - Medium extended and interConnectable (PMC-

MC) comprises a single time-division switching stage, used to establish digital paths
of 64 kbit/s between Unit Groups and between Unit Groups and either the Central
Switching Network (CSN-BC) or another PMC-MC. The PMC-MC is connected with
maximum eight Unit Groups (UG 0...7) to the Switching Network. Two more Unit
Groups (UGs 8 and 9) may be connected without the control data. The control data
(selection and timing signals) are used to select the PCTs and to synchronise them
with the other system parts. Communication with the PCTs connected to UGs 8 and
9 is via a communication channel in the user information line using the IMP protocol.
Thirty channels are available in this line for user data. The PMC-MC consists of the
following functional items:

1. A non-blocking time switch.

2. Receiver Keytone/Receiver Dial Tone (RKT/RDT) Circuits.
These circuits detect key tone signals (representing dialled digits) and dial tones
during call setup.
3. The Add-on Circuit.
Up to 10 add-on calls can be created at the PMC, enabling 3-party conference
calls on extensions. During add-on, a call ticker tone can be inserted. The add-on
circuits of all PMC boards are used systemwide (so not only in the PM where the
PMC is housed).
4. The Tone Generator.
This device is capable of generating 32 different (programmable) tones. The last
16 tones are reserved for DTMF signals according to CCITT recommendation
Q.23.
5. The clock circuit.
The system clock is generated on the PMC board. The source (synchronisation)
may be derived from the PMC-board (internally, stand-alone) or from an external
synchronisation. The source on the board is a 16.384 MHz VCO (Voltage
Controlled Oscillator). This clock generation circuit may operate in two modes:
- Master mode: The clock generates an internal 2.048 MHz clock signal
autonomously or synchronises to an external 2MHz clock signal.
- Slave mode. Either the clock generates an internal 2.048 MHz clock signal
(derived from the 16.384MHz VCO) or it synchronises to an external 2.048
MHz clock, derived from a master PMC-MC via a Network Interconnection
(NIC).
6. Analogue Operator Circuit (AOC) and Digital Operator Circuit (DOC).

112
 The AOC card can connect two analogue operator desks. The DOC connects one
digital operator desk.

The PMC-HR

The Peripheral Module Controller - High Range (PMC-HR) is almost identical to the
PMC-MC but it provides another interface to the switching network. The Clock Circuit
is not available on the PMC-HR.

The following table shows which and how many (Remote) Peripheral Modules the
ISPBX models use:

iS3010 iS3030 iS3050 iS3050 iS3070 iS3090

redundant redundan
t or
standard
Local PM PM55 PM255 PM1100 PM1100 + PM1100+ PM1100+
CSM CSM CSM
PMC PMC-MC PMC-MC PMC-MC PMC-MC PMC-HR PMC-HR
Max. 1 2 4 4 16 31
number of
PMs
Max. 0 1 4 4 15 15
number of
RPMs
Max. 1 2 1 1 4 8
number of
cabinets

Table 2-1 Overview of the use of peripheral modules.

The individual CCS system in a network is called a "unit" or a "node". A network can
have up to 14 units.

CSM PM

A CSM Peripheral Module (part of a CSM shelf) provides the interface between up to
256 telecommunication lines and the iS3070/3090 system. The maximum number of
telecommunication lines depends on whether they are analogue or digital and the

113
 number of board positions which are occupied by Communication Interface External
(CIE) or Interface Network Card (INC) boards.

PM1100

A PM1100 provides the interface between up to 320 telecommunication lines and the
ISPBX. The maximum number of telecommunication lines depends on whether they
are analogue or digital. The PM1100 is a shelf for a floor standing cabinet. It has 20
card slots:

- 1...16 for PCT cards (UG0...7);

- 17 for the PMC;
A PMC-HR for a CCS system and a PMC-MC for a CPU3000 system.
- 18 either for the CPU3000 or for a PCT-CI card (UG8);
- 19 for a PCT-CI* card (UG9);
- 20 for a Power Supply Unit (PSU-ML or -MLD).

PM255

The PM255 is a cabinet with 2 shelves. It has 20 card slots:

- 1..10, upper shelf and 1...6, lower shelf for PCT cards (UG0...7);
- 7, lower shelf for the PMC-MC;
- 8, lower shelf either for the CPU3000 or for a PCT-CI card (UG8);
- 9, lower shelf for a PCT-CI* card (UG9);
- 10, upper shelf for a Power Supply Unit (PSU-ML or -MLD).

*) A PCT-CI card sends and receives Internal Message Protocol (IMP) messages
through user time slot 0. PCT-CI stands for PCT cards which Communicate by means
of IMP.

The PM255 and the PM1100 have equal capacity; they offer the same number of
ports.

PM55

A PM55 consists of two shelves. The upper shelf has four card slots for peripheral
circuit (PCT) boards and the lower shelf two. Card slots three and four of the lower
shelf are for the PMC-MC and for the CPU3000 respectively. Position 5 of the upper
shelf holds the PSU.

PM2500

114
A PM2500 (local or remote), provides the interface between up to 128 analogue or
digital telecommunication lines and the ISPBX.

The Remote Peripheral Module (RPM)

The iS3000 series offer the possibility to place PMs at a remote location, thus
providing a remote switching stage to act as a line concentrator. Two types of Remote
Peripheral Modules (RPMs) are available:

- RPM255; an RPM with the Unit Groups divided over two shelves i.e. an iS3030
shelf.
An RPM255 provides the interface between up to 256 telecommunication lines
and the ISPBX. The maximum number of telecommunication lines depends on
whether they are analogue or digital and the number of links between the RPM255
and the local system.
- RPM1100; a one-shelf RPM, identical to a standard PM.
An RPM1100 provides the interface between up to 256 telecommunication lines
and the ISPBX. The maximum number of telecommunication lines depends on
whether they are analogue or digital and the number of links between the
RPM1100 and the local system. The RPM1100 shelf provides board positions for
18 PCT boards.

The RPMs have the same layout as the standard PMs. The RPMs are connected
to the Switching Network Module using transmission equipment (the Digital Trunk
Unit and optionally the Line Terminating Unit) located in Unit Groups of both the
remote PM and the local PM. Depending on the amount of traffic, one or more
connections with the RPM can be made. The following figure shows an example
with two connections.

Figure 2-7 Connections to the remote peripheral module.

Each link is a standard Primary Rate link (G.703 compatible). The Remote Peripheral
Module is synchronised with the parent system parts by a clock reference, derived
from the incoming 2 Mbit/s line.

115
 2.4. Peripheral Boards

A wide variety of plug-in boards are available to interface an iS3000 system with all
major types of analogue or digital extensions, business phones, public trunks, private
tie-lines, cordless handsets, integrated announcers, paging equipment, operator
consoles, voice processing systems, front-end office equipment, door openers and
conference units.

Boards that can be used to connect peripheral equipment: ALC, DTX-I, DLX-U, DLX-
L.

Boards that can be used to connect operator consoles: AOC, DOC, DTX-I, DLX-U,
DLX-L, DLC-U.

Boards that can be used to connect to the public network: ATU, DTU-PH, DTX-I, DTU-
PU.

Boards that can be used to connect to the private network: ATU, DTU-PH/PU, DTU-
VC.

Special peripheral boards: CFC, ATU-PA, IAS, DCC.

A transmission plan specifies the transmission (send and receive) levels and
impedance values used in a country. The transmission plan of a country is identified
by a code. This code is included in the name of the board (if applicable). All cards in
an ISPBX should have the same transmission plan. A mix of different plans will lead
to wrong signal levels or even to serious distortion.

All modern cards like ALC-G, DCC, DLX-U, DLX-L, CIE and CPU3000 have their 12nc
programmed on board. Also the SB number identification is available. This is the
production serial number. The SB number relates to the test document in the IPSC.
This document contains the history of a product, what was the production date, how
often is has been repaired etc. The document itself is not on board but once the
number is known, the document can be looked-up at the IPSC. Via (remote)
Operational Maintenance it is possible to get a complete listing of the contents of a
system. What cards and what software levels are present at a customers premises
can determine how a problem can be solved, what spare parts should be taken to the
customer etc.

2.4.1. Analogue Line Circuit

An Analogue 2-wire Line Circuit (ALC) for standard telephone sets. It converts the
analogue user information into digital samples (using Pulse Code Modulation) and

116
vice versa. The resulting full duplex 64 kbit/s channel is multiplexed on the 2 Mbit/s
user information line, which connects the Unit Group to the PMC. The line signals,
which are detected and sent by the ALC, are sent to or received from the PMC using
the 2 Mbit/s control data line.

2.4.2. Analogue Trunk Unit

An Analogue Trunk Unit (ATU) provides the interface between a number of analogue
trunk lines, connected to either a public exchange (exchange line) or another PABX
(tie line), and the digital switching system. It converts the analogue user information
into 64 kbit/s digital information, which is multiplexed on the 2 Mbit/s user information
line connected to the PMC. The ATU detects (and sends) the line type dependent line
signals, which cause messages to (or are caused by commands from) the PMC using
the 2 Mbit/s control data line. Different types of ATUs provide for different types of
signalling.

- Analogue Trunk Unit - Private Attachment (ATU-PA)

An ATU-PA is used to connect paging equipment to the digital switching system,
according to European Selective Paging manufacturers Association (ESPA)
specifications ESPA 4.4.4. This type of ATU is not a trunk unit as such, but is so
called because it is controlled as an ATU.
- Analogue Trunk Unit - Private Switching Interface (ATU-PSI)
An ATU-PSI is used for the connection of an intercom and door opener or for the
connection of a Common Answering Emergency Service. This type of ATU is not
a trunk unit as such, but is so called because it is controlled as an ATU.
- Analogue Trunk Unit - General (ATU-G)
An ATU-G can replace a number of ATUs with signalling types ALS70/EO and SS.
Additionally the ATU-G provides the metering and emergency switch-over
functions. The following table shows the boards that can be replaced by the ATU-
G.

ATU-ALS70/EO ATU-SS MC(E)

ATU-AS24 ATU-SS04 MC-D
ATU-AS0B ATU-SS0A MC-F
ATU-SS0B

Table 2-2 Boards Replaced by ATU-G.

117
 2.4.3. Digital Trunk and eXtension Interface - ISDN

The Digital Trunk and Extension Interface - ISDN (DTX-I) is a multi-functional board.
It provides interfaces for 7 or 15 Basic Rate ISDN trunk lines and/or extensions
conform the ITU-I.430 recommendation. These interfaces are four wires. The
extension interfaces are called S0-busses.

Each circuit on the DTX-I can be configured as:

- an extension for the Euro-ISDN, 1TR6 or propriety protocol;

- an interface to a digital operator position;
- a trunk for Euro-ISDN or 1TR6 protocol;
- a tie line for the QSIG, DPNSS or 1TR6 protocol;
- a CTI (Computer Telephony Integration) Interface according to ECMA (CSTA).

It is possible to use a mixture of different protocol types on the same DTX-I card. For
each port on the board, a maximum power of 4 W is available to supply to one or more
extensions when configured as extension or operator interface.

2.4.4. Digital Line eXtension - UPN Interface

The Digital Line eXtension - UPN Interface (DLX-U) offers 2 wire digital extension
interfaces for the ErgoLine D310-2, D320-2, D330-2 and D340-2.

The card's main characteristics:

- 2-wire cabling;
- 2B+D protocol (in 1B mode the second B-channel is disabled);
- line powering up to 4 W;
- typical distance 1000 m. / max. distance 1800 m;
- not compatible with the boards DLC-U/A/B/C/D/I.

There are two versions of the DLX-U:

- DLX-U15; the DLX-U mother board providing 15 circuits.

- DLX-U31; the DLX-U mother board in combination with a daughter board
providing 31 circuits.

The board can work in two modes:

- 1B mode; one 1B+D type of interface for each line. The second B-channel is
switched out by blocking its access to the system's backpanel.
- 2B mode; both B-channels available for each line.

118
Which mode the board applies is projected with OM command ASBRDS.

The supported combinations are:

1. DLX-U15 in 1B mode; 15 accesses with a 2B+D Upn interface of which only 1 B-

channel is applied.
2. DLX-U15 in 2B mode: 15 accesses with a 2B+D Upn interface applying both B-
channels.
3. DLX-U31 in 1B mode: 30 accesses with 1B+D Upn interface that apply 1 B-
channel.

The combination DLX-U31 in 2B mode is not possible. It would work as DLX-U15 in

2B mode with the additional circuits on the daughter board not used. A mix of lines in
1B and 2B mode is not possible.

2.4.5. Digital Line eXtension for Long lines and PNT-L

The Digital Line eXtension for Long lines (DLX-L) offers a long line digital interface
(2B+D) based on 2 wires. With a Private Network Terminator for Long lines (PNT-L)
this 2 wire interface is converted into a 4 wire S0 interface. The DLX-L is based on the
standard ISDN 2B1Q echo cancelling Uk0 interface. This gives the freedom to
connect 'any' terminal to the DLX-L.

The DLX-L has 15 line circuits per board. They can operate in 2B or in 1B mode. See
the description of the DLX-U. Normally the DLX-L will be used in the 2B mode. This
gives the same usage as the 1B mode, but with more flexibility for the user. The costs
are however lower because the PNT-L is shared by two terminals. The benefit of using
the 1B mode is that the second position in the Unit Group can be used for any other
board that occupies only half a Unit Group. These are boards like the ALC-G, DLX-
U15 (in 1B mode).

The major benefit of the DLX-L is of course the line length. The following lengths are
applicable:

119
 Cable diameter Max Cable length to DLX-L Max Cable length with
with normal cable shielded ground cable
0.4 mm 3500 m -
0.5 mm 5500 m 7000 m
0.6 mm - 8000 m
0.8 mm - 15000 m

Table 2-3 DLX-L cable lengths.

The PNT-L offers three possible configurations:

- Short Passive Bus (default and most used);

- Extended Passive Bus;
- Point to Point.

The following figure gives these three options and the length of the S0 bus using a
0.6mm cable given by the supplier of the PNT-L. This figure should be used as an
indication what is possible. A safe length is 600 meters for point to point and extended
passive bus. The selection of the configuration required is done using DIP-switches
on the PNT-L.

Figure 2-8 S0 cable length.

120
The total distance from a terminal towards the ISPBX can be 4325 meters when using
0.4 mm cabling and an extended passive bus behind the PNT-L with 0.6mm cabling.
The PNT-L can be wall mounted or used as a loose box. The PNT-L needs external
mains powering. It is suited for 90 to 264 Volts powering, so it can be used in countries
with 110 Volts and 230 Volts. Up to 4 terminals can be connected to the PNT-L without
the need for external mains powering on the terminals. They are powered from the
PNT-L. Only if DSS or V24 modules are used on the ErgoLine 340 terminal, the need
for external power exists.

2.4.6. Digital Trunk Unit - Protocol Handler

The Digital Trunk Unit - Protocol Handler (DTU-PH) provides the interface for primary
rate connections (30B+D) using common channel signalling protocols. It supports a
wide range of protocols:

- DSS1, 1TR6, DASS2, VN4 for trunk lines.

- DPNSS, QSIG, 1TR6 for tie lines.

The DTU-PH converts the protocol into the Internal Message Protocol (IMP) and vice
versa. The interfaces comply with I.431, G.703 and G.704. The DTU-PH is connected
to a 2 Mbit/s PMC line carrying 30 user channels of 64 kbit/s each and the frame and
signalling signals. The DTU-PH carries a DIP switch block and straps. A present clock
signal may be used to synchronise the system clock.

2.4.7. Digital Trunk Unit - Primary Rate Universal

The Digital Trunk Unit - Primary Rate Universal (DTU-PU) is a board that can be used
to perform the two functions mentioned hereafter. The selection of the functionality
required is done using straps. The interface complies with I.431, G.703 and G.704.

- Channel Associated Signalling functionality.

In this mode the DTU-PU provides the interface between a standard primary rate
link and the ISPBX. This 2 Mbit/s line is carrying 30 user channels of 64 kbit/s each
and frame and signalling information. A wide range of signalling protocols is
supported.
- Common Channel Signalling functionality.
In this mode the DTU-PU provides the interface between the ISPBX and a 2 Mbit/
s PCM line connected to another unit (in a network of iS3070/iS3090 units) or an
RPM. This 2 Mbit/s line is carrying 30 user channels of 64 kbit/s each plus the
frame and proprietary signalling information.

121
 2.4.8. Digital Trunk Unit - Voice Compression

The DTU-VC provides low-cost iSNet Private Networking over three 64 kbit/s digital
lines. Over one 64kbit/s line three compressed voice channels can be sent including
framing and networking signalling. Three compressed voice channels with signalling
may be sent via a loopback channel as one 64 kb/s channel. The compression
technique used is according to G.728.

With a TRunK board - Voice Compressed (TRK-VC) board, the interface between the
DTU-VC and up to three 64 kbit/s tie lines may be made to a DTU-VC/TRK-VC
combination on the remote side thus providing up to nine voice channels with
signalling to be transferred. The TRK-VC is a plug-on card that can be fitted on the
DTU-VC.

Because the voice compression takes place in the switch, this way the capacity of
inter-network tie-lines could be increased.

2.4.9. Line Terminating Unit

A Line Terminating Unit (LTU) is required if the distance between two DTUs exceeds
300 meters (typical). The characteristics of the line interface are conform G.703. The
LTU has extensive supervisory devices:

- Error processing and detection;

- Clock regeneration;
- Alarm signalling;
- In case of alarm: output loop switch control.

Two types of LTU are available:

- LTU-C (C = Copper).
The maximum loss allowed between two LTU-Cs is 40 dB. This means when a
cable is used of two 0,8 mm2 wire pairs, the maximum cable length becomes 2500
meters with a loss of 5 to 10 dB in the MDF.
- LTU-F (F = Fiber).
The maximum allowed loss between two LTU-Fs is 24 dB. If a fiber cable is used
with a loss factor of 0,5 dB/km, the maximum distance is 48 km.

2.4.10. DECT Cluster Controller

A DECT Cluster Controller (DCC) provides the ISPBX with cordless telephony. A DCC
can have up to four radio fixed parts and has 30 channels and allows therefore for 30

122
simultaneous conversations. It is possible to subscribe 510 handsets to one DCC,
which is useful in a network environment. Note that the number of communication
channels is still 30.

Advise on the maximum number of subscriptions per DCC: 30 in a stand-alone system

and 100 in an ISPBX of a private network.

2.4.11. Music On Hold Interface

The Music On Hold Interface (MOH-I) is a circuit connecting a music source (such as
a radio or continuous tape player) to an Analogue Line Circuit. If the music source
fails, a fault is reported to the PMC. It is also possible to use the Integrated
Announcement Server (IAS) board for Music On Hold. The Compatibility Value (CV)
of the party that initiates the on hold situation, determines the MOH to be given. The
CV mechanism (often in combination with different Analysis groups and Assistance
groups) is used to share one ISPBX system by different companies. Using the CV -
MOH relation, enables different companies to give their 'own' Music On Hold.

In case a party that dials the operator A-Queue is put on hold, then the MOH resource
corresponding to this operator A-Queue will be used. There is a relation between the
dialled number leading to the operator A-Queue and the CV. If this CV is not present,
then CV of the trunk is used.

2.4.12. Analogue Combination Card

An Analogue Combination Card (ACC) contains 8 Analogue Line Circuits for the
connection of extensions and two positions for a Peripheral circuit Extension Board
(PEB). The PEB can be any of a series of Trunk Units (TUs) containing up to 4 trunk
line circuits. Some types of TU provide the trunk lines with metering circuits and/or
emergency switch-over circuits.

- TU-SS (subscriber signalling); 2 circuits

- TU-AS (ALS70 signalling); giving 2 circuits

2.4.13. Analogue Operator Circuit

The Analogue Operator Circuit (AOC) provides the interface between two analogue
Operator Positions and the digital switching system. An analogue speech path and a
digital data connection are available for each interface. The AOC is an optional card
mounted on the Peripheral Module Controller (PMC).

123
 2.4.14. Conference Circuit

A Conference Circuit (CFC) allows up to eight parties to talk together. The parties may
be internal or external. A tone generator on the CFC can inject a tone into the
conference call to inform existing participants of the addition of a new participant. A
CFC is connected to the PM Bus, from which it receives the incoming eight user
channels. The eight incoming user channels are added together and sent back in all
the outgoing user channels.

When more than 8 parties are desired, more CFC boards can be used. The boards
can be interconnected in a star network via the switching network. Connecting the
boards in series is also possible, but not advisable because of delays and signal
attenuation. In order to automatically connect the CFCs to each other, hotline relations
must be configured from the central CFC board to the other CFC boards.

If for example 3 CFC boards are used, a conference call can be set up with a
maximum of 19 parties. The central CFC board uses circuit 0 for the conference group
supervisor and circuits 1 and 2 are used to connect to the other 2 CFC boards. The
other 2 boards use one circuit to connect to the central CFC boards.

See also section 2.4.15. "Integrated Announcement Server".

2.4.15. Integrated Announcement Server

An Integrated Announcement Server (IAS) can store up to 255 voice announcements

and play them back to internal or external callers. The server can also be used to
provide music-on-hold and a dynamic delay announcement (this tells the caller how
many calls are waiting in the queue) or other announcements in Automatic Call
Distribution (ACD) groups.

30 different messages can be played back simultaneously. Voice announcements are

recorded using a normal telephone set, under control of the 'IAS Management' PC
application. The total duration of announcements stored in the IAS depends on
whether extra memory boards are fitted; if no extra memory is fitted then 31 seconds
of speech can be stored. Up to 4 extra memory boards can be fitted, giving an extra
25 minutes of storage time. For more information see section the System and
Application Manual - VoiceManagers.

2.4.16. Board Location Rules

Boards can not be installed in any card slot of a Peripheral Module (PM). The following
table shows the card slot location rules for the (R)PM1100 and (R)PM255. The unit

124
groups (02) of the PM55 stick to the same rules as unit groups 07 of the PM255/1100.
The card slots of the Control & Switching Module (CSM) shelf can handle any type
board. With the exception of the DTU-PU and IAS(A) boards which can not be placed
in position 18.

125
 BOARD UG 07 UG 8&9 REMARKS
Position Position
1 2
ACC x x - ALC-E/F or ATU-G to be
used
ALC-E/F + + -
AOC - - - Daughter board of the
PMC
ATUs + + -
CFC + + -
24-DCC 1) - - Consult the iSMobile CE
manual for constraints
32-DCC + - - Consult the iSMobile CE
manual for constraints
DLC-I x x - DTX-I (7) to be used
DLC-U It is advised to use the 15
+ o + lines version
15 lines
+ x +
7 lines
DLX-U It is advised to use the 15
+ o + lines version
15 lines (each line is
2B+D) + o +

31 lines (each line is + x +

1B+D)

7 lines (each line is

2B+D)

126
BOARD UG 07 UG 8&9 REMARKS
Position Position
1 2
DLX-L
+ o +
15 lines (each line is
2B+D) + + +

15 lines (each line is

1B+D)
DOC - - - Daughter board of the
PMC
DTU-PH + o +
DTU-PR x o - DTU-PH to be used
DTU-PU (version 1)
x o - DTU-PU (version 2) to be
as - CA used
- - -
as - CC DTU-PU (version 2) to be
x o - used
as - PR (+IPH)
DTU-PH to be used
DTU-PU (version 2)
+ o -
as - CA
- - + Only possible in UG 0...6
as - CC
o + - Only possible in UG 4...7
as local DTU-CC
+ o - DTU-PH to be used
as remote DTU-CC
x o -
as - PR (+IPH)
DTU-VC + x - DTU-VC occupies 1,5 UG
because of power
consumption

127
 BOARD UG 07 UG 8&9 REMARKS
Position Position
1 2
DTX-I It is advised to use the 15
+ o + lines
15 lines
+ x +
7 lines
ESU(-LG) + + -
IAS
+ - x
15 lines
+ o +
30 lines
LTU-FC + + + Power supply use only
MC + + + Power supply use only
MCE + + -

Table 2-4 Board location rules.

1) = See the iSMobile CE manual;

+ = possible position;

x = possible but not, likely to be used;

- = not possible;

o = board position used by PCTs on the first board in that unit group; possible
for boards with power supply use only.

2.5. Input/Output

2.5.1. General

Systems with the CPU3000 processor boards (SOPHO iS3010/3030/3050) provide

128
the following interfaces:

- Six V.24 ports to connect external management and maintenance applications;

- A V.28 port for signalling alarms.

In systems with CSM shelves (SOPHO iS3070 and iS3090), a Backup and Interface
Module (BIM) is used to communicate with the external world. The BIM is connected
to the processors (CCS) via the Communication Interface External (CIE(-2)). This
board has a high speed (10 Mbit/s) interface with the BIM. The BIM 1.6 contains a 270
Mbytes hard-disk for system backup. The BIM 2.0 is a Windows NT based PC. The
connection of the BIM 2.0 towards the CIE will be 10BaseT Ethernet using TCP/IP.

The BIM may connect 6 up to 26 V.24 external devices, such as:

- a (remote) SysManager;
- a (remote) SOPHO SystemManager (SSM) CallManager;
- a (remote) maintenance terminal;
- a call logging device;
- a remote service centre;
- a CallManager ACD terminal;
- a printer.

Miscellaneous interfaces:

129
 FUNCTION LOCATION OF INTERFACE
CPU3000 CCS SYSTEM
Sensor points for external alarm unit* CIE(-2)*
alarms
Night bell alarm unit CIE(-2)
Alarm box alarm unit CIE(-2)
iSLink DTX-I, DLC-U + PNT1 DTX-I, DLC-U + PNT1
SysManager CPU3000 BIM
SystemManager CPU3000 BIM
Serial printer CPU3000 BIM
SSM Maintenance PC (SSM - -
MPC)
SysManager Maintenance PC CPU3000 CIE(-2)
(SMPC)

Table 2-5 System interfaces.

*) If in a remote PM, this interface is offered by an ATU-EM.

2.5.2. CSTA Ethernet

• CSTA Ethernet for CCS systems

The BIM is equipped with a second Ethernet card that leads to an Electronic Data
Processor (EDP) running a CSTA application. The following figure shows that the
BIM is in between the ISPBX and the EDP acting as an IP router. The hub must
be in between the BIM and the EDP if it concerns a local connection. If both are
connected via the company LAN then the hub function is already included in the
LAN.
The CSTA Ethernet connection of a CCS system has a capacity of 200 CSTA
messages per second (compared with the 15 messages per second for the ISDN
S0-bus connection).
A BIM 1.6. (UNIXWARE) can not combine an Ethernet CSTA link with a tape
backup utility, due to a lack of ISA slots in the BIM PC).

130
Figure 2-9 CSTA over Ethernet for CCS systems.

• CSTA Ethernet for CPU3000 systems

The EDP is connected to the Ethernet connector of the CPU3000. The hub must
be in between the CPU3000 and the EDP if it concerns a local connection. If both
are connected via the company LAN then the hub function is already included in
the LAN.

Figure 2-10 CSTA over Ethernet for CPU3000 systems.

• Boundaries and Restrictions

A distributed ISPBX (multi-unit system) is basically transparent for CSTA.
However, due to the restricted capacity of the inter unit link, an EDP should only
monitor and manipulate extensions of the local unit.

2.6. Technology

2.6.1. The CPU3000

The CPU3000 is used in the SOPHO iS3010, iS3030 and the iS3050 and has the
following characteristics:

131
 - MC68MH360 (+ MC68040 when an AM3000 is added);
- 10Base T Ethernet connection;
- 6 device ports offered by the VIC3000;
- The following functions require an alarm unit to be connected to one of the device
ports of VIC3000:
- Visual and audible alarm indicators;
- Interface for an alarm box;
This interface offers alarm contacts, sense input for alarm buzzer reset and
sense input for testing the emergency bypass function.
- Two sense inputs for alarms;
A sense input connected to an external device causes an ISPBX alarm to be
generated at malfunctioning of this device. Example: external rectifier.
- Interface for a night bell. Please refer to the section about Common Answering
Night Service (CANS).

Details of the alarm unit can be found in the installation manual of the CPU3000
related systems.

ISPBXs equipped with a CPU3000 comply with the CM, SM and PM structure (like the
CCS systems).

The CPU3000 is the successor of the CPU-MT and CPU-ME. It offers more power to
the smaller SOPHO iS3010, iS3030 and iS3050 and a number of additional facilities.
The main differences between the CPU3000 and the CPU-MT are:

- Better performance, especially with the Accelerator Module 3000 (AM3000).

- Ethernet connector for CSTA and file transfer.
- On-board file storage for e.g. toll ticketing files, batch files etc.
- Maintenance Mode operation (see section 1.7.9. "Maintenance Mode - CPU3000
Platform only").

Options for CPU3000:

1. AM3000;
The Accelerator Module 3000 offers the possibility to increase the performance of
the CPU3000. Now each model of the SOPHO iS3000 range can have all the
power available when needed. Heavy CTI applications or CallCentres can now
also be handled by the smaller iS3000 models.
2. 8 & 16 MB Flash Disk;
To increase the Flash Disk capacity extra memory modules can be added, offering
8 or 16 Mbyte per card. Per CPU3000 two of these cards can be installed. The
extra Flash disk capacity can be used e.g. for extra toll ticket storage or supporting

132
 larger future software packages. The Flash Disk is non-volatile; meaning that in
power off situations the contents of the disk is saved.
3. 16 & 32 MB DRAM.
As with the Flash Disk also the DRAM can be expanded. Two variants are
available; a 16 and a 32 Mbyte module. In the DRAM the software package is
active and the configuration of the system is stored. DRAM is volatile, meaning
that if the power is down the contents will be lost.

2.6.2. The CCS

The CCS (Central Control Slice) boards, used in the CSM shelves of the iS3070/
iS3090, provide the processor/memory complex to operate the system software and
to store the user data. Four CCS boards operate in parallel according to the 4/2
concept. The default memory size is 16 Mbytes. It may be extended by means of a
plug-in card to 32 Mbytes. Also call processing power has become a crucial factor in
ISPBX environments, not in the least because of the many, processor time
consuming, applications. The processor boards contain Motorola's 32 bits MC68040
microprocessor which operates at a speed of 66 MHz.

The 4/2 concept

The 4/2 concept uses the four parallel processors and a duplicated memory. The
duplicated memory is divided in four slices across the four processors. The four
processors execute the same instructions which are continuously checked by an error
recovery mechanism which is implemented in the hardware. A single or a double bit
fault and even a fault that affects an entire instruction is detected and recovered
without discontinuity. This constant process of verification ensures that a memory
fault, a processor fault or even a breakdown of an entire CCS may be ruled out. These
events are without interruptions in system operation. The System Assurance System
(SAS) checks regularly the operation of the four processor slices and generates an
alarm when a failure occurs in one of the slices. A faulty slice can be replaced by a
system engineer by simply pulling the board and inserting a new one. Then the new
CCS has to be put into service and, after a synchronisation process of about two
minutes, it becomes operational. Another important feature is the dual mode concept.
Now, extensive maintenance actions are possible while the system continues on-line
operations. In normal mode, four processors work in parallel. In dual mode, two
processors may be used for the on-line software (the 'operational' program). The
remaining two processors can then be used for maintenance purposes ('Standby') e.g.
for loading a new release. It should be noted however, that in this mode no
redundancy is available. See also 2.6.3. "Switching Units - The CSN-BC".

133
 2.6.3. Switching Units - The CSN-BC

In the iS3030 and iS3050, the Central Switching Network - Battery backup and Clock
regeneration (CSN-BC) board provides the following functions:

- Non-blocking Switching Network;

- Battery voltage alarms;
- Clock (re)generation.

The non-blocking Switching Network is able to switch 1536 incoming 64 kbit/s

channels to 1536 outgoing channels. The CSN-BC is needed when three or four PMs
have to be interconnected. It is also possible to apply the CSN-BC in a system with
one or two PMs, but this is not very usual. The only reason is to have a battery voltage
check function. The CSN-BC monitors the voltage of the Emergency Battery Unit
(EBU). The EBU supplies the CPU card memory with power during power down
situations. If there are problems with the EBU voltage, the CSN-BC generates an
alarm signal to the CPU card. The Clock circuit of the CSN-BC generates the 2 MHz
clock and 8 kHz frame synchronisation signal for the entire system. This circuit can be
synchronised by an external clock signal (e.g. from a Digital Trunk Unit). For this
purpose two coaxial front connectors are present.

2.7. Power Supply

The average power consumption per line is estimated on 1,4 Watt.

• Power Supply Units

The system cabinets receive power from Power Supply Units (PSU). Every PM
has a (separate) PSU installed in a fixed location in the shelf. There are 3 types of
Power Supply Units (PSU):
- PSU - Small (PSU-S);
The PSU-S can handle an AC input voltage directly from a transformer. It is
applied in the iS3010 only.
- PSU - Medium Large (PSU-ML);
This PSU requires a DC input voltage. A ripple on this input voltage is no
problem. It is typically used in combination with a transformer/bridge rectifier.
- PSU - Medium Large for DC power (PSU-MLD).
This PSU needs a stable 48V DC input voltage. It can be applied in
combination with an external rectifier.
For transmission plan 2 countries there are special versions of the PSU types.
These PSUs can be strapped for 75Vac or 60Vac ringing voltage and 25Hz or
50Hz ringing frequency. Another difference is that these PSUs offer -60Vdc
signalling voltage (needed for the ATU-ST02, ATU-ST12 or an ATU-ST26).

134
• System Power Modules
There is a complete range of System Power Models (SPM), rectifier models, for
the SOPHO iS3000 Series.
- SPM0;
The SPM0 is an integrated no break rectifier specially designed for the iS3010,
iS3030 and iS3050 to meet the "Correct Power" and safety declarations of the
European Union. This specifies the maximum allowed mains pollution caused
by non-sinus shape current. The SPM0 can only operate in conjunction with
the PSU-ML. It does not support the PSU-S or the PSU-MLD. The SPM0 offers
a "Correct" Power Factor of 0,95 and also a "No Break" facility. The correct
power function assures that the current, which is derived from the mains, is in
phase with the voltage and has approximately the same wave form as the
voltage. The "No Break" facility supports a standby battery capacity of 25Ah
(Single Autonomy) or 50Ah (Double Autonomy). This requires an additional
iS3010 Battery Cabinet with one or two 25Ah battery sets and corresponding
cables per iS3010 or iS3030 system configuration. The "No Break" option is
only recommended for customers with a low frequency of mains fails and offers
only a battery recharge current of 0.5 Amps maximum. Both functions are
implemented on one board: the UpDate Unit (UDU). This unit is a part of the
No Break Rectifier (NBR). The NBR is placed in the power compartment of the
cabinet. The NBR is the successor of the rectifier. For the No Break power
option, an additional cabinet is required containing batteries. This cabinet looks
like an iS3010 cabinet, but the weight of the cabinet is much higher due to the
batteries. It can be mounted to the wall or it can be placed on the floor, with the
use of a floor stand. All iS3010 and iS3030 system configurations are standard
equipped with the SPM0. The SPM7 can also be applied but is more suited for
areas with a high mains power failure rate, because it reloads the batteries
faster then the SPM0. The SPM0 on the other hand is cheaper.
- SPM1;
The SPM1 is an integrated no break rectifier solution specially designed for the
Remote Peripheral Module of the iS3070/iS3090. The SPM1 can also be used
for the iS3050. The SPM1 can be extended in the same iS3000 cabinet with a
maximum backup capacity of 74Ah.
- SPM2;
The SPM2 is an iS3000 integrated no break rectifier solution specially
designed for small iS3070/iS3090 system configurations. The SPM2 can also
be used for large iS3050 system configurations. The SPM2 is fully integrated
as part of the system configuration but requires an additional iS3000 cabinet.
The SPM2 supports two rectifier modules of 30A each. The SPM2 can be
extended with a maximum backup capacity of 196Ah (per SPM2
configuration).

135
 - SPM3;
The SPM3 is an iS3000 integrated no break rectifier solution specially
designed for large iS3070/iS3090 system configurations. The SPM3 supports
up to three rectifiers modules of 30A each. The SPM3 is fully integrated as part
of the total system configuration but requires an additional iS3000 cabinet. The
SPM3 can be extended with an additional iS3000 battery cabinet with a
maximum backup capacity of 508Ah (per SPM3 configuration). The SPM3 can
be supplied in parallel mode for large iS3090 system configurations.
- SPM4;
The SPM4 is a "Plug and Play" no break rectifier solution. The SPM4 can only
be used for iS3010 and iS3030 configurations. It is specially designed for
customers and/or countries with a high frequency of main failure. The SPM4
supports two rectifier modules of 7.5A each. The SPM4 is supplied as an
external stand alone back-up solution. The SPM4 can be extended in the same
power system cabinet with a maximum back-up capacity of 25Ah, 37Ah or
49Ah (per SPM4 configuration). It is allowed to switch the SPM4 in parallel
mode. The SPM4 replaces the SPM0 in case of high-speed recharge capacity
is required with a maximum of 3 Ampere. Note that the SPM0 is an optional
integrated no break rectifier solution and the SPM4 is an external no break
rectifier solution for the iS3010 and iS3030. The SPM4 is technically not
compatible with the SPM0!
- SPM5;
The SPM5 is a "Plug and Play" external no break rectifier solution. The SPM5
can be used for large iS3050 and for small iS3070/iS3090 system
configurations. The SPM5 supports two rectifier modules of 33A each. The
SPM5 is supplied as an external stand alone rectifier solution. The SPM5 can
be extended with an additional battery cabinet with a maximum backup
capacity of 98Ah (per SPM5 configuration). The SPM5 can be switched in
parallel mode.
- SPM6;
The SPM6 is a "Plug and Play" external no break rectifier solution. The SPM6
can be used for large iS3070/iS3090 system configurations. The SPM6
supports up to four rectifier modules of 33A each. The SPM6 is supplied as an
external stand alone rectifier solution. The SPM6 can be extended with an
additional battery cabinet of Benning with a maximum capacity of 98Ah or with
an additional iS3000 battery cabinet with a maximum backup capacity of 508
Ah (per SPM6 configuration). The SPM6 can be supplied in parallel mode for
large iS3090 system configurations.
- SPM7.
The SPM7 is a "Plug and Play" cost effective (integrated or stand alone)
rectifier solution for the iS3010/iS3030 and the iS3050. The SPM7 is supplied

136
 in two cost effective configurations:
1. as a table top stand alone external rectifier solution without sophisticated
battery backup facilities for the iS3010/iS3030 and the iS3050. The SPM7 can
be used to increase the charge current of the iS3010/iS3030 for customers
with a high frequency of mains fails.
2. as an integrated rectifier solution in the iS3050 cabinet as part of the system
configuration without battery backup facility. It supports three PM-shelves. This
requires an additional assembly package.
The SPM7 is supplied with a standard AC/DC cable set.
The SPM2 and SPM3 can be extended with a switched mode, single phase
invertor (500VA or 1000VA), to convert 48V DC input to 220V AC, 50Hz. The 230V
AC generated by the invertor can be used to feed e.g. modems and PCs. The
invertor will be switched in the operational mode if the mains voltage drops below
187V AC and will feed the load. After mains is restored, the load is disconnected
from the invertor and connected to the mains again. The invertor is powered from
the central ISPBX battery.
• Batteries
The Hawker range of batteries can be used in combination with the complete
range of SPM rectifier models. The battery types (SBS 30, SBS 40, SBS 60 and
SBS 130) are sealed maintenance free lead-acid batteries. They are provided with
a safety vent at the top. The batteries can be used in any position, with the
exception of the overhead position.
• iS3010
The iS3010 is standard being delivered with a 660VA transformer, the PSU-ML as
power supply. Optionally the SPM0 can be added for the Correct Power and the
No Break functions. The basic system without batteries contains a 660VA
transformer, a PSU-ML and a Rectifier Plate. The Prophix tool can calculate the
power dissipation of an iS3010. Small-configured iS3010 systems can be
equipped with a 300VA transformer and a PSU-S. The PSU-S does not require a
rectifier plate and can not be combined with a SPM0. The Mean Time Between
Failure (MTBF) of a PSU is 35 years. Transformers hardly ever break down; the
660VA transformer has a MTBF of 11.000 years. A broken 300VA can be replaced
by a 660VA if necessary.
• iS3030
The iS3030 is equipped with a PSU-ML and a 660VA transformer and optionally
the SPM0. The Prophix tool can calculate the power dissipation of an iS3030.
• iS3050
Two options are possible: AC - and DC power supply. The AC version is equipped
with a 800VA transformer and PSU-ML per shelf. An SPM7 can be added if
wanted. The DC version is equipped with a System Power Module (SPM) and
PSU-MLD per shelf.

137
 • iS3070/3090
The iS3070 and iS3090 are standard provided with PSU-MLD per shelf and a
System Power Module (SPM). The CSM shelf contains a PSU-MLD. The other
shelves contain a PSU-ML(D) or a PSU-A. Remote PMs are often AC powered but
DC powering is possible as well.

2.8. Main Distribution Frame

A Main Distribution Frame (MDF) facilitates the connection of Printed Wiring Boards
(PWBs) in the shelves, to public and private telephone exchanges and to telephone
sets and applications for management and maintenance. The MDF can be located in
a system cabinet or in a separate MDF cabinet (the use of a wall mounted or free
standing MDF is always possible).

• SOPHO iS3010/3030
For this system a separate MDF cabinet exists which has the same styling as the
iS3010 or the iS3030 system cabinet. This cabinet offers space for 40 Sofycom
blocks, each for 10 wire pairs. Per iS3010 system one MDF cabinet is needed,
which can be wall mounted or free standing (using a floor stand).
• SOPHO iS3050
For this system two types of MDF can be used; a system cabinet with internal MDF
or a separate MDF cabinet. The four shelf system cabinet with internal MDF has
a capacity of housing 109 Sofycom blocks (8 wire pairs) for internal connections
and 109 Sofycom blocks (10 wire pairs) for external connections. The separate
MDF cabinet has the same styling and size as the system cabinet. It has a capacity
of housing 208 Sofycom blocks (8 wire pairs) for internal connections and 208
Sofycom blocks (10 wire pairs) for external connections.
• SOPHO iS3070/3090
Depending on the size of the iS3070/3090 system it is possible to use a system
cabinet with internal MDF, a separate MDF cabinet, a wall mounted or free
standing MDF. In most cases the wall mounted or free standing MDF will be used,
which can be expanded to the size required for the system. In smaller systems,
MDFs as described under the SOPHO iS3050 may be used.

2.9. Licence Mechanism

The type of system is derived from the number of DNR licenses. This makes it
possible to have an iS3010 based upon fault-tolerant hardware. This licence
mechanism really uncouples hardware and software. Prices are based upon facilities
rather than on hardware.

Call@Net uses the same mechanism as was introduced for SysManager. Each

138
system has a unique identification called fingerprint. This fingerprint is stored in the
CPU3000 or CIE-2 board. Based on this fingerprint and the licences a customer buys,
a licence string is generated. This licence string defines what licences are available in
a system. The licence string is placed in a licence file, which is activated at system
start-up or by means of Operational Maintenance. The presence and the contents of
the License string and of the fingerprint are checked at system start-up and afterwards
at regular time intervals. If the result of the check is not correct, the system becomes
operational with the minimum configuration: 32 extensions, granted SOPHO
SystemManager and all the functions that are not restricted by a license mechanism.

There are two types of licences:

- Allowance; An allowance licence defines whether a function is allowed in that

system. In fact this is a system licence.
- Numeric; A numeric licence defines the number of occurrences of a licence, e.g.
the total number of DeskSharing users.

Besides the types of licences also the period a licence is valid can vary. Three variants
are distinguished:

- Infinitive; Valid through the life-time of a system.

- Try & Buy; With a Try & Buy licence it is possible to let a customer get acquainted
with a software function. After the try & buy period the customer can decide to buy
the function. A Try & Buy licence has a valid period of three months. It can only be
active once per licence per system.
- Temporarily; A temporarily licence has a defined valid period. This can be one ore
more months. Per month a price has to be paid.

A service licence is a temporarily licence and unique per system. The service licence
makes it possible to freely use all the software modules of Call@Net for a limited
period of time. Making it unique per system and temporarily prevents fraud with the
service licence. It should be taken into account that a service engineer has to generate
a service licence for each system he visits and when a service licence is necessary.

Licences can be generated on Philips Business Communications' intranet. This

guarantees fast and easy generation of licence strings. The server is available 24
hours a day, 7 days a week.

Installed base systems that upgrade will be licensed according to what is bought
originally. The IPD licence for example, will be set on the maximum value for that
system. So for CPU-ME systems that upgrade to CPU3000, the IPD licence will be set
on 300. For CPU-MT systems that upgrade to CPU3000, it will be 1000.

139
 With Call@Net, the following items are licensed:

140
ITEM NUMBER DESCRIPTION LICENCE TYPE
1 Basic Service Profile IDentity (BSP-ID) Numeric
2 Internal Message Protocol (IMP) Allowance (CCS
only)
3 Automatic Call Distribution (ACD) agents Numeric
5 Digital Private Network Signaling System Allowance
(DPNSS)
6 Cost Accounting Allowance
7 System Management Allowance
8 Full Detailed Call Recording output (FDCR) Allowance
9 Least Cost Call Routing (LCCR) Allowance
10 Voice Mail Interface Allowance
11 iSNet Private Virtual Networking (PVN) Allowance
12 Integrated Password Dialling Numeric
13 Music On Hold from Integrated Allowance
Announcement Server (IAS)
14 Dynamic Delay Messages Allowance
15 Operator Monitoring Allowance
17 iSLinks for CSTA on S0-bus Numeric
18 Active CSTA monitors Numeric
19 Desksharing Numeric
20 Calling Name and Number Display (CNND) Allowance
21 SOPHO iSLinks for CSTA on Ethernet Numeric
22 Installation DNR-EHWA relation Allowance
23 CSTA I/O Services Allowance
24 CSTA I/O Registration Numeric
25 Free Numbering Allowance
26 Central Directory Dialling (CDD) Allowance
27 Completion of Call to Busy Subscriber Allowance
(CCBS)

141
 ITEM NUMBER DESCRIPTION LICENCE TYPE
29 iSNet iPVN Numeric
30 Project Application 1 Allowance
(special project)
31 Multi Line for ErgoLine D340 Numeric
32 Multi Line for ErgoLine D340 and D330 Numeric
33 Multi Line for ErgoLine D340, D330 and D325 Numeric
34 CSTA PBC Application Allowance
35 CSTA EP Application Allowance
36 CSTA Extern Application Allowance
37 CSTA Extern Application Seat Numeric
38 CSTA CC210 Application Allowance
39 CSTA CC210 Application Seat Numeric
40 CSTA PBC Application Seat Numeric
41 CSTA DMS Application Allowance
42 CSTA DMS Application Seat Numeric
45 CSTA 3rd Party TAPI Application Allowance
46 CSTA 3rd Party TAPI Application Seat Numeric
47 CSTA EP Application Seat Numeric
48 Voice Logging Allowance
49 CSTA Voice Log Application Allowance
50 CSTA Voice Log Application Seat Numeric
51 CSTA CTI Server Application Allowance
52 CSTA CTI Server Application Seat Numeric
53 ErgoLine@Net Numeric
54 IP Phone Numeric
55 IP Trunk Numeric
56 Private Virtual Extension (PVE) Allowance
57 QSIG Call Completion Allowance
58 iSNet on top of QSIG (not yet applicable) Allowance
59 QSIG PVN (not yet applicable) Allowance

142
ITEM NUMBER DESCRIPTION LICENCE TYPE
60 CSTA Messenger application Numeric
61 CSTA Messenger application seat Numeric
64 CSTA Desktop application Numeric
65 CSTA Desktop application seat Numeric

Table 2-6 Licensed items.

2.10. Standards

SOPHO iS3000 models:

- Transmission
PCM coding according A-law ITU G.711/G.712
- Electro-Static discharge
- IEC801 and IEC1000
- 12TR21, 25, 26, 27 and 30
- Electro-magnetic compatibility
- VDE0871 class B
- EN50082-1
- EN55022
- Safety
- EN41003
- EN60950
- Environmental Conditions
- ETS300019: storage class 1.2
transportation class 2.3
stationary use class 3.1
- Protocol types
- Euro-ISDN
- DASS2
- DPNSS
- 1TR6
- VN4+
- ISDN
- I.430 (Basic Rate)
- I.431 (Primary Rate)
- Primary Rate
- G.703
- G.704

143
 - DPNSS
- according BTNR 188, issue 6, January 1995; for the supported supplementary
service as stated in the DPNSS compliance document.
- DPNSS/ISDN interworking according BTNR 189-l, issue 01, December 1992.
- Dialling
- Keytone: Q23
- MFC
- QSIG
- ETS 300 171/2
- ETS 300 173
- ETS 300 239

DECT

- DECT Cordless Handsets are compliant with the standards: CTR6, CTR10 and
CTR22 (GAP).
- Electro-magnetic compatibility
- conform IEC801-3/4
- conform EN55022
- conform ETS 300 1 26 (EN 500096)
- Electro-Static discharge conform IEC 801-2
- Environmental Conditions
- conform ETS 300-019 class 2
- conform IP41
- Safety
- conform EN41003
- conform EN60950

Note: All our products have been developed and manufactured according to ISO
9001. We also hold the TickIt software certificate.

144
3. Software History
The following diagram shows the history of the SOPHO ISPBX software.

Figure 3-1 System software releases.

145
 4. Aliases
This chapter contains a list of facility names that are commonly used and their SOPHO
equivalent.

146
Facility Name SOPHO Equivalent
Add-on Third Party Add-on Conference
Administrative Retrieve Data Generation
Alarm Call Emergency Alarm
Alarm Call Wake-up
Alternative Routing Overflow Routing
Any Number Repetition External Number Repetition
Assistance Area Assistance Group
Attendant Console Operator Desk
Automatic Call Back Automatic Ring-Back
Automatic Call Forwarding Follow-me
Automatic Camp-on-Busy Camp-on-Busy
Automatic Ring-Back on Busy Automatic Ring-Back on Busy
Automatic Ring-Back on Free Automatic Ring-Back on No Answer
Automatic Ring-Back on No Reply Automatic Ring-Back on No Answer
Automatic Repeat on Busy Automatic Repeat Night Extension
Automatic Repeat on No Answer Automatic Repeat Night Extension
Barring External Calls ELC Barred
Barge-in Break-in
Blind Operation Visually Handicapped Operation
Broker Call Shuttle
Busy Over-ride Break-in
Busy Over-ride on Busy Extension Break-in
Call Back When Free Automatic Ring Back
Call Back When No Answer Automatic Ring Back
Call Charge Metering Taxmetering
Call Diversion See also : Executive/Secretary Facility,
Group Arrangement, Direct Dial In, Do
Not Disturb

147
 Facility Name SOPHO Equivalent
Call Diverted Indication Call Diversion (Operator)
Call Forward Follow-me
Call Forwarding Direct Follow-me
Call Forwarding No Reply Call Forwarding Don't Answer
Call Hold Enquiry
Call Metering Metering/Taxmetering
Call Pick-up to Group only General Call Pick-up
Call Pick-up to Members Selective Call Pick-up
Call Recording Toll Ticketting
Call Set-up Supervision Listen-in
Call Transfer Transfer
Camp-On-Busy Display (HuntingGroup Group Observation
Supervisor)
Camp-On Call Indication Call Waiting
Chaining Series Call
Code Calling Abbreviated Dialling
Competition of Calls to Busy Subscriber Automatic Ring Back
Conference Call Multi-Party Call
Console-less Operation Night Service
Consultation Call Enquiry
Data Coupler (Holland) Source Identification
Datakop (Holland) Source Identification
Designated Extension Night Service Common Night Extension
Dial Answer Call Pick-up
Dial Answer Night Service CANS Answering
Dialling Barred Indialling Barred
Digit Translation Digit Conversion
Direct Dialling In Barred Indialling Barred
Direct Switch Through Provisional Switch Through
Direct Extension Night Service Individual Night Extension

148
Facility Name SOPHO Equivalent
Direct-in Termination Permanent Line Extension
Ready for Use Downloading (digital sets)
Exclusion Call Splitting
Executive Intrusion Break-in
Executive Over-ride Break-in
Executive Recording Priority to Operator
External Service Display Calling Number Dialling
Facility Clock Facility Timing
First Ring Instantaneous Ringing
Fixed Destination Call Hot line
Group Beep Extension Status Ring
Group Status Display Extension Status Display
Hold (by extension) Enquiry
Hold for Enquiry, Recall Enquiry
Hotel Floor Group Individual Floor Service
Hunting Group Observation Group Observation
Immediate Ringing Instantaneous Ringing
Individual Call Pick-up Selective Call Pick-up
Inward Restriction Indialling Barred
Man Machine Communication Man Machine Language
Multi Access A combination of Call Pick-up, Extension
Status Display and Second Line
Answering.
Multi Line Second Line Answering
Multi Line Access Group Multi Access
Multiple Console Operation More than One Operator
Night Line Call Pick-up CANS Answering
Number Translation Digit Conversion
Off hook dialling Softspeaking
Operator Assistance Area Assistance Group

149
 Facility Name SOPHO Equivalent
Operator Console Operator Desk
Operator Position Operator Desk
Outgoing Trunk Camp-on Queuing Call Queuing
Over-ride Break-in
Port Shutdown Data Guarding
Power Failure Transfer Emergency Switch Over
Preference to Operator Priority to Operator
Priority Access to Operator Priority to Operator
Priority Operator Access Priority to Operator
Route Optimisation Alternative Routing
Serial Call Series Call
Soft Ringing (on Lamp Flash) Extension Status Ring
Speed Calling Abbreviated Dialling
Stacking Calls Camp-on-busy
Status Display Extension Status Display
Switched Absent - Call Forwarding Call Forwarding when Absent
System Speed Calling Abbreviated Dialling
Three Party Conference Add-on Conference
Timer Stopwatch
Traffic Barring Traffic Classes
Traffic Service Classes Traffic Classes
Unattended Service Night Service
Waiting Call Call Waiting
Waiting Message Message Waiting

Table 4-1 Aliases

150