ACCELERATOR 6.3 TDM PBX INTEGRATION GUIDE

Transcription

1 ACCELERATOR 6.3 TDM PBX INTEGRATION GUIDE April 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 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 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 2014 CONFIDENTIAL Page 2 of 16

3 TABLE OF CONTENTS INTRODUCTION... 4 SUPPORTED VERSIONS... 4 SIP TO PRI CONVERSION... 4 SIMULTANEOUS RINGING (SIMRING)... 4 TDM PBX DEPENDENCIES... 4 License Key... 4 Trunking Interfaces... 4 TDM PBX INTEGRATION REQUIREMENTS... 5 INSTALLATION OF SIP/PRI GATEWAY... 5 TRANSLATIONS PROVISIONING... 5 CONFIGURATION OF SIMRING FEATURE... 5 ACCELERATOR PROVISIONING... 6 Voice Network : PBX/Trunk Dial Plan... 6 Voice Network : Extension Ranges... 7 Voice Network : Carrier Gateways... 7 Voice Network: Voice Mail... 8 Subscriber Dial Plan/Subscriber... 8 FEATURE INTERACTIONS... 9 ACCELERATOR PBX LEVEL 1 INTEGRATION... 9 ACCELERATOR PBX LEVEL 2 INTEGRATION...12 ACCELERATOR PBX LEVEL 3 INTEGRATION...13 APPENDIX A: MULTIPLE CALL APPEARANCE FOR NORTEL DMS-100 PBX ACRONYMS April 2014 CONFIDENTIAL Page 3 of 16

4 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. Supported Versions This document addresses the required configuration changes on TDM PBXs (PBXs that do not support SIP trunk or SIP line interfaces) to enable integrated operation with the Accelerator. SIP to PRI conversion The Accelerator uses the SIP protocol for call control of the calls made and received by Accelerator subscribers. A SIP/PRI gateway is therefore used to provide the necessary inter-working function for these releases. This requires the provisioning of PRI trunks on the TDM PBX along with translations and routing as described in section TDM PBX Integration Requirements. Simultaneous Ringing (SIMRING) If the Accelrator mobile is to be used in conjunction with a desk phone (or soft client), the TDM PBX must support a SIMRING feature that allows an incoming call to ring one or more devices simultaneously. TDM PBX Dependencies License Key To use the Accelerator with TDM PBXs, the following software licenses may be required on the PBX: One SIMRING license per Accelerator subscriber who wishes to use both their desk phone (or soft client) and their Accelerator mobile Trunking Interfaces To use the Accelerator with TDM PBXs, PRI trunks are required on the TDM PBX to interwork with the SIP/PRI gateway. April 2014 CONFIDENTIAL Page 4 of 16

5 TDM PBX Integration Requirements This section describes the requirements for the Accelerator to integrate with a TDM PBX. The following checklist itemizes the items required for integration: SIP/PRI Gateway (e.g. Audiocodes Mediant line of gateways) Available PRI trunk ports on TDM PBX SIMRING feature enabled on TDM PBX Provisioning of translations capability Pilot Numbers and Accelerator alias numbers Provisioning of PBX and subscribers on Accelerator Enterprise solution Installation of SIP/PRI gateway The SIP/PRI gateway needs to be installed in a location accessible by the PRI spans from the TDM PBX and by an Ethernet connection to a network segment routable to the Accelerator Enterprise servers. The PRI spans are connected between the TDM PBX trunk peripheral and the SIP/PRI gateway. Tango Networks has completed interoperability testing with Mediant AudioCodes 2000 gateway, net VX gateway, and AdTran gateway. Please check with Tango for additional gateway interop results. Translations Provisioning Pilot numbers need to be allocated to route calls into the enterprise for handling by Accelerator. Translations need to be set up to route these inbound calls to the pilot numbers over the trunk that is connected to the PRI gateway and then to the Accelerator. Alias numbers 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 trunk to the Accelerator. Configuration of SIMRING feature The SIMRING feature allows an incoming call to ring a group of directory numbers simultaneously. To support the Accelerator, the SIMRING feature is configured for each Accelerator subscriber s desk phone to enable simultaneous ringing of the user s desk phone and an Accelerator alias. April 2014 CONFIDENTIAL Page 5 of 16

