ACCELERATOR 6.3 AASTRA MX-ONE INTEGRATION GUIDE

Transcription

1 ACCELERATOR 6.3 AASTRA MX-ONE INTEGRATION GUIDE September 2014 Tango Networks, Inc. phone: Parkwood Blvd, Suite 500 fax: Frisco, Texas USA

2 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 Tango Networks, Inc. Tango Networks is a trademark s or registered trademarks of Tango Networks, Inc. All other trademarks or service marks are the property of their respective owners. Specifications and features are subject to change without notice. September 2014 CONFIDENTIAL Page 2 of 51

3 TABLE OF CONTENTS INTRODUCTION... 6 SUPPORTED VERSIONS... 7 PBX DEPENDENCIES... 7 AASTRA MX-ONE LICENSE KEY REQUIREMENTS... 7 KNOWN AASTRA MX-ONE ISSUES... 8 ACCELERATOR INTEGRATION PROCSSES... 9 MOBILE UC AND PSTN ACCESS ENABLED ACCELERATOR... 9 MOBILE UC ENABLED ACCELERATOR... 9 PSTN ACCESS ENABLED ACCELERATOR...10 Login to Aastra Admin Interface...11 Create Aastra SIP Trunks...11 Accelerator Single/Mini Node...12 Accelerator 2 Node (and Legacy 3 Node)...12 Add Aastra Trunk(s)...14 Create Route Patterns for Pilot DNs...18 Create a Route for PSTN Access Numbers...24 Create a Route Pattern for PSTN...30 SIP Line Configuration...34 CSTA Configuration...41 ACCELERATOR PROVISIONING...42 Mobile UC Enabled Accelerator...42 Voice Network: PBX/Trunk Dial Plan...42 PSTN Access Enabled Accelerator...43 Voice Network: PBX...43 Useful Commands...43 Link Status between MX-One and Accelerator...43 Link Status between Accelerator and MX-One...44 MOBILE UC FEATURE INTERACTIONS ACCELERATOR PBX LEVEL 1 INTEGRATION...45 ACCELERATOR PBX LEVEL 2 INTEGRATION...48 ACCELERATOR PBX LEVEL 3 INTEGRATION...49 ACRONYMS September 2014 CONFIDENTIAL Page 3 of 51

4 FIGURES Figure 1 Aastra MX-One Administration Web Interface...11 Figure 2 Aastra SIP Trunks - Accelerator Single Node/Mini...12 Figure 3 Aastra SIP Trunks For Accelerator 2 Node (or 3 Node Legacy)...13 Figure 4 Subsystem Menu Add New Route...14 Figure 5 Route Configuration Step Figure 6 Route Configuration Step Figure 7 Route Configuration Step 3 cont Figure 8 Route Configuration Step Figure 9 Route Configuration Step Figure 10 Route Configuration Step Figure 11 Route Configuration Step Figure 12 Route Configuration Complete...18 Figure 13 Destination Menu Step Figure 14 Destination Menu Step Figure 15 Destination Menu Add New Number Series...20 Figure 16 Destination Menu Add New Number Series Step Figure 17 Destination Menu Add New Number Series Step Figure 18 Destination Menu Add New Number Series Complete...22 Figure 19 Destination Menu...22 Figure 20 Destination Menu...23 Figure 21 Destination Menu Step Figure 22 Destination Menu Add - Result...24 Figure 23 Subsystem Menu Add New Route...24 Figure 24 Subsystem Menu Add New Route Step Figure 25 Subsystem Menu Add New Route Step Figure 26 Route Configuration Step 3 cont Figure 27 Route Configuration Step Figure 28 Route Configuration Step Figure 29 Route Configuration Step Figure 30 Route Configuration Step Figure 31 Route Configuration Complete...29 Figure 32 Destination Menu Step Figure 33 Destination Menu Step Figure 34 Destination Menu Add New Number Series...31 Figure 35 Destination Menu Add New Number Series Step Figure 36 Destination Menu Add New Number Series Step Figure 37 Destination Menu Add New Number Series Complete...32 Figure 38 Destination Menu...33 Figure 39 Destination Menu...33 Figure 40 Destination Menu Step Figure 41 Destination Menu Add - Result...34 Figure 42 Extension Menu...35 Figure 43 Extension Menu Add Step Figure 44 Extension Menu Add Step Figure 45 Extension Menu Add Result...37 Figure 46 SIP Device Configuration DN Assignment...38 Figure 47 Directory Number Assignment...38 Figure 48 Directory Number Assignment Extension Change...39 Figure 49 DN Assignment Extension Change Advanced...40 Figure 50 DN Assignment Extension Change Result...41 Figure 51: Accelerator Management Console, Alarm Viewer...44 September 2014 CONFIDENTIAL Page 4 of 51

