Technical - XO Communications
MITEL – SIP CoE
Technical
Configuration Notes
Configure the MiVoice Business 7.1 for
use with XO Communications SIP
Services
MAY 2015
SIP COE 10-4940-00105
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 the MiVoice Business 7.1 for use with XO Communications Recert SIP trunking
May 2015 10-4940-00105_3
®,™ Trademark of Mitel Networks Corporation
© Copyright 2015, 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
XO COMMUNICATIONS Configuration Notes ...................................................................5
3300 vMCD Configuration Notes ........................................................................................5
Network Requirements .................................................................................................................... 5
Assumptions for the 3300 vMCD Programming .............................................................................. 5
Licensing and Option Selection – SIP Licensing ............................................................................ 6
Class of Service Assignment .......................................................................................................... 7
Network Element Assignment ......................................................................................................... 8
Network Element Assignment (Proxy) ............................................................................................ 9
Trunk Service Assignment ............................................................................................................ 10
SIP Peer Profile ............................................................................................................................. 11
SIP Peer Profile Assignment by Incoming DID ............................................................................. 15
Direct Inward Dialing Service ........................................................................................................ 16
ARS Digit Modification Number..................................................................................................... 17
ARS Routes Assignment ............................................................................................................... 18
ARS Digits Dialed Assignment ...................................................................................................... 19
Fax Configuration .......................................................................................................................... 20
Zone Assignment .......................................................................................................................... 22
Mitel Border Gateway Setup ............................................................................................23
MBG Setup .................................................................................................................................... 23
ICP Setup ...................................................................................................................................... 24
SIP Trunk Setup ............................................................................................................................ 25
iii
10-4940-00105_3
XO Communications
Overview
This document provides a reference to Mitel Authorized Solutions providers for
configuring the Mitel MiVB 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
July 2013
Interop with Mitel 3300 MCD 6.0 and XO COMMUNICATIONS
2
June 2014
Interop with Mitel 3300 VMCD 7.0 and XO COMMUNICATIONS
3
May 2015
Interop with MiVB 7.1 and XO COMMUNICATIONS
Interop Status
The Interop of XO COMMUNICATIONS 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 achieved is:
The most common certification which means XO COMMUNICATIONS
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
Test setup to generate a basic SIP call between XO COMMUNICATIONS and the Mitel
MiVB.
Manufacturer
Variant
Software Version
Mitel
MiVB 7.1
13.1.0.33
Mitel
MBG - Gateway
9.0.27.0
Mitel
MBG - Teleworker
9.0.27.0
Mitel
Nupoint Voicemail
V17.0.0.24
Mitel
6865i and 6867i SIP Sets
3.3.1.7087
Mitel
5330 Minet Sets
06.01.00.08
XO
Communications
XO Communications SIP Services
NA
10-4940-00105_3
XO Communications
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 (084940-00034) for detailed test cases.
Feature
Basic Call
Making and receiving a call through XO
COMMUNICATIONS 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.
NuPoint Voicemail
Terminating calls to a NuPoint voicemail boxes and
DTMF detection.
Packetization
Forcing the 3300 MiVB to stream RTP packets through
its E2T card at different intervals, from 10ms to 60ms
Personal Ring
Groups
Receiving calls through XO COMMUNICATIONS and
their PSTN gateway to a personal ring group. Also
moving calls to/from the prime member and group
members.
Teleworker
Making and receiving a call through XO
COMMUNICATIONS and their PSTN gateway to and
from Teleworker extensions.
Video
Making and receiving a call through XO
COMMUNICATIONS with video capable devices.
Fax
T.38 and G711Fax Calls
- No issues found
2
Feature Description
- Issues found, cannot recommend to use
Issues
N/A
- Issues found
10-4940-00105_3
XO Communications
Device Limitations and Known Issues
This is a list of not supported features when XO COMMUNICATIONS is connected to the
Mitel MiVB 7.1.
Feature
Video
Problem Description
XO COMMUNICATIONS does not support video calls over SIP
Trunks.
Recommendation: Consult XO COMMUNICATIONS for future
deployment.
Packetization
Fax
Outbound
Caller-ID for
forwarded call
MiVB was exclusively tested with stream RTP packets through its E2T
card at 10 and 20ms (XO COMMUNICATIONS recommendation)
instead of the Mitel recommended range of 10ms to 60ms.
Recommendation: Use XO COMMUNICATIONS 10 or 20ms
recommended setting.
XO COMMUNICATIONS does not support T.38 Fax with multiple mlines over SIP Trunks; however both G.711 and T.38 (single m-lines)
were tested.
Recommendation: Consult XO COMMUNICATIONS for future
deployment.
With the standard recommended Mitel SIP Peer Profile settings, all
outbound Remote DUT calls had a Caller-ID = XO Communications
but for all outbound “forwarded or transferred” calls the Caller-ID
defaulted to the XO Communications’ CPN pilot number
= 2146355867. Original Caller ID was not forwarded as Mitel adds
both ‘Diversion’ as well as ‘History-info’ header which is not supported
by XO. XO only requires ‘Diversion’ header with one of XO assigned
DIDs.
Recommendation: N/A
10-4940-00105_3
XO Communications
Network Topology
This diagram shows how the testing network is configured for reference.
Figure 1 – Network Topology
4
10-4940-00105_3
XO Communications
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 XO
COMMUNICATIONS and 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.
XO COMMUNICATIONS Configuration Notes
SIP Service Provider Server IP address
205.158.163.138
Registration and Authentication
N/A
Pilot Number
NA
Username/Password
N/A
DIDs
2146355855- 2146355857
Preferred Codec
G.729 / fallback G.711
SIP port
5060
Transport Type
UDP
Session Timer
90 seconds
MiVB Configuration Notes
The following steps show how to program a MiVB to interconnect with 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 MiVB Programming
•
The SIP signaling connection uses UDP on Port 5060
10-4940-00105_3
XO Communications
Licensing and Option Selection – SIP Licensing
Ensure that the MiVB is equipped with enough SIP trunking licenses for the connection to
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 MiVB to be used with all
service providers, applications and SIP trunking devices.
Figure 2 – License and Option Selection
6
10-4940-00105_3
XO Communications
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.
•
Public Network Access via DPNSS set to Yes
•
Campon Tone Security/FAX Machine set to Yes
•
Busy Override Security set to Yes
•
Clear Auto Campon Timer to enable 486 BUSY testing
Figure 3 – Class of Service
10-4940-00105_3
XO Communications
Network Element Assignment
Create a network element for XO COMMUNICATIONS. In this example, the softswitch is
reachable by an IP Address and is defined as “XOcom” in the network element
assignment form. The FQDN or IP addresses of the SIP Peer (Network Element), the
External SIP Proxy and Registrar are provided by your service provider.
If your service provider trusts your network connection by asking for your gateway
external IP address, then programming the IP address for the SIP Peer, Outbound Proxy
and Registrar is not required for SIP trunk integration. This will need to be verified with
your service provider. Set the transport to UDP and port to 5060.
Figure 4 – Network Element Assignment
8
10-4940-00105_3
XO Communications
Network Element Assignment (Proxy)
In addition, depending on 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 ICP will require knowledge of this by programming the Proxy as a network element
then referencing this proxy in the SIP Peer Profile form (later in this document).
Figure 5 – Network Element (Proxy)
10-4940-00105_3
XO Communications
Trunk Service Assignment
This is configured in the Trunk Service Assignment form. In this example the Trunk
Service Assignment is defined for Trunk Service Number 23 which will be used to direct
incoming calls to an answer point in the MiVB.
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 example below shows configuration for incoming DID calls. The MiVB will absorb the
first 0 digits of the DID number from XO COMMUNICATIONS and map them directly to a
3300 4 digit extension assigned in the /Call Routing/Call Handling/ Direct Inward Dialing
Service form shown in Figure 9.
Figure 6 – Trunk Service Assignment
10
10-4940-00105_3
XO Communications
SIP Peer Profile
The recommended connectivity via SIP Trunking does not require additional physical
interfaces. IP/Ethernet connectivity is part of the base 3300 vMCD 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 “XOcom” Network Element.
Registration User Name: XO COMMUNICATIONS does require the use of a
Registration User Name.
Address Type: Select IP address.
Default CPN: The default CPN “2146355867” is applied to all calls unless there is a
match in the "Outgoing DID Ranges" of the SIP Peer Profile. This number will be
provided by XO COMMUNICATIONS. Do not use a Default CPN if you want public
numbers to be preserved through the SIP interface. Add private numbers into the DID
ranges for CPN Substitution form (see DID Ranges for CPN Substitution). Then select
the appropriate numbers in the Outgoing DID Ranges in this form (SIP Peer Profile).
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 XO COMMUNICATIONS.
NOTE-1: Ensure the remaining SIP Peer profile policy options are similar the screen
capture below.
10-4940-00105_3
12
XO Communications
10-4940-00105_3
XO Communications
10-4940-00105_3
XO Communications
Figure 7 – SIP Peer Profile Assignment
14
10-4940-00105_3
XO Communications
SIP Peer Profile Assignment by Incoming DID
This form is used to assign incoming digits from XO COMMUNICATIONS. DID range
numbers assigned by XO COMMUNICATIONS and are associated to a particular SIP
Peer.
Enter one or more telephone numbers. The maximum number of digits per telephone
number is 26. You can enter a mix of ranges or single numbers (for example,
"01661520417,01282505152"). 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 character 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
10-4940-00105_3
XO Communications
Direct Inward Dialing Service
This form is used to direct incoming DIDs from XO COMMUNICATIONS. DID numbers
are assigned and associated to a particular destination number.
Figure 9 –DID mapping
16
10-4940-00105_3
XO Communications
ARS Digit Modification Number
Ensure that Digit Modification for outgoing calls on the SIP trunk to XO
COMMUNICATIONS absorbs or inject additional digits according to your dialling plan. In
this example, we will be absorbing 3 digits for prefixes used: 921 prefix to dial out
followed by 10 digits (DID Calls).
Figure 10 – Digit Modification Assignment
10-4940-00105_3
XO Communications
ARS Routes Assignment
Create a route for SIP Trunks connecting a trunk to XO COMMUNICATIONS. In this
example, the SIP trunk is assigned to Route Number 1. Choose SIP Trunk as a routing
medium and choose the SIP Peer Profile and Digit Modification entry created earlier.
Figure 11 – SIP Trunk Route Assignment
18
10-4940-00105_3
XO Communications
ARS Digits Dialed Assignment
ARS initiates the routing of trunk calls when certain digits are dialed from a station. In this
example, when a user dials 921 the call will be routed to XO COMMUNICATIONS (ie.
Route 1).
Figure 12 – ARS Digit Dialed Assignment
10-4940-00105_3
XO Communications
Fax Configuration
XO COMMUNICATIONS uses the inter-zone 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.
•
•
•
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.
All zones default to G.711 pass through communication (Profile 1).
Figure 13 – Fax Service Profiles
20
10-4940-00105_3
XO Communications
Figure 14 – Fax Advanced Settings
10-4940-00105_3
XO Communications
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”. XO COMMUNICATIONS uses the Inter-zone FAX Profile.
Figure 15 – Zone Assignment
22
10-4940-00105_3
XO Communications
Mitel Border Gateway Setup
MBG Setup
Figure 16 – MBG setup
10-4940-00105_3
XO Communications
ICP Setup
To program an MiVB into the MBG, click on ICP’sAdd an ICP.
Enter a name for the MiVB.
Enter the IP address of the MiVB and select the Type as MCD.
Figure 17 – ICP setup
24
10-4940-00105_3
XO Communications
SIP Trunk Setup
Under the Services tab, click on SIP trunking and then “Add a SIP Trunk”. Enter the SIP
trunk’s details as shown below.
Name – is the name of the trunk
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).
Local/Remote RTP framesize (ms) – is the packetization rate you want to set on
this trunk
Routing rule one – it allows routing of any digits to the selected MiVB
The rest of the settings are optional and could be configured if required. Click Save button
Figure 18 – Services - SIP Trunking setup
10-4940-00105_3
26
XO Communications
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising