Nortel CCT User manual

Nortel Communication Control Toolkit
Planning and Engineering Guide
Product release 5.0 Standard 5.01 June 2007
297-2183-924

Nortel Communication Control Toolkit
Planning and Engineering Guide
Publication number: 297-2183-924
Product release: 5.0
Document release: Standard 5.01
Date: June 2007
Copyright © 2007 Nortel Networks. All Rights Reserved.
Information is subject to change without notice. Nortel Networks reserves the right to make
changes in design or components as progress in engineering and manufacturing may warrant.
The process of transmitting data and call messaging between the Meridian 1 or DMS/MSL-100
switch and Communication Control Toolkit is proprietary to Nortel Networks. Any other use of the
data and the transmission process is a violation of the user license unless specifically authorized
in writing by Nortel Networks prior to such use. Violations of the license by alternative usage of
any portion of this process or the related hardware constitutes grounds for an immediate
termination of the license and Nortel Networks reserves the right to seek all allowable remedies
for such breach.
*Nortel, Nortel (Logo), the Globemark, and This is the Way, This is Nortel (Design mark),
CallPilot, Contivity, DMS, IVR, Meridian, Meridian 1, Meridian Mail, Meridian SL, Optivity,
Succession, and Symposium are trademarks of Nortel Networks.
CITRIX is a trademark of Citrix Systems, Inc.
INTEL, INTEL XEON, and PENTIUM are trademarks of Intel Corporation.
MICROSOFT, MICROSOFT ACCESS, WINDOWS, WINDOWS NT, and WINDOWS XP are
trademarks of Microsoft Corporation.
REPLICATION SERVER and SYBASE are trademarks of Sybase, Inc.
PCANYWHERE is a trademark of Symantec Corporation.

Planning and Engineering Guide v
Revision history
December 2006 The Standard 5.01 issue of the Nortel Communication
Control Toolkit Planning and Engineering Guide is
released. It contains updates for CRs and for Microsoft
Vista.
December 2006 The Standard 5.0 issue of the Nortel Communication
Control Toolkit Planning and Engineering Guide, Release
5.0, is released. It contains updates for telephone sets
based on CRs.
October 2006 The Standard 4.0 issue of the Nortel Communication
Control Toolkit Planning and Engineering Guide, Release
5.0, is released. It contains updates required to
terminology and server specifications for SU03.
June 2006 The Standard 3.0 issue of the Nortel Communication
Control Toolkit Planning and Engineering Guide, Release
5.0, is released.
May 2005 The Standard 2.0 issue of the Nortel Communication
Control Toolkit Planning and Engineering Guide, Release
5.0, is released.
March 2005 The Standard 1.0 issue of the Nortel Communication
Control Toolkit Planning and Engineering Guide, Release
5.0, is released.

vi Communication Control Toolkit
Standard 5.01

Planning and Engineering Guide vii
Contents
1Getting started 9
About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Engineering Communication Control Toolkit . . . . . . . . . . . . . . . . . . . . . . . . 12
What’s new in Release 5.0? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Product description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Related documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2Communication Control Toolkit architecture 27
Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Communication Control Toolkit API application types . . . . . . . . . . . . . . . . . 39
3Engineering Communication Control Toolkit 43
Section A: Engineering the server 45
Hardware requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Operating system configuration requirements . . . . . . . . . . . . . . . . . . . . . . . . 50
Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Guidelines to minimize capacity requirements. . . . . . . . . . . . . . . . . . . . . . . . 56
Section B: Engineering the client 59
Client requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
4Engineering the switch 61
Section A: Engineering Meridian 1/Succession 1000 63
Meridian 1/Succession 1000 switch requirements . . . . . . . . . . . . . . . . . . . . . 64
Meridian 1/Succession 1000 switch capacity . . . . . . . . . . . . . . . . . . . . . . . . . 67
Supported phonesets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Section B: Configuring Meridian 1/Succession 1000 73
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Configuring the ELAN subnet (knowledge worker environment) . . . . . . . . . 75
Configuring CDNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Configuring TAPI phonesets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

viii Communication Control Toolkit
Contents Standard 5.01
5Engineering the network 85
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Contact center and self-service environments . . . . . . . . . . . . . . . . . . . . . . . . 87
Knowledge worker environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Network traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
6Setting up remote support with a VPN 105
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Guidelines for the Remote Support VPN at the customer’s premises . . . . . 108
VPN configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
ASupported migration paths 113
Supported migration paths to Communication Control Toolkit 5.0 . . . . . . . 114
BSupported functions and events 117
Supported features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Supported events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
CStandard call models 125
Inbound call models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Index 151

