MITEL SIP CoE Technical - Intermedia€¦ · 16-4940-00459 Intermedia SIP Trunking with MiVoice...

MITEL – SIP CoE

Technical Configuration Notes

Configure MiVoice Business 7.2 for use with

Intermedia SIP Trunking

AUGUST 2016

SIP COE 16-4940-00459

TECHNICAL CONFIGURATION NOTES

ii

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 7.2 for use with Intermedia SIP Trunking August 2016 – 16-4940-00459

®, ™ Trademark of Mitel Networks Corporation © Copyright 2016, Mitel Networks Corporation

All rights reserved

Table of Contents

iii

OVERVIEW ............................................................................................................... 1

Interop History.................................................................................................................... 1

Interop Status .................................................................................................................... 1

Software & Hardware Setup ............................................................................................... 2

Tested Features ................................................................................................................. 2

Device Limitations and Known Issues ................................................................................ 3

Network Topology .............................................................................................................. 4

CONFIGURATION NOTES ....................................................................................... 5

MiVoice Business Configuration Notes .............................................................................. 6

Network Requirements .................................................................................................................... 6

Assumptions for MiVoice Business Programming .......................................................................... 6

Licensing and Option Selection – SIP Licensing ............................................................................ 7

Class of Service Options ................................................................................................................. 8

Network Elements ......................................................................................................................... 10

Network Elements (Proxy)............................................................................................................. 11

Trunk Attributes ............................................................................................................................. 12

SIP Peer Profile ............................................................................................................................. 13

SIP Peer Profile Assignment by Incoming DID ............................................................................. 19

ARS Digital Modification Plans ...................................................................................................... 20

ARS Routes ................................................................................................................................... 21

ARS Digits Dialed .......................................................................................................................... 22

Fax Configuration .......................................................................................................................... 23

Network Zones .............................................................................................................................. 24

MITEL BORDER GATEWAY SETUP ..................................................................... 25

MiVoice Business Setup .................................................................................................. 25

SIP Trunk Setup ............................................................................................................... 26

16-4940-00459 Intermedia SIP Trunking with MiVoice Business

1

Overview This document provides a reference to Mitel Authorized Solutions providers for configuring the MiVoice Business (MiVB) 7.2 to connect to the Intermedia SIP trunk. Different components 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 October, 2008 Initial Interop with Mitel 3300 9.0 and Accessline SIP Service Provider v12.1.0

2 September, 2009 Refresh Interop with Mitel 3300 MCD 4.0 and Accessline SIP Service Provider v14.4.5

3 April 1, 2011 Refresh Interop with Mitel MCD 4.2 SP1 and Accessline v15.2.0

4 July 14, 2016 Recertification Interop with MiVoice Business (MiVB) 7.2 and Intermedia v16.14.3

5 Aug 17, 2016 Updated notes - Recertification Interop with MiVoice Business (MiVB) 7.2 and Intermedia v16.14.3

Interop Status

This Interop of Intermedia with MiVoice Business 7.2 has been given a Compatible Certification status. This SIP trunk will be included in the SIP CoE Reference Guide.

The most common certification which means MiVoice Business 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.


2

Software & Hardware Setup

The table below provides the hardware and software specifications used to generate basic calls, using Intermedia SIP trunk connected to MiVoice Business 7.2.

Manufacturer Variant Software Version

Intermedia Session Border Controller 16.14.3

Mitel MiVoice Business 7.2 – Mxe Platform Rel: 7.2, Active SW: 13.2.0.17

Mitel MBG SIP Trunk & Teleworker MSL: 10.3.33.0, MBG: 9.1.1.41

Mitel NuPoint Unified Messenger 17.0.0.24.01

Mitel Audio, Web and Video Conferencing 5.0.3.33-1

Aastra 68xxi SIP set 4.1.0.128 or 4.2.0.181

Mitel 53xx Sets 06.03.01.03 (MiNET)

Tested Features

Below table provides an overview of the features tested during the Interoperability test cycle and not a detailed view of the test cases. Please see the SIP Trunk Side Interoperability Test Plan for detailed test cases.

Feature Feature Description Issues

Basic Call Making and receiving a call through SIP service provider and their PSTN gateway, call holding, transferring, conferencing, busy calls, long calls durations, variable codec.

Automatic Call Distribution

Making calls to an ACD environment with RAD 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 MIVB to stream RTP packets through its E2T card at different intervals, from 10ms to 60ms.

