Avayapbx Cc 65

7/30/2019 Avayapbx Cc 65

1/80

Apropos

Avaya/Definity PBX

Integration Guide

http://www.apropos.com

[email protected]

[email protected]

Apropos Technology, Inc.

Worldwide Headquarters

North American Sales

One Tower Lane 28th Floor

Oakbrook Terrace, IL 60181

U.S.A.

phone +1.630.472.9600

fax +1.630.472.9745


2/80

2006 Apropos Technology, Inc. APBXIG-6.5-CC-10/06

All rights reserved. This manual may not be reproduced or distributed, in whole or in part, by any means without

the prior written permission of Apropos Technology, Inc., with the following exception. Customers of Apropos

Technology can reproduce this system document for internal use only. Printed in the United States of America.

Apropos Version 6, iVault, and Interaction Vault are trademarks of Apropos Technology, Inc.

All other brand or product names are registered trademarks or trademarks of their respective companies.


3/80

Avaya/Definity PBX Integration Guide APBXIG-6.5-CC i

Table of Contents

OVERVIEW.............................................................................................................................................1

Additional Reference Materials............................................................................................2PIL VOICE PORT CONFIGURATION....................................................................................................3

Lineside T1 Configuration.................................................................................................................3Avaya Hardware Information .....................................................................................................3

Avaya Part Number List.......................................................................................................4Before You Begin the T1 Configuration...............................................................................4Jumper Configuration ..........................................................................................................5Channel Selector .................................................................................................................5Impedance Ohm Setting......................................................................................................5Hardware Installation...........................................................................................................5Connect the T1 Card ...........................................................................................................6T1 Connectivity to a Frame .................................................................................................6

T1 Connectivity to a Frame Diagram...................................................................................7T1 Connectivity Directly to a Server ....................................................................................8T1 Connectivity Directly to a Server Diagram .....................................................................9Configure the T1 Card.......................................................................................................10

Avaya PBX Software Configuration .........................................................................................11Option Determination.........................................................................................................12Option 1: Expert Agent Selection Automatic Call Distribution (EAS ACD) .......................13Option 2: Non-Expert Agent Selection Automatic Call Distribution...................................19Option 3: Hunt Group Without ACD ..................................................................................24

Route Calls to the Apropos Server ..........................................................................................27Configure a VDN ...............................................................................................................28Configure a Vector.............................................................................................................29

Configure Telephony on the Voice Server...............................................................................30Configure the AG-4040 / AG-4000-2T T1 Board...............................................................31Change the TCP Information.............................................................................................31Modify BUS and Slot Information ......................................................................................31Configuration File Changes...............................................................................................31

Apropos Version 6.............................................................................................................31Apropos Version 5.0.2 Windows 2000 ...........................................................................35Apropos Version 5.0.2 Windows NT ..............................................................................37Apropos Version 5.0 and Version 5.0.1.............................................................................39

Values for PIL and SLP Processes..........................................................................................41Version 6 PIL Process.......................................................................................................41Version 6 SLP Process......................................................................................................41Version 5 PIL Process.......................................................................................................42Version 5 SLP Process......................................................................................................42

ACD PIL Login Script Change .................................................................................................42Version 6.5 PIL Script Change ..........................................................................................42Version 6.0.1 PIL Script Change .......................................................................................44

REQUEUE PORT CONFIGURATION..................................................................................................47

Port Pool Manager Modifications.............................................................................................50

FAIL-OVER CONFIGURATION ...........................................................................................................51

Option Determinations .............................................................................................................51


4/80

ii Avaya/Definity PBX Integration Guide APBXIG-6.5-CC

Using Vectors to Define the Fail-Over Configuration ..............................................................52Using Coverage Paths to Define the Fail-Over Configuration................................................. 54

APROPOS AGENT PHONE CONFIGURATION................................................................................. 59

Link Agent Phone Configuration..............................................................................................59Program the Digital Agent Phone .....................................................................................59

Standard Agent Phone Configuration...................................................................................... 61Digital Standard Agent Phone Configuration.................................................................... 61

Analog Standard Agent Phone Configuration................................................................... 61

SWITCH LINK CONFIGURATION....................................................................................................... 63

Install Switch Link Software Avaya S8700/S8500................................................................63Start the Switch Link Process ...........................................................................................63Install and Configure the NetMerge Server.......................................................................64Complete the NetMerge Installation.................................................................................. 66

Install Switch Link Software Avaya DEFINITY ..................................................................... 66Start the Switch Link Process ...........................................................................................66Install and Configure the NetMerge Server.......................................................................67Complete the NetMerge Installation.................................................................................. 69

SLP Parameters ......................................................................................................................69Version 6 SLP Process .....................................................................................................70Version 5 SLP Process .....................................................................................................70

ADDITIONAL NOTES.......................................................................................................................... 71

ANI and DNIS through Switch Link..........................................................................................71Trunk-to-Trunk Transfers......................................................................................................... 71

INDEX................................................................................................................................................... 73


5/80

Avaya/Definity PBX Integration Guide APBXIG-6.5-CC 1

Overview

This document describes the process for integrating Apropos with an Avaya telephony system using

T1 connections. The audience for this document is Apropos System administrators and Avayasystem administrators involved with the installation and on-going operations of this integrated

system. This document assumes that the Avaya telephony system is installed and operational and

the Apropos System software has been installed and configured. Apropos software installation

instructions can be found in theApropos and Third-Party Software Installation Guide.

The focus of this document is the steps required to configure the Avaya PBX from an Apropos

perspective, as well as the steps required to configure Apropos to support the Avaya telephony

system. There are a wide variety of ways both Apropos and Avayas systems can be deployed. This

document does not attempt to cover each possible configuration, but rather to explain the basic

processes and provide direction for integrating the systems using T1 connections. The steps for your

installation may vary slightly depending on your environment.

Normally, the functions of the Apropos System are distributed over several servers for scalabilityand redundancy reasons. In a typical Apropos System, there are the following servers.

One Primary Server, which is also known as the router.

One Database Server.

Possibly an Interaction Server, for e-mail and Web collaboration. This server is occasionally

combined with the Primary Server.

An Interaction Vault Server, for interaction transcript archiving.

A number of Voice Servers, each with up to 120 concurrent sessions to handle voice-processing

tasks such as auto-attendant, IVR, and in-queue voice treatment.

For small systems, under 25 users and 8 current voice sessions, Apropos functionality can be

deployed using a single server. However, in practice, even for small systems, two servers are

typically used, one for the Database and the other for the rest of the Apropos System software.

Apropos voice processing is handled by PIL processes one process for each concurrent voice

session. In multi-site configurations, remote Apropos Voice Servers can be located at each site if

necessary. If there are separate Avaya systems at each site, the remote Apropos Voice Servers can

be configured to use the resources on the local PBX.

For purposes of interfacing Apropos with Avayas telephony system, we are only concerned with

Apropos Servers that are running PIL processes (Voice Servers).

The integration process also includes the configuration of the PIL and the SLP Processes on the

Apropos Server. The values to use are defined in the section Values for PIL and SLP Processes, page

41. The method to manage those server processes is described in theApropos System Manager Help

(Apropos Version 6) or in theApropos Administrator User Guide (Apropos Version 5.x).

The Avaya/Definity PBX Integration Guide has been designed to work in conjunction with the

Apropos Call Processing Installation Guide and will be referenced multiple times throughout this

document. For more information on the AG-4040/AG-4000 T1 cards, see theApropos Call Processing

Installation Guide. For more information on the Apropos software and third-party installations, see

theApropos and Third-Party Software Installation Guide.


6/80

Overview

2 Avaya/Definity PBX Integration Guide APBXIG-6.5-CC

The following are the major steps you must take to configure the Avaya PBX to work with Apropos.

Configure the jumpers on the card

Install and configure the T1 card

Configure the PBX software

Define the call routing method

Create a fail-over environment

Define ports for requeuing

Configure the application link server

The following are the Apropos configuration pieces necessary to integrate with the Avaya PBX.

