ACCELERATOR 8.0 SIP TRUNK PBX INTEGRATION GUIDE April 2017 Tango Networks, Inc. phone: +1 469-920-2100 2801 Network Blvd, Suite 200 fax: +1 469-920-2099 Frisco, TX 75034 USA www.tango-networks.com
2004-2017 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 and Abrazo are trademarks of Tango Networks, Inc. All other trademarks used herein are the property of their respective owners and are used for identification purposes only. 2004-2017 Tango Networks, Inc. Tango Networks, Abrazo and E=fmc2 are trademarks 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. April 2017 CONFIDENTIAL Page 2 of 13
TABLE OF CONTENTS INTRODUCTION... 4 PBX DEPENDENCIES... 4 License Key... 4 Simultaneous Ringing (SIMRING)... 4 SIP TRUNK PBX PROVISIONING... 5 CONFIGURATION OF SIMRING FEATURE... 5 TRANSLATIONS PROVISIONING... 5 ACCELERATOR PROVISIONING... 6 Voice Network: PBX... 6 Voice Network: Voice Mail... 6 Subscriber... 6 FEATURE INTERACTIONS... 7 ACCELERATOR PBX LEVEL 1 INTEGRATION... 7 ACCELERATOR PBX LEVEL 2 INTEGRATION...10 ACCELERATOR PBX LEVEL 3 INTEGRATION...11 APPENDIX A: MULTIPLE CALL APPEARANCE FOR NORTEL DMS-100 PBX... 12 April 2017 CONFIDENTIAL Page 3 of 13
Introduction The Accelerator extends enterprise PBX functionality to mobile devices allowing end users to be more productive and accessible when out of the office. The Accelerator integrates mobile devices with existing Private Branch Exchanges (PBXs) so that the PBX sees the mobile device as simply another desk phone. This allows the existing PBX feature set to be applied consistently across both devices. Mobile specific functionality is then layered on top. PBX Dependencies License Key To use the Accelerator with a SIP Trunk PBX, the following software licenses may be required on the PBX: SIP Trunk licenses equal to the number of maximum active calls to/from an Accelerator mobile One SIMRING license per Accelerator subscriber who wishes to use both their desk phone (or soft client) and their Accelerator mobile Simultaneous Ringing (SIMRING) If the Accelerator mobile is to be used in conjunction with a desk phone (or soft client), the SIP Trunk PBX must support a SIMRING feature that allows an incoming call to ring one or more devices simultaneously. April 2017 CONFIDENTIAL Page 4 of 13
SIP Trunk PBX Provisioning This section describes the provisioning steps required on the PBX. Configuration of SIMRING feature The SIMRING feature allows an incoming call to ring two or more end user devices simultaneously. In order to include the Accelerator mobile in an end user s ringlist, the SIMRING feature must be configured to route to an alias Directory Number (DN) in addition to the user s existing devices/dns. The alias DN is then routed to the Accelerator by the PBX (see the Translations Provisioning section below). See your PBX documentation for specific information on provisioning this functionality within the PBX. Translations Provisioning Pilot Directory Numbers (PDNs) need to be allocated in order to route calls into the enterprise for handling by Accelerator (refer to the Accelerator Provisioning Guide for more details on PDNs). Translations need to be set up within the PBX to route these inbound calls over the SIP trunk that is connected to the Accelerator. Alias numbers may also need to be set up to support the simultaneous ringing capability of the desk phone. These alias numbers should be set up to route over the same SIP trunk to the Accelerator. April 2017 CONFIDENTIAL Page 5 of 13
Accelerator Provisioning te: This document assumes that the Accelerator has already been provisioned with: - Enterprise information - Wireless carrier information The integration process includes the following steps: 1. Define a Trunk Dial Plan for the SIP Trunk PBX in the Accelerator (optional). 2. Define the SIP Trunk PBX in the Accelerator. 3. Define a SIP Trunk Group/Trunk to route traffic from the SIP Trunk PBX to the Accelerator. 4. Define Pilot Numbers (optional but recommended) - PSTN routable number(s) that represent the mobile route into the enterprise network. The enterprise network must be provisioned to route calls for each pilot number to the Accelerator. 5. Define the Call Service Pilot Numbers - Used for the Call Move service. 6. Define Least Cost Route information for SIP trunk traffic from the Accelerator to the SIP Trunk PBX. (optional). 7. Define the Voice Mail system used with the SIP Trunk PBX. 8. Define Subscriber Dial Plans in the Accelerator. 9. Define Accelerator subscribers that use the SIP Trunk PBX. The steps below describe the unique configuration areas needed to integrate the SIP Trunk with the Accelerator. Refer to the Accelerator Provisioning Guide for a comprehensive explanation of Accelerator provisioning. Voice Network: PBX unique configuration items are required for adding a PBX. Refer to the Accelerator Provisioning Guide, Voice Networks, PBXs, Add New PBX section. Voice Network: Voice Mail unique configuration items are required for adding a VM Server. Refer to the Accelerator Provisioning Guide, Voice Networks, Voice Mail, Add New Voice Mail section. Subscriber unique configuration items for adding Subscribers. Refer to the Accelerator Provisioning Guide, Subscribers section. April 2017 CONFIDENTIAL Page 6 of 13
Feature Interactions This section explains the PBX features that have been integrated with this Accelerator release. Accelerator PBX Level 1 Integration Table 1 Accelerator PBX Level 1 Integration Feature Support Comments Abbreviated Dialing Ad Hoc Conferencing (Internal to PBX) Ad Hoc Conferencing (External to PBX) Uses an external IP Media 2000 conference server. Refer to the Accelerator Provisioning Guide, Voice Networks, Conference Servers section. Call Forward All (Desk) Call Forward All Activation from Mobile Call Forward Busy (Desk) Call Forward Busy Activation from Mobile Call Forward Answer (Desk) Call Forward 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 t Disturb (Desk) PBX Do t Disturb (Mobile) Single Number Services Voice Mail Message Waiting Indication 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. The 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. April 2017 CONFIDENTIAL Page 7 of 13
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 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 Answer capability with a Call Forward Answer feature button from their desk phone Call Forward 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 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. Call Line Identification (CLID) Provides the user information about the calling party. The Accelerator calling line identification when it is the called party. The 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. The Accelerator 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. April 2017 CONFIDENTIAL Page 8 of 13
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. The Accelerator using a personal directory on the phone and handles the translations of those digits into on-net network numbers if appropriate. In addition, the 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. The Accelerator 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 t Disturb (Desk) Allows users to activate or deactivate the Do t Disturb capability by pressing a button or a softkey from their desk phone. When active, Do t Disturb will not ring the mobile or desk phone. PBX Do t Disturb (Mobile) - Allows users to activate or deactivate the Do t Disturb capability by entering a feature access code from their mobile phone. When active, Do t 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. The Accelerator supplying a Message Waiting indication on the mobile phone that indicates that there are voice mail messages in the enterprise voice mail system. April 2017 CONFIDENTIAL Page 9 of 13
Accelerator PBX Level 2 Integration Table 2 Accelerator PBX Level 2 Integration Feature Support Comments Call Accounting Codes 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) 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. The Accelerator 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 COR for mobile originated calls. Class of Service (COS) (PBX) - Allows or denies user access to some system features. The Accelerator COS for mobile originated calls over SIP lines. April 2017 CONFIDENTIAL Page 10 of 13
Accelerator PBX Level 3 Integration Integration Level 3 provides features that are specific to the PBX or specific to vertical markets. The Accelerator does not support any Level 3 integration with the SIP Trunk PBX. April 2017 CONFIDENTIAL Page 11 of 13
Appendix A: Multiple Call Appearance for rtel DMS-100 PBX For a rtel DMS-100 PBX, the desk phones can be configured with Multiple Appearance Directory Number (MADN). The MADN allows each DN to have more than one line. Currently on some older loads of the DMS-100, desks with MADN Multiple Call Appearance (MCA) cannot be datafilled with Simring. We recommend the use of Key Short Hunting (KSH), which is compatible with Simring, and would act as if the desk has two lines for the one DN. The following steps should be taken to convert from MCA to KSH with Simring: 1. Remove MCA from the DN. 2. Assign a new fake DN to the 2 nd line of the desk phone. 3. Add Simring to the first line. 4. Use KSH for both lines. 5. Remove CFB and CFD voicemail re-direct from the first line. 6. KSH Default should route to a voicemail number, in the event that both lines are busy. 7. Add CFD voicemail re-direct to the 1 st and 2 nd line. 8. Add Number Replacement on the 2 nd line to represent the 1 st DN. This would allow the voicemail system to recognize the correct voice mailbox. The only restriction on using the above method is that if the first line is busy, Simring does not activate. This results in the 2 nd desk line ringing, but the mobile would not. April 2017 CONFIDENTIAL Page 12 of 13
Tango Networks, Inc. 2801 Network Blvd, Suite 200 Frisco, TX 75034 USA phone: +1 469-920-2100 fax: +1 469-920-2099 www.tango-networks.com