ACCELERATOR 6.3
MITEL 3300 INTEGRATION GUIDE
© 2004 - 2014 Tango Networks, Inc.
This software is protected by copyright law and international treaties, and is the confidential and proprietary information of Tango Networks, Inc. Unauthorized reproduction, use, or distribution of this software, or any portion of it, may result in severe civil and criminal penalties, and will be prosecuted to the maximum extent possible under the law. The software described in this document is furnished under license agreement and may only be used in accordance with the terms of the agreement. Tango Networks is a trademark of Tango Networks, Inc. All other trademarks used herein are the property of their respective owners and are used for identification purposes only.
© 2004 - 2014 Tango Networks, Inc.
TABLE OF CONTENTS
INTRODUCTION ... 3
SUPPORTED VERSIONS ... 4
KNOWN MITEL ISSUES ... 4
MITEL 3300LICENSE KEY REQUIREMENTS ... 5
ACCELERATOR INTEGRATION PROCESSES ... 6
MITEL 3300PROVISIONING ... 6
Workflow for Mitel Provisioning with a Mobile UC Enabled Accelerator ... 6
Workflow for Mitel Provisioning with a PSTN Access Enabled Accelerator ... 7
Login to Mitel Communications Director ... 7
Network Element Assignment... 8
Class of Service Options Assignment ...11
Trunk Service Assignment ...13
SIP Peer Profile ...15
SIP Peer Profile Assignment by Incoming DID ...17
ARS Digit Modification Plans ...19
ARS Routes ...20
ARS Digits Dialed Assignment...21
Class of Service Options Assignment ...22
SIP Device Capabilities ...24
User and Device Configuration ...26
ACCELERATOR PROVISIONING ...29
Mobile UC Enabled Accelerator ...29
Voice Network: PBX/Trunk Dial Plan ...29
Voice Network: Extension Ranges ...30
Voice Network: Carrier Gateways ...30
Voice Network : Voice Mail ...31
Subscriber Dial Plan/Subscribers ...31
PSTN Access Enabled Accelerator ...32
Voice Network: Trunk Dial Plan/PBX ...32
Voice Network: Extension Ranges ...33
USEFUL COMMANDS ...33
View Line Registration Status ...33
Link Status between Mitel PBX and Accelerator ...34
Link Status between Accelerator and Mitel PBX ...35
MOBILE UC FEATURE INTERACTIONS ... 36
ACCELERATOR PBXLEVEL 1INTEGRATION ...36
ACCELERATOR PBXLEVEL 2INTEGRATION ...39
Introduction
***The Accelerator can potentially be provisioned in one of three ways based on your Accelerator license key. Your license key dictates whether your enterprise has the ability to enable Mobile UC and/or PSTN Access (SIP Trunking) functionality.
During Accelerator provisioning, a Carrier(s) was created that enabled one or both of these services. How you integrate your Mitel PBX with the Accelerator solution depends on how your Carrier(s) is configured on the Accelerator.
Mobile Unified Communications (Mobile UC) - The Mobile UC application extends PBX and Unified Communications (UC) features to mobile devices. Examples include Single Number, Single Voicemail, and Abbreviated Dialing.
For Mobile UC, the Accelerator uses a combination of SIP lines and trunks to integrate with the Mitel PBX.
o SIP Trunk Interfaces – Used when the PBX provides originating and terminating services to calls from the Accelerator. For originations, the Accelerator originates on behalf of the mobile. For terminations, the Accelerator rings the desk on behalf of the mobile network.
o SIP Line Interfaces – Used to receive terminations from the PBX for Accelerator Mobile UC subscribers. If a call comes into the Mitel desk phone number, a SIP INVITE is sent over a SIP line interface to the Accelerator to ring the mobile phone.
o CTI (MiTai) must be enabled for each subscriber that intends to use the Call Move service and to monitor Mitel desk phones for the Message Waiting Indicator (MWI).
PSTN Access (e.g. SIP Trunking application) – PSTN Access facilitates interworking between enterprise and SIP entities such as PBXs and PSTN carriers (i.e. SIP Trunking Service Providers) as well as between internal enterprise SIP entities.
For PSTN Access, the Accelerator uses only SIP trunk service to integrate with the Mitel PBX; there are no SIP lines associated with the Accelerator trunking service.
Important Note: Through out this document and other Accelerator documents the term PSTN Access is used to describe the functions of the SIP Trunking Controller application or product. These terms are interchangeable. Whenever you see PSTN Access we are talking about the SIP Trunking Controller.
Supported Versions
This document addresses the way that the Accelerator solution integrates with the Mitel 3300. It is intended for users with a thorough understanding of the 3300. The Tango Accelerator solution supports integration with Mitel 3300 8.0-9.0 and 10.2 releases.
Notes: Starting with Mitel 3300 software build 10.x.x.x [the Mitel] documentation [refers] to the software by it's MCD version instead1.
The 10.2 release corresponds to MCD 4.2.
This guide is meant to familiarize the reader with the minimum
provisioning steps required on the Mitel PBX for Accelerator integration. It does not attempt to address all possible configurations options or features that can be applied within the PBX. Please consult your Mitel documentation for Mitel 3300 specific issues.
The screen shots in the sections that follow may not reflect your version of Mitel release. The 8.0-9.0 configuration screens are slightly different from the 10.2 but the concepts to integrate the PBX with the Accelerator are the same.
Known Mitel Issues
1. In some scenarios Music on Hold is played during a Call Move. This is due to feature interactions with the Mitel MiTAI CTI interface for all Mitel releases.
2. Music on Hold is not supported for the Mitel 8.0 release.
1
Mitel 3300 License Key Requirements
To use the Accelerator solution with 3300, the following software licenses are required:
o SIP Trunk License - The number of SIP Trunk Licenses required is engineered based on the number of concurrent calls on the PBX. Each Accelerator call can require multiple SIP Trunk licenses depending on the Mobile Policy applied.
o IP Device License - One incremental license is required per Accelerator subscriber to account for the mobile phone that is now configured on the PBX.
o SIP User License - One incremental license is required per Accelerator subscriber. Each mobile is configured as a generic SIP device. The SIP User License corresponds to the SIP Lines that will be created.
o Mitai/Tapi Computer Integration – For Mobile UC, the Mitai license is needed for the Call Move and Voice Mail services. This license
Accelerator Integration Processes
Mitel 3300 Provisioning
The integration with the Accelerator can be setup in several ways. During Accelerator provisioning, your enterprise selected a Carrier based on your Accelerator enterprise license key. Your license key may be enabled for Mobile UC functionality or it may be enabled for PSTN Access functionality, or even both.
The sections and steps outlined below will guide your workflow to integrate your Mitel 3300 PBX with the Accelerator.
Note: The 3300 must first be configured appropriately with domain and host information as per Mitel documentation.
Use the following steps to define SIP trunks, Routing, and User configurations on the Mitel PBX for interactions with the Accelerator Mobile UC service.
Workflow for Mitel Provisioning with a Mobile UC Enabled Accelerator
1. Login to Mitel Communications Director – page 72. Define Network Element Assignment – page 8
3. Define Class of Service Options Assignment – page 11 4. Define Trunk Service Assignment – page 13
5. Define SIP Peer Profile – page 15
6. Define SIP Peer Profile Assignment by Incoming DID – page 17 7. Define ARS Digit Modification Plans – page 19
8. Define ARS Routes – page 20
9. Define ARS Digits Dialed Assignment – page 21
10. Define Class of Service Options Assignment – page 22 11. Define SIP Device Capabilities – page 24
12. Create new User and Device Configuration - 26
Workflow for Mitel Provisioning with a PSTN Access Enabled
Accelerator
Use the following steps to define SIP trunks and Routing on the Mitel PBX for interactions with the Accelerator PSTN Access service.
1. Login to Mitel Communications Director – page 7 2. Define Network Element Assignment – page 8
3. Define Class of Service Options Assignment – page 11 4. Define Trunk Service Assignment – page 13
5. Define SIP Peer Profile – page 15
6. Define SIP Peer Profile Assignment by Incoming DID – page 17 7. Define ARS Digit Modification Plans – page 19
8. Define ARS Routes – page 20
9. Define ARS Digits Dialed Assignment – page 21 10. Execute PSTN Access Enabled Accelerator – page 32
Login to Mitel Communications Director
1. Access the 3300 administration web interface by using the URL
https://hostname/ in a browser, where hostname is the hostname of the Mitel Communications Director for the 3300.
Login using the appropriate credentials. Select the System Administration Tool.
Figure 2: Mitel 3300 Administration
This document uses Alphabetical forms list to navigate between tasks as shown in the next two screen shots.
Figure 3: Select View Alphabetically
Network Element Assignment
Depending on your Accelerator configuration, you may need to create more than one Network Element Assignment.
The Network Element Assignment section should be executed for each trunk identified. If both Mobile UC and PSTN Access are enabled then a total of 2 trunks will be needed with different ports (i.e., (2) Network Element
Assignments). Mobile UC uses port 5060 and PSTN Access uses port 5080. See Figure 4 below.
2. Using the alphabetically sorted forms (see Figure 3 on page 8), navigate to the Network Element form and click on the Add button.
The Network Element form manages the elements within a network. This form defines the network attributes such as name, IP address, SIP Peer information, and the external SIP ports.
Figure 5: Network Element Assignment
The following values should be changed in the Network Element Assignment form and all others should be left at their default values:
Name – Specifies the name of the Accelerator. This value should be unique and will be used in subsequent provisioning. You may want to use acronyms to help identify the elements. Using a single node Accelerator with both Mobile UC and PSTN Access enabled as an example, you could name the elements like MUC_Name and another element named PSTNA_Name.
Type
–
Set to Other. FQDN or IP Address
:
The physical IP address or hostname of the Accelerator. SIP Peer – Checked (enabled).
SIP Peer Transport – UDP.
SIP Peer Port – The port value will be 5060 for Mobile UC and 5080 for PSTN Access (if enabled).
External SIP Proxy Transport – UDP.
External SIP Proxy Port – The port value will be 5060 for Mobile UC and 5080 for PSTN Access (if enabled).
SIP Registrar fields should be left blank. Be sure to click the Save button.
Class of Service Options Assignment
3. Using the alphabetically sorted forms (see Figure 3 on page 8), navigate to the Class of Service Options Assignment form. This form will be referenced by the Trunk Attributes form in the next step (Step #4). You can create a separate COS for Mobile UC and PSTN Access, however, the settings are the same and you can use the same COS form.
Figure 6: Class of Service Options Assignment Selection
Choose one of the unused numbers (i.e. “9” in the above example) and select Change. The screen capture below is a partial representation of the data that is configurable on this screen but the specification that follows is complete. You may also want to include a Comment to help identify this COS.
Figure 7: Class of Service Options Assignment (partial)
The following values should be changed in the Class of Service Options Assignment form and all others should be left at their default values:
ANI/DNIS/ISDN Number Delivery Trunk – Yes.
Call Forwarding (External Destination) – Yes.
Display Caller ID on muticall/keylines – Yes.
Display Dialed Digits during Outgoing Calls – Yes.
HCI/CTI/TAPI Call Control Allowed – Yes.
HCI/CTI/TAPI Monitor Allowed – Yes.
Public Network Access via DPNSS – Yes.
Public Network to Public Network Connection Allowed – Yes.
Public Trunk – Yes.
Two B-Channel Transfer Allowed – Yes.
Trunk Service Assignment
4. Using the alphabetically sorted forms (see Figure 3 on page 8), navigate to the Trunk Attributes form. This form is used to assign a Class of Service to the trunk and whether or not any incoming digits (to the Mitel PBX) are to be absorbed or inserted.
The same Trunk Attribute can be used for Mobile UC and for PSTN Access (if enabled.) Note that you can create separate forms for each of these services if you wish.
Choose one of the unused numbers (i.e. “4” in the above example) and select Change.
Make note of this Trunk Attribute number as you will need in the future steps. You may need to ask your PBX administrator whether the Trunk Attribute number you have selected being used.
Figure 9: Trunk Service Assignment
The following values should be changed in the Trunk Service Assignment form and all others should be left at their default values:
Class of Service – Specify as defined in Step 3 on 11.
Dial In Trunks Incoming Digit Modification – Absorb - This value depends on your PBX dial plan and how you handle incoming numbers to the Mitel PBX. Our example specifies the number 0 (zero) meaning that no digits are to be ‘stripped’ or absorbed. If you are uncertain of the value that needs to be provisioned here, use the value 0 (zero). Do not leave this field blank. A blank value indicates that all incoming digits will be absorbed.
Dial In Trunks Incoming Digit Modification – Insert – In our
example we left this field blank meaning that no digits are to be inserted to the incoming digit stream. Do not insert a 0 (zero) as this will actually insert the zero digit.
Trunk Label – The recommendation is to leave this field blank as the value here populates the Calling Line ID.
SIP Peer Profile
5. Using the alphabetically sorted forms (see Figure 3 on page 8), navigate to the SIP Peer Profile form. This form is used to configure SIP trunks. Select Add. Create separate profiles for Mobile UC and PSTN Access (if enabled).
The following values should be changed in the SIP Peer Profile form and all others should be left at their default values:
SIP Peer Profile Label – Set to a unique name.
Network Element – Set to the value as described in Step 2 on page 10 for Mobile UC or PSTN Access (if enabled).
Address Type – IP Address of the Mitel PBX.
Maximum Simultaneous Calls – Enter the maximum allowable number of incoming and outgoing simultaneous calls for this peer. The value cannot exceed the number of SIP Trunk Licenses. This parameter depends on the call models of the customer and is an engineered value.
Trunk Service – Set to the value as described in Step 4 on page 13 for Mobile UC or PSTN Access (if enabled).
Private SIP Trunk – Yes.
Public Calling Party Number Passthrough – Yes.
Enable Mitel Proprietary SDP – No.
Force sending SDP in initial Invite message – Yes.
Session Timer – Set to 0. Be sure to click the Save button.
SIP Peer Profile Assignment by Incoming DID
Using the alphabetically sorted forms (see Figure 3 on page 8), navigate to the SIP Peer Profile Assignment by Incoming DID form. This form determines whether calls incoming to the Mitel PBX from the Accelerator are ‘allowed’ to proceed. The ‘To’ party is authenticated based on the information provisioned in this form. This form is used by both Mobile UC and PSTN Access services. Basically, this form defines which called
numbers are allowed to come into the PBX from this SIP trunk (or another provisioned SIP trunk) and includes incoming DIDs or the full range of allowed desk numbers. For example, desk numbers that begin with ‘50xx’ and are 4 digits in length will be defined as 50*. This definition
encompasses desk numbers such as 5001, 5002, 5051, etc.
If your Pilot DNs route through the Mitel PBX, then include those ranges in this form.
Note: If all or some of these numbers already exist on other SIP Peer Profiles they do not need to be added here.
Figure 12: SIP Peer Profile Assignment by Incoming DID
The following values should be changed in the SIP Peer Profile Assignment by Incoming DID form and all others should be left at their default values. You may also want to add a Comment to identify this range.
Incoming DID Range – Set to the range of incoming DIDs for this trunk. The Mitel PBX documentation describes this field attribute as:
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 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 '-'.
The following combinations are valid: 0010*
2000-3000, 55*, 8000 50*,33*
The following combinations are invalid: 55*-66* cannot use as a range 55*,5500 overlap
SIP Peer Profile Label – Should be set to the SIP Peer Profile Label configured previously for Mobile UC or PSTN Access services. (Step 5 on page 15).
ARS Digit Modification Plans
6. Using the alphabetically sorted forms (see Figure 3 on page 8), navigate to the ARS2 Digit Modification Plans form. This form species the
number of digits to absorb from the dialed number and the digits to insert during outpulsing to the Accelerator.
Choose one of the unused numbers and select Change.
One ARS Routes form should be created for Mobile UC and a separate one for PSTN Access (if enabled).
Figure 13: ARS Digit Modification Plans
The following values should be changed in the ARS Digit Modification Plans form and all others should be left at their default values:
Number of Digits to Absorb – Our example specifies the number 0 (zero) meaning that no digits are to be ‘stripped’ or absorbed for the Mobile UC service. Do not leave this field blank. A blank value indicates that all incoming digits will absorbed.
For PSTN Access, you will want to absorb any prefix digits before the call is sent to the Accelerator. For example, if you must first dial the digit ‘9’ before your number, you will want to remove it. For instance, when dialing a UK mobile number such as 07786xxxxxx that is prefixed with a ‘9’ (907786xxxxxx), you will want to remove just one digit (the ‘9’) and leave all other numbers intact.
ARS Routes
7. Using the alphabetically sorted forms (see Figure 3 on page 8), navigate to the ARS Routes form. This form assigns trunk number, digit
modification number, and route type. Choose one of the unused numbers and select Change.
One ARS Routes form should be created for Mobile UC and a separate one for PSTN Access (if enabled).
Make note of the route assignment number(s) as you will need them in future steps.
Figure 14: ARS Routes
The following values should be changed in the ARS Routes form and all others should be left at their default values:
Routing Medium – Set to SIP Trunk.
SIP Peer Profile – Set to the SIP Peer Profile configured previously in Step 5 on page 15.
Digit Modification Number – Set to the value defined in Step 6 on page 19. For Mobile UC, you will want to indicate the modification number that absorbs 0 digits. For PSTN Access, you will want to specify the
modification number that absorbs any prefix digits.
ARS Digits Dialed Assignment
8. Using the alphabetically sorted forms (see Figure 3 on page 8), navigate to the ARS Digits Dialed Assignment form. This form initiates the routing of trunk calls.
Select Add.
For PSTN Access, if you have a prefix that must be dialed so that calls route to the Accelerator, create an ARS Digits Dialed Assignment with an associated Route Assignment.
If routing Pilot DNs through the Mitel PBX, you will also want to create an ARS Digits Dialed Assignment so that calls to the Pilot numbers are routed to the Accelerator.
Figure 15: ARS Dialed Digits Assignment
The following values should be changed in the ARS Digits Dialed Assignment form and all others should be left at their default values:
Digits Dialed – Set to the start pattern of the offnet dialing prefix for PSTN Access calls. For Mobile UC, if routing pilots through the Mitel PBX, set to the start pattern for the pilot numbers. This includes Call Move Service Pilot Numbers. Note that Call Move pilots are required here even if routing regular pilots via a Carrier Gateway.
Number of Digits to Follow – Should be set to the number of digits that will follow the pattern specified in Digits Dialed.
Termination Type - Should be set to Route.
Termination Number - Should be set to the number of the ARS Routes created previously.
Class of Service Options Assignment
Note that Steps 9 and 10 are ‘preparation’ steps that are used by Step 11. These two ‘prep’ steps configure Mitel desk phones to also ring their mobile phones any time their desk phones are dialed.
9. Using the alphabetically sorted forms (see Figure 3 on page 8), navigate to the Class of Service Options Assignment form. This COS will be used when we create a new user and point their multiline appearances to an existing user (see Figure 24 on page 28).
Note that this example uses the same COS that was created earlier on page 11. You can, however, create a new COS by selecting an unused number and click Change.
The screen capture below is a partial representation of the data that is configurable on this screen, but the specification that follows is complete.
Figure 17: Class of Service Options Assignment (partial)
The following values should be changed in the Class of Service Options Assignment form and all others should be left at their default values:
ANI/DNIS/ISDN Number Delivery Trunk – Yes.
Call Forwarding (External Destination) – Yes.
Display Caller ID on muticall/keylines – Yes.
Display Dialed Digits during Outgoing Calls – Yes.
HCI/CTI/TAPI Call Control Allowed – Yes.
HCI/CTI/TAPI Monitor Allowed – Yes.
Public Network Access via DPNSS – Yes.
Public Network to Public Network Connection Allowed – Yes.
SIP Device Capabilities
10. Using the alphabetically sorted forms (see Figure 3 on page 8), navigate to the SIP Device Capabilities form. This form will be used when we create a new user and point their multiline appearances to an existing user (see Figure 24 on page 28).
Note the SIP device capabilities number as you will need it in later steps.
Figure 18: SIP Device Capabilities Assignment
Choose one of the unused numbers (i.e. “4” in the above example) and select Change. Ensure that the Force sending SDP in initial Invite message option is set to Yes. Leave all other fields at their default values.
User and Device Configuration
11. Using the alphabetically sorted forms (see Figure 3 on page 8), navigate to the User and Device Configuration form to create a new user. This new user will simultaneously ring the Accelerator so that the mobile can be alerted when the associated user’s existing desk number is dialed. This document assumes that the user already has multiple line
appearances provisioned so that if the user is on their desk phones any new incoming calls can ‘roll’ to the next line appearance.
In the example below, our existing user has a desk extension of 5001. A new user was created using number 5051. The point of this exercise is to map the new user’s multiline key (Extension related to Tango solution) to the original user’s desk extension.
You are creating a new SIP device that will be associated to the existing user’s phone. This notifies the Accelerator when the user gets a call on their original desk phone.
Here is the original user’s (5001) configuration. No modification is required for any of the existing user tabs.
Here is the original user’s (5001) multiline key definitions. No modification is required.
Figure 21: Keys tab Configuration – Existing User 5001
Here is the new user’s (5051) definition. A new user will need to be created for each Accelerator user so that when the user’s desk phone is dialed, their mobile phone is also alerted.
Figure 22: Multiline Configuration – New User 5051
The following values should be changed in the new user’s Profile tab and all others should be left at their default values:
Last Name and First Name – Should be set to the same values as the user this multiline user will be associated with.
Device Type – Set to Generic SIP Phone.
Voice Mail and Desktop Admin – NOT be checked. If checked, a new voice mail box and desktop admin account will be created.
Navigate to the Keys tab for the new user and point the keys to the original user at 5001.
It is important to note that the new user’s key definitions will need as many multiline appearances (i.e., the number of lines) that appear on the original user’s desk phone. In other words, the original user has 3 key definitions which means the new user will need the same number of keys.
Figure 23: Keys tab Configuration – New User 5051
Now select the Service Details tab for the new user and ensure that the Class of Service (from page 22) and SIP Device Capabilities (from page 24) are configured based on the previous steps of this document.
Note that Class of Restriction fields define which calls cannot access an outgoing trunk route. Since we only use the SIP line for receiving terminations to the desk number, this setting does not apply to us.
Accelerator Provisioning
Note: This document assumes that the Accelerator has already been provisioned with:
- Enterprise information
- Wireless carrier information. The Carrier(s) should be enabled for Mobile UC and/or PSTN Access.
Mobile UC Enabled Accelerator
The section discusses the integration process for a Mobile UC with/without a PSTN Access enabled Accelerator.
The steps below describe the unique configuration areas needed to integrate the Mitel PBX with the Accelerator solution. Refer to the Accelerator
Provisioning Guide for a comprehensive explanation of Accelerator
provisioning.
Voice Network: PBX/Trunk Dial Plan
1. Add Trunk Dial Plan (required) – There are no unique configuration items for Trunk Dial Plans and the Mitel PBX. Refer to the Accelerator
Provisioning Guide, Voice Networks, PBXs,Add Trunk Dial Plan section.
2. Add PBX (required) – No unique configuration items for adding a PBX. Refer to the Accelerator Provisioning Guide, Voice Networks, PBXs, Add
New PBX section.
If your enterprise intends to use the Route via Enterprise mobile policy by routing Pilot DNs through the PBX to the Accelerator, go ahead and provision the Pilot DNs on the PBX’s main page under the Pilot Numbers section. Note that the Pilots here must be E.164 routable.
Also, if your enterprise intends to use the Call Move service, go ahead and provision the Call Service Pilots on the PBX’s main page under the Call Service Pilot Numbers section. Note that the Pilots here do not have to be E.164 routable. Note that the Call Move feature access code can be found on the Accelerator provisioning page at: Services ->Feature Settings.
Add Trunk Groups/Trunk (required) –If the hostname is entered, the Accelerator queries the DNS server for the associated DNS SRV records. This allows for redundancy and/or load balancing based on the DNS SRV records if the customer has deployed multiple Mitel servers. Refer to the Accelerator Provisioning
Guide, Voice Networks, PBXs (Add/Modify), Add Trunk Groups/Trunks
section.
o Trunk Group Request URI parameters are not used by the Mitel PBX and therefore do not need to be provisioned.
Add Line Groups/Line (required) –o Host Address, Port and Transport Type should match the IP Address of the Mitel PBX with a port value of 5060.
If the hostname is entered, the Accelerator queries the DNS server for the associated DNS SRV records. This allows for redundancy and/or load balancing based on the DNS SRV records if the customer has deployed multiple Mitel servers. Accelerator Provisioning Guide, Voice
Networks, PBXs (Add/Modify), Add Line Groups/Line section.
o Line Group Request URI parameters are not used by the Mitel PBX and therefore do not need to be provisioned.
Add CTI Peer connection (required for Call Move service) - A CTI Peer will need to be configured for each extension range defined for the Mitel PBX.o Only Use Extension in CTI Requests and Monitor Desk Phones for MWI should both be checked. Refer to the Accelerator
Provisioning Guide, Voice Networks, PBXs (Add/Modify), Add CTI Peer
section.
Add Least Cost Routing (optional) - No unique configuration items for Least Cost Routing. Refer to the Accelerator Provisioning Guide, VoiceNetworks, PBX, Least Cost Routes, Add Least Cost Routes section.
Voice Network: Extension Ranges
3. Add Extension Ranges (required) – No unique configuration items for adding an Extension Range. Refer to the Accelerator Provisioning Guide,
Voice Networks, Extension Ranges, Add New Extension Ranges section.
Voice Network: Carrier Gateways
4. Carrier Gateways (required if your enterprise routes calls between the wireless carrier and the Accelerator) – If your enterprise intends to use an SBC or Carrier Gateway between the carrier and the enterprise, then add a Carrier Gateway. Be sure to supply the Outbound Domain as required by the add Carrier Gateway page.
Add Trunk Groups/Trunk (required if using a Carrier Gateway) – o Host Address, Port and Transport Type should match the value ofthe carrier’s SIP endpoint.
If the hostname is entered, the Accelerator queries the DNS server for the associated DNS SRV records. This allows for redundancy and/or load balancing based on the DNS SRV records if the customer has deployed multiple Mitel servers. Refer to the Accelerator Provisioning
Guide, Voice Networks, Carrier Gateway (Add/Modify), Add Trunk
Groups/Trunks section.
Trunk Group Request URI parameters are normally not required by most SIP endpoints, however, consult your carrier’s instructions.
Add Least Cost Routing (optional) - No unique configuration items for Least Cost Routing. Refer to the Accelerator Provisioning Guide, Voice Networks, Carrier Gateway, Least Cost Routes, Add Least Cost Routessection.
Voice Network : Voice Mail
5. Add Voice Mail for the Mitel PBX in the Accelerator system. Select PBX as the Voice Mail Server Type. Refer to the Accelerator Provisioning
Guide, Voice Networks, Voice Mail Servers, Add Voice Mail Server section.
Subscriber Dial Plan/Subscribers
6. Add Subscriber Dial Plan - (required) - No unique configuration items for adding Subscriber Dial Plans. Refer to the Accelerator Provisioning
Guide, Subscribers, Add Subscriber Dial Plan section.
7. Add Subscribers (required) - Several items to note when provisioning subscribers:
Enterprise Desk Number - Should match the extension provisioned on the Mitel PBX for the user.
Home PBX – Select the newly created Mitel PBX as the subscriber’s Home PBX.
Direct Inward Dial (DID) - Should match the full national phone
number provisioned on the Mitel PBX for this user. The value here on the subscriber page is recommended if the subscriber’s DID does not map directly to their desk extension. If the subscriber’s DID does map directly to their desk extension, provision their DID in the Extension Range page under the DID Supported section.
SIP Address - Should match the directory number of the Multi-Line user that is associated with this subscriber. This value maps to the Mitel new user’s ‘Number’ bullet found on page 27.
Line Group – Should match the IP address of the Mitel PBX.
If you have only Mobile UC enabled in your Accelerator license key then you are finished. Proceed to the Useful Commands section on page 33 to verify your configuration.
If you also have PSTN Access enabled, proceed to the next section, PSTN Access Enabled Accelerator on page 32.
PSTN Access Enabled Accelerator
If your configuration is Mobile UC only, refer to section Mobile UC Enabled Accelerator starting on page 29.
The steps below describe the unique configuration areas needed to integrate the Mitel PBX with the Tango solution for PSTN Access services. Refer to the
Accelerator Provisioning Guide for a comprehensive explanation of Accelerator
provisioning.
Note: If your configuration is Mobile UC and PSTN Access, notice that most of the configuration areas have been addressed in the Mobile UC section just above. You must, however, create new PSTN Access provisioning on the Accelerator; you cannot reuse the ones provisioned for Mobile UC.
Voice Network: Trunk Dial Plan/PBX
1. Add Trunk Dial Plan (required for routing calls to/from Accelerator to Mitel PBX) – There are no unique configuration items for Trunk Dial Plans and the Mitel PBX. Refer to the Accelerator Provisioning Guide, Voice
Networks, PBXs,Add Trunk Dial Plan section.
2. Add PBX (required) – No unique configuration items for adding a PBX. Refer to the Accelerator Provisioning Guide, Voice Networks, PBXs, Add
New PBX section.
Add Trunk Groups/Trunk (required) –o Host Address, Port and Transport Type should match the IP Address of the Mitel PBX with a port value of 5060.
If the hostname is entered, the Accelerator queries the DNS server for the associated DNS SRV records. This allows for redundancy and/or load balancing based on the DNS SRV records if the customer has deployed multiple Mitel servers. Refer to the Accelerator Provisioning
Guide, Voice Networks, PBXs (Add/Modify), Add Trunk Groups/Trunks
section.
o Trunk Group Request URI parameters are not used by the Mitel PBX and therefore do not need to be provisioned.
Add Least Cost Routing (optional) - No unique configuration items for Least Cost Routing. Refer to the Accelerator Provisioning Guide, VoiceVoice Network: Extension Ranges
3. Add Extension Ranges (required) – No unique configuration items for adding an Extension Range. Refer to the Accelerator Provisioning Guide,
Voice Networks, Extension Ranges, Add New Extension Ranges section.
This completes the PSTN Access section. Proceed to the next section, Useful Commands on page 33 to verify your configuration.
Useful Commands
View Line Registration Status
Using Mitel’s View by Category menu (refer to the 1st picture of Figure 3 on
page 8), navigate to Maintenance and Diagnostics -> IP Telephony Inventory -> All IP Telephones. Your phones should show In Service.
Figure 25: Mitel Maintenance Command All IP Telephones
The Mitel documentation describes the possible State field values as:
Start - The telephone has registered successfully with the ICP directly after powering up or rebooting.
Forced - The telephone was redirected to this ICP by another ICP.
Hand Off - The telephone was intentionally handed-off to this ICP by another ICP (for example, due to login or failback).
Fail Over - The telephone has re-homed after losing contact with its ICP (for example, due to ICP failure, network error, etc.). On resilient phones, this message indicates the phone lost contact with its ICP and then reestablished contact with either its primary or secondary ICP. On non-resilient phones, the message indicates the phone lost and then reestablished contact with its home ICP.
Network Error - Hand off error - ICP unreachable - the phone can't find the ICP to which it was handed off (most probably due to a network error).
Set Error - ACK expiry - there was a communication error between the phone and the ICP.
Set Error - PIN timeout.
SSL Retry - Set registered on non-SSL port and asked to re-register
System Error - ICP generated failure.
System Error - Hand off error - no DB entry.
System Error - Hand off error - set type mismatch.
Unknown.
Link Status between Mitel PBX and Accelerator
Using the alphabetically sorted forms (see Figure 3 on page 8), navigate to the Maintenance Commands form. Enter the following command:
SIP LINK STATE ALL [Enter] or click the Submit button The link should show IN SERVICE.
Link Status between Accelerator and Mitel PBX
Launch the Accelerator Management Console and navigate to the Session Conductor element3. Click the Alarm icon on the toolbar and determine if the
2010 Alarm ID exists. If present, the connectivity between the Accelerator and the Mitel PBX is in trouble. If the alarm does not exist then no errors are reported and the link should be operational.
Mobile UC Feature Interactions
The intent of the Tango solution is to seamlessly add a mobile component to all of the services that 3300 provides to the end user. The Tango system is integrated with PBXs at three levels of integration for Mobile UC. The Mitel 3300 is integrated at Level 2. This section explains the PBX features that have been integrated with this Accelerator release. Features that are not yet
supported are indicated as such in the summary tables following the feature descriptions.
Accelerator PBX Level 1 Integration
Integration Level 1 provides the subscriber basic services that are commonly used.
Table 1 Accelerator PBX Level 1 Integration
Feature Support Comments
Abbreviated Dialing Yes Ad Hoc Conferencing (Internal to PBX) No Ad Hoc Conferencing (External to PBX) Yes
Uses an external IP Media 2000 conference server. Refer to the Accelerator Provisioning Guide, Voice Networks, Conference Servers section.
Call Forward All (Desk) Yes Call Forward All Activation from Mobile Yes Call Forward Busy (Desk) Yes Call Forward Busy Activation from Mobile Yes Call Forward No Answer (Desk) Yes Call Forward No Answer Activation from Mobile Yes Call Hold and Retrieve (Mobile) Yes Call Line Identification (CLID) Yes Call Transfer – Blind Yes Call Transfer – Consultative Yes Call Waiting and Retrieve Yes Direct Inward Dialing Yes Direct Outward Dialing Yes
Directory Dial Yes
Flexible Dialing Support Yes Intelligent Call Delivery Yes Least Cost Routing Yes Meet-Me Conference Yes Multiple Calls per Line Yes PBX Do Not Disturb (Desk) Yes PBX Do Not Disturb (Mobile) Yes Single Number Services Yes Voice Mail Message Waiting Indication Yes
The following features are considered Level 1:
Ad Hoc Conferencing (Internal to PBX)- Allows an Accelerator subscriber to initiate a reservation-less conference from a mobile phone using the conference resources of the PBX.
Ad Hoc Conferencing using (External to PBX) - Allows an Accelerator subscriber to initiate a reservation-less conference from a mobile phone using external media server located in the enterprise.
Call Forward All (Desk) - Allows users to forward all calls to another destination including those calls to the mobile number. This feature is activated via the desk phone.
Call Forward Activation on Mobile - - Allows users to forward all calls to another destination. Users enter a feature access code on their mobile phone to activate or deactivate call forwarding.
Call Forward Busy (Desk) - Allows users to forward calls (including those to their mobile number) to another destination when their device is busy. Users activate or deactivate the Call Forward Busy capability with a Call Forward Busy feature button from their desk phone
Call Forward Busy Activation on the Mobile - Allows users to forward calls to another destination when their device is busy. Users activate or deactivate the Call Forward Busy capability with a feature access code from their mobile phone.
Call Forward No Answer (Desk) - Allows users to forward calls(including calls to their mobile number) to another destination when their device is not answered. Users activate or deactivate the Call Forward No Answer capability with a Call Forward No Answer feature button from their desk phone
Call Forward No Answer Activation on Mobile - Allows users to forward calls to another destination when their device is not answered. Users activate or deactivate the Call Forward No Answer capability with a feature access code from their mobile phone.
Call Hold and Retrieve (Mobile) – Lets users temporarily disconnect from a call, use the telephone for another call, and then return to the original call. The Accelerator solution supports this capability in concert with the wireless network.
Call Line Identification (CLID) – Provides the user information about the calling party. Accelerator supports calling line identification when it is the called party. Accelerator also supports ensuring that the enterprise identity of the caller is preserved when a call is initiated from the mobile phone. In this case although the call is made from a mobile, the calling line ID will be that of the Accelerator user's desktop phone. The enterprise main number may also optionally be used in place of a subscriber’s DID for off-net calling.o Consultative Call Transfer - Call is transferred allowing interaction between the user who initiated the transfer and the transfer
destination.
Call Waiting and Retrieve - Provides users with an audible alert in the voice stream that a new incoming call is waiting. The user can retrieve the call from the desk phone. Accelerator supports call waiting in concert with the wireless network. Call Waiting tones are provided by the mobile phone when an incoming call is waiting, and waiting calls can be retrieved from the mobile phone.
Direct Inward Dialing - Allows the desk phone to be directly accessed from the PSTN. The Accelerator solution supports enterprise Direct Inward Dialing.
Direct Outward Dialing - Allows users inside an enterprise to dial directly to an external number. The Accelerator solution supports the mobile device dialing directly to an external number.
Directory Dial - Lets users select numbers to dial from a corporate or personal directory. Accelerator supports using a personal directory on the phone and handles the translations of those digits into on-net network numbers if appropriate. In addition, Accelerator support a corporate directory look up capability for access to the corporate address book.
Flexible Dialing Support - The Accelerator has a flexible dialing plan enabling PBX services to be provided to mobile users.
Intelligent Call Delivery - Ensures that both the desk phone and mobile phone ring when the dialed number is an Accelerator subscriber.
Least Cost Routing – For mobile originations and terminations, the Accelerator ensures that the least cost route is used. This results in the enterprise voice network being used to route the call as much as possible, reducing PSTN interconnect costs, and other voice costs such as roaming.
Meet-Me Conference - Allows users to set up a dial-in conference of up to six parties. The mobile user can participate in the meet-me conference by dialing the conference bridge.
Multiple Calls per Line – Allows multiple calls to be delivered to a single number and have the incoming call information displayed to the user. Accelerator supports this feature on the mobile phone based on the ability to support call waiting for mobile phone devices. Mobile devices typically show a maximum of two lines per mobile phone.
PBX Do Not Disturb (Desk) – Allows users to activate or deactivate the Do Not Disturb capability by pressing a button or a softkey from their desk phone. When active, Do Not Disturb will not ring the mobile or desk phone.
PBX Do Not Disturb (Mobile) - Allows users to activate or deactivate the Do Not Disturb capability by entering a feature access code from their mobile phone. When active, Do Not Disturb will not ring the mobile phone however the desk phone will continue to ring.
Voice Mail Waiting Indication - Provides a visible indication on the mobile phone that there is a message waiting in the voice mail system. Accelerator supports supplying a Message Waiting indication on the mobile phone that indicates that there are voice mail messages in the enterprise voice mail system.
Accelerator PBX Level 2 Integration
Integration Level 2 provides the subscriber more advanced features than more commonly used basic features.
Table 2 Accelerator PBX Level 2 Integration
Feature Support Comments
Call Accounting Codes No Call Coverage/Hunt Groups Yes Call Line Identification Restriction (CLIR) (Mobile) Yes Call Pull (Desk->Mobile Call Move) Yes Call Push (Mobile->Desk Call Move) Yes Class of Restriction (COR) (PBX) Yes Class of Service (COS) (PBX) Yes
The following features are considered Level 2 integration targets:
Call Accounting Codes - To support the mobile office environment, client billing must be supported when the user is away from his/her desktop phone and using a mobile phone. For example, law offices, accounting firms, consulting firms and other organizations benefit from tracking the length of a call for a client. Client billing is achieved by having the user enter a code to specify that the call relates to a specific client matter or account. The code, which is often referred to as a client matter code (CMC) or call accounting code, can be assigned to customers, students, or other populations for call accounting and billing purposes. Call accounting codes are used by enterprise to manage call accounting.
Call Coverage/Hunt Groups - Allows a group of extensions to be set up to handle multiple calls to a single telephone number. For each call to the number, the PBX hunts for an available extension in the hunt group and connects the call to that extension. The Accelerator can be defined as one of the extensions.
Call Line Identification Restriction (CLIR) (Mobile) - Allows the user to restrict their calling line information from being displayed to the called number. Accelerator supports restriction of calling line identification from mobile phones. Enterprise identity will be replaced; however restriction code will be preserved.
Call Pull (Desk->Mobile Call Move)- Allows a subscriber to move a phone call between the desk phone and the mobile phone. Feature is invoked from the mobile phone.
Class of Restriction (COR) (PBX) - Defines the restrictions that apply when a user places or receives a call. The Accelerator supports COR for mobile originated calls.
Class of Service (COS) (PBX) - Allows or denies user access to some system features. The Accelerator supports COS for mobile originated calls over SIP lines.
Accelerator PBX Level 3 Integration
Integration Level 3 provides features that are specific to the PBX or specific to vertical markets.