Configuration of the AG-4040 or AG-4000 T1 boards

PIL process

SLP Process

Additional Reference Materials

The information provided in this document works in conjunction with the information andprocedures in the following documents or Help systems.

Apropos and Third-Party Software Installation Guide

Apropos CallProcessing Installation Guide

The integration of Apropos with Avaya includes the following configurations.

PIL Voice Port Configuration,page3

Requeue Port Configuration,page47

Fail-over Configuration,page 51

Apropos Agent Phone Configuration,page 59

Switch Link Configuration,page62


7/80


PIL Voice Port Configuration

This section describes the various configuration options for the Avaya T1 card. The T1 card is used

in conjunction with the Apropos PIL port application and can be provisioned to utilize three differentconfigurations, depending on your licenses, options, and infrastructure environment.

The integrated system consists of Apropos required hardware and third-party supplied hardware

and software. This section provides a description of the Apropos hardware and the part numbers of

the Avaya hardware that were used and tested during this system integration.

The physical connection from the Avaya PBX is terminated to an AG-4040 or AG-4000 card within

the Apropos Voice. Appropriate cabling and connectivity is outlined in this document.

Lineside T1 Configuration

Once you install the Avaya T1 card in the Avaya PBX, you must properly configure the card.

For a more detailed description of Avaya hardware and software setup, refer to the appropriateAvaya documentation.

Avaya Hardware Information

All references to a specific Avaya part number indicate which part numbers were tested and verified

for this integration process.

Specific Avaya part numbers are determined by the type of Avaya PBX at your site.

Contact your Avaya sales representative for confirmation of your site needs.

Although other hardware may satisfy your integration requirements, this document

restricts the discussion to the part numbers listed in theAvaya Part Number List section.

The Apropos Voice Server can be configured to integrate with an Avaya PBX using a TN464 T1 card.

Installation of the Avaya T1 card requires hardware setup and software configuration of the Avaya

PBX. There are multiple versions of the Avaya TN464 T1 card that can be used.

This document discusses how to configure the T1 hardware and PBX software properly to work with

the Apropos software. The steps for your installation may vary slightly depending on your

environment. For a more detailed description of the Avaya hardware and software setup, see the

appropriate Avaya documentation.

The T1 card interfaces with the Apropos AG-4040 or the AG-4000 T1 card using a single cable. This

type of integration provides the following advantages.

The installation time is reduced due to the reduction of the physical wiring required. Non-T1installations require a dedicated wire pair for each of the 24 lines to the PBX. For the T1

integration, a single cable using two wire pairs is necessary.

The interface is a true digital integration.


8/80



Avaya Part Number List

The following is a list of the part numbers for the Avaya hardware referred to in this document.

Although other Avaya hardware may provide the equivalent functionality, the list oftested Avaya

hardware is provided as a reference. For a more detailed description of Avaya hardware available,

see the appropriate Avaya documentation or contact your Avaya sales representative.

Hardware Type Avaya Model or Part Number

PBX DEFINITY

(or)

S8700 / S8500

T1 Card TN464

where is the version

Cable 601317191

RJ-48 to DB-15 Converter Vendor of your choice

(or)

Black Box Company, part number FA060

Before You Begin the T1 Configuration

The version of the TN464 T1 card determines whether you must configure two jumpers on the card.

Use the following information to determine the next step in your integration.

Version Action

C or D Set the jumpers as described in the Jumper Configuration section, page 5.

F Skip the Jumper Configuration section and continue the installation as described in the

Hardware Installation section, page 5.


9/80



Jumper Configuration

When TN464C or TN464D vintage cards are used, two jumpers on the T1 card must be configured.

These jumpers are not present on the TN464F card. If you have a TN464F card, skip this section

and continue with the Hardware Installation section, page 5.

Proper jumper settings are crucial to the functionality and success of integration between the PBXand Apropos Server. The descriptions of jumper functionality and requirements follow. Some of

these settings may vary due to your specific PBX environment.

The jumpers are on the lower left quadrant of the board when looking at it with the faceplate on the

right.

Backplane

Connectors

Faceplate

24 / 32 channel selector

75 / 120 ohm selector

Vintage T1 Card

Channel Selector

This jumper setting determines the appropriate number of channels used for an application and

controls the bit rate. For United States applications, select 24 channels. For Non-United States

applications, select 32 channels.

Impedance Ohm Setting

This jumper determines the impedance of the cable for the T1 interface. For United States and

Non-United States applications, select the 120-ohm setting.

Hardware Installation

The Lineside T1 card must be installed into the appropriate Avaya PBX slot. The TN464F T1 cardprovides an interface to an external DS1 interface and supports 24 DS0 channels carried on a 1.544

Mbps DS1 link. These DS0 channels can be administered as either trunks to other switches or lines

to off-premise stations.


10/80



Connect the T1 Card

The Lineside T1 Card in the Avaya PBX is connected with a cable to the AG-4040/AG-4000 T1 card

in the Apropos Server. Two wiring configurations are described in this section.

T1 Connectivity to a FrameThe first wiring configuration connects the Avaya PBX, using an Amphenol cable, to a 66-block or a

110-block to split out the appropriate pairs. The Amphenol cable consists of the following endpoints.

The 25-pair Amphenol connector, which plugs into the I/O panel of the PBX

The terminating point which consists of one of the following

An RJ-48 connector

A connection to the 66-block or 110-block wiring frame

Avaya PBX T1 signaling for all 24 channels is transmitted using the Amphenol connector pins 22,

23, 47, and 48. This cable can be connected to a frame to split out the needed pairs. This

connectivity can also be achieved by terminating the other end of the Amphenol cable to an RJ-48

connector using the appropriate pairs.

When an RJ-48 connector is used, the following is the required pin connection order.

Amphenol connector RJ-48 connector

Pin 22 LI (RX) Pin 4 R1 Transmit to Network

Pin 23 LO (TX) Pin 1 R Receive from Network

Pin 47 LI (RX) Pin 5 T1 Transmit to Network

Pin 48 LO (TX) Pin 2 T Receive from Network


11/80



T1 Connectivity to a Frame Diagram

The following diagram shows the Avaya PBX connected to a 66-block wiring frame, which is

connected to an Apropos Server using an RJ-48 jack connector.

Amphenol

Avaya

PBXRJ-48

Jack

Apropos

Server

AG-4040

Pin 22

Pin 23

Pin 47

Pin 48

Pin 4

Pin 1

Pin 5

Pin 2

66-Block Frame

T1 Card

T1 Connectivity Directly to a Server diagram


12/80



T1 Connectivity Directly to a Server

The other wiring configuration uses a direct connection from the Avaya PBX, using the Avaya cable,

to the Apropos Server. The Avaya cable consists of the following end connectors.

A 25-pair Amphenol connector, which plugs into the I/O panel of the PBX

A male DB-15 connector

A DB-15 to RJ-48 converter is used to connect the DB-15 male connector of the Avaya cable to the

Apropos Server, using a straight-through RJ-48 to RJ-48 cable. This converter can be obtained from

a vendor of your choice or from the Black Box Company, see http://www.blackbox.com, using part

number FA060.

The RJ-48 to DB-15 converter must be configured with the following pins connected.

DB-15 Female connector RJ-48 Jack Connector

Hole location 1 Pin 2




The following diagram shows the DB-15 to RJ-48 converter pin configuration.

Pins1

9

3

11

1

15

1 8

9

3

DB-15 FemaleConnector

RJ-48 Jack

11

Pins1

2

3

4

5

6

7

8

DB-15 to RJ-48 Converter diagram


13/80



T1 Connectivity Directly to a Server Diagram

The following diagram shows the Avaya PBX connection directly to the server. The T1 signaling for

all 24 channels is transmitted using the DB-15 male connector of the Avaya cable. T1 transmit and

receive pairs must be connected between the T1 Card and the Apropos equipment.

The following is the sequence of the connections.

Plug the DB-15 male connector into the DB-15 to RJ-48 converter.

To the DB-15 to RJ-48 converter, connect one end of the straight-through cable with RJ-48

