+ All Categories
Home > Documents > Configure Ascom IP-DECT 8.0.9 to use with MiVoice MX-ONE …€¦ · MITEL MITEL – SIP CoE...

Configure Ascom IP-DECT 8.0.9 to use with MiVoice MX-ONE …€¦ · MITEL MITEL – SIP CoE...

Date post: 01-Jul-2018
Category:
Upload: dangthu
View: 272 times
Download: 4 times
Share this document with a friend
24
MITEL SIP CoE Technical Configuration Notes Configure Ascom IP-DECT 8.0.9 to use with MiVoice MX-ONE 6.0 SP2 FEBRUARY 2016 SIP COE 16-4940-00427 TECHNICAL CONFIGURATION NOTES
Transcript
Page 1: Configure Ascom IP-DECT 8.0.9 to use with MiVoice MX-ONE …€¦ · MITEL MITEL – SIP CoE Technical Configuration Notes –SIP CoE Technical Configuration Notes Configure Ascom

MITEL – SIP CoE

Technical Configuration Notes

MITEL – SIP CoE

Technical Configuration Notes

Configure Ascom IP-DECT 8.0.9 to use with

MiVoice MX-ONE 6.0 SP2

FEBRUARY 2016

SIP COE 16-4940-00427

TECHNICAL CONFIGURATION NOTES

Page 2: Configure Ascom IP-DECT 8.0.9 to use with MiVoice MX-ONE …€¦ · MITEL MITEL – SIP CoE Technical Configuration Notes –SIP CoE Technical Configuration Notes Configure Ascom

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 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 IP-DECT 8.0.9 to use with MiVoice MX-ONE 6.0 SP2 February 2016 – 16-4940-00427

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

All rights reserved

Page 3: Configure Ascom IP-DECT 8.0.9 to use with MiVoice MX-ONE …€¦ · MITEL MITEL – SIP CoE Technical Configuration Notes –SIP CoE Technical Configuration Notes Configure Ascom

Table of Contents

iii

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 IP DECT Configuration Notes ............................................................................... 16

General .......................................................................................................................................... 16

REFERENCES ........................................................................................................ 19

Page 4: Configure Ascom IP-DECT 8.0.9 to use with MiVoice MX-ONE …€¦ · MITEL MITEL – SIP CoE Technical Configuration Notes –SIP CoE Technical Configuration Notes Configure Ascom
Page 5: Configure Ascom IP-DECT 8.0.9 to use with MiVoice MX-ONE …€¦ · MITEL MITEL – SIP CoE Technical Configuration Notes –SIP CoE Technical Configuration Notes Configure Ascom

16-4940-00427 Ascom IP-DECT with MiVoice MX-ONE

1

Overview This document provides a reference to Mitel Authorized Solutions providers for configuring the MiVoice MX-ONE 6.0 SP2 to host Ascom IP-DECT 8.0.9. 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 Feb 01, 2016 Initial Interop of Ascom IP-DECT 8.0.9 with MiVoice MX-ONE 6.0 SP2

Interop Status

This Interop of Ascom IP-DECT with MiVoice MX-ONE has been given a Certification status. This device will be included in the SIP CoE Reference Guide. The status Ascom IP-DECT 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

Page 6: Configure Ascom IP-DECT 8.0.9 to use with MiVoice MX-ONE …€¦ · MITEL MITEL – SIP CoE Technical Configuration Notes –SIP CoE Technical Configuration Notes Configure Ascom

16-4940-00427 Ascom IP-DECT with MiVoice MX-ONE

2

Software & Hardware Setup

The table below provides the hardware and software specifications used in interop of Ascom IP-DECT with MiVoice MX-ONE.

Manufacturer Variant Software Version

Mitel MiVoice MX-ONE Virtual 6.0 SP2

Aastra 68xxi SIP set 3.3.1.4305 (6730i),

4.1.0.128 (6863i, 6865i)

Ascom IP-DECT Base Station IPBS2: 8.0.9, Bootcode: 8.0.9

HW:IPBS2-A3/1B1

Ascom IP-DECT handsets: d81-Protector, d62-Protector, d62-talker