Personal Ring Groups (PRG)

Receiving calls through MiVoice Business and their PSTN gateway to a personal ring group. Also moving calls to/from the prime member and group members.

Teleworker Making and receiving a call through MiVoice Business and their PSTN gateway to and from Teleworker extensions.

Video Making and receiving a call through MiVoice Business with video capable devices.

Fax G.711 Fax calls.

- No issues found - Issues found, cannot recommend to use - Issues found Not tested/applicable


3

Device Limitations and Known Issues

This is a list of problems or not supported features when Intermedia SIP trunk is connected to the. MiVoice Business 7.2

Feature Problem Description

FAX Intermedia does not support FAX using T.38.

Recommendation: Consult with Intermedia for further information and updates.

PRACK Intermedia does not support PRACK correctly in the following call scenario,

- A call from Mitel to PSTN service such as conferencing or IVR system

- The PSTN sends alerting 183 and immediately connecting the call with 200 OK

Recommendation: Mitel recommends to disable PRACK when SIP

Trunking with Intermedia as already noted in this configuration guide. Consult with Intermedia for further information and updates.

Video Intermedia does not support Video.

Recommendation: Consult with Intermedia for further information and

updates.


4

Network Topology

This diagram shows how the testing network is configured for reference.

Figure 1 – Network Topology

Teleworker/ MBG

Server

Intermedia SBC MiVoice Business

(MiVB)

NuPoint Voicemail

Server

Mitel SIP Interoperability

Network Configuration

Aastra 6867i

SIP Phone

Aastra 6867i

SIP Phone


5

Configuration Notes This section is a description of how the SIP Interop network was configured. These notes provide a guideline as how a device can be configured in a customer environment and how the Intermedia and MiVB programming were configured in our test environment.

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.

This section provides an example of non-overlapping dial plan configuration for Intermedia and MiVB systems. In the example, MiVB and Intermedia systems use the following extension numbers:

Intermedia dial plan includes extensions 2066863771 and 2066866403.

MiVoice Business dial plan includes extensions 7800 – 7899.

Four-Digit Plans: When configuring, adhere to the guidelines provided in the ITU-Recommendation E.164 to ensure that both systems interpret and route phone numbers correctly. The E.164 recommendation is available on the International Telecommunications Union Web site at http://www.itu.int/rec/T-REC-E.164/en.


6

MiVoice Business Configuration Notes

The following information shows how to configure a MiVB 7.2 to interconnect with Intermedia.

Network Requirements