connectors.

Connect the other end of the straight-through cable with RJ-48 connectors to the Apropos Server.

DB-15 to RJ-

48 Converter

Avaya

PBX

Avaya cable,

art # 601317191Straight-through cablewith RJ-48 to RJ-48

Connectors

Apropos

Server

T1 Card

AG-4040

T1 Connectivity Directly to a Server diagram


14/80



Configure the T1 Card

Once the T1 card has been installed into the PBX and all appropriate cabling has been connected,

you are ready to configure the T1 card. You must know the cabinet and slot location of the T1 card

in your PBX. This example uses 01B10 (Cabinet 01, Carrier B, and Slot 10).

To configure your T1 card, perform the following steps.1. Log in to your PBX, if you are not already logged in.

2. At the Command prompt line, enter the following command.

add ds1

Where is the value of the T1 card in your PBX. This example uses 01B10.

3. Press Enter. The DS1 Circuit Pack window displays.

4. Enter the appropriate information in the following fields. The following shows the required

Apropos values to use for this PBX type.

Name - Enter a descriptive name. This example usesApropos T1.

Bit Rate - Enter 1.544.

Line Coding - Enter b8zs.

Framing Mode - Enter esf.

Signaling Mode - Enter robbed-bit.

Accept the defaults for all other fields not specifically mentioned.

5. Press Enter to apply changes and return to the Command prompt line.

This completes the configuration for the T1 card. Continue with theAvaya PBX Software

Configuration section, section, page 11 to continue the integration process.

add ds1 01b10 Page 1 - 2DS1 CIRCUIT PACK

Location: 01B10 Name: Apropos T1

Bit Rate: 1.544 Line Coding: b8zsLine Compensation: 1 Framing Mode: esfSignaling Mode: robbed-bit

Interface Companding: mulawIdle Code: 11111111

Slip Detection? n Near-end CSU Type: other

Echo Cancellation? n

ESF DATA LINK OPTIONS

Network Management Protocol: tabsSend ANSI-T1.403 One-Second Performance Reports? n

Far-end CSU Address: b


15/80



Avaya PBX Software Configuration

This section covers the integration of Apropos software to the Avaya PBX hardware and the system

software. Throughout this section, we reference parameters that must be set to a specific value.

These parameters are determined by setting specific values in the appropriate fields. Some fields

may be site specific and are not required by the Apropos integration. Only parameters and the

corresponding fields that apply to the required Apropos settings are addressed here. Any additional

fields not specifically mentioned in this document remain at the default values. Additionally, as

other releases of Avaya system software become available, you may notice additional fields while

configuring your Avaya equipment.

The Avaya DEFINITY PBX specifically uses the G3 software for the system integration. However,

the MultiVantage software for the system integration runs on a variety of Avaya hardware, such as

the S8700 and the DEFINITY servers.

MultiVantage is the centerpiece of Avaya Next Generation Enterprise Class IP Solutions (ECLIPS).

This architecture is typically used in a converged voice and data network and can add IP telephony

capability.

Additionally, it provides control to Avaya Media Gateways and Avaya Communications Devices.

Avaya MultiVantage evolved from the DEFINITY software, therefore this guide can be used toconfigure either PBX model to integrate with the Apropos System.

Based on testing results, the information listed in the table below will provide the appropriate

versions of software packages to be used based on the version of Apropos software and Avaya System

software.

Apropos Version

5.0.2-SP3

Apropos Version

6.0

Apropos Version

6.0.1

Apropos Version

6.0.1-SP2

Apropos Version

6.5 and Above

Avaya System

Software

Release10 and

Below

CTC v5 Server

CTC v5 Client

CTC v5 Server

CTC v5 Client

NetMerge v6

Server

CTC v5 Client

NetMerge v6

Server

NetMerge v6

Client

NetMerge v6

Server

NetMerge v6

Client

Avaya System

Software

Release11 and

Above

NetMerge v6

Server

CTC v5 Client

NetMerge v6

Server

CTC v5 Client

NetMerge v6

Server

CTC v5 Client

NetMerge v6

Server

NetMerge v6

Client

NetMerge v6

Server

NetMerge v6

Client


16/80



Option Determination

Several configuration options are available for your Avaya PBX. The options purchased for your

Avaya PBX determine which types of configuration options are available to you. The Apropos

recommended software configuration option for a T1 integration is the Expert Agent Selection (EAS)

option. Although the EAS option does not come with the base software package, it can be purchased

and installed. All Avaya PBXs have Hunt Group without ACD as part of the standard package.

Perform the following steps to configure the PBX software.

1. Determine the correct configuration option to use,page 12.

2. Perform the appropriate configuration option. The following are the available configuration

options.

Expert Agent Selection Automatic Call Distribution (EAS ACD),page 13.

Non-EAS ACD,page 19.

Hunt Group without ACD (default),page 24.

3. Configure the Apropos Agent Phone,page 59

Determine Optional Features Available

The first step is to determine the appropriate integration for your environment. To determine

whether your Avaya PBX has one or all of the software configurations previously listed, perform the

following the steps.

1. Log in to your PBX, if you are not already logged in.


display system-parameters customer-options

3. Press Enter. The Call Center Optional Features window displays.

display system-parameters customer-options Page 6 of 11

CALL CENTER OPTIONAL FEATURES

Call Center Release: 12.0

ACD? y PASTE (Display PBX Data on Phone)? yBCMS (Basic)? y Reason Codes? y

BCMS/VuStats Service Level? y Service Level Maximizer? yBSR Local Treatment for IP & ISDN? y Service Observing (Basic)? y

Business Advocate? n Service Observing (Remote/By FAC)? yCall Work Codes? y Service Observing (VDNs)? y

DTMF Feedback Signals For VRU? y Timed ACW? yDynamic Advocate? n Vectoring (Basic)? y

Expert Agent Selection (EAS)? y Vectoring (Prompting)? yEAS-PHD? y Vectoring (G3V4 Enhanced)? y

Forced ACD Calls? n Vectoring (ANI/II-Digits Routing)? yLeast Occupied Agent? y Vectoring (G3V4 Advanced Routing)? y

Lookahead Interflow (LAI)? n Vectoring (CINFO)? yMultiple Call Handling (On Request)? y Vectoring (Best Service Routing)? y

Multiple Call Handling (Forced)? y Vectoring (Holidays)? yVectoring (Variables)? y

(NOTE: You must logoff & login to effect the permission changes.)


17/80



Determine the Correct Configuration Option to Use

On the Call Center Optional Features window, review the responses in the following fields to

determine the configuration options available.

When Expert Agent Selection (EAS) is y, use the EAS ACD option,page 13.

WhenACD is y, use the Non-EAS ACD option,page 19.

WhenACD is n and Expert Agent Selection (EAS) is n, use the Hunt Group without ACD

option,page 24.

Determine Whether Vectoring is Available to Use

On the Call Center Optional Features window, when the response toVectoring (Basic) is y, your

Avaya PBX has been equipped with Call Vectoring. This information is used with any integration

type.

Option 1: Expert Agent Selection Automatic Call Distribution (EAS ACD)

The following three steps are required to complete this integration method.

1. Define an EAS ACD Hunt Group.2. Configure the station values for each PIL port.

3. Configure the EAS Agent Login ID.

Values used in examples

For this integration method, the following values are used in the examples.

Agent Login ID - 5101 through 5124

Group Extension - 5800

Hunt Group - 6

Re-direct to VDN - 6000

Station Numbers - 5601 through 5624

All integrations utilizing Apropos 5.x and below require the AAS (Auto Login) parameter to

be set to y (Yes). Due to enhancements of Apropos release 6.x and above, the value AAS

must be set to n (No).

Also, for Apropos version 6.x and above users, a PIL script change is required for the

completion of the PIL EAS ACD integration. Specific areas of change are noted in the

examples shown in this section.


18/80



Define an EAS ACD Hunt Group

The first step in this configuration method is to define an EAS ACD Hunt Group. This hunt group

