Professional Documents
Culture Documents
Reference Manual
The information contained herein is proprietary and confidential and cannot be disclosed or duplicated
without the prior written consent of Genesys Telecommunications Laboratories, Inc.
Copyright 20032008 Genesys Telecommunications Laboratories, Inc. All rights reserved.
About Genesys
Genesys Telecommunications Laboratories, Inc., a subsidiary of Alcatel-Lucent, is 100% focused on software for call
centers. Genesys recognizes that better interactions drive better business and build company reputations. Customer
service solutions from Genesys deliver on this promise for Global 2000 enterprises, government organizations, and
telecommunications service providers across 80 countries, directing more than 100 million customer interactions every
day. Sophisticated routing and reporting across voice, e-mail, and Web channels ensure that customers are quickly
connected to the best available resourcethe first time. Genesys offers solutions for customer service, help desks,
order desks, collections, outbound telesales and service, and workforce management. Visit www.genesyslab.com for
more information.
Each product has its own documentation for online viewing at the Genesys Technical Support website or on the
Documentation Library DVD, which is available from Genesys upon request. For more information, contact your sales
representative.
Notice
Although reasonable effort is made to ensure that the information in this document is complete and accurate at the
time of release, Genesys Telecommunications Laboratories, Inc., cannot assume responsibility for any existing errors.
Changes and/or corrections to the information contained in this document may be incorporated in future versions.
Trademarks
Genesys, the Genesys logo, and T-Server are registered trademarks of Genesys Telecommunications Laboratories,
Inc. All other trademarks and trade names referred to in this document are the property of other companies. The
Crystal monospace font is used by permission of Software Renovation Corporation, www.SoftwareRenovation.com.
Telephone
+888-369-5555 or +506-674-6767
support@genesyslab.com
+44-(0)-1276-45-7002
support@genesyslab.co.uk
Asia Pacific
+61-7-3368-6868
support@genesyslab.com.au
Japan
+81-3-6361-8950
support@genesyslab.co.jp
Prior to contacting technical support, please refer to the Genesys Technical Support Guide for complete
contact information and procedures.
Released by
Genesys Telecommunications Laboratories, Inc. www.genesyslab.com
Document Version: 46ge_ref_09-2008_v4.6.001.00
Table of Contents
Preface
................................................................................................................... 5
Intended Audience..................................................................................... 6
Chapter Summaries................................................................................... 6
Document Conventions ............................................................................. 7
Related Resources .................................................................................... 9
Making Comments on This Document .................................................... 10
Chapter 1
Chapter 2
Bundled Products................................................................................. 21
Genesys Integrated Products .................................................................. 21
Framework 7.6......................................................................................... 22
Layers ................................................................................................. 22
Documentation.................................................................................... 23
Universal Routing 7.6 .............................................................................. 24
Universal Routing Documentation ...................................................... 25
Voice Treatment Option 7........................................................................ 25
Components ....................................................................................... 26
VTO Demo Mode................................................................................ 26
VTO Documentation ........................................................................... 27
IVR Interface Option 7.5 .......................................................................... 28
IVR Interface Option Documentation .................................................. 29
Multimedia 7.6 ......................................................................................... 29
Express Voice ..................................................................................... 29
Express Multimedia ............................................................................ 29
Multimedia Documentation ................................................................. 30
Reporting ................................................................................................. 30
CCPulse+ 7.5 ..................................................................................... 31
Reporting Documentation ................................................................... 33
Reference Manual
Table of Contents
Chapter 3
Index
................................................................................................................. 81
Preface
Welcome to the Genesys Express 4.6 Reference Manual. This document
provides you with information on the solutions and applications that are a part
of Genesys Express 4.6.
This document is valid only for the 4.6 release(s) of this product.
Note: For versions of this document created for other releases of this product,
Express CTI, Express Voice, and Express Multimedia belong to the Genesys
Express family of ready-to-run, contact center solutions, which offer the
flexibility of a tiered packaging system. The family includes the following
suites:
Reference Manual
Preface
Intended Audience
Intended Audience
This document is primarily intended for:
Chapter Summaries
In addition to this preface, this document contains the following chapters:
Preface
Document Conventions
Document Conventions
This document uses certain stylistic and typographical conventions
introduced herethat serve as shorthands for particular kinds of information.
You will need this number when you are talking with Genesys Technical
Support about this product.
Type Styles
Italic
In this document, italic is used for emphasis, for documents titles, for
definitions of (or first references to) unfamiliar terms, and for mathematical
variables.
Examples:
A customary and usual practice is one that is widely accepted and used
within a particular industry or profession.
The formula, x +1 = 7 where x stands for . . .
Monospace Font
A monospace font, which looks like teletype or typewriter text, is used for
all programming identifiers and GUI elements.
This convention includes the names of directories, files, folders, configuration
objects, paths, scripts, dialog boxes, options, fields, text and list boxes,
operational modes, all buttons (including radio buttons), check boxes,
commands, tabs, CTI events, and error messages; the values of options; logical
arguments and command syntax; and code samples.
Examples:
Reference Manual
Preface
Document Conventions
The following table presents the complete set of error messages T-Server
distributes in EventError events.
Monospace is also used for any text that users must manually enter during a
configuration or installation procedure, or on a command line:
Example:
Square Brackets
Square brackets indicate that a particular parameter or value is optional within
a logical argument, a command, or some programming syntax. That is, the
parameters or values presence is not required to resolve the argument,
command, or block of code. The user decides whether to include this optional
information. Here is a sample:
smcp_server -host [/flags]
Angle Brackets
Angle brackets indicate a placeholder for a value that the user must specify.
This might be a DN or port number specific to your enterprise. Here is a
sample:
smcp_server -host <confighost>
Preface
Related Resources
Related Resources
Consult these additional resources as necessary:
Reference Manual
Genesys Express 4.6 Users Guide. Written for agents, supervisors and
system administrators, this guide contains step-by-step instructions for
performing common contact center tasks. It also includes instructions for
installing Genesys Desktop SIP Endpoint if an agent is working in an
environment that uses SIP Server to handle interactions.
IVR Interface Option 7.5 IVR Server System Administrators Guide. This
guide describes how to configure, install, and use IVR Server.
Genesys 7 Migration Guide. After using Genesys Express, you may want
to move out of the Express environment into a broader range of Genesys
software. Genesys has a documented migration strategy for each software
release (for example, Framework, Enterprise Routing, Reporting, and so
on). Please refer to the applicable portion of the Genesys Migration Guide,
or contact Genesys Technical Support for additional information.
Preface
Release Notes and Product Advisories for this product and other associated
products, which are available on the Genesys Technical Support website at
http://genesyslab.com/support.
10
Chapter
Software Components
Genesys Express components and files are grouped into these categories:
Reference Manual
11
Software Components
Application
Type
Express Path
(Start >
Programs >
Genesys
Solutions > ...)
Version
Remarks
cfg_dbserver
DB Server
(independent)
Framework
7.6
Runs
independently
from
Configuration
Server
Configuration Server
Configuration
Server
Framework
7.6
Installed as a
Service
Configuration Manager
Configuration
Manager
Framework
7.6
Management Framework
Configuration Wizard
None
Framework
7.6
StatServer
Stat Server
Framework
7.6
Installed as a
Service
LogDBServer
DB Server
Framework
7.6
Installed as a
Service
Message Server
Message
Server
Management Layer
7.6
Installed as a
Service
No
application
type in
Configuration
Layer
Management Layer
7.6
Installed as a
Service
12
Software Components
Application
Type
Express Path
(Start >
Programs >
Genesys
Solutions > ...)
Version
Remarks
SolutionControlServer
Solution
Control
Server
Management Layer
7.6
Installed as a
Service
Solution
Control
Interface
Management Layer
7.6
DataSourcerDBServer
DB Server
Framework
7.6
Installed as a
Service
Stat Server
Framework
7.6
Installed as a
Service
CC Analyzer
Data Sourcer
Reporting 7.2
7.2
Installed as a
Service
ETL Proxy
Not applicable
7.2
CC Analyzer
Data Mart
Reporting 7.2
7.2
ETL
Assistant
Reporting 7.2
7.2
CCPulse+
Reporting 7.5
7.5
CC Analyzer
Data
Modeling
Assistant
Reporting 7.2
7.2
Installed as a
Service
Reference Manual
13
Software Components
Application
Type
Express Path
(Start >
Programs >
Genesys
Solutions > ...)
Version
Remarks
ERSDBServer
DB Server
Framework
7.6
Installed as a
Service
Universal
Routing
Server
Routing
7.6
Installed as a
Service
Interaction
Routing
Designer
Routing
7.6
Delivery
Server
Delivery Server
6.5
Installed as a
Service
Web Server
GenesysDesktop >
Web
7.6
Installed as a
Service
Application
Type
MCR EMailServerJava
Version
Remarks
7.6
Installed as a
Service
Interaction
Server
Multi-Channel Routing
7.6 > Interaction Server
7.6
Installed as a
Service
MCR InteractionServer
DBServer
DB Server
Framework
7.6
Installed as a
Service
MCR ClassificationServer
Classification
Server
Multi-Channel Routing
7.6 > Classification
Server
7.6
Installed as a
Service
14
Express Path
(Start > Programs >
Genesys Express
Solutions > ...
Software Components
Application
Type
Express Path
(Start > Programs >
Genesys Express
Solutions > ...
Version
MCR KnowledgeManager
Knowledge
Manager
Multi-Channel Routing
7.6 > Knowledge
Manager
7.6
MCR
UniversalContactServer
Contact
Server
Multi-Channel Routing
7.6 > Universal Contact
Server
7.6
MCR
UniversalContactServer
Manager
Contact
Server
Manager
Multi-Channel Routing
7.6 > Universal Contact
Server Manager
7.6
No
application
type in
Configuration
Manager
7.6
MCR Extension
No
application
type in
Configuration
Manager
7.6
No
application
type in
Configuration
Manager
7.1
Common Wizard
Component set
No
Genesys Wizard Manager
application
> Genesys Wizard
type in
Manager
Configuration
Manager
7.6
Remarks
Installed as a
Service
Reference Manual
15
Software Components
listed in Table 3.
Description
On Installation
CD?
Operating System
No
No
Yes
For information, go to
www.microsoft.com/sql/editions/express/default.mspx.
Web Container
Yes
Yes
License Manager
C:\Flexlm\)
E-mail Server
(POP3 and
SMTP)
(Express
Multimedia only)
Yes
16
Software Components
Installation Directory
Version
7.6.0
7.6.0
C:\GCTI\MCR\Chat Server
7.6.0
Voice Treatment Option (optional for Express Voice and Express Multimedia)
Voice Treatment Server
C:\GCTI\VTServer
7.0.1
C:\GCTI\VTManager
7.0.1
TServer_IVR
C:\GCTI\IVRIServer
7.5.0
I-Server
C:\GCTI\IVRIServer
7.5.0
Not Applicable
7.6.0
7.6.0
7.6.0
C:\GCTI\OutboundContactServerDBServer
7.6.0
C:\GCTI\CPDServer
7.6.0
C:\GCTI\CallConcentratorDBServer
7.6.0
Call Concentrator
Call Concentrator DBServer
Reference Manual
17
Software Components
Installation Directory
Version
Call Concentrator
C:\GCTI\CallConcentrator
7.0.0
Generic T-Server
C:\GCTI\Generic_Tserver
6.5.1
C:\GCTI\Simulator\TestSim\
6.5.3
C:\GCTI\Simulator\
6.5.3
C:\GCTI\Simulator\PbxV\
6.5.3
Aspect ACD
C:\GCTI\TServerAspect
7.6.0
Alcatel A4200
C:\GCTI\TServerA4200
7.0.2
Alcatel A4400
C:\GCTI\TServerA4400
7.6.0
Cisco CallManager
C:\GCTI\TServerCiscoCM
7.6.0
C:\GCTI\CiscoSM
7.6.0
Definity G3 ECS
C:\GCTI\TServerG3
7.6.0
Ericsson MD110
C:\GCTI\TServerMD110
7.6.0
Nortel Meridian
C:\GCTI\TServerSuccession
7.6.0
Nortel Symposium
C:\GCTI\TServerSuccession
7.6.0
Siemens Hicom300/HiPath
4000 CSTA I
C:\GCTI\TServerHic300Hi4000
7.6.0
NEC NEAX
C:\GCTI\TServerNEAX
7.6.0
NEC OpenWorXc
C:\GCTI\TserverOpenWorX
7.2.0
C:\GCTI\NECProxy
7.0.2
Simulation Solution
18
Installation Directory
Version
SIP Server
C:\GCTI\TServerSIP
7.6.0
C:\GCTI\SIPSM
7.6.0
a. The T-Server application name created when you choose a particular switch for
production is called VoiceTserverProduction.
b. See the Genesys 7 Supported Media Interfaces Reference Manual, located on the
Technical Support website, for information on these supported switches and their
version numbers.
c. NEC OpenWorX is composed of NEC NEAX and NEC Proxy.
Express suite you purchased. See Table 3 in the Genesys Express 4.6
Deployment Guide for a list of products installed for your suite.
Framework 7.6
Universal Routing 7.6
Voice Treatment Option 7.0
IVR Interface Option 7.5
Multimedia 7.6 (formerly Multi-Channel Routing)
Reporting
7.5: CCPulse+ and Stat Server
7.2: Data Sourcer, Data Mart, Data Modeling Assistant, and reporting
templates
Call Concentrator 7
Genesys Desktop 7.6
SIP Server 7.6
Outbound 7.6
Note: If you purchased Genesys Voice Platform, Genesys Express 4.6 can
Reference Manual
19
If you purchased Genesys Express directly from Genesys and have a signed
Genesys Support Contract, please consult the Technical Support Guide
available on the Genesys Documentation Library DVD for instructions on
obtaining technical support for these products.
If you purchased the software from a value-added-reseller (VAR), please
contact the VAR for technical support.
Help Desk
You can also call the Genesys Technical Support Help Desk at +888-3695555.
Contact the Genesys Technical Support Help Desk to be put on a product
notification list for all release notes, white papers, and other application
information.
20
Chapter
Bundled Products
This chapter describes the Genesys products that are part of Genesys Express
and includes these sections:
Genesys Integrated Products, page 21
Framework 7.6, page 22
Universal Routing 7.6, page 24
Voice Treatment Option 7, page 25
IVR Interface Option 7.5, page 28
Multimedia 7.6, page 29
Reporting, page 30
Call Concentrator 7, page 34
Outbound Contact 7.6, page 34
Genesys Desktop 7.6, page 36
z
you purchased.
Provided for a standard hardware and software platform, the products are fully
installed and integrated on one server.
Reference Manual
21
Framework 7.6
Framework 7.6
Genesys Framework is the foundation for all Genesys-based interaction
management systems. It provides these functions:
Configuration (see page 72) centralizes processing and storage of all the
data required for Genesys solutions to work within a particular
environment.
Access Control (see page 76) sets and verifies user permissions for access
to solution functions and data.
Solution Control (see page 37) starts and stops solutions and monitors their
status. The Solution Control Interface (SCI) performs this function for
Genesys Express.
Alarm Processing (see page 72) defines and manages conditions critical to
solution operation.
Local Control Agent (LCA) (see page 47) starts and stops applications,
detects failures, and communicates application and host status to the
Management Layer.
Layers
The Genesys Framework consists of four layers. Each layer has associated
software components and depends on the layers below it to work properly:
1. The Configuration Layer (see page 45) processes and stores all the data
required for running Genesys solutions in a particular environment; it
notifies clients of any configuration changes. The Configuration Layer also
controls user access to a solutions functions and data.
2. The Management Layer (see page 37) controls the startup and status of
solutions, logging of maintenance events, generation and processing of
alarms, and management of application failures. The Solution Control
Interface (Figure 6 on page 48) is part of the Management Layer.
22
Framework 7.6
4. The Services Layer generates the statistical data used for interaction
processing and contact center reporting, enables solutions to communicate
with various database management systems (DBMSs), and provides
interfaces for desktop integration with Genesys-based interaction
management systems.
Stat Server (see page 50) tracks real-time states of interaction
management resources and collects statistics about contact center
performance. Genesys solutions use the statistical data for more
intelligent real-time interaction management, and the Reporting Layer
uses the data to generate real-time and historical contact center reports.
DB Server (see page 45) provides the interface between Genesys
applications and the database management system where the databases
for solutions operations reside.
Desktop APIs provide tools for the integration of customer agent
desktop applications with Genesys-based interaction management
systems.
Documentation
The Genesys Documentation Library DVD supplies the following Framework
documentation. This list is not comprehensive.
Simulator Documents
Framework 7.6
Reference Manual
23
IP T-Servers
24
Reference Manual
25
Transfer the customer to the most appropriate agent queue based on both
entered-digits response and account history.
Play one or more voice messages if the caller waits for a specified period,
defined by one or more timeouts.
You can write and store any number of custom scripts (see Figure 12 on
page 57) and specify which treatment script a call receives in routing
strategies.
Components
VTO has two main components, Voice Treatment Server (VT Server) and
Voice Treatment Manager (VT Manager), and one minor component,
VTPhone.
1. VT Server (see page 56) runs as a Windows Service that supports the
actual processing of the calls using identified treatment scripts. VT Server
functions with T-Server, Universal Routing Server, and Configuration
Server. Genesys Express uses version 7.0.
2. VT Manager (see page 56) is the user interface you use to create/edit voice
treatment scripts for incoming calls and manage individual voice files.
Genesys Express uses version 7.0.
3. VTPhone (see page 58) is the user interface that imitates a callers phone
for demonstrating what happens when calls are routed to VT Server for
voice treatments.
Note: VTO provides voice-assisted service as well as call parking, but it is
26
Generic
T-Server
VT Server
Switch
Simulator
Windows audio
subsystem
VTPhone
Caller
The component, VTPhone, imitates a callers phone set to enable VTO Demo
Mode to model incoming calls.
See VTPhone on page 58 for more information about VTPhone. See the
Genesys Express 4.6 Users Guide for information about using VTPhone in a
demonstration.
VTO Documentation
The Genesys Documentation Library DVD supplies the following Voice
Treatment Option 7 documentation:
Reference Manual
27
IVR Server uses the standard 7.5 T-Library for interactions. IVR Server
supports connection to both the regular T-Server and the IVR T-Server
function of an IVR Server operating in IVR-In-Front mode.
28
Multimedia 7.6
IVR Interface Option 7.5 IVR Driver for WVR for AIX System
Administrators Guide
IVR Interface Option 7.5 IVR Driver for WVR for Windows System
Administrators Guide
IVR Interface Option 7.5 IVR Driver for Edify System Administrators
Guide
Multimedia 7.6
Multimedia is a group of software components designed to facilitate Internetbased communication between a visitor to a website and the company who
publishes the site.
Express Voice
Express Voice users are given the option to install two Multimedia
components, Universal Contact Server and Universal Contact Server Manager.
Contact Server enables you to use the Contact Database to handle customer
calls. Contact Database stores all information about customer contacts
including names, telephone numbers, agent comments about a particular
customer call, and so on. Contact Server Manager is the GUI application for
setting archiving and pruning functions for the Contact Database.
Express Multimedia
Express Multimedia users are provided with the e-mail functionality of
Multimedia automatically when they install the suite. You can configure
E-mail Server to screen e-mail messages for content and send automatic
responses when appropriate, with or without handling by an agent. If E-Mail
Server determines that an agent response is required, it routes the message to
an appropriate agent or queue based on routing criteria specified in Universal
Routing Server.
Reference Manual
29
Reporting
Features
The following Multimedia features support this advanced e-mail and chat
functionality of Express Multimedia:
E-mail Server JavaThis server interfaces with the enterprise mail server
and the Genesys Web API Server, bringing in new e-mail interactions and
sending out replies or other outbound messages.
Chat ServerThis server works with Web API Server to open, conduct,
and close chat interactions between agents and customers.
E-mail via webWeb visitors may submit e-mail to a contact center using
an e-mail client.
Multimedia Documentation
The Genesys Documentation Library DVD supplies the following Multimedia
documentation:
Reporting
Genesys Reporting is comprised of one product, CCPulse+, that provides
contact center managers with a business view of operational status and
30
Reporting
Data Sourcer 7.2 (see page 64) stores statistics from the Services Layer and
configuration updates from the Configuration Layer in a temporary
database called ODS (Operational Data Storage).
The Reporting Database (see page 69) stores collected data for analysis
and presentation through CCPulse+ historical reports.
CCPulse+ 7.5
CCPulse+ provides both real-time and historical reporting.
Real-Time Reporting
From a real-time reporting perspective, CCPulse+ enables monitoring
interactions among CTI entities and presents customizable views of contact
center objects. Using CCPulse+, you can monitor the current state and activity
of objects in the contact center to make decisions about staffing, scheduling,
and call-routing strategies.
CCPulse+ monitors agent performance using the Genesys components.
Drawing on data from the Stat Server and Configuration Server, CCPulse+
receives data from T-Servers for the switch.
Once CCPulse+ is connected to Configuration Server and Stat Server,
CCPulse+ monitors status and statistics related to contact center objects
(agents, agent groups, queues, route points) and displays them on the
supervisors desktop.
The major features of CCPulse+ for real-time reporting include:
Reference Manual
31
Reporting
Historical Reporting
In CCPulse+, contact center managers can view reports that provide historical
information about:
32
Reporting
application data is sourced from Stat Server and Configuration Server, and
loaded into Operational Data Storage (ODS). From the ODS, raw data is
extracted, transformed, and loaded to a Data Mart by the Extraction
Transformation Loading (ETL) Runtime Engine, which is designed to
support static as well as ad hoc reporting.
Reporting Documentation
The Genesys Documentation Library DVD supplies the following Reporting
documentation:
Note: A Help file for each of the following applications is available in the
Reference Manual
33
Call Concentrator 7
Call Concentrator 7
Call Concentrator 7.0 works with certain Genesys Framework components to
collect and record call data in your enterprise, whether single tenant or
multitenant. Call Concentrator is a Reporting product that is designed to
provide data for call-based reporting. That is, you can trace the course of
specific calls, collect data about them, and create reports based on that
information.
Call Concentrator functionality consists of two basic processes: interpreting
the data it receives, and recording the data after it is interpreted. Call
Concentrator collects two types of data:
Call Concentrator stores call and call segment data in a number of database
tables, each of which maintains records of a different aspect of the interaction.
34
Collection efforts
Telemarketing
Fund raising
Market research and surveys
Emergency notifications
Product promotions
Recalls
OCM
Outbound Contact Server (OCS) is a dialing and pacing engine that supports
different dialing modes depending on customer business needs. OCS performs
these functions:
Manage campaigns
Outbound Contact Manager (OCM) is the GUI client for call center managers
to perform these functions:
CPD Server
Reference Manual
35
Chat
36
Chapter
Management Layer
The Framework 7.6 Management Layer enables you to access, view, and
control the Genesys integrated products. It has these components:
Reference Manual
37
Note: For more information about fault management and the Management
38
Reference Manual
39
Menu bar
Toolbar
Shortcuts pane
List pane
Tree view
SCI Menus
The main SCI menu bar contains File, Action, View, and Help menus. The
next section summarizes the items found on each of these menus.
Note: For complete information on each menu item as well as SCI window
File Menu
These commands are available from the File menu:
40
Open
Print Setup
Reconnect
Recent Files
Exit
Closes the session with SCI and shuts down the connection to
the Log Database, Solution Control Server, and Configuration
Server.
Action Menu
These commands are available from the Action menu:
Start
Stop
Find
Refresh
View Menu
These commands are available from the View menu:
Summary
Active Alarms
Alarm Conditions
Hosts
Applications
Solutions
Centralized Log
Reference Manual
Shortcuts Bar
Items Tree
Details Pane
Toolbar
Status Bar
Options
41
Help Menu
The Help menu offers help on using SCI through the Contents, Search, and
Index commands. It also opens the About Solution Control Interface
window, which contains application version and copyright information.
Simulation
Production (once configured for your site-specific requirements)
You can work in one mode a time.
Figure 3 on page 40 shows the Simulation and Production solutions in the SCI
starting window. Each mode uses its own T-Server (VoiceTServerSimulation
and VoiceTServerProduction as listed in Table 8 on page 74).
The capability to switch between Simulation and Production modes allows you
to make changes and test them in the Simulation mode without changing the
Production setup. Once changes test successfully in the Simulation solution,
you can make those same changes to the Production solution.
Startup Priority
NECProxy
42
Startup Priority
GVP
12
12
20
CPD
21
22
31
Reference Manual
32
33
34
35
36
40
Genesys Desktop
41
50
51
52
55
56
43
Startup Priority
57
CallConcentrator
58
Note: If an application fails to start, the application with the next startup
Framework Components
If necessary, refer to page 22 for a review of Framework. This section
summarizes the Framework applications.
44
SOLUTIONS
Services Layer
Media Layer
Management Layer
Configuration Layer
Figure 4: Framework Architectural Layers
DB Server (cfg_dbServer)
As part of the Configuration Layer (see page 22), DB Server provides the
interface between Genesys applications and the database management system
where the operational databases for applications reside (see page 69).
DB Server for Genesys Express functions with the database engine Microsoft
SQL Server. For more information on DB Server and databases, see the
Framework 7.6 Deployment Guide and the Framework 7.6 DB Server Users
Guide on the Genesys Documentation Library DVD
For an architectural diagram of this layer, see Figure 5.
Note: Genesys Express 4.6 supports Microsoft SQL Server 2000 with
Configuration Server
As part of the Configuration Layer, Configuration Server provides centralized
access to the GCTI76 Configuration Database (page 71) based on permissions
that you can set for any user to any configuration object. Configuration Server
Reference Manual
45
also maintains the common logical integrity of configuration data and notifies
applications of changes made to the data. For an architectural diagram, see
Figure 5.
Configuration Manager
Configuration Manager provides an interface for viewing/manipulating
configuration objects and other data in the GCTI76 database. For an
architectural diagram of the Configuration Layer that includes this component,
see Figure 5.
DB
Server
Configuration
Database
Configuration
Manager
Management
Layer
Configuration
Server
Media
Layer
Services
Layer
Solution
Deployment
Wizards
SOLUTIONS
Log DB Server
As part of the Management Layer (see page 22), Log DB Server is attached to
Message Server (see Figure 6) and Configuration Server (see Figure 5). Log
DB Server stores all messages from all of the applications so that Message
Server can go through the logs and look for any alarms (see page 72). Figure 6
shows an architectural diagram.
46
Note: For more information on Log DB Server, see the Framework 7.6 DB
Message Server
As part of the Management Layer (see page 22), Message Server provides
centralized processing and storage of every applications maintenance events.
Events are stored as log records in the genesys_log database (see page 71)
where they are available for further centralized processing. Message Server
also checks for log events configured to trigger alarms. If a match is detected,
the alarm is sent to Solution Control Server for immediate processing. Figure 6
shows an architectural diagram.
Note: For more information on Message Server, see the Framework 7.6 DB
Reference Manual
47
Centralized Log
Database
DB
Server
Solution
Control
Interface
Message
Server
Solution
Control
Server
Network
Management
System
SOLUTIONS
Note: For more information on Solution Control Server, see the Framework
Voice T-Server
As part of the Media Layer (see page 22), Voice T-Server (Telephony Server)
provides an interface to/from traditional telephony systems. It understands
both the switch and the telephony-enabled applications. Voice T-Server
establishes communication with the underlying PBX using an interface that
allows the monitoring and control of telephony services via computer. In
effect, this means that client workstations connected to the telephony server
can access PBX functionality within software applications. For an architectural
diagram, see Figure 7.
48
Non-voice
Media Server
Interaction
Server
Traditional Telephony
SIP Telephony
T-Server
SIP Server
SOLUTIONS
Figure 7: Media Layer Architecture
As described on page 42, Genesys Express allows you to work in either the
Simulation or Production modes. Each mode uses its own T-Server
(VoiceTServerSimulation and VoiceTServerProduction, as listed in Table 8 on
page 74).
Note: If you want to work in the Simulation mode, after deploying Genesys
Express 4.6, you must also install the Standard Model Environment,
which configures the VoiceTServerSimulation. See the Genesys
Express 4.6 Standard Model Environment Users Guide for
information.
The CD installation process, described in the Genesys Express 4.6 Deployment
Guide, prompts you to select the switch type that will be used in the Production
environment. The switch types listed in the Deployment Wizard are Nortel
Meridian, Nortel Symposium, Avaya Communication Manager (formerly
called Definity ECS G3), Alcatel A4400, Ericsson MD110, and NEC NEAX,
NEC OpenWorX (includes NEC NEAX and NEC Proxy), Cisco CallManager,
Aspect ACD, Alcatel A4200, Siemens Hicom 300/HiPath 4000.
Reference Manual
49
Note: For more information on Voice T-Server, see Figure 13 on page 58 and
the Sample Interaction Flow on page 53. Also see the Framework
7.6 Configuration Options Reference Manual and the Genesys Express
4.6 Deployment Guide on the Genesys Documentation Library DVD.
Also see the appropriate Genesys reference manual for the T-Server
you deployed for Genesys Express.
Stat Server
Note: Genesys Express uses two Stat Servers: Stat Server for routing, and
Media
Layer
DB
Server
Database
SOLUTIONS
Note: For more information on Stat Server, see Sample Interaction Flow on
page 53. Also see the Framework 7.6 Stat Server Users Guide on the
Genesys Documentation Library DVD.
50
Note: The Test Simulator application object is called Switch Simulator in the
Simulation solution.
The Test Simulator is accompanied by:
Generic T-ServerA special edition of the Genesys T-Server for use with
the Test Simulator.
Contact Center Activity Simulator (CCAS)A client application (of TServer) that simulates events in a contact center, including answering and
transferring calls, attaching data, and routing calls.
Note: For more information on Test Simulator, see the 6.5 Genesys Simulator
Test Toolkit Users Guide and the 6.5 Genesys Simulator Test Toolkit
Generic T-Server Reference Manual on the Genesys Documentation
Library DVD.
Reference Manual
51
ERS DB Server
This component is the connection point between Universal Routing Server and
the Genesys_ERS database (see page 71).
Note: For more information, see the Universal Routing documentation listed
52
Universal
Routing
Server
T-Server
VT Server
Stat
Server
DB Server
Agent DN
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
Call Flow
1. A customer calls the contact center and the interaction enters the premise
PBX switch system.
2. The switch informs T-Server of the calls arrival and asks T-Server how to
handle the call.
Note: The exact details of how the call is transferred depend on how you
configured this.
Reference Manual
53
54
Agent availability.
Note: For more information on IRD, see the Universal Routing 7.6 Reference
Reference Manual
55
VTO Components
During deployment of Express Voice or Express Multimedia, you have the
option to install VTO (page 26). The VTO components include Voice
Treatment Server (VT Server), Voice Treatment Manager (user interface), and
VTPhone.
56
Note: For more information, see the Voice Treatment Option 7 Voice
Reference Manual
57
All applications
retrieve configuration
information from
Config Manager.
3. URS queries Stat Server
for agent status.
1. Call comes in
to Routing Point on PBX.
2. Call is transferred to
VTO and VTO asks
customer for account
number request type
(service of info). URS
uses that number for
data dip to get
customer tier and
other information.
.
Figure 13: Example Call Flow Diagram of VTO in a Genesys Express Environment
call flow.
VTPhone
The VTO Demo Mode models incoming calls through the GUI component
imitating the callers phone set, VTPhone. VTPhone generates calls via
communication with the Generic T-Server.
Generated calls are then handled by the components of the Simulation solution,
which include Switch Simulator and Generic T-Server, and optionally,
Universal Routing Server. The generated call may be logically processed by
the Simulation solution as a real call, including attaching data and applying
routing strategies. The simulated call is then delivered to VTServer for
treatment.
Note: If you want to run the Simulation solution, you must install the
58
VTServer treats the incoming call using the same scripts and voice recordings
as it would a real call. VTServer uses the Windows audio subsystem to
perform voice playback and recording for the call.
The callers Dual Tone Multi Frequency (DTMF) input is simulated by
VTPhone and is communicated to VTServer directly. VTServer processes
DTMF input the same way as it does the DTMF input recognized by Dialogic.
While the call is being processed by the simulated environment and treated by
VTServer, VTPhone monitors and displays the call state and attached data.
The simulated call may be:
Reference Manual
59
Tserver_IVR
Tserver_IVR is a virtual T-Server residing within IVR Server. When a vendorprovided IVR is connected directly to the PSTN without a premise switch, the
configuration is called IVR-In-Front. In this configuration, there may be no TServer to connect to because there is no premise switch. Tserver_IVR takes on
the T-Server role in the IVR-In-Front configuration. IVR Server operating in
IVR-In-Front mode is designed to support IVRs that are connected directly to a
PSTN by performing functions similar to a regular T-Server.
When an IVR is considered a termination point for incoming calls, no premise
switch is involved, and no local T-Server receives notification of the incoming
call. Instead, IVR Server operating in IVR-In-Front mode provides this
functionality.
Note: There are occasions with IVR-In Front that you may also want a
I-Server
I-Server is one of two components that make up IVR Server. I-Server enables
load balancing statistics and other IVR Server functions.
MCR Components
Genesys Express includes a limited number of MCR components. Express
Voice users have the option to deploy the Contact Management components,
Contact Server and Contact Server Manager. Express Multimedia
automatically includes Contact Server, Contact Server Manager, E-mail Server
Java, MCR Interaction Server, Knowledge Manager, and Classification Server
when users install the solution. Chat Server is an optional component. The
sections that follow summarize the servers and processes.
60
Reference Manual
61
Reporting Components
The reporting component, CCPulse+, is part of the Reporting Layer, and is
available with Express Voice and Express Multimedia. This layer provides
real-time and historical data on almost every aspect of contact center business
that uses the Genesys system.
If necessary, refer to page 30 for a review of Genesys Reporting.
Note: A good starting point for more information about Reporting
CCPulse+
CCPulse+ provides both real-time and historical reporting.
Real-Time Reporting
CC Pulse+ monitors agent performance in real time and displays the
information for supervisors and managers via on-screen reports (views).
Note: For more information, see the Reporting 7.5 Deployment Guide on the
62
Note: A good starting point for more information is the Reporting Index on
StatServerReporting
Note: Genesys Express uses a separate Stat Server for reporting purposes
called StatServerReporting.
Stat Server receives information from T-Server and converts accumulated data
for directory numbers, agents, agents groups, and the like into statistical
information. Stat Server supplies statistical calculations to other Genesys
applications, such as Data Sourcer, upon request. For an architectural diagram,
see Figure 18 on page 67.
DB ServerDMA reads data from and writes data to the Operational Data
Storage (ODS) specified by the Database Access Point.
page 33. When working in DMA, click the Help menu to access
Reporting 7.2 Data Modeling Assistant Help.
Reference Manual
63
Data Sourcer
Data Sourcer periodically collects statistical information (such as profiles, time
ranges, and statistical filters) from StatServerReporting about current contact
center objects.
You can view host and associated Data Sourcer information in ETL Assistant.
Figure 16 shows the Report Views tab of ETL Assistant with Data Sourcer
information.
For each object specified in DMA, Data Sourcer obtains statistical data for
consecutive time intervals of assigned durations and writes this information to
the ODS (see Table 6 on page 71). Data in the ODS is later retrieved by the
Extraction, Transformation, and Loading (ETL) Runtime Service module (see
page 66).
Data Sourcer functions as both a client and a server.
64
Reference Manual
65
ETL Assistant
ETL stands for extraction, transformation, and loading.
ETL Assistant is the historical reporting component that enables you to:
Define the inputs to ETL Runtime for writing to the reporting Data Mart.
Review Data Mart content (see Figure 15 on page 62).
Establish a purge schedule for Data Mart elements.
For an architectural diagram, see Figure 18.
Note: For more information on ETL Assistant, see the Reporting 7.5
Deployment Guide and the Reporting 7.2 ETL Runtime Users Guide
on the Documentation Library DVD. When working in ETL, click the
Help menu to access Reporting 7.2 ETL Assistant Help.
66
DB Server
Stat
Server
Configuration
Server
Data
Sourcer
Data
Modeling
Assistant
Report Layouts
ODS
Data Collection
ETL
Runtime
Engine
ETL
Assistant
Data Mart
Data Mart
DB Server
CCPulse+
Information Delivery
Figure 18: Reporting Components Architecture for Express Voice
Reference Manual
67
Genesys Desktop
Genesys Desktop
Genesys Desktop is a desktop application that allow agents in the contact
center to handle customer interactions. They have streamlined GUIs that
support all contact center interactions on the same desktop. For Express CTI
and Express Voice this includes voice interactions. For Express Multimedia,
this includes voice and e-mail interactions.
Note: For information on using Genesys Desktop see the online help file
Answer a call.
Access customer information from past interactions.
Record customer information.
Transfer a call.
Put a customer on hold.
Hold a conference call.
Hang up (disconnect from a customer).
Become ready for a new call.
Make a customer call.
Genesys Desktop is not installed but accessed through an URL to the Genesys
Desktop server through Internet Explorer.
Note: For details on Genesys Desktop, see the Genesys Express 4.6 Users
Delivery Server
By default, Express Voice and Express Multimedia supply Delivery Server
from which you can download applications. Agents and supervisors access
Delivery Server using Internet Explorer from which they can easily install:
Note: The first time you connect to the Delivery Server from the Express
68
Databases
Databases
The Deployment Wizard installs the Microsoft SQL Server 2005 Express
Edition, a data storage and query processor used for solution development.
Once you move from a testing environment to a production environment, you
must upgrade the database, for example, to Microsoft SQL Server 2005,
including its user interface. The information in this section assumes the
upgrade has already taken place as described in the Genesys Express 4.6
Deployment Guide.
Notes:
If you are using Microsoft SQL Server 2005 Express Edition, you
can obtain a free management tool, Microsoft SQL Server
Management Studio Express from the Microsoft website,
www.microsoft.com.
Once the upgrade has taken place, access the databases as follows:
1. Select Start > Programs > MS SQL Server 2005 > Enterprise Manager.
The SQL Server Enterprise Manager window opens.
Reference Manual
69
Databases
Note: Express Multimedia uses databases not used by Express Voice and
Viewing Tables
To view rows and column names in a table:
1. Expand the folder for the table; for example, expand the Genesys_ERS
folder (see Figure 19).
70
Databases
In the right pane, if you right-click a table name and select Open Table >
Return Top, a window will open showing the rows and columns in that
table.
List of Databases
Table 6 provides a list and description of the databases used by the Genesys
Express suites (Express CTI, Express Voice, and Express Multimedia).
Table 6: List of Databases
Databases
Description
GCTI76
Genesys_ERS
Genesys_Log
ETL
ODS
MCR_UCS
MCR_UCS_Archive
MCR_IS
Reference Manual
71
Configuration Objects
Description
Outbound
CallCon
Configuration Objects
When Genesys Express is deployed on the target servers, configuration objects
are created and stored in Configuration Database. Configuration Manager
provides an interface for viewing/manipulating configuration data in the
GCTI76 database. This section describes some of the objects.
Environment Folder
In the subfolders under Environment in Configuration Manager, you will find
configuration settings for the following items:
Alarm Conditions
Alarm conditions apply to events that must be known and managed as soon as
they occur. The alarm conditions listed here and reflected in SCI are
Connection Failure, Application Failure, CTI Link Failure, Licensing
Error, and Host Inaccessible.
Application Templates
These models are used for registering new applications in the database.
Applications
These various Genesys software programs serve the contact center and are
integrated into Express CTI, Express Voice (see Figure 20) and Express
Multimedia.
72
Configuration Objects
There are two types of applications: GUI applications and server applications.
A majority of the applications are server applications; all managers and
wizards are GUI applications.
Reference Manual
73
Configuration Objects
Hosts
These machines run the various CTI application servers in the environment. In
the delivered solution, there can be one or more Express Servers host
machines. See Table 7 for an example of a host configuration.
Table 7: Configuration Manager, Host Information
Host Name
IP Address
OS Type
Version
LCA Port
State
Enabled
Your Express
server name
(read from server
during
installation)
Windows
2000/
Windows
2003/
5.0
4999
Yes
Solutions
These sets of application functions accomplish particular business tasks in
contact centers. See Table 8.
Table 8: Configuration Manager, Solution Information
Name
Solution Type
Solution
Control Server
Name
State Enabled
Production
Express
Solution Control
Server
Yes
Simulation
Express
Solution Control
Server
Yes
Note: See Table 5 on page 42 for a list of solution applications for Genesys
Express 4.6.
74
Configuration Objects
Switching Offices
You cannot register a switch (Table 10 on page 78) under the Resources folder
unless you previously registered a switching office to accommodate it.
The type of switching office available depends on the switch selected during
the installation process. See Table 9 for the list of switching offices.
Table 9: Configuration Manager, Switching Offices
Switching Office Name
Switch Type
State Enabled
VoiceSwitchingOfficeSimulation
Generic Switch
Yes
SwitchingOfficeG3
Yes
SwitchingOfficeA4400
Alcatel 4400
Yes
SwitchingOfficeA4200
Alcatel 4200
Yes
SwitchingOfficeSymposium
Yes
SwitchingOfficeCiscoCM
Yes
SwitchingOfficeHic300Hi4000
Yes
SwitchingOfficeAspect
Yes
SwitchingOfficeNEAX
NEC NEAX
Yes
SwitchOpenWorX
NEC NEAX
Yes
SwitchingOfficeMeridian1TCP
Nortel Meridian 1
Yes
SwitchingOfficeMD110
Ericsson MD110
Yes
SwitchingOfficeMCR
Multimedia Switch
Yes
SwitchingOfficeIVR
Yes
SwitchingOfficeSIPCS
SIP Switch
Yes
Resources Folder
The subfolders under Resources contain the Configuration Database objects
described below.
Reference Manual
75
Configuration Objects
Access Groups
Access groups are groups of Persons who need to have the same set of
permissions with respect to Configuration Database objects.
Action Codes
Action Codes enable agents to report the business results of customer
interactions, as well as to explain the reasons for certain operations. These are
not supplied with Genesys Express.
Agent Groups
Agent Groups are a group of agents who provide particular sets of contact
center services.
Calling Lists
Calling Lists are references to tables of information about the numbers to be
called during an outbound campaign. These are not supplied with Genesys
Express.
Campaigns
Campaigns are structures for organizing and managing an automated process
of making outbound calls to the destinations specified in Calling Lists. These
are not supplied with Genesys Express.
DN Groups
These groups may be used in network-level routing algorithms and in some
types of statistics. These are not supplied with Genesys Express.
Fields
Fields are single pieces of data within more complex data structures (for
example, database records).
Filters
Filters are used for specifying conditions of data selection from a data
repository (for example, from a database table.)
76
Configuration Objects
Formats
Formats are used to specify Fields that form a data structure.
IVRs
IVRs (Interactive Voice Responses) are telephony objects consisting of IVR
ports. These are supplied with Genesys Express if IVR Link is selected during
deployment.
Persons
Persons are the contact center personnel, including agents, who need access to
CTI applications.
Place Groups
Place groups are used if, according to the call-processing algorithms, the calls
need to be distributed among a set of Places under the control of CTI
applications rather than through the ACD mechanisms of the switch. These are
not supplied with Genesys Express.
Places
A Place is a location that has one of more DNs operated by a single agent.
These are not supplied with Genesys Express.
Scripts
Scripts identify processing scenarios (for example, a routing strategy) or
treatments that can be applied to customer interactions.
Skills
Skills are qualities or abilities that agents possess that affect how they are
placed in a contact center hierarchy.
Statistical Days
A Statistical Day is a numerically expressed workload that a particular Agent
Group is expected to handle during a business day. These are not supplied with
Genesys Express.
Reference Manual
77
Configuration Objects
Statistical Tables
Statistical Tables are groups of Statistical Days that represent statistically
modeled performances of Agent Groups over a calendar period of up to one
year. These are not supplied with Genesys Express.
Switches
Table 10 lists the Switch definitions supplied with Genesys Express.
Table 10: Switches
Switch Name
Type
VoiceSwitchSimulation
Generic Switch
SwitchG3
SwitchA4400
Alcatel 4400
SwitchA4200
Alcatel 4200
SwitchSymposium
SwitchCiscoCM
Cisco CallManager
SwitchHic300Hi4000
SwitchAspect
SwitchNEAX
NEC NEAX
SwitchingOfficeOpenWorX
NCE NEAX
SwitchMeridian1TCP
Nortel Meridian 1
SwitchMD110
Ericsson MD110
SwitchMCR
Multimedia Switch
SwitchIVR
SwitchSIPCS
SIP Switch
78
Configuration Objects
VoiceSwitchProduction DNs
You must configure production DNs for your Production solution.
Note: VoiceSwitchProduction is a generic name for all Voice Switch names.
VoiceSwitchSimulation DNs
Expand the Switches folder and then the VoiceSwitchSimulation folder. If
you install the Standard Model Environment after deploying Genesys Express,
VoiceSwitchSimulation DNs are configured. See the Genesys Express 4.6
Standard Model Environment for more information.
Reference Manual
79
Configuration Objects
SwitchSIPCS DNs
Expand the Switches folder and then the SwitchSIPCS folder. You must
configure DNs for your Production solution.
Table Access
Table Access objects describe database tables of a specified Format and
explain how these tables can be accessed through Database Access Points.
Time Zones
Time Zones are defined in the Time Zones folder.
Transactions
Transactions define how CTI applications calculate customer-defined
statistics.
Treatments
Treatments describe sets of actions performed upon a specific call.
Voice Prompts
Voice Prompts are called treatment objects an may include a set of actions to
be applied to a called party. Used for the Genesys Interactive Voice Response
(IVR) product. These are not supplied with Genesys Express.
Note: For more information on Configuration Manager, see the Framework
80
Index
A
access group . . . . . . . . . . . . . . . . . 76
Actions Wizard . . . . . . . . . . . . . . . . 32
agent
logins by switch . . . . . . . . . . . . . . . 79
alarm conditions . . . . . . . . . . 41, 46, 47, 72
alarm signaling . . . . . . . . . . . . . . . . 38
Alcatel A4200 switch . . . . . . . . . . . . . 18
Alcatel A4400 switch . . . . . . . . . . . . . 18
Apache . . . . . . . . . . . . . . . . . . . . 16
application version numbers . . . . . . . . . 11
applications
Configuration Manager . . . . . . . . . . . 72
failure . . . . . . . . . . . . . . . . . . 38, 72
Framework . . . . . . . . . . . . . . . . . 44
Routing . . . . . . . . . . . . . . . . . 52, 62
templates . . . . . . . . . . . . . . . . . . 72
architectural diagrams
Configuration Server . . . . . . . . . . . . 46
Data Sourcer . . . . . . . . . . . . . . . . 65
Reporting Layer . . . . . . . . . . . . . . . 62
Solution Control Server . . . . . . . . . . . 48
Stat Server. . . . . . . . . . . . . . . . . . 50
T-Server . . . . . . . . . . . . . . . . . . . 49
Universal Routing . . . . . . . . . . . . . . 52
VTO . . . . . . . . . . . . . . . . . . . . . 58
Aspect ACD switch . . . . . . . . . . . . . . 18
Attached Data . . . . . . . . . . . . . . . . 22
attached data . . . . . . . . . . . . . . . . . 23
audience
defining . . . . . . . . . . . . . . . . . . . 6
automated responses . . . . . . . . . . . . 30
Avaya Definity ECS G3 switch . . . . . . . . 18
Call Concentrator . . . . . . . . . . . . . . . 17
CallConcentrator
startup priority . . . . . . . . . . . . . . . . 44
canned text . . . . . . . . . . . . . . . . . . 30
CC Analyzer
Collection Service . . . . . . . . . . . . . . 64
Stat Server . . . . . . . . . . . . . . . . . 13
CC Pulse. . . . . . . . . . . . . . . . . . 13, 73
CCA Data Sourcer . . . . . . . . . . . . . 13, 64
cfg_dbserver . . . . . . . . . . . . . . . . 12, 73
chapter summaries
defining . . . . . . . . . . . . . . . . . . . . 6
Chat Server . . . . . . . . . . . . . . . . . . 17
Cisco CallManager switch . . . . . . . . . . . 18
Cisco Stream Manager
startup priority . . . . . . . . . . . . . . . . 43
Cisco Stream Manager switch . . . . . . . . . 18
commenting on this document . . . . . . . . . 10
components
Framework . . . . . . . . . . . . . . . . . 44
Genesys Voice Platform . . . . . . . . . . 60
GVP . . . . . . . . . . . . . . . . . . . . . 59
IVR . . . . . . . . . . . . . . . . . . . . . 59
Reporting . . . . . . . . . . . . . . . . . . 62
Universal Routing . . . . . . . . . . . . . . 52
VTO . . . . . . . . . . . . . . . . . . . . . 56
configuration database objects . . . . . . . . 75
Configuration Layer . . . . . . . . . . . . . . 22
Configuration Manager . . . . . . . . . . . . 73
application . . . . . . . . . . . . . . . . . 46
Base software . . . . . . . . . . . . . . . . 12
Configuration Server . . . . . . . . . . . . . . 46
application . . . . . . . . . . . . . . . . . 73
Base software . . . . . . . . . . . . . . . . 12
function . . . . . . . . . . . . . . . . . . . 45
Connection Failure alarm condition . . . . . . 72
Contact Center Activity Simulator . . . . . 18, 51
contact history . . . . . . . . . . . . . . . . . 30
B
Browser . . . . . . . . . . . . . . . . . . . 16
business data . . . . . . . . . . . . . . . . 23
Reference Manual
81
Index
Contact Server
overview . . . . . . . . . . . . . . . . . . . 61
startup priority . . . . . . . . . . . . . . . . 43
Contact Server Manager . . . . . . . . . . . 17
overview . . . . . . . . . . . . . . . . . . . 61
Contact Server Service
Genesys software . . . . . . . . . . . . . . 17
CPD (Call Progress Detection Server)
startup priority . . . . . . . . . . . . . . . . 43
CTI Link Failure . . . . . . . . . . . . . . . 72
CustomDBServer for Routing
startup priority . . . . . . . . . . . . . . . . 43
customer tier . . . . . . . . . . . . . . . . . 54
D
Data Mart . . . . . . . . . . . . . . . . 33, 64, 66
Data Modeling Assistant . . . . . . 13, 33, 63, 73
Data Sourcer . . . . . . . . . . . . . . 13, 64, 73
startup priority . . . . . . . . . . . . . . . . 43
Data Sourcer DB Server . . . . . . . . . . . 13
Data Sourcer DBServer
startup priority . . . . . . . . . . . . . . . . 43
Data Sourcer for Stat Server . . . . . . . . . 64
database migration . . . . . . . . . . . . . . 16
database objects in Configuration Manager . 75
databases
reporting . . . . . . . . . . . . . . . . . . . 64
SQL server . . . . . . . . . . . . . . . . . 69
DataSourcer DB Server . . . . . . . . . . . 73
DataSourcerDAP . . . . . . . . . . . . . . . 73
DB Server
definition . . . . . . . . . . . . . . . . . . . 45
diagram . . . . . . . . . . . . . . . . . . . 50
interaction flow . . . . . . . . . . . . . . . 53
DB Server (routing)
startup priority . . . . . . . . . . . . . . . . 43
DBServer for CallConcentrator
startup priority . . . . . . . . . . . . . . . . 44
DBServer for DataMart
startup priority . . . . . . . . . . . . . . . . 43
DBServer for Outbound
startup priority . . . . . . . . . . . . . . . . 43
Decision Support System Architecture . . . . 32
Delivery Server . . . . . . . . . . . . . . . . 14
startup priority . . . . . . . . . . . . . . . . 43
diagram
Configuration Server . . . . . . . . . . . . 46
Message Server . . . . . . . . . . . . . . . 48
SCI . . . . . . . . . . . . . . . . . . . . . 48
Stat Server. . . . . . . . . . . . . . . . . . 50
T-Server . . . . . . . . . . . . . . . . . . . 49
Universal Routing . . . . . . . . . . . . . . 52
VTO . . . . . . . . . . . . . . . . . . . . . 58
directory
Environment . . . . . . . . . . . . . . . . . 72
82
directory numbers . . . . . . . . . . . . . . . 78
DMA . . . . . . . . . . . . . . . . . . . . . .63
DN groups . . . . . . . . . . . . . . . . . . . 76
DNs . . . . . . . . . . . . . . . . . . . . . . 78
document
conventions . . . . . . . . . . . . . . . . . . 7
errors, commenting on . . . . . . . . . . . 10
version number . . . . . . . . . . . . . . . . 7
documentation
Framework . . . . . . . . . . . . . . . . . 23
IVR Interface Option . . . . . . . . . . . . 29
Multimedia . . . . . . . . . . . . . . . . . 30
Reporting . . . . . . . . . . . . . . . . . . 33
Universal Routing . . . . . . . . . . . . . . 25
VTO . . . . . . . . . . . . . . . . . . . . . 27
Dual Tone Multi Frequency . . . . . . . . . . 59
E
e-mail
forwarding . . . . . . . . . . . . . . . . . . 30
server software . . . . . . . . . . . . . . . 16
E-mail Server Java
overview . . . . . . . . . . . . . . . . . . 61
startup priority . . . . . . . . . . . . . . . . 43
Environment directory . . . . . . . . . . . . . 72
Ericsson MD110 . . . . . . . . . . . . . . . . 18
ERS DB Server . . . . . . . . . . . . . . 52, 73
ERSDAP . . . . . . . . . . . . . . . . . . . . 73
ERSDBServer . . . . . . . . . . . . . . . . . 14
ETL
databases . . . . . . . . . . . . . . . . . . 71
extraction process . . . . . . . . . . . . . 66
Proxy . . . . . . . . . . . . . . . . . . . . 73
Runtime . . . . . . . . . . . . . . . . . 33, 73
Server . . . . . . . . . . . . . . . . . . . . 73
ETL Assistant . . . . . . . . . . . . . . . . . 13
ETL_Proxy . . . . . . . . . . . . . . . . . . . 13
ETLService . . . . . . . . . . . . . . . . . . 13
startup priority . . . . . . . . . . . . . . . . 43
Express CTI . . . . . . . . . . . . . . . . . . 5
Express Multimedia . . . . . . . . . . . . . . 5
Express Voice . . . . . . . . . . . . . . . . . 5
Extended Current Status window . . . . . . . 32
extraction from ODS for reporting . . . . . . . 66
F
failures . . . . . . . . . . . . .
fault management . . . . . . .
fields in Configuration Manager
FLEXlm . . . . . . . . . . . .
FLEXlm License Manager . . .
formats . . . . . . . . . . . . .
forwarding e-mail . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 38, 72
. . . 38
. . .76
. . . 16
. . . 38
. . . 77
. . . 30
Index
Framework
Access Control function . . . . . .
Alarm Processing function. . . . .
Attached Data Distribution function
Configuration function . . . . . . .
documentation. . . . . . . . . . .
External Interfaces function . . . .
Fault Management . . . . . . . .
functions . . . . . . . . . . . . . .
servers and processes . . . . . .
Solution Control function . . . . .
Troubleshooting function . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 22
. 22
. 22
. 22
. 23
. 22
. 22
. 22
. 44
. 22
. 22
G
GCTI database . . . . . . . . . . . . . . .45, 71
Generic T-Server . . . . . . . . . . . . . .18, 51
Genesys databases . . . . . . . . . . . . . 69
Genesys Desktop
startup priority . . . . . . . . . . . . . . . . 43
Genesys Express
Express CTI . . . . . . . . . . . . . . . . . 5
Express Multimedia . . . . . . . . . . . . . 5
Express Voice . . . . . . . . . . . . . . . . 5
family of solutions . . . . . . . . . . . . . . 5
optional components . . . . . . . . . . . . 17
standard components . . . . . . . . . . . . 12
third party software . . . . . . . . . . . . . 15
Genesys Voice Platform . . . . . . . . . . . 17
Genesys Web Server . . . . . . . . . . . . 14
GVP . . . . . . . . . . . . . . . . . . . . . 60
startup priority . . . . . . . . . . . . . . . . 43
H
Hamster Mail Server third party software
history of contacts . . . . . . . . . . . .
Host Inaccessible alarm condition . . . .
hosts in Configuration Manager . . . . .
.
.
.
.
.
.
.
.
16
30
72
74
I
Interaction Routing Designer
application in the Configuration Layer . . . . 73
Base software . . . . . . . . . . . . . . . . 14
starting. . . . . . . . . . . . . . . . . . . . 55
Internet Contact Center
automated responses . . . . . . . . . . . . 30
contact history . . . . . . . . . . . . . . . . 30
universal queue . . . . . . . . . . . . . . . 30
Internet Contact Solution
documentation. . . . . . . . . . . . . . . . 30
features . . . . . . . . . . . . . . . . . . . 30
I-Server. . . . . . . . . . . . . . . . . . .17, 60
Reference Manual
. . . . . . . . 29
. . . . . . . . 60
. . . . . . . . 60
. . . . . . . . 77
L
layout templates . . . . . . . .
LCA . . . . . . . . . . . . . .
License Manager . . . . . . .
Licensing Error alarm condition
Local Control Agent . . . . . .
log database . . . . . . . . . .
Log DB Server . . . . . . . . .
logging . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. . . . 63
12, 22, 47
. . . . 16
. . . .72
12, 22, 47
. . . .71
. . 12, 46
. . 38, 41
M
Management Layer . . . . . . . . . . . . . . 22
MCR . . . . . . . . . . . . . . . . . . . . . .43
MCR Chat Server
startup priority . . . . . . . . . . . . . . . . 43
MCR Classification Server
startup priority . . . . . . . . . . . . . . . . 43
MCR Components . . . . . . . . . . . . . . . 60
MCR EMailServerJava. . . . . . . . . . . . . 14
MCR Interaction Server . . . . . . . . . . . . 14
startup priority . . . . . . . . . . . . . . . . 43
MCR Interaction Server DBServer
startup priority . . . . . . . . . . . . . . . . 43
MCR InteractionServer DBServer . . . . . . . 14
Media Layer . . . . . . . . . . . . . . . . . . 23
Message Server . . . . . . . . . . . . . . . . 46
architectural diagram . . . . . . . . . . . . 48
Base software . . . . . . . . . . . . . . . . 12
function of . . . . . . . . . . . . . . . . . . 47
Microsoft Internet Explorer 6.0. . . . . . . . . 16
migrating to MS SQL 2000. . . . . . . . . . . 16
Model Environment
access groups. . . . . . . . . . . . . . . . 76
Environment folder . . . . . . . . . . . . . 72
switches . . . . . . . . . . . . . . . . . . . 78
monitoring objects . . . . . . . . . . . . . . . 32
MS SQL Server 2000 . . . . . . . . . . . . . 69
MS-Tserver
overview . . . . . . . . . . . . . . . . . . 61
N
NEC NEAX switch . . . . . . . . . . . . . . . 18
NEC OpenWorX switch . . . . . . . . . . . . 18
83
Index
NECProxy
startup priority . . . . . . . . . . . . . . . . 42
Nortel Meridian 1 switch . . . . . . . . . . . 18
Nortel Symposium switch . . . . . . . . . . 18
O
ODS . . . . . . . . . . . . . . . . 33, 64, 66, 71
operating system
Windows 2000 Server . . . . . . . . . . . . 16
Windows 2003. . . . . . . . . . . . . . . . 16
optional components . . . . . . . . . . . . . 17
Outbound Contact . . . . . . . . . . . . . . 17
Outbound Contact Server
startup priority . . . . . . . . . . . . . . . . 43
P
PBX
interaction diagram . . . . . . . . . . . . . 53
PBX Simulator . . . . . . . . . . . . . . . . 50
PBX T-Server. . . . . . . . . . . . . . . . . 48
POP3 server . . . . . . . . . . . . . . . . . 16
Production solution . . . . . . . . . . . . . . 42
R
readme.htm . . . . . . . . . . . . . . . . . 11
real-time status . . . . . . . . . . . . . . . . 38
real-time views . . . . . . . . . . . . . . . . 32
Report Layouts . . . . . . . . . . . . . . . . 63
Reporting
CC Pulse . . . . . . . . . . . . . . . . . . 32
Data Mart . . . . . . . . . . . . . . . . . . 66
documentation. . . . . . . . . . . . . . . . 33
extraction assistant . . . . . . . . . . . . . 66
Operational Data Store . . . . . . . . . . . 64
Reporting Layer . . . . . . . . . . . . . . . 31
Resources directory . . . . . . . . . . . . . 75
Response Manager
overview . . . . . . . . . . . . . . . . . . . 61
routing
architectural diagram . . . . . . . . . . . . 54
criteria . . . . . . . . . . . . . . . . . . . . 25
designer . . . . . . . . . . . . . . . . . . . 55
documentation. . . . . . . . . . . . . . . . 25
interaction flow . . . . . . . . . . . . . . . 53
overview . . . . . . . . . . . . . . . . . . . 24
Universal Routing . . . . . . . . . . . . . . 24
S
SCI . . . . . . . . . . . . . . . . . . . . . . 13
screen pop . . . . . . . . . . . . . . . . . . 26
84
server
operating system . . . . . . . . . . . . . . 16
servers
CCA Stat Server . . . . . . . . . . . . . . 63
Configuration . . . . . . . . . . . . . . . . 45
DB Server . . . . . . . . . . . . . . . . . . 45
Enterprising Routing DB . . . . . . . . . . 52
I-Server . . . . . . . . . . . . . . . . . . . 60
IVR Server . . . . . . . . . . . . . . . . . 59
Solution Control . . . . . . . . . . . . . . . 47
Statistics . . . . . . . . . . . . . . . . . . 50
Universal Routing . . . . . . . . . . . . . . 52
Voice T-Server . . . . . . . . . . . . . . . 49
Services Layer . . . . . . . . . . . . . . . . . 23
Siemens Hicom300/HiPath 4000 CSTA I switch
18
Simulation solution. . . . . . . . . . . . . . . 42
simulation voice switch . . . . . . . . . . . . 78
Simulators . . . . . . . . . . . . . . . . . 18, 23
SIP Server
startup priority . . . . . . . . . . . . . . . . 42
SIP Stream Manager
startup priority . . . . . . . . . . . . . . . . 43
Solution Control Interface
Base software . . . . . . . . . . . . . . . . 13
Solution Control Server . . . . . . . . . . . . 13
diagram . . . . . . . . . . . . . . . . . . . 48
solutions . . . . . . . . . . . . . . . . . . 42, 74
SQL Server 2000 . . . . . . . . . . . . . . . 16
SQL Server 2005 Express Edition . . . . . . . 69
standard log setting . . . . . . . . . . . . . . 41
Standard Response Library . . . . . . . . . . 30
startup priority (servers) . . . . . . . . . . . . 42
Stat Server . . . . . . . . . . . . . . . . . . . 63
Base software . . . . . . . . . . . . . . . . 12
CC Analyzer . . . . . . . . . . . . . . 13, 63
CC Pulse . . . . . . . . . . . . . . . . . . 32
definition . . . . . . . . . . . . . . . . . . 50
diagram . . . . . . . . . . . . . . . . . . . 50
relation to URS . . . . . . . . . . . . . . . 54
reporting
startup priority . . . . . . . . . . . . . . 43
Universal Routing . . . . . . . . . . . . . . 25
statistical days . . . . . . . . . . . . . . . . . 77
statistical tables . . . . . . . . . . . . . . . . 78
statistical transactions . . . . . . . . . . . . . 80
StatServer
startup priority . . . . . . . . . . . . . . . . 42
support . . . . . . . . . . . . . . . . . . . . . 19
switch for Simulation solution . . . . . . . . . 78
Switch Simulator
GUI . . . . . . . . . . . . . . . . . . . . . 50
startup priority . . . . . . . . . . . . . . . . 42
switches . . . . . . . . . . . . . . . . . . . . 78
Alcatel A4200 . . . . . . . . . . . . . . . . 18
Alcatel A4400 . . . . . . . . . . . . . . . . 18
Index
Aspect ACD . . . . . . . . . . . . . . . . . 18
Avaya Definity ECS G3 . . . . . . . . . . . 18
Cisco CallManager . . . . . . . . . . . . . 18
Cisco Stream Manager . . . . . . . . . . . 18
Ericsson MD110 . . . . . . . . . . . . . . . 18
NEC NEAX . . . . . . . . . . . . . . . . . 18
NEC OpenWorX . . . . . . . . . . . . . . . 18
Nortel Meridian 1 . . . . . . . . . . . . . . 18
Nortel Symposium . . . . . . . . . . . . . . 18
Siemens Hicom300/HiPath 4000 CSTA I . . 18
supported . . . . . . . . . . . . . . . . . . 18
Switching Offices . . . . . . . . . . . . . . . 75
T
table access . . . . . . . . . . . . . . . . . 80
technical support . . . . . . . . . . . . . . . 19
Telnet . . . . . . . . . . . . . . . . . . . . . 50
templates . . . . . . . . . . . . . . . . . . . 63
Test Simulator . . . . . . . . . . . . . . . . 50
third party software . . . . . . . . . . . . . . 15
Threshold Wizard . . . . . . . . . . . . . . 32
time zones . . . . . . . . . . . . . . . . . . 80
trace log setting . . . . . . . . . . . . . . . 41
treatments . . . . . . . . . . . . . . . . . . 80
T-Server . . . . . . . . . . . . . . . . . .42, 49
diagram . . . . . . . . . . . . . . . . . 54, 58
switches . . . . . . . . . . . . . . . . . . . 78
VoiceTServer . . . . . . . . . . . . . . . . 48
TServer for IVR
startup priority . . . . . . . . . . . . . . . . 43
TServer_IVR . . . . . . . . . . . . . . . . . 17
Tserver_IVR . . . . . . . . . . . . . . . . . 60
typographical styles . . . . . . . . . . . . . . 7
version numbers . . . . . . . . . . . . . . . . 11
versions.htm . . . . . . . . . . . . . . . . . . 11
Voice Communication Server (GVP). . . . . . 60
voice directory numbers . . . . . . . . . . . . 79
Voice Treatment Manager . . . . . . . . . 17, 56
Voice Treatment Option . . . . . . . . . . . . 25
relation to Configuration Server . . . . . . . 56
Voice Treatment Server . . . . . . . . . . 17, 56
startup priority . . . . . . . . . . . . . . . . 43
VoiceSwitchingOffice . . . . . . . . . . . . . 75
VoiceSwitchSimulation. . . . . . . . . . . . . 78
VoiceT-Server . . . . . . . . . . . . . . . . . 48
VoiceTserverProduction . . . . . . . . . . . . 19
startup priority . . . . . . . . . . . . . . . . 42
VoiceTserverSimulation
startup priority . . . . . . . . . . . . . . . . 42
W
Windows 2000 Server . . . . . . . . . . . . . 16
Windows 2003 . . . . . . . . . . . . . . . . . 16
Windows Service
start . . . . . . . . . . . . . . . . . . . . . 38
Windows Services . . . . . . . . . . . . . . . 38
Wizard . . . . . . . . . . . . . . . . . . . . . 32
X
XML format . . . . . . . . . . . . . . . . . . 40
U
universal queue . . . . . . . . . . . . . . . 30
Universal Routing
architectural diagram . . . . . . . . . . . . 54
DB Server . . . . . . . . . . . . . . . . 43, 52
Designer . . . . . . . . . . . . . . . . . . . 55
documentation. . . . . . . . . . . . . . . . 25
overview . . . . . . . . . . . . . . . . . . . 24
Universal Routing Server. . . . . . . . . . . 14
interaction flow . . . . . . . . . . . . . . . 53
starting. . . . . . . . . . . . . . . . . . . . 52
startup priority . . . . . . . . . . . . . . . . 43
Universal Routing Service . . . . . . . . . . 59
V
VBScript . . . . . . . . . . . . . . . . . . . 32
version numbering
document . . . . . . . . . . . . . . . . . . 7
Reference Manual
85
Index
86