Accelerator Avaya CS1000 Integration Guide

ACCELERATOR 6.
3
AVAYA CS1000 INTEGRATION GUIDE
April 2014
Tango Networks, Inc. phone: +1 469-229-6000

3801 Parkwood Blvd, Suite 500 fax: +1 469-467-9840
Frisco, Texas 75034 USA www.tango-networks.com
Accelerator 6.3 Avaya CS1000 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
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 51

CONTENTS
INTRODUCTION ............................................................................................. 5
SUPPORTED VERSIONS ......................................................................................................... 6
PBX DEPENDENCIES MOBILE UC........................................................................................... 6
KNOWN LIMITATIONS .................................................................................... 7

ACCELERATOR INTEGRATION PROCESSES ........................................................ 8
MOBILE UC AND PSTN ACCESS ENABLED ACCELERATOR .................................................................. 8
MOBILE UC ENABLED ACCELERATOR ......................................................................................... 8
Assumptions ........................................................................................................ 8
CS1000 Provisioning Work Flow for Mobile UC .......................................................... 9
Avaya CS1000 7.5 Provisioning Mobile UC ...........................................................10
Avaya Aura Session Manager Provisioning (AASM) .......................................10
Define SIP Domains ........................................................................... 11
Define Locations ................................................................................ 11
Define SIP Entities Accelerator .......................................................... 12
Define SIP Entities Avaya CS1000 ..................................................... 13
Define Entity Links ............................................................................. 14
Define Entity Link CS1000 TCP Entity Link .......................................... 14
Define Entity Link CS1000 UDP Entity Link ......................................... 15
Define Entity Link Accelerator TCP Entity Link ..................................... 16
Define Entity Link Accelerator UDP Entity Link .................................... 17
Define Routing Policy ......................................................................... 18
Define Dial Pattern ............................................................................. 20
Call Server Provisioning Mobile UC ............................................................21
Before You Get Started ....................................................................... 21
Required License Keys ........................................................................ 21
Required SIP Access Port Licenses ....................................................... 22
Accessing the Call Server .................................................................... 22
Determine if Avaya CS1000 Has Sufficient Licenses ............................... 22
Enable Personal Call Assistant (PCA) Feature Mobile UC ....................... 24
Overview of Steps .............................................................................. 24
Enable PCA at Customer Level ............................................................. 24
Add Virtual Superloop......................................................................... 24
Using Call Server CLI for Virtual Superloop ........................................... 25
Configure PCA for Phones ................................................................... 25
Enabling SIP CTI via TR87 .................................................................. 26
Configure Application Module Link (AML) .............................................. 26
Configure Value Added Server (VAS) .................................................... 27
Element Manager Provisioning - Configure SIP CTI .........................................28
Configure Phones for SIP CTI Services .................................................. 32
Enabling Trunk Features ..................................................................... 37
CallPilot Voicemail Provisioning Mobile UC ...................................................38
Configure Message Waiting Indicator (MWI) .......................................... 38
Configure CallPilot subscriber .............................................................. 39
Interaction with Private Network Identifier (PNI).................................... 40
Distance Steering Codes ..................................................................... 40
PSTN ACCESS ENABLED ACCELERATOR .....................................................................................41
ACCELERATOR PROVISIONING ................................................................................................42
Mobile UC Enabled Accelerator ..............................................................................42
Voice Network : PBX/Trunk Dial Plan ............................................................42
Voice Network : Enterprise Ranges ..............................................................43
Voice Network : Carrier Gateways ................................................................43
Voice Network : Voice Mail ..........................................................................44
Subscriber: Subscribers/Subscriber Dial Plan.................................................44

PSTN Access Enabled Accelerator ..........................................................................45

Voice Network : PBX/PBX Dial Plan ..............................................................45
MOBILE UC FEATURE INTERACTIONS ............................................................. 46

ACCELERATOR PBX LEVEL 1 INTEGRATION .................................................................................46

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

your Accelerator license key. Your license key dictates whether your
enterprise has the ability to enable Mobile UC and/or PSTN Access (SIP
Trunking) functionality.
During Accelerator provisioning, a Carrier was created that enabled one or

both of these services. How you integrate your Avaya CS1000 7.5 PBX with
the Tango solution depends on how your Carrier 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, the Accelerator uses a combination of SIP lines and trunks
to integrate with the Avaya CS1000 7.5 PBX. SIP lines are used so that
Tango-controlled mobile devices appear as standard SIP phones and
therefore benefit from the common set of PBX services offered to such
devices. SIP trunks are used when the Accelerator 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, the Accelerator uses only SIP trunk(s) to integrate with
the Avaya CS1000 7.5 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.
Mobile UC and SIP Trunking combination It is possible to have both

the Mobile UC functionality as well as the PSTN Access functionality enabled
on your Accelerator.

Supported Versions
This document is intended for users with an in-depth knowledge of any of the
following:
Avaya Communication Server 1000 release 7.5

o Call Server release 7.5Q
o SIP Signaling Server release 7.50.17
o Avaya Aura Session Manager release 6.2
o Call Pilot (Voice Mail) release 5.0
Note: This guide is meant to familiarize the reader with the minimum
provisioning steps required on the Avaya CS1000 7.5 PBX for
Accelerator integration. It does not attempt to address all possible
configurations options or features that can be applied within the PBX.
Please consult your Avaya CS1000 7.5 documentation for Avaya
Communication Server 1000 specific issues.
PBX Dependencies Mobile UC
The following lists the CS1000 components and license keys required for
integrating with the Tango solution:
o CS1000 System Software Rel. 7.5
o SIP Access Port License
One per active call. Please see the Tango Engineering Guide for
how to calculate the maximum number of active calls required for
your system.
o Personal Call Assistant License
1 per Accelerator subscriber
o SIP CTI TR87
1 per Accelerator subscriber that has the optional Call Move
Feature provisioned
o AST License
1 per Accelerator subscriber that has the optional Call Move
Feature provisioned