contains all of the PIL port stations as members of the group. Multiple parameters need to be

configured to provide a successful integration. The parameters listed below provide the required

Apropos values.

To configure an EAS ACD Hunt Group, perform the following steps.



add hunt-group

Where is the value of the unassigned hunt group numbers. This example uses 6.

3. Press Enter. The Hunt Group window displays.

display hunt-group 6 Page 1 of 3HUNT GROUP

Group Number: 6 ACD? y

Group Name: Apropos T1 PIL Ports Queue? yGroup Extension: 5800 Vector? yGroup Type: ead-mia

TN: 1COR: 1 MM Early Answer? n

Security Code:ISDN Caller Display:

Queue Length: 24Calls Warning Threshold: Port:Time Warning Threshold: Port:

Skill? y Expected Call Handling Time (sec): 180AAS? n Service Level Target (% in sec): 80 in 20

Measured: internalSupervisor Extension:

Controlling Adjunct: none

VuStats Objective:Timed ACW Interval (sec):Multiple Call Handling: none

Redirect on No Answer (rings): 3Redirect to VDN: 6000

Forced Entry of Stroke Counts or Call Work Codes? n

Message Center: none

LWC Reception: noneAUDIX Name:


19/80





ACD - Enter y.

Group Name - Enter a descriptive name. This example usesApropos T1 PIL Ports.

Queue - Enter y.

Group Extension - This is a valid, unassigned PBX extension. When your Avaya PBX has

been equipped with Call Vectoring, this value may be an extension number. If you do not

have the Call Vectoring option, this value must be a valid Direct Inward Dialing (DID)

number. This example uses 5800.

Vector - Enter y, if the vectoring option has been purchased.

GroupType - Enter ead-mia.

COR - Enter the appropriate Class of Restriction (COR) level for your environment. This

example uses 1.

QueueLength - Enter a number equal to the number of PIL ports used. This example

uses 24.

Skill - Enter y.

AAS - Enter n. This option allows the Apropos PIL ports to log in at startup automatically.

All integrations utilizing Apropos 5.x and below require the AAS (Auto Login)

parameter to be set to y (Yes). Due to enhancements of Apropos release 6.x and

above, the value AAS must be set to n (No).

Measured - This value is determined by your system environment.

If your PBX is equipped with Basic Call Management System (BCMS), enter internal.

If your system is equipped with Call Management System (CMS), enter external or

both.

Redirect on No Answer (rings) - This parameter dictates the number of rings that a callwill be presented to a PIL port before a No Answer condition is recognized. This example

uses 3 rings.

Redirect to VDN - This is a valid Vector Directory Number (VDN) used in conjunction

with the Redirect on No Answer (rings) parameter. Enter a value that represents an

available ACD group or attendant that is available to answer calls in the event of an Apropos

Server failure. This example uses 6000.

Accept the default values for all other fields not specifically mentioned, unless your specific

environment requires otherwise.

Use the appropriate key, as defined by your site, to apply the changes and return to the

Command prompt line.


20/80



Configure the Station Values for Each PIL Port

The next step in this integration is to configure the station values for each PIL port. You must have

a valid range of unassigned PBX extension numbers to complete this step. This section must be

repeated for all PIL ports.

To configure the PIL ports, perform the following steps.


add station

Where is a valid, unassigned PBX extension. This example uses 5601.

2. Press Enter. The Station window displays.

add station 5601 Page 1 - 3STATION

Extension: 5601 Lock Messages? n BCC: 0Type: DS1FD Security Code: TN: 1Port: 01B1001 Coverage Path 1: COR: 1Name: T1 PIL-1 Coverage Path 2: COS: 1

Hunt-to Station: 5602 Tests? y

STATION OPTIONSLoss Group: 4

Off Premises Station? yR Balance Network? n

FEATURE OPTIONSLWC Reception: noneLWC Activation? n Coverage Msg Retrieval? y

LWC Log External Calls? n Auto Answer: noneCDR Privacy? n Data Restriction? n

Redirect Notification? n Call Waiting Indication? yPer Button Ring Control? n Att. Call Waiting Indication? y

Distinctive Audible Alert? ySwitchhook Flash? y Adjunct Supervision? y

Ignore Rotary Digits? nH.320 Conversion? n Per Station CPN - Send Calling Number?

Service Link Mode: as-neededMultimedia Mode: basic Audible Message Waiting? n

AUDIX Name:Coverage After Forwarding? sMultimedia Early Answer? n

Emergency Location Ext: 5601

SITE DATARoom: Headset? nJack: Speaker? nCable: Mounting: dFloor: Cord Length: 0

Building: Set Color:

ABBREVIATED DIALINGList1: List2: List3:

HOT LINE DESTINATIONAbbreviated Dialing List Number (From above 1, 2 or 3):

Dial Code:Line Appearance: call-appr


21/80





Type - Enter DS1FD.

Port - Enter the appropriate card and port number. This example uses 01B1001 (Cabinet

01, Carrier B, Slot 10, and Port 01).

COR - Enter the appropriate Class of Restriction for your environment. This example uses1.

Name - Enter a descriptive name. This example uses T1 PIL-1.

COS - Enter the appropriate Class of Service for your environment. This example uses 1.



4. Repeat this procedure for all remaining PIL ports. This example uses 5602 through 5624.


22/80



Configure the EAS Agent Login ID

The final step in this integration is to configure the EAS Agent Login ID. You must have a valid

range of unassigned PBX extension numbers to complete this step. Add one Agent ID for each PIL

port installed on the Apropos Server.

To configure the Agent Login IDs, perform the following steps.


add agent-loginID


2. Press Enter. The Agent LoginID window displays.

add agent-loginID 5101 Page 1 - 2AGENT LOGINID

Login ID: 5101 AAS? nName: Apropos PIL Port 1 AUDIX? nTN: 1 LWC Reception: none

COR: 1 LWC Log External Calls? nCoverage Path: AUDIX Name for Messaging:Security Code:

LoginID for ISDN Display? nPassword:

Password (enter again):Auto Answer: none

Direct Agent Skill:Call Handling Preference: skill-level

SN SL SN SL SN SL SN SL1: 6 1 16: 31: 46:2: 17: 32: 47:3: 18: 33: 48:4: 19: 34: 49:5: 20: 35: 50:6: 21: 36: 51:

7: 22: 37: 52:8: 23: 38: 53:9: 24: 39: 54:10: 25: 40: 55:11: 26: 41: 56:12: 27: 42: 57:13: 28: 43: 58:14: 29: 44: 59:15: 30: 45: 60:


23/80





AAS - Enter n. This option allows the Apropos PIL ports to log in at startup automatically.

All integrations utilizing Apropos 5.x and below require the AAS (Auto Login)

parameter to be set to y (Yes). Due to enhancements of Apropos release 6.x andabove, the value AAS must be set to n (No).

Name - Enter a descriptive name. This example usesApropos PIL Port 1.

AUDIX - Enter n.

LWC Reception - Enter none.

COR - Enter the appropriate Class of Restriction for your environment. This example uses

1.

Auto Answer - Enter none.

SN - The Skill Number is the Hunt Group number assigned in theDefine an EAS ACD

Hung Group section, page 16. This example uses 6.

SL - Enter 1.




This portion of the integration is now complete. Continue with theApropos Agent Phone

Configuration section, page 59to continue the integration process.

Option 2: Non-Expert Agent Selection Automatic Call Distribution

This configuration utilizes a hunt group with ACD for all of the Apropos PIL ports. You must have a

valid range of unassigned PBX extension numbers to complete this step. The following two steps arerequired to complete this integration method.

1. Configure each Apropos PIL port.

2. Define the Non-EAS ACD Hunt Group.

Values Used in Examples



Hunt Group - 5

Re-direct to VDN - 6000



24/80



Configure Each Apropos PIL Port

The first step in this configuration method is to configure each Apropos PIL port. This hunt group

contains all of the PIL port stations as members of the group. Multiple parameters need to be

configured to provide a successful integration. The parameters listed below provide the required

