MX-ONE User Manual

MX-ONE User Manual
MX-ONE User Manual
- MX-ONE Telephony System Description
- Feature List
MX-ONE User Manual
MX-ONE Telephony System Description
Contents
1 Executive Summary
2 System Overview
2.1 General
2.2 Architecture
2.3 Telephony Server
2.4 Media Gateway
3 Operation and Maintenance

3.1 Fault management
3.2 Configuration Management
3.3 Security Management
3.4 Performance Management
3.5 Accounting Management
4 Terminals and End User Equipment

4.1 Supported Terminal Types
5 License Handling
5.1 Individual License
5.2 System License
6 Networking
7 Quality of Service
8 Environmental Conditions
8.1 General
8.2 Climatic Environment
8.3 Electromagnetic Compatibility and Protection (for Media Gateway)
MX-ONE User Manual
1 Executive Summary
MX-ONE Telephony System is intended to be used as a Branch office to an ASB
501 04 system. The system consists of an ITU-T H.323 compliant packet based
voice communication system and it is designed to fit into the existing infrastructure
of a modern enterprise LAN (Local Area Network). This saves the cost of operating
an additional network for voice.
The enterprise LAN must be based upon the IEEE 802 Local and Metropolitan
Area Network family as data link layer, where the MX-ONE Telephony System
supports IEEE 802.3 more known as Ethernet, and, on top of that running the
Internet Protocol (IP).
To the end user, the MX-ONE Telephony System is transparent in comparison with
the classic circuit switched PBX. Number dialing and terminal interaction is the
same with the same array of services and functionality found in a classic circuit
switched system. This means that most well known features and services are
available for the end user via IP telephones.
The MX-ONE Telephony System comes with vast networking capabilities. The
combination makes integration into the existing infrastructure easy, and, the
flexibility of the MX-ONE Telephony System makes it scale very well for networked
Branch offices.
The MX-ONE Telephony System also provides the enterprise with a step-wise
migration from the classic circuit switched Private Branch Exchange (PBX) into a
converged voice and data network.
2 System Overview
2.1 General
MX-ONE User Manual
This section gives an overview of the MX-ONE Telephony System with its
components, terminals, services and features. Together they form a fully featured
enterprise telephony solution for deployment in the enterprise LAN environment.
For detailed information on the components, terminals and so on, please see later
section in this document or in separate documents in the library. For example, for
descriptions of the individual features see description for FEATURE LIST and for
capacities of the system and the individual features, see description for
CAPACITIES .
2.2 Architecture
The core of the enterprise network is based upon IEEE 802, more known as
Ethernet, preferably in a switched architecture with capabilities of high-grade
quality transmission. The Quality of Service (QoS) capability of the data link layer,
Ethernet layer, is the fundamental base for low delay and packet loss, parameters
of great importance for voice services running over packet networks.
The network layer, IP layer, must also satisfy the Quality of Service needs of an IP
based voice system running in a converged voice and data network.
The entities of LAN switching and IP routing are not part of the MX-ONE Telephony
System offering as such but are rather the pre-requirements of a functional system.
The QoS capabilities of a modern enterprise LAN are matched in the network
elements of the MX-ONE Telephony System. The end-to-end Quality of Service for
voice services over IP can therefore be met and the transition to packet based
voice is secured.
MX-ONE User Manual
Figure 2-1. Architectural overview
2.2.1 MX-ONE Telephony System
The MX-ONE Telephony System is composed of a Telephony Server and a Media

Gateway.
Combined together they constitute the basic H.323 functionality of call signaling,
call control and media streaming/media conversion. Connected to the enterprise
LAN they provide voice services over IP in the IS/IT environment.
MX-ONE User Manual
The Telephony Server and the Media Gateway are to be treated as one system
component inseparable from each other. The Telephony Server is based upon
open standard hardware and run on a commercially available operating system.
The Media Gateway is an embedded device traversing the speech from TDM to IP
and vice versa.
2.2.2 End-user Terminals
To the voice end-user the MX-ONE Telephony System solution offers H.323
endpoints in the form of wired IP phones and H.323 compatible IP clients.
The wired IP phones must be supplied from Ericsson to ensure the highest level of
featured functionality but can be of any brand, supporting the open standard of
H.323. It is also possible to connect four analog extensions. They can be used for
legacy phones for emergency or elevator courtesy phones or group 3 fax machines
intended for indoor use for example.
2.2.3 Networking Capabilities
In this context, networking means to provide voice services over network links to
other entities of PBXes. The intra connectivity over private ISDN is according to
ITU-T ISDN signaling over the Q reference point, more known as QSIG.
One major gain with the MX-ONE Telephony System is the networking capabilities
over IP based networks.
Implementing QSIG over H.323 over packet based IP networks, to supply basic
and supplementary services transparently, makes networked PBXes possible over
IP intranets and also over the Internet with appropriate protection.
Networking PBXes over IP cut costs related to the TDM-based leased line.
Furthermore it simplifies Branch office scenarios to more fit the data network model
with IP connected Branch Offices.
3.1 Telephony Server

MX-ONE User Manual
3.1.1 General
The Telephony Server consists of software loaded on a standard server platform. It

is recommended to use a server grade hardware (HW) with sufficient redundancy
in memory and hard disks etc.
The software consists basically of the following parts:
• The telephony applications
Software that executes the call handling and has full control of all ongoing
calls and resources in the Media Gateway. For detailed information on the
telephony functions, please see description for FEATURE LIST and see
description for CAPACITIES .
• The service system
Middleware that interfaces the telephony applications. For a detailed

description, please see 2.3.2 Service System .
• The Linux operating system

• The hardware (Intel x86/.IA32)
MX-ONE User Manual
Figure 3-1. Telephony Server
3.1.2 Service System
The Service system includes the following functions used to support the
applications:
• Start and restart of the Telephony System

• Data backup
• Handling of alarms
• Handling of telephony licenses
3.1.2.1 Start and restart of the Telephony System
System start
The purpose of the system start is to put the system into operation after major
program packages have been installed.
Initial load and start
MX-ONE User Manual
At the initial load and start, values are assigned to data to activate the system
functions.
Initial load and start is divided into the following steps:
• Loading or starting program units

• Initiating system data either from a terminal or from a command file
• Entering commands to deblock the virtual device boards in the Media Gateway
Manual restart
Manual restart is used to initially set dynamic data manually in order to correct
faults that have occurred in the system.
The following can be manually restarted:
• The system
All program units are restarted. All traffic in the exchange is stopped and all
connections that existed before the restart is disrupted.
• Program units
Each stated program unit is restarted.
• Virtual device boards
The restart is carried out by an activation request from the device-handling

program to the stated board.
A manual restart is initiated by a command and the result is presented on the

connected terminal.
3.1.2.2 Backup
Data backup
The Data backup function is used to backup and restore exchange data.
The following types of exchange data can be restored:
MX-ONE User Manual
• System configuration data

• Application data (for example, extensions and trunks)
The system can store five backup versions. If there already exist five versions
when a new backup is created, the oldest version is removed.
Data backup is initiated by a command or done periodically and if it fails, an alarm
will be sent.
Safety backup
Safety backup is executed via a backup script.
3.1.3 Configuration
3.1.3.1 Program unit configuration
Every program unit has a name and a unique program unit number. Every program
unit also is assigned a set of characteristics and this set of characteristics defines
the program unit type. Examples of such characteristics are whether the program
unit handles device boards or not or if the program unit is issuing alarms.
Information on program unit types and the sets of characteristics can be obtained
from the system.
3.1.3.2 Hardware configuration
The Media Gateway has only one physical board but the device boards are
emulated (virtual boards).
Information on existing device boards can be printed, for example:
• Board type
• If the board is blocked or not
It is also possible to receive information on certain resources on the Media

Gateway, for example, revision information, virtual device boards, auxiliary devices
as well as information on the Media Gateway itself.
MX-ONE User Manual
3.1.4 Features
3.1.4.1 Functional Change
The Functional change feature is used when a modification program package is to

be put into service. The purpose of the feature is to carry out the following as
smoothly as possible:
• Correct errors in the software

• Change/add functions in the software
• Update the software
The feature performs the following:
• Prepares the system for program unit change

• Adds new program units
• Switches to the new program units
• Ends program unit change
• Displays program unit change information, for example, which version is active or
passive and the revision states of the old and new versions
3.1.4.2 System Supervision
The System supervision feature is used to:
• Control the performance of the supervised objects

• Detect faults
• Initiate fault correction measures
• Isolate faults
Supervision of execution signals and times

The system supervision feature supervises the execution signals and times in the
traffic and background level.
All signals are checked before they are allowed to start executing in a program
unit. If any fault is found, the signal is not executed and the job is discarded. The
faulty signal is stored for manual fault investigation.
MX-ONE User Manual
If the signal is correct, the execution in the program unit starts. If the program unit
is looping more than the allowed time, the execution will be interrupted and the job
discarded. This is called execution time out.
Disturbance counter
A disturbance counter reflects the quality of the program execution. The counter is
incremented a number of steps each time a fault occurs. The number of steps
depends on the severity of the disturbance.
An alarm is sent when the first execution fault occurs after start or restart and when
the counter exceeds the maximal allowed value. The counter is periodically
decremented to avoid exceeding the value.
Program unit administration
A program unit is handled separately on the following occasions:
• Unsuccessful restart
• Unsuccessful reload
• Some other problem has caused a request for restart
If a program unit fails at restart, it is blocked for signaling.

Restart of virtual device board
The restart is activated by a request from the program that administers the virtual
device board. Two attempts are made to restart the board, if both are
unsuccessful, the board is blocked and an alarm is issued.
Reload
The following types of reload exist:
• Reload of system
• Reload of program unit
• Reload of data
All commands altering exchange data and program code are stopped at a reload.
When the permanent errors have been repaired, a reload takes place.
Data reload always takes place in the entire system. During the start phase,
program units are informed about the connections between dynamic and reload
MX-ONE User Manual
data. This is to give the program units the possibility to update these connections.
An alarm is issued to inform about the data reload. If the data reload or the start
phase fails, an alarm will be issued.
Blocking
Blocking is used to isolate a faulty program unit in the system and thereby avoiding
fault situations until the fault has been repaired. The program unit is taken out of
traffic and will not receive any signals.
The consequences for the system depend on function of the program unit. When a
traffic executing program is blocked, any calls from the board are ignored and the
users connected to the board are taken out of traffic.
3.1.4.3 Signal Tracing
The signal tracing feature is used for fault location. The feature implements the
trace error log and the general trace function and stores signals transported in the
interfaces or text items generated by the program code. Up to fifteen signal traces
can be specified simultaneously.
3.2 Media Gateway
3.2.1 General
The Media Gateway is used to convert the media provided in the Switch Circuit
Network to the format required in the IP network or vice versa. For this, the Media
Gateway contains the bearer control protocols and hardware devices for network
access termination and media stream manipulation.
The Media Gateway is equipped with the following devices.
• 8 E1 interfaces (ISDN, QSIG)

• 4 analog extension interfaces (analog phones and G3 fax)
• 2 Ethernet (10/100BaseT) interfaces for signaling and media
MX-ONE User Manual
The Media Gateway design is based on packet (cell) switched platform

