List Of Changes; Licence File Modification For Tapi; Route Selected Messaging; Cdn Acquire/De-Acquire - Nortel CCT Release Note

Differences between tapi 3.0 and tapi 3.1

Hide thumbs Also See for CCT:

Differences between TAPI 3.0 and TAPI 3.1 for CCT 5.0

Overview

The purpose of this document is to list the changes in the TAPI 3.1 core component of

Nortel Communication Control Toolkit 5.0.

List of Changes

TAPI 3.1 licensing has been updated and 3.0 licenses are no longer valid. If 'CCT' is not

enabled in the TAPI 3.1 license then TAPI will not work and no lines can be opened. The

TAPI environment type (Knowledge Worker or MLSM) is now also a license feature.

TAPI 3.1 for CCT now supports Route Selected messages. When a call is made to a CDN,

a Route Request message is sent to the switch. TAPI 3.1 now handles the returned Route

Selected message.

The CDN call waits in a queue until a Route Selected message is received and will not be

removed from the queue when a timeout value is reached, as is the case in TAPI 3.0.

When the Route Selected message is received the call is removed from the call queue and

routed to an agent.

TAPI 3.1 for CCT allows a user to acquire and de-acquire an existing CDN using the

lineDevSpecific function.

Event Log Messages has been added for time outs on the Nortel TSP startup and

shutdown.

Table of Contents

Cct 5.0