MITEL SIPCoE Technical Configuration Notes Configure Inn-Phone SIP Phone for use with MCD SIP CoE
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 for use with MCD March 2012,, Trademark of Mitel Networks Corporation Copyright 2012, 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 Resiliency... 3 Device Limitations... 4 Device Recommendations... 5 Network Topology... 6 CONFIGURATION NOTES...7 3300 ICP Configuration Notes... 7 Network Requirements... 7 Assumptions for the 3300 ICP Programming... 7 Licensing and Option Selection SIP Licensing... 8 Multiline IP Set Configuration... 9 Class of Service Options... 10 SIP Device Capabilities... 14 Station Attributes settings... 16 Multiline Set Keys... 17 Reroute Assignment... 18 INN-PHONE D720 SIP PHONE SETUP NOTES... 20 Accessing... 20 configuration settings... 21 Network Configuration... 21 SIP Configuration... 23 Resiliency Configuration... 28 MULTI-PROTOCOL BORDER GATEWAY SETUP NOTES (OPTIONAL)...30 Network Requirements... 30 Assumptions for the Multi-Protocol Border Gateway Configuration... 30 ICPs... 30 Connectors SIP Configuration... 31 Adding a SIP device... 31 iii
Overview This document provides a reference to Mitel Authorized Solutions providers for configuring the Mitel 3300 ICP to host the hospitality SIP phone. 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 03/15/12 Interop with Mitel 3300 10.2.1.12_1 and Interop Status The Interop of has been given a Certification status. This device will be included in the SIP CoE Reference Guide. The status the 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. Software & Hardware Setup This was the test setup to generate a basic SIP call between the SIP device and the 3300 ICP. Manufacturer 1 Variant Software Version Mitel 3300 ICP MXe Platform 10.2.1.12_1 Mitel MBG - Teleworker 6.1.8.0 Mitel 5340, 5212 SIP Phones R8.0.01.06.02.03 Mitel 5340, 5215 IP Phones Minet, 04.01.00.15 Inn-Phone D720 912100
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 Line Side Interoperability Test Pans for detailed test cases. Feature Feature Description Basic Call Making and receiving a call DTMF Signal Sending DTMF after call setup (i.e. mailbox password) Call Hold Putting a call on hold Music-on-Hold The sounds played to other party which is held Call Transfer Transferring a call to another destination Call Forward Forwarding a call to another destination Conference Conferencing multiple calls together Redial Last Number Redial MWI Message Waiting Indication Dynamic Extension Personal Ring Group configuration Resiliency Basic calls through a Secondary SIP proxy T.38 Fax Fax Messages N/S Video Video Capabilities N/S Teleworker Mitel remote connectivity with Teleworker - No issues found 2 Issues - Issues found, cannot recommend to use - Issues found
Resiliency The following table lists the scenarios of resilience supported by this device when connected to the MCD 4.2 on the 3300 ICP. Device Scenario 1 Inn-Phone D720 - No issues found Issues found Scenario 2 Scenario 3 Not Supported Scenario 4 Not Supported - Issues found, cannot recommend use - 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: 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 behaviour. Scenario 2: The device has inherent knowledge of the primary and secondary 3300 ICPs and will switch between them if a SIP request (REGISTER, INVITE, or SUBSCRIBE) times out. Behaviour will be characterized based on whether the device returns to primary ICP 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: The behaviour 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 ICP much more quickly, and much more unnoticeably. (If the device can detect a failure of the primary ICP, and can failover immediately, the chance that the user even notices a lack of service falls dramatically.) Scenario 4: 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
Device Limitations This is a list of problems or not supported features when the hospitality SIP device is connected to the Mitel 3300ICP. Feature Music-on-Hold (MOH) Problem Description With Device Based features enabled and MOH is disabled on 3300ICP, the local MOH is played while Inn-Phone is held. I.e. there is no silence! Recommendation: none. Design specifics. Call Transfer When transfering calls blindly, call transfer fails if button Transfer pressed two times (to initite the hold and to complete the transfer). Recommendation: On Inn-Phone, press Hold button first. Then dial the number and press Transfer to complete the blind transfer. Conference 3-party conference failed when other 2 parties are SIP phones. Button "Conference" on the phone was used. While phone SIP1 stays on-hold, conference starts between only 2 parties: Inn-Phone and SIP2. Some noise is audible at InnPhone. SIP1 remains connected but there is no audio path established. Recommendation: Use Mitel IP phones (Minet) instead of SIP phones or contact Inn-Phone. Unable to establish 3-party conference when using PBX's Feature Access Code (FAC, e.g. *30). When trying to place second party on hold to dial the FAC, InnPhone switches to the first part. Thus, there is no way to dial the Conference prefix because Inn-Phone is swapping the held parties. Recommendation: None. Contact Inn-Phone. When goes on-hook first to leave the conference, other two parties are disconnected as well. Recommendation: None. Contact Inn-Phone. Personal Ring Group The phone does not dial its own number. When you dial the phone's own number, it rejects such dialing right away and does not send any INVITEs to 3300ICP. There are some scenarios e.g. when you need to make your phone Absent and dial Personal Ring Group's number of your extension (and let other members to ring); or when you need to be rerouted to the voice mail. All these scenarios failed. Recommendation: None. Contact Inn-Phone. Resiliency Scenario 2: When both profiles realm1 and realm2 are configured and active, Inn-Phone maintains two registrations simultaneously. When primary and secondary PBXs are up and running, those registrations are competing with each other. As result, the phone becomes unavailable for inbound calls time after time even when 4
registered with a primary PBX. Recommendation: Not sure that the concept of realm1, realm2 and realm3 serves to resiliency. Use resiliency Scenario 1. Device Recommendations The is recommended for deployment with Device Based In-Call Features enabled. See Sip Device Capabilities Assignment form below for more information. 5
Network Topology This diagram shows how the testing network is configured for reference. 6
Configuration Notes This section is a description of how the SIP Interop was configured. These notes should give a guideline how a device can be configured in a customer environment and how the Inn-Phone D720 was configured in our test environment. We recommend that the is configured in Device Based mode. You will configure the Device Based mode in the SIP Device Capabilities Form as described in this section. 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. 3300 ICP Configuration Notes The following steps show how to program a 3300 ICP to connect with the SIP phone. 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 the 3300 ICP Programming 7 The SIP signaling connection uses UDP on Port 5060.
Licensing and Option Selection SIP Licensing Ensure that the 3300 ICP 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. Figure 1 License and Option Selection form 8
Multiline IP Set Configuration On the Mitel 3300 ICP, a SIP device type can be programmed either in the User Configuration form or the Multiline IP Set Configuration form and it should be 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 a telephone number). The Number and User PIN must match the information in the Inn-Phone D720 phone s settings. All other field names should be programmed according to the site requirements or left at default. Figure 2 Multiline IP Sets form 9
Class of Service Options The Class of Service Options 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 by the Station Service Assignment form for the SIP devices. Many different options may be required for your site deployment, but these are the options that are required to be changed from the default for a Generic SIP Device to work with the 3300 ICP. 10 Conference Call set to Yes HCI/CTI/TAPI Call Control Allowed set to Yes HCI/CTI/TAPI Monitor Allowed set to Yes Message Waiting set to Yes Public Network Access via DPNSS set to Yes Auto Campon Timer is blanked (no value)
11
12
Figure 3 Class of Service Options form 13
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 similar to 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 Inn-Phone D720 phone device. Ensure that Replace System based with Device based In-Call Feature is set to Yes. NOTE: By default, supports Reliable Provisional Responses. So, when this feature is required, you can enable it in SIP Device Capabilities form. 14
Figure 4 SIP Device Capabilities Assignment form 15
Station Attributes settings Use the Station Attributes form to assign the previously configured Class of Service and SIP Device Capability number to each of the phones in the 3300. This form utilizes Range Programming. Select the phone number and then select Change. Enter the previously configured SIP Device Capability number and Class of Service for Day, Night 1 & Night 2. Figure 5 Station Attributes form 16
Multiline Set Keys Use the Multiline Set Keys form to assign the line type, ring type, and directory number to each line selected on the device. The has 2 line keys. For the tests, only 2 calls per line were programmed as per Figure 6. Figure 6 Multiline Set Keys form 17
Reroute Assignment Mitel recommends that call forwarding is programmed using the Call rerouting forms of the 3300. Call forwarding programmed from the has also been tested but we suggest that administrators use Call Rerouting. Call Rerouting is configured at the system to allow for extensions to forward on different conditions to different extensions, i.e. forward to voicemail when no answer. The following is a description how to configure call rerouting and does not necessarily show how this Inn-Phone D720 was programmed. Program the Call Rerouting First Alternative Assignment form with the destination of the call forwarding and the options (Normal, This, Last). Please see the 3300 help files for more info. There is also a Call Rerouting Second Alternative Assignment form for more complicated forwarding needs. Figure 7 Call Rerouting First Alternative form If any Call Forwarding Always is required then the Call Rerouting Always Alternative Assignment form would need to be programmed. 18
Figure 8 Call Rerouting form Use the Alternative Numbers from the previous forms and fill out the Call Rerouting Assignment form for the programmed extension. 19
SIP Phone Setup Notes The following steps show how to program the hospitality SIP Phone to interconnect with the 3300 ICP In our test environment, we configured through the web interface. Although web interface allows defining TFTP server, we did not find instructions or configuration files patterns on how to use this tool. Accessing has two RJ-45 ports labeled WAN Port and LAN Port. Connect Ethernet cable to WAN Port. NOTE: LAN Port of could be configured as DHCP server for other devices connected to this port. In our environment, we did not use this feature. To access the phone via web browser, you need to know its IP address. You can check the IP address on the phone s display, when it is connected to the network and booted: - On the phone, press Menu button. Using Up and Down arrow buttons, navigate to menu option 4 Network; Press Enter button; In Network menu, navigate to option 5 Status; Press Enter button; Take a note of IP address assigned to the phone, e.g. W192.168.101.142. NOTE: Use Menu button to leave the current menu option and jump one step up. Optionally, you can manually configure static WAN IP address of the phone. To do this: - On the phone, press Menu button. Navigate to menu option 4 Network; Press Enter button; In Network menu, select option 1 WAN Setup; Press Enter button; Configure settings in menus IP Type and Fixed IP Settings as required. To access through the web interface, open a web browser, e.g. Internet Explorer, and type the phone s IP address following the port 9999 in the address bar, like: http://<ip address>:9999 Enter user name and password when prompted: root and test respectively (see Figure 9). 20
Figure 9 Web interface login configuration settings Network Configuration When is accessed, navigate to Network->WAN (see Figure 10). You may need to set the static IP address and configure other network settings, e.g. gateway, DNS s IP address. In our test environment, we assigned static IP address to. If you require IP addresses assigned by DHCP, then select option DHCP Client NOTE: Please, note that DNS server s IP address could remain static and needs to be configured separately even though DHCP Client is selected. Make sure that DNS Type is set accordingly (see Figure 10). 21
Figure 10 WAN Settings Navigate to Network->LAN (see Figure 11). If additional IP devices need to be connected to the network, you can enable LAN port of and configure the IP address range as required. 22
Figure 11 LAN Settings SIP Configuration Navigate to SIP Settings->Service Domain. Select the Realm number and configure SIP settings according to the site environment (see Figure 12). Settings for User Name and Register Password must match those created earlier in Mitel 3300ICP. Domain and Proxy servers on this page represent Mitel 3300ICP. Alternatively you may use FQDN (DNS names) for Domain and Proxy servers. 23
Figure 12 SIP domain settings Navigate to SIP Settings->Port Ensure that default setting for SIP Port is 5060 (see Figure 13). 24
Figure 13 SIP port setting Navigate to SIP Settings->Codec Arrange the codecs priority according to the site requirements (see Figure 14). You may also need to set RTP packets rate for G.711 and G.729 codecs (default value is 20ms). 25
Figure 14 Codec priority settings Navigate to SIP Settings->Codec ID (see Figure 15) Ensure that ID for RFC2833 is set accordingly (101 in our test environment). 26
Figure 15 ID setting for RFC2833 Navigate to SIP Settings->Other On this page, select SIP Server type as shown in Figure 16. To provide resiliency as of Scenario 1 (configuration will be discussed later), when booting up, may send so-called A-record or SRV-record requests to DNS server. Depending on your DNS server configuration you can identify here what type of request should be sent to DNS server. By default, A-record is sent out. As shown in Figure 16, in our test environment we have configured SRV-record. 27
Figure 16 Other setting Resiliency Configuration To provide resiliency behavior as in Scenario 1, configure the parameters for Domain and Proxy server as shown in Figure 17. In this example, sipint4 is the DNS name of primary SIP proxy (3300ICP) and sipint2 is the secondary SIP proxy (3300ICP). NOTE: Before configuring this parameter, make sure that DNS server correctly resolves the names of both SIP proxies to IP addresses! The order, in which the SIP proxies IP addresses are resolved, is also important! To check it, use the command in command shell: nslookup sipint4sipint2.sipcoe.mitel.com As we noticed in previous section, by default uses an A-record for DNS lookup. Enable DNS SVR as per Figure 16, if DNS server supports SRV-records. 28
Figure 17 SIP settings for resiliency 29
Multi-Protocol Border Gateway Setup Notes (Optional) The following steps show how to program the Multi-Protocol Border Gateway (MBG) server to allow connections between the and the 3300 ICP for teleworking. Network Requirements Please, refer to the Multi-Protocol Border Gateway Engineering guidelines for further information. Assumptions for the Multi-Protocol Border Gateway Configuration 3300 ICP configuration completed as per instructions in previous section. The SIP signaling connection between the 3300 ICP and the Multi-Protocol Border Gateway server uses UDP on Port 5060. Multi-Protocol Border Gateway server installed and configured for SIP client support. ICPs On the ICPs tab, click Add an ICP and enter ICP information (name, IP address, type). For newly created ICP, select the Default for SIP and click Update. In this example, the 3300 ICP with IP address 192.168.10.20 is the default SIP ICP: Figure 18 ICP configuration 30
Connectors SIP Configuration Enable SIP support on MBG as follows: - On the Connectors tab, click SIP Support and then click Edit. - Check the SIP connector enabled check box. - Click Save (see Figure 19) Figure 19 Enable SIP support Adding a SIP device We need to add to the MBG s list of supported devices. On the Devices tab, click SIP Devices and then click Add a SIP Device. Enter the data as shown in Figure 20. For most standard configurations Set-side and ICP-side user names and passwords are the same as they were configured in Mitel 3300ICP for this user. At, in Service Domain section, indicate the IP address of MBG as the PBX s address. Reboot. If teleworker configuration was programmed correctly, should pass through MBG and be registered on 3300ICP smoothly. 31
Figure 20 Add a SIP device 32
33