4.3.17

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 Feature Description 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 - Issues found, cannot recommend to use - Issues found Not tested/applicable

Page 7: Configure Ascom IP-DECT 8.0.9 to use with MiVoice MX-ONE …€¦ · MITEL MITEL – SIP CoE Technical Configuration Notes –SIP CoE Technical Configuration Notes Configure Ascom

16-4940-00427 Ascom IP-DECT with MiVoice MX-ONE

3

Resiliency

The following table lists the scenarios of resilience supported by this device when connected to the MX-ONE.

Device Scenario 1 Scenario 2 Scenario 3 Scenario 4

Ascom IP-DECT Not Tested Not Tested Not Tested Not Tested

- No issues found - Issues found, cannot recommend to use - 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 MX-ONE 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.

Page 8: Configure Ascom IP-DECT 8.0.9 to use with MiVoice MX-ONE …€¦ · MITEL MITEL – SIP CoE Technical Configuration Notes –SIP CoE Technical Configuration Notes Configure Ascom

16-4940-00427 Ascom IP-DECT with MiVoice MX-ONE

4

Application Limitations and Known Issues

This is a list of problems or not supported features when Ascom IP-DECT is connected to the MiVoice MX-ONE 6.0 SP2. General recommendations are provided to avoid the limitations.

Feature Problem Description

Basic Call Display Ascom IP-DECT, by design only displays SIP Calling Name and not the number for incoming calls.

Basic Call Codec Ascom IP-DECT changes the media attribute 110 from PCMU/16000 to PCMU/8000 instead of using media attribute 0 (PCMU/8000).

Recommendation: Contact Ascom Support for further information and updates. Ticket #: IPDECT-2303

DTMF Signal Ascom IP-DECT does not support Inband DTMF

Recommendation: Use SIP INFO whenever possible. Contact Ascom Support for further information and updates. Ticket #: IPDECT-2286

Port Support Ascom IP-DECT, by design can only change ports when both sending and receiving ports are changed and set to same value.

Registration Ascom IP-DECT GUI does not notify user that after changing registration time, DECT master must be restarted.

Recommendation: Contact Ascom Support for further information and updates. Ticket #: IPDECT-2304

Redial MiVoice MX-ONE only supports redial on trunk calls and not local calls. However, Ascom IP-DECT supports device based redial. Click the Call button to display the latest list of numbers dialed. Select number from the list to redial.

Conference Ascom IP-DECT cannot host a conference, but could attend as conference participant.

FAX Ascom IP-DECT does not support FAX

Video Ascom IP-DECT does not support Video

Teleworker Ascom IP-DECT does not support connectivity via MBG/Teleworker

Page 9: Configure Ascom IP-DECT 8.0.9 to use with MiVoice MX-ONE …€¦ · MITEL MITEL – SIP CoE Technical Configuration Notes –SIP CoE Technical Configuration Notes Configure Ascom

16-4940-00427 Ascom IP-DECT with MiVoice MX-ONE

5

Network Topology

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

Figure 1 – Network Topology

MiVoice MX-ONE

Mitel SIP Interoperability

Network Configuration

Layer 2

Switch

Aastra 68xxi SIP Phone Aastra 68xxi

SIP Phone

Ascom IP-DECT

Base Station IPBS2

Ascom d81

IPDECT

Handset

Ascom d62

IPDECT

Handset

Page 10: Configure Ascom IP-DECT 8.0.9 to use with MiVoice MX-ONE …€¦ · MITEL MITEL – SIP CoE Technical Configuration Notes –SIP CoE Technical Configuration Notes Configure Ascom

16-4940-00427 Ascom IP-DECT with MiVoice MX-ONE

6

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 IP-DECT .

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 <1%, jitter < 30ms, one-way delay < 80ms).

Assumptions for MiVoice MX-ONE Programming

The SIP signaling connection uses UDP on Port 5060

Page 11: Configure Ascom IP-DECT 8.0.9 to use with MiVoice MX-ONE …€¦ · MITEL MITEL – SIP CoE Technical Configuration Notes –SIP CoE Technical Configuration Notes Configure Ascom

16-4940-00427 Ascom IP-DECT with MiVoice MX-ONE

7

System Overview