5 TABLES Table 1 Accelerator PBX Level 1 Integration...47 Table 2 Accelerator PBX Level 2 Integration...48 Table 3 Accelerator PBX Level 3 Integration...49 Table 4 Acronyms...50 September 2014 CONFIDENTIAL Page 5 of 51

6 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 was created that enabled one or both of these services. How you integrate your Aastra MX-OneMX-One PBX with the Accelerator depends on how your carrier 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 Voic , and Abbreviated Dialing. For Mobile UC, the Accelerator uses a combination of SIP lines and trunks to integrate with the Aastra PBX. o o o SIP Trunk Interfaces Used for providing terminating services for calls from the Accelerator. For terminating call types where the call is being terminated to an Accelerator subscriber's desk or mobile. SIP Line Interfaces Used to provide originating services and for simultaneous ringing of a subscribers desk and mobile devices. When an Accelerator UC Subscriber places a mobile origination call (RVE) the Accelerator will deliver the call to the PBX using the line interface. This allows the PBX to provide that subscribers originating services to the call. CSTA CSTA must be provisioned for the Call Move feature. However, this feature does not work at this time. 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 Aastra PBX; there are no SIP lines associated with the Accelerator trunking service. In general, PSTN Access is used when the Accelerator must relay a call from the Aastra PBX desk phone to the PSTN. And, vice-versa; PSTN originated calls to DIDs assigned to the Aastra PBX will be routed from the carrier to the Accelerator PSTN Access service to the PBX. September 2014 CONFIDENTIAL Page 6 of 51

7 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 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 integrates with Aastra MX-One. The document supports Aastra MX-One 5.0. This guide is meant to familiarize the reader with the minimum provisioning steps required on the Aastra MX-One for Accelerator integration. It does not attempt to address all possible configurations options or features that can be applied within the MX-One. Please consult your Aastra documentation for MX-One specific issues. The screen captures in this document may vary depending on your release. It is intended for users with a thorough understanding of the Aastra MX-One. PBX Dependencies The following lists the Aastra MX-One components, license keys, and PBX dependencies required to integrate with the Accelerator: Aastra MX-One For Mobile UC - Per Subscriber license enabling an extension. This may or may not require additional licensing depending on the existing licensing package. The MX-One server(s) must first be configured appropriately with domain and host information as per MX-One documentation before integrating with the Accelerator. Aastra MX-One License Key Requirements The Aastra MX-ONE licenses needed for this integration are: SIP trunk licenses, please note that the quantity of licenses depend on how the system is deployed. 3 rd Party SIP Device License for each Abrazo user CSTA-PHASE3-INTERFACE license needed for each Abrazo user that will be provisioned for Call Move services. Please always check with your Aastra partner that your system has the correct licenses, before beginning the integration deployment. September 2014 CONFIDENTIAL Page 7 of 51

8 Known Aastra MX-One Issues 1. The Call Move feature does not currently work with Aastra. 2. MWI has not been tested with Aastra. September 2014 CONFIDENTIAL Page 8 of 51

9 Accelerator Integration Procsses The integration with the Accelerator can be setup in several ways. During the Accelerator provisioning, your enterprise selected Carrier types 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 Aastra MX-OneMX-One PBX with the Accelerator. Mobile UC and PSTN Access Enabled Accelerator For a Mobile UC and PSTN Access enabled Accelerator, execute both sets of steps outlined below; Mobile UC Enabled Accelerator section and the PSTN Access Enabled Accelerator section. It does not matter which set you execute first, meaning it does not matter if you provision PSTN Access first or Mobile UC first. Mobile UC Enabled Accelerator The Accelerator requires both SIP Line and SIP Trunk provisioning within the MX-One to provide full functionality. In addition, in order to enable the optional Call Move feature, CSTA must be provisioned within the MX-One. However, the Call Move feature does not work at this time. For a Mobile UC enabled Accelerator, execute these steps. 1. Login to Aastra Admin Interface on page Create Aastra SIP Trunks to route traffic between the MX-One and the Accelerator. See page Create Route Patterns for Pilot DNs on page 18. This is an optional step based on your Carrier connection. These route patterns are used for Pilot DNs to the Accelerator. 4. Create SIP Line Configuration to support the mobile devices as SIP devices. See page If you intend to use the Accelerator Call Move feature, create the CSTA connection to enable the Call Move service. See section CSTA Configuration on page Execute the Mobile UC Enabled Accelerator section on page 42. September 2014 CONFIDENTIAL Page 9 of 51