incorporating all the required network interfaces and media handling resources.The
Media Gateway makes it easier to use active (simultaneous) VoIP channels for
large numbers of IP extensions. The VoIP Channels have, and as well as
• Echo Cancellation
• Comfort Noise Generator (CNG)
• Voice Activity detection (VAD)
• Auxiliary resources, for example, DTMF (Dual Tone Multi Frequency)
sender/receiver, tone sender and conference bridges
3.2.2 Major Functions
Analog interfaces
It is possible to configure the software for analog connections.
Group 3 fax terminals can be connected to the POTS interface and when fax data
is to be sent over an IP network, only G.711 codec mode is supported (that is, put-
through mode). This means that when the data is recognized as fax traffic by the
Telephony Server, the selection of speech codec will be forced to G.711.
ISDN/QSIG
The 30B+D (I.431) format is supported. The D-channel signaling support conforms
to I.441 (30B+D) Layer 2 specifications.
Note The layer 2 specification of QSIG is the same as ISDN. Only the layer 3 is
different and handled by the system application SW in the Telephony Server.
Normally one of the 8 E1 interfaces serves as clock master for the Media Gateway.
If this E1 interface is lost, another E1 interface is selected as clock source.
VoIP
The Media Gateway is involved only in the conversion of the RTP packet into TDM
data, or vice versa. This is used for gateway calls. The ISDN signals are
terminated in the Media Gateway and the layer 3 signals are sent to the Telephony
Server for further processing.
For the RTP packet, G.711, G.729AB or G.723.1 speech codecs are supported
with dynamic packet length from 10 ms to 30 ms in steps of 10 ms.
MX-ONE User Manual
VAD for silence code generation and CNG for better speech quality, are supported
and can be enabled per call.
Static jitter buffer is also supported for maximum 240 ms buffer length. The buffer
is configurable and allocated on per call basis.
Maximum 60 active (simultaneous) VoIP channels are supported and it is possible
to select arbitrary codec mode for each channel.
Echo Cancellation
The Media Gateway supports echo cancellation complying with ITU-T G.168
standard.
The echo canceller implemented in the DSP is mainly used for the VoIP traffic but
can be attached to any traffic. The echo cancellation algorithm manages up to 128
ms tail length with minimum 20 dB attenuation.
3.2.3 Application and Networking Environment
The IP media is transmitted over the corporate LAN while the Media Gateway
communicates with the Telephony Server via a dedicated 10/100BaseT Ethernet
link carrying call/media control and connection protocol on top of TCP/IP.
The E1 interface provides access to both public (PSTN) and private networks. The
networking protocol for the PSTN is based on ISDN while the networking protocol
for the private network is based on QSIG Basic Call (QSIG Generic Functional
Protocol (GFP) for supplementary services).
3.2.3.1 Mechanical
MX-ONE User Manual
Dimensions
Width 19 inch
Height 1 U (1 U=44.45 mm)
Depth 240 mm
Cabling
Type Quantity Purpose
Front
RJ45 2 10/100BaseT interfaces for connection to the Telephony Server
(call control signaling) and media (VoIP)
9 pin D-type 1 V.24 serial port
RJ45 8 E1 connection (1 per link)
RJ11 4 Analog/Fax interface, 4 ports
Rear
IEC320 1 AC inlet
/EN60320
Power Supply and Cooling
Input power 100-240 VAC, 50 - 60 Hz
Cooling Forced fan cooling
Status Display/Indicator
MX-ONE User Manual
The status of the Media Gateway and connectors is displayed with light emitting
diodes (LEDs).
• Green - power status

• Red - major fault
3.2.3.2 Interfaces and Resources
Ethernet and IP Interface

There are two 10/100BaseT Ethernet ports in the Media Gateway, one port is
dedicated for the Telephony Server-Media Gateway communication and the other
is dedicated for transport of realtime and other IP packets, for example, voice
packets.
3.2.3.3 Interworking with Telephony Server
Start/restart
The Media Gateway is booted from the network at start up. At initial power up or
system restart, the bootstrap logic first performs the necessary hardware
initialization (serial interface, flash parameter settings and Ethernet interface
(signaling only port) etc.). The bootstrap logic for Media Gateway startup/restart is
stored in the flash memory. Then the software is retrieved from the Telephony
Server.
Interfaces with the Service System
The interfaces with the Service System are mainly related to the basic platform
functions, including the operating system functions, but the interfaces are also
related to the application dependent configuration and alarm functions. The
following interfaces exist:
• IP interface
For communication between the Telephony Server and the Media Gateway.
• Virtual board interface

MX-ONE User Manual
For addressing, switching and controlling virtual board devices. Examples of

virtual board interfaces are:
o Board control interface
SW-HW interface used for control and restart of virtual boards.
o Media control interface
For control of switch connections.
• Operation and maintenance interface
For handling messages for alarm as well as status reports and supervision
between the Telephony Server and the Media Gateway. The following
messages are defined:
o Tracing of messages
For tracing of this interface in the Telephony Server. It is possible to

call trace down to the hardware level.
o Media Gateway configuration fetch
The virtual board configuration is fetched from the Media Gateway at

initial start of the Telephony Server.
o Media Gateway polling interface
The Media Gateway is polled regularly for alarms, which also serves
as a heartbeat between the Telephony Server and the Media
Gateway. The Media Gateway reports alarms, a list of alarm
categories and a list of corresponding alarm texts.
o Media Gateway maintenance interface

MX-ONE User Manual
The information about restartable/reconfigurable resources in the

Media Gateway is fetched. Restart or reconfiguration of the Media
Gateway can be requested through this interface.
3.2.3.4 Auxiliary Functions
Key code (DTMF) Receiver/Sender

The Media Gateway supports the in-band signaling sending and detection based
on DTMF. The key code receivers detect the DTMF coded digits received from
analog telephones or incoming trunk lines.
For certain applications, DTMF receivers are activated for the entire duration of a
call to detect service requests.
Tone Sender
Tone senders are required for incoming trunk calls and conference calls. The tone
senders send out tone messages (such as dial tone, busy tone, congestion tone or
ringback tone).
The tone sender characteristics comply with the specific characteristics for the
selected market.
Multi-party Ports
The Media Gateway supports a number of multi-party ports (or conference inlets)
for conference calls. The function is implemented in the DSP logic.
Recorded Voice Announcements (RVA)
The Media Gateway supports Recorded Voice Announcement (RVA) for greetings,
and call progress messages. The Voice Prompts are stored in WAV file format
(normally in the Telephony Server), downloaded at startup and stored in the local
flash memory. Storage capacity in the Media Gateway is at least 60 minutes. It is
possible to change the contents of the voice prompts in runtime. The Media
Gateway also supports concatenation of several voice prompts to one message
and repetition of a single stored prompt.
MX-ONE User Manual
4 Operation and Maintenance

The Operation and Maintenance is built upon the FCAPS model:
• Fault management
• Configuration
• Accounting
• Performance
• Security
4.1 Fault management
4.1.1 Alarms
The alarm feature is used to store information on faults and disturbances in- or
outside a system and to bring the attention of service personnel to these faults and
disturbances.
4.1.2 Alarm Classes
Each alarm is assigned one of the following alarm classes:

Alarm class Severity level
4 Critical
3 Alert
2 Warning
1 Information
0 Cleared
The alarm severity 0 (cleared) is special. When the alarm sender notices that an
alarm condition no longer exists, the sender will clear the alarm and the alarm
class changes to 0.
4.1.3 Alarm Generation

MX-ONE User Manual
The alarm classes (except alarm class 4 (critical)) are assigned a limit for
incrementation alarm. This means that an incrementation alarm is generated when
a predetermined number of alarms with a certain alarm class have been stored in
the alarm log. The incrementation alarm is then assigned the next higher alarm
class. The limits for incrementation alarms are specified in a configuration file.
An alarm is also generated when the alarm log risks becoming full.
4.1.4 Alarm Actions
Alarm actions can be configured to run when an alarm is stored in the alarm log, or
when an alarm changes severity, for example is cleared.
The alarm action can be any UNIX or Linux program or script and examples of
actions that can be taken are:
• Sending email or SMS with alarm information

• Updating web pages
4.1.5 Alarm Presentation
Alarms can be presented in the following ways:
• As printout of alarm log (can be in any of eight formats)

• As continuous view of alarm log
• As email or SMS
• On a network management center/workstation
4.1.6 Clearing of Alarms
When the system detects that an alarm condition (fault) no longer exists, the alarm
log is informed and the alarm is cleared.
A cleared alarm has the alarm class 0 but information on the old class is kept.
4.1.7 Alarm Noticed

MX-ONE User Manual
When an alarm is noticed and the correction work has started, the alarm is marked
as noticed. It is possible to add a comment when entering the notice command.
The command is stored with the alarm in the alarm log.
4.1.8 Alarm Log
If the alarm log becomes full, the alarm with the lowest severity levels are removed
from the log. A configurarion parameter determines which alarms that are least
important
4.1.9 Availability
Alarms are not lost when the system is restarted. However, they are lost when the
alarm feature is reloaded. After a reload, the feature will request a resend of all
alarms from the alarm sender.
4.1.10 SNMP
The Telephony Server has an advanced alarm and event handling function.
An SNMP-interface exposes standard MIB II information and alarms generated in
the Telephony Server are sent as SNMP traps. When alarms are cleared in the
system, alarm cleared traps are sent to the connected SNMP Managers.
In addition to alarms, events are stored in the Linux syslog. These events are
usually not critical for the operation of the system, but they might provide useful
information on the behaviour of the software or when debugging.
4.1.11 Automatic fault administration
The automatic fault administration feature is used to implement the following

actions when faults occur. The system is to:
• Decide and carry out a suitable recovery to minimize the consequences for the
system.
MX-ONE User Manual
• Inform the system operator about faults and the results from the measures taken.
The alarm log is used for the communication.
4.2 Configuration Management
By using commands it is possible to adapt the system to suit the individual

customer. The configuration alternatives include extension and system features
and the adaptation of the trunk lines to the PSTN or to other PBXes. The
configuration is done from an I/O terminal with a commmand line interface.
Extension adaptation can also be done from the Extension manager included in the
D.N.A. suite. It is possible to configure the system both locally and remotely.
4.3 Security Management
User Authentication
Each command is ssigned one of eight authorization classes, which are assigned
an alterable password with a maximum of 16 characters. The authorization classes
decides which user can use a specific command.
Audit and Security Trail
The Security trail contains information on all administrative-user logon attempts,
including user ID, date, time etc.
The Audit trail contains all configuration operations that in some way modify data in
the Telephony Server (create, modify and delete - operations)
4.4 Performance Management
Threshold Supervision
Critical resources in the Telephony Server are continuously monitored. When they
reach a certain threshold, alarms are generated.
Traffic Measurements
MX-ONE User Manual
Traffic measurements provide statistical information on the telephony traffic in the

