Accelerator Alcatel OmniPCX7.1 Integration Guide

ACCELERATOR 8.
4
ALCATEL OMNIPCX 7.1 INTEGRATION GUIDE
April 2018
Revision 8.4.0.0
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
Accelerator 8.4 Alcatel OmniPCX 7.1 Integration Guide
© 2004 - 2018 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 - 2018 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.
Revision 8.4.0.0 - April 2018 CONFIDENTIAL Page 2 of 38

TABLE OF CONTENTS
INTRODUCTION ............................................................................................. 4
SUPPORTED VERSIONS ......................................................................................................... 5
OMNIPCX PBX LICENSE REQUIREMENTS – MOBILE UC ................................................................... 5
ACCELERATOR INTEGRATION PROCESSES ........................................................ 6

MOBILE UC ENABLED ACCELERATOR ......................................................................................... 6
Main TG .............................................................................................................. 6
SIP Gateway ........................................................................................................ 6
SIP Proxy ............................................................................................................ 6
SIP External Gateway ........................................................................................... 7
Open Telephony Server ......................................................................................... 8
SIMRing .............................................................................................................. 9
SIMRING via Tandem Extensions & Ghost Extensions for Non-SIP Desk Phones .10
SIMRING via Remote Extension & Set Supervision for Non-SIP Desk Phones .....18
SIMRING for SIP Phones and SIP Soft Clients ................................................22
PBX Translations .................................................................................................22
Voice Mail Configuration .......................................................................................27
PSTN ACCESS ENABLED ACCELERATOR .....................................................................................27
ACCELERATOR PROVISIONING ................................................................................................28
Mobile UC Enabled Accelerator ..............................................................................28
Voice Network: Trunk Dial Plan ....................................................................28
Voice Network: PBX ...................................................................................28
Voice Network: Enterprise Ranges ...............................................................29
Voice Network: Carrier Gateways .................................................................29
Voice Network: Voice Mail ...........................................................................29
Subscriber Dial Plan/Subscribers ..................................................................30
PSTN Access Enabled Accelerator ..........................................................................30
Voice Network: Trunk Dial Plan ....................................................................30
Voice Network: PBX ...................................................................................30
ACCELERATOR INTEGRATION CHECKLIST – MOBILE UC.................................... 32

OMNIPCX SYSTEM LEVEL INTEGRATION ITEMS .............................................................................32
OMNIPCX INDIVIDUAL USER INTEGRATION ITEMS .........................................................................32
MOBILE UC FEATURE INTERACTIONS ............................................................. 33

ACCELERATOR PBX LEVEL 1 INTEGRATION .................................................................................33

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 OmniPCX PBX with the
Accelerator solution depends on how your Carrier(s) is configured on the
Accelerator.
• Mobile Unified Communications (Mobile UC) - The Mobile UC

application extends PBX and Unified Communications (UC) features to
mobile devices. Examples include Single Number, Single Voicemail, and
Abbreviated Dialing.
For Mobile UC, the Accelerator uses a combination of SIP lines and trunks
to integrate with the OmniPCX PBX.
o SIP Trunk Interfaces – Used when the PBX provides originating and
terminating services to calls from the Accelerator. For originations,
the Accelerator originates on behalf of the mobile. For terminations,
the Accelerator rings the desk on behalf of the mobile network.
o SIP Line Interfaces – Used to receive terminations from the PBX for
Accelerator Mobile UC subscribers. If a call comes into the OmniPCX
desk phone number, a SIP INVITE is sent over a SIP line interface to
the Accelerator to ring the mobile phone.
o CTI must be enabled for each subscriber that intends to use the Call
Move service.
• 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 OmniPCX 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 OmniPCX PBX desk phone to the PSTN. And, vice-versa; PSTN
originated calls to DIDs assigned to the OmniPCX PBX will be routed from
the carrier to the Accelerator PSTN Access service to the PBX.
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.

Supported Versions
This document addresses the way that Tango solution integrates with the
Alcatel-Lucent OmniPCX Enterprise Communication 7.1 solution. It is
intended for users with a thorough understanding of the OmniPCX.
Note: This guide is meant to familiarize the reader with the minimum
provisioning steps required on the OmniPCX 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
OmniPCX documentation for Alcatel-Lucent OmniPCX Enterprise
Communication 7.1 specific issues.
OmniPCX PBX License Requirements – Mobile UC
Table 1 OmniPCX Software Licenses – Mobile UC
SIP Trunk License Remote Extension Ghost User MyphoneAPI