10 PSTN Access Enabled Accelerator Use the following steps to define SIP trunks and Routing on the Aastra PBX for interactions with the Accelerator PSTN Access service. 1. Login to Aastra Admin Interface on page Create Aastra SIP Trunks to route traffic between the MX-One and the Accelerator. See page Create a Route Pattern on page 24 to route PSTN calls and/or all calls (when Accelerator supports inter-pbx traffic) to the Accelerator. 4. If your Accelerator is PSTN Access only, then execute the steps list in section PSTN Access Enabled Accelerator on page However, if your Accelerator is a combination of both Mobile UC and PSTN Access, and you have not executed the PBX integration steps for Mobile UC listed on the previous page, execute that section now. Otherwise, you are finished with the PBX-side integration. Execute the section Mobile UC Enabled Accelerator on page 42. September 2014 CONFIDENTIAL Page 10 of 51

11 Login to Aastra Admin Interface After ensuring that the MX-One server(s) are configured appropriately with domain and host information, use the following steps to login to the MX-One. Access the MX-One administration web interface by pointing a web browser to the URL: or IP Address/ Hostname represents the hostname of the MX-One server. Log-in with the appropriate credentials. The first screen of the interface is displayed. Figure 1 Aastra MX-One Administration Web Interface Create Aastra SIP Trunks For a Mobile UC enabled and/or PSTN Access enabled Accelerator, SIP trunks must be configured between the Aastra MX-One PBX and the Accelerator. The number of SIP trunks that must be configured depends on whether the Accelerator is a redundant system or not. September 2014 CONFIDENTIAL Page 11 of 51

12 Accelerator Single/Mini Node One trunk for each enabled service. If both Mobile UC and PSTN Access are enabled then a total of 2 trunks will be needed with different ports. Mobile UC uses port 5060 and PSTN Access uses port See Figure 2 below. Also, if you need to change the Accelerator port numbers 5060 or 5080, visit the Tango Management Console Reference Guide, section Configuration, Cluster-Level Configuration, Session Conductors, System Settings Tab, and then find the Receiving Sip Port fields. Figure 2 Aastra SIP Trunks - Accelerator Single Node/Mini Accelerator 2 Node (and Legacy 3 Node) Only the trunk corresponding to the Accelerator s service Address is used for routing purposes as this is the address associated with the Accelerator s internal distributor. The session conductor trunks are required for authentication purposes only so that the MX-One accepts incoming requests without requiring Digest authentication. Note that the Legacy 3 node configuration is not shown in this document. Mobile UC configurations uses a total of 3 trunks where: September 2014 CONFIDENTIAL Page 12 of 51

13 1 st trunk - Physical address of Accelerator sc1 with port nd trunk Service Address with port rd trunk - Physical address of Accelerator sc2 with port 5070 PSTN Access configurations uses a total of 3 trunks where: 1 st trunk - Physical address of Accelerator sc1 with port nd trunk Service Address with port rd trunk - Physical address of Accelerator sc2 with port 5090 Both Mobile UC & PSTN Access configurations uses a total of 6 trunks where: Mobile UC Portion: o 1 st trunk - Physical address of Accelerator sc1 with port 5070 o 2 nd trunk Service Address with port 5060 o 3 rd trunk - Physical address of Accelerator sc2 with port 5070 PSTN Access Portion: o 1st trunk - Physical address of Accelerator sc1 with port 5090 o 2nd trunk Service Address with port 5080 o 3rd trunk - Physical address of Accelerator sc2 with port 5090 Figure 3 Aastra SIP Trunks For Accelerator 2 Node (or 3 Node Legacy) September 2014 CONFIDENTIAL Page 13 of 51