Telephony Server. Examples of measurements are outgoing calls on a certain
route and the total number of incoming calls.
Traffic measurements must be configured and started manually and data will be
collected based on a number of configurable criteria.
4.5 Accounting Management
The Telephony Server logs call records that can be used for billing purposes. Each
call record can include a configurable number of data fields depending on the
information that is required for output. The output can be stored as a file or can be
sent to a connected post processing equipment.
5 Terminals and End User Equipment
The entrance point for the end-user of the MX-ONE Telephony System solution is
via its clients. These clients can be hardware telephones or software clients
running as PC applications.
To the voice end-user, the MX-ONE Telephony System offers H.323 Endpoints in
the form of wired IP phones and IP clients.
The following terminal types are supported:
• IP telephones
DBC 422 and DBC 425
• IP clients
ECC and ECA which are parts of the D.N.A. suite.

MX-ONE User Manual
• Analog devices
Analog telephones, answering machines or Group 3 FAX. For full

functionality, the device must have a recall key with timed break-of-loop.
6 License Handling
The license handling feature and its license server are used to:
• Check if a service is available

• Seize and release licenses
Each license file consists of license tags, the number of currently used licenses
and a maximum number of licenses. Each sales object that requires licensing has
a unique license tag.
The license file is delivered to a site in an encrypted form using DES (Data
Encryption Standard), and is installed on the license server in encrypted mode.
There are two types of licenses:
• Individual license
• System license
6.1 Individual License
The individual license is used for ports, for example, the IP extension or personal
number. Each individual license is defined with a maximum number of allowed
licenses .
A sales object that requires a license, seizes one when the object is initiated and
releases it when the object is removed from the system.
6.2 System License

MX-ONE User Manual
The system license is used for optional system features like, for example, network
services. A system license has one of the following two values: service is available
or service is NOT available.
Tryout Period
It is possible to have a tryout period for sales objects. The length of the tryout
period is defined when the license file is loaded into the system. The license file
can be used as tryout license on any system (any hardware ID), but is limited to a
maximum of 30 days.
7 Networking
General
In the MX-ONE Telephony System, a number of network features has been
introduced. Two groups of network features are distinguishable, that is, system and
user features (covering both extension and operator features). To use the network
features fully, a signaling system that can convey the necessary information is
needed.
For connections with ISDN, system features as well as user features are
applicable.
For connections with packet-based signaling, H.323, system features as well as
user features are applicable.
The network features are divided in two groups, those using standard ISO-QSIG
signaling and others using proprietary signaling. When the MX-ONE Telephony
System is connected to an ASB 501 04, all features are available for both ISDN
and H.323 signaling.
The system features are used by an exchange or exchanges in order to route a call
in a controlled, rapid manner to the called destination.
A user can only affect user features, not system features.
Calls, for example from the PSTN in a satellite exchange or from an extension, can
be rerouted or diverted to the exchange where the centralized operator function
MX-ONE User Manual
has been introduced. Answer positions can be specified per exchange with a
maximum of local Night Service extension, and a maximum of three centralized
operators. The exchanges are informed about present centralized operators, and
select an answer position in a descending order of priority from exchanges with
active operators.
8 Quality of Service
The MX-ONE Telephony System supports layer 2 and layer 3 QoS. To ensure a
better flow of guaranteed packet delivery, layer 2 QoS is supported according to
IEEE 802.1p/Q. This labels layer 2 frames with a priority setting enabling VLAN
aware devices to give priority to the Media Gateway voice traffic and the Ericsson
IP Telephones DBC 42x.
Layer 3 QoS is supported by means of Differentiated Services according to RFC
2474 and is implemented in all Ericsson voice products for the enterprise.
Managing QoS is not just a matter of plain support in the network elements and
clients but rather of a policy based upon what is wanted to achieve. It is however a
strong recommendation to plan for and deploy QoS in an IP network intended to
carry voice for business class telephony.
9 Environmental Conditions
9.1 General
The MX-ONE Telephony System consists of various products designed in-house

(for example, the Media Gateway and IP Telephones) as well as insourced server
products based on the PC pentium platform.
The MX-ONE Telephony System operates in typical residential, commercial, and
light industrial location. In locations where the environmental parameters exceed
MX-ONE User Manual
the values described in this document, special measures must to be taken, for
example, using extra cooling for high temperatures or inserting extra filtering for the
electrical environment.
In the following sections, the regulatory rules are listed for various operational
conditions. The relevant values and parameters are imposed, in the first hand, for
the in-house products of the MX-ONE Telephony System but the same is likely to
be applicable to other outsourced products and HW platforms under similar
operational conditions.
Any deviating values are to be given in the respective products along with the
operational conditions.
9.2 Climatic Environment
The values below are taken from the ETSI standard ETS 300 019-1 (1992)
(Environmental conditions and environmental tests for telecommunications
equipment), which combines environmental parameters specified in the IEC 721-3
series (Classification of groups of environmental parameters and their severities).
The MX-ONE Telephony System comply with ETS 300 019-1-1, class 1.1 Weather
protected, partly temperature controlled storage locations. This is in line with class
1K3 (climatic) and 1M2 (mechanical) in IEC 721-3-1 (1987).
The limits of the climatogram are:
• Temperature range: -5 to +45 degrees C

• Relative humidity: 5 to 95%
9.3 Electromagnetic Compatibility and Protection (for

Media Gateway)
9.3.1 Emission
9.3.1.1 Radiated Emission

MX-ONE User Manual
CISPR 22 Class A applies to the Enclosure.
9.3.1.2 Conducted Emission
CISPR 22 Class A applies to all RF emissions.

IEC 61000-3-2, Class A applies for in-house products.
9.3.2 Immunity
9.3.2.1 Radiated immunity - Enclosure port
CISPR 24//IEC 61000-4-3 Radio-frequency electromagnetic field - Amplitude modulated

CISPR 24//IEC 61000-4-2 Electrostatic discharge
9.3.2.2 Conducted immunity - signal ports and telecommunication ports
CISPR 24//IEC 61000-4-6 Radio-frequency continuously conducted

EN 55024/EN 61000-4-5 Surge (applicable for EU)
CISPR 24/IEC 61000-4-4 F ast transients
9.3.2.3 Conducted immunity - input a.c. power ports
Note (including equipment marketed with a separate a.c./d.c power converter)

CISPR 24/IEC 61000-4-6 Radio-frequency continues conducted
CISPR 24/IEC 61000-4-11 Voltage dips
CISPR 24//IEC 61000-4-11 Voltage interruptions
CISPR 24//IEC 61000-4-5 Surges
CISPR 24//IEC 61000-4-4 Fast transients
9.3.3 Electrical Safety Requirements
The MX-ONE Telephony System falls within the scope of and complies with the
regulatory rules of the Safety of Information Technology Equipment - IEC 60950
(Europe), UL 60950 (North America).
MX-ONE User Manual
Feature List
Contents
1 Executive Summary
2 Glossary
3 Features
3.1 Feature Descriptions
3.2 Feature Types
3.2.1 System Features
3.2.2 User Features
3.2.3 Network Features
3.3.1 IP Phone and IP Client
3.3.2 Analog Phone
3.4 Feature List
3.4.1 Abbreviated Dialing
3.4.2 Account Code
3.4.3 Alarm Extension
3.4.4 Alternative Routing
3.4.5 Analog Extensions
3.4.6 Authorization Code
3.4.7 Callback, Busy Extension/Call completion
3.4.8 Callback, Busy Outgoing Lines
3.4.9 Callback, No Reply/Call completion
3.4.10 Callback, Not Available/Call completion
3.4.11 Call Information Logging
3.4.12 Calling Line Identity
3.4.13 Call List (Call log)
3.4.14 Call Metering/Charging
3.4.15 Call Pick-up, Individual
3.4.16 Call Pick-up, Group
3.4.17 Call Waiting/Call offer
3.4.18 Camp on Busy
3.4.19 Choice of Language
3.4.20 Class of Service (CoS) or Common Service Profile (CSP)
3.4.21 Common Public Directory Number
3.4.22 Conference
MX-ONE User Manual
3.4.23 Connected Line Identity

3.4.24 CSTA
3.4.25 Customer Group
3.4.26 Customer Identity Storage
3.4.27 Direct-In Dialing
3.4.28 Diversion, Busy
3.4.29 Diversion, Bypass
3.4.30 Diversion, Common
3.4.31 Diversion, Direct
3.4.32 Diversion, Individual
3.4.33 Diversion, No Reply
3.4.34 Diversion, Origin
3.4.35 DNIS for ACD
3.4.36 Do Not Disturb, Group
3.4.37 Do Not Disturb, Individual
3.4.38 DSS1 Network side
3.4.39 Electronic Mail
3.4.40 Emergency Calls to Operator
3.4.41 Facility Restriction Level/Travelling Class Mark (FRL/TCM)
3.4.42 Follow-me, External
3.4.43 Follow-me, Internal
3.4.44 Free Seating
3.4.45 General Cancellation
3.4.46 Generic Extension
3.4.47 Group Hunting
3.4.48 Hot Line, Delayed
3.4.49 Hot Line, Direct
3.4.50 Incoming Automatic Inter-PBX Calls
3.4.51 Incoming Calls via Operator
3.4.52 Information System/Interception Service
3.4.53 Inquiry
3.4.54 Internal Basic Calls
3.4.55 Intrusion on Busy Extension
3.4.56 Intrusion with Forced Release
3.4.57 IP Extension
3.4.58 IP Networking
3.4.59 ISDN Networking
3.4.60 Last External Number Redial
3.4.61 Least Cost Routing
3.4.62 Malicious Call Tracing
3.4.63 Manual Message Waiting (MMW)
3.4.64 Message Diversion
3.4.65 Message Waiting
3.4.66 Message Waiting Indication (MWI)
3.4.67 Music on Hold/Wait
3.4.68 Name Identity
MX-ONE User Manual
3.4.69 Night Service

3.4.70 Number Analysis/Number Series
3.4.71 Number Conversion and Bearer Capability Substitution
3.4.72 PBX Operator
3.4.73 Original A-Number
3.4.74 Outgoing Automatic Call
3.4.75 Outgoing Call via Centralized Operator
3.4.76 Parking with Individual Call Pick-Up
3.4.77 Path Replacement
3.4.78 Personal Number
3.4.79 Priority Routing
3.4.80 Private Network Routing
3.4.81 Recall to Operator
3.4.82 Recorded Voice Announcement
3.4.83 Refer Back
3.4.84 Release Principles
3.4.85 Repeated Diversion
3.4.86 Rerouting
3.4.87 Routing, Alternative Routing
3.4.88 Routing, Overflow
3.4.89 Routing, Repeat Attempt
3.4.90 Routing, Return Block
3.4.91 Serial Call
3.4.92 Suffix Dialing (End-to-End DTMF)
3.4.93 Traffic Connection Matrix
3.4.94 Traffic Recording
3.4.95 Transfer/Call Transfer
3.4.96 Transit Counter
3.4.97 Transit Traffic
3.4.98 Trunk Call Discrimination (TCD)
3.4.99 Voice Mail
MX-ONE User Manual
1 Executive Summary
This document gives a short description of all features available in MX-ONE
Telephony System.
The MX-ONE Telephony System is intended as being a branch node to an existing
MD110 at the Main site.
This means that the MX-ONE Telephony System must use the existing Centralized
operator and Voice mail system located at the Main site.
The MX-ONE Telephony System is intended mainly for IP extensions. All Mobile
extensions must also be installed at the Main site.
2 Glossary
For a complete list of abbreviations and glossary, see description for ACRONYMS,
ABBREVIATIONS AND GLOSSARY .
3 Features
3.1 Feature Descriptions
For each feature, the following information is presented:
• Feature type
• Definition
• Settings
• Procedure and function
For information on capacity, see description for CAPACITIES .

