Вы находитесь на странице: 1из 22

Mobile Extension Release 1.

NOTICE
The information contained in this document is believed to be accurate in all respects but is not
warranted by Mitel Networks Corporation. The information is subjected to change without notice
and should not be construed in any way as a commitment by Mitel or any of its affiliates or
subsidiaries. Mitel and its affiliates and subsidiaries assume no responsibility for any errors or
omissions in this document. Revisions of this document or new editions of it may be issued to
incorporate changes.
No part of this document may be reproduced or transmitted in any form by any means
electronic or mechanical for any purpose without written permission from Mitel Networks
Corporation.

MOBILE EXTENSION SOLUTION Release 1.5


Engineering Guidelines
July, 2007

, Trademark of Mitel Networks Corporation


Copyright 2007 Mitel Networks Corporation
All rights reserved

MOBILE EXTENSION

TABLE OF CONTENTS

ABOUT THIS DOCUMENT .............................................................................................. 1


Overview .......................................................................................................................................1
Prerequisites .................................................................................................................................1
About the Mobile Extension Documentation Set ..........................................................................1

WHAT'S NEW FOR RELEASE 1.5 .................................................................................. 1


SECURITY AND THE MOBILE EXTENSION SOLUTION............................................... 2
UPGRADING MSL 7.0 TO 8.2.......................................................................................... 2
ENTERPRISE SITE CONFIGURATION........................................................................... 2
Supported ICP Configurations ......................................................................................................2
Supported User Desk Phones ......................................................................................................2
Supported Web Browsers .............................................................................................................2
Supported ICP Trunks ..................................................................................................................2
Software Requirements ................................................................................................................3
Minimum MSL Hardware Requirements for Mobile Extension Server .........................................3
Mobile Extension APC Configuration in 3300 CXi/CX..................................................................3
MSL 8.2 Configuration ..................................................................................................................3
MSL 8.2 Firewall and Local Network Configuration......................................................................3
MSL 8.2 in Server Gateway Mode ................................................................................................5
MSL Server in DMZ ......................................................................................................................6
Audio Format.................................................................................................................................6
Bandwidth Requirements..............................................................................................................6
Mobile Extension IP License Requirements .................................................................................6
Mobile Extension G.729 Configuration .........................................................................................7

CALLING LINE ID ............................................................................................................ 8


CLID Configuration .......................................................................................................................9
CLID Trouble Shooting .................................................................................................................9
Mobile Extension CLID Logs .....................................................................................................9

MOBILE EXTENSION CONFIGURATION ..................................................................... 10


Domain Settings..........................................................................................................................10
Outgoing Line Configurations .....................................................................................................10
TUI Ports .....................................................................................................................................10
TUI Port Configuration ................................................................................................................10

iii

Engineering Guidelines
Mobile Extension Server User Configurations ............................................................................10
Mobile Extension Use of MiTAI Monitors....................................................................................11
Installing Mobile Extension Blade on Existing MSL Server with Teleworker..............................12
Mobile Extension and Teleworker Co-resident on APC .............................................................12
Mobile Extension Master Server Feature ...................................................................................13
Master Server Deployment .........................................................................................................15
Master/Slave Server Performance..............................................................................................15

PERFORMANCE ANALYSIS......................................................................................... 16
GLOSSARY OF TERMS ................................................................................................ 17

iv

MOBILE EXTENSION

About this Document


Overview
These guidelines are provided to assist System Administrators in deploying the Mitel
Mobile Extension application. The Mobile Extension (ME) application runs on the Mitel
Standard Linux OS, which can be installed on different hardware platforms. This document
describes the minimum hardware requirements and support for those platforms and some
recommended settings for larger configurations.

Prerequisites
The scope of these Engineering Guidelines is to cover the Mobile Extension Solution
application, which requires the MSL server. Readers should first read the MSL Installation
and Administration Guide and the MSL Qualified Hardware documents available from
http://edocs.mitel.com.