There must be adequate bandwidth to support the VoIP network. 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 MiVoice Business Engineering guidelines on the Mitle eDocs Website (http://edocs.mitel.com) 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 MiVoice Business Programming

The SIP signaling connection uses UDP on Port 5060

http://edocs.mitel.com/


7

Licensing and Option Selection – SIP Licensing

Ensure that MiVoice Business is equipped with enough SIP trunking licenses for the connection to Intermedia. 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 MiVB to be used with all service providers, applications and SIP trunking devices.

Figure 2 – License and Option Selection


8

Class of Service Options

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

Many different options may be required for your site deployment, but ensure 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 MiVoice Business.

Public Network Access via DPNSS set to Yes

If use FAX equipment ensure that the following options are enabled,

Campon Tone Security/FAX Machine set to Yes

Busy Override Security set to Yes


9

Figure 3 – Class of Service Options


10

Network Elements

Create a network element for a SIP Peer, Intermedia. In this example, the gateway is reachable by an IP Address and is defined as Intermed in the Network Elements form. The FQDN or IP addresses of the SIP Peer (Network Element), the External SIP Proxy, and Registrar are provided by your service provider.

If your service provider trusts your network connection by asking for your gateway external IP address, then programming the IP address for the SIP Peer, Outbound Proxy and Registrar is not required for SIP trunk integration. This will need to be verified with your service provider. Please note that in our example, Intermedia has requested to set the transport to UDP and port to 6060, as oppose to default 5060.

Figure 4 – Network Elements


11

Network Elements (Proxy)

Depending on your configuration, a Proxy may need to be configured to route SIP data to the service provider. If you have a Proxy server installed in your network, MiVoice Business require knowledge of this by programming the Proxy as a network element, then referencing this Proxy in the SIP Peer profile, as you see later in this document.

Below shows configuration for MBG trunk Network Element as Outbound Proxy that is used in this interop for correct routing.

Figure 5 – Network Elements for Outbound Proxy


12

Trunk Attributes

Use Trunk Attributes form to configure Trunk Service Number. In this example, the Trunk Service Number 12 will be used to direct incoming calls to an answer point in MiVoice

Business.

Program the Non-dial In or Dial In Trunks (DID) according to the site requirements and what

type of service was ordered from your service provider.

Figure 6 below shows configuration for incoming DID calls. The MiVoice Business will absorb the first 6 digits of the DID number received from Intermedia’s SIP trunk leaving 4 digits for MiVoice Business to translate and ring the 4-digit extension.

For example, the Intermedia’s SIP trunk delivers numbers 206-686-6403 through SIP trunk to MiVoice Business, which will absorb the first 6 digits (206686) leaving the remaining 4 digits (6403) to route the call. Number 6403 must be programmed as a valid dialable number in the MiVoice Business. Alternatively, you can create a System Speed Call number to associate 6403 with the real telephone extension in MiVB. Please refer to MiVoice Business 7.2 System Administration documentation for further programming information.

Figure 6 – Trunk Service Assignment


13

SIP Peer Profile

The recommended connectivity via SIP Trunking does not require additional physical interfaces. IP/Ethernet connectivity is part of the base MiVoice Business Platform. The SIP Peer Profile should be configured as shown in Figures 7 - 12.

The settings on all other tabs of SIP Peer Profile form remain unchanged, at their default values. Click Save to submit the settings.

Under Basic tabs:

Network Element: The selected SIP Peer Profile needs to be associated with previously created Intermed Network Element.

Registration User Name: The MiVoice Business does not support Bulk registration. As such trunks have to be registered individually. As Intermedia require MiVB to register, this field was used for user names that Intermedia expected the system to register with. In this example, they were the provided DIDs: 2066863771, 2066866403.

Address Type: Select IP address of the MiVoice Business as shown.

Outbound Proxy Server: Select Network Element previously configured for the outbound proxy server. For this test, MBG trunk outbound proxy server has been used.

Trunk Service: Enter the trunk service previously configured, 12 in this configuration notes.

SMDR: If Call Detail Records (CDR) are required for SIP Trunking, the SMDR Tag should be

configured (by default there is no SMDR and this field is left blank).

Maximum Simultaneous Calls: Configure this entry to be the maximum number of SIP

trunks provided by Intermedia.

Authentication: Enter the username and password provided by the provider. Please note

that Intermedia required Authentication and provided the username and password.

NOTE: Ensure the remaining SIP Peer profile policy options are similar to the screen capture

below.


14

Figure 7 – SIP Peer Profile - Basic

Figure 8 – SIP Peer Profile – Call Routing


15

Under Calling Line ID tab:

The Default CPN (Calling Party Number) is applied to all outgoing calls; unless there is a match in the Outgoing DID ranges of the SIP Peer profile. This number is usually one of the

numbers supplied by Intermedia, i.e. 2066863771.

Do not use a default CPN if you want public numbers to be preserved through the SIP interface. Add private numbers into the DID ranges for CPN Substitution form (see DID Ranges for CPN Substitution). Then select the appropriate numbers in the Outgoing DID Ranges in this form (SIP Peer Profile).

Figure 9 – SIP Peer Profile – Calling Line ID


16

Under SDP Options tab:

Currently (July 2016), Video streams are not supported over Intermedia SIP trunk. Thus, set option Allow Peer to Use Multiple Active M-Lines to ‘No’. Configure other settings as

show below.

Figure 10 – SIP Peer Profile – SDP Options


17

Under Signaling and Header Manipulation tab:

Intermedia SIP supports PRACK. As such, we recommend that option Disable Reliable Provisional Responses is set to ‘No’, and Require Reliable Provisional Responses on Outgoing Calls is set to ‘Yes’.

Figure 11 – SIP Peer Profile – Signaling and Header Manipulation


18

For Timers, Key Press Event, Outgoing DID Ranges, and Profile Information tabs, leave the default settings intact.

Figure 12 – SIP Peer Profile – Timers


19

SIP Peer Profile Assignment by Incoming DID

This form is used to assign incoming digits from the SIP peer, Intermedia. DID range numbers assigned by Intermedia are used to associate to a particular SIP Peer.

Enter one or more telephone numbers. The maximum number of digits per telephone number is 26. You can enter a mix of ranges or single numbers (for example, "6135554000-6135554400, 6135554500"). The entire field width is limited to 60 characters.

Use a comma to separate telephone numbers and ranges. Use a dash (-) to indicate a range of telephone numbers. The first and last characters cannot be a comma or a dash. If the numbers do not fit within the 60 character maximum, you can create a new entry for the same profile.

Use a '*' to reduce the number of entries that need to be programmed. This is a type of "prefix identifier", and cannot be used as a range with '-'. For example, the string "11*" would be used to associate a peer with any number in the range from 110 up to the maximum digits per telephone number (In this case, 11999999999999999999999999.) Note that the string "11" by itself would not count as a match, as the '*' represents 1 or more digits.

Figure 13 – SIP Peer Profile Assignment by Incoming DID


20

ARS Digital Modification Plans

Ensure that ARS Digit Modification for outgoing calls on the SIP trunk to Intermedia absorbs or inject additional digits according to your dialing plan. In this example, digit modification number 4 will be absorbing 3 digits, and injecting additional 206686, when ARS prefix 944 is entered to dial out.

Figure 14 – ARS Digit Modification Plans


21

ARS Routes

Create a route for SIP Trunks connecting a trunk to Intermedia. In this example, the SIP trunk is assigned to Route Number 17. Choose SIP Trunk as a routing medium and choose the SIP Peer Profile and Digit Modification entry created earlier.

Figure 15 – ARS Routes


22

ARS Digits Dialed

ARS initiates the routing of trunk calls when certain digits are dialed from a station. In this example, when a user dials 944 followed by 4 digits, the call will be routed to MiVB via Route 17.

Figure 16 – ARS Digit Dialed


23

Fax Configuration

Intermedia uses the intra-zone default G.711 pass through communication (Profile 1). The Fax Service Profiles form allows user to define the settings for FAX communication over the IP network. Below default settings can be modified:

Inter-zone FAX profile: defines the FAX settings between different zones in the network. There is only one Inter-zone FAX profile; it applies to all inter-zone FAX communication. It defaults to V.17, 14400bps. It defines the settings for FAX Relay (T.38) FAX communication.

Intra-zone FAX profile: defines the FAX settings within each zone in the network.

Profile 1 defines the settings for G.711 pass through communication.

Profile 2 to 64 define the settings for FAX Relay (T.38) FAX communication.

All zones default to G.711 pass through communication (Profile 1).

Figure 17–Fax Service Profile

Figure 18 – Fax Advanced Settings


24

Network Zones

By default, all zones are set to Intra-zone FAX Profile 1, which defaults to G.711 pass-through communication.

Based on your network diagram, assign the Intra-zone FAX Profiles to the Zone IDs of the zones. If audio compression is required within the same zone, set Intra-Zone Compression to “Yes”. In our example, Zone ID 2 is setup with Intra-zone fax Profile 2 which supports T.38 pass-through communication.

Figure 19 – Network Zones


25

Mitel Border Gateway Setup

MiVoice Business Setup

To program a MiVoice Business into Mitel Border Gateway (MBG),

Login to Server Manager of MBG

Select Mitel Border Gateway under Applications

Select Service Configuration tab

Click on ICPs

Select Add ICP

Enter a name for MiVoice Business; example: Sipint2

Enter the IP address of MiVoice Business

Select the Type; example: MiVoice Business

Figure 20 – Configuration - ICP Setup


26

SIP Trunk Setup

To program a Intermedia SIP trunking into Mitel Border Gateway (MBG),

Under the Services tab of MBG, click on SIP Trunking

Select Add a SIP Trunk and enter the SIP trunk’s details as shown.

Name: Enter the trunk name; for example: Intermedia

Remote trunk endpoint address: Enter the public IP address or FQDN of the provider’s switch or gateway. This address should be provided to you by the provider.

Remote trunk endpoint port: Enter the port provided to you by the provider. In this example, port 6060 was specified. If not specified, default port 5060 is used.

Local/Remote RTP framesize (ms): Enter the packetization rate you want to set on this trunk. Auto is set to 20 ms.

PRACK: Set to Disabled.

Routing rule one: Allows routing of any digits to the selected MiVB

The rest of the settings are optional and could be configured if required

Click Save

Figure 21 – Services - SIP Trunking setup


27

MITEL SIP CoE Technical - Intermedia€¦ · 16-4940-00459 Intermedia SIP Trunking with MiVoice...

Documents

Transcript of MITEL SIP CoE Technical - Intermedia€¦ · 16-4940-00459 Intermedia SIP Trunking with MiVoice...