MX-ONE User Manual
In this document, features are listed in alphabetical order in a tabular format.
Most of the features described in this document are covered by a basic license.
3.2 Feature Types
3.2.1 System Features
System features are features that are fixed or can be programmed in the MX-ONE
Telephony System. These features cannot normally be affected by any type of user
terminal. System features can only be used within the MX-ONE Telephony System
system or over a network to other connected MX-ONE Telephony System systems
or to other PBXes.
3.2.2 User Features
User features generally can be accessed from any user terminal that is connected
to the MX-ONE Telephony System.
For information on which user features that can be initiated or terminated for each
the type of terminal, see description for CAPACITIES .
3.2.3 Network Features
Network features are generally available only when the MX-ONE Telephony
System is connected to another MX-ONE Telephony System or to other PBXes by
way of an ISDN tie line using ISO QSIG or via H.323 over an IP connection.
For information about which features that are available for the PSTN/ISDN and
ISDN ISO-QSIG/ H.323 connections, see description for CAPACITIES.
Note Certain network features are only available when the MX-ONE Telephony
System is connected to another MX-ONE Telephony System, an MD110, or a
BusinessPhone system; these features may not work with a PBX from another
vendor.
MX-ONE User Manual
The terminals described in this section are the ones that can be connected to MX-
ONE Telephony System. Most of these terminals are voice terminals.
3.3.1 IP Phone and IP Client
Any H.323-compatible IP terminal (phone or client) may be connected to the MX-

ONE Telephony System. However, for full functionality, Ericsson IP phones or the
Ericsson Communication Client (ECC) must be used. Basic functionality is
available according to the H.323v2/v4 standard, including Inherent Free Seating.
Terminal features include: support of G.711, G.723.1, and G.729ab codecs.
New features, corrections, and enhancements are installed automatically from the
web server when the phone is first turned on. The IP address can be assigned
automatically from a DHCP server or manually entered.
For more information on supported phones and clients, see feature description for
IP EXTENSION .
3.3.2 Analog Phone
Any type of analog phone with DTMF Signaling can be connected to the MX-ONE
Telephony System. The analog phone must have a recall key with timed break-of-
loop.
3.4 Feature List
3.4.1 Abbreviated Dialing
User
Feature
Definition The ability of extensions to make calls by dialing an abbreviated number
which is automatically translated to a full number and sent out by the system.
MX-ONE User Manual
Abbreviated numbers can be common to the system for all users or individual
for use by a single extension (only applicable for analog extensions).
Settings Programming of abbreviated numbers are done by command from an I/O
terminal.
Procedure An abbreviated number is a 2-5 digit number. The numbers are divided into
and function four tables; extensions can be allowed to use some or all tables.
Abbreviated dialing can be made semi-automatic by programming
incomplete numbers, where the extension can add digits to complete the
number. For example, when an extension in one exchange makes a Direct In-
Dialing call to an extension in another exchange, the abbreviated number to
the other exchange is used and thereafter adds the called party's extension
number.
Individual number can be made semi-automatic in the same way as described
for abbreviated dialing.
3.4.2 Account Code
User See also feature description for ACCOUNT CODE

Feature
Definition The primary purposes of the Account Code with verification are as follows:
- To ensure extensions can charge calls to an Account Code (a project,
department or client) instead of the extension's own number
- To prevent unauthorized use; the extension is forced to enter an Account Code
before dialing an external number.
Settings Account codes are set by commands from an I/O terminal.
Procedure An extension dials a procedure and the Account Code prior to the destination
and number.
function
3.4.3 Alarm Extension
User Feature
Definition The ability to have an emergency centre in the system. Alarm extensions
can be assigned to analog extensions.
Settings Alarm extensions are set by command from an I/O terminal.
Procedure and A conference is automatically established for a call to a busy alarm
function extension except for the cases below. An automatic alarm conference is not
established if:
- The alarm extension or the party connected to the alarm extension, or the
calling party, has a parked party
MX-ONE User Manual
- The alarm extension is not in speech state

- The alarm extension is involved in an ordinary Conference or another
multiparty call
Up to seven parties plus the alarm extension can simultaneously be
connected to the same alarm conference. A periodic tone message called
Conference Tone can be sent to all participants.
3.4.4 Alternative Routing
Network
Feature
Definition The ability to reach external destinations via different routes.
Settings Alternative routing and their predigits are set by command from an I/O
terminal.
Procedure Every route can have seven alternative routes. The system uses sequential
and function hunting on the ordinary route and the alternative routes, that is when the
ordinary is fully occupied, the system starts hunting in the first alternative
route and so on.
The system can add and discriminate programmed predigits, that is, if a
route to another PBX is fully occupied and the call has to be switched via
the PSTN, the system adds the extra digits needed.
A maximum of 20 predigits can be added to each alternative route, and the
total code may not consist of more than 34 digits.
3.4.5 Analog Extensions
User Feature
Definition Extension with loop interface for connection of analog phones and
fax machines.
Settings Analog extensions are set by command from an I/O terminal.
Procedure and
function
3.4.6 Authorization Code
User See also feature description for AUTHORIZATION CODE FOR

Feature EXTENSION
Definition There are two types of authorization codes available to control or limit access
to an extension.
MX-ONE User Manual
Common Authorization Code

This code does not have to be affiliated with any directory number in the
system, but it can be limited to one extension. The code cannot be changed
by the user. Two different functions are provided:
- Locking/unlocking an extension. When locked, a lower common category
code or common service profile is used.
- Authorization code dialing. This enables the calling party to use other
categories or service profiles than those with which the extension is
programmed.
Individual Authorization Code
This code is always affiliated to a directory number in the system. In addition
to the functions available to common codes, individual codes also allow
changing of the authorization code from the phone. This enables the
authorization code user to change the code when required.
Settings Authorization codes are initiated by commands from an I/O terminal.
Procedure The user dials the allocated feature code.
and function
3.4.7 Callback, Busy Extension/Call completion
User
Feature
Definition The ability of an extension to initiate supervision on a busy extension, and be
automatically rung when the dialed extension becomes free.
Settings The Class of Service (CoS) code is set by command from an I/O terminal.
Procedure The calling party dials a suffix digit when the busy tone is received. A
and function confirmation tone is sent to acknowledge the supervision. Both parties are
supervised and, whenever concurrently free, a connection is established. The
calling party is rung with a special Callback ringing signal. If the calling
party does not answer within a predefined time, the supervision is cancelled.
Cancellation of a Callback order is done via a procedure from the phone.
3.4.8 Callback, Busy Outgoing Lines
User
Feature
Definition The ability of an extension to initiate supervision on a busy route and be
automatically rung when an external line becomes free.
Settings The CoS code is set by command from an I/O terminal.
Procedure The extension dials a suffix digit when the busy tone is received. The dial
MX-ONE User Manual
and function tone is sent to the extension which now dials the route number plus all or part
of the external number completed by #, and replaces the handset. The
extension is rung, if free, when an external line becomes free and all the
digits dialed except the last. The last digit is sent when the extension answers
the Callback. If the extension does not answer within a predefined time, the
supervision is cancelled. Cancellation of a Callback order is via a procedure
from the phone.
3.4.9 Callback, No Reply/Call completion
User
Feature
Definition The ability to establish supervision of an extension that does not answer a
call.
Procedure Supervision is established when the calling extension dials a suffix digit
and function when the ringing tone is received. Both parties are supervised. The calling
party is rung with the Callback signal as soon as the called party replaces the
handset after having used the phone. Callback is cancelled with a procedure
from the phone.
3.4.10 Callback, Not Available/Call completion
User
Feature
Definition The ability of an extension in one system to initiate supervision of an
unavailable extension in another exchange, and to be rung automatically
when the called extension becomes available and free.
Procedure An extension which has called an unavailable extension in a terminating
and function exchange can, while receiving busy tone, initiate Callback/Call Completion
by means of a suffix digit. When the supervised party becomes free, the
calling party is called back. When the calling party answers, ringing starts at
the called party.
3.4.11 Call Information Logging
System See also feature description for CALL INFORMATION LOGGING

Feature
MX-ONE User Manual
Definition The MX-ONE Telephony System provides data for all types of calls. Data
records for the calls are generated in the Telephony Server and, after the end
of the call, the required data is output to a peripheral unit over a special
channel. Abandoned incoming trunk calls due to no answer are also
registered. Possible peripheral units are:
- Printer for direct printout.

- Post processing equipment, for example, a computer.
- Storage media for external processing.
The following data is logged into internal data records:
- Time at start of call
- Time at end of call
- Call duration
- Date
- Number of meter pulses, if a pulse receiver exists.
- Identity of calling party (extension or operator directory number), incoming
external line number or, if an authorization code has been entered, the
extension number affiliated to the code.
- Dialed external line route number.
- Selected external line route number.
- Dialed number (maximum 20 digits).
- Address of answering party (when it deviates from dialed number).
- Queue time to operator
- Information status for call (type of call)
- Account code
- Authorization code
- External line, call direction, incoming/outgoing
- Route access code for selected route
- Ring time duration
- Queue time duration
- Information status for call (type of call)
- Account code
- Authorization code
- External line, call direction, incoming/outgoing
- Route access code for selected route
- Ring time duration
- Queue time duration
Settings The fields to be included in the output can be defined by Command from I/O
interface. Also, the call criteria (that is, which types of calls should be logged)
may be set.
Procedure It is possible to define different output criteria.
and function
3.4.12 Calling Line Identity

MX-ONE User Manual
User Feature
Definition Automatic transfer of the calling party's number to the called party's
exchange.
Settings -
Procedure and During call set up the calling party's number is transmitted automatically to
function the called party's exchange. The caller may initiate Number presentation
restriction for an individual call.
3.4.13 Call List (Call log)
User Feature
Definition A list of the calls, both the incoming and outgoing for IP phones.
Settings -
Procedure and The user can browse through all calls, incoming missed calls, incoming
function answered calls and outgoing calls. The user can initiate a call to any entry
in the call list.
3.4.14 Call Metering/Charging
System Feature
Definition The ability to detect, store and read stored metering pulses from a public
exchange.
Settings The metering routes and lines are set by command from an I/O terminal.
Procedure and External lines (ISDN) can receive metering information from the public
function exchange. The cost/metering pulses are stored per extension.
3.4.15 Call Pick-up, Individual
User Feature
Definition The ability of an extension to answer a call to any other extension from
their own phone.
Settings -
Procedure and A call to an extension can be answered from any phone by dialing the
function extension number followed by a suffix digit when the busy tone is
received.
3.4.16 Call Pick-up, Group