MiVoice MX-ONE 6.0 is a native SIP soft switch for the plain IP environment. It supports legacy protocols and TDM based lines through the use of hardware based media gateways.

Figure 2 – MiVoice MX-ONE System Overview

There are two user interfaces for configuration and management of MiVoice MX-ONE

1. Provisioning Manager (previously know as Manager Provisioning) – MP

User interface for configuration and management of the Telephony system

URL: <MiVoice MX-ONE IP address>/mp

2. Service Node Manager (previously known Manager Telephony System) – MTS

User interface for managing the entire MX-ONE network

URL: <MiVoice MX-ONE IP address>/mts

Page 12: Configure Ascom IP-DECT 8.0.9 to use with MiVoice MX-ONE …€¦ · MITEL MITEL – SIP CoE Technical Configuration Notes –SIP CoE Technical Configuration Notes Configure Ascom

16-4940-00427 Ascom IP-DECT with MiVoice MX-ONE

8

Adding SIP Extension

To program Ascom IP-DECT device on the MiVoice MX-ONE,

1. Login to Provisioning Manager (MP) user interface.

2. Go to the Services > Extension form.

Figure 3 – Manage Extension

3. Select the telephony system that Ascom IP-DECT will be registering the DECT devices to (ex: MTS0), and set the extension type as IP, and select Next.

Figure 4 – Add Extension

Page 13: Configure Ascom IP-DECT 8.0.9 to use with MiVoice MX-ONE …€¦ · MITEL MITEL – SIP CoE Technical Configuration Notes –SIP CoE Technical Configuration Notes Configure Ascom

16-4940-00427 Ascom IP-DECT with MiVoice MX-ONE

9

4. In IP extension form, select the directory number you’ll be using for the Ascom IP-DECT 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

Page 14: Configure Ascom IP-DECT 8.0.9 to use with MiVoice MX-ONE …€¦ · MITEL MITEL – SIP CoE Technical Configuration Notes –SIP CoE Technical Configuration Notes Configure Ascom

16-4940-00427 Ascom IP-DECT with MiVoice MX-ONE

10

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

Page 15: Configure Ascom IP-DECT 8.0.9 to use with MiVoice MX-ONE …€¦ · MITEL MITEL – SIP CoE Technical Configuration Notes –SIP CoE Technical Configuration Notes Configure Ascom

16-4940-00427 Ascom IP-DECT with MiVoice MX-ONE

11

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

Page 16: Configure Ascom IP-DECT 8.0.9 to use with MiVoice MX-ONE …€¦ · MITEL MITEL – SIP CoE Technical Configuration Notes –SIP CoE Technical Configuration Notes Configure Ascom

16-4940-00427 Ascom IP-DECT with MiVoice MX-ONE

12

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 <MiVoice MX-ONE IP>/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

Page 17: Configure Ascom IP-DECT 8.0.9 to use with MiVoice MX-ONE …€¦ · MITEL MITEL – SIP CoE Technical Configuration Notes –SIP CoE Technical Configuration Notes Configure Ascom

16-4940-00427 Ascom IP-DECT with MiVoice MX-ONE

13

5. Provide Hunt Group Name and select Apply

Figure 11 – Hunt Group – Add Result

6. Select Done.

Figure 12 –Updated Hunt Group List

Page 18: Configure Ascom IP-DECT 8.0.9 to use with MiVoice MX-ONE …€¦ · MITEL MITEL – SIP CoE Technical Configuration Notes –SIP CoE Technical Configuration Notes Configure Ascom

16-4940-00427 Ascom IP-DECT with MiVoice MX-ONE

14

Hunt Group Members

Service Note Manager (MTS)

Hunt group Members could be entered using MTS application.

7. Login to <MiVoice MX-ONE IP>/mts

8. Select Telephony > Groups > Hunt Group Member

9. Select Hunt Group that you want to add members to (ex: 1041), and select to edit.

10. Enter a single or comma separated list of extension members.

11. Select Apply

Figure 13 – Add Hunt Group Members – MTS application

Page 19: Configure Ascom IP-DECT 8.0.9 to use with MiVoice MX-ONE …€¦ · MITEL MITEL – SIP CoE Technical Configuration Notes –SIP CoE Technical Configuration Notes Configure Ascom