Known Limitations
There are several issues that related to voicemail retrieval and deposit:
Issue 1: Voicemail in a Route Direct scenario does not work properly. The
call attempts voicemail retrieval instead of deposit. A ticket is open
with Avaya to resolve this problem.
Issue 2: UNISTIM phones that attempt voicemail retrieval must first enter
their desk extension followed by the # sign then followed by their
password. The call does not automatically recognize the
subscribers mail box number. A ticket is open with Avaya to
resolve this problem.
Issue 3: MWI for UNISTIM subscribers does not update MWI on the
subscribers mobile phone. A ticket is open with Avaya to resolve
this problem.

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 functions, or
even both.
The sections and steps outlined below will guide your workflow to integrate
your Avaya Communication Server 1000 PBX with the Accelerator.
Mobile UC and PSTN Access Enabled Accelerator
For a Mobile UC and PSTN Access enabled Accelerator, execute both sets of
steps outlined below; Mobile UC Enabled Accelerator section and the PSTN
Access Enabled Accelerator section. It does not matter which set you execute
first, meaning it does not matter if you provision PSTN Access first or Mobile
UC first.
Mobile UC Enabled Accelerator
Assumptions
It is assumed that the basic configuration of the Call Server and SIP Signaling
Server applications has been completed, and that the Avaya Communication
Server 1000 is configured to support analog, digital, UNIStim, and SIP
telephones.
It is also assumed that the definitions for PSTN routing already exist in the
CS1000 configuration.
For references on how to administer these functions see:
https://support.avaya.com

CS1000 Provisioning Work Flow for Mobile UC
The workflow to integrate the Avaya CS1000 with the Accelerator is described
below. This outline reflects the Table of Contents and is repeated here for
clarity.
Avaya Aura Session Manager Provisioning Mobile UC

o Define SIP Domains
o Define Locations
o Define SIP Entities:
Accelerator
Avaya CS1000 PBX
o Define Entity Links:
CS1000 TCP and UDP Entity Links
Accelerator TCP and UDP Entity Links
o Define Routing Policy
o Define Dial Pattern
Call Server Provisioning Mobile UC
o Before You Get Started:
Required License Keys
Required SIP Access Port Licenses
- Accessing the Call Server
o Enable Personal Call Assistant (PCA)
Enable PCA at the Customer Level
Add Virtual Superloop
Configure PCA for Phones
o Enable SIP CTI TR87 (for Call Move service)
Configure AML and VAS
o Enable SIP Trunk Features
Element Manager (via UCM) Mobile UC
o Configure SIP CTI on the Element Manager
Call Pilot (Voicemail) Provisioning
o Configure Message Waiting Indicator (MWI)
o Configure CallPilot Subscriber
Last of Call Server Provisioning Mobile UC
o Interaction with PNI
o Distance Steering Codes

Avaya CS1000 7.5 Provisioning Mobile UC
The following sections cover provisioning for the Avaya CS1000 7.5 PBX for
integration with the Accelerator Mobile UC services.
Avaya Aura Session Manager Provisioning (AASM)
This section provides the procedures for configuring the AASM to route calls
between the CS1000 and the Accelerator.
Configuration is accomplished by accessing the browser-based GUI of the

Aura System Manager, using the URL:
http://<fqdn>/SMGR
Where <fqdn> is the fully qualified domain name of Aura System Manager.
Log in to SMGR with the appropriate credentials (not shown).
From the main System Manager page click on the Routing link as shown in
the Figure 1.
Figure 1 SMGR Routing Link

Define SIP Domains

1. Expand the Routing menu topic and select Domains as shown in Figure
2.
2. Click New (not shown). Enter the following values and use default values
for remaining fields:
Name Enter the Authoritative Domain Name. In the sample
configuration, bvdwdev.com was used.
Type Select sip .
Notes (optional) Add a description.
3. Click Commit to save. Figure 2 below shows the SIP Domain defined for
the bvwdev.com domain.
Figure 2 SIP Domain Defined - AASM
Define Locations
Locations are used to identify logical and/or physical locations where SIP
Entities reside for purposes of bandwidth or location-based routing.
1. Expand Routing and select Locations from the left menu.

2. Click New (not shown).
3. In the General section, enter the following values and use default values
Name Enter a descriptive name for the location.
Notes (optional) Add a brief description
4. In the Location Pattern section, click Add and enter the following
values:
IP Address Pattern Enter the logical pattern used to identify the
location. For this sample configuration, 192.168.*.* was used.
Notes (optional) Add a brief description.

5. Click Commit to save.
Figure 3 below shows the Location defined in this sample configuration.
Figure 3 Location Defined - AASM
Define SIP Entities Accelerator
A SIP Entity must be added for each telephony system connected to the
Session Manager over SIP trunks.
1. Define the Tango Accelerator SIP Entity by expanding the Routing

topic and select SIP Entities from the left menu.
Name Enter an identifier for the SIP Entity.
FQDN or IP Address Enter IP address of the Accelerator.
Type Select Other.
Notes (optional) Enter a brief description
Adaptation No adaptation was used.
Location Select the Location defined in the Define Locations section on
page 11.
Time Zone Enter the appropriate Time Zone.

6. SIP Link Monitoring Select Use Session Manager Configuration.

7. Click Commit to save the definition of the new SIP Entity.
Figure 4 shows the SIP Entity defined for the Accelerator in the sample
configuration.
Figure 4 Accelerator SIP Entity Defined - AASM
Define SIP Entities Avaya CS1000

