MITEL – SIP CoE

Technical
Configuration Notes

Configure MiVoice Business 7.0 for use with

MiVoice MX-ONE SIP Trunk
DECEMBER 2014
SIP COE 14-4940-00352
TECHNICAL CONFIGURATION NOTES
 NOTICE

The information contained in this document is believed to be accurate in all respects but
®
is not warranted by Mitel Networks™ Corporation (MITEL ). The information is subject 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 such changes.

No part of this document can be reproduced or transmitted in any form or by any means -
electronic or mechanical - for any purpose without written permission from Mitel Networks
Corporation.

TRADEMARKS

Mitel is a trademark of Mitel Networks Corporation.

Windows and Microsoft are trademarks of Microsoft Corporation.

Other product names mentioned in this document may be trademarks of their respective
companies and are hereby acknowledged.

Mitel Technical Configuration Notes – Configure MiVoice Business 3300 to interface with MiVoice
MX-ONE SIP Trunking

Nov 27, 2014, 14-4940-00352

®,™ Trademark of Mitel Networks Corporation

© Copyright 2014, Mitel Networks Corporation
All rights reserved

ii
 Table of Contents

OVERVIEW ............................................................................................................... 1
Interop History....................................................................................................................1
Interop Status ....................................................................................................................1
Software & Hardware Setup ...............................................................................................2
Tested Features .................................................................................................................2
Tested Features .................................................................................................................3
Device Limitations and Known Issues ................................................................................4
Network Topology ..............................................................................................................5

CONFIGURATION NOTES ....................................................................................... 6

MiVoice Business 3300 Configuration Notes ......................................................................6
Network Requirements .................................................................................................................... 6
Assumptions for MCD Programming............................................................................................... 6
Licensing and Option Selection – SIP Licensing ............................................................................ 7
Class of Service Assignment .......................................................................................................... 8
Network Element Assignment ....................................................................................................... 11
Trunk attributes (trunk service number) ........................................................................................ 11
SIP Peer Profile ............................................................................................................................. 12
ARS Digit Modification Plan .......................................................................................................... 15
ARS Routes ................................................................................................................................... 16
ARS Digits Dialed .......................................................................................................................... 16
MiVoice MX-ONE Configuration Notes .............................................................................16
Creating a User ............................................................................................................................. 16
Creating the SIP Trunk .................................................................................................................. 17

iii
14-4940-00352 MiVoice MX-ONE

Overview
This document provides a reference to Mitel Authorized Solutions providers for
configuring the MiVoice Business 3300 (3300) to connect to MiVoice MX-ONE through
SIP Trunk.

The different devices can be configured in various configurations depending on your VoIP
solution. This document covers a basic setup with required option setup.

Interop History

Version Date Reason

1 November, 2014 Initial Interop of MiVoice Business 7.0 sp2 with MX-ONE through
SIP trunk

Interop Status
The Interop of MiVoice MX-ONE with SIP Trunk was tested and has been given a
Certification status. This service provider or trunking device will be included in the SIP
CoE Reference Guide. The status MiVoice MX-ONE SIP Trunking achieved is:

The most common certification which means MiVoice MX-ONE SIP

Trunking has been tested and/or validated by the Mitel SIP CoE team.
Product support will provide all necessary support related to the interop,
but issues unique or specific to the 3rd party will be referred to the 3rd
party as appropriate.
14-4940-00352 MiVoice MX-ONE

Software & Hardware Setup

The table below provides the hardware and software specifications used to generate a
basic SIP call between MiVoice MX-ONE and the MiVoice Business 3300 (MCD) using
SIP trunk.
Manufacturer Variant Software Version

Mitel 3300 MCD – Mxe Platform MCD 7.0 (13.0.0.80) GA

Mitel Aastra Mx-one with VMG (VM) 5.0 SP5 Hotfix1 (TS: build
2.310.2 and MTS: build
9.316.2)
Mitel Minet sets: 5330e R8 06.02.00.06
Mitel Aastra 6863i, 6865i,6867i 4.0.0.92
Mitel MBG - Teleworker 8.0.27.0
Mitel MBG – SBC 8.0.27.0
Mitel NuPoint voice mail server Build 17.0.0.24.01
Mitel MiVoice Video Unit 2.1.2.9
Mitel MiVoice MX-ONE ( with VMG) 5.0 SP5 Hotfix1 (TS: build
2.310.2)

Tested Features
This is an overview of the features tested during the Interop test cycle and is not a
detailed view of the test cases. Please see the SIP Trunk Side Interoperability Test Plans
for detailed test cases.

2
14-4940-00352 MiVoice MX-ONE

Tested Features
This is an overview of the features tested during the Interop test cycle and not a detailed
view of the test cases. Please see the SIP Trunk Side Interoperability Test (ApTest) for
detailed test cases.

Feature Feature Description Issues

Basic Call Making and receiving a call through MiVoice MX-ONE