16-4940-00427 Ascom IP-DECT with MiVoice MX-ONE

15

Provisioning Manager (MP)

Hunt group Members could be entered using MP application

1. Login to <MiVoice MX-ONE IP>/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

Page 20: Configure Ascom IP-DECT 8.0.9 to use with MiVoice MX-ONE …€¦ · MITEL MITEL – SIP CoE Technical Configuration Notes –SIP CoE Technical Configuration Notes Configure Ascom

16-4940-00427 Ascom IP-DECT with MiVoice MX-ONE

16

Ascom IP DECT Configuration Notes

This section outlines the basic instructions on how to program Ascom IP-DECT to interconnect with MiVoice MX-ONE. This is by no means a comprehensive guideline. We assume that Ascom IP-DECT is running the latest software release.

Please consult Ascom guides for more information (See References).

General Configuration

Ascom IP-DECT base station supports web interface for configuration and administration. Under General > Info, you can find version and serial number of IP-DECT Base station.

Figure 15 – General Configuration

Users

Under the Users tab, select show to see the list of extensions and devices registered with MiVoice MX-ONE. In example below, DUT1, an Ascom d81 IP-DECT set is registered with extension 1026 on MiVoice MX-ONE.

Figure 16 – Users setup

Page 21: Configure Ascom IP-DECT 8.0.9 to use with MiVoice MX-ONE …€¦ · MITEL MITEL – SIP CoE Technical Configuration Notes –SIP CoE Technical Configuration Notes Configure Ascom

16-4940-00427 Ascom IP-DECT with MiVoice MX-ONE

17

DECT Configuration

Select Configuration> DECT to review and make changes to DECT system as required.

Most important forms are System, Suppl. Serv., and Master for our testing.

System

Use System form to setup authentication credentials, preferred Codec, and packetization rate. Ascom IP-DECT supports both G.711 (A-law and µ-law) and G.729 codec.

Figure 17 – DECT System Settings

Supplementary Services

Use Supplementary Services form to enable device based features using feature access

codes (FAC).

Figure 18 – DECT Supplementary Services

Page 22: Configure Ascom IP-DECT 8.0.9 to use with MiVoice MX-ONE …€¦ · MITEL MITEL – SIP CoE Technical Configuration Notes –SIP CoE Technical Configuration Notes Configure Ascom

16-4940-00427 Ascom IP-DECT with MiVoice MX-ONE

18

Master tab

On Master form,

1. Set protocol as SIP/UDP

2. Provide MiVoice MX-ONE IP address as proxy (ex: 192.168.101.204)

3. To enable outband DTMF, select Allow DTMF Through RTP, and de-select Send Inband DTMF. Alternatively, to enable Inband DTMF, de-select Allow DTMF Through RTP, and select Send Inband DTMF. When neither is selected, SIP INFO would be used.

4. Set Registration timer. Minimum acceptable timer is 300 sec.

Figure 19 – DECT Master

Page 23: Configure Ascom IP-DECT 8.0.9 to use with MiVoice MX-ONE …€¦ · MITEL MITEL – SIP CoE Technical Configuration Notes –SIP CoE Technical Configuration Notes Configure Ascom

16-4940-00427 Ascom IP-DECT with MiVoice MX-ONE

19

References

Ascom IP-DECT Installation and Operation Manuals:

3. IP-DECT Base Station & IP-DECT Gateway (software version 8.0.x) TD 92579EN

4. System Description Ascom IP-DECT system TD 92375EN

5. System Planning Ascom IP-DECT TD 92422GB

MiVoice MX-ONE documents:

6. MiVoice MX-ONE Installation and Maintenance Software Release 6.0 Issue 1

7. Call Park Pool – Operational Directions 2011 145-15431-ANF90114

Page 24: Configure Ascom IP-DECT 8.0.9 to use with MiVoice MX-ONE …€¦ · MITEL MITEL – SIP CoE Technical Configuration Notes –SIP CoE Technical Configuration Notes Configure Ascom

16-4940-00427 Ascom IP-DECT with MiVoice MX-ONE

20


Recommended