Technical
Configuration Notes
Configure the Mitel 5000
Communications Platform SIP
Trunking for use with EarthLink
SIP trunk
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 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 5000 Communications Platform for use with EarthLink SIP trunk
August 2011, 11-4940-00180
®,™ Trademark of Mitel Networks Corporation © Copyright 2011, Mitel Networks Corporation
iii
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
Mitel 5000 Communications Platform Configuration Notes ... 5
Network Requirements ... 5
Assumptions for the Mitel 5000 Communications Platform Programming ... 5
Licensing and Option Selection – SIP Licensing ... 6
Creating and Configuring a SIP Peer Trunk Group ... 7
Programming the Configuration settings ... 8
Programming the Trunk Group Configuration properties ... 11
Programming the Trunks in Trunk Group Configuration Folder ... 12
Phone Configurations ... 13
Call Configurations ... 16
1
Overview
This document provides a reference to Mitel Authorized Solutions providers for configuring the Mitel 5000CP to connect to EarthLink SIP trunk. 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 August 30 , 2011 Initial Interop with Mitel 5000CP 5.0 and EarthLink SIP trunk
Interop Status
The Interop of EarthLink has been given a Certification status. This service provider or trunking device will be included in the SIP CoE Reference Guide. The status EarthLink achieved is:
The most common certification, which means that SIP Trunk from EarthLink 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 EarthLink service provider and the 5000CP.
Manufacturer Variant Software Version
Mitel 5000CP CS 5.0 release 30 Mitel IP set 5340, 5360 04.01.00.20 Mitel MAS (NuPoint) 2.2 14.2.0.36 Adtran Total Access 908e, IP Business Gateway A4.08.00.E Metaswitch Application Server Ver. 7.3 Nortel PSTN gateway CS2000/MG15K
Acme Packet Session Boarder Controller SBC 4250 & 4500 Ver. SC6.1.0 MR-7 Patch 4 (Build 855)
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.
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 Issues
Basic Call Making and receiving a call through the SIP Service provider and their PSTN gateway, call holding, transferring, conferencing, busy calls, long calls durations, variable codec.
Automatic Call Distribution
Making calls to an ACD environment with RAD treatments, Interflow and Overflow call scenarios and DTMF detection. MAS/NuPoint
Voicemail
Terminating calls to a NuPoint voicemail boxes and DTMF detection.
Embedded voicemail
Using the embedded voicemail system on Mitel 5000
Dynamic
Extension Express
Receiving a call through the SIP Service provider and their PSTN gateway to Mobile extensions and TUI interface. Also moving calls to/from Desktop and Twinned devices. Video Making and receiving a call through EarthLink’ SIP trunk
with video capable devices. Not Supported Fax G.711 Fax Calls
Fax T.38 Fax Calls Not Supported
3
Device Limitations and Known Issues
This is a list of problems or not supported features when EarthLink has a SIP trunk connected to the Mitel 5000 Communications Platform.
Features Problem Description
Faxing G.711 faxing is possible over the trunk only.
Recommendation: None. EarthLink does not support T.38 faxing. Calls to “busy” PSTN
numbers
When Mitel extension calls to a “busy” PSTN number, the audible “busy” tone is heard almost immediately. However, SIP message “486 – Busy Here” arrives at 5000CP only after 30 seconds.
Because of this, forward trunk clearing is impossible until the real SIP message 486 is received.
Recommendation: none. Contact EarthLink for further details.
Video Calls Mitel 5000CP does not support multiple m-lines and as such is incapable to process video calls.
Video functionality is unavailable over the ErthLink SIP trunk.
Recommendation: none
Reliable Provisional Responses (PRACK)
Mitel 5000 Communications Platform does not support PRACK at this time.
Recommendation: Contact Mitel for further information regarding this
feature.
Packetization rate The SIP trunk fully supports only 20ms packets rate whereas Mitel 5000CP supports 20ms and 30ms rates (Audio Frames).
Recommendation: In Mitel 5000CP, keep packets rate of 20ms.
Call privacy on outbound calls
There is no way to configure a "classical" privacy in 5000CP (with "anonymous").
If you remove the Calling Party Number from Trunk Group Configuration, EarthLink rejects this call.
If you enter e.g. "1111111111", then this call will be accepted and number delivered at far end is "1111111111".
Recommendation: Contact EarthLink for further information regarding this issue.
Network Topology
This diagram shows how the testing network is configured for reference.
5
Configuration Notes
This section is a description of how the SIP Interop was configured.
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.
Mitel 5000 Communications Platform Configuration Notes
The following steps show how to program Mitel 5000 Communications Platform to interconnect with EarthLink Service Provider.
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 for G.729. Almost all Enterprise LAN networks can support this level of traffic without any special engineering. Please refer to the 5200 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 Mitel 5000 Communications Platform Programming
Licensing and Option Selection – SIP Licensing
Ensure that the Mitel 5000 is equipped with enough SIP Trunks licences for the connection to EarthLink. This can be verified within the Software License form.
Check 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 Mitel 5000 to be used with all service providers and applications.
7
Creating and Configuring a SIP Peer Trunk Group
To support SIP trunks through a SIP trunk service provider, the SIP Trunk Groups folder was added to the SIP Peers folder in DB Programming.
To create a SIP Trunk Group for EarthLink, navigate to System->Device and Feature Codes->SIP Peers-Codes->SIP Trunk Groups and right click in the right hand window panel. Then select “Create SIP Trunk Group”. (See Figure 3)
Figure 3: Example of Create SIP Trunk Group
When you create a SIP Peer trunk group without using a template, you must obtain the necessary information from the SIP trunk service provider, and then configure this information in DB Programming.
When Trunk group for EarthLink is been created, we have to configure parameters in Configuration and Trunk Group Configuration nodes.
Programming the Configuration settings
• Registrar: Although EarthLink’ SIP trunk requires registration, we don’t need to configure
any registration details in Mitel 5000. Instead, all these settings were configured in Adtran IP Business Gateway by EarthLink personnel.
Set Enable Registration option to No as shown in Figure 4.
9
• Authentication:
In this form, we still need to configure Username and Password for outbound calls as shown in Figure 5.
EarthLink should provide Username and Password.
Figure 5: Example of Authentication form
• Keep-Alive: The Keep-Alive option keeps refreshing the NAT bindings for any
Firewall/NAT in the path. It also helps in determining whether the SIP peer is reachable or not. Leave the default values here.
• NAT Settings: Specifies the NAT address type. The default is “No NAT or SIP-Aware
NAT” (for systems that are using a SIP-aware firewall). If you are not using a SIP-aware firewall, you must change the setting to “Non SIP-Aware NAT”. Leave the default values here.
• Alternate IP/FQDN List: At the time of testing, EarthLink used a single IP address to
send SIP messages to the Mitel 5000. Therefore, there is no need to configure any alternative IP addresses or FQDNs.
Click Configuration node (see Figure 6)
• IP Address: Indicates the IP address of the SIP peer trunk group. Since we use Adtran
IP Business Gateway as Back2Back agent, we have to configure IP address of Adtran’s LAN interface here.
• Port Number: Indicates the port that the system listens on the system for SIP peer
• Fully Qualified Domain Name: Indicates the domain name of the SIP peer trunk group.
In our test environment, we do not use FQDN. Therefore, leave is blank.
Figure 6: Example of Configuration form
• Call Configuration: Enter the call configuration number in Value field that you want to
use with this trunk group.
Clicking Call Configuration takes you to the Call Configuration folder where you can add a new call configuration profile or configure the existing profile(s) (e.g. codecs for voice and faxing, DTMF settings, etc. See section Call Configurations). (System->IP-Related Information->Call Configurations-><call configuration number>).
• Operating State: Indicates the operating state of the SIP peer. If required, the status
could be changed to “Out-of-Service – Maintenance”.
• Maximum Number of Calls: Indicates the maximum number of concurrent calls that are
been permitted towards the SIP peer. This number is not configurable in here and depends on number of trunks added at System->Device and Feature Codes->SIP Peers->SIP Trunk Groups-><SIP Trunk group #>->Trunk Group Configuration->Trunks (see next section for details)
• Use ITU-T E.164 Phone Number: If set to Yes, the Mitel 5000 handles ITU-T E.164
formatted phone numbers as part of the incoming SIP INVITE messages from the SIP peer.
• Static Binding: It specifies whether a static binding exist for the corresponding SIP Peer.
If set to Yes, then IP address and listening port for the SIP Peer must be configured. Leave this setting to Yes.
11
• Use Peer Address In From Header: In our test environment, we set it to No.
Programming the Trunk Group Configuration properties
To program the Trunk Group Configuration properties, navigate to System->Device and Feature Codes->SIP Peers->SIP Trunk Groups-><SIP Trunk group #>->Trunk Group Configuration:
As per Figure 7, we need to configure three most important parameters:
- Day and Night Ring-In Type – in our test environment we configured Single ring-in type
with the value of 1310, where “1310” is the extension number where the incoming DID trunk calls are terminated.
- Calling Party Number – is the default calling party number, which 5000CP presents to
the provider’s SIP trunk. EarthLink should give this number to you. If this value is missing, EarthLink rejects to process this call. So, insure that this field is not blank.
For the rest of the settings, refer to the DB Programming Help for trunk programming
Programming the Trunks in Trunk Group Configuration Folder
The number of SIP trunks that we create in here will appear as Maximum Number of Calls in the Configuration screen (see Figure 6).
Create the SIP peer trunks as follows:
• Navigate to System->Device and Feature Codes->SIP Peers->SIP Trunk Groups-><SIP
Trunk group #>->Trunk Group Configuration->Trunks
• Right-click the right pane and the select Create SIP Peer Trunk. The Create SIP Peer Trunk dialog box appears (see Figure 8).
• Select the extension number you want to use for the item in the Starting Extension field. The recommended range is 94001–94999;
• Indicate the number of extensions you want to create in the Number of Extensions field. If the system is set to have more than one extension, the new trunks will be assigned sequentially to the next available numbers.
• Click OK. For the EarthLink, 3 extensions were created, See Figure 8. The number of available SIP Trunks licenses restricts the number of SIP peer trunks.
13
Phone Configurations
Some configuration settings need to be updating for the extensions.
In our test environment, when Outgoing key is pressed on the phone, we wanted to direct outbound calls to the EarthLink’ SIP trunk. To do this:
• Navigate to System->Device and Feature Codes->Phones-><Phone’s extension
number>->Associated Extension
• In right hand pane, select Outgoing Extension and enter the number of SIP Trunk Group corresponding to EarthLink’ trunk (in our test environment – 92006). See Figure 9 for details.
You can configure a voicemail extension in the same screen.
Figure 9: Configure outgoing extension for the phone
When configuring call forwarding to a voicemail box, it is not enough to create the mailbox and assign it to the phone. You also have to define a Forwarding Path and assign it to the phone. To do this:
• Navigate to System->Phone Related Information->System Forwarding Paths
• Define at least Forwarding Point 1 for the selected path. In the example in Figure 10, we defined extension 2502 as the forwarding point for path #3. Extension 2502 is a MAS (NuPoint) server’s voicemail pilot number. We also defined extension 2500 as Forwarding Point 1 for path #2. Extension 2500 represents the pilot number for Basic voicemail (BVM).
NOTE: For easier identification later on, we would recommend to enter a text in the
Description field as shown in Figure 10.
Figure 10: Example of Forwarding Path definition
Now, when Forwarding Path #3 and #6 are defined, we can assign one of them to the phone:
• Navigate to System->Device and Feature Codes->Phones-><Phone’s extension
number>->Forwarding Paths
• Right click in right hand pane and select Add to Forwarding Paths List
• Select the Forwarding Paths and click Next
• Select the required Forwarding Path’s number and click Add Items button
• Click Finish
NOTE: If you wish to forward unanswered internal calls to the defined Forwarding Point, set
15
Call Configurations
Call configurations define the settings that IP phones and gateways use when connected to calls. You can assign multiple devices to a specific call configuration.
By default, all IP devices are been placed in Call Configuration 1, which is programmable. You do not need to add SIP phones to Call Configurations, because these devices negotiate call configurations before establishing a connection. You can program up to 25 different Call Configurations.
Since EarthLink SIP trunk does not support T.38 faxing, we recommend enabling codec G.711U for faxing (see Figure 12 for details).
Set Audio Frames/IP Packet to “2” which corresponds to the packet rate of 20ms. To view the list of IP phones which are currently assigned to the call configuration:
• Navigate to System->IP-Related Information->Call Configurations-><call configuration
number>
17
Figure 12: Call Configuration Options
You can move extensions to this call configuration profile. To do this:
• Right click in right hand pane and select Move to Phones List
• Select the device type, e.g. 52xx/53xx and click Next
• Select extensions that you want to move and click Move Items button
• Click Finish
To view and move SIP Trunk Groups to the Call Configuration:
• Navigate to System->IP-Related Information->Call Configurations-><call
configuration number>
• Click SIP Trunk Groups
• Right click in right hand pane and select Move to SIP Trunk Groups List
• Select the type, e.g. SIP Trunk Group and click Next
• Select the required trunk group that you want to move and click Move Items button
Adtran 908e Configuration settings (Optional)
Adtran IP Business Gateway was configured as a Back2Back agent to enable SIP communication between EarthLink and Mitel 5000. EarthLink provides the configuration file for this type of gateway. This file contains all required settings to configure the gateway to connect to EarthLink SIP trunk.
So, every configuration file is a site specific.
Below, just for reference, we provide the configuration file loaded in Adtran Total Access 908e for our test environment.
!
!
! ADTRAN, Inc. OS version A4.08.00.E
! Boot ROM version 14.05.00.SA
! Platform: Total Access 908e (2nd Gen), part number 4242908L1
! Serial number CFG0602027
!
!
hostname "MITEL_LAB_908e"
enable password test;
set password to access Adtran’s config mode!
clock timezone -5-Eastern-Time
!
ip subnet-zero
ip classless
ip routing
!
!
ip domain-proxy
ip name-server 207.230.65.90 207.230.65.74
!
!
no auto-config
!
event-history on
no logging forwarding
no logging email
!
no service password-encryption
!
username "admin" password "123456";
set name and password for web access!
ip policy-timeout tcp telnet 14400
ip policy-timeout udp 5060 600
!
ip firewall
no ip firewall alg msn
no ip firewall alg mszone
no ip firewall alg h323
!
!
19
!
!
qos map VOICE 10
match dscp 46
match list DNS
priority percent 90
!
!
interface eth 0/1
description MITEL_LAB
speed 100
ip address 192.168.101.35 255.255.255.0;
Adtran’s internal interfaceaccess-policy Private
media-gateway ip primary
no shutdown
!
!
interface eth 0/2
description MITEL_PUBLIC_WAN_IP
speed 100
ip address 66.46.196.190 255.255.255.0;
Adtran’s external interfaceaccess-policy Public
media-gateway ip primary
max-reserved-bandwidth 100
qos-policy out VOICE
no shutdown
!
!
interface t1 0/1
shutdown
!
interface t1 0/2
shutdown
!
interface t1 0/3
shutdown
!
interface t1 0/4
shutdown
!
!
interface fxs 0/1
no shutdown
!
interface fxs 0/2
no shutdown
!
interface fxs 0/3
no shutdown
!
interface fxs 0/4
no shutdown
!
interface fxs 0/5
no shutdown
!
interface fxs 0/6
no shutdown
!
interface fxs 0/7
no shutdown
!
interface fxs 0/8
no shutdown
!
!
interface fxo 0/0
no shutdown
!
!
ip access-list standard DATA
permit any
!
ip access-list standard MATCH_ALL
permit 192.168.101.0 0.0.0.255
!
!
ip access-list extended DNS
permit tcp any host 207.230.65.90
permit tcp any host 207.230.65.74
permit tcp any host 192.168.101.20
permit tcp any host 192.168.101.35
!
ip access-list extended HOSTED_VOICE_LIST
remark NAT list HOSTED_VOICE_LIST
permit ip any host 207.230.65.90
permit ip any host 207.230.65.74
permit ip any host 97.67.232.73
permit ip any 66.0.12.192 0.0.0.31
permit ip any 97.67.73.0 0.0.0.31
permit ip any 97.66.135.160 0.0.0.31
permit ip any 97.67.73.32 0.0.0.31
permit ip any 97.67.31.32 0.0.0.31
permit ip any 66.0.48.32 0.0.0.31
permit ip any 97.67.73.64 0.0.0.31
permit ip any 66.184.162.224 0.0.0.31
permit ip any host 209.192.55.72
permit ip any 97.67.232.160 0.0.0.31
permit ip any 97.66.255.128 0.0.0.15
permit ip any host 64.179.100.93
!
ip access-list extended REMOTE_MANAGEMENT_ACCESS
permit tcp any any eq www log
21
permit tcp any any eq telnet log
permit udp any any eq snmp log
permit tcp any any eq https log
permit tcp any any eq ssh log
permit tcp any any eq ftp log
permit icmp any any echo log
!
ip access-list extended VOICE_WAN
permit udp any any eq 5060
permit tcp any any eq 5060
!
!
ip policy-class Private
allow list MATCH_ALL self
nat source list HOSTED_VOICE_LIST address 66.46.196.190
overload
nat source list DATA address 66.46.196.190 overload
!
ip policy-class Public
allow list REMOTE_MANAGEMENT_ACCESS
allow list VOICE_WAN
!
!
ip route 0.0.0.0 0.0.0.0 66.46.196.1
!
no ip tftp server
no ip tftp server overwrite
ip http server
ip http secure-server
no ip snmp agent
ip ftp server
no ip scp server
no ip sntp server
!
!
snmp-server community ITC-PubliC RO
!
!
auto-link
!
ip sip
ip sip udp 5060
ip sip tcp 5060
!
!
voice feature-mode network
voice forward-mode network
!
!
voice dial-plan 1 local NXX-NXX-XXXX
voice dial-plan 2 long-distance 1-NXX-NXX-XXXX
!
voice codec-list G.711_only
codec g711ulaw
!
!
voice ani-list ALL_ANI
ani $
!
voice trunk-list METASWITCH_SIP_LINES
trunk T01
!
!
voice trunk T01 type sip
description "SIP Line to LAB Meta"
sip-server primary sbc.voiplab.deltacom.net
codec-group G.711_only
!
voice trunk T10 type analog supervision loop-start
connect fxo 0/0
rtp delay-mode adaptive
!
!
voice grouped-trunk METASWITCH_SIP_LINES
description "SIP_Lines_to_Metaswitch"
trunk T01
accept $ cost 0
deny proxy
permit list ALL_ANI
!deny all other trunks
!deny all other ani
!
voice grouped-trunk FXO_01
trunk T10
accept $ cost 10
deny list METASWITCH_SIP_LINES
permit proxy
permit list ALL_ANI
!deny all other trunks
!deny all other ani
!
!
voice user 01
password "1234"
description "SIP_IDENTITY_USER"
sip-identity metaswitch T01
sip-authentication password "1234"
!
!
voice user 2562413369
connect fxs 0/1
first-name "Adtran908e_ST"
last-name "FXS_0/2"
password "1234"
23
