MITEL SIP CoE Technical. Configuration Note. Configure MiVB for use with Netcall Telecom Liberty SIP Trunking. SIP CoE

Transcription

1 MITEL SIP CoE Technical Configuration Note Configure MiVB for use with Netcall Telecom Liberty SIP Trunking SIP CoE

2 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 MIVB for use with Netcall Liberty SIP Trunking October 2014, , Trademark of Mitel Networks Corporation Copyright 2014, Mitel Networks Corporation All rights reserved ii

3 Table of Contents OVERVIEW... 1 Interop History... 1 Interop Status... 1 Software & Hardware Setup... 2 Tested Features... 3 Device Limitations and Known Issues... 4 Network Topology... 5 CONFIGURATION NOTES... 6 MIVB Configuration Notes... 6 Configuration Template... 6 Network Requirements... 6 Assumptions for MIVB Programming... 6 Licensing and Option Selection SIP Licensing... 7 Class of Service Assignment... 8 Network Element Assignment... 9 Network Element Assignment (Proxy) Trunk Attributes SIP Peer Profile ARS Digit Modification Plans ARS Routes ARS Digits Dialed Netcall Liberty Configuration Notes Liberty Connection tests Liberty Common Configuration iii

4

5 Overview This document provides a reference to Mitel Authorized Solutions providers for configuring the Mitel Voice Business to connect to Netcall Liberty SIP Trunking. 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 October, 2014 Initial Interop with Mitel Voice Business 7.0 and Netcall Liberty 2.4 SIP trunk Interop Status The Interop of Netcall Liberty SIP Trunking has been given a Certification status. This service provider or trunking device will be included in the SIP CoE Reference Guide. The status Netcall Liberty SIP Trunking achieved is: The most common certification which means Netcall Liberty SIP Trunking 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.

6 Software & Hardware Setup This was the test setup to generate a basic SIP call between Netcall Liberty SIP Trunking and the MiVB. Manufacturer Variant Software Version Mitel MiVB Mxe Platform Service Provider Netcall Liberty Telephony platform 2.4 2

7 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 Pans ( ) for detailed test cases. Feature Feature Description Issues Basic Call & SIP Features Automatic Call Distribution NuPoint Voic Packetization Personal Ring Groups Mitel Voic Mitel Auto Attendant External Hot Desking Teleworker Video Making and receiving a call from Netcall Liberty, 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 voic boxes and DTMF detection. Forcing the Mitel Voice Business to stream RTP packets through its E2T card at different intervals, from 10ms to 90ms Receiving calls through Netcall Liberty and their PSTN gateway to a personal ring group. Also moving calls to/from the prime member and group members. Connecting calls directly and diverted from Liberty to the Mitel Embedded voic system. Interoperability with this allow calls to transfer to and from the Mitel attendant to the Netcall system. Receiving calls through Netcall Liberty and their PSTN gateway to PRG with EHDU. Including moving calls to/from the prime member of the PRG with the EHDU. Also placing calls from the EHDU and using mid call features with EHDU. Making and receiving a call Netcall Liberty and their PSTN gateway to and from Teleworker extensions. Making and receiving a call through Netcall Liberty with video capable devices. Not Tested Not available Fax T.38 and G711Fax Calls N/A - No issues found - Issues found, cannot recommend to use - Issues found N/A N/A N/A N/A

8 Device Limitations and Known Issues This is a list of problems or not supported features when Netcall Liberty SIP Trunking is connected to the MIVB. Feature Authentication Codec Video Fax Conference and Twinned extensions Problem Description Netcall Liberty used trusted IPs for this interop test. Authentication is not needed or supported. Recommendation: Use trusted IPs. G.729 Codec is not supported by Netcall Liberty Recommendation: Program SIP Peer to use G711 as suggested below. Netcall Liberty does not support video calling Recommendation: System is call center, voice dialer and IVR and video calling is not a requirement. Netcall Liberty does not support G.711 fax calling. Recommendation: The Netcall ACD does not need to handle fax traffic. The test environment did not support follow me, twinning or conferencing. Recommendation: Netcall uses standard SIP messaging and connecting to single SIP phones is no different to connecting to Special Mitel features. Carefully test if required as part of an installation however we would envisage no errors. 4

9 Network Topology This diagram shows how the testing network is configured for reference. Figure 1 Network Topology

10 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 Netcall Liberty SIP Trunking MiVB 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. MIVB Configuration Notes The following steps show how to program a MiVB to interconnect with Netcall Liberty SIP Trunking. Configuration Template A configuration template can be found in the same MOL Knowledge Base article as this document. The template is a Microsoft Excel spreadsheet (.csv format) solely consisting of the SIP Peer profile option settings used during Interop testing. All other forms should be programmed as indicated below. Importing the template can save you considerable configuration time and reduce the likelihood of data-entry errors. Refer to the MIVB documentation on how the Import functionality is used. 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 MiVB 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 MIVB Programming The SIP signaling connection uses UDP on Port

11 Licensing and Option Selection SIP Licensing Ensure that the MiVB is equipped with enough SIP trunking licenses for the connection to Netcall LIBERTY SIP device. 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 MiVB to be used with all service providers, applications and SIP trunking devices. Figure 2 License and Option Selection

