ACCELERATOR 6.3 ASTERISK 1.4 INTEGRATION GUIDE

ACCELERATOR 6.3

ASTERISK 1.4 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 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 - 2014 Tango Networks, Inc.

Tango Networks, Abrazo and E=fmc2 are trademarks or registered trademarks of Tango

TABLE OF CONTENTS

INTRODUCTION ... 4

SUPPORTED VERSIONS ... 5

INTERCONNECTION VIA SIPTRUNKS ... 5

ACCELERATOR INTEGRATION PROCESSES ... 6

MOBILE UCENABLED ACCELERATOR ... 6

Adding a SIP Trunk ... 8

Adding an Asterisk User ...10

Adding a SIP Device ...11

Outbound Routes Configuration ...13

Pilot DN Configuration ...14

PSTNACCESS ENABLED ACCELERATOR ...19

ACCELERATOR PROVISIONING ...20

Mobile UC Enabled Accelerator ...20

Voice Network: PBX/Trunk Dial Plan...20

Voice Network: Extension Ranges ...21

Voice Network: Carrier Gateways ...21

Voice Network: Voice Mail ...21

Subscriber Dial Plan/Subscriber ...21

PSTN Access Enabled Accelerator ...22

Voice Network: PBX ...22

Voice Network: Extension Ranges ...22

MOBILE UC FEATURE INTERACTIONS ... 23

ACCELERATOR PBXLEVEL 1INTEGRATION ...23

ACCELERATOR PBXLEVEL 2INTEGRATION ...26

ACCELERATOR PBXLEVEL 3INTEGRATION ...26

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 Asterisk 1.4/1.6 PBX with Tango depends on how your Carrier(s) is configured on the Accelerator.

 Mobile UC - The Mobile UC application extends PBX and Unified

Communications (UC) features to mobile devices. Examples include Single Number, Single Voicemail, Abbreviated Dialing, and Presence Status. For Mobile UC, SIP trunks are used when Tango must terminate a call via the Public Switched Telephone Network (PSTN).

 PSTN Access (e.g. SIP Trunking Controller) – 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, Tango uses only SIP trunk(s) to integrate with the Asterisk 1.4/1.6.

Important Note: Through out this document and other Tango

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.

 Mobile UC and SIP Trunking combination – It is possible to have both the Mobile UC functionality as well as the PSTN Access functionality

Supported Versions

This document addresses the way that Tango integrates with the Asterisk 1.4 and 1.6 PBX. It is intended for users with a thorough understanding of the Asterisk 1.4 and 1.6 PBX.

Note: This guide is meant to familiarize the reader with the minimum provisioning steps required on the Asterisk PBX for Tango integration. It does not attempt to address all possible configurations options or

features that can be applied within the PBX. Please consult your Asterisk documentation for Asterisk 1.4/1.6 specific issues.

Interconnection via SIP Trunks

Tango interacts with the Asterisk Trixbox PBX via SIP and a gateway in order to reach the PSTN. In a Tango Accelerator deployment, a SIP to PRI gateway is recommended. Alternatively, a PRI card can be used within the Asterisk Trixbox.

Accelerator Integration Processes

The integration with the Accelerator can be setup in several ways. During 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 Asterisk 1.4/1.6 PBX with the Accelerator.

Mobile UC Enabled Accelerator

The Accelerator needs to be configured as a SIP trunk as described below. Once this is completed, the off-PBX extensions can be used for simultaneous ringing. The SIP trunk interface(s) are used by Tango to terminate a call to the wireless operator’s network. A SIP trunk is also used by the PBX to route mobile calls to Tango via the enterprise using Pilot Directory Numbers, Service Pool Numbers or TLDNs.

After ensuring that the Trixbox server(s) are configured appropriately with domain and host information, use the following steps to establish a SIP connection between Tango and the Asterisk Trixbox.

1. Access the Trixbox administration web interface by using the URL http://address/maint in an Internet browser window, where ip-address is the IP ip-address of the Trixbox server. Log in with the appropriate credentials. The first screen of the interface is displayed.