14 Add Aastra Trunk(s) Reminder: The number of trunks you will need to create is based on whether you are a single/mini node Accelerator or a redundant node Accelerator. And If you have Mobile UC and/or PSTN Access enabled Carriers defined on the Accelerator. An explanation can be found a few pages back, referring to Figure 2 and Figure 3. To configure new SIP trunks, select System Subsystem Subsystem Name. From the Subsystem Menu select External Lines Route and then click the Add button. Figure 4 Subsystem Menu Add New Route For type of signaling, select IP Public, SIP from the drop down and click the Next button. The following Route Configuration screen will be displayed. Figure 5 Route Configuration Step 2 September 2014 CONFIDENTIAL Page 14 of 51

15 Type in a route name and select a route number from the drop down menu and hit Next. There is no need to click the Advanced button as the defaults are being accepted. Figure 6 Route Configuration Step 3 September 2014 CONFIDENTIAL Page 15 of 51

16 For Outgoing Traffic, select udp protocol, enter the Accelerator IP into the Proxy Address field. In the Invite URI String for Unknown Public Number, enter the MX-One IP into fields. In the From URI String for Unknown Public Number, enter the Accelerator IP address. All other fields are left at their default value. Figure 7 Route Configuration Step 3 cont. The last fields of Part 3 are shown for informational purposes. These can be left at their default values. Figure 8 Route Configuration Step 4 September 2014 CONFIDENTIAL Page 16 of 51

17 Enter server number as required. In the example 1 is used. Figure 9 Route Configuration Step 5 All defaults are accepted on Step 5 / 7 Figure 10 Route Configuration Step 6 Accept defaults September 2014 CONFIDENTIAL Page 17 of 51

18 Figure 11 Route Configuration Step 7 Name Identity is not necessary. Leave blank and hit Apply to complete. Figure 12 Route Configuration Complete Create Route Patterns for Pilot DNs Note: If you have a direct data link from the carrier to the enterprise via an SBC this section can be skipped. The SBC is provisioned as a Carrier Gateway on the Accelerator. This section applies to those Accelerator configurations with Mobile UC enabled. Based on your connection to the Carrier, this section discusses creating Pilot Directory Numbers (PDNs). To configure a new Number Series, select System Subsystem Subsystem Name. From the Subsystem Menu select External Lines Destination and then click the Add button. September 2014 CONFIDENTIAL Page 18 of 51

19 Figure 13 Destination Menu Step 1 For Type of Destination select Destination and hit Next Figure 14 Destination Menu Step 2 Beside the Destination field hit Edit. September 2014 CONFIDENTIAL Page 19 of 51

20 Figure 15 Destination Menu Add New Number Series Select Add. Figure 16 Destination Menu Add New Number Series Step 1 Select the Number Series Type: External numbers, then hit Next. September 2014 CONFIDENTIAL Page 20 of 51

21 Figure 17 Destination Menu Add New Number Series Step 1 In our example, we are using 0188 and 0189 as our Pilot DNs. So enter 018 in the External Destination field then hit apply. September 2014 CONFIDENTIAL Page 21 of 51

22 Figure 18 Destination Menu Add New Number Series Complete Hit Done Figure 19 Destination Menu After returning to the Number Series menu, hit Back September 2014 CONFIDENTIAL Page 22 of 51

23 Figure 20 Destination Menu You are back to the Destination Menu Step 2. Select the Destination just created and then the Route Name created when adding the trunk, then hit next. Figure 21 Destination Menu Step 3 Leave all fields to their defaults and hit Apply. September 2014 CONFIDENTIAL Page 23 of 51

24 Figure 22 Destination Menu Add - Result Create a Route for PSTN Access Numbers This section concerns only those Accelerator configurations with PSTN Access configurations. These steps listed here are used to route PSTN calls and/or all calls (when Accelerator supports inter-pbx traffic) to the Accelerator. To configure Route Patterns, select System Subsystem Subsystem Name. From the Subsystem Menu select External Lines Route and then click the Add button. Figure 23 Subsystem Menu Add New Route For type of signaling, select IP Public, SIP from the drop down and click the Next button. The following Route Configuration screen will be displayed. September 2014 CONFIDENTIAL Page 24 of 51