1. Define the Avaya CS1000 SIP Entity by expanding the Routing topic
and select SIP Entities from the left menu.
Name Enter an identifier for the SIP Entity.
FQDN or IP Address Enter IP address of the Avaya CS1000.
Type Select SIP Trunk.
Notes (optional) Enter a brief description
Adaptation No adaptation was used.
Location Select the Location defined in the Define Locations section on
page 11.
Time Zone Enter the appropriate Time Zone.
8. SIP Link Monitoring Select Use Session Manager Configuration.
9. Click Commit to save the definition of the new SIP Entity.
Figure 5 shows the SIP Entity defined for the CS1000 in the sample
configuration.

Figure 5 Avaya CS1000 SIP Entity Defined - AASM
Define Entity Links
A SIP trunk between the Session Manager and a telephony system is

described by an Entity Link. In the sample configuration, SIP Entity Links
were added between the Session Manager and each telephony system.
Define Entity Link CS1000 TCP Entity Link

1. Expand Elements -> Routing and select Entity Links from the left
menu.
3. Enter the following values to configure an Entity Link for the CS1000:
Name Enter an identifier for the link.
SIP Entity 1 Select SIP Entity defined for the Session Manager.
SIP Entity 2 Select the CS1000 SIP Entity defined in the Define SIP
Entities Avaya CS1000 on page 13.
Protocol - After selection SIP Entity 1 and 2, select TCP as the required
protocol.
Port Verify Port for both SIP entities is the default listen port. For the
sample configuration, default listen port is 5060.
Connection Policy From the drop-down menu, select Trusted.
Notes (optional) Enter a brief description.

10. Click Commit to save Entity Link definition.
Figure 6 shows the TCP entity link defined for the SIP trunk between the
Session Manager and the CS1000.
Figure 6 Entity Link between CS1000 and Session Manager (TCP)

Defined - AASM
Define Entity Link CS1000 UDP Entity Link

menu.
3. Enter the following values to configure an Entity Link for the CS1000:
SIP Entity 2 Select the CS1000 SIP Entity defined in in the Define SIP
Entities Avaya CS1000 on page 13.
Protocol - After selection SIP Entity 1 and 2, select UDP as the required
protocol.

Figure 7 shows the UDP entity link defined for the SIP trunk between the
Session Manager and the CS1000.
Figure 7 Entity Link between CS1000 and Session Manager (UDP)
Define Entity Link Accelerator TCP Entity Link

menu.
3. Enter the following values to configure an Entity Link for the Accelerator:
SIP Entity 2 Select the Accelerator SIP Entity defined in the Define SIP
Entities Accelerator on page 12.
Protocol - After selection SIP Entity 1 and 2, select TCP as the required
protocol.

Figure 8 shows the TCP entity link defined for the SIP trunk between the
Session Manager and the Accelerator.
Figure 8 Entity Link between Accelerator and Session Manager

(TCP)
Define Entity Link Accelerator UDP Entity Link

menu.
6. Enter the following values to configure an Entity Link for the Accelerator:
SIP Entity 2 Select the Accelerator SIP Entity defined in Define SIP
Entities Accelerator on page 12.
Protocol - After selection SIP Entity 1 and 2, select UDP as the required
protocol.

Figure 9 shows the UDP entity link defined for the SIP trunk between the
Session Manager and the Accelerator.
Figure 9 Entity Link between Accelerator and Session Manager

(UDP)
Define Routing Policy
Routing policies describe the conditions under which calls are routed to the
SIP Entities specified in the Define SIP Entities Accelerator section and the
Define SIP Entities Avaya CS1000 section on pages 12 and 13 respectively.
Two routing policies must be added, one for the CS1000 and one for
Accelerator.
1. To add a routing policy, expand Elements Routing and select Routing

Policies.
3. In the General section, enter the following values:
Name - Enter an identifier to define the routing policy.
Disabled - Leave unchecked.
Notes (optional) - Enter a brief description.
4. In the SIP Entity as Destination section, click Select. The SIP Entity
List page opens (not shown).
Select the SIP Entity associated with CS1000 defined in the Define SIP
Entities Avaya CS1000 section on page 13 and click Select. (For the
SIP Entity associated with the Accelerator, the reference is the Define SIP
Entities Accelerator section on page 12.)
The selected SIP Entity displays on the Routing Policy Details page.
5. Use default values for the remaining fields. Click Commit to save the
Routing Policy definition.
Note: The routing policy defined in this section is an example. Other

routing policies may be appropriate for your networks.

Figure 10 shows the Routing Policy for the CS1000.
Figure 10 Routing Policy for CS1000
6. Repeat all the steps in this section and define the routing policy to the
Accelerator as shown in Figure 11.
Figure 11 Routing Policy for Accelerator

Define Dial Pattern

1. To define a dial pattern, expand Routing select Dial Patterns (not
shown).
for the remaining fields:
Pattern Enter dial pattern for calls to the CS1000.
Min Enter the minimum number of digits that must be dialed.
Max Enter the maximum number of digits that may be dialed.
SIP Domain Select the SIP Domain from the drop-down menu or select
All if the Session Manager should accept incoming calls from all SIP
Domains.
4. In the Originating Locations and Routing Policies section, click Add.
5. The Originating Locations and Routing Policy List page opens (not shown).
6. In Originating Locations table, select Belleville.
7. In Routing Policies table, select the Routing Policy defined for CS1000 in
the Define Routing Policy section on page 18.
8. Click Select to save these changes and return to the Dial Pattern
Details page.
9. Click Commit to save.
Figure 12 shows the Dial Pattern defined for the sample configuration to route
calls to the CS1000.
Figure 12 Dial Pattern to the CS1000

Figure 13 shows the Dial Pattern defined for the sample configuration to route
calls to the Accelerator.
Figure 13 Dial Pattern to the Accelerator
Call Server Provisioning Mobile UC
To use Accelerator services, subscribers need to be provisioned with certain

features. The following sections detail the steps required to enable these
services.
Before You Get Started
Before you start to provision subscribers, check the subscriber feature