2. Select switch to switch to administrator mode and login. The following screen is displayed.

Figure 2 Initial Asterisk Status Screen

3. Once logged in to the Asterisk Provisioning page, from the PBX pull down menu, select PBX Settings.

4. The Asterisk PBX Settings page will be displayed.

Figure 4 PBX Settings Screen

Adding a SIP Trunk

1. Select Trunks to Add a Trunk. The following page will be displayed.

2. Select Add SIP Trunk to add the Accelerator information. Sample Accelerator provisioning information is provided below. Submit Changes.

Adding an Asterisk User

1. Select Users to add an Accelerator enabled Asterisk user. Enter Tango Asterisk Subscriber information and click Submit.

Adding a SIP Device

1. From the PBX Setup menu, select Devices.

Figure 8 Select Devices

2. The Add Device screen will be displayed. From the Device pull down menu, select Generic SIP Device. Click on Submit.

Figure 9 Select Generic SIP Device

3. The Add SIP Device screen will be displayed. Enter the Device ID, the Description, and select the Default User for the device. Click on Submit.

4. Modify the SIP Device by selecting it from the Device list. The following screen will be shown.

Figure 11 Select SIP Device

5. The modify device screen will be displayed. The field dtmfmode must be rfc2833. The type field must be peer. The dial field must have the device extension number (e.g. 9090) and the alias that was provisioned for Tango user within the Accelerator Provisioning (e.g.

4449090@CorpAE). Click Submit to add the changes to the database.

Outbound Routes Configuration

1. Navigate to the Outbound Routes screen by selecting it from the left pane. The Add Route screen is displayed.

Figure 13 Basic Setup Menu – Outbound Routes 2. On the Add Route screen, type in the Route Name (e.g.

AliasRoutetoE). On the Dial Patterns field, type the alias range for the enterprise (e.g. 44493XX, where XX is a wildcard). The value(s) in the Dial Patterns field should reflect the Accelerator subscriber Alias field value(s). A separate entry should exist for each Accelerator subscriber alias range.

3. On the Trunk Sequence pull down menu, select the SIP Trunk defined for the Accelerator (e.g. SIP/CorpAE). Click Submit to add the route to the database.

Pilot DN Configuration

The Pilot DN for the Accelerator must be configured in order to have services available to Tango subscribers. The following steps define the provisioning necessary in the Asterisk Trixbox 1.4 PBX.

1. On the left pane, select Tools. From the Tools menu, select Custom Destinations.

Figure 15 Tools Menu – Custom Destinations

2. Add a Custom Destination for the Accelerator Server. Enter the Custom Destination (custom-redirtocorpe as described with the sample PDN of 9725551234), a Description and any applicable Notes. Click Submit Changes.

3. From the PBX pull-down menu, select Config File Editor.

Figure 17 PBX Pull-down Menu – Config File Editor

4. From the list of configurations, select the extensions_custom.conf file.

5. Enter the definition of the Custom Destination defined earlier as described in the following screen (e.g. [custom-redirtocorpe] and exten => 9725551234,1,Dial(SIP/${EXTEN}@CorpAE,40)). Click on Update to submit the changes.

Figure 19 Edit Extensions Configuration File

6. On the extensions_custom.conf menu, select Re-Read Configs to apply the changes to the Asterisk PBX.

7. Return to the PBX Settings as described inFigure 3 Select PBX Settings on page 7.

8. Under the Setup Menu on the left pane, select Inbound Routes.

Figure 21 Setup Menu – Inbound Routes

9. Add an Incoming Route which will define the PDN to be associated with the appropriate Accelerator as shown below.

Fields that need to be configured include:

– DID Number – The PDN for the Accelerator.

– Custom Destinations – The destination defined for the Accelerator.