25 Figure 24 Subsystem Menu Add New Route Step 2 Type in a route name and select a route number from the drop down menu and hit Next. There is no need to click the Advanced button as the defaults are being accepted. Hit Next. September 2014 CONFIDENTIAL Page 25 of 51

26 Figure 25 Subsystem Menu Add New Route Step 3 For Outgoing Traffic, select udp protocol, enter the Accelerator IP into the Proxy Address field. In the Invite URI String for Unknown Public Number, enter the MX-One IP into fields. In the From URI String for Unknown Public Number, enter the Accelerator IP address. All other fields are left at their default value. September 2014 CONFIDENTIAL Page 26 of 51

27 Figure 26 Route Configuration Step 3 cont. The last fields of Part 3 are shown for information. These can be left at their default values. Figure 27 Route Configuration Step 4 Enter server number as required. In the example 1 is used. September 2014 CONFIDENTIAL Page 27 of 51

28 Figure 28 Route Configuration Step 5 All defaults are accepted on Step 5 / 7 Figure 29 Route Configuration Step 6 Accept defaults September 2014 CONFIDENTIAL Page 28 of 51

29 Figure 30 Route Configuration Step 7 Name Identity is not necessary. Leave blank and hit Apply to complete. Figure 31 Route Configuration Complete September 2014 CONFIDENTIAL Page 29 of 51

30 Create a Route Pattern for PSTN This section applies to those Accelerator configurations with PSTN enabled. To configure a new Number Series, select System Subsystem Subsystem Name. From the Subsystem Menu select External Lines Destination and then click the Add button. Figure 32 Destination Menu Step 1 For Type of Destination select Destination and hit Next Figure 33 Destination Menu Step 2 Beside the Destination field hit Edit. September 2014 CONFIDENTIAL Page 30 of 51

31 Figure 34 Destination Menu Add New Number Series Select Add. Figure 35 Destination Menu Add New Number Series Step 1 Select the Number Series Type: External numbers, then hit Next. September 2014 CONFIDENTIAL Page 31 of 51

32 Figure 36 Destination Menu Add New Number Series Step 1 In our example, we are using 9 to dial the PSTN. So enter 9 in the External Destination field then hit apply. Figure 37 Destination Menu Add New Number Series Complete September 2014 CONFIDENTIAL Page 32 of 51

33 Hit Done Figure 38 Destination Menu After returning to the Number Series menu, hit Back Figure 39 Destination Menu You are back to the Destination Menu Step 2. Select the Destination just created and then the Route Name created when adding the trunk, then hit next. September 2014 CONFIDENTIAL Page 33 of 51

34 Figure 40 Destination Menu Step 3 Leave all fields to their defaults and hit Apply. Figure 41 Destination Menu Add - Result SIP Line Configuration This section pertains to those Accelerators with Mobile UC enabled. The Accelerator must be added as a third party SIP device to each MX-One subscriber that subscribes to the service. This section assumes that subscribers and their primary desk phones have already been provisioned. See Aastra documentation for more details on provisioning users and their desk phones. September 2014 CONFIDENTIAL Page 34 of 51

35 To configure new third party SIP phones (to enable call delivery from/to the mobile), select Services Extension. Click the Add button. Figure 42 Extension Menu Figure 43 Extension Menu Add Step 1 Select the Telephony System and IP for the Extension Type. Click the Next button. September 2014 CONFIDENTIAL Page 35 of 51

36 Figure 44 Extension Menu Add Step 2 Complete the following: Extension Number Range A new Extension Number Range may need to be set. See Aastra documentation and guidelines. Extension Number The first available automatically populates. Select that one or use the drop down to select the one desired. September 2014 CONFIDENTIAL Page 36 of 51

37 Domain Name DEFAULT was selected here. Refer to Aastra guidelines if another domain name is necessary. Common Service Profile Select per corporate guidelines for dial plan. All remain fields can be left at default. Select Apply. Figure 45 Extension Menu Add Result Once the User is created, you can associate this with an Enterprise Directory Number via parallel ringing. This number may have been created previously and assigned to an Enterprise Phone or Soft Client. This is illustrated below. September 2014 CONFIDENTIAL Page 37 of 51

38 Figure 46 SIP Device Configuration DN Assignment Select Services Extension. In the Enter Extension Number(s) field, enter the Enterprise Directory Number and select View. Figure 47 Directory Number Assignment Select the pencil icon to modify. September 2014 CONFIDENTIAL Page 38 of 51