1 per Accelerator
SIP 1 per Accelerator
Subscriber
Desk Subscriber for n/a n/a
(on SIP gateway of
Phones SimRing
OmniPCX)
1 per Accelerator
SIP
Subscriber
Soft n/a n/a n/a
(on SIP gateway of
Phones
OmniPCX)
1 per Accelerator
1 per Accelerator
Non- 1 per Accelerator 1 per non-SIP Subscriber for Call
Subscriber
SIP Subscriber for phone Tango Move (on XML
(on SIP gateway of
Phones SimRing Subscriber server of
OmniPCX)
OmniPCX)

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 Alcatel-Lucent OmniPCX Enterprise Communication 7.1 PBX with the
Accelerator.
Mobile UC Enabled Accelerator
Tango requires both SIP Line and SIP Trunk provisioning within the OmniPCX
PBX to provide full functionality. In addition, in order to enable the optional
Call Move feature within Tango, each subscriber must be CSTA-enabled on
the OmniPCX PBX.
Main TG
Tango utilizes existing PSTN interfaces on the PBX for connectivity between
the between the enterprise network and the wireless operator’s network.
Because of this, there must be at least one PSTN trunk group provisioned on
the OmniPCX.
This document assumes that PSTN trunk groups are already provisioned. For
more information, refer to Alcatel-Lucent OmniPCX documentation.
SIP Gateway
On the OmniPCX, the SIP gateway acts as an interface between the PCX
digital telephone sets and the SIP telephones. It allows SIP sets to access the
legacy network and services and allows legacy sets to contact SIP sets or
another network via a SIP external gateway.
This document assumes that the SIP Gateway is already provisioned for the
existing desk phones. For more information, refer to Alcatel-Lucent OmniPCX
documentation.
SIP Proxy
The SIP Proxy is used to configure the values of timers used in SIP exchanges
and enables digest authentication.

This document assumes that the SIP Proxy is already provisioned. For more
information, refer to Alcatel-Lucent OmniPCX documentation.
SIP External Gateway
A SIP external gateway represents a SIP user group that is accessible via a
remote gateway or proxy, like the Accelerator, and contains authentication
data which is used by the remote gateway or proxy. There must be a SIP
Trunk set up between the SIP External Gateway and the Accelerator to allow
signaling communication via SIP.
An example configuration of the SIP Trunk used between the Accelerator and
the SIP External Gateway is shown below with pertinent fields in bold.
Node Number (reserved) : 101

Instance (reserved) : 1
SIP External Gateway ID : 1
SIP Remote domain: (domain name of Accelerator)
SIP Port Number : 5060
SIP Transport Type + UDP
RFC3262 Forced use + False
Authentification domain : --------
Registration ID : --------
Registration Id in P_asserted + False
Registration timer : 0
SIP Outbound Proxy : --------
External proxy user part : --------
Supervision timer : 0
Trunk group number : 11
Pool Number : -1
Outgoing realm : --------
Outgoing username : --------
Outgoing Password : --------
Confirm : --------
Incoming username : --------
Incoming Password : --------
Confirm : --------
RFC 3325 supported by the distant + True
SDP IN 180 + True
Minimal authentication method + SIP None
Note: Ensure that the “minimal authentication method” is set to “None”

to define the Accelerator as a trusted endpoint.

Open Telephony Server
The Open Telephony Server is utilized to support Accelerator Call Move

service. This document assumes that the physical Open Telephony Server and
software is already provisioned on the OmniPCX PBX. For more information,
refer to Alcatel-Lucent OmniPCX documentation.
For a user to utilize the Accelerator Call Move service, the subscriber must
have Computer Supported Telecommunications Application (CSTA) enabled.
With CSTA enabled, Tango is able to utilize XML over SOAP for communication
with the OmniPCX to offer the Call Move service. Refer to the following
provisioning steps to enable CSTA.
Start a session on the GUI based Web Administration (WBA) management

tool. An example of the login screen is below.
Figure 1 OmniTouch Login Screen

1. After login, the following screen is displayed. Under the Provisioning

heading on the left menu bar, Click on Users.
Figure 2 OmniTouch Administrator Screen
2. Create a user account based upon their desk number. User information
includes:
– First and Last name of user
– Login name (this can be anything)
– Telephone number (this should be the user’s desk number)
3. Assign “Telephony Services” capabilities to the user
4. Repeat steps three and four for all users which can use the Accelerator
Call Move service.
SIMRing
There are three types of users that can be configured on the Alcatel PBX:
physical desk phones, soft clients and tandem extensions. Desk phones are
handsets that sit on the desk. Soft Clients are virtual clients running on a
personal computer. This document assumes that the user’s physical desk
phones and soft clients are already provisioned. For more information, refer
to Alcatel-Lucent OmniPCX documentation.
This section outlines the provisioning requirements to implement SIMRing for:
– Non-SIP Desk Phones

– SIP Phones and SIP Soft Clients
Provisioning is achieved via the supported management interfaces on the