and their PSTN gateway, call holding, transferring,
conferencing, busy calls, long calls durations, variable
codec.
Automatic Call Making calls to an ACD environment with RAD
Distribution treatments, Interflow and Overflow call scenarios and
DTMF detection.
NuPoint Voicemail Terminating calls to a NuPoint voicemail boxes and
DTMF detection.
Packetization Forcing the Mitel 3300 MCD to stream RTP packets
through its E2T card at different intervals, from 10ms to
90ms
Personal Ring Receiving calls through MiVoice MX-ONE to a personal
Groups ring group. Also moving calls to/from the prime
member and group members.
Teleworker Making and receiving a call MiVoice MX-ONE to and
from Teleworker extensions.
Video Making and receiving a call through MiVoice MX-ONE
with video capable devices.
Fax T.38 and G711Fax Calls Not tested
Authentication Incoming/outgoing authenticated calls
- No issues found - Issues found, cannot recommend to use - Issues found
14-4940-00352 MiVoice MX-ONE

Device Limitations and Known Issues

This is a list of limitations when MiVoice MX-ONE SIP Trunking is connected to the MCD.

Feature Problem Description

Trunk Registration Limitation: It is not possible to register to the MiVoice MX-ONE via a SIP
trunk.
MX-ONE supports registration for outgoing trunk towards an ISP.
Fax G.711/T.38 Was not tested due to Lab setup environment.
Basic Incoming PSTN calls were not performed due to lab setup environment.

4
14-4940-00352 MiVoice MX-ONE

Network Topology
The interop addressed by this activity is intended to test the SIP trunk between the enterprise SIP
customer premises equipment MiVoice Business 3300 and MiVoice MX-ONE.
Figure 1 shows how the testing network is configured for reference. In this configuration the
MiVoice MX-ONE was installed on a VM server.

Figure 1 – Network Topology

14-4940-00352 MiVoice MX-ONE

Configuration Notes
This section provides recommendations and guidelines on how to configure an up and
running MiVoice Business 3300 and a MiVoice Border Gateway MBG systems to achieve
connectivity and interoperability requirements. Hence theses configurations do not
represent the programming of both systems in their entirety.

These notes include screenshots as much as possible of the configuration done in the
SIP CoE test lab environment.

The configuration notes are organized in this order:

1. Configuration of the MiVoice Business 3300 system

2. Configuration of the MiVoice MX-One.

Disclaimer: Although Mitel has attempted to setup the interop testing facility as
closely as possible to a customer premise environment, implementation setup
could be different onsite. YOU MUST EXERCISE YOUR OWN DUE DILIGENCE IN
REVIEWING, planning, implementing, and testing a customer configuration.

MiVoice Business 3300 Configuration Notes

The following steps show how to program a MiVoice Business to interconnect through sip
trunk with MiVoice MX-ONE.

Network Requirements
• There must be adequate bandwidth to support the voice over IP. As a guide, the
Ethernet bandwidth is approx 85 Kb/s per G.711 voice session and 29 Kb/s per
G.729 voice session (assumes 20ms packetization). As an example, for 20
simultaneous SIP sessions, the Ethernet bandwidth consumption will be approx 1.7
Mb/s for G.711 and 0.6Mb/s. Almost all Enterprise LAN networks can support this
level of traffic without any special engineering. Please refer to the 3300 Engineering
guidelines for further information.
• For high quality voice, the network connectivity must support a voice-quality grade of
service (packet loss <1%, jitter < 30ms, one-way delay < 80ms).

Assumptions for MCD Programming

The SIP signaling connection uses UDP on Port 5060.

6
14-4940-00352 MiVoice MX-ONE

Licensing and Option Selection – SIP Licensing

Ensure that the MiVoice Business 3300 is equipped with enough SIP trunking licenses for
the connection to the MiVoice MX-ONE. This can be verified within the License and
Option Selection form.

Enter the total number of licenses in the SIP Trunk Licences field. This is the maximum
number of SIP trunk sessions that can be configured in the 3300 to be used with all
service providers, applications and SIP trunking devices.

Figure 2 – License and Option Selection

14-4940-00352 MiVoice MX-ONE

Class of Service Assignment

The Class of Service Options Assignment form is used to create or edit a Class of
Service and specify its options. Classes of Service, identified by Class of Service
numbers, are referenced in the Trunk Service Assignment form for SIP trunks.

Many different options may be required for your site deployment, but eensure that “Public
Network Access via DPNSS” Class of Service Option is configured for all devices that
make outgoing calls through the SIP trunks in the 3300.

• Public Network Access via DPNSS set to Yes

• Busy Override Security set to Yes

8
14-4940-00352 MiVoice MX-ONE
14-4940-00352 MiVoice MX-ONE

Figure 3 – Class of Service

10
14-4940-00352 MiVoice MX-ONE

Network Element Assignment

Create a network element for the MiVoice MX-ONE. In this example, the soft switch is
reachable by an IP Address and is defined as “MX-ONE” in the network element
assignment form.

Figure 4 – Network Elements Assignment for both MX-ONE trunk