Apropos values.

To configure each Apropos PIL port, perform the following steps.



add station

Where is the value of the valid, unassigned PBX extension. This example uses 5649.



Extension: 5649 Lock Messages? n BCC: 0

Type: DS1FD Security Code: TN: 1Port: 01B1101 Coverage Path 1: 11 COR: 1Name: T1 PIL-1 Coverage Path 2: COS: 1








Ignore Rotary Digits? n Per Station CPN - Send Calling Number?H.320 Conversion? nService Link Mode: as-neededMultimedia Mode: basic Audible Message Waiting? n





ABBREVIATED DIALINGList1: List2: List3:

HOT LINE DESTINATIONAbbreviated Dialing List Number (From above 1, 2 or 3):


25/80





Type - Enter DS1FD.



COR - Enter a Class of Restriction for your environment. This example uses 1.


COS - Enter an appropriate Class of Service. This example uses 1.

Coverage Path 1 Enter an unused Coverage Path number. This coverage path will be used

later for your Fail-Over environment. This example uses 11.




Define the Non-EAS ACD Hunt Group

The next step in this configuration method is to define a non-EAS ACD Hunt Group. This hunt

group contains all of the PIL port stations as members of the group. Multiple parameters need to beconfigured to provide a successful integration. The parameters listed below provide the required

Apropos values.

To configure a non-EAS ACD Hunt Group, perform the following steps.



add hunt-group

Where is the value of the unassigned hunt group numbers. This example uses 5.


26/80



3. Press Enter. The Hunt Group window displays.

add hunt-group 5 Page 1 - 61HUNT GROUP

Group Number: 5 ACD? yGroup Name: Non-EAS T1 Hunt Queue? y

Group Extension: 5700 Vector? yGroup Type: ucd-mia

TN: 1COR: 1 MM Early Answer? n

Security Code:ISDN Caller Display:

Queue Length: 24Calls Warning Threshold: Port:Time Warning Threshold: Port:

Skill? n Expected Call Handling Time (sec): 180AAS? y

Measured: noneSupervisor Extension:

Controlling Adjunct: none

Timed ACW Interval (sec):Multiple Call Handling: none

Redirect on No Answer (rings): 3Redirect to VDN: 6000

Forced Entry of Stroke Counts or Call Work Codes? n

Message Center: none

LWC Reception: noneAUDIX Name:

Group Number: 5 Group Extension: 5700 Group Type: ucd-mia

Member Range Allowed: 1 - 1500 Administered Members (min/max): 1 /24Total Administered Members: 24

GROUP MEMBER ASSIGNMENTSExt Name (24 characters) Ext Name (24 characters)

1: 5649 PIL 1 14: 5662 PIL 142: 5650 PIL 2 15: 5663 PIL 153: 5651 PIL 3 16: 5664 PIL 164: 5652 PIL 4 17: 5665 PIL 175: 5653 PIL 5 18: 5666 PIL 186: 5654 PIL 6 19: 5667 PIL 197: 5655 PIL 7 20: 5668 PIL 20


27/80





ACD - Enter y.

Group Name - Enter a descriptive name. This example uses Non-EAS T1 Hunt.

Queue - Enter y.

Group Extension - This is a valid, unassigned PBX extension. When your Avaya PBX has

been equipped with Call Vectoring, this value may be an extension number. If you do not



Vector - Enter y, if the vectoring option has been purchased.

GroupType - Enter ucd-mia.


example uses 1.

QueueLength - Enter a number equal to the number of PIL ports used. This example

uses 24.

Skill - Enter n.

AAS - Enter y. This option allows the Apropos PIL ports to log in at startup automatically.


If your PBX is equipped with BCMS, enter internal.

If your system is equipped with CMS, enter external or both.

Redirect on No Answer (rings) - This parameter dictates the number of rings that a call

will be presented to a PIL port before a No Answer condition is recognized. This example

uses 3.

Redirect to VDN - This is a valid Vector Directory Number (VDN) used in conjunction

with the Redirect on No Answer (rings) parameter. Enter a value that represents an

available ACD group or attendant that is available to answer calls in the event of an Apropos

Server failure. This example uses 6000. Group Member Assignments - Enter all of the station ports that were configured in the

Configure Each Apropos PIL Port section, page 20.




Configuration section, page 59, to continue the integration process.


28/80



Option 3: Hunt Group Without ACD

This configuration utilizes a hunt group without ACD for all of the Apropos PIL ports. The following

two steps are required to complete this integration method.

1. Configure the station values for each PIL port.

2. Define the hunt group.

Values Used in Examples



Hunt Group - 7


Configure the Station Values for Each PIL Port

The first step in this integration method configures the station values for each Apropos PIL port.

You must have a valid range of unassigned PBX extension numbers to complete this step. Thissection must be repeated for all PIL ports.

To configure the PIL ports, perform the following steps.



add station



29/80






Type - Enter DS1FD.



COR - Enter the appropriate Class of Restriction for your environment. This example uses

1.


COS - Enter the appropriate Class of Service for your environment.

Coverage Path 1 Enter an unused Coverage Path number. This coverage path will be used

later for your Fail-Over environment. This example uses 11.





Extension: 5649 Lock Messages? n BCC: 0Type: DS1FD Security Code: TN: 1Port: 01B1101 Coverage Path 1: 11 COR: 1Name: T1 PIL-1 Coverage Path 2: COS: 1








Ignore Rotary Digits? n Per Station CPN - Send Calling Number?H.320 Conversion? n

Service Link Mode: as-neededMultimedia Mode: basic Audible Message Waiting? n






30/80


31/80





ACD - Enter n.

Group Name - Enter a descriptive name. This example uses T1 Hunt Group.

Queue - Enter n.

Group Extension - This is a valid, unassigned PBX extension. When your Avaya PBX hasbeen equipped with Call Vectoring, this value may be an extension number. If you do not



Vector - Enter n.

GroupType - Enter ucd-mia.


example uses 1.

Group Member Assignments - Enter all of the station ports that were configured in the

Configure Each Apropos PIL Port section, page 20.

Accept the default values for all other fields not specifically mentioned, unless your specificenvironment requires otherwise.


Configuration section, page 59, to continue the integration process.

Route Calls to the Apropos Server

The Avaya PBX has the capability of routing calls to the Apropos Server in any of the following

ways.

Use Dialed Number Information Service (DNIS) to route to a Vector Directory Number (VDN).

This is the recommended method.

Use Dialed Number Information Service to route to a hunt group extension. Use Direct Inward Dialing (DID) to a VDN.

Use Direct Inward Dialing to a hunt group extension.

Use Auto-Attendant routing to a VDN or hunt group extension.

To use the recommended routing method, you must configure at least one VDN and one vector. Each

VDN within the Avaya PBX is associated with one vector number.

This section defines the steps to configure a VDN and vector to route calls to the Apropos Server. To

complete this configuration, perform the following two steps.

1. Configure the Vector Directory Number.

2. Configure the vector.


32/80



Configure a VDN

You must have a valid, unassigned PBX extension number to complete this step.

To configure the VDN, perform the following steps.

1. Log in to your Avaya PBX, if you are not already logged in.


add vdn


3. Press Enter. The Vector Directory Numberwindow displays.



Name - Enter a descriptive name. This example usesApropos Server 800-555-5555.

COR - Enter a Class of Restriction (COR) for your environment. This example uses 1.

Vector Number - This is an unassigned PBX Vector number. This example uses 1.


If your PBX is equipped with BCMS, enter internal.

If your system is equipped with CMS, enter external or both.



add vdn 6800 Page 1 - 2VECTOR DIRECTORY NUMBER

Extension: 6800Name: Apropos Server 800-555-5555

Vector Number: 1Attendant Vectoring? n

Meet-me Conferencing? nAllow VDN Override? n

COR: 1TN: 1

Measured: internal

VDN of Origin Annc. Extension:1st Skill:2nd Skill:3rd Skill:

AUDIX Name:

Return Destination:VDN Timed ACW Interval:

BSR Available Agent Strategy: 1st-found

