MITEL – SIP CoE
Technical Configuration Notes
Configure Ascom i62 5.4.2 to use with MiVoice MX-ONE 6.0 SP2 FEBRUARY 2016 SIP COE 16-4940-00431 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 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 Ascom i62 5.4.2 to use with MiVoice MX-ONE 6.0 SP2 February 2016 – 16-4940-00431
®, ™ Trademark of Mitel Networks Corporation © Copyright 2016, 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 Resiliency .......................................................................................................................... 3 Application Limitations and Known Issues.......................................................................... 4 Network Topology .............................................................................................................. 5
CONFIGURATION NOTES ....................................................................................... 6 MiVoice MX-ONE Configuration Notes ............................................................................... 6 Network Requirements .................................................................................................................... 6 Assumptions for MiVoice MX-ONE Programming .......................................................................... 6 System Overview ............................................................................................................................ 7 Adding SIP Extension...................................................................................................................... 8 Authentication ................................................................................................................................ 11 Hunt Group .................................................................................................................................... 12 Hunt Group Members .................................................................................................................... 14
Ascom i62 Configuration Notes ........................................................................................ 16 Access Ascom i62 ......................................................................................................................... 16 Ascom i62 General Media ............................................................................................................. 18 Ascom i62 SIP Capabilities ........................................................................................................... 19 VoWiFi Networks ........................................................................................................................... 20 Ascom Messaging ......................................................................................................................... 22
REFERENCES ........................................................................................................ 23
iii
16-4940-00431
Ascom i62 with MiVoice MX-ONE
Overview This document provides a reference to Mitel Authorized Solutions providers for configuring the MiVoice MX-ONE 6.0 SP2 to host Ascom i62 5.4.2. The Ascom Voice over Wireless Fidelity (VoWiFi) system provides wireless IP telephony, messaging and alarm functions to enterprise LANs. Ascom i62 is a VoWiFi handset and its functions are license dependant and are available in three versions: Talker, Messenger, and Protector. 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 1
Date
Reason
Feb 03, 2016
Initial Interop of Ascom i62 5.4.2 with MiVoice MX-ONE 6.0 SP2
Interop Status This Interop of Ascom i62 with MiVoice MX-ONE has been given a Certification status. This device will be included in the SIP CoE Reference Guide. The status Ascom i62 achieved is: Mitel-Qualified Test” (MQT) Certification. Applies to various types of MSA member products/services, where a Mitel regional sales organization and the MSA member have mutually agreed to pursue Mitel certification in support of joint business opportunities. MQT certification is an assertion made by Mitel that Mitel has executed a standard interop test plan for the product/service category, and determined that the interop was sufficiently successful to deploy the solution at a customer site, subject in some cases to certain restrictions or limitations. Any such restrictions or limitations identified during the testing are documented in a formal test report and/or Mitel Config Guide. An MQT designation does not in any way imply that all functionality of the MSA member product/service has been tested. Nor does it imply that there are no known issues related to the interop. It is the responsibility of the MSA member and the Mitel channel partner to ensure that they understand the extent of the Mitel testing and that they determine whether the documented/known issues will impact their specific customer deployment. Support for the integrated solution will be provided jointly by the sponsoring regional Mitel sales organization and the MSA member. This MQT certification is valid exclusively for Mitel deployments in Sweden, as authorized in writing by the Mitel Sweden Country Sales Manager. The Product Support protocol for this solution is as follows:
Mitel SE Pro services provides support for approved EFT sites
Mitel SE will be responsible for all MiVoice MX-One related Product Support issues
1
16-4940-00431
Ascom i62 with MiVoice MX-ONE
Software & Hardware Setup The table below provides the hardware and software specifications used in interop of Ascom i62 with MiVoice MX-ONE. Manufacturer
Variant
Mitel
MiVoice MX-ONE Virtual
Aastra
68xxi SIP set
Software Version 6.0 SP2 3.3.1.4305 (6730i), 4.1.0.128 (6863i, 6865i)
Ascom
i62 VoWiFi handset: Protector, Talker, Messenger
5.4.2
Ascom
Unite Connectivity Manager (UCM)
5.6.2
VMWare
vSphere
Client: Version 5.5.0 | Build 1618071 ESXi: Version 5.5.0 | Build 1623387
Tested Features This is an overview of the features tested during the interop test cycle. This is not a detailed view of the test cases. Please refer to SIP Line Side Interoperability Test Plan found in aptest manager repository for the selected run test cases and their corresponding results. Feature
Issues
Registration
Registration/Deregistration and authentication
Basic Call
Making and receiving a call
PRACK Support
Making and receiving a call with Provisional Response Acknowledgement messaging
DTMF Signal
Sending DTMF after call setup (i.e. mailbox password)
Call Hold/Retrieve
Putting a call on hold and retrieve
Call Transfer
Transferring a call to another destination
Call Forward
Forwarding calls to another destination
Call Pickup
Pickup calls ringing on another set
Conference
Conferencing multiple calls together
Redial
Last Number Redial
MWI
Message Waiting Indication
Resiliency
Basic calls through a secondary SIP server
Fax
Sending and receiving Fax including T.38
Video
Video capabilities
Teleworker
Mitel remote connectivity wit Teleworker
- No issues found
2
Feature Description
- Issues found, cannot recommend to use
- Issues found
Not tested/applicable
16-4940-00431
Ascom i62 with MiVoice MX-ONE
Resiliency The following table lists the scenarios of resilience supported by this device when connected to the MX-ONE. Device Ascom i62
- No issues found
Scenario 1 Not Tested
Scenario 2 Not Tested
Scenario 3 Not Tested
- Issues found, cannot recommend to use
Scenario 4 Not Tested
- Issues found
Note: Refer to list of device limitations and known issues later in the document for recommendations.
The various scenarios are described below. The scenario names are a convenience for understanding this section of the configuration guide. Scenario 1 - Bronze: Resiliency is achieved by utilizing the ability of DNS servers to provide multiple IP addresses against a single FQDN. This is generally achieved by using DNS SRV or A records. This scenario requires nothing from a SIP Endpoint except that it supports standard DNS behavior. Scenario 2 - Silver: The device has inherent knowledge of the primary and secondary MXONE and will switch between them if a SIP request (REGISTER, INVITE, or SUBSCRIBE) times out. Behavior will be characterized based on whether the device returns to primary MX-ONE and when this occurs. This scenario has some dependency on user action in order to detect a failure, especially if configured with a long registration expiry time, so the chance of a user experiencing a long delay making a call goes up. Scenario 3 - Gold: The behavior of the device is the same as that of scenario 2, except that the device will “ping" the currently active server with an OPTIONS request. If the OPTIONS request times out, the device will switch to the alternate server for all future requests. The intent of this scenario is to provide much faster failure detection by the device. This will allow devices to failover to their alternate MX-ONE much more quickly, and much more unnoticeably. (If the device can detect a failure of the primary MX-ONE, and can failover immediately, the chance that the user even notices a lack of service falls dramatically.) Scenario 4 - Platinum: The device will support a new SIP header designed specifically for resiliency. The P-Alternate-Server header must be included in a 200 OK or 301 Moved Permanently response. This header will include data that designates the potential servers and which server the UA must use.
3
16-4940-00431
Ascom i62 with MiVoice MX-ONE
Application Limitations and Known Issues This is a list of problems or not supported features when Ascom i62 is connected to the MiVoice MX-ONE 6.0 SP2. General recommendations are provided to avoid the limitations. Feature Call Forwarding
Problem Description Ascom i62 can support device based local diversion such as Call Forward All, Call Forward Busy, and Call Forward No Answer using handset GUI. It does not support device web configuration tool. Recommendation: Contact Ascom support for further information
Session Timer
Ascom i62 cannot set session timer. However, it would use session timer provided by MiVoice MX-ONE.
DTMF Signal
Ascom i62 does not support Inband DTMF Recommendation: Use either Outband DTMF or SIP Info
4
Redial
MiVoice MX-ONE only supports system based redial via service codes on trunk calls and not local calls. However, Ascom i62 supports device based redial.
MWI
Ascom i62 does not support Message Waiting Indicator (MWI) feature
FAX
Ascom i62 does not support FAX
Video
Ascom i62 does not support Video
Teleworker
Ascom i62 does not support connectivity via MBG/Teleworker
16-4940-00431
Ascom i62 with MiVoice MX-ONE
Network Topology This diagram shows how the testing network is configured for reference.
Mitel SIP Interoperability Network Configuration
Ascom i62 VoWiFi Handsets MiVoice MX-ONE
Aastra 68xxi SIP Phone
Layer 2 Switch
Wifi router Wireless Access Point
Ascom Unite Connectivity Manager Aastra 68xxi SIP Phone
Figure 1 – Network Topology
5
16-4940-00431
Ascom i62 with MiVoice MX-ONE
Configuration Notes This section is a description of how the SIP interoperability network was configured. These notes provide a guideline as to how a device can be configured in a customer environment and how the MiVoice MX-ONE was 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.
MiVoice MX-ONE Configuration Notes The following information shows how to configure a MiVoice MX-ONE 6.0 SP2 to connect with Ascom i62 .
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 MX-ONE 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 Extension form.
Figure 3 – Manage Extension
3. Select the telephony system that Ascom i62 will be registering the devices to (ex: MTS0), and set the extension type as IP, and select Next.
Figure 4 – Add Extension
8
16-4940-00431
Ascom i62 with MiVoice MX-ONE
4. In IP extension form, select the directory number you’ll be using for the Ascom i62 devices from the available range (ex: 1042). Ensure SIP protocol is selected. Provide a directory name and select Phone type to Other type.
Figure 5 – Add Extension – IP form 5. Select Advanced button, and enable Allow Third Party SIP Client.
Figure 6 – Add Extension – Advanced view
9
16-4940-00431
Ascom i62 with MiVoice MX-ONE
6. Select Apply.
Figure 7 –Extension – Add Result 7. When created extension is registered, additional information related to actual device would be displayed.
Figure 8 –Extension – Change Result
10
16-4940-00431
Ascom i62 with MiVoice MX-ONE
Authentication To enable registration with authentication, assign a SIP passcode that the device is require to supply during authentication. 1. In IP extension form, select Edit next to Authorization Codes.
2. Select Add in Authorization Codes form. In Authorization Codes – Add form enter Authorization code (ex: 1234) and Call Logging (CIL) code that is associated with each authorization code. Select to see more details.
3. Select Apply
4. Select Continue. Ensure that passcode selected appears in IP extension form next to Authorization Codes.
Figure 9 –Add Authorization Code
11
16-4940-00431
Ascom i62 with MiVoice MX-ONE
Hunt Group Hunt groups are added using Service Node Manager (MTS) application. Hunt Group Members could however be added using either MTS or MP application.
Add Hunt Group 1. Login to /mts 2. Select Telephony > Groups > Hunt Group 3. Select Add
4. Select Available Directory Number Interval of choice, and select Next. Could leave as default. For incoming calls to reach all hunt group members more equitably, set Member Selection Order to Longest free, as oppose to default Sequential.
Figure 10 –Add Hunt Group
12
16-4940-00431
Ascom i62 with MiVoice MX-ONE
5. Provide Hunt Group Name and select Apply
Figure 11 – Hunt Group – Add Result
6. Select Done.
Figure 12 –Updated Hunt Group List
13
16-4940-00431
Ascom i62 with MiVoice MX-ONE
Hunt Group Members Service Note Manager (MTS) Hunt group Members could be entered using MTS application. 7. Login to /mts 8. Select Telephony > Groups > Hunt Group Member
9. Select Hunt Group that you want to add members to (ex: 1041), and select 10. Enter a single or comma separated list of extension members.
11. Select Apply
Figure 13 – Add Hunt Group Members – MTS application
14
to edit.
16-4940-00431
Ascom i62 with MiVoice MX-ONE
Provisioning Manager (MP) Hunt group Members could be entered using MP application 1. Login to /mp 2. Select Services > Extensions 3. To see all added extensions, enter * to Enter Extension Number(s) field 4. Select View 5. Select extension of choice, and select
to edit.
6. In Hunt Group(s) field, enter Hunt Group number of choice (ex: 1041) 7. Select Apply
Figure 14 – Add Hunt Group Member – MP application
15
16-4940-00431
Ascom i62 with MiVoice MX-ONE
Ascom i62 Configuration Notes This section outlines how to access and configure Ascom i62 using Device Manager running on UCM. This is by no means a comprehensive guideline. Assumptions:
Wireless router is configured.
Ascom i62 is running the latest software release. Please consult Ascom guides for more information (See References).
Access Ascom i62 1. Access Unite Connectivity Manager (UCM) box, by entering URL: http:// (ex: http://192.168.101.190) on web browser of choice. 2. Enter provided login credentials to access UCM
3. Select Device Manager from the main screen of UCM.
Figure 15 – Unite Connectivity Manager
16
16-4940-00431
Ascom i62 with MiVoice MX-ONE
4. Devices tab lists all wireless devices the UCM has discovered. It also provides real time device attributes including device type, ID, software version, and associated DN.
Figure 16 – Device Manager – Devices 5. Select Numbers tab to access the list of DNs and their associated devices. In example below four Ascom i62 devices with numbers 1035 to 1038 are discovered. Notice all versions: Protector, Talker and messenger are present.
Figure 17 – Device Manager - Numbers 6. Double click on device number to access the Edit the parameters for , to modify various parameters associated with the device.
17
16-4940-00431
Ascom i62 with MiVoice MX-ONE
Ascom i62 General Media On Edit parameters for page, select VoIP > General to configure device’s general media attributes.
VoIP protocol: SIP
Codec configuration: In this example G.711 u-law is selected
Codec packetization time configuration: 20
Offer Secure RTP: No (Select Yes, when SRTP is supported)
Endpoint ID: 1036, this is the directory number configured in MiVoice MX-ONE
Retain the settings of all other fields as per default.
Figure 18 – General Media Attributes
18
16-4940-00431
Ascom i62 with MiVoice MX-ONE
Ascom i62 SIP Capabilities On Edit parameters for page, select VoIP > SIP to configure device’s SIP capabilities.
SIP transport: UDP
Primary SIP proxy: IP address or FQDN of MiVoice MX-ONE.
Listening port: 5060; local SIP port configured on MiVoice MX-ONE
SIP proxy password: Same password configured as authorization code of the DN
Send DTMF using RFC2833 or SIP INFO: select RFC2833 for Outband DTMF, otherwise select SIP INFO. Ascom i62 handsets do not support Inband DTMF.
Direct signaling: No
Retain the settings of all other fields as per default.
Figure 19 – Device SIP Capabilities
19
16-4940-00431
Ascom i62 with MiVoice MX-ONE
VoWiFi Networks In Edit parameters for , select Network to view number of WiFi network access points available. In addition, to view and modify network attributes as required. In our example, attributes of Network A is displayed below.
Figure 20 – Network A
20
16-4940-00431
Ascom i62 with MiVoice MX-ONE
In our example, attributes of Network B is displayed below.
Figure 21 – Network B
21
16-4940-00431
Ascom i62 with MiVoice MX-ONE
Ascom Messaging In Edit parameters for , select Device > Unite to review or modify UCM IP address or other messaging values as required.
Figure 22 – Ascom Messaging
22
16-4940-00431
Ascom i62 with MiVoice MX-ONE
References Ascom i62 Manuals: 1. System Planning Ascom VoWiFi System
TD 92408EN
2. System Description Ascom VoWiFi System
TD 92313EN
3. Configuration Manual: Ascom i62 VoWiFi Handset
TD92675EN
4. Unite Connectivity Manager
TD 92735EN
MiVoice MX-ONE documents: 5. MiVoice MX-ONE Installation and Maintenance Software Release 6.0 Issue 1
23
16-4940-00431
24
Ascom i62 with MiVoice MX-ONE