OmniPCX. There are two ways that datafill may be provisioned to enable
simring for non-SIP desk phones. Each is valid and explained below.

SIMRING via Tandem Extensions & Ghost Extensions for Non-SIP Desk
Phones
The incremental licensing requirements for implementing simultaneous

ringing via tandem extensions and ghost extensions are:
– Remote Extension – one license required per Tango subscriber

– Ghost User – Quantity is an OmniPCX formula based upon the
percentage of simultaneous originations
A tandem extension enables the Alcatel Simultaneous ringing functionality for

desk phones. A tandem extension is basically a logical association between
two “sets”; one called the “main set” and the other called the “secondary set.”
Each tandem extension has a “remote extension” that forwards the tandem
extension to the proper network element. Tandem sets must be managed in
multi-line mode, which means that a dedicated digital set can have one ore
more call numbers and each call number can be associated with one or more
programmable keys. To achieve this, each extension should have a “program
key” entry for “1” set to Function=”Multi-Line”. One additional requirement
for tandem extension is the concept of the Ghost User, which essentially
defines an analogue set without physical hardware that is utilized by the PBX
to setup the tandem call.
To setup SimRing for the Accelerator using the Tandem Extension

functionality,
a. Create the tandem extension (i.e., the “secondary set”) for the
user
b. Create the multi-line program key for the tandem extension
c. Assign the tandem extension for the user (i.e., the “main set”)
d. Create the engineered number of ghost user(s)
e. Create the remote extension (to the Accelerator) for the tandem
extension.
For example, assume that desk set 2507000 needs to be set up with a
tandem extension of 2507100. The tandem extension (2507100) has a
remote extension set up to ring 91504507001, which is the Accelerator. The
following is example datafill with pertinent fields in bold text.
a. Create the tandem extension (2507100) for the user (2507000).

Directory Number : 2507100
Directory name : --------

Directory First Name : ------------------------
UTF-8 Directory Name : ------------------------
UTF-8 Directory First Name : ------------------------
Location Node : 1
Shelf Address : 255
Board Address : 255

Equipment Address : 255

Set Type + Remote extension
Entity Number : 1
Set Function + Default
Profile Name : --------
Key Profiles + None
Domain Identifier : 0
Secret Code : ****

Confirm : ****
Associated Set No. : 1000

Cost Center ID : 255
Cost Center Name : --------
Charging COS + Justified
Public Network COS : 2
External Forwarding COS : 255
Phone Features COS : 0
Connection COS : 0
Hunt Group Dir No. : --------
ACD Group Directory No. : --------
Pickup Group Name : --------
Reserved Time Slot + False
Voice Mail Dir.No. : 1000
Voice Mail Type + 4645
Paging Trunk Group : 255
Paging Beeper : ----
Tele-Marketing Agent + False
ISDN User
External + True
Internal + True
Display ext. calling number + True
ISDN Teleservice + Phone

Hotel-Set Operation + Administrative
Use Type Of Dir. No. + Normal
Number Of Set Users : 1
Multi-line station + YES
Dialed number masked + NO
Routing Table : 0
Associated Videophone + False
VIP (Very Important Pers.) + False
Assistant Directory Number : 2507100
Calls Priority : 0
PCBT Associated + NO
Urgent Call + NO
PIN (Personal Ident.No.)
PIN No. : --------

PIN With Secret Code + True
Type of control + By COS
PIN group number : 1
Can be Called/Dialed By Name + YES

Displayed Name : 2507000

Errors on Secret Code Counter : 0
ACD station + NO
Incidents Teleservice + NO
Voice Guide listening Class : 7
Caller COS : 4
VSI Transparency + False
Type of Keyboard + Default keyboard
Errors on Business Code Counter : 0
STAP + Off-hook
Use Personal Calling Number + False
Group PIN control + No group
CCA Operations + False
A4980 + No 4980
Z IVR + False
NOMADIC + False
TAPI premium server + NO
Conference group : -1
Announcement group : -1
Call Restriction COS : 0
Applicable Restriction COS : 0
Implicit Priority
Activation mode : 0
Priority Level : 0
Explicit Priority
Activation mode : 0
Priority Level : 0
Pre-emptable Primary Inc. Line + NO
Pre-emptable Secondary Inc. Line + NO
Priority Presentation + NO
Ith Service type + Not Valid
CUG List Number : -1
Preferential CUG : -1
CUG Outgoing Access + False
CUG Incoming Access + False
Automatic reconfiguration + CTQ Forbidden-ConnectionTO
Associated RSI : --------
4630 access without Code + False
Dial by name and text msg. + NO
Multi-Line Properties
Automatic Incoming Seizure + True