Trunk attributes (trunk service number)

The Trunk Attributes is defined for Trunk Service Number (5), which will be used to direct
incoming calls to an answer point in the MiVoice Business 3300ICP.
Set the number of Class of Service that was configured in the section above (7).
Please refer to the 3300 System Administration documentation for further programming
information on how to manipulate incoming digits.

Figure 5: Trunk Attributes (trunk service number)

14-4940-00352 MiVoice MX-ONE

SIP Peer Profile

The recommended connectivity via SIP Trunking does not require additional physical
interfaces. IP/Ethernet connectivity is part of the base 3300 MCD Platform. The SIP Peer
Profile should be configured with the following options:

Figure 6: SIP Peer Profile Assignment- Basic

Figure 7: SIP Peer Profile Assignment- Call Routing

12
14-4940-00352 MiVoice MX-ONE

Figure 8 : SIP Peer Profile Assignment- Calling Line ID

Figure 9: SIP Peer Profile Assignment- SDP Options

14-4940-00352 MiVoice MX-ONE

Figure 10 : SIP Peer Profile Assignment- Signaling and Header Manipulation

Figure 11 : SIP Peer Profile Assignment- Timers

14
14-4940-00352 MiVoice MX-ONE

ARS Digit Modification Plan

MiVoice Business offers many way to perform digits manipulations, the following
screenshots show one way of performing translations on the dialled digits in order to
route through the MX-One SIP trunk to reach the MiVoice MX-ONE.

Ensure that Digit Modification for outgoing calls to SIP trunk absorbs or inject additional
digits according to your dialling plan. In our test environment, we will be absorbing 3
digits.
In our test environment, we will dial 960 to the MX-ONE outgoing SIP trunk to terminate a
call to MiVoice MX-ONE.

Figure 12 – ARS Digit Modification form

14-4940-00352 MiVoice MX-ONE

ARS Routes
Create a route for the MX-ONE SIP trunk. In this test environment, MX-ONE sip trunk is
associated with Route Number 8. Choose SIP Trunk as a routing medium and choose
the SIP Peer Profile and ARS Digit Modification entry created earlier.

Figure 13 – ARS Routes form

ARS Digits Dialed

ARS initiates the routing of trunk calls when certain digits are dialed from an extension. In
this test environment, when user dials 960, the call will be routed to MX-ONE sip trunk.
For outbound calling, 3300 ICP expects an “unknown” number of digits to be dialed after
dialing of 960 as shown below.

Figure 14 – ARS Digit Dialed Assignment Form

MiVoice MX-ONE Configuration Notes

The following steps show how to program a MiVoice MX-ONE to interconnect through sip
trunk with MiVoice Business 3300.

Creating a User

Command Line was used in this interop to create users. The following steps provide the
commands used to create users with command line.

16
14-4940-00352 MiVoice MX-ONE

• step 1: setting up line extensions:

$ number_initiate -number xxxx..yyyy -numbertype ex
- setting up trunk extensions:
$ number_initiate -number xxx -numbertype ed

• step 2: Creating Extension service profile:

$ extension_profile -i --csp 1 --ext-traf 0103151515 --ext-serv
2131320110010000000001000003 --ext-cdiv 11100011101131 --ext-roc 000001
--ext-npres 0011001 --csp-name "Fully open"

• step 3: Initiating sip extension users

extension -i -l 1 --csp 1 -d xxxx --max-terminals 1

• step 4
ip_extension -i -d xxxx

To verify the newly created Users on MiVoice MX-One using the MX-ONE Manager Provisioning
as follows.

Creating the SIP Trunk

The Sip trunk used for this interop was created using the command line on MiVoice MX-ONE.
The following steps provide the commands used to create the sip trunk.
• step 1 for trunk:
$ number_initiate -number XX -numbertype ed
• step 2a: Outbound settings:
14-4940-00352 MiVoice MX-ONE

$ sip_route -set -route 1 -uristring0 sip:?@<remote Ip#> -remoteport

5060 -fromuri0 sip:?@<MX-one IP#> -protocol tcp
• step 2b: Inbound settings
$ sip_route -set -route 1 -accept REMOTE_IP -match <remote IP #> -
trusted ID_ASSERT
Note: The REMOTE_IP will match the IP address sent in the source IP header.
Also use the commands ROCAI and RODAI to set the basic route data.

• step 3a
$
ROCAI:ROU=1,SEL=7110000000000010,TRM=4,SERV=3110000001,TRAF=03151515,SI
G=1111110000A0,BCAP=101100;
• step 3b
$ RODAI:ROU=1,TYPE=TL66,VARC=00000000,VARI=00000000,VARO=00000000;
Finally associate the route to specific HW equipment (heritage from legacy stuff)

• step 4
$ ROEQI:ROU=1,tru=1-1&&1-10;
• step 5
$ RODDI:DEST=XX,ROU=3,ADC=0005000000000250000001110000,SRT=3;

18
14-4940-00352 MiVoice MX-ONE