Avaya CT for Siebel 7 · Preface 6 Avaya CT for Siebel Installation Guide Related documentation This section provides a list of documents related to the switch, Avaya CT, Avaya CT

Avaya CT for Siebel 7Release 4.0Installation Guide

September 2006

© 2006 Avaya Inc. All Rights Reserved.

NoticeWhile reasonable efforts were made to ensure that the information in this document was complete and accurate at the time of printing, Avaya Inc. can assume no liability for any errors. Changes and corrections to the information in this document might be incorporated in future releases.

Documentation disclaimerAvaya Inc. is not responsible for any modifications, additions, or deletions to the original published version of this documentation unless such modifications, additions, or deletions were performed by Avaya. Customer and/or End User agree to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation to the extent made by the Customer or End User.

Link disclaimerAvaya Inc. is not responsible for the contents or reliability of any linked Web sites referenced elsewhere within this documentation, and Avaya does not necessarily endorse the products, services, or information described or offered within them. We cannot guarantee that these links will work all the time and we have no control over the availability of the linked pages.

WarrantyAvaya Inc. provides a limited warranty on this product. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya�s standard warranty language, as well as information regarding support for this product, while under warranty, is available through the Avaya Support Web site:http://www.avaya.com/support

LicenseUSE OR INSTALLATION OF THE PRODUCT INDICATES THE END USER'S ACCEPTANCE OF THE TERMS SET FORTH HEREIN AND THE GENERAL LICENSE TERMS AVAILABLE ON THE AVAYA WEB SITE http://support.avaya.com/LicenseInfo/ ("GENERAL LICENSE TERMS"). IF YOU DO NOT WISH TO BE BOUND BY THESE TERMS, YOU MUST RETURN THE PRODUCT(S) TO THE POINT OF PURCHASE WITHIN TEN (10) DAYS OF DELIVERY FOR A REFUND OR CREDIT.Avaya grants End User a license within the scope of the license types described below. The applicable number of licenses and units of capacity for which the license is granted will be one (1), unless a different number of licenses or units of capacity is specified in the Documentation or other materials available to End User. "Designated Processor" means a single stand-alone computing device. "Server" means a Designated Processor that hosts a software application to be accessed by multiple users. "Software" means the computer programs in object code, originally licensed by Avaya and ultimately utilized by End User, whether as stand-alone Products or pre-installed on Hardware. "Hardware" means the standard hardware Products, originally sold by Avaya and ultimately utilized by End User.