Automatic Outgoing Seizure + True
Selective Filtering + False
Overflow on no answer + False
Overflow on busy + False
Supervision at off-hook + True
Automatic Outgoing Seizure for MLA + False
Access Code to UUS messages + NO

Phone book Name (Dial by name) : ------------------------
Phone book First Name : ------------------------

Tandem
Tandem Directory Number : 2507000

Main set in the tandem + False
Partial busy + False
Ringing in partial busy + Long Ring
Specific supervision + False
URL UserName : ------------------------

URL Domain : ------------------------
b. Create the multi-line program key for the tandem extension

(2507001)
Key No. : 1
Function + Multi-line
Mnemo (Pocket,Mobile,4040,Alc8&9) : ----------
Direct/Prog(Alc.8 & 9) Key Number : 0
c. Assign the tandem extension (2507100) for the user (2507000)

Directory name : 2507000

Location Node : 1
Shelf Address : 255
Board Address : 255
Set Type + IPTouch 4068
Entity Number : 1
Key Profiles + Company
Language ID : 1
Secret Code : ****

Confirm : ****

Connection COS : 0


Voice Mail Dir.No. : 1000
Voice Mail Type + 4645
ISDN User
External + True
Internal + True
Routing Table : 0
Calls Priority : 0
Urgent Call + NO
PIN No. : --------


ACD station + NO
Caller COS : 4
STAP + Off-hook
A4980 + No 4980
Z IVR + False
NOMADIC + False

Implicit Priority
Activation mode : 0
Priority Level : 0
Explicit Priority
Activation mode : 0
Priority Level : 0
Ith Service type + NotValid
Add On Module 1 + None
Internal Alphanum.Keyboard + English
Called Associated DECT set : --------
Dial by name and text msg. + YES
Internal Alphanum.Keyboard + English
Dial by name and text msg. + YES

Overflow on no answer + True
Supervision at off-hook + False
Phone book Name (Dial by name) : 2507000
NS Right (Notification server) + NO
CSTA routing + False
Tandem
Tandem Directory Number : 2507100

Main set in the tandem + True
Ringing in partial busy + Long Ring

4645 Voice Mail Box
4645 Voice Mail Type + Standard

4645 Class of Service : 1
URL UserName : ------------------------
URL Domain : ------------------------
Advanced configuration + False
d. Set Ghost user extension (2507200)

Directory name : Ghost

Location Node : 1
Shelf Address : 255
Board Address : 255
Set Type + ANALOG
Entity Number : 1
Key Profiles + None
Language ID : 1
Secret Code : ****

Confirm : ****

Connection COS : 0
Voice Mail Dir.No. : --------
Voice Mail Type + No Voice Mail
ISDN User
External + True
Internal + True


Multi-line station + NO
Routing Table : 0
Calls Priority : 0
Urgent Call + NO
PIN No. : --------


Displayed Name : Ghost
ACD station + NO
Caller COS : 4
STAP + Off-hook
A4980 + No 4980
Z IVR + False
NOMADIC + False
Implicit Priority
Activation mode : 0
Priority Level : 0
Explicit Priority
Activation mode : 0
Priority Level : 0
Ith Service type + Not Valid


DATA Connection COS : 0
Message LED + False
Ext.Alarm Equipment + Alarm On Opened Loop
Phone book Name (Dial by name) : Ghost
Modem Trunk Group Info
Trunk Group ID : 255

Trunk Number : 255
Ghost Z + True
Ghost Z Feature + Remote extension
VAD use for Ghost Z + False
CSTA routing + False
CMF 4600 (DTMF frequencies) + False
URL UserName : ------------------------
URL Domain : ------------------------
CLIP + False
Compatible. CLIP display + ASCII
Analog type + No specific management
e. Create the remote extension to the Accelerator for the tandem

extension (2507100).
Remote extension number : 91504507001
SIMRING via Remote Extension & Set Supervision for Non-SIP Desk
Phones
The incremental licensing requirements for implementing simring via remote

extensions and set supervision are:
– Remote Extension – one license required per Tango subscriber
To setup SimRing for the Accelerator using the Set Supervision functionality,
a. Create the remote extension for the user

b. Create the multi-line program key for the remote extension
c. Create the set supervision program key for the remote extension
d. Associate the remote extension to the Accelerator

For example, assume that desk set 2509900 needs to be set up with a remote
extension (1509900) to ring the Accelerator at 91504509900. The following is
example datafill with pertinent fields bolded.
a. Create the remote extension (1509900)

Directory name : 1509900

Location Node : 1
Shelf Address : 255
Board Address : 255
Set Type + Remote Extension
Entity Number : 1
Key Profiles + None
Language ID : 1
Secret Code : ****

Confirm : ****