39 Figure 48 Directory Number Assignment Extension Change Select Advanced September 2014 CONFIDENTIAL Page 39 of 51

40 Figure 49 DN Assignment Extension Change Advanced In the Parallel Ringing Secondary Directory Number 1 field, enter the SIP device number created previously and hit Apply. In our example, it is September 2014 CONFIDENTIAL Page 40 of 51

41 Figure 50 DN Assignment Extension Change Result CSTA Configuration This section applies to those Accelerator configurations with Mobile UC enabled. To support the Call Move feature, CSTA must be configured on the Aastra MX- One PBX. This is still currently under development. September 2014 CONFIDENTIAL Page 41 of 51

42 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 and/or a PSTN Access enabled Accelerator. The steps below describe the unique configuration areas needed to integrate the Aastra MX-One PBX with the Accelerator. 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 Aastra PBX. Refer to the Accelerator Provisioning Guide, Voice Networks, PBXs, Add Trunk Dial Plan section. 2. Add PBX (required) Refer to the Accelerator Provisioning Guide, Voice Networks, PBXs, Add New PBX section. o Add Trunk Group/Trunk (required) Host Address and Port corresponds to the IP address or DNS resolvable host name of the Aastra MX-One PBX with a port value of If you have PSTN access only, then the Trunk Group port number should be defined with the port used in the PSTN Access. Trunk Group Request URI parameters are not used by the Aastra PBX and therefore do not need to be provisioned. Additional trunks may be added to the Trunk Group. o Add Line Groups/Line (required) - Host Address corresponds to the IP address or DNS resolvable host name of the Aastra MX-One PBX. Port must match the SIP Phone Port value configured in the Aastra PBX on the System Aastra MX-One screen (generally 5060). Line Group Request URI parameters are not used by the Aastra PBX and therefore do not need to be provisioned. Refer to the Accelerator Provisioning Guide, Voice Networks, PBXs (Add/Modify), Add Line Groups/Line section. September 2014 CONFIDENTIAL Page 42 of 51

43 PSTN Access Enabled Accelerator If your configuration is Mobile UC only, refer to section Mobile UC Enabled Accelerator on page 42. This section is for those Accelerators that have only PSTN Access enabled. If your configuration is Mobile UC only or a combo of Mobile UC/PSTN Access, refer to section PSTN Access Enabled Accelerator starting on page 42. The steps below describe the unique configuration areas needed to integrate the Aastra MX-One with the Accelerator. Refer to the Accelerator Provisioning Guide for a comprehensive explanation of Accelerator provisioning. Voice Network: PBX 1. Add Trunk Dial Plan (required) There are no unique configuration items for Trunk Dial Plans and the Aastra 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. o o Add Trunk Groups/Trunk (required) Host Address and port corresponds to the IP address or DNS resolvable host name of the Aastra MX-One PBX. Trunk Group Request URI parameters are not used by the Aastra PBX and therefore do not need to be provisioned. Additional trunks may be added to the Trunk Group. Refer to the Accelerator Provisioning Guide, Voice Networks, PBXs (Add/Modify), Add Trunk Groups/Trunk section. Add Least Cost Routing (optional). No unique configuration items for Least Cost Routing. Refer to the Accelerator Provisioning Guide, Voice Networks, Least Cost Routes, Add Least Cost Routes section. 2. 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 43 to verify your configuration. Useful Commands Link Status between MX-One and Accelerator There is no status indicator on the MX-One to show the link state of the Trunks to the Accelerator. September 2014 CONFIDENTIAL Page 43 of 51

44 Link Status between Accelerator and MX-One Launch the Accelerator Management Console and navigate to the Session Conductor element 1. 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. Figure 51: Accelerator Management Console, Alarm Viewer 1 Refer to the Tango Management Console Reference Guide, Management Console Login section. Also reference the Accelerator Alarms and OMs Guide. September 2014 CONFIDENTIAL Page 44 of 51