Observe on Agent Answer? n

Display VDN for Route-To DAC? nVDN Override for ISDN Trunk ASAI Messages? n


33/80



Configure a Vector

Each vector in the Avaya PBX is comprised of a series of vector steps. Each step represents a

command to define the process used to handle calls. Vectors may have from 1 to 32 steps.

This section provides an example of the minimum instructions necessary to route calls to the

Apropos Server.

The following example does not address any instructions necessary for a server failure.

Those instructions are shown in the Fail-Over Configuration section, page 51, for more

information.

To configure the vector, perform the following steps.

1. Log in to your Avaya PBX, if you are not already logged in.


add vector

Where is a valid, unassigned PBX vectornumber. This example uses 1.

3. Press Enter. The Call Vector window displays.

add vector 1 Page 1 - 3CALL VECTOR

Number: 1 Name: Apropos ServerMultimedia? n Attendant Vectoring? n Meet-me Conf? n Lock? n

Basic? y EAS? y G3V4 Enhanced? y ANI/II-Digits? y ASAI Routing? yPrompting? y LAI? n G3V4 Adv Route? y CINFO? y BSR? y Holidays? yVariables? Y

01 wait-time 4 secs hearing ringback02 queue-to skill 6 pri h03 wait-time 20 secs hearing ringback04 announcement 546605 goto step 3 if unconditionally06 stop070809101112...303132


34/80





Name - Enter a descriptive name. This example usesApropos Server.

Steps - This section allows you to define the step-by-step process of handling calls. Each

line provides an instruction to the PBX. This example uses the following instructions to

route the calls. The values to enter are indicated in bold. Line 01 - wait-time4 secs hearing ringback. This instruction states that the Apropos

PIL port waits for 4 seconds for clean up between calls, and that ringback is the tone

heard by the caller.

Line 02 - queue-to skill 6 pri m. This is the EAS Skill Group to which calls are

queued. The following values entered are determined by the configuration option chosen.

Enter 6 for the EAS ACD option.

Enter 5 for the Non-EAS ACD option.

Enter 7 for the Hunt Group without ACD option.

After entering one of these options, enter m for the priority.

Line 03 - wait-time 20 secs hearing music. This instruction states that while the call

is queued, the caller hears music play for 20 seconds.

Line 04 - announcement 5466. This instruction provides the caller with a recorded

announcement identified as routing value 5466, in this case the caller hears theAll

agents are currently busy announcement.

Line 05 - goto step 3 ifunconditionally. This instruction keeps the call queued until

it is answered. The instructions in lines 03 through 05, are repeated unconditionally

until the call is answered or the caller disconnects.

Line 06 - stop. This command ends the subroutine after the call is answered or the

caller disconnects.

Configure Telephony on the Voice Server

The integration process includes the configuration of several items on the Apropos Server. These

items are referenced in this section and discussed in detail in the applicable Apropos documentation.

Configure the AG-4040 / AG-4000-2T T1 Board,page 31

Change the TCP Information,page 31

Modify BUS and Slot information,page 31

Configuration File Changes,page 31

Apropos Version 6,page 31

Apropos Version 5.0.2 Windows 2000,page 35

Apropos Version 5.0.2 Windows NT,page 37

Apropos Version 5.0 and Version 5.0.1,page 39

Each PBX integration type can include variations from system defaults. The following items are

impacted for this integration.

AG-4040 / AG-4000-2T T1 Board Configuration

PIL process


35/80



Configure the AG-4040 / AG-4000-2T T1 Board

This section defines the configuration procedures for the AG-4040 / AG-4000 T1 board. Follow the

instructions in the Call Processing Installation Guide, with the following exceptions. These

exceptions apply specifically to the Avaya T1 integration.

Change the TCP InformationYou must change the TCP information to reflect the correct protocols. To select the protocols,

uncomment the following lines in the ag.cfgfile.

For Windows 2000 and 2003 Operating Systems

TCP = ops0.tcp # Off-Premises Station trunk control program

TCP = nocc.tcp # NO Call Control protocol always downloaded for debugging purposes

For Windows NT Operating Systems

TCP = lps0.tcp # Digital Loop Start OPS-FX protocol

TCP = nocc.tcp # NO Call Control protocol always downloaded for debugging purposes

Modify BUS and Slot Information

Modify the PCIBUS and PCISLOT fields from the pciscan (Windows NT, 2003 and 2000) or

blocate (Windows NT only) utility information.

Configuration File Changes

Modifications to the configuration file parameters are specific to the Apropos server versions. Please

see the appropriate section, as it applies to your site.

Apropos Version 6,page 31

Apropos Version 5.0.2 Windows 2000,page 35

Apropos Version 5.0.2 Windows NT,page 36

Apropos Version 5.0 and Version 5.0.1,page 39

Apropos Version 6

The values outlined below are specific to an Avaya Definity PBX utilizing Lineside T1s integrating

to Apropos Version 6 Servers. The two files that must be modified for Apropos v6 integrations are

the oamsys.cfgand the ag.cfg. Changes to the cta.cfgfile are not required for this integration.

The values in the following table apply to the AG 4040 and AG4000 2-T1 boards.

ag.cfg File Parameters

Fields to Modify Value to Use

TCP / Windows 2000 ops0.tcp

TCP / Windows 2000 nocc.tcp

Idle Code For U.S. Integrations: MU-LAW

Idle Code For Non-U.S. Integrations: A-LAW

Clock Source NETWORK

Frame Type ESF

Line Code B8ZS


36/80



Sample oamsys.cfg File

Modify your oamsys.cfg file to look like the following sample. This is a single board configuration

sample. If you are using a multiple-board system, you must uncomment additional board sections.

Note specific areas where changes are made.

Determine Bus and Slot Information

At a DOS prompt on your voice server, type the following command.

pciscan

A window will display with the bus and slot information for AG4040 / AG-4000 T1 card. This

information must be added to the oamsys.cfgfile.

Using any text editor, modify the oamsys.cfgfile. Once modified, the file should look similar to the

following. Specific settings that must be changed are bold and called out with boxed text.

#-------------------------------------------------------# aprs_sample_ag4000_t1_oamsys.cfg## This is a sample OAM system configuration file used by the oamsys tool. It describes# all the NMS boards in a chassis.

## Each board is has its own section in this file. Each is delimited by a user-defined# board name in square brackets. All board names and numbers must be unique.## You will need to modify the bus and slot numbers for each board to match your chassis# configuration. You may also need to add more board sections if you have more boards in your chassis.#----------------------------------------------

[Supervisor]AutoStartEnabled=YesAutoStopEnabled=Yes

#-------------------------------------------------# Uncomment the following section to boot board #0 # Also correctly set the appropriate Bus/Slot info#-------------------------------------------------

[Board0]Product = AG_4000_T1

AutoStart = YesAutoStop = YesNumber = 0Bus = XXSlot = YYFile = ag.cfg

#-------------------------------------------------# Uncomment the following section to boot board #1 # Also correctly set the appropriate Bus/Slot info#-------------------------------------------------

#[Board1]# Product = AG_4000_T1# AutoStart = Yes# AutoStop = Yes# Number = 1# Bus = XX# Slot = YY# File = aprs_ag4000_ag.cfg

#-------------------------------------------------

Enter the appropriateBusandSlotinformation you receivedfrom runningpciscan.

Enter theFilename for yourag.cfg file.


37/80



# Uncomment the following section to boot board #2# Also correctly set the appropriate Bus/Slot info#-------------------------------------------------

#[Board2]# Product = AG_4000_T1# AutoStart = Yes

# AutoStop = Yes# Number = 2# Bus = XX# Slot = YY# File = aprs_ag4000_ag.cfg

#-------------------------------------------------# Uncomment the following section to boot board #3. Also, correctly set the appropriate Bus/Slot info.#-------------------------------------------------

#[Board3]# Product = AG_4000_T1# AutoStart = Yes# AutoStop = Yes# Number = 3

# Bus = XX# Slot = YY# File = aprs_ag4000_ag.cfg