About the Mobile Extension Documentation Set


For easy access to the various Mitel documentation suites, go to http://edocs.mitel.com.
Note: You require a Mitel OnLine user name and password to access this site.
The following guides provide complete information about Mobile Extension:

The Mobile Extension Engineering Guidelines (this document).

The Mobile Extension Installation and Maintenance Guide provides information about system
requirements; installation of Mobile Extension and configuring Mobile Extension options and
firewalls.

The Mobile Extension Quick Reference Guide provides basic user instructions

Visit Mitel on Line (MOL) for the latest updated Technical Bulletins, Release Notes and
Knowledge Base articles.

What's New for Release 1.5

Support for the MSL 8.2 platform

Answer Confirmation Feature

ME Interface Tab in MS Office Communicator

ME Master/Slave server support providing

Global TUI

Global GUI

Multi-server Cold Standby

Central DB Backup
1

Engineering Guidelines

Security and the Mobile Extension Solution


The Mitel Standard Linux (MSL) server may host many applications with very different
features. While it is technically feasible to install several applications on the same MSL
server, the inherent design of each application may impact co-residency considerations.
For example, the Teleworker application is specifically designed for connection to the public
Internet. Other MSL applications, like Mobile Extension, Live Business Gateway, and
NuPoint Messenger, are designed to operate only within the enterprise LAN.
Security best practices suggest run as little on your firewall as possible. Therefore, security
best practices would suggest that highly secure deployments of applications designed to
operate within the enterprise LAN should be installed alone on MSL and not co-resident
with applications specifically designed for connection to the public Internet. For this reason
Mitel does not recommend that enterprise-only applications like Mobile Extension and
Teleworker be installed on the same MSL.

Upgrading MSL 7.0 to 8.2


A MSL 8.2 CD is required for upgrading from MSL 7.0 to 8.2. For complete instructions
refer to the MSL Installation and Administration Guide available at Mitel OnLine.

Enterprise Site Configuration


The Mitel Mobile Extension application release 1.5 is installed on a MSL 8.2 server
running on the Enterprise LAN and must have IP connectivity to all ICPs which have
Users, Outgoing Lines, or TUIs.

Supported ICP Configurations

3300 ICP Release 6.X, 7.0, 7.1, 8.0 and newer

SX-200 ICP 3.0 and newer

Note: 3300 Release 7.1 UR1 is required for CLID functionality.


Note: 3300 Release 7.1 UR 2 is required for more than 300 users per ICP.
Also: The SX-200 ICP does not support CLID.

Supported User Desk Phones