MX-ONE User Manual
User See also feature description for EXTENSION GROUPS

Feature
Definition The ability of a member of a defined group to pick up a call to another
member in the group.
Settings The initiation of groups and alternative answering groups (if any) is done by
command from an I/O terminal.
Procedure Calls to one extension within a group can be answered by any other group
and function member by dialing a service code. Each group can have four alternative
answering groups and, if no calls to its own group exist, calls to the
alternative groups are answered with the same procedure. It is not possible to
answer Callback to another party member, nor is answer permitted if both
calling and answering parties have a parked party. If the same procedure is
used for an Answer Group, the stated order of priority applies for all calls to
these facilities.
3.4.17 Call Waiting/Call offer
User Feature
Network
feature
Definition The ability of an extension or the centralized operator to send an audible
indication that an internal or external call is waiting.
Call offer from a centralized operator is only applicable if ISDN ISO-QSIG
or H.323 signaling is used in the private network.
Settings The ability to send and receive a Call Waiting tone is given individually by
CoS and set by command from an I/O terminal.
Procedure A calling extension initiates Call Waiting Indication by dialing a suffix
and function digit. Call Waiting Indication is automatically sent on calls routed via the
centralized operator or on Direct In-Dialing lines, if this is programmed.
The ring tone is sent for 30 seconds to the calling party and the extension
can during this time answer the waiting call by terminating, parking or
transferring of the ongoing call.
3.4.18 Camp on Busy
Operator
Feature
Definition The ability of the centralized operator to camp on a call to a busy extension.
Settings -
MX-ONE User Manual
Procedure The operator extends the call in the normal way and the waiting call is
and function indicated to the called party. The call is connected automatically to the
extension when the call in progress has finished. The call is routed back to the
operator if not answered within 60 seconds. The operator may camp several
calls on the same busy extension. On a call to a busy extension in the
network, a check is made to verify if the incoming external line category
permits network services and if the external originating party is an operator.
If so, the call is camped on in the terminating exchange. When an operator
with a connected party calls a busy extension in the terminating exchange, a
message is provided stating whether extending of the connected party is
possible.
3.4.19 Choice of Language
User Feature See also feature description for CHOICE OF LANGUAGE .

Definition The purpose of the Choice of Language feature is to allow every user of an
Ericsson IP phone to select the language in which the text messages appear.
The phone user can select one of ten available languages by dialing a
procedure from the phone. The system administrator can specify the
language for the IP terminal from the ten available languages or set it as the
exchange language.
Settings The language of text strings shown on the IP phone's display can be selected
on a per-user basis.
Procedure Any user can change the language for the extension by dialing a procedure
and function from that particular terminal.
There is a separate set of eight special characters per language. The system
administrator can define and view the special characters in any of the
languages.
3.4.20 Class of Service (CoS) or Common Service Profile (CSP)
System CoS for Analog extensions, CSP for generic extensions.

Feature
Definition The ability to give every extension an individual CoS code that is equal with
allowed or denied types of calls and/or facilities.
Procedure The CoS code consists of common classes and individual classes. Common
and function classes are assigned as system parameters and affect all extensions in the
system. Individual classes are given per extension and open up or close the
MX-ONE User Manual
possibility of using facilities, for example, Intrusion.
3.4.21 Common Public Directory Number
System
Feature
Definition An ISDN connected public exchange receive the identity of connected A-
party in the calling party number.
The identity is used for charging in the public exchange.The public
exchange does not check the received A-party identity.
To avoid charging the wrong subscriber the identity of A-party must be
included in the number series the system has been assigned in the public
exchange.
The common public directory number is used when an extension number is
not allowed to be transmitted to the public exchange, and when charging is
to be carried out on a common number.
Settings The common public directory numbers are set by command from I/O
terminal.
Procedure and
function
3.4.22 Conference
User See also description for CONFERENCE

Feature
Definition The ability to establish Conference calls with 3 - 8 parties.
Settings The number of permitted participants are set by command from an I/O
terminal.
Procedure This type of Conference call can either be set up by an extension or by the
and function centralized operator, provided the category of participants allows Conference
calls. The participants can be an internal party, a private network party or an
external party in any combination within the limitations stated above .
A warning tone is issued to all participants at regular intervals during the call.
The warning tone can be turned on/off from the command line interface.
Only the Conference leader in an extension initiated Conference can use the
Inquiry and Refer Back feature, and receive Call Waiting Indications during
the Conference. The Conference leader can, by using the Inquiry and
Intrusion feature on one of the participants, temporarily place both parties
outside the Conference. One or both can return to the Conference depending
on the procedure used by the Conference leader.
MX-ONE User Manual
3.4.23 Connected Line Identity
User Feature
Definition Automatic transfer of the connected party's number to the called party's
exchange.
Settings -
Procedure and During call set up the connected party's number is transmitted
function automatically to the calling party's exchange. The caller may initiate
Number presentation restriction for an individual call.
Example: After transfer and when a Conference has returned to a two-party
conversation the remaining parties are updated with the correct number
information.
3.4.24 CSTA
System See also feature description for COMPUTER SUPPORTED

Feature TELECOMMUNICATIONS APPLICATIONS (CSTA) , CS
Definition CSTA is an application protocol that enables a computer domain to
communicate with a telephony domain.
When a call arrives, a message is sent from the MX-ONE Telephony System
to the computer to inform it of the event. The message contains information
such as which extension received the call, who is calling and which number
was dialed. The computer typically uses this information to perform a
database search and initiates a call set up in the MX-ONE Telephony System.
Settings The CSTA interface is set up by command from an I/O terminal.
Procedure -
and
function
3.4.25 Customer Group
System See also operational directions for CUSTOMER GROUP

Feature
Definition An MX-ONE Telephony System can consist of a number of customers who
can be completely separated with regard to telephony. The customers are
arranged in one customer group. The MX-ONE Telephony System only
supports one customer group.
Settings Customers are initiated by command from an I/O terminal.
Procedure Each customer virtually has their own system. Customers within the
MX-ONE User Manual
and function customer group can have their own resources, such as routes and operator
groups at the Main site, but also have features for utilizing common system
resources within the customer group.
3.4.26 Customer Identity Storage
User Feature
Definition This feature allows a Customer Identity to be associated with an external
caller (customer).
Settings -
Procedure The identity may be received automatically, or manually entered by the
and function calling party using the DTMF keypad. If the call is transferred, for instance
via a voice server, the Customer Identity is transferred with the call.
3.4.27 Direct-In Dialing
System
Feature
Definition The incoming external line (PSTN) calls can be routed directly to extensions
with Direct In-Dialing.
Settings Type of signaling indication of origin and rerouting in certain traffic cases
are set by command from an I/O terminal.
Procedure The extension number is transmitted from the public exchange. The digits
and function are analysed to find out whether the extension has a CoS that allows Direct
In-Dialing.
NOTE: The call can be rerouted (for example, to a centralized operator who
gets information about the dialed number and reason for rerouting) if
congestion occurs, or if the extension is not answered, busy, vacant, blocked
for Direct In-Dialing or in line-lockout state.
3.4.28 Diversion, Busy
User Feature See also feature description for CALL DIVERSION

Definition The ability of an analog extension with Individual Diversion to have calls
diverted when busy.
Settings The CoS code set by command from an I/O terminal.
Procedure and Diversion is activated and cancelled by the extension or the centralized
function operator.
MX-ONE User Manual
Diversion can be activated automatically at the initiation of an Individual

Diversion position. Calls to a busy analog extension with Individual
Diversion are diverted to the answering position.
3.4.29 Diversion, Bypass

Definition The ability to bypass the diversion state.
Settings -
Procedure and The answering position can always reach the diverted extension by
function dialing the diverted number.
An extension that has a CoS code allowing Intrusion is also allowed to

use Diversion Bypass.
3.4.30 Diversion, Common

Definition The ability of an extension to have calls diverted to a common
answering position.
Settings The CoS code and the allocation of an answering position is done by
Procedure and Diversion is activated and cancelled by the extension, the answering
function position or the centralized operator.
A diverted extension that initiates a call receives a special dial tone to
indicate that the diversion state prevails.
3.4.31 Diversion, Direct

Definition The ability of an extension temporarily to move incoming calls to another
(extension) position or centralized operator.
Procedure and Diversion is activated and cancelled by the extension or the centralized
function operator. The diversion destination is set from the command line interface.
Diversion can be activated automatically at the initiation of an Individual
Diversion position.
Calls to a free or busy extension with Direct Diversion are diverted to the
answering position.
MX-ONE User Manual
3.4.32 Diversion, Individual

Definition The ability of an extension to have calls diverted to an individual answering
position.
The answer position selection can be dependent on call origin (public,
private, internal) and the call is then diverted to either the individual
position or to the common position specified for that origin.
Settings The CoS code and the allocation of answering positions is done by
Procedure and Diversion is activated and cancelled by the extension, the answering
function position or the centralized operator.
A diverted extension that initiates a call receives a special dial tone to
indicate that the diversion state prevails.
3.4.33 Diversion, No Reply
User See also feature description for CALL DIVERSION

Feature
Definition The ability of an analog extension with Individual Diversion to have calls
diverted on No Reply.
Settings The CoS code and set by command from an I/O terminal.
Procedure A call to an analog extension with Individual Diversion that is not answered
and function within 14 seconds is diverted to the answering position. Subsequent calls are
diverted after 8 seconds provided the extension has not initiated a call in the
meantime.
3.4.34 Diversion, Origin
System See also feature description for CALL DIVERSION

Feature
Definition The ability of analog extension users to divert their calls to different
answering positions depending on the origin of the call, that is, if it is an
internal, external, or private network call. For IP extensions, the personal
number feature is used for diversion on origin.
Settings The function uses common or individual diversion numbers and an extension
CoS, which is set by command from an I/O terminal.
Procedure Calls to an extension which has Diversion On Origin can be diverted to three
and function different numbers depending on the origin type.
MX-ONE User Manual
Diversion can also be avoided for example for one origin. The normal
diversion procedures are valid.
3.4.35 DNIS for ACD
System See feature description for DNIS FOR ACD

Feature
Definition This service which provides the ability for the CTI groups to identify
different customers based on the number the customer is dialing.
When the call is presented the DNIS number and name are displayed together
with the calling party number and name. Each DNIS number is stored
together with its affiliated name and CTI-group number. An incoming DNIS
call fetches its stored name and the call is sent to its specified service group
number. When the call is presented to the receiver, the DNIS number and
name are presented.
Settings The DNIS numbers are initiated by command from an I/O terminal.
Procedure -
and function
3.4.36 Do Not Disturb, Group
User See also feature description for EXTENSION GROUPS