licenses and the SIP access port licenses.
Required License Keys
To enable the subscriber features required for Accelerator service, the

following license keys must be enabled and have sufficient resources available
(one unit per Accelerator subscriber):
Personal Call Assistant (PCA)
AST
SIP CTI TR87

Required SIP Access Port Licenses
The Avaya CS1000 also requires a sufficient number of SIP Access Port (i.e.,
SIP Trunk) licenses to facilitate communication with the Accelerator. SIP
Access Port licenses are calculated based on the maximum number of
concurrent calls allowed via the SIP protocol.
Accessing the Call Server
The Call Server CLI can be accessed from the Unified Communications
Manager CLI using the cslogin command via a console session such as
PuTTY.
Figure 14 Call Server CLI Login
Determine if Avaya CS1000 Has Sufficient Licenses
The following steps explain how an administrator can determine if the Avaya
CS1000 system has a sufficient number of licenses:
1. cslogin Log in to the Call Server.
2. LD 22 Navigate to Overlay 22.
3. REQ: SLT Print out system limits.
A list similar to the following will be displayed. Verify that the license
requirements can be met. The four relevant license types and the number of
IP users are highlighted below in bold. Each license type needs to have a
number greater than 0 in the LEFT column.

System type is Communication Server 1000/CPPM Linux

CPPM - Pentium M 1.4 GHz
IPMGs Registered: 1
IPMGs Unregistered: 0
IPMGs Configured/unregistered: 0
TRADITIONAL TELEPHONES 32767 LEFT 32749 USED 18

DECT USERS 32767 LEFT 32767 USED 0
IP USERS 32767 LEFT 32705 USED 62
BASIC IP USERS 32767 LEFT 32765 USED 2
TEMPORARY IP USERS 32767 LEFT 32767 USED 0
DECT VISITOR USER 10000 LEFT 10000 USED 0
ACD AGENTS 32767 LEFT 32759 USED 8
MOBILE EXTENSIONS 32767 LEFT 32760 USED 7
TELEPHONY SERVICES 32767 LEFT 32767 USED 0
CONVERGED MOBILE USERS 32767 LEFT 32767 USED 0
AVAYA SIP LINES 32767 LEFT 32750 USED 17
THIRD PARTY SIP LINES 32767 LEFT 32745 USED 22
PCA 32767 LEFT 32766 USED 1

ITG ISDN TRUNKS 32767 LEFT 32767 USED 0
H.323 ACCESS PORTS 32767 LEFT 32767 USED 0
AST 32767 LEFT 32756 USED 11
SIP CONVERGED DESKTOPS 32767 LEFT 32767 USED 0
SIP CTI TR87 32767 LEFT 32743 USED 24
SIP ACCESS PORTS 32767 LEFT 32703 USED 64
RAN CON 32767 LEFT 32767 USED 0
MUS CON 32767 LEFT 32767 USED 0
IP RAN CON 16884 LEFT 16884 USED 0

IP MUS CON 16896 LEFT 16896 USED 0
IP MEDIA SESSIONS 35842 LEFT 35842 USED 0
TNS 32767 LEFT 32337 USED 430
ACDN 24000 LEFT 23896 USED 14
AML 16 LEFT 10 USED 6
IDLE_SET_DISPLAY CS1K 7.5_1
LTID 32760 LEFT 32705 USED 0
RAN RTE 512 LEFT 512 USED 0
ATTENDANT CONSOLES 32767 LEFT 32767 USED 0
IP ATTENDANT CONSOLES 32767 LEFT 32767 USED 0
BRI DSL 10000 LEFT 10000 USED 0
DATA PORTS 100 LEFT 100 USED 0
PHANTOM PORTS 32767 LEFT 32767 USED 0
TRADITIONAL TRUNKS 32767 LEFT 32757 USED 57
ELC ACCESS PORTS 32767 LEFT 32767 USED 0
DCH 255 LEFT 249 USED 0
The output in the above example shows 32,766 licenses available for PCA,
32,756 for AST, and 32,743 for SIP CTI TR87. This means that up to 32,743
Avaya CS1000 users can be provisioned for Accelerator services. (Each
Accelerator user requires one license for each of the three PCA, AST, and SIP
CTI TR87 services.)
Note: The previous example also shows 32,703 SIP ACCESS PORTS
available. As configured above, the Avaya CS1000 is configured to
support 64 SIP dialogs on the Avaya CS1000 at the same time.

Enable Personal Call Assistant (PCA) Feature Mobile UC
The Personal Call Assistant (PCA) feature allows a second DN to be alerted

whenever a subscriber receives an incoming call. The second DN is alerted in
parallel (simultaneously) with the device(s) associated with the primary DN.
The Accelerator requires this service in order to alert the subscribers mobile
device in parallel with the users desk phone.
Overview of Steps
To enable this service for a subscriber, use the following one time setup
procedures:
Enable PCA at customer level
After the above one-time setup procedures are completed, use the next
procedure for each subscriber who will have access to the Accelerator PCA
feature:
Each of these procedures is explained next.
Enable PCA at Customer Level

1. cslogin Log in to call server.
2. LD 15 Go to Overlay 15.
3. Press Enter for all prompts to enable PCA at the customer level.
REQ: CHG
TYPE: FTR
CUST: xx For Large System and CS1000: 0-99
For Small System, CS1000S, Media Gateway 1000B, and Media
Gateway 1000T: 0-31
PCA: ON Enables Personal Call Assistant.
The virtual superloop is an area that is assumed to already exist or the

administrator knows how to manage a virtual superloop. The CLI-based
instructions presented here are for completeness.
A superloop must be set up in order to enable simultaneous ringing of the

Accelerator to provide services to the mobile phone. Since every superloop
contains 4 sets of 32 VTNs, 1 superloop must be set up for every 128
Accelerator subscribers.

Virtual Terminal Numbers (VTNs) enable configuration of service data for an