#-------------------------------------------------# Uncomment the following section to boot board #4. Also, correctly set the appropriate Bus/Slot info.#-------------------------------------------------

#[Board4]# Product = AG_4000_T1# AutoStart = Yes# AutoStop = Yes# Number = 4# Bus = XX# Slot = YY

# File = aprs_ag4000_ag.cfg


38/80



Sample ag.cfg File

Modify your ag.cfgfile to look like the following sample. This is a single board configuration sample.

If you are using a multiple-board system you must uncomment additional board sections. Note

specific areas where changes are made.

Using any text editor, modify the ag.cfgfile. The file should look similar to the following. Specific

settings that must be changed are bold and called out with boxed text.## AG Plugin-in Config File for AG 4000# ag.cfg## TCP files are shipped with the AG-CAS sub-package of Natural Access. Be sure that you installed# the protocols that are specified below before trying to start a board with this configuration file.

TCPFiles[0] = nocc.tcp # "no trunk control" protocol# TCPFiles[1] = wnk0.tcp # two-way wink start trunk control program, T1 and analog DID# TCPFiles[1] = wnk1.tcp # two-way wink start trunk control program, analog E+MTCPFiles[1] = ops0.tcp # Off-Premises Station trunk control program

# TCPFiles[1] = gds0.tcp # Digital Ground Start trunk control program

# DSP (.m54) files to link in

DSP.C5x.DSPFiles = callp.m54 dtmf.m54 ptf.m54 signal.m54 tone.m54 voice.m54 wave.m54 rvoice.m54

DLMFiles[0] = gtp.leoDLMFiles[1] = voice.leoDLMFiles[2] = svc.leo

# If one needs to override the internal Companding Mode default of the AG4000 board type (T1/E1),# uncomment the appropriate XLaw/Lib lines (typically MU-LAW/ag2libu for US and A-LAW/ag2liba elsewhere)

# XLaw = MU-LAW# DSP.C5x.Lib = ag2libu.r54# XLaw = A-LAW# DSP.C5x.Lib = ag2liba.r54

Clocking.HBus.ClockMode = STANDALONEClocking.HBus.ClockSourceNetwork = 1 # 1, 2, 3 or 4 for the reference trunk connectionClocking.HBus.ClockSource = NETWORK # NETWORK or OSC

NetworkInterface.T1E1[0].FrameType = ESF # ESF or D4NetworkInterface.T1E1[0].LineCode = B8ZS # AMI, B8ZS, AMI_ZCS, AMI_BELL, AMI_DDS or AMI_GTE

# NetworkInterface.T1E1[1].FrameType = ESF # ESF or D4# NetworkInterface.T1E1[1].LineCode = B8ZS # AMI, B8ZS, AMI_ZCS, AMI_BELL, AMI_DDS or AMI_GTE

# NetworkInterface.T1E1[2].FrameType = ESF # ESF or D4# NetworkInterface.T1E1[2].LineCode = B8ZS # AMI, B8ZS, AMI_ZCS, AMI_BELL, AMI_DDS or AMI_GTE

# NetworkInterface.T1E1[3].FrameType = ESF # ESF or D4

# NetworkInterface.T1E1[3].LineCode = B8ZS # AMI, B8ZS, AMI_ZCS, AMI_BELL, AMI_DDS or AMI_GTE

#------------------------------------------------------------------------------# Other default settings may be found in your AG 4000 Installation and Developers Manual.#------------------------------------------------------------------------------

This integrationrequires thatthe protocolsTCPFiles[0] =nocc.tcp andTCPFiles[1] =ops0.tcp beuncommented.

Enter the values in boldfor theClockSource,FrameType, andLineCodefor yourAvaya integration.


39/80



Apropos Version 5.0.2 Windows 2000

The values outlined below are specific to an Avaya Definity PBX utilizing Lineside T1s integrating

to Apropos Version 5.0.2 Windows 2000 Servers. The file to be modified for Apropos v5.0.2

integrations is the ag.cfgfile. Changes to the cta.cfgfile are not required for this integration. The

following table contains values for the AG4000 2-T1 board.



TCP ops0.tcp

TCP nocc.tcp



Bus Number Use value found with pciscan

Slot Number Use value found with pciscan

Clock Ref NET1

Frame Type ESF

Line Code B8ZS

Sample ag.cfg File






pciscan

A window will display with the bus and slot information for AG-4000 T1 card. This information

must be added to the ag.cfgfile.


settings that must be changed are bold and called out with boxed text.

# -------------------------------# ag.cfg# Sample configuration file for standalone AG4000## -------------------------------[AGBOARD]

#---------- COMMON section --------

# Un-comment the ONE appropriate protocol with nocc being the default.# TCP = wnk0.tcp # two-way wink start trunk control program, T1 and analog DID# TCP = wnk1.tcp # two-way wink start trunk control program, analog E+MTCP = ops0.tcp # Off-Premises Station trunk control program# TCP = gds0.tcp # Digital Ground Start trunk control programTCP = nocc.tcp # "NO Call Control" protocol - always downloaded for debugging

This integrationrequires that theprotocolsTCP =ops0.tcp andTCP = nocc.tcpbe uncommented.


40/80



# Common MU-LAW/A-LAW DSP functionsAG2DspFile = tone.m54 # Beep, tone generation, dialAG2DspFile = callp.m54 # Call Progress detectionAG2DspFile = signal.m54 # Out-of-band channel associated signalingAG2DspFile = dtmf.m54 # DTMF and silence/energy detectorsAG2DspFile = ptf.m54 # Cleardown and precise tone detectionAG2DspFile = voice.m54 # NMS ADPCM play and record

AG2DspFile = mf.m54 # MF detection# AG2DspFile = rvoice.m54 # Unformatted PCM play and record# AG2DspFile = oki.m54 # OKI ADPCM play/recordAG2DspFile = wave.m54 # play and record wave files

# Uncomment the appropriate IDLE CODE (typically MU-LAW for the US and A-LAW elsewhere)

IdleCode = MU-LAW# IdleCode = A-LAWRunModule = gtp.leoRunModule = svc.leoRunModule = voice.leoRunModule = ag2fax.leo

#--------- BOARDS section ----------

## use the tool 'pciscan' to identify the PCIBUS and PCISLOT for each board in the system#-----------------------------------

Board 0PCIBUS = XXPCISLOT = YY

ClockRef = NET1 # NET1, NET2, NET3, NET4 or OSC (Master Clock Reference# from T1 connection)

FrameType = ESF # D4 or ESFLineCode = B8ZS # AMI, B8ZS, AMI_ZCS, AMI_BELL, AMI_DDS or AMI_GTE

End Board

#-----------------------------------

Enter the appropriateBusandSlotinformation youreceived from runningpciscan.

Enter thevalues in boldfor theClockSource,FrameType,andLineCodefor your Avayaintegration.


41/80



Apropos Version 5.0.2 Windows NT

The values outlined below are specific to an Avaya Definity PBX utilizing LinesideT1s integrating to

Apropos Version 5.0.2 Windows NT Servers. The file to be modified for Apropos v5.0.2 integrations

is the ag.cfgfile. Changes to the cta.cfgfile are not required for this integration. The following

table contains information for the AG 4000 2-T1 board.



TCP lps0.tcp

TCP nocc.tcp



Bus Number Use value found with blocate

Slot Number Use value found with blocate

Clock Ref NET1

Frame Type ESF

Line Code B8ZS

Sample ag.cfgFile





At a DOS prompt on your voice server, type the following command.blocate





# -------------------------------# ag.cfg# Sample configuration file for standalone AG4000

#---------- COMMON section --------

# Un-comment the ONE appropriate protocol with nocc being the default.# TCP = wnk0.tcp # "2-way Wink" protocol# TCP = did0.tcp # "Incoming Only Wink" protocol# TCP = ogt0.tcp # "Outgoing Only Wink" protocolTCP = lps0.tcp # "Digital Loop Start - OPS-FX" protocol# TCP = lps9.tcp # "Digital Loop Start - OPS-SA" protocol# TCP = gst8.tcp # "Digital Ground Start - GST-FX" protocol# TCP = gst9.tcp # "Digital Ground Start - GST-SA" protocolTCP = nocc.tcp # "NO Call Control" protocol - always downloaded for debugging purposes