PSTN Access Enabled Accelerator

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 steps below describe the unique configuration areas needed to integrate the Asterisk 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 Asterisk 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) – One item to note when provisioning Trunk Groups/Trunks in the Accelerator. Trunk Group

Request URI parameters are not used by the Asterisk 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 Least Cost Routing (optional) in the Accelerator for the Asterisk PBX. No unique configuration items for Least Cost Routing. Refer to the

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.



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 Asterisk 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.



section.

Voice Network: Voice Mail

5. Add Voice Mail for the Asterisk PBX in the Accelerator. 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/Subscriber

6. Add Subscriber Dial Plan. No unique configuration items for adding Subscriber Dial Plans. Refer to the Accelerator Provisioning Guide, Subscribers, Add Subscriber Dial Plan section.

7. Add Subscribers. One item to note when provisioning subscribers: o Alias – This will be associated to the user’s SIP device on the Asterisk

Trixbox provisioning interface. See Adding a SIP Device.

If you have only Mobile UC enabled in your Accelerator license key then you are finished.

PSTN Access Enabled Accelerator

The steps below describe the unique configuration areas needed to integrate the Asterisk PBX with Tango. 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 Asterisk PBX. Refer to the Accelerator

Provisioning Guide, Voice Networks, PBXs, Add Trunk Dial Plan section. 8. 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 corresponds to the IP address or DNS resolvable host name of the Asterisk PBX.

o Port must match The SIP trunk port value on the Asterisk PBX. o Trunk Group Request URI parameters are not used by the Asterisk

PBX and therefore do not need to be provisioned.

o Refer to the Accelerator Provisioning Guide, Voice Networks, PBXs (Add/Modify), Add Trunk Groups/Trunk section.

 Add Least Cost Routing in the Accelerator for the Asterisk PBX

(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.

Voice Network: Extension Ranges

9. Add Extension Ranges (required) – No unique configuration items for adding an Extension Range. Refer to the Accelerator Provisioning Guide,

Mobile UC Feature Interactions

The intent of Tango is to seamlessly add a mobile component to all of the services that the Asterisk PBX provides to the end user. The Accelerator is integrated with PBXs at three levels of integration for Mobile UC. The Asterisk PBX is integrated at Level 2 integration. This section explains the PBX

features that have been integrated with this Accelerator release.

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 Hold and Retrieve (Mobile) – Lets users temporarily disconnect from a call, use the telephone for another call, and then return to the original call. Tango 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.

 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 Blind Call Transfer – Call is transferred without interaction between

the user who initiated the transfer and the transfer destination. 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. Tango supports enterprise Direct Inward Dialing.

 Direct Outward Dialing - Allows users inside an enterprise to dial directly to an external number. Tango 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.

 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.

 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 Yes Ad Hoc Conferencing (Internal to PBX) Yes 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

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 Yes Call Line Identification Restriction (CLIR) (Mobile) Yes Call Pull (Desk->Mobile Call Move) No Call Push (Mobile->Desk Call Move) Yes Class of Restriction (COR) (PBX) Yes Class of Service (COS) (PBX) Yes

Accelerator PBX Level 3 Integration

Acronyms

Table 3 Acronyms TERM DEFINITION Accelerator Tango Enterprise CA Certificate Authority CDR Call Detail Record CFA Call Forward All Calls CFB Call Forward Busy

CFNA Call Forward Not Answered CLI Command Line Interface CLID Calling Line Identification

CLIR Calling Line Identification Restriction COR Class of Restriction

COS Class of Service

CTI Computer Telephony Integration DID Direct Inward Dial

DN Directory Number

DTMF Dual-Tone Multi-Frequency IPDR Internet Protocol Data Record Mobilizer Tango Carrier

MWI Message Waiting Indication NAT Network Address Translation PBX Private Branch Exchange PDN Pilot Directory Number

PSTN Public Switched Telephone Network SIM Ring Simultaneous Ring

SIP Session Initiation Protocol

SMDI Simplified Message Desk Interface SOAP Simple Object Access Protocol TDM Time Division Multiplex