Feature
Definition The Group Do Not Disturb feature allows a master extension to mark a
group of extensions as Group Do Not Disturb, that is, calls to extensions in
the group are not signaled on the phone.
Settings Groups and group members are initiated by command from an I/O terminal.
Procedure If the extension has any diversion activated or an individual divertee
and function position, the call is diverted. If the extension has no diversion and the
incoming call is a Direct In-Dialing call which has a CoS permitting
rerouting, it is rerouted to a centralized operator.
Bypass of Group Do Not Disturb can be done with the Diversion Bypass
procedure from a master extension.
3.4.37 Do Not Disturb, Individual
User Feature
Definition The ability of an authorized analog extension to prevent calls from being
signaled at the phone set.
MX-ONE User Manual
Settings -
Procedure and An analog extension can invoke the feature by dialing a procedure. No
function further calls to the extension are permitted, but Direct In-Dialing calls are
rerouted to the centralized operator.
3.4.38 DSS1 Network side
System Feature See also feature description for DSS1 NETWORK SIDE
Definition The MX-ONE Telephony System can act as a network side of an ISDN-T
connection. This is mainly for branch office applications.
Settings -
Procedure and -
function
3.4.39 Electronic Mail
See also feature description for ELECTRONIC MAIL

Definition An electronic mail system is used for storing messages in the users' mailboxes
and for sending them to and from these mailboxes. Interworking between the
mail system and the telephony system enables waiting messages to be
announced, that is, messages that have not yet been read or printed out.
When a message has been registered in a mail system the message is signaled
to the telephony system which notifies the relevant extension. After a
message has been presented to the receiving party, or cancelled by other
means, the message system informs the sending party and the notification
ceases unless other messages to the extension are waiting to be announced.
Settings The electronic mail is set up by command from an I/O terminal.
Procedure Users with IP phones will receive an indication on a dedicated key when a
and function message has been stored.
3.4.40 Emergency Calls to Operator
User Feature
Definition A special type of incoming call to the centralized operator which is
given the highest priority.
Settings Emergency numbers must be initiated by command from an I/O
terminal.
Procedure and Extensions and tie lines can initiate calls with the highest priority by
MX-ONE User Manual
function dialing a predefined emergency number.
3.4.41 Facility Restriction Level/Travelling Class Mark (FRL/TCM)
Network
Feature
Definition Facility Restriction Level/Travelling Class Mark (FRL/TCM) is used to
restrict user access to routes in the private network.
Settings FRL/TCM is set by command from an I/O terminal.
Procedure The FRL is associated as a CoS to all users and is sent as a TCM in the
and function private network. Before a transit exchange permits a call attempt on the
chosen route, the level of the outgoing route is checked. The mark must be
greater than or equal to this level.
3.4.42 Follow-me, External
User See also feature description for CALL DIVERSION

Feature
Definition The ability of an extension temporarily to divert calls to private networks and
to the PSTN/ISDN.
Procedure An extension or the centralized operator can order and cancel the external
and function Follow-me diversion feature by use of a procedure.
Incoming calls to the extension are then diverted (rerouted) to the external
destination. However, Follow-me calls cannot be camped on to the external
destination, that is, if the external destination is busy with an ongoing call, a
subsequent call encounters a busy tone.
Metering pulses and call information logging are registered for the extension
that activated the external Follow-me.
3.4.43 Follow-me, Internal

Definition The ability of an extension to temporarily move incoming calls to another
extension position.
Settings -
Procedure and Activated and cancelled by the extension, the answering position or the
function centralized operator. The extension receives a special dial tone to indicate,
when initiating a call, that the Follow-me state is active.
MX-ONE User Manual
3.4.44 Free Seating
User See also feature description for FREE SEATING

Feature
Definition Free seating is a service that allows the user to log on to any available phone,
and get the user's personal categories, calls and messages.
When initiating the virtual generic extension for a Personal number, which
must be done for the Free-seating feature, a license for Free seating is seized.
Settings -
Procedure For IP terminals, the user logs on/off using the standard log on/off procedure.
and function
Analog extensions enter a special feature code to activate/deactivate free
seating. An individual authorization code must be used. When logged on or
activated, the user's set of function keys will be used, but only certain
functions will follow the user. Some functions, such as group hunting, are
barred. A special dial tone is used to indicate that the user is logged
on/activated.
Log off can also be done remotely from a centralized operator.
3.4.45 General Cancellation
User Feature
Definition The ability to deactivate all activated features such as Callback, Follow-
me, Message Diversion and Do Not Disturb, with only one procedure.
Settings -
Procedure and An extension can dial a procedure that erases or deactivates all services
function that have been requested by or for the extension.
3.4.46 Generic Extension
System
Feature
Definition A Generic Extension is affiliated only to a directory number.
A number of categories are affiliated to a Generic Extension. Those
categories are collected in a number of Common Service Profiles, CSP and
every Generic Extension must be affiliated to a CSP.
A virtual Generic Extension is created when a directory number with a CSP
is initiated in the MX-ONE Telephony System. When a terminal is
MX-ONE User Manual
affiliated, it is changed into the type of the physical terminal.

All extensions except the Analog extensions are Generic extensions.
Settings A Generic Extension is initiated by command from an I/O terminal.
After the basic setup has been initiated for the directory number, different
applications can be defined to affiliate this directory number to an extension
position.
Procedure and A virtual Generic Extension can be used by temporary users such as
function consultants who normally do not have a wired extension.
The number of virtual Generic Extensions is related to the number of
directory numbers and not to the physical number of terminals or positions.
3.4.47 Group Hunting
User Feature See also description for EXTENSION GROUPS

Definition A group of extensions can be called with a common number.
Settings The Hunting groups and its members are set up by command from an I/O
terminal.
Procedure and A group of extension can be called with a 2-5 digit number.
function Incoming calls are routed to a free extension in the group, either with
sequential hunting or evenly distributed. All extensions in a group keep
their own private number and CoS.
An extension can be a member of several hunting groups. An extension can
temporarily withdraw from the group by activating Follow-me to its own
phone.
Calls to a group from which all members have excluded themselves are
diverted to the group's divertee position.
3.4.48 Hot Line, Delayed
User Feature
Definition The ability of an analog extension to be connected automatically to a
predefined position after the handset has been lifted for a certain time.
Settings The connection position (address) is set per extension by command from an
I/O terminal.
Procedure Ringing is sent to the preprogrammed party (another extension, centralized
and function operator, abbreviated number, etc.) a certain time after the extension lifts the
handset. Before that time, the extension can dial as any normal extension.
3.4.49 Hot Line, Direct

MX-ONE User Manual
User Feature
Definition The ability of an analog extension to be automatically connected to a
predefined position immediately after lifting the handset.
Settings The connection position (address) is set per extension by commands from
an I/O terminal.
Procedure and Ringing is sent to the preprogrammed party (another extension,
function centralized operator, abbreviated number etc.) when the extension lifts the
handset.
3.4.50 Incoming Automatic Inter-PBX Calls
User
Feature
Network
Feature
Definition Incoming calls from other PBXes can be routed directly to an extension.
Settings Acceptance of automatic direct calls is set per route by command from an
I/O terminal.
Procedure The route can be programmed to accept calls from other private exchanges.
and function Automatic calls from other private exchanges are processed as Direct In-
Dialing calls from the public network.
NOTE: The call can be rerouted (for example, to a centralized operator that
gets information about the dialed number and reason for rerouting) if
congestion occurs, or if the extension is not answered, busy, vacant, blocked
for Direct In-Dialing or in line-lockout state.
3.4.51 Incoming Calls via Operator
Network Feature
Definition Incoming calls can be routed to the centralized operator.
Settings Setting is done by commands from an I/O terminal.
Procedure and The centralized operator receives the call and can extend it to any
function extension in the private network.
3.4.52 Information System/Interception Service
User
Feature
System
MX-ONE User Manual
Feature
Definition Message Diversion is activated by an extension procedure containing an
interception message. The interception message is sent to the connected
interception computer. All new calls to an extension which has activated
interception diversion are diverted directly to an answering position
programmed as the Message Diversion position. The purpose is to provide
answering position personnel with a better means of giving callers
meaningful interception messages.
Settings The information system/service is set up by command from I/O terminal.
Procedure The procedure for booking Message Diversion includes an interception
and function message which is sent direct to the interception computer.
3.4.53 Inquiry
User See also feature description for THREE-PARTY SERVICES

Feature
Definition The ability of an extension to park a call and make an Inquiry call.
Settings -
Procedure The original call (internal or external) is parked by the extension using the
and function procedure for Inquiry. The required number (internal, external or centralized
operator) is dialed. The parked party cannot overhear the Inquiry call.
Referral to the parked party is done by using the Refer Back procedure.
3.4.54 Internal Basic Calls
User Feature
Definition The ability of an extension to call another extension or group number.
Settings -
Procedure The extension lifts the handset and dials the required number on receipt of
and function the dial tone. If the extension fails to dial within a certain time (8 s) or the
pause between two digits exceeds a certain time (8 s), a disconnection signal
is sent.
3.4.55 Intrusion on Busy Extension
User Feature
Network
Feature
MX-ONE User Manual
Definition The ability of the centralized operator or extension user to intrude on the
conversation of an engaged internal extension or an extension within a
private network using ISDN or H.323 signaling.
Settings Both the intruder and the intruded party need a specific CoS set by
Procedure and A suffix digit is used to enter the ongoing conversation. An Intrusion tone is
function heard by all parties.
3.4.56 Intrusion with Forced Release
Network
Feature
Definition The ability of an centralized operator, after Intrusion, to force release the
third party.
Settings -
Procedure and The centralized operator can force release the third party by pressing the
function Intrusion key once more. Forced release cannot be initiated earlier than one
second after Intrusion.
3.4.57 IP Extension
User Feature See also feature description for IP EXTENSION

Definition The IP extension is a type of terminals that is connected to the IP network.
It allows employees to work remotely and also employees at remote small
offices to connect their terminals to the system.
Settings The IP Extension is set up by command from I/O terminal.
Procedure and -
function
3.4.58 IP Networking
Network See also feature description for IP NETWORKING

Feature
Definition The IP networking feature allows multimedia communications between an
MX-ONE Telephony System and other H.323 compliant systems (even from
other vendors), making use of the IP network to transmit the media.
Settings The IP networking feature is set up by command from an I/O terminal.
Procedure IP networking allows that an MX-ONE Telephony System can be connected
MX-ONE User Manual
and function through the data network to remote PBXes in multi-site organizations (tie
lines, VPN), to PBXes of other organizations or to the public IP network.
The IP network uses TCP/IP as the underlying protocol and therefore the
voice is converted into packets in order to be transmitted via the IP network,
and then unpacked in the other end. The use of the IP network to transmit
voice may reduce transmission costs, and allows the transmission of different
media (voice, video, data).
3.4.59 ISDN Networking
Network See also operational directions for NETWORKING

Feature
Definition ISDN networking allows communication between an IP PBX and other
PBXes using QSIG signaling. The connection requires ISDN E1
connections between the systems to be connected.
Settings The ISDN networking is set up by command from an I/O terminal.
Procedure and ISDN networking allows that a telephony system can be connected through
function leased lines to remote PBXes in multisite organisations or to PBXes of
other organisations.
3.4.60 Last External Number Redial
User Feature
Definition Dialed external numbers are automatically stored and can be re-transmitted
by the extension using a simple code.
Settings -
Procedure and All outgoing external numbers from each extension are stored. A stored
function number is erased when a new external number is dialed. The extension uses
a certain code to re-transmit the stored number.
3.4.61 Least Cost Routing
System See also feature description for LEAST COST ROUTING