Planning and Engineering Guide 9
Chapter 1
Getting started
In this chapter
About this guide 10
Engineering Communication Control Toolkit 12
What’s new in Release 5.0? 13
Product description 14
Related documents 25

10 Communication Control Toolkit
Getting started Standard 5.01
About this guide
Welcome
Communication Control Toolkit helps you implement Computer Telephony
Integration for installed and browser-based client integrations. It delivers a
single cross-portfolio multi-channel API that facilitates the integration of contact
center, knowledge worker, and self-service solutions with your client
applications. These client applications can be simple software phones, agent
telephony toolbars with screen pops, intelligent call management applications,
and so on.
Computer Telephony Integration
Computer Telephony Integration (CTI) describes an environment where
telephony systems and computer systems interact with each other. This
interaction can take many forms, including Interactive Voice Response (IVR),
computer controlled call routing, call recording, predictive dialing, client
desktop integration, and so on.
Most CTI applications support one or both of the following functions:
control of telephony communications, such as
Make call
Answer call
Route call
Transfer call
monitoring of telephony communications, such as
Pop an application screen when an inbound call arrives
Record call statistics
As the boundary between computer and telephony systems becomes more
blurred, the telephony platform is evolving to become a more integrated part of a
broader communications infrastructure that, among others, includes voice,
e-mail, instant messaging, and video.

Planning and Engineering Guide 11
June 2007 Getting started
Who should read this guide
This guide is for Communication Control Toolkit system designers and technical
support staff members. It is also intended to be used by administrators who are
responsible for day-to-day management of Communication Control Toolkit.

12 Communication Control Toolkit
Getting started Standard 5.01
Engineering Communication Control Toolkit
Engineering tasks
When engineering Communication Control Toolkit, you must perform the tasks
listed in the following checklist:
Description ✔
Determine requirements for Communication Control Toolkit. See
Chapter 3, “Engineering Communication Control Toolkit.”
Determine switch requirements. See Chapter 4, “Engineering the
switch.”
Determine network requirements. See Chapter 5, “Engineering the
network.”
Determine the requirements of the remote support system. See
Chapter 6, “Setting up remote support with a VPN.”

Planning and Engineering Guide 13
June 2007 Getting started
What’s new in Release 5.0?
The Communication Control Toolkit Release 5.0 is an evolution of Nortel’s
Computer Telephony Integration (CTI) products, including
IPML 2.1
TAPI 3.1
The Communication Control Toolkit incorporates the features of these products,
plus the following new features.
New features
a new easy-to-use graphical toolkit based on Windows Form Controls
a reference implementation—This implementation can be used in testing,
and can be easily modified to create a custom client application.
support for Windows Server 2003 Standard Edition and Enterprise Edition
enhanced security—A secure transport layer based on TCP sockets
provides authentication and security for the toolkit.
firewall friendliness
Citrix/Terminal Services support—The toolkit is designed to operate in a
terminal services environment. It supports both Citrix and Microsoft
Terminal Services.

14 Communication Control Toolkit
Getting started Standard 5.01
Product description
Features
The Communication Control Toolkit application program interface (API) is
object oriented and is implemented as a set of .NET types and interfaces. It
provides the following features:
Unified client integration
The Communication Control Toolkit is an integration toolkit for installed
clients, browser-based clients, and server-to-server integrations. The toolkit
delivers a single cross-portfolio multi-channel API, which is deployed through
the Developer Partner Program. The API is used to develop communication
control applications or integrations.
CTI coresidency
In a contact center environment, the Communication Control Toolkit Release 5.0
reduces the number of CTI servers required from two to one. (Both the TAPI
Service Provider and IPML products required a separate server.)
Communication Control Toolkit can also coreside with the MPS 500.
Note: Communication Control Toolkit cannot coreside with Symposium Agent
or Symposium Web Center Portal.
Database backup
The Communication Control Toolkit utilizes the built-in capabilities of the
Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) database to provide
database backup and restore operations. Database backups can be performed on
an ad hoc or scheduled basis while the system is running.
To restore the database, you must first shut down the Communication Control
Toolkit application. After restoring the database, you can restart the application.
Firewall friendliness
For the protection of your system, the Communication Control Toolkit operates
within a firewall.