12 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 calls through NetCall LIBERTY SIP device in the MiVB. 8

13 Network Element Assignment Create a network element for Netcall LIBERTY SIP device. In this example, the device is reachable by an IP Address and is defined as netcall in the network element assignment form. The FQDN or IP addresses of the SIP Peer (Network Element is provided by your network administrator. Figure 3 Network Element Assignment

14 Network Element Assignment (Proxy) In addition, depending in your configuration, a Proxy may need to be configured to route SIP data to the SIP device. If you have a Proxy server installed in your network, the MiVB 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 4 Network Element Assignment (Proxy) 10

15 Trunk Attributes This is configured in the Trunk Attributes form. In this example the Trunk Attributes is defined for Trunk Service Number 13 which will be used to direct incoming calls to an answer point in the Mitel MiVB. Program the Non-dial In or Dial In Trunks (DID) according to the site requirements. The example below shows configuration for incoming DID calls. The Mitel MiVB will absorb the 0 digits of the DID number from Netcall s Liverty SIP device which the MiVB will use to route calls to their destination. Please refer to the Mitel MiVB System Administration documentation for further programming information. Figure 5 Trunk Attributes

16 SIP Peer Profile The recommended connectivity via SIP Trunking does not require additional physical interfaces. IP/Ethernet connectivity is part of the base MiVB 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 Netcall Network Element. Registration User Name Not required Address Type: Select IP address. Outbound Proxy Server: If required select the Network Element previously configured for the Outbound Proxy Server. Trunk Service Assignment: Enter the trunk service assignment previously configured. SMDR: 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). Maximum Simultaneous Calls: This entry should be configured to maximum number of SIP trunks provided by Netcall. NOTE: Ensure the remaining SIP Peer profile policy options are similar the screen capture below. 12

17 Figure 6 SIP Peer Profile Assignment- Basic

18 Figure 8 SIP Peer Profile Assignment- Call Routing Figure 9 SIP Peer Profile Assignment- Calling Line ID 14

19 Figure 10 SIP Peer Profile Assignment- SDP Options

20 Figure 11 SIP Peer Profile Assignment- Signaling and Header Manipulation 16

21 Figure 12 SIP Peer Profile Assignment- Timers Figure 13 SIP Peer Profile Assignment- Key Press Event

22 ARS Digit Modification Plans Ensure that Digit Modification for outgoing calls on the SIP trunk to Netcall absorbs or inject additional digits according to your dialling plan. In this example, we will be absorbing 3 digits (in this case will be 903 to dial out). Figure 17 Digit Modification Assignment 18

23 ARS Routes Create a route for SIP Trunks connecting a trunk to Netcall. In this example, the SIP trunk is assigned to Route Number 20. Choose SIP Trunk as a routing medium and choose the SIP Peer Profile and Digit Modification entry created earlier. Figure 18 SIP Trunk Route Assignment

24 ARS Digits Dialed ARS initiates the routing of trunk calls when certain digits are dialed from a station. In this example, when a user dials 977, the call will be routed to Netcall (ie. Route 20. Figure 19 ARS Digit Dialed Assignment 20

25 Netcall Liberty Configuration Notes Figure 1 Use Start / Liberty / Configuration / Telephony Protocol Config. Choose Next to move to the first setup screen. This normally setup by the Netcall engineer as part of the system installation. Figure 2 Select SIP trunk

26 Figure 3 Enter the IP address mitel MiVB into the SIP proxy. SIP Domain can be left blank. Figure 4 Choose TCP as a preferred choice. 22

27 Figure 5 Choose the number of inbound and outbound channels these will either be 50% in and 50% out or 66.6% in and 33.3% out and the total will depend on the channels purchased. The total should match the licenced trunks. The next 3 screen reflect the application purchased and not the SIP trunk The rest of the setup screens reflect th products purcased capicaty of these. Moving these from their set values may effect the system leicse. There next part of the set up is to route the calls normally viai DDI to the varous services. Figure 6 This is done via the Web on the Admn / Call routing screen.

28 Figure 7 This is where PBX s outbound DDI is routed to the inbound Netcall configuation. Calls back to the PBX have to be routed in the number rules section. 24

29 Liberty Connection tests Liberty is often part of an array of IVR systems, and it is important to test configurations. In order to confirm this operation an extra test was performed. Call into the Mitel Auto-attendant. Direct the call to Liberty. Liberty place call to extension. Call diverted to Mitel Embedded voic . Confirm the system can be heard and leave a message. Retrieve the message. The trace for this is included in the tests.

30 Liberty Common Configuration Multiple SIP trunk transfers Number 1 st Choice 2 nd Choice 3 rd Choice External Operator 1005 Trunk 1 Trunk 2 Backup Name Dialer 1006 Trunk 2 Trunk 1 Service Trunk 1 Service Trunk 2 Scenarios 1. Confirm 1005 routes to Trunk 1 and 1006 routes to Trunk Taking system 1 down then 1005 will route to trunk 2 3. Taking system 1 & 2 down then 1005 will route to backup. 4. Taking system 1 down and 1007 will get busy. 5. Taking system 2 down and 1008 will get busy. Programming required on Mitel Refer to the Mitel MiVB Administrator guide to program trunk diversion on busy and no answer. 26

31