MITEL SIP CoE Technical Configuration Notes Configure to use with MiVoice Business 8.0 SP3 FEBRUARY 2018 SIP COE HO883 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 to use with MiVoice Business 8.0 SP3 March 2018 HO883, Trademark of Mitel Networks Corporation Copyright 2018, Mitel Networks Corporation All rights reserved ii
Table of Contents OVERVIEW... 1 Interop History... 1 Interop Status... 1 Software & Hardware Setup... 1 Tested Features... 2 Device Limitations and Known Issues... 3 Network Topology... 4 CONFIGURATION NOTES... 5 MiVoice Business Configuration Notes... 5 Network Requirements... 5 Assumptions for the MiVoice Business Programming... 5 Licensing and Option Selection SIP Licensing... 6 Multiline IP Set Configuration... 7 Class of Service Assignment... 10 SIP Device Capabilities... 17 Station Attributes... 19 Enabling Voice Encryption in MIVB... 21 Configuration Notes... 21 Accessing Tesira audio system... 21 Tesira system VoIP configuration settings... 22 iii
Overview This document provides a reference to Mitel Authorized Solutions providers for configuring the MiVoice Business to host the. 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 May 28, 2013 Interop with Mitel 3300ICP 12.0.0.49 (MCD 6.0) and Biamp Tesira audio system 2 December, 2015 Re-fresh with MIVB 7.2 and Biamp Tesira audio system 3 February, 2018 Interop with MiVoice Business 8.0 SP3 (14.0.2.26) and Interop Status The Interop of with MiVoice Business has been given a Certification status. This device will be included in the SIP COE Reference Guide. The status the set achieved is The most common certification which means the device/service 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. Although the Interop testing was executed using the, but this certification is applicable to any Biamp Tesira SERVER running the same firmware as tested. Software & Hardware Setup The table below provides the hardware and software specifications used. Manufacturer Variant Software Version Mitel MiVoice Business 8.0 SP3 (14.0.3.19) Software 3.4.0.22 Firmware 3.4.1.2 Main Operating Version 3.0.7.8 Mitel 68xx SIP Set 5.0.0.1017 Mitel 69xx Minet Phone Main Load: 01.03.00.099 1
Tested Features This is an overview of the features tested during the Interop test cycle and not a detailed view of the test cases. Feature Feature Description Execution Issues Register/Deregister Basic Call PRACK Support Call Hold/Retrieve Call Transfer Call Forward (ESM) Conference Call Park DTMF Voicemail Call Forwarding Video Fax Teleworker Personal Ring Group Different Port Resiliency TLS/SRTP Registration/Deregistration (authentication) with the MiVoice Business Making and receiving a call Making and receiving a call with Provisional Response Acknowledgement messaging Putting a call on hold/retrieve w/o MOH Transferring a call to another destination Forwarding calls to another destination using ESM Conferencing multiple calls together Call Park to other DN Out of Band using RFC 2833 / Inband Access Voice mail Forward calls using device-based setup Video calls between endpoints Sending and receiving Fax Mitel remote connectivity with Teleworker Multiple sets ringing when one number dialed Device being able to support a different local SIP port Basic calls through a secondary SIP server Basic Calls with encrypted signaling and media - No issues found - Issues found, cannot recommend to use - Issues found Not tested/applicable 2
Device Limitations and Known Issues This is a list of issues or not supported features using the with MiVoice Business. Features Problem Description Resiliency TLS/SRTP De-Registration Timer Resiliency is not supported by device Recommendation: Contact Biamp for further information Tested using Biamp and 3 rd party SIP phones device doesn t send Register with Expire 0 Recommendation: Contact Biamp for further information Wideband Codec device does not support g722.1 Recommendation: Contact Biamp for further information Device based CF device doesn t support Device based CF Recommendation: Contact Biamp for further information In-Band DTMF Three Way Conference Codec Negotiation other than Biamp Preferred Tested two extensions. MIVB doesn t support In-band IVR If the negotiated codec happens to be different than what is offered as preferred by Biamp, there will be distorted sound Recommendation: Contact Biamp for further information TLS Conference Biamp as participant There is no RTP from Biamp. This is only seen while Mitel IP phone calls Biamp and invites the other party in to conference Recommendation: Contact Biamp for further information 3
Network Topology This diagram shows how the testing network is configured for reference. Figure 1 Network Topology 4
Configuration Notes This section is a description of how the SIP Interop network was configured. These notes provide a guideline as to how a device can be configured in a customer environment and how the MiVoice Business 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 Business Configuration Notes The following steps show how to configure a MiVoice Business to host Biamp Tesira SERVER-IO AVB 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 Mitel 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 the MiVoice Business Programming The SIP signaling connection uses UDP on port 5060. The SIP signaling connection uses TLS on port 5061 5
Licensing and Option Selection SIP Licensing Ensure that the MiVoice Business is equipped with enough IP Users licenses for the connection of SIP end points. This can be verified within the License and Option Selection form. See Figure 2. Figure 2 License and Option Selection 6
Multiline IP Set Configuration On the MiVoice Business, a SIP device can be programmed either in the User Configuration form or the Multiline IP Set Configuration form and are programmed as a Generic SIP Phone. Enterprise Manager can also be used to provision where this application is installed. The User PIN is the SIP authentication password and the Number is the Directory Number (DN is a telephone number). The Number and User PIN must match the information in the settings. All other field names should be programmed per the site requirements or left at default. See an example in below Figures 3,4,5 Figure 3 Multiline IP Set Configuration 7
Figure 4 Multiline IP Set Configuration Continue 8
Figure 5 Multiline IP Set Configuration Continue 9
Class of Service Assignment The Class of Service Options form is used to create or edit the Class of Service and specify its options. Classes of Service, identified by Class of Service numbers, are referenced by the Station Attributes form for the SIP device. Many different options may be required for your site deployment, but the options below are required to be changed from the default for a Generic SIP Device to work with the MiVoice Business. (See example in Figure 6,7,8,9) Under General tab: Navigate to section Campon and ensure: Auto Campon Timer is blanked (no value) Navigate to section HCI and ensure: HCI/CTI/TAPI Call Control Allowed set to Yes HCI/CTI/TAPI Monitor Allowed set to Yes Navigate to section Trunk and ensure: Public Network Access via DPNSS set to Yes Under Advanced tab: Navigate to section Conference and ensure: Conference Call set to Yes Navigate to section Message Waiting and ensure: Message Waiting set to Yes 10
Figure 6 Class of Service 11
Figure 7 Class of Service Continue 12
Figure 8 Class of Service Continue 13
Figure 9 Class of Service Continue Advanced Figure 9A Class of Service Continue 14
Figure 9B Class of Service Continue Figure 9C Class of Service Continue 15
Figure 9D Class of Service Continue Figure 9E Class of Service Continue 16
SIP Device Capabilities This form provides configuration options that can be applied to various types of SIP devices. The association between the SIP device and the form is like how the Class of Service options work. The SIP Device Capabilities number provides a SIP profile that can be applied to particular SIP devices to allow for alternate capabilities as recommended through the Mitel interop process. In the SIP Device Capabilities form, program a SIP Device Capabilities Number for the Biamp Tesira SERVER-IO AVB. The form below depicts how the options were set for the interop testing. Figure 10 SIP Device Capabilities - Basic 17
Set SDP Options as shown in Figure 11. Figure 11 SIP Device Capabilities SDP Options Set Signaling and Header Manipulation as shown in Figure 12. Figure 12 SIP Device Capabilities Signaling and Header Manipulation Settings for the Timers are important part for the SIP devices configuration. Set Registration Period, Subscription Period and Session Timer to match those configured in 18
the and per the site requirements. See an example in Figure 13. The settings on all other tabs of SIP Device Capabilities form remain unchanged, at their default values. Figure 13 SIP Device Capabilities Timers Station Attributes Use the Station Attributes form to assign the previously configured Class of Service and SIP Device Capability number to each of the in the MiVoice Business. This form utilizes Range Programming. Select the s number then select Change. Enter the previously configured SIP Device Capability number and Class of Service for Day, Night 1 & Night 2 User and Devices Advanced Configuration Station Attributes. See an example in Figure 14 below. 19
20
Enabling Voice Encryption in MIVB Figure 14 Station Attributes System Properties System Feature Settings System Options -> Last 2 settings Set Voice Encryption Enabled and Voice/Video SRTP Encryption Enabled to YES as in Figure 15 Figure 15 System Option Enabling Voice Encryption Configuration Notes The following steps show how to program VoIP settings in Biamp Tesira audio system to interconnect with the MIVB 8.0 SP3 More detailed instructions and guidelines for the configuration settings of Biamp Tesira audio system we strongly recommend contacting the Professional Services department at Biamp Systems. The configuration settings below are the main reference points and by any means could not be considered as the comprehensive configuration instructions. Accessing Tesira audio system In order to control the Tesira server, you need to download the control software. Ask Biamp representative from where you can obtain this software. Once installed, you will need to register this software and activate it. Tesira audio system, which supports VoIP connections, has two Ethernet cards installed. Plug network cable into RJ-45 socket labeled Primary on the server s back panel. Read the IP address of this connection in the Network Parameters menu at the front display of Tesira. You will use this IP address exclusively for connecting to and controlling the Tesira audio system. Also, on Tesira s back panel, there is another RJ-45 socket labeled VoIP connections only. Make sure that you connect second Ethernet cable to this socket. Tesira audio system communicates with Mitel MIVB through this connection. 21
Tesira audio system is configured with.tmf design files. The.tmf file creation procedure is out of scope of this document. Nevertheless, we would just like to pay your attention on the following: -.tmf file is built from the blocks as shown in Figure 16. Make sure that blocks VoIP Control/Status and VoIP Dialer are added to the file; - Brand new instance of.tmf file needs to be compiled first. Use options Compile or Compile All in the Tesira s controlling software to do this; - You can edit.tmf design file only when controlling software is disconnected from Tesira server. To disconnect, use tool bar s button Disconnect From System in the upper left corner of the controlling software (see Figure 16); - Any changes in Tesira s configuration you made are not taking in effect immediately. To enable them, you have to save.tmf file and execute Send Configuration procedure. To initiate configuration sending, use tool bar s button Send Configuration in the upper left corner of the controlling software (see Figure 16); Figure 16 Example of basic.tmf design file and access to the settings Tesira system VoIP configuration settings Setting SNTP server For Tesira s stability when connected to MiVB 8.0, it is important to configure SNTP server. To do this, 22
- Disconnect the controlling software from Tesira server; - Click VoIP Control/Status block and navigate to DSP Properties tab on the right; - Click SNTP Address field and enter the address of your SNTP server. See Figure 16 for details. VoIP Line Properties Since Tesira emulates SIP devices behavior, we need to configure SIP settings as we would do for any SIP phone connected to Mitel MIVB. To access these settings: - Disconnect the controlling software from Tesira server; - Click VoIP Control/Status block and navigate to DSP Properties tab on the right; - Click in the field adjacent to Line Properties. See Figure 16 for details. In VoIP Line Properties screen, select Line1 and then select Protocol tab. Configure the SIP settings as shown in Figure 17. In this example, - User Name and Authentication Password must match the settings previously configured in Mitel MIVB for this extension - Select Generic for Proxy Vendor - Proxy Address represents IP address of Mitel MIVB (3300 ICP) - Configure the timer value for Registration Expiration accordingly matching the value in Mitel MIVB - Enable Session Timer and PRACK support - Configure Local Dial Plan in accordance with the customer s site requirements. NOTE: To enable SRTP, the transport protocol in Tesira should be changed to TLS. Switch to Line 2 settings and configure them in the same way as Line 1. Click OK to accept the settings. 23
Figure 17 VoIP Line Properties 24
VoIP Dialer When connected to MiVB, VoIP Dialer block should be added to.tmf design file as shown in Figure 16. VoIP Dialer allows Tesira to execute the basic telephony operations in the same way as standard telephone set would do. In our lab environment, we have configured Tesira audio system with two line. so, in VoIP Dialer, switch between Line 1 and Line 2 keypads to control the functionality of either line. See example in Figure 18. Figure 18 VoIP Dialer 25
26