Connection COS : 0
Voice Mail Dir.No. :
Voice Mail Type + No Voice Mail
ISDN User
External + True
Internal + True



Routing Table : 0
Calls Priority : 0
Urgent Call + NO
PIN No. : --------


ACD station + NO
Caller COS : 4
STAP + Off-hook
A4980 + No 4980
Z IVR + False
NOMADIC + False
Implicit Priority
Activation mode : 0
Priority Level : 0
Explicit Priority
Activation mode : 0
Priority Level : 0
Ith Service type + NotValid


Dial by name and text msg. + NO

Overflow on no answer + False
Supervision at off-hook + True
Phone book Name (Dial by name) : ------------------------
Tandem
Tandem Directory Number : -------

Main set in the tandem + False
Ringing in partial busy + Short Ring
URL UserName : ------------------------

URL Domain : ------------------------
b. Create the multi-line program key (key #1) for the remote
extension (1509900)
Key No. : 1
Function + Multi-line
Mnemo <Pocket, Mobile, 4040, Alc8&9> : -----
Direct/Prog(Alc.8&9) Key Number : 0
c. Create the set supervisor key (Key #2) for the remote extension
(1509900)
Key No. : 2
Function + Set Supervision

Mnemo <Pocket, Mobile, 4040, Alc8&9> : -----
Ringing Mode + Long Ring
d. Associate the remote extension (1509900) to the Accelerator

(91504509900)
Remote extension number : 91504509900

SIMRING for SIP Phones and SIP Soft Clients
For users of SIP Phones and SIP Soft Clients, no incremental datafill is
required beyond the actual user datafill. In order to enable simring, the Tango
registers with the Alcatel OmniPCX PBX as another SIP endpoint for the user.
PBX Translations
When a Tango mobile user dials a phone number and the call is to be routed
through the PBX, translations are required on the PBX to route the incoming
call (from a PSTN trunk group) to the Accelerator (using via the SIP External
Gateway).
In addition, when the Accelerator determines that a call should be routed to

the wireless network, translations on the PBX are required to route the
incoming call (from the SIP External Gateway) to the PSTN (via a PSTN trunk
group).
The following PBX translations are involved for ensuring communication

between the wireless network, the enterprise network and the Accelerator.
1. Prefix Plan – Defines the first digit that is dialed. A prefix plan for
numbers that must be routed to the Accelerator should be defined. The
numbers include:
– Alias DNs
– Pilot DNs
– Service DNs
The following example shows that all numbers prefixed with a ‘9’ should
use the Discriminator Rules defined in Discriminator 1.
Figure 3 Prefix Plan – Review/Modify Screen

2. Discriminator Number – The Discriminator Number is the base

definition of a dialing route and is based upon the Prefix Plan. A
Discriminator number should be defined for the Accelerator.
The following example shows Discriminator Number 1 is defined for SIP

calls to the Accelerator.
Figure 4 Discriminator Number – Review/Modify Screen
1. Discriminator Rule – The Discriminator Rule associates a called number

to an Automatic Route Selection (ARS) list. The discriminator rule is
selected based upon the discriminator number. Integration between
Alcatel OmniPCX and the Accelerator requires Discriminator Rules to be
configured on the OmniPCX for the following types of numbers:
– Alias DNs such as the SIMRING DNs that must be routed to the
Accelerator. The example below shows an Alias DN as 15045099.
– Pilot DNs for wireless originations and termination of public DID
numbers that must be routed to the Accelerator. The example
below shows a Pilot DN as 65055099.
– Service DNs are internal service DNs that must be routed to the
Accelerator for Call Move service. The example below shows a
Service DN as 77788899.
The following example shows 3 separate Discriminator Rules instances;

one for Alias (15045099), Pilot DN (65055099), and Service DN
(77788899). The example details the Alias DN and is defined as: For all
10 digit numbers starting with 15045099, use ARS Route List 13.

Figure 5 Discriminator Rule – Review/Modify Screen
2. ARS Route List – The ARS Route List is the base definition for a trunk
route and is selected based upon the discriminator rule. An ARS Route
List must be defined for the Accelerator.
The example below shows ARS Route List 13 which is named RBAR-AE
Figure 6 ARS Route List – Review/Modify Screen
3. ARS Route – The ARS Route associates an ARS Route List to the SIP
trunk group. The ARS route is selected based upon the ARS Route List.
An ARS Route must be defined for the Accelerator’s ARS Route List.
The example below, ARS Route RBAR-AE is ARS Route List 13. It is
associated with SIP trunk 11.

Figure 7 ARS Route – Review/Modify Screen
4. Numbering Command Table – The Numbering Command Table

associates an ARS Route to a specific SIP External Gateway. A Numbering
Command Table must be associated to the Accelerator’s external SIP
gateway number. The Numbering Command Table ID must be assigned
to the Accelerator’s ARS Route.
In this example, Numbering Command Table 1 is associated to External

SIP Gateway 1.
Figure 8 Numbering Command Table – Review/Modify Screen
5. Time Based Route List – The Time Based Route List assigns what time a
specific ARS Route List can be used by the PBX. A Time Based Route List
must be associated to the Accelerator’s ARS Route List.
In this example, Time-based Route List ID 1 is associated with ARS Route

List 13 using a default Time-based Route (1,-1,-1)

Figure 9 Time-based Route List – Review/Modify Screen
6. Direct Speed Dialing Number Prefix – Speed Dialing can be configured

to automatically prepend prefix digit(s) to a dialed number. A Direct
Speed Dial Number Prefix should be created for Pilot DNs and Service DNs
so that when dialed, the OmniPCX will automatically prepend the
Accelerator’s Prefix Plan prefix digit to the Pilot DN or the Service DN
digits.
In this example, whenever the start of a PilotDN is dialed (650), the

OmniPCX will automatically insert a ‘9’, thereby matching Prefix Plan 9.
Figure 10 Direct Speed Dial Number Prefix – Review/Modify

Screen

Voice Mail Configuration
For the single voicemail service, Tango users must have a voice mail
connection path defined. Because voice mail configuration on the PBX is not
changed by the Accelerator, refer to Alcatel-Lucent documentation for
additional information about configuring voicemail for users.
It is recommended that at least four rings be used to route a call to voice mail.
PSTN Access Enabled Accelerator

To make the Accelerator the ingress/egress point for off net calls between the
PBX and your SIP Trunk provider, modify your PBX’s routing tables to send
off-net calls over a SIP Trunk to the Accelerator on the SIP Trunking port
(default of 5080). This SIP Trunk should also allow incoming calls from the
Accelerator. Make sure any required Class of Service attributes are set
appropriately on the PBX. On-net calls between PBX’s can also be configured
to route via the Accelerator using a similar process. It is often desirable to
create a second SIP Trunk on the PBX in order to specify different Class of
Service attributes for on-net calls. Consult your PBX’s configuration guide for
specific details on SIP Trunk configuration.

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 OmniPCX PBX with the Accelerator. Refer to the Accelerator Provisioning
Guide for a comprehensive explanation of Accelerator provisioning.
Voice Network: Trunk Dial Plan

1. Add Trunk Dial Plan (required) –There are no unique configuration items
for Trunk Dial Plans and the OmniPCX PBX. Refer to the Accelerator
Provisioning Guide, Voice Networks, Trunk Dial Plan section.
Voice Network: PBX

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 OmniPCX 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 Line Groups/Line (required) – One item to note when provisioning
Line Groups/Lines in the Accelerator. Line Group Request URI
parameters are not used by the OmniPCX 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.

• Add CTI Peer (XML/SOAP) connection for the Call Move service
(required for Call Move) - No unique configuration areas exist for the
OmniPCX PBX. Refer to the Accelerator Provisioning Guide, Voice
Networks, PBXs (Add/Modify), Add CTI Peer section.
• Add Least Cost Routing (optional) in the Accelerator for the OmniPCX
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: Enterprise Ranges

3. Add Enterprise Ranges (required) – No unique configuration items for
adding an Enterprise Range. Refer to the Accelerator Provisioning Guide,
Voice Networks, Enterprise 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 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 OmniPCX servers. Refer to the Accelerator
Provisioning Guide, Voice Networks, Carrier Gateway (Add/Modify),
Add Trunk Groups/Trunks section.
o 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.
Voice Network: Voice Mail

5. Add Voice Mail for the OmniPCX 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/Subscribers

6. Add Subscriber Dial Plan (required) - No unique configuration items for
adding Subscriber Dial Plans. Refer to the Accelerator Provisioning Guide,
Subscribers, Add Subscriber Dial Plan section.
7. Add Subscribers (required) - Several items to note when provisioning
subscribers:
• Home PBX – select the newly created Alcatel PBX as the subscriber’s
Home PBX.
• Home PBX Provides Orig Svcs – enable this setting. When checked,
Tango always originates the call on behalf of the mobile user for mobile
originations into their home PBX within the enterprise.
• Desk phone is SIP
o If the user’s desk phone is H.323 or digital phone (i.e., a trunk user),
leave the option unchecked
o If the user’s desk phone is SIP (i.e., a line user), check the option
If you have only Mobile UC enabled in your Accelerator license key then you
are finished.
If you also have PSTN Access enabled, proceed to the next section, PSTN
Access Enabled Accelerator.
PSTN Access Enabled Accelerator

The steps below describe the unique configuration areas needed to integrate
the OmniPCX PBX with the Tango Accelerator. Refer to the Accelerator
Provisioning Guide for a comprehensive explanation of Accelerator
provisioning.
Voice Network: Trunk Dial Plan
1. Add Trunk Dial Plan (required) –There are no unique configuration items
for Trunk Dial Plans and the OmniPCX PBX. Refer to the Accelerator
Provisioning Guide, Voice Networks, Trunk Dial Plan section.
Voice Network: PBX
2. Add PBX (required) – No unique configuration items for adding a PBX.
Refer to the Accelerator Provisioning Guide, Voice Networks, PBXs, Add
New PBX section.
• Add Trunk Groups/Trunk (required)
o Host Address corresponds to the IP address or DNS resolvable host
name of the OmniPCX PBX.
o Port must match The SIP trunk port value on the OmniPCX PBX.
o Trunk Group Request URI parameters are not used by the OmniPCX
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 (optional) in the Accelerator for the OmniPCX
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.

This finishes the PSTN Access Integration section.

Accelerator Integration Checklist – Mobile UC
OmniPCX System Level Integration items

o Define the SIP trunk between the SIP external gateway and the
Accelerator
o Define PBX Translations to route Accelerator Pilots to the Accelerator
(over the SIP Trunk)
o Define PBX Translations to route Accelerator Service Numbers to the
Accelerator (over the SIP trunk)
OmniPCX Individual User Integration items

o For Non SIP Phone Users – Option 1
– Create the tandem extension (i.e., the “secondary set”) for the
user
– Create the multi-line program key for the tandem extension
– Assign the tandem extension for the user (i.e., the “main set”)
– Create the engineered number of ghost user(s)
– Create the remote extension (to the Accelerator) for the tandem
extension.
o For Non SIP Phone Users – Option 2
– Create the remote extension for the user
– Create the multi-line program key for the remote extension
– Create the set supervision program key for the remote extension
– Associate the remote extension to the Accelerator

Mobile UC Feature Interactions
The intent of the Tango is to seamlessly add a mobile component to all of the
services that the Alcatel OmniPCX provides to the end user. The Accelerator is
integrated with PBXs at three levels of integration for Mobile UC. The
OmniPCX is integrated as 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 All 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. 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 supports 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, Tango
ensures that the least cost route is used. This results in the enterprise
voice network being used to route the call as much as possible, reducing
PSTN interconnect costs, and other voice costs such as roaming.
• Meet-Me Conference - Allows users to set up a dial-in conference of up
to six parties. The mobile user can participate in the meet-me conference
by dialing the conference bridge.

• Multiple Calls per Line – Allows multiple calls to be delivered to a single

number and have the incoming call information displayed to the user.
Accelerator supports this feature on the mobile phone based on the ability
to support call waiting for mobile phone devices. Mobile devices typically
show a maximum of two lines per mobile phone.
• PBX Do Not Disturb (Desk) – Allows users to activate or deactivate the
Do Not Disturb capability by pressing a button or a softkey from their desk
phone. When active, Do Not Disturb will not ring the mobile or desk phone.
• PBX Do Not Disturb (Mobile) - Allows users to activate or deactivate
the Do Not Disturb capability by entering a feature access code from their
mobile phone. When active, Do Not Disturb will not ring the mobile phone
however the desk phone will continue to ring.
• 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 Message 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 2 Accelerator PBX Level 1 Integration
Feature Support Comments

Abbreviated Dialing Yes
Ad Hoc Conferencing (Internal to PBX) No
Uses an external IP Media 2000
conference server. Refer to the
Ad Hoc Conferencing (External to PBX) Yes Accelerator Provisioning Guide, Voice
Networks, Conference Servers
section.
Call Forward All (Desk) Yes
Call Forward All Activation from Mobile Yes
Call Forward Busy (Desk) Yes
Call Forward Busy Activation from Mobile Yes
Call Forward No Answer (Desk) Yes
Call Forward No Answer Activation from Mobile Yes
Call Hold and Retrieve (Mobile) Yes
Call Line Identification (CLID) Yes
Call Transfer – Blind Yes
Call Transfer – Consultative Yes
Call Waiting and Retrieve Yes
Direct Inward Dialing Yes
Direct Outward Dialing Yes
Directory Dial Yes
Flexible Dialing Support Yes
Intelligent Call Delivery Yes
Least Cost Routing Yes
Meet-Me Conference Yes
Multiple Calls per Line Yes
PBX Do Not Disturb (Desk) Yes
PBX Do Not Disturb (Mobile) Yes
Single Number Services Yes
Voice Mail Message Waiting Indication Yes

Integration Level 2 provides the subscriber more advanced features than

more commonly used basic features. The following features are considered
Level 2 integration targets:
o 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.
o 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. Tango can be defined as
one of the extensions.
o 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.
o 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.
o 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.
o Class of Restriction (COR) (PBX) - Defines the restrictions that
apply when a user places or receives a call. Tango supports COR for
mobile originated calls.
o Class of Service (COS) (PBX) - Allows or denies user access to
some system features. Tango supports COS for mobile originated calls
over SIP lines.

Table 3 Accelerator PBX Level 2 Integration
Feature Support Comments

Call Accounting Codes No
Call Coverage/Hunt Groups Yes
Call Line Identification Restriction (CLIR) (Mobile) Yes
Call Pull (Desk->Mobile Call Move) Yes Requires Alcatel Open Telephony Server
Call Push (Mobile->Desk Call Move) Yes Requires Alcatel Open Telephony Server
Class of Restriction (COR) (PBX) Yes
Class of Service (COS) (PBX) Yes
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 Alcatel-
Lucent OmniPCX Enterprise Communication 7.1 PBX.

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

Accelerator Alcatel OmniPCX7.1 Integration Guide

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Accelerator Alcatel OmniPCX7.1 Integration Guide

Загружено:

Авторское право:

Доступные форматы

ACCELERATOR 8.

Tango Networks, Inc. phone: +1 469-920-2100

© 2004 - 2018 Tango Networks, Inc.

© 2004 - 2018 Tango Networks, Inc.

Revision 8.4.0.0 - April 2018 CONFIDENTIAL Page 2 of 38

ACCELERATOR INTEGRATION PROCESSES ........................................................ 6

ACCELERATOR INTEGRATION CHECKLIST – MOBILE UC.................................... 32

MOBILE UC FEATURE INTERACTIONS ............................................................. 33

Revision 8.4.0.0 - April 2018 CONFIDENTIAL Page 3 of 38

The Accelerator can potentially be provisioned in one of three ways based on

During Accelerator provisioning, a Carrier(s) was created that enabled one or

• Mobile Unified Communications (Mobile UC) - The Mobile UC

Important Note: Through out this document and other Tango

Revision 8.4.0.0 - April 2018 CONFIDENTIAL Page 4 of 38

OmniPCX PBX License Requirements – Mobile UC

Table 1 OmniPCX Software Licenses – Mobile UC

SIP Trunk License Remote Extension Ghost User MyphoneAPI

Revision 8.4.0.0 - April 2018 CONFIDENTIAL Page 5 of 38

Accelerator Integration Processes

Mobile UC Enabled Accelerator

Revision 8.4.0.0 - April 2018 CONFIDENTIAL Page 6 of 38

SIP External Gateway

Node Number (reserved) : 101

Note: Ensure that the “minimal authentication method” is set to “None”

Revision 8.4.0.0 - April 2018 CONFIDENTIAL Page 7 of 38

Open Telephony Server

The Open Telephony Server is utilized to support Accelerator Call Move

Start a session on the GUI based Web Administration (WBA) management

Figure 1 OmniTouch Login Screen

Revision 8.4.0.0 - April 2018 CONFIDENTIAL Page 8 of 38

1. After login, the following screen is displayed. Under the Provisioning

Figure 2 OmniTouch Administrator Screen

This section outlines the provisioning requirements to implement SIMRing for:

– Non-SIP Desk Phones

Provisioning is achieved via the supported management interfaces on the

Revision 8.4.0.0 - April 2018 CONFIDENTIAL Page 9 of 38

The incremental licensing requirements for implementing simultaneous

– Remote Extension – one license required per Tango subscriber

A tandem extension enables the Alcatel Simultaneous ringing functionality for

To setup SimRing for the Accelerator using the Tandem Extension

a. Create the tandem extension (2507100) for the user (2507000).

Node Number (reserved) : 101

Directory name : --------

Revision 8.4.0.0 - April 2018 CONFIDENTIAL Page 10 of 38

Equipment Address : 255

Secret Code : ****

Associated Set No. : 1000

ISDN Teleservice + Phone

PIN (Personal Ident.No.)

PIN No. : --------

Can be Called/Dialed By Name + YES

Revision 8.4.0.0 - April 2018 CONFIDENTIAL Page 11 of 38

Displayed Name : 2507000

Automatic Incoming Seizure + True

Access Code to UUS messages + NO

Revision 8.4.0.0 - April 2018 CONFIDENTIAL Page 12 of 38

Tandem Directory Number : 2507000

URL UserName : ------------------------

b. Create the multi-line program key for the tandem extension

c. Assign the tandem extension (2507100) for the user (2507000)

Directory name : 2507000

Secret Code : ****

Associated Set No. : 1000

Revision 8.4.0.0 - April 2018 CONFIDENTIAL Page 13 of 38