Planning and Engineering Guide 15
June 2007 Getting started
Firewall traversal is achieved through the use of a single, bidirectional TCP
socket connection between the Communication Control Toolkit client and
server. Connections are initiated from client to server only, with any data
required to be transmitted from the server back to the client (such as
asynchronous event notifications) utilizing the existing connection already in
place.
Notes:
Communication Control Toolkit clients use a single port for
communication with the server. By default, this port is 29373; however, the
port number is configurable (for detailed instructions, see the Installation
and Maintenance Guide). If you are using a firewall, ensure that this port is
open.
In the case where Network Address Translation (NAT) is used by the
firewall, the firewall must map the TCP port number used to reach the
Communication Control Toolkit service on the internal network to the same
port number on the external network. This is an inherent limitation of using
the Communication Control Toolkit secure transport across a network
boundary secured by a firewall.
Terminal Services support
The Communication Control Toolkit operates in a Terminal Services
(specifically Citrix and Microsoft Terminal Services) environment.
Migration path
The Communication Control Toolkit Release 5.0 allows you to migrate from an
existing TAPI Service Provider 3.0 or IPML 2.1 implementation. To facilitate a
staged migration, Communication Control Toolkit can coexist with legacy TAPI
and IPML ActiveX clients. For more information about migration paths, see
Appendix A, “Supported migration paths.”
Note: Communication Control Toolkit cannot coreside with Symposium Agent.
If you are using Symposium Agent, you must install it on a separate server.
Networking
Communication Control Toolkit uses the existing TAPI networking layer.
Therefore, it supports networking with legacy TAPI servers.

16 Communication Control Toolkit
Getting started Standard 5.01
Open switch connectivity
Since it supports a variety of switch interfaces, Communication Control Toolkit
can connect to a variety of switch types.
The IPML Service Provider supports the following switch interfaces:
Meridian Link Services (MLS) version 4.2 and greater
IVR-ASAI on the Avaya G3, Release 6
IVR-GTS on the Genesys T-Server Release 10
The TAPI Service Provider supports the following interfaces:
Meridian Link Services (MLS) version 4.2 and greater
Application Module Link (AML) on X11 Release 25.40B and greater, or
Succession Release 3 and greater
Access rights
All access rights to the Communication Control Toolkit server are defined
through Windows user accounts using standard Windows authentication
mechanisms.
Administration and configuration
To configure and maintain Communication Control Toolkit, you use a custom
Microsoft Management Console (MMC) snap-in. MMC is an extensible
common presentation service for management applications that is included with
the Windows 2000 and Windows Server 2003 operating systems.
The Communication Control Toolkit snap-in utility uses a graphical user
interface to administer resources such as user, address, terminal and workstation
data, and their relationships. You can use the snap-in utility to import data from
other sources. For example, you can import address and terminal data from the
switch TAPI database. (For more information about the import tools, see
“Import tools” on page 17.)
You can also use the Communication Control Toolkit snap-in utility to back up
Communication Control Toolkit persistent data.

Planning and Engineering Guide 17
June 2007 Getting started
The Communication Control Toolkit snap-in utility uses Microsoft SQL Server
2000 Desktop Engine (MSDE 2000) to store persistent configuration
information. MSDE databases can store up to 2 Gb of data. The Communication
Control Toolkit does not need to store much information about each user, so the
2 Gb limit does not pose a problem.
Import tools
You can add resources manually, or you can use an import tool. The following
types of import tools are available:
Import IPML Data
This tool allows you to import address data from IPML Service Provider into
Communication Control Toolkit. It is accessible from the tree tab of the
Communication Control Toolkit snap-in utility.
Import M1 TSP Data
This tool allows you to import addresses and terminals from TAPI Service
Provider into Communication Control Toolkit.
Import Active Directory Users
This tool allows you to import the active directory users from the workstations
and the local domain into Communication Control Toolkit.
Import Workstations
This tool allows you to import workstations from the local domain.
TAPI Connector
TAPI Connector provides call control and monitoring to the Nortel legacy
switching platforms. It converts Communication Control Toolkit requests to
TAPI API calls, and TAPI events to Communication Control Toolkit events.
TAPI interfaces
The TAPI Service Provider interfaces with the underlying switching platform in
one of the following ways:
Direct Connect—(Meridian 1/Succession 1000) Direct Connect allows the
TAPI Service Provider to connect directly to the switch using the