6 Accelerator Provisioning Note: 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 TDM PBX in the Accelerator (required). 2. Define the TDM PBX in the Accelerator (required). Define a SIP Trunk Group/Trunk to route traffic from the TDM PBX to the Accelerator (required). 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. Define the Call Service Pilot Numbers (required if using the Call Move service)- Used for the Call Move service. Define Least Cost Route (optional) information for SIP trunk traffic from the Accelerator to the TDM PBX (optional). 3. Define the Enterprise Ranges used in the enterprise. 4. Define the Carrier Gateways (required if your enterprise routes calls between the wireless carrier and the Accelerator). 5. Define the Voice Mail system used with the TDM PBX (recommended). 6. Define Subscriber Dial Plans in the Accelerator (required). 7. Define Accelerator subscribers that use the TDM PBX (required). The steps below describe the unique configuration areas needed to integrate the TDM 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 TDM 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. Add Trunk Group/Trunk (required) o A SIP trunk is created to route traffic from the Accelerator to SIP PRI Gateway associated with the TDM PBX. Multiple trunks to different gateways may be created for scalability/redundancy reasons. The April 2014 CONFIDENTIAL Page 6 of 16

7 o o Accelerator will randomly select trunks in a trunk group on a per-call basis and will route advance among trunks in the trunk group if a trunk is unavailable. When provisioning Trunk Groups/Trunks in the Accelerator. Trunk Group Request URI parameters are not used by the TDM PBX and therefore do not need to be provisioned. Refer to the Accelerator Provisioning Guide, Voice Networks, PBXs (Add/Modify), Add Trunk Groups/Trunk section. Add Pilot Numbers (required if your enterprise intends to route Pilot DNs through the TDM PBX) - No unique configuration areas required for provisioning Pilot Numbers to the Accelerator. Refer to the Accelerator Provisioning Guide, Voice Networks, PBXs (Add/Modify) section. Add Call Service Pilot Number (required if using the Call Move Service). No unique configuration items for Call Service Pilot Numbers. Refer to the Accelerator Provisioning Guide, Voice Networks, PBXs (Add/Modify) section. Add Least Cost Routing (optional) in the Accelerator for the TDM PBX. No unique configuration items for Least Cost Routing. Refer to the Accelerator Provisioning Guide, Voice Networks, 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. If you are using Pilot numbers to route calls from the wireless carrier to the Accelerator using the Carrier Gateway, provision the Pilot Numbers on the Carrier Gateway s main page. Depending on your configuration, the Pilot numbers here may need to be E.164 routable. Add Trunk Groups/Trunk (required if using a Carrier Gateway) o o Host Address, Port and Transport Type should match the value of the 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 TDM 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 Routes section. April 2014 CONFIDENTIAL Page 7 of 16

8 Voice Network: Voice Mail 3. Add Voice Mail (recommended) for the TDM PBX in the Accelerator. Select either SIP or SMDI as the Voice Mail Server Type. Refer to the Accelerator Provisioning Guide, Voice Networks, Voice Mail Servers, Add Voice Mail Server section. Note: For Callpilot voic , select SMDI as Voice Mail Server Type. Subscriber Dial Plan/Subscriber 4. 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. 5. Add Subscribers (required) - No unique configuration items for adding Subscribers. Refer to the Accelerator Provisioning Guide, Subscribers, Add Subscriber section. April 2014 CONFIDENTIAL Page 8 of 16

9 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) No 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 No Call Forward Busy (Desk) Call Forward Busy Activation from Mobile No Call Forward No Answer (Desk) Call Forward No Answer Activation from Mobile No 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 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 2014 CONFIDENTIAL Page 9 of 16

10 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. Call Line Identification (CLID) Provides the user information about the calling party. The Accelerator supports 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 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. April 2014 CONFIDENTIAL Page 10 of 16

11 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 supports 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 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. 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 supports supplying a Message Waiting indication on the mobile phone that indicates that there are voice mail messages in the enterprise voice mail system. April 2014 CONFIDENTIAL Page 11 of 16

12 Accelerator PBX Level 2 Integration 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) No Call Push (Mobile->Desk Call Move) Class of Restriction (COR) (PBX) No Class of Service (COS) (PBX) No 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 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. April 2014 CONFIDENTIAL Page 12 of 16

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 TDM PBX. April 2014 CONFIDENTIAL Page 13 of 16

14 Appendix A: Multiple Call Appearance for Nortel DMS-100 PBX For a Nortel 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: 6. Remove MCA from the DN. 7. Assign a new fake DN to the 2 nd line of the desk phone. 8. Add Simring to the first line. 9. Use KSH for both lines. 10. Remove CFB and CFD voic re-direct from the first line. 11. KSH Default should route to a voic number, in the event that both lines are busy. 12. Add CFD voic re-direct to the 1 st and 2 nd line. 13. Add Number Replacement on the 2 nd line to represent the 1 st DN. This would allow the voic 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 2014 CONFIDENTIAL Page 14 of 16

15 Acronyms Table 3 Term Accelerator CA CDR CFA CFB CFNA CLI CLID CLIR COR COS CTI DID DN DTMF IPDR Mobilizer MWI NAT PBX PDN PSTN SIM Ring SIP SMDI SOAP TDM TLDN TLS Acronyms Definition Tango Enterprise 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 Tango Carrier 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 April 2014 CONFIDENTIAL Page 15 of 16

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