License type(s)Concurrent User License (CU). End User may install and use the Software on multiple Designated Processors or one or more Servers, so long as only the licensed number of Units are accessing and using the Software at any given time. A "Unit" means the unit on which Avaya, at its sole discretion, bases the pricing of its licenses and can be, without limitation, an agent, port or user, an e-mail or voice mail account in the name of a person or corporate function (e.g., webmaster or helpdesk), or a directory entry in the administrative database utilized by the Product that permits one user to interface with the Software. Units may be linked to a specific, identified Server.Shrinkwrap License (SR). With respect to Software that contains elements provided by third party suppliers, End User may install and use the Software in accordance with the terms and conditions of the applicable license agreements, such as "shrinkwrap" or "clickwrap" license accompanying or applicable to the Software ("Shrinkwrap License"). The text of the Shrinkwrap License will be available from Avaya upon End User�s request (see �Third-party Components" for more information).

Copyright Except where expressly stated otherwise, the Product is protected by copyright and other laws respecting proprietary rights. Unauthorized reproduction, transfer, and or use can be a criminal, as well as a civil, offense under the applicable law.

Third-party componentsCertain software programs or portions thereof included in the Product may contain software distributed under third party agreements ("Third Party Components"), which may contain terms that expand or limit rights to use certain portions of the Product ("Third Party Terms"). Information identifying Third Party Components and the Third Party Terms that apply to them is available on the Avaya Support Web site:http://support.avaya.com/ThirdPartyLicense/

Preventing toll fraud"Toll fraud" is the unauthorized use of your telecommunications system by an unauthorized party (for example, a person who is not a corporate employee, agent, subcontractor, or is not working on your company's behalf). Be aware that there can be a risk of toll fraud associated with your system and that, if toll fraud occurs, it can result in substantial additional charges for your telecommunications services.

Avaya fraud interventionIf you suspect that you are being victimized by toll fraud and you need technical assistance or support, call Technical Service Center Toll Fraud Intervention Hotline at +1-800-643-2353 for the United States and Canada. For additional support telephone numbers, see the Avaya Support Web site:http://www.avaya.com/support

TrademarksAvaya and the Avaya logo are either registered trademarks or trademarks of Avaya Inc. in the United States of America and/or other jurisdictions.

Downloading documentationFor the most current versions of documentation, see the Avaya Support Web site:http://www.avaya.com/support

COMPASThis document is also available from the COMPAS database. The COMPAS ID for this document is 121444.

Avaya supportAvaya provides a telephone number for you to use to report problems or to ask questions about your product. The support telephone number is 1-800-242-2121 in the United States. For additional support telephone numbers, see the Avaya Support Web site:http://www.avaya.com/support

http://www.avaya.com/support


http://www.avaya.com/support/

http://support.avaya.com/LicenseInfo/

http://support.avaya.com/ThirdPartyLicense/

http://www.avaya.com/support/

September 2006 3

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Reason for reissue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Communication server documentation . . . . . . . . . . . . . . . . . . . . . . . . . 6Avaya CT documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Avaya AE Services Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . 6Avaya CT for Siebel documentation . . . . . . . . . . . . . . . . . . . . . . . . . . 7Siebel Enterprise Applications documentation . . . . . . . . . . . . . . . . . . . . . 7

Planning for installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Server installation checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Reviewing hardware and software requirements . . . . . . . . . . . . . . . . . . . . . 11

Required servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Optional servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Avaya CT for Siebel server hardware and software requirements . . . . . . . . . . . . 12Avaya CT Server hardware and software requirements . . . . . . . . . . . . . . . . . 13Avaya AE Services hardware and software requirements . . . . . . . . . . . . . . . . 13Database server hardware and software requirements . . . . . . . . . . . . . . . . . 14Communication server requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 14Example network diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Server side components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Preinstallation checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Permissions checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Installing Avaya CT for Siebel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Required knowledge and skills . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Where to install the components . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Installing the Avaya CT for Siebel 7 Integration. . . . . . . . . . . . . . . . . . . . . . 23Repairing a damaged Avaya CT for Siebel Integration installation . . . . . . . . . . . . . 26Modifying an Avaya CT for Siebel Integration installation . . . . . . . . . . . . . . . . . 27Removing the Avaya CT for Siebel Integration . . . . . . . . . . . . . . . . . . . . . . 29

Avaya CT for SiebelInstallation Guide

Contents

Contents

4 Avaya CT for Siebel Installation Guide

Setting up the Change State applet . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Building a call database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Required knowledge and skills . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Checklist for building a database . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Building a Microsoft SQL database . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Building an IBM DB2 database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Setting up the CMS Data Feed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Required knowledge and skills . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Configuring the CMS Data Feed . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Configuring a DSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Configuring an SQL DSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Configuring a DB2 DSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Preparing the CMS files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Starting the Data Feed service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Setting up Call Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Required knowledge and skills . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53About Call Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Configuring Call Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Starting Call Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Registering and administering the product . . . . . . . . . . . . . . . . . . . . . . . 59Registering the product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Administering the product. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

September 2006 5

Preface

This document provides information necessary to install the Avaya Computer Telephony (CT) for Siebel 7 solution server applications.

Reason for reissueThis document was reissued to include support for Siebel 7 with Avaya CT Server as well as Avaya Application Enablement Services (AE Services).

The Avaya CvCT for Siebel 7 Integration Driver Installer, the Application Installer, and the TSPrep Installer are merged into one common installer.

OrganizationThis guide is organized as follows:

● Planning for installation on page 9

● Installing Avaya CT for Siebel on page 21

● Building a call database on page 33

● Setting up the CMS Data Feed on page 41

● Setting up Call Service on page 53

● Registering and administering the product on page 59

Preface


Related documentationThis section provides a list of documents related to the switch, Avaya CT, Avaya CT for Siebel, and Siebel Enterprise Applications.

Communication server documentationThe following documentation CD-ROMs provide information about communication server installation and administration:

● MultiVantage� Software Documentation Library, 555-233-823

● DEFINITY ECS Release 10 Documentation Library, 555-233-822



These documentation CD-ROMs can be ordered by calling 1-800-457-1235 (toll free in the United States and Canada) or +1-207-866-6701 outside of the United States and Canada, or by using the Avaya Web site, http://www.avaya.com/support.

Avaya CT documentationThe following document is related to Avaya CT. This document is stored on the Avaya CT CD-ROM (not provided with Avaya CT for Siebel).

Avaya AE Services DocumentationSee the Avaya AE Services Installation and Administration and Maintenance Guide.

Avaya CT document File name (PDF)

Telephony Services Administration and Maintenance netmangd.pdf


Related documentation

September 2006 7

Avaya CT for Siebel documentationThe following documents are related to Avaya CT for Siebel. These documents are stored on the Avaya CT for Siebel 7 CD-ROM under the \Docs folder in the root directory.

Siebel Enterprise Applications documentationThe following documents are related to Siebel Enterprise Applications. These documents are stored on the Siebel Bookshelf CD-ROM (not provided with Avaya CT for Siebel).

Avaya CT for Siebel documents File name (PDF)

User Guide user.pdf

Installation Guide install.pdf

Administration Guide admin.pdf

Release Notes ReleaseNotes.pdf

Siebel Bookshelf documents

Communications Server Administration Guide

Siebel Tools Guide

Application Administration

Preface


September 2006 9

Planning for installation

Before beginning the actual installation, review this chapter for an overview of the tasks. This chapter includes several conceptual diagrams that show how the components work together.

This section includes the following topics:

● Server installation checklist on page 10

● Reviewing hardware and software requirements on page 11

● Preinstallation checklist on page 19

● Permissions checklist on page 20

When the tasks in this section are completed, continue the installation. See Installing Avaya CT for Siebel on page 21.



Server installation checklistThe server installation checklist is provided as a general record of installation. With this reference, the installer may see at a glance what happens next, and what has already happened. Avaya recommends that you print this checklist and keep it handy throughout the installation.

Requirement Check-off

Planning for installation on page 9● Reviewing hardware and software requirements on page 11

● Preinstallation checklist on page 19

● Permissions checklist on page 20

Installing Avaya CT for Siebel on page 21

● Setting up the Change State applet on page 31

Building a call database on page 33

Setting up the CMS Data Feed on page 41● Configuring the CMS Data Feed on page 42

● Configuring a DSN on page 45

● Preparing the CMS files on page 48

● Starting the Data Feed service on page 51

Setting up Call Service on page 53● Configuring Call Service on page 55

● Starting Call Service on page 57

Registering and administering the product on page 59

Reviewing hardware and software requirements

September 2006 11

Reviewing hardware and software requirementsIt is important to realize there is a difference between the Avaya CT Server and the Avaya CT for Siebel server.

● The Avaya CT Server is also known as the TServer (telephony server). This server is the required equipment for the regular Avaya CT solution.

● The Avaya CT for Siebel server is a separate server that contains the software required for Avaya CT to work with the Siebel server. It must be separate from the Avaya CT Server.

The following sections list required and optional servers and application software.

Required serversThe following servers are required to support the Avaya CT for Siebel solution:

Server Version/Purpose

Avaya CT for Siebel server Avaya CT for Siebel server applications

Avaya CT Server / Avaya AE Services

Avaya CT Release 9.5 or later / Avaya AE Services Release 3.0 or later

Database server Microsoft® SQL Server 2000 / SQL Server 2005 or IBM® DB2 Version 7.2 database server

Communication server DEFINITY® ECS Release 9 or laterAvaya MultiVantage� Software, Release 1.1 or later

Siebel server Siebel Server System (Application, Database, Web, Name Servers)



Optional serversThe following servers are optional for the Avaya CT for Siebel solution:

Avaya CT for Siebel server hardware and software requirements

The Avaya CT for Siebel server has the following minimum hardware requirements:

Server Purpose

Avaya CT Server / Avaya AE Services

Backup server with the following optional component:● Avaya CT Server applications and Avaya AE Services

Database server Backup for Microsoft SQL or IBM DB2 database server

Hardware Requirements

CPU Pentium processor 1 Gigahertz (GHz) or higher● Symmetric multiprocessor configurations consisting of up to

four processors are supported.● Asymmetric multiprocessor configurations are not supported.

RAM As per Siebel recommendations, see Bookshelf for details.

Network connection One network interface card

Drive CD-ROM drive


September 2006 13

The Avaya CT for Siebel server has the following software requirements:

Avaya CT Server hardware and software requirementsFor hardware and software requirements of the Avaya CT Server, see the Avaya Computer Telephony documentation.

Avaya AE Services hardware and software requirementsFor hardware and software requirements of Avaya AE Services, see the Avaya AE Services documentation.

Software Requirements

Operating system One of the following:● Windows 2000 Server or later● Windows Server 2000, Service Pack 1 required, Service

Pack 2 recommended● Windows Advanced Server 2000, Service Pack 1 required,

Service Pack 2 recommended● Windows Server 2003, Service Pack 1 required

Network software TCP/IP protocol stack

Telephony software One of the following:● Avaya Computer-Telephony Release 9.5 or later● Software Release 1.1 or later

Siebel software Siebel Dedicated Client

Database Client software All of the following:● Microsoft SQL or IBM DB2● BTRIEVE



Database server hardware and software requirementsThe database server has the following minimum hardware requirements:

The database server has the following software requirements:

Communication server requirementsOn the communication server, verify that the following requirements have been met:

Hardware Requirements

CPU Pentium processor 500 megahertz (MHz) or higher

RAM 512 megabytes (MB)

Network connection One network interface card

Drive CD-ROM drive

Software Requirements

Operating system One of the following:● Windows 2000 Server or later● Windows Server 2000, Service Pack 1 required, Service Pack 2

recommended● Windows Advanced Server 2000, Service Pack 1 required,

Service Pack 2 recommended

Network software TCP/IP protocol stack

Database software On the database server, verify that the following have been done:

● Microsoft SQL Server 2000 Service Pack 2 / SQL Server 2005 or IBM DB2 Version 7.2 or later is installed

● Microsoft SQL Server Agent Service is configured properly and running

● For multisite transfers, Microsoft SQL Enterprise Edition 2000 / SQL Enterprise Edition 2005 is installed


September 2006 15

● The communication server must be DEFINITY ECS R9 or later, or MultiVantage Software R1.1 or later.

● The communication server must be appropriately configured to collect digits if the Call Service is to be installed.

● If the communication server is DEFINITY ECS R10, or MultiVantage Software R1.1 or later, verify that the following administration has been done:

- On the System Parameters Customer Options form, the Computer Telephony Adjunct Links option on Page 2 and the Agent States option on Page 8 must be enabled.

- On the Feature-related System Parameters form, the Create Universal Call ID (UCID) option on Page 4 and the Send UCID to ASAI option on Page 10 must be enabled. The UCID Network Node ID field on Page 4 must be administered with a node ID (for example, 0001).

- On the Computer Telephony Integration (CTI) Link form, the Station Type field must be set to ADJLK, the Fixed TEI field must be enabled, the TEI field must be set to 1, the CRV field must be set to 2, and the Event Minimization field must be disabled.

● If the communication server is DEFINITY ECS R9, verify that the following administration has been done:

- On the System Parameters Customer Options form, the ASAI Proprietary Adjunct Links option on Page 2 must be enabled.

- On the Feature-related System Parameters form, the Create Universal Call ID (UCID) option on Page 4 and the Send UCID to ASAI option on Page 8 must be enabled. The UCID Network Node ID field on Page 4 must be administered with a node ID (for example, 0001).

- On the CTI Link form, the Station Type field must be set to ADJLK, the Fixed TEI field must be enabled, the TEI field must be set to 1, and the CRV field must be set to 2. On Page 2, the Event Minimization field must be disabled.

Example network diagramThe completed installation resembles the network diagram below. This is a very basic diagram. See Server side components on page 16 for more detail about the server installation and how the components work together.

In a basic network:

● The communication server generates the call center data for the Call Management System (CMS) server and telephony service for the Avaya CT Server.



● The Avaya CT Server (also called the TServer) / Avaya AE Services controls the Computer Telephony Integration (CTI). The TServer Preparation Files are installed on the Avaya CT Server.

● The Database server controls access to the Call Database.

● The Avaya CT for Siebel server contains the software for operation of the CMS Data Feed and Call Service.

● The Siebel Communication server is one of the servers of the Siebel system. It will be installed with the Telephony Driver so that the clients may access the TServer.

● The CMS server contains the call center data used with the Data Feed.

● The client machines access the servers to obtain data when answering calls.

Server side componentsThe Avaya CT for Siebel server is a component consisting of the CT for Siebel Administrative Tool, CMS Data Feed, CMS Data Pool, the Call Database builder, Siebel agent state applets, and Call Service. It must be installed on a machine having the Siebel Mobile client. The Call Database can be built on Microsoft SQL or IBM DB2. If the Call


September 2006 17

Database is DB2, it is very important that the Avaya CT for Siebel server is installed on the same server as the DB2 Database server. See the following figure.

CT for Siebel Administrative Tool - This tool generates the reports and the labels for the CMS data that will be displayed across the marquees. It also imports configurations, sets the Change Agent Work modes, and configures the CMS Data Feed and Call Service.

CMS Data Feed/Pool - This tool extracts the CMS Solaris® server data into a memory cluster (known as the CMS Data Pool). Then, using Windows operating system, it integrates the data with reports and labels from the Messaging Database and the Administrative Tool, finally feeding the combined data into Siebel for distribution among the designated agents.

Call Database - The Call Database (or CTI Database) is a database for holding such data as bookmarks and transfers for collaborative agent functions (conference, transfer, and so forth), Siebel row IDs for outbound calls, and queue time values.

The Messaging Database is a sub table of the Call Database. The specific CMS Messaging Report Groups and labels (that is, the title for each statistic) are generated in the Administrative Tool, but they are stored in the Messaging Database. They are shown separately to illustrate their functions, but the Messaging Database is actually a sub table of the Call Database.



Note:Note: The Messaging and Call Databases are one database (the Call Database).

They are separated here for illustration purposes.

Call Service - This optional component allows the CT Server to monitor the Vector Directory Numbers (VDNs) so that collected digits and queue time may be collected and reported. Special VDNs may be provisioned for compatibility with Internet Call Center.

Applets - These are enhancements to the Agent Work bars that reside on the server.

Preinstallation checklist

September 2006 19

Preinstallation checklistUse this checklist to ensure all necessary steps have been completed before installing the Avaya CT for Siebel server applications.


The Avaya CT Server / Avaya AE Services is running. Verify that the "Tlink" process is running between Avaya CT / AE Services and the communication server.

All VDNs are added in the Avaya Administrator.

The Siebel server is running.

All relevant agent machines are installed with the Siebel client, and communications must be enabled for the user in the server using the uagent.cfg file.

CTI Database server exists on the network.

Siebel is properly installed and configured.

Avaya CT Client Version 9.5 or later is properly installed and configured.

The Avaya CT client is installed on the same machine running the Avaya CT for Siebel applications.



Permissions checklistUse this checklist to verify that logins have been created for the supporting applications.


An Avaya CT login has been created to log in to the telephony server.

A database login has been created with database administrator privileges.

A Siebel login has been created with administrator privileges.

A Windows administrator login has been created.

September 2006 21

Installing Avaya CT for Siebel

Most of the components shown in Server side components on page 16 are installed automatically through the applications component installation process. You can install the Data Feed, the Data Pool, the Administrative Tool, and the applets with minimal input.


● Required knowledge and skills on page 21

● Where to install the components on page 22

● Installing the Avaya CT for Siebel 7 Integration on page 23

● Repairing a damaged Avaya CT for Siebel Integration installation on page 26

● Modifying an Avaya CT for Siebel Integration installation on page 27

● Removing the Avaya CT for Siebel Integration on page 29

Required knowledge and skillsGeneral Windows operating system knowledge is required for these tasks.



Where to install the componentsThe Server Applications may be installed anywhere on the network, provided the other key components (Avaya CT Server / Avaya AE Services, database server, Siebel server, and agent machines) can access them. Although Avaya recommends that you provide a server machine exclusively for the Avaya CT for Siebel solution, it may be installed on an existing server. Avaya strongly advises you not to place these components on the same machine as the Avaya CT Server / Avaya AE Services (the TServer). The Administrator�s Tool must also be installed on the Database server.

The following figure illustrates the typical network architecture for Avaya CT for Siebel:

Installing the Avaya CT for Siebel 7 Integration

September 2006 23

Installing the Avaya CT for Siebel 7 IntegrationTo install the Avaya CT for Siebel 7 Integration components:

1. When you are upgrading from an earlier release of the software, Avaya recommends that you uninstall the previous release first.

2. Close all open applications.

3. Log in as the administrator.

4. Stop Siebel Services.

5. Insert the Avaya CT for Siebel 7 CD-ROM in the CD-ROM drive of the Avaya CT for Siebel server.

Note:Note: When the Windows operating system is using the Explorer shell, Explorer

automatically opens the contents of the CD-ROM if the AutoRun feature is not disabled.

6. If the contents of the CD-ROM are not displayed automatically,

a. On the Windows desktop, double-click My Computer.b. Double-click the CD-ROM drive.

7. Double-click Avaya CvCT Integration for Siebel 7 Application.exe.

The Choose Setup Language dialog box is displayed.

8. Choose the language for the setup and click OK. The software searches for installed components upon execution.

The Welcome dialog box is displayed.

9. Click Next.The License Agreement dialog box is displayed.

10. Click Yes.

The Feature selection dialog box is displayed.

11. Select the components and subcomponents to install.

12. Click Next.● If the "Avaya CvCT Driver" option is selected, go to step 13.

● If the "Application Installer" option is selected, go to step 18.

● If the "TSPrep Installer" option is selected, go to step 22.



Note:Note: The TSPrep Installer option is not required in case of Avaya AE Services.

The Choose Siebel Version dialog box is displayed.

13. Select the correct version of Siebel installed on the machine and click Next.14. To install the integration driver in a location other than the default, click Browse to

select a new location.

Note:Note: Avaya recommends installing the Integration driver in the <Siebel

Installation Dir>\siebsrvr\BIN.

15. Click Next.The Create DSN dialog box is displayed.

16. Select the database platform for Avaya CvCT for Siebel 7 integration for creating DSN and click Next.The Avaya CvCT for Siebel 7 integration database location dialog box is displayed.

17. Enter the database location as IP address or machine name and click Next.● If the "Application Installer" option is selected, go to step 18.

● If the "TSPrep Installer" option is selected, go to step 19.

● If you are not using either of the two options, go to step 22.

The Choose Destination location dialog box is displayed.

18. To install the application components in a location other than the default, click Browse to select a new location and click Next.● If the "TSPrep Installer" option is selected, go to step 19.

● If not, go to step 22.

The License Path for TSPrep Application dialog box is displayed.

Note:Note: The license file should be installed in a shared folder on the Avaya CT for

Siebel server.

19. In the License Path for TSPrep Application dialog box, click Browse to select the correct folder.

20. Select the path for the license file and click Next.The License file for TSPrep Application dialog box is displayed.

21. Select the appropriate license file and click Next.22. Review the list to make sure the settings selected are correct and click Next.

All the components selected are installed.

Installing the Avaya CT for Siebel 7 Integration

September 2006 25

23. Click Finish.

The server shuts down and restarts.



Repairing a damaged Avaya CT for Siebel Integration installation

You might need to repair the installation if a file or library gets corrupted.

To repair a damaged installation:




4. Insert the Avaya CT for Siebel 7 CD-ROM in the CD-ROM drive of the Avaya CT for Siebel server.






The Maintenance Welcome dialog box is displayed.

7. Click Repair.8. Click Next.

The software reinstalls the appropriate files. When the process is finished, the Finish Notification dialog box is displayed.

9. Click Finish.


Modifying an Avaya CT for Siebel Integration installation

September 2006 27

Modifying an Avaya CT for Siebel Integration installation

To modify an installation:




4. Insert the Avaya CT for Siebel 7 CD-ROM in the CD-ROM drive of the Avaya CT for Siebel applications server.







7. Click Modify.

8. Click Next.The Select Components dialog box is displayed.

9. Select the optional components you want to install.

Note:Note: If you clear the check box for any component that is already selected, the

software uninstalls that component.

10. Click Next.For installing the selected components, go through the steps listed in the following procedures:

● For Avaya CvCT Driver - Go to Step 13 in Installing the Avaya CT for Siebel 7 Integration.

● For Application Components - Go to Step 18 in Installing the Avaya CT for Siebel 7 Integration.

● For TSPrep Installer - Go to Step 19 in Installing the Avaya CT for Siebel 7 Integration.



Note:Note: The TSPrep Installer option is not required in case of Avaya AE Services.

The software installs the appropriate files. When the process is finished, the Finish Notification dialog box is displayed.

11. Click Finish.


Removing the Avaya CT for Siebel Integration

September 2006 29

Removing the Avaya CT for Siebel IntegrationTo remove the Avaya CT for Siebel integration:




4. Insert the Avaya CT for Siebel 7 CD-ROM in the CD-ROM drive of the Avaya CT for Siebel applications server.

Note:Note: When the Windows operating system is using the Explorer Shell, Explorer






7. Click Remove.

8. Click Next.A confirmation dialog box is displayed.

9. Click Yes to remove the application files.

The software removes the appropriate files. When the process is finished, the Finish Notification dialog box is displayed.

10. Click Finish.




September 2006 31

Setting up the Change State applet

Note:Note: Setting up the Change State applet is optional.

This feature allows the agents to change their telephone work modes from their desktop. This applet is set up on the Siebel Communication server.

To install the Change State applet:

1. Create the following folder on the server where the Siebel tools will be installed:

c:\Program Files\Avaya

2. Navigate to c:\<Siebel_folder>\tools\Objects\Enu\siebel.srf.

3. Copy the file siebel.srf to the c:\Program Files\Avaya folder.

4. Log in to the Siebel tools using the Siebel administrator login.

5. Choose Server from the field.

6. Lock the following projects: Bitmap, Command, Communications Administration, and Toolbar.

7. Create a new project named Avaya CTI and lock it.

8. From the toolbar, click Tools > Import from Archive.

A confirmation dialog box is displayed.

9. Click Yes.

10. Import Agent State Applet.sif from <Application Install Path>\Siebel 7 Applets for CvCT (for example, C:\ Program Files\Avaya\Siebel 7 Applets for CvCT\Agent State Applet.sif).

11. Click the Merge option.

12. Click Next.The tools will then review any conflicts and actions. When this completes, you can accept the changes.

Setting up the Change State applet


13. Click Tools > Compile Projects.The Object Compiler dialog box is displayed.

14. Select Locked projects and then click Browse to select the C:\Program Files\Avaya\siebel.srf file.

15. Click Compile.

16. When the compile is complete, stop Siebel services.

17. Copy the siebel.srf file from the C:\Program Files\Avaya folder and replace the one in the C:\<Siebel directory>\siebsrvr\Objects\Enu\siebel.srf folder.

18. Copy the files change_agent_state_disabled.gif and change_agent_state_enabled.gif files from the <Application Install Path>\Siebel 7 Applets for CvCT to the SWEApp\Public\ENU\Images folder for the thin client.

19. Copy the files change_agent_state_disabled.gif and change_agent_state_enabled.gif files from the <Application Install Path>\Siebel 7 Applets for CvCT to the Client\Public\ENU\Images folder for the thick client.

20. Start Siebel services.

September 2006 33

Building a call database

The next step is to create a call database using either Microsoft SQL or IBM DB2. This database is used by both the Toolbar and the CMS Messaging Service. The Toolbar uses this database as a holding queue for bookmark and screen transfers, while the call database uses the database for holding the reports, data labels, Siebel row IDs for outbound calls, and queue time values.



● Checklist for building a database on page 34

● Building a Microsoft SQL database on page 35

● Building an IBM DB2 database on page 37


Knowledge of the system network is required for these tasks.



Checklist for building a databaseUse the following checklist to assist before and after building a database:


Before you build the database...

Building the call database requires both the Database login (to make changes and amendments to the database server) and the Avaya CT login (to send the data to another Toolbar). Have these profiles readily available before proceeding.

After you build the database...

Verify that the CTI database has an administrative user named CVCTUSER.

Verify that the following tables exist in the CTI database: CALLDATA, DIVISIONS, GROUPS, ITEMS, MSGLOG, LIMITS, MULTISITE, and SCHEMAVER.If MULTISITE is not selected when building the call database, the MULTISITE table will not be in the database.

Verify that the following stored procedures exist in the database: sp_putdata10w, sp_putlogData, sp_Addrecord, sp_putData, sp_CleanTable.These procedures must have execute permissions for CVCTUSER.

Building a Microsoft SQL database

September 2006 35

Building a Microsoft SQL databaseTo build a Microsoft SQL database:

1. Click Start > Programs > Avaya CT for Siebel 7 > Administrator Tool.The Avaya CT for Siebel window is displayed.

2. Click File > Configure Database Provider.The Configure Database Provider dialog box is displayed.

3. Select the SQL database from the Select the Database Provider drop-down menu.

4. Click OK.

5. Select Service > DBBuilder.The Call DB Setup Options dialog box is displayed.

6. In the Options area, these options allows a high degree of customization that creates a database that best suits your needs. Select the desired options, which include:

● Call Database -This installs a new SQL Database that will contain the bookmark and screen transfer information for the Toolbar. If this is not installed, the agents will not be able to transfer screens or bookmarks.

● Multi-Site - This sets up the database so that it may be accessed by more than one SQL database. If more than one Call Center will be sharing this database, be sure to select this option. Otherwise, it is not necessary.



● Queue Time - This instructs the database to store the Queue Time from an incoming call. This time will subsequently be reported to the appropriate agent. This will not function if the Call Service is not present.

● Messaging Database - This option provides the CMS Data Feed.

7. In the Security area, select I will be using Standard Security, enter the user ID, and enter the password.

8. Click Continue.

Note:Note: The SQL Connection dialog box may be displayed. If it is, provide the

appropriate login credentials.

The Select Database dialog box is displayed.

9. Select <New>.

10. Click OK.

Note:Note: If a CTI Database already exists, you may select it instead of building a new

database, but it will erase all data that is currently in the database.

The New Call DB dialog box is displayed.

11. Enter a name for the database and select the appropriate size of the call center. Avaya recommends that the database be named CTI. Use the following guidelines for choosing the database size:

● Small - Call center with fewer than 50 agents.

● Medium - Call center with more than 50 agents but fewer than 250 agents.

● Large - Call center with multiple sites or a call center with more than 250 agents.

12. Click Create.

The Database Builder creates the database. When the installation success screen appears, the installation is complete.

Tip:Tip: The Data Feed services and the Call Service must be set before this

database will function properly. Do not exit the Administrator Tool as it will be required later.

Building an IBM DB2 database

September 2006 37

Building an IBM DB2 databaseBefore building an IBM DB2 database, you must fulfill the following prerequisites:

● You must log on as an administrative user for the DB2 database.

● The database server must have a C compiler.

● The build options for stored procedure builder must be set.

To build an IBM DB2 database:

1. Click Start > Programs > IBM DB2 > Stored Procedure Builder.The IBM DB2 Stored Procedure Builder dialog box is displayed.

2. In the Project window, right-click a database icon.

A menu is displayed.

3. Click SQL SP Build Options.

4. In the Compiler environment field, enter the fully qualified path to the command file that sets up the compiler environment variables. Depending on the compiler you are using, do one of the following:

● For Microsoft Visual C++ Version 5.0, enter:

c:\devstudio\vc\bin\vcvars32.bat

● For Microsoft Visual C++ Version 6.0, enter:

c:\Microsoft Visual Studio\VC98\bin\vcvars32.bat

● For IBM VisualAge C++ for Windows Version 3.6, enter:

c:\ibmcxxw\bin\setenv.bat

● For IBM VisualAge C++ for Windows Version 4, enter:

c:\ibmcppw40\bin\setenv.bat

Note:Note: If your C++ compiler is not installed on your C drive, change the path in

these commands to reflect the location of the C++ compiler on your system.

5. In the Compiler options field, enter the C compiler options for building the SQL stored procedures on the database server. Depending on the compiler you are using, do one of the following:

● For Microsoft Visual C++ Versions 5.0 and 6.0, enter the following on a single line:

cl -Ox -W2 /TC -D_X86_=1 -IC:\SQLLIB\include SQLROUTINE_FILENAME.c /link -dll -

def:SQLROUTINE_FILENAME.def /out:SQLROUTINE_FILENAME.dll C:\SQLLIB\lib\db2api.lib



● For IBM VisualAge C++ for Windows Version 3.6, enter the following on a single line:

"ilib /GI SQLROUTINE_FILENAME.def & icc -Ti -Ge- -Gm+ -W2 -IC:\SQLLIB\include SQLROUTINE_FILENAME.c /B\"/ST:64000 /PM:VIO /DLL\" SQLROUTINE_FILENAME.exp C:\SQLLIB\lib\db2api.lib"

● For IBM VisualAge C++ for Windows Version 4, enter:

"vacbld"

If you do not specify the configuration file after the vacbld command, DB2 will create the following default configuration file at the first attempt of creating any SQL procedure:

C:\SQLLIB\function\routine\sqlproc.icc

If you want to use your own configuration file, you can specify your own configuration file when setting the DB2 registry value for DB2_SQLROUTINE_COMPILE_COMMAND:

"vacbld C:\SQLLIB\function\sqlproc.icc"

Note:Note: Replace C:\SQLLIB with the actual DB2 server installation path.

The above options are the default compile commands if the DB2_SQLROUTINE_COMPILE_COMMAND is not set. To return to the default compiler options, set the value for the Compiler Command to blank.

For more command options, refer to the Release Notes (release.txt) in your DB2 installation path.

6. In the Precompiler options field, enter the precompiler options for building the SQL stored procedures on the database server. For information about precompiler options, see the DB2 Command Reference.

7. In the Debugger timeout field, enter a value to set the number of seconds before stored procedures run to completion.

8. Select the Keep files on server check box to keep intermediate files created during the SQL stored procedure build process on the database server.

9. Click OK.

10. Close the window.

11. Click Start > Programs > Avaya CT for Siebel 7 > Administrator Tool.The Avaya CT for Siebel window is displayed.

12. Click File > Configure Database Provider.The Configure Database Provider dialog box is displayed.

13. Select the DB2 database from the Select the Database Provider drop-down menu.

Building an IBM DB2 database

September 2006 39

14. Click OK.

15. Click Service > DBBuilder.The Create DB2 Database Wizard dialog box is displayed.

16. Click Next.The Select Database Options dialog box is displayed.

17. Enter a DB Name and select Create DB. Avaya recommends that you use the name CTI.

18. Click Next.The database is created, which may take some time. The Finished Creating Database dialog box is displayed.

19. Select Yes.

20. Click Next.The Finalize Database Table Structure dialog box is displayed.

21. In the Database Login Information area, enter a Login Name (usually CVCTUSER), the password, the database name created in Step 17, and the name of the database server.

22. In the Table Creation Options area, these options allows a high degree of customization that creates a database that best suits your needs. Select the desired options, which include:

● Call Database -This installs a new database that will contain the bookmark and screen transfer information for the Toolbar. If this is not installed, the agents will not be able to transfer screens or bookmarks.

● Multi-Site - This sets up the database so that it may be accessed by more than one DB2 database. If more than one Call Center will be sharing this database, be sure to select this option. Otherwise, it is not necessary.

● Queue Time - This instructs the database to store the Queue Time from an incoming call. This time will subsequently be reported to the appropriate agent. This will not function if the Call Service is not present.

● Messaging Database - This option provides the CMS Data Feed.

23. Click Next.The Database Builder creates the database. When the installation success screen appears, the installation is complete.

24. Click OK.

Tip:Tip: The Data Feed services and the Call Service must be set before this

database will function properly. Do not exit the Administrator Tool as it will be required later.



September 2006 41

Setting up the CMS Data Feed

The next step is to configure the CMS Data Feed. This is the service that extracts data from the Call Center CMS and sends it to Siebel for distribution to agents via the Siebel Marquee.

The Data Feed is a vital part of the CMS Messaging System because it provides the lifeline between CMS and Siebel. It is more than a mere link; it also translates the CMS (which is in Solaris) into a format readable by Siebel and fuses it with the labels and distribution instructions from the Messaging Database (or Call Database).

This feed is run as a service. If the service is terminated or taken down, the link between Siebel and the CMS will be severed, and the data will not appear in the marquees.



● Configuring the CMS Data Feed on page 42

● Configuring a DSN on page 45

● Preparing the CMS files on page 48

● Starting the Data Feed service on page 51


Solid knowledge of the system network is required for these tasks.

Solaris experience is helpful but not required for these tasks.



Configuring the CMS Data FeedTo configure the CMS Data Feed:

1. If the administration tool for CT for Siebel is not already open, click Start > Programs > Avaya CvCT Integration for Siebel 7 > Administrator Tool.The Avaya CT for Siebel window is displayed.

2. Click Service > CMS > CMS Data Feed Configuration.

The CMS Data Feed Configuration dialog box is displayed.

3. Click the Siebel tab.

4. Enter data in the Siebel tab as described in the following table:

Siebel tab fields Description

Siebel Login The Siebel login that has permissions to add, change, and delete Message Broadcast records.

Password The password for the user.

Encrypt Click this box to encrypt the file to an .INI file, so it will be available upon load.

Configuring the CMS Data Feed

September 2006 43

5. Click the Database tab.

Connection String The Siebel Connection String. This is the Gateway String needed to give access to the service. For example:

host=�siebel://<Gateway_Server>/<Siebel_Enterprise_Name>/SCCObjMgr_enu/<Siebel_Server>�

Note: Verify this with the Connection String setting in the [/call center] section of the Siebel eapps.cfg file.The eapps.cfg file is located at <Siebel Directory (sea7x)>\SWEApp\BIN on Siebel server machine.

Sleep Time The time, in milliseconds, when the Siebel server becomes inactive if there is no network interaction.

Enable Logging If Siebel has logging enabled, it will generate a text file (the log file) appended with system events and actions. This is optional, but would be useful for troubleshooting.

Max Log The maximum size of the log file, in kilobytes. If the limit is exceeded, Siebel deletes the oldest data from the log file to make room for the newest data.

Siebel tab fields Description



6. Enter the information for logging into the database and extracting the CMS data as described in the following table:

7. Click OK.

The CMS Data Feed is now configured. See the Avaya CT for Siebel 7 Administration Guide for information on how to create your messaging reports.

Database tab fields Description

SQL Server Enter the database server identification.

Database Name Enter the name of the CTI Database (typically CTI).

Integrated Security Select this box to use the integrated security option.

Login ID Provide the SQL or DB2 login.

Password Enter the password for the SQL or DB2 login.

Encrypt Click this box to encrypt the file to an .INI file, so it will be available upon load.

Configuring a DSN

September 2006 45

Configuring a DSNA Data Source Name (DSN) should be configured for use with Siebel. The system DSN is a system identification, rather than a domain user, that provides the Siebel server with the proper login credentials.

You must configure either an SQL DSN or a DB2 DSN. See one of the following options:

● Configuring an SQL DSN on page 45

● Configuring a DB2 DSN on page 47

Configuring an SQL DSNTo configure an SQL DSN:

1. Click Start > Settings > Control Panel > Administrative Tools (Windows 2000 / Windows 2003).

The Control Panel is displayed.

2. Select Data Sources (ODBC) (Windows 2000 / Windows 2003).

The ODBC Sources dialog box is displayed.

3. Click the System DSN tab.

4. Select the CMS Data Feed Data Source Name and click Configure.

The Microsoft SQL Server DSN Configuration dialog box is displayed.

5. Verify the server address in the Server field (a description is not required).



6. Click Next.Another Microsoft SQL Server DSN Configuration dialog box is displayed.

7. Select SQL Server Authentication and provide the Siebel login and password.

8. Click Client Configuration.

The Add Network Library Configuration dialog box is displayed.

9. Verify that TCP/IP is selected as the network library. Do not do anything further in this dialog.

10. Click OK.

Another Microsoft SQL Server DSN Configuration dialog box is displayed. This dialog displays stored procedures, ANSI identifiers, and miscellaneous database settings. Do not make any changes to this dialog.

11. Click Next.Another Microsoft SQL Server DSN Configuration dialog box is displayed that displays language settings and log file locations. Do not make any changes to this dialog box.

12. Click Finish.

The ODBC Microsoft SQL Server Setup dialog box is displayed showing all of the DSN settings.

13. Click Test Data Source.

Configuring a DSN

September 2006 47

14. The SQL Server ODBC Data Source Test dialog box is displayed. The message TESTS COMPLETED SUCCESSFULLY!, should appear at the end of the test results.

15. Click OK and exit the ODBC Connection Wizard.

16. Open the Siebel Configuration file and locate the heading titled [Server].

17. Change the value of ConnectString to CMS Data Feed.

18. Continue with Preparing the CMS files on page 48.

Configuring a DB2 DSNTo configure a DB2 DSN:

1. Click Start > Settings > Control Panel > Administrative Tools (Windows 2000).

The Control Panel is displayed.

2. Select Data Sources (ODBC) (Windows 2000).

The ODBC Sources dialog box is displayed.

3. Click the System DSN tab.

4. Select CMSDF DSN.

5. Click ConfigureThe CLI-ODBC Settings dialog box is displayed.

6. On the DataSource tab, populate the dialog box as shown:

● Data Source Name: CMS Data Feed

● UserID: <Databse UserID>

● Password: <Database Password>

7. Click OK.

8. Continue with Preparing the CMS files on page 48.



Preparing the CMS filesThe Solaris configuration must be set up within the CMS.

To prepare the CMS files:

1. Upload the Solaris files from the Avaya CT for Siebel 7 CD-ROM folder /Unix Scripts to the /tmp directory in the CMS to the FTP server. There are two files: install.ksh and install.tar. FTP install.ksh using ASCII file transfer and install.tar using binary file transfer.

2. Log in as root to the CMS.

3. Enter:

cd /tmp

4. Enter:

ls -l

Verify that the two files that were sent using FTP are present on the CMS server.

5. Enter:

chmod 755 install.ksh

6. Enter:

./install.ksh

Messages similar to the following are displayed:

Siebel CMS Reports Unpacker V1.0

Enter directory to install:(Press Return to accept default - /export/home/cms/siebel)

Preparing the CMS files

September 2006 49

7. Press Enter.Messages similar to the following are displayed:

Note:Note: The term wallboards is synonymous with CMS Data Feed.

8. Enter the IP address of the Avaya CT for Siebel server. This is the same server where you installed the CMS Data Feed application and CMS Data Pool is operating.

Messages similar to the following are displayed:

9. Enter: y

Wallboards software will be installed in the /export/home/cms/siebel directoryCreating directory /export/home/cms/siebelFixing dir permissions...Unpacking archive.....Fixing Siebel dir(s) permissions..Creating Report axcis_agCreating Report ascis_spCreating Report axcis_udCreating Report axcis_tg

Welcome to the Wallboards for Siebel Installation

This will walk you through the install and configuration of the �Wallboards on Siebel� data feed

If you wish to quit at any time, simply type �abort�.

Please enter the IP address for the�Wallboards for Siebel� NT Service:

We can now generate the dat files.Do you want to continue[y/n]?



10. The installation program requests parameter data for reports. Enter the information as described in the following table:

After the data is entered, messages similar to the following are displayed:

11. Enter: y

12. The GEM files are created and the CMS is properly configured. The CMS may now stream the data into the Data Pool.

13. Enter:

cd /export/home/cms/siebel

14. Enter:

./startall

The service starts.

Parameter data Description

ACD This is number of the ACD, which is usually 1. Refer to your CMS documentation for further details.

Refresh rate This is the frequency in seconds with which the report data is refreshed.

Agent skills1

1. This data may be entered individually (for example, 1), delimited by semicolon (for example, 1;2;3;4), or entered as a range (f or example, 1-100). Avaya recommends that you enter the full range of this parameter available on your communication server.

This is the agent split range to monitor for CMS data.

Split/skills1 This is the split ID range to monitor for CMS data.

VDNs1 This is the VDN ID range to monitor for CMS data.

Trunk group1 This is the Trunk Group ID range to monitor for CMS data.

We now have enough info to generate the gem files.Do you want to continue[y/n]?

Starting the Data Feed service

September 2006 51

Starting the Data Feed serviceThe Data Feed service must be started in the Windows operating system so that the data forwarded from the CMS server will be processed and reported.

To start the data feed service:

1. Click Start > Programs > Avaya CvCT Integration for Siebel 7 > Administrator Tool.The Avaya CT for Siebel window is displayed.

2. Click Service > Services Controller > CMS Data Feed.

The CMS Data Feed Services Controller dialog box is displayed. Data Feed has the following states:

● SERVICE_STOP_PENDING● SERVICE_STOPPED● SERVICE_RUN_PENDING● SERVICE_RUNNINGThe status should currently read SERVICE_STOPPED. In this mode, the CMS data is not being received, and the reports cannot be generated.

3. If Data Feed is running, click Stop to place the service in the SERVICE_STOP_PENDING mode. The system starts shutting down the service.

Click Refresh and the state changes to SERVICE_STOPPED when the shutdown is complete.

4. Click Start.This places the service in the SERVICE_RUN_PENDING mode and begins loading the service.

5. Click Refresh.

When the service state changes to SERVICE_RUNNING, the service is operational.

6. Click the Automatically Start on Service on Server Boot check box.

This launches the service immediately upon server reboot. Avaya recommends this for uninterrupted service.

7. Click Close.



September 2006 53

Setting up Call Service

Call Service is a special component that monitors an incoming VDN. This allows the system to track many more characteristics of the call, such as the time a call has been waiting in queue and any collected digits the customer has entered while waiting. This component is installed automatically, but may be omitted in a custom installation.

Note:Note: This is an optional component, and if a custom installation was performed

without this option, skip this chapter.



● About Call Service on page 54

● Configuring Call Service on page 55

● Starting Call Service on page 57




About Call ServiceCollected Digits and Queue Time are not normally populated in soft phones because they require an in-depth monitor of the incoming VDN. For example, Queue Time indicates to the agent how long this customer has been waiting on hold.

Collected Digits are touchtone numbers entered by the customer following prompts from a �collect� step in a call vector. There are cases where it will be helpful to retain the data.

For example, a caller is prompted for a Personal Identification Number (PIN) by the vector for routing purposes. When the call is routed, the agent may still need that PIN. Without Collected Digits, it is simply discarded when the vector routes the call. The customer may be annoyed to repeat a number already given.

Configuring Call Service

September 2006 55

Configuring Call ServiceTo configure the call service:

1. Click Start > Programs > Avaya CvCT Integration for Siebel 7 > Administrator Tool.The Avaya CT for Siebel window is displayed.

2. Click Service > Call Service > Call Service Configuration.

The Call Service Configurator dialog box is displayed.

3. Click the CTI tab and populate the dialog box with data as described in the following table:

4. Click Apply to save changes.

5. Click the VDN tab.

6. Enter a VDN to be monitored in the VDN field.

7. Select the way the VDN will be monitored: Regular or ICC.

● Regular - No additional software is required. The VDNs are monitored normally. This VDN data is stored in the VDN.DAT file.

CTI tab fields Description

Tlink The address string of the switch. If more than one is available, they are shown in the drop-down box.

User Name The Avaya CT login.

Password The password for the Avaya CT login.

Delay The cycle time to connect to the TServer.

Encrypt Select this box to encrypt the file to an .INI file, so it is available upon load.

Logging The Call Service may also record all events for the monitored VDN. If this box is selected, all VDN events are recorded to the log file.

Queue Time This option enables the monitoring of call queue time.

Message Care Click to enable the option for Message Care integration.

ICC Click to enable the creation of Internet Call Center VDNs.



● ICC - The VDN data is subject to Internet Call Center specialized fields. This VDN data is stored in the ICC.DAT file.

If the call center does not use Internet Call Center, all VDNs should be set up as Regular.

! Important:! Important:Important: VDNs may be monitored in different ways. Certain applications and

configurations may have fields that are not visible to normal VDN monitoring. Avaya Internet Call Center uses unique VDN fields. If the VDN is used, it must be specified, so that the extra fields will be read.

8. Click Add.

The VDN is now displayed in the Current VDNs field.

9. Repeat Steps 6 through 8 to add more VDNs.

10. Click the Message Care tab.

11. Enter a Database Server name for the SQL or DB2 server, a User ID, and a Password, and whether the password will be encrypted on the SQL or DB2 server.

12. Click Apply to save the changes.

13. If Queue Time Reporting is desired, click the Queue Time tab. Otherwise, continue with Step 16.

14. Enter the Data Server for the SQL or DB2 server, Database, User ID, Password, and whether the password will be encrypted on the SQL or DB2 server.

15. Click Apply.

16. Click OK.

Note:Note: Once Call Service is running, you can stop and restart it through the

Administrator Tool. Click Service > Services Controller > Call Service to stop the service.

Starting Call Service

September 2006 57

Starting Call ServiceCall Service must be started on the Windows operating system.

To start Call Service:

1. Load the Avaya CT for Siebel Administrator Tool.

2. Click Service > Services Controller > Call Service.

The Call Service Services Controller dialog box is displayed. Call Service has the following states:

● SERVICE_STOPPED● SERVICE_RUNNING● SERVICE_START_PENDINGThe status should currently read SERVICE_STOPPED. In this mode, calls are not being monitored.

3. If Call Service is running, click Stop to place the service in the SERVICE_STOP_PENDING mode. The system starts shutting down the service.

Click Refresh afterwards and the state changes to SERVICE_STOPPED when the shutdown is complete.

4. To start the service, click Start.This places the service in the SERVICE_START_PENDING mode and begins loading the service.

5. Click Refresh.

When the service state changes to SERVICE_RUNNING, the service is operational.

6. Select the Automatically Start on Service on Server Boot check box.

This launches the service immediately upon server reboot. Avaya recommends this for uninterrupted service.

7. Click Close.



September 2006 59

Registering and administering the product

The call center server has now been set up with the necessary components and the servers have been configured the Avaya CT for Siebel. However, you must now register and administer the product.


● Registering the product on page 59

● Administering the product on page 60

Registering the productNote:

Note: These steps are not applicable for Avaya AE Services.

To register the product:

1. Write down your TServer link and IP address.

2. Write down your backup TServer link and IP address (if applicable).

3. Write down the version of Siebel you are running.

4. Call Avaya Professional Services at 1-800-242-2121 in the United States and +1-720-444-9990 outside the United States.

5. Give the representative your TServer, backup TServer, and Siebel version information.

6. Provide the �sold-to� information or a Functional Location (FL) number.

7. A DAT file is sent via e-mail.

8. Copy the DAT file to the Siebel Communication server.

9. Specify the DAT file location within the Driver:LicensePath parameter. See the chapter �Configuration parameters� in the Avaya CT for Siebel 7 Administration Guide.

Registering and administering the product


Administering the productDo the following to administer the product:

1. Set up any additional Agent States. This is described in the Avaya CT for Siebel 7 Administration Guide.

2. If the Send All Calls option was selected, be sure the voice mail extension is functioning.

3. Individual stations may be modified inside Siebel by altering the Parameters, Commands, and Events. See the Avaya CT for Siebel 7 Administration Guide for a complete list of these Avaya CT for Siebel settings.

4. Add agent telesets to Siebel and Avaya CT. The Avaya CT for Siebel 7 Administration Guide provides an overview of this procedure.

September 2006 61

Glossary

Application Enablement Services (AE Services)

Application Enablement Services (AE Services) provides an enhanced set of APIs, protocols and Web services. It merges DLG, CVLAN, Avaya CT, and CMAPI into a single platform that provides a communication channel to all Avaya Communication Manager Media Servers.

Communication server An Avaya telephone communication server (also know as a switch) is a communication server that includes a DEFINITY ECS or a server using Avaya MultiVantage software.

Computer Telephony Integration (CTI)

Computer Telephony Integration (CTI) technology allows interactions on a telephone and a computer to be integrated or coordinated.

TServer TServer (also known as Avaya CT Server) is the adjunct processor that performs call monitoring and control functions, security database functions, and link management.

TServer


September 2006 63

IndexAadministering the product . . . . . . . . . . . . . 60AE Services . . . . . . . . . . . . . . . . . . . . 61application enablement services . . . . . . . . . . 61Avaya AE Services documentation . . . . . . . . . . 6Avaya CT documentation . . . . . . . . . . . . . . 6Avaya CT for Siebel documentation. . . . . . . . . . 7Avaya CT for Siebel server hardware and software

requirements. . . . . . . . . . . . . . . . . . . 12

Bbuilding

database. . . . . . . . . . . . . . . . 33, 35, 37

CCall Service . . . . . . . . . . . . . . . . . . . . 54checklist

building a database. . . . . . . . . . . . . . . 34permissions . . . . . . . . . . . . . . . . . . 20preinstallation . . . . . . . . . . . . . . . . . 19server installation. . . . . . . . . . . . . . . . 10

communication server . . . . . . . . . . . . . . . 61communication server documentation. . . . . . . . . 6computer telephony integration . . . . . . . . . . . 61configuring

Call Service . . . . . . . . . . . . . . . . . . 55CMS Data Feed . . . . . . . . . . . . . . . . 42DB2 DSN . . . . . . . . . . . . . . . . . . . 47DSN . . . . . . . . . . . . . . . . . . . . . . 45SQL DSN . . . . . . . . . . . . . . . . . . . 45

CTI . . . . . . . . . . . . . . . . . . . . . . . . 61

Ddocumentation

Avaya AE Services . . . . . . . . . . . . . . . . 6Avaya CT . . . . . . . . . . . . . . . . . . . . 6Avaya CT for Siebel . . . . . . . . . . . . . . . 7communication server . . . . . . . . . . . . . . 6Siebel Enterprise Applications. . . . . . . . . . . 7

Iinstallation planning . . . . . . . . . . . . . . . . . 9

installingAvaya CT for Siebel . . . . . . . . . . . . . . . 21Avaya CT for Siebel 7 Integration . . . . . . . . 23Change State applet . . . . . . . . . . . . . . 31

Mmodifying

Avaya CT for Siebel 7 Integration . . . . . . . . 27

Nnetwork diagram . . . . . . . . . . . . . . . . . . 15

Ooptional servers . . . . . . . . . . . . . . . . . . 12

Ppermissions checklist . . . . . . . . . . . . . . . . 20planning for installation . . . . . . . . . . . . . . . . 9preinstallation checklist . . . . . . . . . . . . . . . 19preparing the CMS files. . . . . . . . . . . . . . . 48

Rregistering the product . . . . . . . . . . . . . . . 59related documentation . . . . . . . . . . . . . . . . 6removing

Avaya CT for Siebel 7 Integration . . . . . . . . 29repairing

Avaya CT for Siebel 7 Integration . . . . . . . . 26required servers . . . . . . . . . . . . . . . . . . 11requirements

Avaya CT for Siebel server hardware and software 12Avaya CT Server hardware and software . . . . . 13communication server . . . . . . . . . . . . . . 14database server hardware and software . . . . . 14reviewing hardware and software . . . . . . . . 11

Sserver installation checklist . . . . . . . . . . . . . 10server side components . . . . . . . . . . . . . . 16setting up

Call Service. . . . . . . . . . . . . . . . . . . 53


Change State applet . . . . . . . . . . . . . . 31Data Feed . . . . . . . . . . . . . . . . . . . 41

Siebel Enterprise Applications documentation . . . . . 7starting

Call Service. . . . . . . . . . . . . . . . . . . 57Data Feed service on the Siebel server . . . . . . 51

Wwhere to install the components . . . . . . . . . . . 22

Documents

Avaya CT for Siebel 7 · Preface 6 Avaya CT for Siebel Installation Guide Related documentation This section provides a list of documents related to the switch, Avaya CT, Avaya CT