IP phone, such as key layout and class of service, without requiring the IP
phone to be dedicated (hard-wired) to a given TN on the Voice Gateway
Media Card.
Using Call Server CLI for Virtual Superloop

3. Press Enter for all prompts.
REQ: CHG
TYPE: SUPL
SUPL: Vxxx Virtual super loop in multiples of 4.
For Large System: v0-v156
For systems with Fibre Network Fabric: v0-v252
For CS1000: v0-v252
For Small System and CS1000S: v96-v112
Example SUPL entries:

SUPL: V96
SUPL: V100
Per-TN configuration is required to define a PCA TN for each

Acceleratornabled subscriber. Before executing this procedure, however,
allocate a range of numbers to use as the target DN for the PCA feature (i.e.,
the DN that will be alerted in parallel to the primary DN). Using the DN and
adding a unique prefix is the recommended alias DN format. Calls terminating
to this range will be configured to route via a SIP Trunk to the Accelerator in a
later step.

3. Press Enter for all prompts other than those listed below.
REQ: NEW
TYPE: PCA
TN: l s c u For Large System and CS1000 system
where l = loop, s = shelf, c = card, u = unit
or
TN: c u For Small System, CS1000S system, Media Gateway 1000B, and
Media Gateway 1000T
where c = card and u = unit
CUST: xx Where xx is the customer number defined in LD 15

CLS: AHA Automatic Hold Allowed
KEY: 0 aaa Primary PCA DN
yyyy where aaa = MCN, MCR, SCN, or SCR
where yyyy = the primary DN

KEY:1 HOT P Target PCA DN

nn yyyy where nn = length of the PCA DN (32 maximum)
where yyyy=the target DN (the number to ring
simultaneously with primary DN)
Example KEY entries:

KEY: 0 MCR 2359905
KEY: 1 HOT P 10 1354359905
In this example, if a call terminates to 2359905 the CS1000 will
ring 2359905 and 1354359905 simultaneously.
For more information, refer to the Personal Call Assistant section in the Avaya
NN43001-106 document.
Enabling SIP CTI via TR87
The Tango solution uses the CS1000s SIP CTI link to provide the Call Move
feature. This feature allows an active call to be moved from a desk phone to a
mobile and vice-versa. Each Acceleratornabled subscriber who has the Call
Move feature must therefore have the SIP CTI service activated. Each
subscriber requires an AST license and a SIP CTI license in order to activate
SIP CTI. (See Required License Keys on page 21.)
Overview of Steps
To enable SIP CTI for a subscriber, use the following one time setup
procedures. The SIP CTI is for the Accelerator Call Move Service:
Configure Application Module Link (AML) (used for SIP CTI
communication)
Configure Value Added Server (VAS) such as to set up an IP server
Configure SIP CTI on Element Manager
After the above one-time setup procedures are executed, use the next
procedure for each subscriber that will have access to the Accelerator Call
Move feature:
Configure Phones for SIP CTI services
Each of these procedures is explained next.
Configure Application Module Link (AML)

REQ: CHG
TYPE: ADAN

ADAN: NEW ELAN xx A new AML link; the link is an ELAN type.
For Small System: 32 to 47

For Large System: 32 to 127.
An AML link number in the above range implies that the

transport is over a TCP link, and denotes a logical AML
ELAN type.
CTYP: ELAN
Configure Value Added Server (VAS)

2. LD 17 Go to Overlay 17
REQ: CHG
TYPE: VAS
VAS: NEW
VSID: vas# VAS ID
For Small System: 32 to 47

For Large System: 32 to 127
A VAS number in the above range denotes a logical

VAS ID.
ELAN link# The AML ELAN link number provisioned when the
AML link was created.
SECU: No Enables security for Meridian Link Applications.

Element Manager Provisioning - Configure SIP CTI
To complete these steps, you must log first login to the Unified
Communications Manager (UCM). Use Internet Explorer to access the web
interface:
The UCM login URL is similar to:
https://192.168.x.x/network_login
1. Find and click the Go to central login for Single Sign-On link.
Figure 15 UCM Login screen
2. Enter the User ID and Password to Log In.
Figure 16 UCM Single Sign-On Login screen

3. The following screen is displayed. Select the link for appropriate Element
Manager. In the example configuration, EM on cppm1 was selected.
Figure 17 Element Manager Login
4. Select System IP Network Nodes: Servers, Media.

5. In this example, we selected Node 551.
Figure 18 Node Screen

6. Select the Node and scroll down until you find and click Gateway
(SIPGw).
Figure 19 Select Gateway (SIPGw) Screen

7. Ensure that the SIP CTI Service: Enable CTI service is enabled
(checked).
8. Click Save.
Figure 20 Enable CTI Service on Element Manager
9. Select the Signaling Server instance in the lower portion of the screen.
Synchronize the Node by clicking the Start Sync button.
Figure 21 Synchronize Node

10. Select the Signaling Server instance in the lower portion of the screen.
Synchronize the Node by clicking the Start Sync button.
Figure 22 Transfer Configuration to Node
Configure Phones for SIP CTI Services
Note: This procedure must be done for each phone.
Per-TN configuration is required to define which TNs are used for SIP CTI and
to define the specific DN keys on each TN that are available for control by SIP
CTI applications. Use the Call Server console command line:
1. cslogin Log in to call server

12. Press Enter for all prompts other than those listed below to turn on T87A.
REQ: CHG
TYPE: xxx Where xxx is the digital phone type of the DN, e.g., i2001,
i2004, i2050, etc., depending on the primary desk phone type
TN: l s c u For Large System and CS 1000 system:
where l = loop, s = shelf, c = card, u = unit
or
TN: c u For Small System, CS 1000S system, Media Gateway 1000B,
and Media Gateway 1000T:
where c = card and u = unit
ECHG: YES Enables TR87 Allow Remote Call Control
ITEM: CLS T87A
ITEM: AST 0
ITEM: Press Enter to exit
REQ: PRT Print the TN to validate the change
You should see output similar to the following. Validate that T87A and AST 00
show up under the CLS section. (Each is highlighted in bold in the following
sample output.)