# Common MU-LAW/A-LAW DSP functions

This integrationrequires thatthe protocolsTCP = lps0.tcpandTCP =nocc.tcpbeuncommented.


42/80



AG2DspFile = tone.m54 # Beep, tone generation, dialAG2DspFile = callp.m54 # Call Progress detectionAG2DspFile = signal.m54 # Out-of-band channel associated signalingAG2DspFile = dtmf.m54 # DTMF and silence/energy detectorsAG2DspFile = ptf.m54 # Cleardown and precise tone detectionAG2DspFile = voice.m54 # NMS ADPCM play and record

AG2DspFile = mf.m54 # MF detection# AG2DspFile = rvoice.m54 # Unformatted PCM play and record# AG2DspFile = oki.m54 # OKI ADPCM play/recordAG2DspFile = wave.m54 # play and record wave files


IdleCode = MU-LAW# IdleCode = A-LAW

RunModule = gtp.leoRunModule = svc.leoRunModule = voice.leo

RunModule = ag2fax.leo

#--------- BOARDS section ----------# use the tool 'blocate' to identify the PCIBUS and PCISLOT for each board in the system#-----------------------------------

Board 0

PCIBUS = XXPCISLOT = YY

ClockRef = NET1 # NET1, NET2, NET3, NET4 or OSC (Master Clock Reference# from T1connection)

FrameType = ESF # D4 or ESF

LineCode = B8ZS # AMI, B8ZS, AMI_ZCS, AMI_BELL, AMI_DDS or AMI_GTE

End Board#-----------------------------------

Enter theappropriateBusandSlotinformation youreceived fromrunningblocate.

Enter the valuesin bold for theClockRef,FrameType, andLineCodefor your

Avaya integration


43/80



Apropos Version 5.0 and Version 5.0.1

The values outlined below are specific to an Avaya Definity PBX utilizing LinesideT1s integrating to

Apropos Version 5.0 and 5.0.1 Windows NT Servers. The file to be modified for Apropos v5.0 and

5.0.1 integrations is the ag.cfgfile. Changes to the cta.cfgfile are not required for this integration.

The following table contains information for the AG 4000 2-T1 board.



TCP lps0.tcp

TCP nocc.tcp



Bus Number Use value found with blocate

Slot Number Use value found with blocate

Clock Ref NET1

Frame Type ESF

Line Code B8ZS

Sample ag.cfg File






blocate





# -------------------------------# ag.cfg## Sample configuration file for standalone AG4000

#---------- COMMON section --------

# Un-comment the ONE appropriate protocol with nocc being the default.# TCP = wnk0.tcp # "2-way Wink" protocol# TCP = did0.tcp # "Incoming Only Wink" protocol# TCP = ogt0.tcp # "Outgoing Only Wink" protocolTCP = lps0.tcp # "Digital Loop Start - OPS-FX" protocol# TCP = lps9.tcp # "Digital Loop Start - OPS-SA" protocol# TCP = gst8.tcp # "Digital Ground Start - GST-FX" protocol# TCP = gst9.tcp # "Digital Ground Start - GST-SA" protocolTCP = nocc.tcp # "NO Call Control" protocol - always downloaded

#for debugging purposes

This integrationrequires that theprotocolsTCP =lps0.tcp andTCP =nocc.tcpbeuncommented.


44/80



# Common MU-LAW/A-LAW DSP functions

AG2DspFile = tone.m54 # Beep, tone generation, dialAG2DspFile = callp.m54 # Call Progress detectionAG2DspFile = signal.m54 # Out-of-band channel associated signalingAG2DspFile = dtmf.m54 # DTMF and silence/energy detectorsAG2DspFile = ptf.m54 # Cleardown and precise tone detection

AG2DspFile = voice.m54 # NMS ADPCM play and recordAG2DspFile = mf.m54 # MF detection# AG2DspFile = rvoice.m54 # Unformatted PCM play and record# AG2DspFile = oki.m54 # OKI ADPCM play/recordAG2DspFile = wave.m54 # play and record wave files


IdleCode = MU-LAW# IdleCode = A-LAW

RunModule = gtp.leoRunModule = svc.leoRunModule = voice.leoRunModule = ag2fax.leo

#--------- BOARDS section ----------# use the tool 'blocate' to identify the PCIBUS and PCISLOT# for each board in the system#-----------------------------------

Board 0

PCIBUS = XXPCISLOT = YY

ClockRef = NET1 # NET1, NET2, NET3, NET4 or OSC (Master Clock Reference# from T1 connection)

FrameType = ESF # D4 or ESF

LineCode = B8ZS # AMI, B8ZS, AMI_ZCS, AMI_BELL, AMI_DDS or AMI_GTE

End Board#-----------------------------------

Enter theappropriateBusandSlotinformation youreceived fromrunningblocate.

Enter the values in boldfor the ClockRef,FrameType, and

LineCode for yourAvaya integration.


45/80



Values for PIL and SLP Processes

The following identifies the information to use in the Call Processing Server Processes for this

integration. These server processes are configured in the Apropos System Manager application and

are described in the Apropos System Manager Help system.

The PIL process is a required Call Processing Server Process. However, the value of the SwitchLink, in the PIL process, can determine whether the SLP process must be configured. When the

SLP process must be configured, the values shown in the SLP Process section are used.

When the Switch Link value is True or Enabled, an SLP process must be configured that

corresponds to the Associated Switch Link Process value of the PIL process.

When the Switch Link value is False or Disabled, and your site uses switch link enabled

agents, an SLP process must be configured that corresponds to the Associated Switch Link

Process value of the agents.

When the Switch Link value is False or Disabled, and your site does not use switch link

enabled agents, the SLP process is not configured.

The properties and values for the PIL and SLP Processes vary slightly from Apropos Version 5 to

Version 6. Refer to the appropriate table below for the settings affecting your site.

Version 6 PIL Process

The following identifies the property and the appropriate value to use during the PIL process

configuration. The appropriate values for fields not specifically mentioned here, are site determined.

Property Value

extension Applicable Directory Number

port type t1_loop_start

switchlink Use True for on or False for off.

link name Enter the appropriate Link name.

Version 6 SLP Process

The following identifies the property and the appropriate value to use during the SLP process

configuration. The appropriate values for fields not specifically mentioned, are site determined.

Property Value

ctclogicalidLink Name as defined in the Dialogic CTC Server

Configuration Program.

ctcserver Where the CTC software is located. Default is localhost.

ctctransport ncacn_ip_tcp

PBX Type From the drop down list select ctc_lucent

ACDMode EAS


46/80



Version 5 PIL Process

The following identifies the property and the appropriate value to use during the PIL process

configuration. The appropriate values for fields not specifically mentioned here, are site determined.

Property Value to UsePIL Extension Number Applicable Directory Number

PIL Port Type t1_loop_start

Switch Link Mode Enabled

Associated Switch Link Process Select a value from the appropriate list.

Version 5 SLP Process

The following identifies the property and the appropriate value to use during the SLP process

configuration. The appropriate values for fields not specifically mentioned, are site determined.

Property Value to UseCTC Link Identifier Link Name as defined in the Dialogic CTC Server

Configuration Program.

CTC Server Hostname Where the CTC software is located. Default is localhost.

CTC Transport Mode ncacn_ip_tcp

PBX Type ctc_lucent

Startup Service Dependency CTCServer

Link ID Populated automatically from the SLP Process Namewhen created. Do not change this value.

ACD PIL Login Script Change

Version 6.5 PIL Script Change

For Apropos Version 6.5 and above users, a PIL script change is required for the completion of the

PIL EAS ACD integration. You must add your PIL Agent ID numbers to the array table as they

relate to the PIL ports. The se

Documents

Avayapbx Cc 65