18 Communication Control Toolkit
Getting started Standard 5.01
Embedded LAN (ELAN) TCP/IP link. The TAPI Service Provider uses the
proprietary Application Module Link (AML) protocol to communicate with
the switch.
Meridian Link Services (MLS)—(Meridian 1/Succession 1000) The
Meridian Link Services protocol allows the TAPI Service Provider to
connect to Symposium Call Center Server, which, in turn, connects to the
switch. Symposium Call Center Server communicates with the switch
using AML. Meridian Link Services uses TCP/IP on an Ethernet link.
Meridian Link Services is an easy-to-use proprietary protocol.
No matter what the connection protocol, TAPI attempts to normalize all
switching platforms to a single call model. For the most part, TAPI applications
do not need to be aware of what switch they are actually controlling.
Note: The Communication Control Toolkit supports TAPI 3.0 for the
Meridian 1/Succession 1000.
Device types
Communication Control Toolkit supports all of the device types currently
supported by TAPI. These device types include
regular DN
Controlled DN (CDN)
ACD Position ID
IVR port
ACD-DN
These devices are modeled as Address objects. It is possible to determine the
underlying device type from the AddressCapabilities property of the Address
object. Each address is associated with a single Terminal object. In the case of
CDNs, which have no real terminal association, a virtual Terminal object is
instantiated.
Terminals and addresses
Upon initialization, the TAPI Connector uses its database to populate the
Contact Management Framework with all terminals and addresses in its domain.
In general, for a telephony configuration, each terminal references one or two
addresses, and each address references a single Terminal object.

Planning and Engineering Guide 19
June 2007 Getting started
Coexistence
Since the TAPI Connector is another TAPI application, existing legacy TAPI
applications continue to function. A Communication Control Toolkit application
and a TAPI application can both control the same device; however, there are
special design requirements for the TAPI application. (For more information, see
the Nortel Symposium TAPI Service Provider Programmer’s Guide.)
Device to user mapping
Communication Control Toolkit allows you to limit the TAPI devices to which
its users have access. To do so, you use the Device to User Mapping function of
the Communication Control Toolkit snap-in utility. For example, you can
configure Communication Control Toolkit to allow User A to access only the
telephone at his or her desk, and to allow User B to monitor all telephones in a
contact center.
The TAPI Connector has access to all configured devices and their respective
addresses. However, the actual mapping of users to a device occurs in the layers
above the TAPI Connector. The TAPI Connector exposes all that it knows about
the underlying switch without any regard to users.
Note: To define access rights for legacy TAPI applications, you must use the
Microsoft Telephony Management Console.
Call data
Communication Control Toolkit supports three different call data types:
key/value pairs
string
binary
The TAPI Service Provider does not support the new call data types (key/value
pairs and string). It only supports binary data (unstructured call data in single
array of up to 4 kb). Any structuring of the TAPI call data occurs outside the
TAPI Service Provider.
TAPI device-specific functions
The TAPI Service Provider uses line device-specific commands to perform
requested operations. The commands are hidden from the Contact Management
Framework and the TAPI Connector.

20 Communication Control Toolkit
Getting started Standard 5.01
The line device specific-commands are particular to the switch type to which the
TAPI Service Provider is connected.
SAPphone support
Communication Control Toolkit is compatible with SAPphone* R/3, release
2.54, which is the soft phone interface to mySAP* customer relationship
management (CRM) solutions.
Note: If you use SAPphones for CRM functionality, Nortel recommends that
you install the SAPphone server, release 3, on a separate server platform.
IPML Connector
The IPML Connector provides an interface between the Contact Management
Framework and the IPML environment, thus providing access to call control and
monitoring functionality on Nortel and third-party switching platforms. The
IPML Connector provides a normalized interface to the switch links, exposing a
single call control and monitoring model to clients. It is similar in functionality
to the TAPI Connector and is used in the following environments:
a contact center that employs a third-party switch (Avaya G3 or Genesys
T-Server)
a contact center with legacy ActiveX Toolkit Desktop clients
an IVR-only implementation
The IPML Connector may also be required to forward device monitoring
information to the Contact Management Framework for Communication Control
Toolkit agent control.
.
CAUTION
Risk of CPU contention, increased network loading, disk
access degradation
Do not install the SAPphone server on the Communication Control
Toolkit server.