TYPE: 2004P1
TN 61 05
DATE
PAGE
DES
MODEL_NAME
EMULATED
KEM_RANGE
DES SET01
TN 061 0 00 05 VIRTUAL
TYPE 2004P1
CDEN 8D
CTYP XDLC
CUST 0
NUID
NHTN
CFC_ZONE 001
CUR_ZONE 001
ERL 0
ECL 0
FDN
TGAR 0
LDN NO
NCOS 7
SGRP 0

RNPG 0
SCI 0
SSU
XLST
CLS CTD FBD WTA LPR MTD FND HTD TDD HFA CRPD
MWD LMPN RMMD SMWD AAD IMD XHD IRD NID OLD VCE DRG1
POD DSX VMD SLKD CCSD SWD LND CNDA
CFTD SFD MRD DDV CNID CDCA MSID DAPA BFED RCBD
ICDD CDMD LLCN MCTD CLBD AUTU
GPUD DPUD DNDA CFXD ARHD CLTD ASCD
CPFA CPTA ABDD CFHD FICD NAID BUZZ AGRD MOAD
AHA DDGA NAMA
DRDD EXR0
USMD USRD ULAD RTDD RBDD RBHD PGND FLXD FTTC MCBN
VOLA VOUD CDMR ICRD MCDD T87A KEM2 MSNV FRA PKCH
CPND_LANG ENG
HUNT
PLEV 02
DANI NO
AST 00
Note: AST specifies primary phone (Key 00) which is the only phone
line that can be specified for a call move.
IAPG 0
AACS NO
ITNA NO

DGRP
MLWU_LANG 0
MLNG ENG
DNDR 0
KEY 00 MCR 2359905 0 MARP
CPND
NAME Some CS1K User
XPLN 14
DISPLAY_FMT FIRST,LAST
01 MCR 2359905 0
CPND
NAME Some CS1K User
XPLN 14
DISPLAY_FMT FIRST,LAST
02
03
04
05
06
07
08
09
10
11
12

13
14
15
16
17 TRN
18 AO6
19 CFW 16
20 RGA
21 PRK
22 RNP
23
24 PRS
25 CHG
26 CPN
27
28
29
30
31

Enabling Trunk Features
To enable the Accelerator Call Move feature, two trunk features must be
enabled (value = YES) on the Call Server:
TRNX - Allow transfer on ringing of supervised external trunks across the
network.
EXTT - Allow unconditional external trunk-to-trunk transfer. A caller can
transfer a call made to one outgoing trunk to another outgoing trunk
without restrictions based on supervision. This prompt applies only to
situations involving two calls originated by the same caller.
Note: Even though both the TRNX and EXTT trunk features need to be
enabled (there by allowing external trunk transfers), you can still
maintain security on the CS1000 by using trunk-to-trunk access
restriction features like Trunk Group Access Restriction (TGAR) / Trunk
Access Restriction Group (TARG) and Trunk Barring. If the TRNX and
EXTT features are not enabled, then phones cannot transfer calls
externally from the CS1000, which would prevent the Accelerator Call
Move feature from working.
TGAR controls access to the exchange network, tie trunks, and other
trunks and services on the CS1000. Phones are assigned a TGAR code to
block access to certain trunk groups. When a phone tries to access a
trunk route, the system first checks the Class of Service of the terminal.
If access is allowed, the system then checks the TGAR code. If the TGAR
code of the phone matches one of the Trunk Access Restriction Group
codes programmed against the trunk group, access is denied. For
example, a phone with a TGAR code of 1 cannot use trunks that have a
TARG code of 1.
To enable these features, perform the following steps:

14. Press Enter for all prompts other than those listed below to change the
customer data block.
REQ: CHG
TYPE: NET
TYPE NET_DATA:
CUST: 0
TRNX: YES
EXTT: YES

CallPilot Voicemail Provisioning Mobile UC
The Tango solution supports the CS1000/CallPilot voicemail solution. The

CS1000 notifies the Accelerator by sending a SIP NOTIFY for voicemail
deposit and retrieval. The CallPilot entry for the CS1000 subscriber is
configured with the alias DN of CS1000 subscriber.
Overview of Steps
Configure Message Waiting Indicator (MWI) (enables SIP NOTIFY
communication)
Configure CallPilot subscriber with a MWI DN (this is the alias DN of the
CS1000 subscriber)
Configure Message Waiting Indicator (MWI)

REQ: CHG
TYPE: ADAN
ADAN: CHG DCH XX
RCAP: MWI Add MWI as a Remote Capability of the far-end

Configure CallPilot subscriber
For the Accelerator to receive MWI messages (Message Waiting Indicator) for
a subscriber, the PCA alias DN of that CS1000 subscriber must be added in
the CallPilot MWI DN field.
17. Log in to CallPilot web provisioning interface.

18. In Figure 23 below, we searched for Extension DN 58713. Next, we
clicked the 11201 search result for that subscriber.
Figure 23 Search for CallPilot subscriber
19. Add CS1000 alias DN of the subscriber to the subscribers CallPilot

account.
Figure 24 Configure MWI alias DN

The CallPilot subscriber DNs page describes the DNs that are alerted upon a
voicemail notification as shown by the MWI DN fields. Figure 24 shows a
subscriber DN of 58713, and an alias DN of 458713.
Interaction with Private Network Identifier (PNI)