Refer to the Mobile Extension Installation and Maintenance Guide (http://mitel.edocs) for a
complete list of supported desk phones.

Supported Web Browsers

Internet Explorer 5.5 and up

Firefox 1.5 and up

Supported ICP Trunks

All trunk types supported except for LS trunks which dont provide answer
supervision. LS trucks can be used when the Answer Confirmation feature is used.

Note: for CLID functionality on the 3300 ICP the following trunk types are supported
2

MOBILE EXTENSION

PRI/BRI
DAS II
R2

Software Requirements

MSL release 8.2 (8.2.6.0 or greater)

Server must be registered at the Mitel Applications Management Center for the
Mobile Extension Solution product

Minimum MSL Hardware Requirements for Mobile Extension Server

X-86 Architecture

PC Compatible at least 1.8 GHZ P4 CPU 512MB RAM 10GB hard drive

Note: MSL 8.2 and Mobile Extension 1.5 application supports multiprocessor and dual core
hardware platforms. The MSL 8.2 OS does not support 64 bit processors.

Mobile Extension APC Configuration in 3300 CXi/CX


The Mobile Extension application blade can be installed and run on an APC card in a 3300
CXi/CX platform. This configuration will support a maximum of the following:

30 Mobile Extension Users (which requires 30 desktop monitor phones), 10 Outgoing


Line phones and 4 TUI phones

Supports 10 simultaneous Mobile Extension User calls plus TUI calls

Note: Audio compression option using G.729 is not supported on the APC

MSL 8.2 Configuration


There are two supported configurations for the Mitel Teleworker Solution running on the
MSL 8.2 today which are:

Teleworker as Internet Gateway (Server Gateway mode)

Teleworker Solution Deployed in DMZ

Ideally the Mobile Extension application is installed on a MSL 8.2 server configured on the
corporate LAN in server-only mode. However, some customers may chose to install the
Mobile Extension blade on an existing MSL that is running in Server-Gateway mode. This
configuration does have some security risk since the box is facing the Internet and could be
compromised by some security hole. For more information about the MSL configurations
refer to the MSL 8.2 Installation and Administration Guide at http://mitel.edocs.
Note: the ME application should never be installed in the DMZ.

MSL 8.2 Firewall and Local Network Configuration


In MSL Release 8.2, the MSL firewall is enabled by default in server-only mode. Therefore,
the server firewall rules must be configured to allow all local networks (or "trusted
networks") to have access to the MSL server, so that the IP address of each ICP and
phone on your network that will be used by Mobile Extension falls within one of the IP
3

Engineering Guidelines
ranges configured within the local networks. Failure to add all the subnets where IP
telephones or ICP(s) exist can result in a "no audio" condition. The following image is an
example of a local network configuration for a MSL server:

The following form is used to add trusted local networks:

MOBILE EXTENSION

Typically local area networks are added by subnet. In all cases, the Router property
should be set to the address of the router on the subnet attached to the MSL internal
interface. For example:

To allow access from the single subnet 192.168.12.0 through 24, you would enter
192.168.12.0 and 255.255.255.0 in the Local Networks panel.

If the customers network has multiple subnets, with a common prefix, you can allow
access from the prefix. For example, if the customer uses various subnets within the
192.168.0.0 through 16 network, you would enter 192.168.0.0 and 255.255.0.0 in the
Local Networks panel, and allow the local router to determine the routing to the
individual subnets.

MSL 8.2 in Server Gateway Mode


The following diagram illustrates the Mobile Extension blade installed on a MSL server
configured in Server Gateway mode.

Mitel ICP

MSL 8.2

L2 Ports

ME
TW Gateway

To
Internet

Firewall

DSL
Modem

IP License Usage
If port filtering is used on the LAN side the following ports must be open to the LAN for the
Mobile Extension Service to function correctly:
Port Usage and Protocol

Number

HTTPS TCP

443

MiTAI TCP

8001

MiNET TCP

6800 6802

SSH TCP

22

Audio Streaming UDP

55000 - 58999 even ports only (i.e. 55000,


55002, 55004, etc.) Mitel IP Phones

Engineering Guidelines

MSL Server in DMZ


Mitel does not support installing the Mobile Extension blade in the DMZ.

Audio Format
The Mobile Extension Server supports G.711 and G.729 encoding.

Bandwidth Requirements

100 Mbps Full Duplex Switched Ethernet

Bandwidth usage details required by Mobile Extension include voice stream, peak control
stream utilization, and IP header overhead.
Assumptions:

G.711 voice stream requires 100 Kbps including signaling

G.729 voice stream requires 50 Kbps including signaling

Each Mobile Extension call has 2 voice streams


Number of Concurrent
Mobile Extension
Calls

G.711 Voice
Streaming Bandwidth

G.729 Voice
Streaming Bandwidth

200 kbps (bidirectional)

100 kbps

50

10 Mbps

5 Mbps

100

20 Mbps

10 Mbps

Bandwidth Usage

Mobile Extension IP License Requirements


The following table gives examples of the number of required IP licenses for a given
number of Mobile Extension Users:
Number of
Mobile
Extension
Users

Number of IP
Licenses for
Virtual
Phones

Suggested IP
Licenses for
Outgoing
Lines

Suggested
IP licenses
for TUI

Total
Number of
Additional

10

10

15

25

25

36

50

50

16

71

100

100

33

10

143

IP licenses

IP License Usage
Note: The total number of additional IP licenses does not include the desktop phone
license.

MOBILE EXTENSION
The suggested number of Outgoing Lines is for a site with average traffic patterns, based
on an average of 5 calls an hour with an average duration of 3 minutes. Higher traffic sites
may require more Outgoing Lines.
Note: The 3300 ICP CX/CXi has a maximum of 100 IP licenses. Therefore, if 50 Users
wanted to use Mobile Extension this platform may not be adequate since you would need
approximately 119 IP licenses (50 desktop phones, 50 Desktop monitors, 16 Outgoing
Lines, and 3 TUI ports). However, if the 50 Users were Hotdesk Users and were not
typically all logged into desk phones at the same time it may be sufficient (15 Desktop, 50
Desktop monitors, 16 Outgoing Lines, 3 TUI ports for a total of 84 IP licenses).

Mobile Extension G.729 Configuration


Mobile Extension 1.5 has optional support for using G.729 audio encoding to support low
bandwidth configurations. However, if the Mobile Extension server has to do transcoding
from G.711 to G.729 it can severely limit the number of simultaneous calls the Mobile
Extension Server can process. The following diagram illustrates the preferred compression
zone configuration with Mobile Extension 1.5:
Mitel ICP
Ottawa

Compression Zone Configuration


Mitel ICP
Toronto

IP Trunk
ME User

ME User

WAN

Zone 1
Zone 3
ME Server
Desktop
Monitor

Outgoing
Line

ME User
Mobile
Telephone

Zone 2

Mobile Extension 1.5 Compression Zone Configurations


The above diagram is an example of how Mobile Extension should be configured with
compression zones. The following objects are illustrated:
Mitel ICP: In this example 3300 ICP. Note the SX200 ICP doesnt support compression
zones but uses a COS scheme which can be configured to provide the same functionality.
Mobile Extension User: Mobile Extension User desktop telephones.
Desktop Monitor: Mobile Extension Server virtual telephone.
Mobile Extension Server: MSL 8.2 Server running the Mobile Extension 1.5 application
Desktop Monitor & Outgoing Line: Mobile Extension virtual phones
7

Engineering Guidelines
Zone 1: Compression zone for local Users on the Ottawa ICP with no intra-zone
compression (i.e. local calls will be G.711, remote calls from Ottawa - Toronto will be
G.729).
Zone 2: Compression zone for all Mobile Extension virtual phones with intra-zone
compression enabled. This will mean all Mobile Extension calls will be compressed and
providing the ICP has enough DSP resources and compression license should prevent the
Mobile Extension server from having to do transcoding.
Zone 3: Compression zone for Toronto ICP local Users, with no intra-zone compression.
When Mobile Extension is used with G.729 compression, its best to have all the calls
compressed to avoid transcoding. If the Mobile Extension application is forced to do
transcoding from G.711 to G.729, it will limit the number of simultaneous calls the Mobile
Extension server is able to process. Typically one transcoded call is approximately
equivalent to 10 calls not requiring transcoding. The following points are recommendations
when using the Mobile Extension 1.5 application with G.729 compression support:
1. Ensure that your ICP(s) have been configured with the maximum DSP resources.
2. Ensure that your ICP(s) have adequate G.729 licenses.
3. Configure all of the Mobile Extension Outgoing Lines and desktop monitors to be
in a compressed zone with intra-zone compression enabled.
4. Monitor the Mobile Extension call reports to know if Mobile Extension is required
to do transcoding.
5. If Mobile Extension is required to do transcoding set the Percentage of calls
requiring transcoding option in the Mobile Extension options page. This setting is
required because the application doesnt know if it has to do transcoding until the
call is established. Therefore, this percentage is used as new Mobile Extension
User calls are received to calculate if the required CPU resources are available.
If the application determines that the required resources are not available, a call
record is created indicating this error.
6. To calculate the Percentage of calls requiring transcoding perform the following
steps:
a. Generate the Mobile Extension Call report for a period of 1 day using a
typical business day.
b. Export the report into an Excel spreadsheet.
c.

The Call Report contains a column named Audio Format which will be set
to Compressed (G.729 call), Non-Compressed (G.711 call), or Transcoded
(transcoded call G.729 to G.711). For a 2-4 hour period determine the total
calls processed, and the number of transcoded calls.

d. Using the totals calculated in step c apply the following formula:


Percent Transcoded = ((Transcoded Calls /Total Calls) * 100)

Calling Line ID
Mobile Extension 1.5 supports CLID which in some situations allows Users to do call screening
based on the caller ID. This feature is turned off by default and is controlled by the following
options External calling line id and Internal calling line id which are options found on the Mobile
Extension Options page. This feature should be enabled with some caution (best to try after
business hours), since in some regions calls may be blocked if that region doesnt want the CLID
specified.

MOBILE EXTENSION

CLID Configuration
CLID is dependent on the following items:
1. Must be using 3300 release 7.1 UR1 or greater.
2. Not supported when the mobile phone is another internal IP desk phone on the
same ICP; only supported over trunks.
3. Must be using supported trunk types (see page 2).
4. Not supported on the SX-200 ICP.
5. Internal calls in most cases will not work if not using DID trunks since caller will
not have a valid PSTN number. Normal CPN substitution should occur and the
call should be presented in the same format as having your telephone forwarded.
6. CO must allow the CLID to be specified. In some regions the CO blocks calls or
uses a default CLID.

CLID Trouble Shooting


The simplest test to verify that CLID will function as you expect is to forward a desktop
phone not currently configured in Mobile Extension to a mobile phone device and make an
internal/external call to the desktop phone. If the CLID information is not what you expect
you may need to configure the 3300 CPN substitution, or the CO in your area could be
ignoring the CLID data being passed.

Mobile Extension CLID Logs


The Mobile Extension application provides logs to help trouble shoot problems with the
CLID functionality. These logs are provided when the Mobile Extension logs settings are
set to Info and have the following format:
INFO - Maint - Mc2LineMonitor.initiateMobileCall(): Mobile call for desk ext: 63994
Caller Number/Name 63993/J. Smith Internal Device
The log fields are defined here:
Log Field

Description

INFO:

Log level type

Maint

Log category type

Mc2LineMonitor.initiateMobileCall

Class and Function name

Mobile call desk ext: 63994

User desktop extension

Caller Number/Name 63993/J. Smith

Caller number and name


received and used by the
application.

Internal Device

Call was identified as an


internal call.

If the call was from an external trunk the following log would be printed:
INFO - Maint - Mc2LineMonitor.initiateMobileCall(): Mobile call for desk ext: 63994 Caller
Number/Name 6135922122/J. Smith External Device
If the Mobile Extension application didnt specify a CLID the following log would be
printed:
INFO - Maint - Mc2LineMonitor.initiateMobileCall(): Mobile call for desk ext: 63994 No CLID
Specified External Device
9

Engineering Guidelines

Mobile Extension Configuration


Domain Settings
The Mobile Extension application provides a mechanism fro grouping Users and Outgoing
Lines using the Domain setting. These virtual phone objects are shared within their
assigned Domain, and will only be used for calls to Users within the same Domain. This
logical grouping can be based on location, COS/COR, or some other site-specific
requirement. If all Outgoing Lines in a Domain are busy, any subsequent calls for Users in
that Domain will not be presented to their mobile devices. A maintenance log will be
generated in the Mobile Extension application to alert the system Administrator that this
situation has occurred, and more Outgoing Lines may need to be added to the Domain.
If there is no requirement to split Users into different groups they can be all within one
domain.

Outgoing Line Configurations


Outgoing Lines are used to call a users Mobile device, and if answered on their mobile
device, the Outgoing Line is involved in streaming the audio to the mobile device. Since the
Outgoing Lines are making calls on behalf of Users they should typically be configured with
the same COS/COR as the Users. Anytime a Mobile Extension User answers a call on their
desktop phone the Outgoing Line is released for use by other Users in the same Domain
and is not involved in the call.
For typical customer sites the Users to Outgoing Line ratio is 3 to 1. However, if the Users
are split into many different domains, or the site has higher than average call traffic, more
Outgoing Lines may be required.

TUI Ports
TUI ports are used primarily to activate/de-activate the Mobile Extension service or to
change the mobile device DN. The Mobile Extension User web interface provides the
same functionality. Therefore, depending on the Mobile Extension Users preferences (web
interface or IVR phone interface) will influence the required number of TUI ports. The
average system is 1 port for every 10 Users, but larger sites may require fewer and smaller
sites may require more.

TUI Port Configuration


Typically TUI ports will be assigned to a hunt group in the ICP with one pilot number that all
Users can use.

Mobile Extension Server User Configurations


A Mobile Extension Server running on the minimum specified hardware configuration can
support the following number of Users and Outgoing lines:

200 Mobile Extension Users, 66 Outgoing lines (concurrent calls) and up to 10 TUI
ports

If additional Users are required adding faster hardware and memory can be used to
increase capacity. The HP Proliant DL360 running at 3.2 GHZ with 2 GB of RAM will
support the following configuration:

10

500 Mobile Extension Users, 165 Outgoing lines (concurrent calls), and 20 TUI Ports

MOBILE EXTENSION
Note: The above configuration is the maximum number of Users supported on a single
Mobile Extension Server for release 1.5.

Mobile Extension Use of MiTAI Monitors


The Mobile Extension application uses MiTAI monitors on all of its phone objects which
adds some overhead processing to the ICP. The following table gives some examples of
the number of MiTAI monitors used:
Number
of Users

Desk Phone
Line
Appearance
Monitors

Desktop
Monitors

Outgoing
Line
Monitors

TUI
monitors

MiTAI
Monitor
Total

30

30

30

10

73

150

150

150

50

10

360

300

300

300

100

10

710

Mobile Extension MiTAI Monitor Count


The following example is a customer site where all Users are using 5235 desktop phones,
Microsofts Office Communicator, and Mobile Extension:
Number of
Users

5235 Phone
Monitor

Office
Communicator
Monitors

Mobile
Extension
Monitors

Total
Monitors

30

30

30

73

133

150

150

150

360

660

300

300

300

710

1310

Example MiTAI Monitor Count


Note: One 3300 ICP can only support 1000 MiTAI monitors

11

Engineering Guidelines

Installing Mobile Extension Blade on Existing MSL Server with Teleworker


When installing the Mobile Extension blade on an existing MSL server running Teleworker,
the following configuration recommendations are made:

Ensure the hardware meets the Mobile Extension Server minimum hardware
requirements

Ensure the MSL version is 8.2

Running on the minimum hardware platform specified reduce the maximum number
of Mobile Extension Users by the number of Teleworker Users (i.e. 30 Teleworker
Users results in a maximum of 170 Mobile Extension Users and 56 outgoing lines)

The following configurations are based on a hardware platform equivalent to the HP


Proliant DL360 running at 3.2 GHZ with 2 GB of RAM:

250 Teleworker Users and 250 Mobile Extension Users when using
5212/5224/5020/5215/5220/Navigator phones

125 Teleworker Users and 250 Mobile Extension Users when using 5340/5330/5235

75 Teleworker Users and 200 Mobile Extension Users when using YA Soft phones

Note: Relationship is one-to-one between Mobile Extension and Teleworker Users.

Mobile Extension and Teleworker Co-resident on APC


The Mobile Extension application blade can be installed with the Teleworker blade on an
APC. This is not a recommended configuration however will support the following
maximums:

15 Teleworker Users

10 Mobile Extension Users which requires 10 desktop monitor phones, 3 Outgoing


Line phones and 1 TUI phone

Supports 3 simultaneous Mobile Extension User calls & 4 Teleworker calls

Note: Increasing Mobile Extension Users decreases number of Teleworker Users by


equal number (increase Mobile Extension Users by 2 = decrease Teleworker Users
by 2)
The above configuration maximums may change based on future performance testing.

12

MOBILE EXTENSION

Mobile Extension Master Server Feature


ME release 1.5 includes the following features which rely on a Master/Slave server
configuration:

Global TUI for all ME Users (up to 2500 Users on 5 Slave servers)

Global GUI for all ME Users

Single Server backup for all servers

Single Cold Standby Server for all Slave servers

Automated Cold Standby server swap over

The following diagram illustrates the recommended network hierarchy using a Master
server:

Master Server Network Configuration


Object Description:
ME Master Server: MSL 8.2 server running ME 1.5 configured as a Master server. This
server is also running all of the TUI ports for this site.
Slave[1,2,3,4]: MSL 8.2 server running ME 1.5 running up to 500 ME Users (depending on
hardware configuration)
Cold Standby: MSL 8.2 server installed with ME 1.5 not currently running with any Users,
Outgoing Lines, or TUI ports.
Mitel ICP: Mitel 3300 or SX200

13

Engineering Guidelines
The recommended configuration is to run Users and Outgoing Lines on the Slave servers
and TUI ports on the Master server. If a Slave server dies the single Cold Standby server
can be enabled to run the dead Slaves configuration using the Master servers Change
Server feature. The following diagram illustrates the Master server setup tab:

Master Server Setup Tab


The above illustration is an example Master server which is running TUI ports locally and
Users on a Slave server. The local server must be added as a Slave server as well to have
the Global GUI/TUI functionality. If the Master server was to die, all of the Slave servers
would continue to function normally processing User calls. The Global TUI/GUI functionality
would not be available since the Master server is not running. The cold standby server
could be turned into the Master server by completing the following steps:
1. Enabling the Master server option on the Options tab of the cold standby.
2. Reboot the cold standby server
3. Add the Slave servers to the Master Setup tab.
4. Import the TUI port configuration.
Another option would be to restore a backup of the Master server on the Cold Standby and
reboot the server.

14

MOBILE EXTENSION

Master Server Deployment


The following steps should be used in deploying a ME Master/Slave solution:
1. Install all of the ME servers with the appropriate MSL 8.2 load and ME 1.5 load.
2. Set the Master Server option in the ME Options tab to On on the chosen Master
server.
3. Set the Web Service Password and Confirm Password and press the Save
button.
4. On each of the Slave servers set the Web Service Password and Confirm
Password. Note: this password is used by the Master server to gain access to the
Slave servers data.
5. Reboot the Master server to enable the Master server functionality.
6. Login to the Master server Server Manger interface and select the Mobile
Extension application.
7. Start the Mobile Extension service on the Overview tab if its not running.
8. Once the Mobile Extension service is active select the Master Setup tab.
9. Add each of the Slave servers to the Master Setup including the local host if
running TUI ports or Users on the Master server.
10. Select each of the Slave servers and press the Start button.
Note: After pressing the Start button the Master server will attempt to log into the Slave
server and if successful, it will take a snap shot of the slave servers DB and instruct the
slave server to notify it of any changes which will keep the Master servers data
synchronized with the slaves.

Master/Slave Server Performance


Mitel does not support the ME application Master/Slave feature when installed on MSL with
other applications such as Mitels Teleworker application.
When running the ME application and using the Master/Slave feature it will have little or no
performance impact on Slave servers. Therefore, Slave servers can run the maximum
number of Users, Outgoing Lines and TUIs as specified in this document providing the
hardware meets the performance requirements specified in this document.
The Master server functionality uses approximately 20% of the servers resources and
therefore reduces the maximum number of Users, Outgoing Lines, and TUIs which can be
run on the server.
Backing up Slave server statistics on a busy server can have a negative impact on
performance. Therefore, this should be done at non-peek hours or disabled if not required.

15

Engineering Guidelines

Performance Analysis
Actual performance results for a HP Proliant DL360 indicate that the Mobile Extension
Solution Release 1.5 can easily process 400 simultaneous G.711 streams (200 calls)
without any noticeable degradation in audio quality or performance. During the test, voice
quality was sampled by making actual calls between two Mobile Extension devices and
was found to be excellent under full load. The panel and console were fully responsive
during the test.
The following table summarizes maximum configurations for the hardware platforms we
have tested:
Hardware Platform

Number of
Users

Simultaneous
Calls
(Outgoing Lines)

APC

30

10

Minimum Hardware
Platform

200

66

10

HP Proliant DL 360
or equivalent

500

165

20

TUI Lines

Note: 3300 Release 7.1 UR 2 is required for more than 300 users per ICP.

16

MOBILE EXTENSION

Glossary of Terms
Term

Description

CLID

Calling Line Identification

CO

Central Office

CODEC

(enCOder/DECoder) Software or hardware that compresses and


decompresses audio and video data streams.

DMZ

Demilitarized Zone
In a DMZ configuration, most computers on the LAN run behind a firewall
connected to a public network like the Internet. One or more computers
also run outside the firewall, in the DMZ.

DTMF

Dual Tone Multi-Frequency generated typically by touch tone phones

E2T

Ethernet to TDM a system component that provides a gateway function


for voice samples, between the packet domain (Ethernet) and TDM
domain

G.711

ITU-T codec audio standard, specifying an audio signal with a 3.4 KHz
bandwidth (ordinary analog voice signal) over an A-law and -law
digitized, linear PCM at 64Kbps. In G.711, encoded voice is already in
the correct format for digital voice delivery in the PSTN or through PBXs.

G.729

This ITU-T standard describes CELP compression where voice is coded


into 8-kbps streams. The two variations of this standard (G.729A and
G.729A Annex A) differ mainly in computational complexity; both provide
speech quality similar to 32-kbps ADPCM.

ICP

Integrated Communications Platform

IP

Internet Protocol (RFC 1122 Section 3.)

IPSec

Internet Protocol Security

ISP

Internet Service Provider

IVR

Integrated Voice Response

LAN

Local Area Network

ME

Mobile Extension

MiNet

Mitel Network Layer Protocol A layer 2 protocol used to transport


messages between the PBX and all Mitel DNIC phones

MSL

Mitel Standard Linux

NAT

Network Address Translation - a technique for translating one set of IP


addresses, often private, to another set, often public (RFC 1631
May94)

Outgoing
line

Mobile Extension software phone emulator which calls user mobile


phone when a call is received at the Users desktop.

QoS

Quality of Service

RTP

Real Time Protocol (RFC 1889)

SRTP

Secure Real Time Protocol (IETF Standard:


http://www.ietf.org/rfc/rfc3711.txt Apr 04)

SSL

Secure Socket Layer

TCP

Transmission Control Protocol (RFC 1122 Section 4.1)


17

Engineering Guidelines

Term

18

Description

TFTP

Trivial File Transfer Protocol (RFC 783). A simple file transfer protocol
(no password protection or user directory services) that uses UDP to
transfer files across a network

Transcode

Changing audio digital format from one format to another (G.711 to


G.729)

TUI

Telephone User Interface provides IVR type interface using audio voice
prompts and DTMF tones

UDP

User Datagram Protocol (RFC 1122 Section 4.1)

UI

User Interface

VoIP

Voice over Internet Protocol

VPN

Virtual Private Network