Feature
Definition Least Cost Routing allows the system to select the most economical route
for an outgoing public call. Least Cost Routing numbers are programmed
from the command line interface.
Function
MX-ONE User Manual
Least Cost Routing performs analysis of the dialed number including the
Least Cost Routing access code and attempts to route the call over the most
economic available route at any time based on the following:
- external line availability
- user's Routing CoS
- user's Trunk Call Discrimination CoS
Time of Day
Least Cost Routing, Time of Day is a function that allows the system to
make the selection of the most economical route for an outgoing call
dependent on the time of day and the day within the week.
This means that it is always possible to select the most economical route
even if the cost relations between the different routes vary with the time of
day and day within the week.
Expensive route warning tone

A special tone is returned to the calling party when a call is overflowed to
an alternative route which is marked as expensive.
Settings The Least Cost Routing tables are set up by command from an I/O terminal.
Procedure and -
function
3.4.62 Malicious Call Tracing
User Feature
Definition The ability of an analog extension, who is or has been participating in an
incoming public ISDN call, to request tracing of a malicious call, for
example, a bomb threat.
Settings The extension CoS code is set by command from an I/O terminal.
Procedure and The feature is requested by putting the call on hold, and then dialing a
function procedure. The request to trace is sent to the public network which
performs the actual tracing.
3.4.63 Manual Message Waiting (MMW)
User Feature
Network
Feature
Definition The ability of an extension or centralized operator manually to notify an
extension that a message is waiting.
Settings An extension CoS code is set by command from an I/O terminal.
MX-ONE User Manual
Procedure and The feature is requested by dialing a specific procedure or pressing the
function MMW key. The destination extension then switches on the Message
Waiting Indication.
When the extension which received the indication becomes aware that there
is a waiting message, a call can automatically be set up back to the party
who requested the MMW indication.
3.4.64 Message Diversion
User
Feature
Definition An individual or common diversion position must be chosen as the Message
Diversion position, which is also used for Direct Diversion. An extension,
group hunting group number, a line pick-up group, a centralized operator may
be used as the Message Diversion position.
Message Diversion is activated and cancelled either from the interception
terminal or by a procedure from the extension.
Settings The meaning and syntax of the Message Diversion messages can be changed
by command from an I/O terminal.
Procedure Message Diversion is activated by an extension procedure containing an
and function interception message, which is sent to the connected interception computer.
All new calls to an extension that has activated interception diversion are
diverted directly to an answering position programmed as the Message
Diversion position. The purpose is to provide answering position personnel
with a better means of giving callers meaningful interception messages.
Prerequisite for use of Interception Services: An external interception
computer is connected to the MX-ONE Telephony System via the General
Information Computer Interface (GICI).
3.4.65 Message Waiting
User
Feature
Definition A function for notifying an extension of messages that have not yet been read
or recorded and which are stored in one or several information systems.
An information system consists of a peripheral unit that is connected to the
MX-ONE Telephony System by way of the GICI.
Settings -
Procedure The Message Waiting function can be used by several information systems
and function connected in parallel to the system. An information system can be in the form
of an interception computer, a Voice Mail system, or a text message system.
MX-ONE User Manual
The function can be introduced even if not all information systems connected
are capable of handling the signaling required for Message Waiting.
When a message has been registered in an information system, it is signaled
to the MX-ONE Telephony System, which then notifies the relevant
extension.
After a message has been presented to the receiving party or cancelled by
other means, the message system informs the sending party and the
notification ceases unless other messages to the extension exist.
3.4.66 Message Waiting Indication (MWI)
User Feature
Definition The ability of an extension to receive a Message Waiting Indication, MWI,
in the form of an LED, a display message, or a special dial tone at Off-
hook, depending on type of extension.
Settings An extension CoS code is programmed with command from an I/O
terminal.
Procedure and The feature is requested by an interception computer system for a particular
function extension when there is at least one message waiting for that extension
user.
3.4.67 Music on Hold/Wait
System See also feature description for RECORDED VOICE

Feature ANNOUNCEMENT
Definition Music on Hold is a feature for providing sound, such as music or marketing
information, for example, to a parked or queued subscriber or extension.
The sound files are stored in memory.
Music on Hold/Wait is not available to centralized operators or for calls
queued to centralized operator.
Settings The Recorded Voice Announcement feature is used for Music on
Hold/Wait.
Procedure and -
function
3.4.68 Name Identity
User See also feature description for NAME IDENTITY .

Feature
MX-ONE User Manual
Definition The Name Identity function is used to associate an easily recognizable name
with various individual items that are normally identified in the system by a
number. The function is also useful when applied to incoming and outgoing
external calls where the external number exceeds the length of the field
reserved for it in the display. The calling/connected Name Identity function
allows the assignment of a name to the following individuals:
- Analog extension (primary and secondary)
- Hunt Groups
- Ericsson IP terminals
The function also allows the name associated with an individual to be

conveyed through the system, together with its number, so that both the
number and name are displayed together. The Name Identity of the parties
involved in a call is transferred. For external calls this is by way of an ISDN
private or public network.
Settings The names are set with command from an I/O terminal
Procedure -
and function
3.4.69 Night Service
System Feature
Definition Incoming calls during the night are routed to pre-programmed answering
positions.
Settings Type of Night Service and the assignment of answering positions are set
by command from an I/O terminal at the Main site.
Procedure and Night Service is activated at the Main site.
function
3.4.70 Number Analysis/Number Series
System See also operational directions for NUMBERING

Feature
Definition The ability to analyse dialed or received numbers and feature codes,
including separators.
Settings Number series are initiated and changed by command from an I/O terminal
Procedure and When a user makes a call, or when certain features are executed, the dialed
function or received digits or characters are analysed regarding number type, length,
and range.
MX-ONE User Manual
3.4.71 Number Conversion and Bearer Capability Substitution
System
Feature
Definition Number Conversion and Bearer Capability Substitution are services that
perform conversion of sent and received numbers and of Bearer capabilities
and Teleservices from database tables.
Settings The database contents and route CoS are initiated from an I/O terminal.
Procedure Calls that need number conversion or bearer capability substitution, this is
and function done automatically by the system. The functions may be useful for example
when an ISDN network shall interwork with another network. ISDN Type Of
Number is used to determine how the conversion shall be done.
3.4.72 PBX Operator
Network Feature See also operational directions for PBX OPERATOR TRAFFIC
Definition The branch node does not have an operator but uses the centralized
operator in the Main site.
Settings Functions in the IP PBX for the centralized operator is set by
commands from I/O terminal.
Procedure and -
function
3.4.73 Original A-Number
System
Feature
Definition The Original A-number feature allows the diverted to party (the C-party) to
see the calling party's (the A-party's) number in the following cases: The B-
party has external follow me to the C-party activated. The C-party is an
answer position in the B-party's active list for personal number.
Procedure -
and function
3.4.74 Outgoing Automatic Call
User
MX-ONE User Manual
Feature
Definition The ability of an extension to make outgoing calls without assistance from
the centralized operator
Procedure The extension dials the route access code and normally, on receipt of a dial
and function tone, the wanted external number. A supervisory tone is sent after the route
access code if the extension is barred from making outgoing calls or using
the route access code.
3.4.75 Outgoing Call via Centralized Operator
User
Feature
Network
Feature
Definition The ability of an extension in a sub-exchange to make an outgoing call with
assistance from the centralized operator
Settings -
Procedure For this traffic case, three sub-cases can apply:
and function - The extension replaces the handset after ordering the call. The extension in
the sub-exchange dials the centralized operator access code. After ordering
the call, the extension replaces the handset. The centralized operator dials the
required number, awaits answer, calls the extension, awaits answer, and
finally extends the call.
- The extension does not replace the handset after ordering the call. The
centralized operator dials the required number and extends the call without
the extension having to replace the handset.
- The centralized operator extends the call with dial tone. The centralized
operator dials the route access code, awaits dial tone from the called
exchange, and extends the call, that is, allows the extension to dial the actual
destination.
3.4.76 Parking with Individual Call Pick-Up
User
Feature
Definition The ability to park a call and pick it up from any analog phone
Settings -
MX-ONE User Manual
Procedure The extension uses the procedure for Inquiry and goes On-hook to park the
and function call. The call can be picked up from any other analog phone by dialing the
extension's number, followed by a suffix digit. If the call is still parked after
30 seconds, the extension's phone starts ringing.
3.4.77 Path Replacement
Network
Feature
Definition Path replacement (ISO-QSIG) is carried out in certain situations when, for
example, transfer or alternative routing has occurred, in order to facilitate
better utilization of the lines in a network.
Settings The Path replacement parameters have to be set up with command from an
I/O terminal.
Procedure and Path replacement is carried out after a network call has been answered. A
function new optimum route between the parties is selected, the parties are re-linked,
and the original route is disconnected.
3.4.78 Personal Number
User See also feature description for PERSONAL NUMBER

Feature
Definition General
A Personal Number is an extension directory number with a terminal of any
type assigned, which has the Repeated Deflection service available. The aim
of Personal Number is to provide system users (voice extensions) with
different possible answering positions for the incoming calls.
Features
The Personal Number service has the following characteristics:
Every Personal Number can have up to 5 different lists available, but only
one of them can be active.
Each list can be set up with up to 10 different answering positions that are
selected depending on the user location (for example, at the office, at home).
The user can activate and deactivate the service or change the active list by
way of a procedure.
MX-ONE User Manual
When the Personal Number service is activated, incoming calls to the

Personal Number are deflected to the positions in the active list, until the call
is answered or is stopped for any reason. When the Personal Number service
is not activated, all incoming calls to the Personal Number are distributed to
the assigned terminal as in a normal call. The settings of the personal number
can be done automatically depending upon calendar and location information
stored for the user.
Settings Personal numbers and list entries are programmed by command from an I/O
terminal.
Procedure The user can chose the Profile by means of a procedure. The user with web
and function interface can also add a new profile or adjust an existing profile.
3.4.79 Priority Routing
Network
Feature
Definition It is possible to classify circuits within a route, or a whole route, with respect
to permitted access from an extension or an incoming external line. A
specific CoS, routing access, is associated with extensions, external lines, and
operators. This information is used when selecting an outgoing circuit in the
own system and is sent forward with the call request.
Settings The Priority routing is set by command from an I/O terminal.
Procedure -
and function
3.4.80 Private Network Routing
Network See also operational directions for NETWORKING

Feature
Definition The feature provides high capacity routing and Number Conversion capabilities
for the private network based on ISDN ISO-QSIG or H.323 signaling. A number
of the network features are proprietary to MX-ONE Telephony System and ASB
501 04.
Settings Private network destinations and their required individual number translations
can be set by command from an I/O terminal.
Procedure Functions as a preprocessor to the basic routing software. Alternative routing is
and performed based on the dialed number, which is compared with entries in the
function Private Network Routing database. If the route choice is specified to use
individual translation, the translation number is fetched from the Private
Network Routing database.
MX-ONE User Manual
3.4.81 Recall to Operator
Operator
Feature
Definition Extended calls by the centralized operator that is not answered within a
certain time recall the centralized operator
Settings The times before recall can be changed by command from I/O terminal.
Procedure and Extended calls by the centralized operator that is not answered within a
function certain time recall the centralized operator
3.4.82 Recorded Voice Announcement
System See also feature description for RECORDED VOICE