When a PNI other than 0 is defined in the Route Data Block (RDB) of the
CS1000, a voicemail deposit results in a SIP INVITE being sent to the
Accelerator (in addition to the SIP NOTIFY). When this SIP INVITE message is
received by the Accelerator, it is rejected with a SIP 488 Not Acceptable
Here final response message. The voicemail notification operation is not
affected by this extraneous SIP INVITE message exchange and can be
ignored.
The following procedure can be used to view the PNI configuration on the
CS1000:
20. LD 21 List Configuration ISDN service route
REQ: PRT
TYPE: RDB
ISDN: YES
PNI: (1) 1-32700 Default value is PNI=1
Distance Steering Codes
In the section Create Route Entries to Accelerator Gateway Endpoint,

the Alias DN, Pilot DN, and Service DN prefix routes were added to go to the
AASM for SIP trunking. With the SIP/PRI Gateway option, the Pilot DN now
needs to be routed to the appropriate PRI trunk to the SIP/PRI Gateway. This
is done via Distance Steering Codes (DSC).
The Pilot DN prefix should already have a DSC defined in Overlay 87. The
DSC has a Route List Index (RLI) that points to a Route List Blocks (RLB).
Each RLB will have Route Numbers (ROUT) which points to a Route Data
Block (RDB) that either contains a SIP or PRI trunk. The DSC needs to have
the RLI changed to from the SIP trunk to the PRI trunk.
To display the current DSC setting:
1. cslogin Log in to call server

REQ: prt
CUST: 0
FEAT: cdp
TYPE: dsc Distance Steering Code
DSC: 33 Prefix 33

The displayed output:

DSC 33
FLEN 10
DSP LSC
RLI 2
NPA
NXX
To change the RLI, enter chg under REQ and press Enter until the RLI line is
reached.
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 PBXs 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 PBXs 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 PBXs 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 section discusses the integration process for a Mobile UC with/without a

PSTN Access enabled Accelerator.
The steps below describe the unique configuration areas needed to integrate
the Avaya CS1000 7.5 PBX with the Tango solution. 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 Avaya CS1000 7.5 PBX. Refer to the
Accelerator Provisioning Guide, Voice Networks, PBXs, Add Trunk Dial Plan
section.
2. Add PBX (required) The Domain name field must match what was
provisioned on the CS1K. See the Define SIP Domains section on page
11. For all other PBX fields, refer to the Accelerator Provisioning Guide,
Voice Networks, PBX section.
Add Trunk Group/Trunk Create a trunk group according to the
Accelerator Provisioning Guide. Phones that do not register with the
Avaya CS1000 PBX are considered trunk type phones.
o Host Address, Port and Transport Type should match the value
configured for the Node IP of the Avaya CS1000 7.5 platform.
o Trunk Group Request URI parameters are not used by the Avaya
CS1000 7.5 PBX and therefore do not need to be provisioned.
Add Line Group/Line Create a line group according to the Accelerator
Provisioning Guide Voice Networks, PBXs (Add/Modify), Add Line
Groups/Trunk section. Phones that register directly to the PBX are
considered line type phones.
Add Pilot Numbers (required). No unique configuration areas required
for provisioning Pilot Numbers to the Accelerator system. Refer to the
Accelerator Provisioning Guide, Voice Networks, PBXs (Add/Modify)
section.

