MITEL SIP CoE Technical Configuration Notes Configure the Mitel 3300 MCD 4.0 for use with XO Communications SIP CoE 10-4940-00105
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 the Mitel 3300 MCD 4.0 for use with XO Communications SIP Trunking January 2010, 10-4940-00105, Trademark of Mitel Networks Corporation Copyright 2010, 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 3300 MCD Configuration Notes...5 Network Requirements... 5 Assumptions for the 3300 MCD Programming... 5 Licensing and Option Selection SIP Licensing... 6 Class of Service Assignment... 7 Network Element Assignment... 9 Network Element Assignment (Proxy)... 10 Trunk Service Assignment... 11 SIP Peer Profile... 12 SIP Peer Profile Assignment by Incoming DID... 15 Digit Modification Number... 16 Route Assignment... 17 ARS Digits Dialed Assignment... 18 T.38 Fax Configuration... 19 Zone Assignment... 20 Mitel Border Gateway Configuration Notes...21 iii
Overview This document provides a reference to Mitel Authorized Solutions providers for configuring the Mitel 3300 MCD to connect to XO Communications. 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 December 18, 2009 Initial Interop with Mitel 3300 10.0.1.23 and XO Communications SIP trunk Interop Status The Interop of XO Communications trunk line has been given a Certification status. This service provider or trunking device will be included in the SIP CoE Reference Guide. The status XO Communications trunk line achieved is: The most common certification which means XO Communications SIP trunk 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 XO Communications trunk line and the 3300 MCD. Manufacturer Variant Software Version Mitel 3300 MCD Mxe Platform 10.0.1.23 Mitel Minet sets: 5340, 5215, 5330 01.06.01.02 Mitel MBG - Teleworker V5.2.9.0 Mitel MBG - Gateway V5.2.11.0 Mitel Mobile Extension 1.7.13.0 Mitel NuPoint NuPoint voice mail server V12.0.1.34 Sonus Network Border Switch (NBS) V06.04.06 S005 BroadSoft BroadSoft System AS version Rel_14.sp9_1.123 NS version Rel_14.sp4_1.165
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 Trunk Side Interoperability Test Plans (08-4940-00034) for detailed test cases. Feature Feature Description Issues Basic Call Automatic Call Distribution NuPoint Voicemail Packetization Personal Ring Groups Mobile Extension Teleworker Video Fax Making and receiving a call through the XO Communications SIP trunk, call holding, transferring, conferencing, busy calls, long calls durations, variable codec. Making calls to an ACD environment with RAD treatments, Interflow and Overflow call scenarios and DTMF detection. Terminating calls to a NuPoint voicemail boxes and DTMF detection. Forcing the 3300 MCD to stream RTP packets through its E2T card at different intervals, from 10ms to 90ms Receiving calls through XO Communications SIP trunk to a personal ring group. Also moving calls to/from the prime member and group members. Receiving a call through the SIP trunk to Mobile extensions and TUI interface. Also moving calls to/from Desktop and Twinned devices. Making and receiving a call through XO Communications SIP trunk to and from Teleworker extensions. Making and receiving a call through XO Communications SIP trunk with video capable devices. No video calls supported. T.38 and G711Fax Calls - No issues found - Issues found, cannot recommend to use - Issues found 2
Device Limitations and Known Issues This is a list of problems or not supported features when the XO Communications SIP trunk is connected to the Mitel 3300. Feature Provisional Responses CPN Restriction Packetization rate Problem Description PRACK is not supported by XO Communications. This will not affect call functionality or quality with XO Communications but rather simply a characteristic of this interop. Recommendation: Ensure Disable Reliable Provisional Responses option is set to Yes in the SIP Peer profile When CPN Restriction SIP Peer profile option is set to Yes, the call will be presented as anonymous@anonymous.invalid to XO Communications. As such, it will be rejected by them. Recommendation: Ensure CPN Restriction option is set to No in the SIP Peer profile The trunk fully supports the 10ms, 20ms packetization rates. With rates of 30ms and 40ms, the provider s SIP server switches to 20ms rate although the audio stays up in both directions. Recommendation: keep packetization rate to 10ms or 20ms in the SIP Peer profile. Video Fax Video functionality is unavailable over the trunk. Recommendation: none When the Multiple Active M-lines are enabled in SIP Peer Profile form, T.38 outgoing faxing fails. XO Communications only support single m-line for faxing. This will not affect call functionality or quality with XO Communications but rather simply a characteristic of this interop. Recommendation: Set Allow Peer to Use Multiple Active M-lines to No in SIP Peer Profile form
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 was configured. These notes should give a guideline how a device can be configured in a customer environment and how the XO Communications 3300 programming 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. 3300 MCD Configuration Notes The following steps show how to program a 3300 MCD to interconnect with the XO Communications. 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 MCD Programming The SIP signaling connection uses UDP on Port 5060.
Licensing and Option Selection SIP Licensing Ensure that the 3300 MCD is equipped with enough SIP trunking licenses for the connection to the XO Communications. 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 3300 to be used with all service providers, applications and SIP trunking devices. Figure 2 License and Option Selection form 6
Class of Service Assignment The Class of Service Options Assignment 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 in the Trunk Service Assignment 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 3300. Busy Override Security set to Yes Campon Tone Security/FAX Machine set to Yes Public Network Access via DPNSS set to Yes
Figure 3 Class of Service form 8
Network Element Assignment Create a network element for a SIP Peer (XO_Commun) as shown in Figure 4. Set the transport to UDP and port to 5060. Figure 4 Network Element Assignment
Network Element Assignment (Proxy) In addition, depending in 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, the 3300 MCD will require knowledge of this by programming the Proxy as a network element then referencing this proxy in the SIP Peer Profile assignment (later in this document). Figure 5 Network Element Assignment (Proxy) 10
Trunk Service Assignment This is configured in the Trunk Service Assignment form. The Trunk Service Assignment is defined for Trunk Service Number (17), which will be used to direct incoming calls to an answer point in the 3300. 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. The figure below shows configuration for incoming DID calls. The 3300 will absorb the first 6 digits of the DID number from the XO Communications SIP Trunk leaving 4 digits for the 3300 to translate and ring the remaining 4 digit extension. For example, the XO Communications SIP Trunk delivers number 214-635-5890 to the 3300. The 3300 will absorb the first 6 digits (214-635) leaving the 3300 to ring extension 5890. Extension 5890 must be programmed as a valid dialable number in the 3300. As an alternative way, you can create a System Speed Call number to associate the extension 5890 with the real telephone extension on 3300 ICP. Please refer to the 3300 System Administration documentation for further programming information. Figure 6 Trunk Service Assignment
SIP Peer Profile The recommended connectivity via SIP Trunking does not require additional physical interfaces. IP/Ethernet connectivity is part of the base 3300 MCD Platform. The SIP Peer Profile should be configured with the following options: Network Element: The selected SIP Peer Profile needs to be associated with previously created XO_Commun Network Element. Registration User Name: Leave it empty Address Type: Enter the Use IP Address or FQDN in SIP messages. Maximum Simultaneous Calls: This entry should be configured to maximum number of SIP trunks provided by XO Communications. Outbound Proxy Server: Select the Network Element previously configured for the Outbound Proxy Server (MBGTrunk). SMDR Tag: If Call Detail Records are required for SIP Trunking, the SMDR Tag should be configured (by default there is no SMDR and this field is left blank). Trunk Service Assignment: Enter the trunk service assignment previously configured 17 in this configuration. Calling Line ID Options: 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. XO Communications could provide this number. Otherwise, use the one of DID numbers assigned on the trunk by the provider. Default CPN should be known to the provider s SIP switch otherwise it refuses to process any calls. CPN Restriction: Set it to No. When it is set to Yes, the call will be presented as anonymous@anonymous.invalid. As such, it will be rejected by the provider s SIP switch. Authentication Options: Since this SIP trunk is authenticated by IP address, leave this field blank. SDP Options: Currently (December 2009) video streams are not supported over XO Communications SIP trunk. Set option Allow Peer to Use Multiple Active M-Lines to No. Currently, RTP Packetization Rate on the XO Communications SIP trunk could be set to 10ms, 20ms, 30ms and 40ms. Please, note that only rates of 10ms and 20ms are fully supported by the provider s SIP server. With rates of 30ms and 40ms, the provider s SIP server switches to 20ms rate although the audio remains up in both directions. Set the RTP Packetization Rate to some desired level. Signaling and Header Manipulation Options: You might set value for Session Timer to 0. However, this timer clears and resets the unresponsive connections and it is not recommended to set to 0. 12
Currently, Reliable Provisional Responses (PRACK) are not supported on the trunk. You might enable the support of Reliable Provisional Responses in 3300 ICP when this feature will become available on the trunk.
Figure 7 SIP Peer Profile Assignment 14
SIP Peer Profile Assignment by Incoming DID This form is used to associate DID range numbers from XO Communications SIP Trunk to a particular SIP Peer profile. Enter one or more telephone numbers. The maximum number of digits per telephone number is 26. You can enter a mix of ranges and 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 characters 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 8 SIP Peer Profile Assignment by Incoming DID
Digit Modification Number Ensure that Digit Modification for outgoing calls to XO Communications SIP Trunk absorbs or inject additional digits according to your dialling plan. In this test environment, we will be absorbing 3 digits (in this case you will need to dial 901 to access XO Communications SIP trunk; thus, digits 901 will be absorbed). Figure 9 Digit Modification Assignment 16
Route Assignment Create a route for SIP Trunks connecting a trunk to XO Communications SIP Trunk. In this test environment, the SIP trunk is assigned to Route Number 30. Choose SIP Trunk as a routing medium and choose the SIP Peer Profile and Digit Modification entry created earlier. Figure 10 SIP Trunk Route Assignment
ARS Digits Dialed Assignment ARS initiates the routing of trunk calls when certain digits are dialed from an extension. In this test environment, when a user dials 901, the call will be routed to XO Communications SIP Trunk (i.e. Route 30). 3300 ICP expects 10 digits to be dialed after dialing of 901. Figure 11 ARS Digit Dialed Assignment 18
T.38 Fax Configuration To enable T.38 faxing over XO Communications SIP trunk, we used the inter-zone 2 FAX profile. This form allows you to define the settings for FAX communication over the IP network. You can modify the default settings for the: 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.29, 7200bps. 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. o o 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. o All zones default to G.711 pass through communication (Profile 1). Figure 12 Fax Configuration
Zone Assignment By default, all zones are set to Intra-zone FAX Profile 1. 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. Figure 13 Zone Assignment The assignment of the pre-configured zone to the SIP Peer profile can be done in Network Element Assignment form. 20
Mitel Border Gateway Configuration Notes When configuring Mitel Border Gateway (MBG), you need to identify the working 3300 ICP where to forward SIP messages to and configure SIP trunk. To do this: Login to MBG and click Mitel Border Gateway Click ICPs tab (see Figure 14 for details) Figure 14 MBG s main page On ICPs page, ensure that the working 3300 ICP is configured and Default for SIP radio button for this ICP is selected (see Figure 15). Click Update button
Figure 15 ICP configuration page Click Connectors tab (see Figure 16 for details) and then click SIP trunks Click Add a SIP trunk link Figure 16 Connectors configuration page Enter the SIP trunk s details as follows (see also Figure 17): 22
Name is the name of the trunk Local ICP address the IP address of the working 3300 ICP configured earlier (see Figure 15) Remote trunk endpoint address the public IP address of the provider s switch or gateway (this address should be given to you by the provider, e.g. XO Communications). Local/Remote RTP framesize (ms) is the packetization rate you want to set on this trunk The rest of the settings are optional and could be configured if required. Click Save button Figure 17 SIP Trunk configuration settings
24