Feature ANNOUNCEMENT
Definition The Recorded Voice Announcement (RVA) feature allows announcements to
be supplied to incoming calls to a centralized operator (operator
announcement). It also allows announcements to be supplied to a calling
party for the following call cases:
- Called party has activated Follow-me
- Called party has activated Direct Diversion and Diversion on Busy to an
extension
- Called party has activated external Follow-me
- Called party is an Group Hunting Group
- The call is placed in a Group Hunting Group or operator queue for a spec-
ified amount of time.
- Vocal guidance for analog extensions when the caller encounters certain
traffic cases.
When there is no available RVA resource in an announcement group, the call
is still processed, but no voice announcement is supplied to the call-ing party.
Settings The allocation of the recorded messages is set by command from an I/O
terminal.
Procedure -
and function
3.4.83 Refer Back
User Feature See also feature description for THREE-PARTY SERVICES

Definition The ability of an extension in Inquiry mode to refer back and forth between
the inquiree and the original call. The connected/parked party can be an
internal party, a party in the private network or an external party.
MX-ONE User Manual
Settings -
Procedure Every time the extension wants to alternate an Inquiry call, the Refer Back
and function procedure is used.
3.4.84 Release Principles
System
Feature
Definition First party release
An established connection is released when either the calling or the called
party terminates the call.
Calling party release
An established connection is released when the calling party terminates the
call.
Called party release
An established connection is released when the called party terminates the
call.
Settings Route setting by command from an I/O terminal.
Procedure First party release
and function When any party goes On-hook (or equivalent action) the connection is
automatically released. The remaining party is given busy tone.
Calling party release
When the calling party goes On-hook first the connection is released
automatically. The called party, if still remaining, is given busy tone. If the
called party goes On-hook first the connection remains. Time supervision is
started in the calling party's exchange. If the called party goes Off-hook
before the time supervision expires, speech connection is again established. If
time supervision expires, the connection is released.
Called party release
When the called party goes On-hook first, the connection is released
automatically. The calling party, if still remaining, is given a busy tone. If the
calling party goes On-hook first, the connection remains. Time supervision is
started in the called party's exchange. If the calling party goes Off-hook
before time supervision expires, speech connection is again established. If
time supervision expires, the connection is released.
3.4.85 Repeated Diversion

Definition Repeated Diversion is a set of rules that determines how Call Diversion
and Follow-Me can be combined.
MX-ONE User Manual
Settings -
Procedure and -
function
3.4.86 Rerouting
System
Feature
Network
Feature
Definition When a call from an external line encounters Congestion, Vacant Number,
Busy, Not Available, or No Reply, it is possible to program routes or
individual external lines for rerouting to an answering position.
Settings Rerouting is set by command from an I/O terminal.
Procedure Depending on the incoming route category, when a call encounters
and function Congestion, Vacant Number, Busy, Not Available, or No Reply, a decision is
made as to whether the call is to be rerouted. Different rerouting numbers can
be set for a day or night switched system. Different rerouting numbers can be
set per customer in the customer group. The function can be networked.
3.4.87 Routing, Alternative Routing
Network
Feature
Definition The ability to reach external destinations by way of different routes.
Settings Alternative routing is set by command from an I/O terminal.
Procedure The system uses sequential hunting on the ordinary route and the alternative
and function routes; that is, when the ordinary is fully occupied, the system starts hunting
in the first alternative route, and so on.
The system can add and discriminate programmed pre-digits; that is, if a
route to another PBX is fully occupied and the call has to be switched by way
of the PSTN, the system adds the extra digits needed. A maximum of 20 pre-
digits can be added to each alternative route, and the total code may not
consist of more than 34 digits.
3.4.88 Routing, Overflow
Network
MX-ONE User Manual
Feature
Definition The process of routing a call automatically via another (second choice) route
from the system when a call cannot find a free circuit in a first choice route.
There may also be overflow, at the same system, from a second choice route
to a third choice, and so on.
Settings The Routing feature is set by command from an I/O terminal.
Procedure If there are no free circuits in the requested route, overflow can occur to
and function alternative routes. In the originating system, overflow can occur to a
maximum number of seven alternative routes; that is, the originating system
permits eight choices to the requested destination.
3.4.89 Routing, Repeat Attempt
Network
Feature
Definition The process whereby another attempt to set up a connection for a call, from
the point where the first attempt took place when difficulty is encountered
in the setting up of the connection.
Procedure and A repeat attempt can be made if, for example, the seize acknowledgement
function signal is received either too early or not at all.
If the acknowledgement signal is not received at all, it is interpreted either
as a line fault or that the seized exchange is unable to respond to the seize
signal.
3.4.90 Routing, Return Block
Network Feature
Definition An exchange is not permitted to route the call to another circuit in the
route from which the call originated.
Procedure and -
function
3.4.91 Serial Call
Operator
Feature
MX-ONE User Manual
Definition The ability of the centralized operator to regain an external call when the
called party terminates the call.
Settings -
Procedure Incoming and outgoing external calls can be serial call marked by the
and function centralized operator. When the not serial call marked party terminates the
call, the centralized operator is recalled. If the serial call marked party
terminates the call the centralized operator is not recalled or informed.
3.4.92 Suffix Dialing (End-to-End DTMF)
User Feature
Definition The ability of an extension in speech state to dial suffix digits/characters,
for example, to control an external equipment.
Settings How the suffix dialing shall be treated is set by command from an I/O
terminal.
Procedure and The feature is automatically available to analog extensions and IP
function terminals in speech.
3.4.93 Traffic Connection Matrix
System
Feature
Definition A check is made in the system to verify that the interconnection of two
parties is permitted. The parties may be extension, group hunting group,
conference equipment, or external line. The check is done in a 16x16 matrix.
Settings The matrix is programming by command from an I/O terminal.
Procedure -
and function
3.4.94 Traffic Recording
System
Feature
Definition Traffic recording of a number of different measurement objects, for example,
voice extension or route, can be initiated. The maximum number of ongoing
measurements in parallel is 250. For each measurement a measurement result
is obtained that is stored in the program memory and also on a storage unit.
The collection of measurement data from the measurement objects is initiated
automatically at each quarter of an hour. The measurement result can be
MX-ONE User Manual
printed out on a printer terminal.

A congestion monitoring value can be initiated/altered for the objects route
group.
A special type of the traffic recording is performed for the Least Cost Routing
(LCR) facility. Traffic recording for LCR cannot be initiated, interrupted or
removed. It is active all the time and used counters are updated automatically
and reset during a system reload as well as after each printout.
Settings Traffic recording is initiated by command from an I/O terminal.
Procedure -
and function
3.4.95 Transfer/Call Transfer
User Feature See also feature description for THREE-PARTY SERVICES

Network
Feature
Definition The ability of an extension to transfer a call to another party in own system
or in another connected system, centralized operator or external line. The
function Call transfer is only available within an ISDN QSIG or H.323
private network
Settings Whether transfer to trunk and transfer before answer are permitted or not is
set by command from an I/O terminal.
Procedure The extension first initiates an Inquiry call, and when the call is established
and function the Transfer procedure is used.
3.4.96 Transit Counter
Network
Feature
Definition A transit counter is used in ISDN/H.323 networks in order to prevent call
being routed in loops.
Settings The number of allowed transit exchanges can be set by command from an
I/O terminal.
Procedure and For each route a value can be set that defines the maximum number of
function transit exchanges, a call can be routed through in order to reach its final
destination.
3.4.97 Transit Traffic

MX-ONE User Manual
Network
Feature
Definition The ability to transit switching in the exchange.
Settings The route programming is set by command from an I/O terminal.
Procedure and Incoming external line calls can be switched to other external lines,
function either automatically or by the centralized operator.
3.4.98 Trunk Call Discrimination (TCD)
System
Feature
Definition The ability to block extensions primarily from calling certain parts of the
public network
Settings Each extension can be initiated for call discrimination with one of 15 possible
categories for day traffic and 15 possible categories for night traffic. A
number table is also programmed for the 15 categories. Settings are made by
Procedure An extension is assigned to one of 15 possible categories for verifying dialed
and function digits on outgoing calls. Extensions can be assigned separate categories for
day and night switched systems. The check can continue for up to ten dialed
digits and include internal as well as outgoing external destinations. If an
extension attempts to call a forbidden number a tone message is received and
thereafter the call is placed in the line lockout state.
3.4.99 Voice Mail
System Feature
Definition Allows callers to leave messages for users that are not available to
answer a call. The Voice Mail must be located at the Main site.
Settings Calls to be routed to the centralized Voice Mail is set up by command
from an I/O terminal.
Procedure and The user accesses the Voice Mail to retrieve messages via phone using a
function procedure.

MX-ONE User Manual

Uploaded by

Copyright:

Available Formats

MX-ONE User Manual

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MX-ONE User Manual

Uploaded by

Copyright:

Available Formats

MX-ONE User Manual

MX-ONE User Manual

- MX-ONE Telephony System Description

MX-ONE Telephony System Description

3 Operation and Maintenance

4 Terminals and End User Equipment

Figure 2-1. Architectural overview

2.2.1 MX-ONE Telephony System

The MX-ONE Telephony System is composed of a Telephony Server and a Media

2.2.2 End-user Terminals

2.2.3 Networking Capabilities

3.1 Telephony Server

The Telephony Server consists of software loaded on a standard server platform. It

• The telephony applications

• The service system

Middleware that interfaces the telephony applications. For a detailed

• The Linux operating system

Figure 3-1. Telephony Server

3.1.2 Service System

• Start and restart of the Telephony System

3.1.2.1 Start and restart of the Telephony System

• Loading or starting program units

Each stated program unit is restarted.

• Virtual device boards

The restart is carried out by an activation request from the device-handling

A manual restart is initiated by a command and the result is presented on the

• System configuration data

3.1.3.1 Program unit configuration

3.1.3.2 Hardware configuration

It is also possible to receive information on certain resources on the Media

3.1.4.1 Functional Change

The Functional change feature is used when a modification program package is to

• Correct errors in the software

The feature performs the following:

• Prepares the system for program unit change

3.1.4.2 System Supervision

The System supervision feature is used to:

• Control the performance of the supervised objects

Supervision of execution signals and times

If a program unit fails at restart, it is blocked for signaling.

3.1.4.3 Signal Tracing

3.2 Media Gateway

• 8 E1 interfaces (ISDN, QSIG)

The Media Gateway design is based on packet (cell) switched platform

3.2.2 Major Functions

3.2.3 Application and Networking Environment

• Green - power status

3.2.3.2 Interfaces and Resources

Ethernet and IP Interface

3.2.3.3 Interworking with Telephony Server

• Virtual board interface

For addressing, switching and controlling virtual board devices. Examples of

o Board control interface

SW-HW interface used for control and restart of virtual boards.

o Media control interface

For control of switch connections.

• Operation and maintenance interface

For tracing of this interface in the Telephony Server. It is possible to