Add Call Service Pilot Number (optional but recommended for 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 in the Accelerator system for the Avaya
CS1000 7.5 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.
Modify the Subscription Parameters to configure SIP subscription
parameters (recommended).
o The Subscription Duration should be set to the same value as
configured on the Avaya CS1000 7.5. This value indicates how often
the Accelerator needs to re-register for SIP lines.
o The Maximum Outstanding Requests field will throttle the number
of subscription requests the Accelerator sends to the Avaya CS1000
7.5 at any one time, preventing accidental overload of the server. This
number may need to be increased if a large number of subscribers
need to be registered in a short period of time (e.g. using the default
two minute duration time).
Voice Network : Enterprise Ranges

3. Add Extension Ranges (required) No unique configuration items for
adding an Enterprise Range. Refer to the Accelerator Provisioning Guide,
Voice Networks, Enterprise Ranges, Add New 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 Gateways main page. Depending on your configuration,
the Pilot numbers here may need to be E.164 routable.
Add Trunk Group/Trunk (required if using a Carrier Gateway)
o Host Address, Port and Transport Type should match the value of
the carriers 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 Avaya CS1000 7.5 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 carriers 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

3. Add Voice Mail for the Avaya CS1000 7.5 PBX in the Accelerator system.
Select SIP the Voice Mail Server Type. Provide a voicemail retrieval and
deposit number in addition to an MWI host address and port number. This
item assumes that a CallPilot Voice Mail server is used with the CS1000
PBX. Refer to the Accelerator Provisioning Guide, Voice Networks, Voice
Mail Servers, Add Voice Mail Server section.
Subscriber: Subscribers/Subscriber Dial Plan

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. Several items to note when provisioning subscribers.
For more information, refer to the Accelerator Provisioning Guide,
Subscribers, Subscribers section:
o Home PBX Select the newly created Avaya CS1000 7.5 7.5 PBX as
the subscribers Home PBX.
o Home PBX Provides Orig Svcs Enable this setting for those
phones that will register as a line interface to the PBX. When checked,
the Accelerator always originates the call on behalf of the mobile user
for mobile originations into their home PBX within the enterprise. For
non-line phones (i.e. SIP phones), there is no need to check this box
as it will only affect routing and not present the call as a line type
call.
o Alias Refer to the Enable Personal Call Assistant (PCA) Feature
Mobile UC section on page 25 for information on provisioning the Alias
field.
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
This section is for those Accelerators that have only PSTN Access enabled or
have both Mobile UC and PSTN Access enabled.
If your configuration is Mobile UC only, refer to section Mobile UC

with/without PSTN Access Enabled Accelerator starting on page 42.
The steps below describe the unique configuration areas needed to integrate
the Avaya CS1000 7.5 PBX with the Tango solution. Refer to the Accelerator
Provisioning Guide for a comprehensive explanation of Accelerator
provisioning.
Voice Network : PBX/PBX Dial Plan

1. Add Trunk Dial Plan (required) There are no unique configuration items
for Trunk Dial Plans and the Avaya CS1000 7.5 PBX. Refer to the
Accelerator Provisioning Guide, Voice Networks, PBXs, Add Trunk Dial Plan
section.
2. Add PBX The Domain name field must match what was provisioned on
the CS1K. See the Define SIP Domains section on page 11. For all other
PBX fields, refer to the Accelerator Provisioning Guide, Voice Networks,
PBX section. For all other PBX fields, refer to the Accelerator Provisioning
Guide, Voice Networks, PBX section.
Add Trunk Group/Trunk (required)
o Refer to the Accelerator Provisioning Guide, Voice Networks, PBXs
(Add/Modify), Add Trunk Groups/Trunk section.
Add Least Cost Routing in the Accelerator system for the Avaya
CS1000 7.5 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.

Mobile UC Feature Interactions
Accelerators integration with PBXs is done in three levels. Avaya CS1000 7.5
has been integrated at Level 1 for Mobile UC with one addition, Call Move,
which is a Level 2 feature. The following charts indicate the PBX features that
have been integrated as part of the 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. 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.
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 Tango solution 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
subscribers 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. 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.
Direct Inward Dialing - Allows the desk phone to be directly accessed
from the PSTN. The Tango solution supports enterprise Direct Inward
Dialing.
Direct Outward Dialing - Allows users inside an enterprise to dial
directly to an external number. The Tango solution 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 subscribers 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.
Table 1 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
Yes
Mobile
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:
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.
Table 2 Accelerator PBX Level 2 Integration
Feature Support Comments

Call Accounting Codes No
Call Coverage/Hunt Groups No
Call Line Identification Restriction (CLIR) (Mobile) Yes
Call Pull (Desk->Mobile Call Move) Yes
Call Push (Mobile->Desk Call Move) Yes
Class of Restriction (COR) (PBX) No
Class of Service (COS) (PBX) No

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 features with the
Avaya Communication Server 1000 PBX.

Tango Networks, Inc.
3801 Parkwood Blvd, Suite 500
Frisco, Texas 75034 USA
phone: + 1 469-229-6000
fax: + 1 469-467-9840
www.tango-networks.com

Accelerator Avaya CS1000 Integration Guide

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Accelerator Avaya CS1000 Integration Guide

Caricato da

Copyright:

Formati disponibili

ACCELERATOR 6.

Tango Networks, Inc. phone: +1 469-229-6000

2004 - 2014 Tango Networks, Inc.

2004 - 2014 Tango Networks, Inc.

April 2014 CONFIDENTIAL Page 2 of 51

KNOWN LIMITATIONS .................................................................................... 7

April 2014 CONFIDENTIAL Page 3 of 51

PSTN Access Enabled Accelerator ..........................................................................45

MOBILE UC FEATURE INTERACTIONS ............................................................. 46

April 2014 CONFIDENTIAL Page 4 of 51

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

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

Mobile UC - The Mobile UC application extends PBX and Unified

PSTN Access (e.g. SIP Trunking Controller) PSTN Access facilitates

Important Note: Through out this document and other Tango

Mobile UC and SIP Trunking combination It is possible to have both

April 2014 CONFIDENTIAL Page 5 of 51

Avaya Communication Server 1000 release 7.5

PBX Dependencies Mobile UC

April 2014 CONFIDENTIAL Page 6 of 51

April 2014 CONFIDENTIAL Page 7 of 51

Accelerator Integration Processes

Mobile UC and PSTN Access Enabled Accelerator

Mobile UC Enabled Accelerator

For references on how to administer these functions see:

April 2014 CONFIDENTIAL Page 8 of 51

CS1000 Provisioning Work Flow for Mobile UC

Avaya Aura Session Manager Provisioning Mobile UC

April 2014 CONFIDENTIAL Page 9 of 51

Avaya CS1000 7.5 Provisioning Mobile UC

Avaya Aura Session Manager Provisioning (AASM)

Configuration is accomplished by accessing the browser-based GUI of the

Figure 1 SMGR Routing Link

April 2014 CONFIDENTIAL Page 10 of 51

Define SIP Domains

Figure 2 SIP Domain Defined - AASM

1. Expand Routing and select Locations from the left menu.

April 2014 CONFIDENTIAL Page 11 of 51

5. Click Commit to save.

Figure 3 below shows the Location defined in this sample configuration.

Figure 3 Location Defined - AASM

Define SIP Entities Accelerator

1. Define the Tango Accelerator SIP Entity by expanding the Routing

April 2014 CONFIDENTIAL Page 12 of 51

6. SIP Link Monitoring Select Use Session Manager Configuration.

Figure 4 Accelerator SIP Entity Defined - AASM

Define SIP Entities Avaya CS1000

April 2014 CONFIDENTIAL Page 13 of 51

Figure 5 Avaya CS1000 SIP Entity Defined - AASM

Define Entity Links

A SIP trunk between the Session Manager and a telephony system is

Define Entity Link CS1000 TCP Entity Link

April 2014 CONFIDENTIAL Page 14 of 51

10. Click Commit to save Entity Link definition.

Figure 6 Entity Link between CS1000 and Session Manager (TCP)

Define Entity Link CS1000 UDP Entity Link

April 2014 CONFIDENTIAL Page 15 of 51

4. Click Commit to save Entity Link definition.

Figure 7 Entity Link between CS1000 and Session Manager (UDP)

Define Entity Link Accelerator TCP Entity Link

April 2014 CONFIDENTIAL Page 16 of 51

5. Click Commit to save Entity Link definition.

Figure 8 Entity Link between Accelerator and Session Manager

Define Entity Link Accelerator UDP Entity Link