45 Mobile UC Feature Interactions The intent of the Accelerator is to seamlessly extend existing PBX voice features to mobile. The Accelerator system is integrated with PBXs at three levels of Mobile UC integration. The Aastra MX-One PBX is integrated at Level 2 (see below). Accelerator PBX Level 1 Integration Integration Level 1 provides the subscriber basic services that are commonly used. The following features are considered Level 1: Abbreviated Dialing - Allows extension dialing or internal dialing from the desktop phone. Accelerator allows the user to dial these same abbreviated numbers from the mobile phone. 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 supports this capability in concert with the wireless network. September 2014 CONFIDENTIAL Page 45 of 51

46 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. Call Transfer Lets users move a currently established call from their mobile phone to another destination. This is implemented by the user entering a mid-call feature code followed by the transfer to number. There are two types of call transfers that are supported by this functionality: o o Blind Call Transfer Call is transferred without interaction between the user who initiated the transfer and the transfer destination. 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 supports enterprise Direct Inward Dialing. Direct Outward Dialing - Allows users inside an enterprise to dial directly to an external number. The Accelerator 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. September 2014 CONFIDENTIAL Page 46 of 51

47 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. Single Number Services - A single phone number that a subscriber publishes to communicate with others. When this single number is dialed, the subscriber s enterprise desktop phone as well as mobile phone will 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. Table 1 Accelerator PBX Level 1 Integration Feature Support Comments Abbreviated Dialing Ad Hoc Conferencing (Internal to PBX) Ad Hoc Conferencing (External to PBX) Call Forward All (Desk) Call Forward All Activation from Mobile Call Forward Busy (Desk) Call Forward Busy Activation from Mobile Call Forward No Answer (Desk) Call Forward No Answer Activation from Mobile Call Hold and Retrieve (Mobile) Call Line Identification (CLID) Call Transfer Blind Call Transfer Consultative Call Waiting and Retrieve Direct Inward Dialing Direct Outward Dialing Directory Dial Flexible Dialing Support Intelligent Call Delivery Least Cost Routing Meet-Me Conference Multiple Calls per Line PBX Do Not Disturb (Desk) PBX Do Not Disturb (Mobile) Single Number Services Voice Mail Message Waiting Indication No Uses an external IP Media 2000 conference server. Refer to the Accelerator Provisioning Guide, Voice Networks, Conference Servers section. September 2014 CONFIDENTIAL Page 47 of 51

48 Accelerator PBX Level 2 Integration Integration Level 2 provides the subscriber more advanced features than more commonly used basic features. 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. Call Push (Mobile->Desk Call Move)- Allows a subscriber to move a phone call between the desk phone and the mobile phone. Feature is be 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. Table 2 Accelerator PBX Level 2 Integration Feature Support Comments Call Accounting Codes No Call Coverage/Hunt Groups Call Line Identification Restriction (CLIR) (Mobile) Call Pull (Desk->Mobile Call Move) Call Push (Mobile->Desk Call Move) Class of Restriction (COR) (PBX) Class of Service (COS) (PBX) September 2014 CONFIDENTIAL Page 48 of 51

49 Accelerator PBX Level 3 Integration Integration Level 3 provides features that are specific to the PBX or specific to vertical markets. Manager/Assistant Services Provides the ability for an assistant to help manage and screen inbound calls for the manager Table 3 Accelerator PBX Level 3 Integration Feature Support Comments Manager/Assistant Services September 2014 CONFIDENTIAL Page 49 of 51

50 Acronyms Table 4 TERM Mobilizer Accelerator CA CDR CFA CFB CFNA CLI CLID CLIR COR COS CTI DID DN DTMF IPDR MWI NAT PBX PDN PSTN SIM Ring SIP SMDI SOAP TDM TLDN TLS Acronyms DEFINITION Tango Carrier Solution Tango Enterprise Solution Certificate Authority Call Detail Record Call Forward All Calls Call Forward Busy Call Forward Not Answered Command Line Interface Calling Line Identification Calling Line Identification Restriction Class of Restriction Class of Service Computer Telephony Integration Direct Inward Dial Directory Number Dual-Tone Multi-Frequency Internet Protocol Data Record Message Waiting Indication Network Address Translation Private Branch Exchange Pilot Directory Number Public Switched Telephone Network Simultaneous Ring Session Initiation Protocol Simplified Message Desk Interface Simple Object Access Protocol Time Division Multiplex Temporary Location Directory Number Transport Layer Security September 2014 CONFIDENTIAL Page 50 of 51

51 Tango Networks, Inc Parkwood Blvd, Suite 500 Frisco, Texas USA phone: fax: