Nortel CCT Instruction Manual

1
Nortel Communication Control Toolkit
Release 5.0
Differences between TAPI 3.0 and TAPI 3.1 for CCT 5.0
Issue: V0.3
Date: April 14, 2005
Abstract :
This document lists the differences between TAPI 3.0.0.8 and TAPI 3.1.4.2 for CCT 5.0.
_____________________________________________________________________
PROPRIETARY INFORMATION: The information contained in this document is the property of Nortel
Networks. Except as specifically authorized in writing by Nortel Networks, the holder of this document
shall keep all information contained herein confidential and shall protect same in whole or in part from
disclosure and dissemination to all third parties
*Nortel, the Nortel logo and the Globemark are trademarks of Nortel.
NOTICE: Notwithstanding any explicit confidentiality or proprietary markings to the contrary, the
information contained in this document has been reviewed and approved for public disclosure
by Nortel. However, the access to, use and disclosure of this document and the information
contained therein continue to be subject to copyright and other restrictions, conditions and
limitations as detailed in the Terms of Use. (http://www.nortel.com/help/legal/index.html)

2
Revision History
Issue
No.
Release Date Reason for Issue Author
0.1 April 12, 2005 First draft Martha Stundon
0.2 April 14, 2005 Second draft Martha Stundon
0.3 April 14, 2005 Review updates David O’Connell

3
Table of Contents
Differences between TAPI 3.0 and TAPI 3.1 for CCT 5.0................................................. 1
Differences between TAPI 3.0 and TAPI 3.1 for CCT 5.0................................................. 4
Overview ......................................................................................................................... 4
List of Changes................................................................................................................ 4
1. Licence file modification for TAPI 3.1............................................................... 4
2. Route Selected Messaging .................................................................................. 4
3. CDN Acquire/De-Acquire................................................................................... 4
4. Event Log Messaging Modified.......................................................................... 4
5. TAPI 3.1 Error Message rewording .................................................................... 5

4
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
1. Licence file modification for TAPI 3.1
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.
2. Route Selected Messaging
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.
3. CDN Acquire/De-Acquire
TAPI 3.1 for CCT allows a user to acquire and de-acquire an existing CDN using the
lineDevSpecific function.
4. Event Log Messaging Modified
Event Log Messages has been added for time outs on the Nortel TSP startup and
shutdown.

5
5. TAPI 3.1 Error Message rewording
ID New Error Message Old Error Message
1. CALL_STATUS_CDN_NOT_ACQUIRED,
LINEERR_RESOURCEUNAVAIL,
CALL_STATUS_CDN_NOT_ACQUIRED,
LINEERR_OPERATIONFAILED,
2. CAUSE_TARGET_DN_INVALID,
LINEERR_TARGETNOTFOUND,
CAUSE_TARGET_DN_INVALID,
LINEERR_OPERATIONFAILED,
3. CAUSE_CDN_IS_NOT_CONFIGURED,
LINEERR_RESOURCEUNAVAIL,
//CAUSE_CDN_IS_NOT_CONFIGURED,
LINEERR_OPERATIONFAILED,
4. CAUSE_POLL_TIMER_IS_OUT_OF_RANGE,
LINEERR_INVALTIMEOUT,
//CAUSE_POLL_TIMER_IS_OUT_OF_RANGE,
LINEERR_OPERATIONFAILED,
5. CAUSE_DEVICE_NOT_A
V
AILABLE,
LINEERR_RESOURCEUNAVAIL,
//CAUSE_DEVICE_NOT_AVAILABLE,
LINEERR_OPERATIONFAILED,
6. CAUSE_BAD_PARAMETER_PASSED_TO_FUN
CTION, LINEERR_INVALPARAM,
//CAUSE_BAD_PARAMETER_PASSED_TO_FUNCTION,
LINEERR_OPERATIONFAILED,
7. CAUSE_OUT_OF_MEMORY_LOCAL,
LINEERR_NOMEM,
//CAUSE_OUT_OF_MEMORY_LOCAL,
LINEERR_OPERATIONFAILED,
8. CAUSE_DN_IS_BUSY,
LINEERR_INUSE,
//CAUSE_DN_IS_BUSY,
LINEERR_OPERATIONFAILED,
9. CAUSE_CANNOT_ASSUME_COMMAND_WHILE
_LOGGED_ON,
LINEERR_OPERATIONUNAVAIL,
//CAUSE_CANNOT_ASSUME_COMMAND_WHILE_LOGGED_ON,
LINEERR_OPERATIONFAILED,
10. CAUSE_OPTION_NOT_AVAILABLE_TO_CUS
TOMER, LINEERR_INVALFEATURE,
//CAUSE_OPTION_NOT_AVAILABLE_TO_CUSTOMER,
LINEERR_OPERATIONFAILED,
11. // Unsuccessful call termination
CS_DESTINATION_RESOURCE_BLOCKING,
LINEERR_RESOURCEUNAVAIL,
//CS_DESTINATION_RESOURCE_BLOCKING,
LINEERR_OPERATIONFAILED,
12. // Invalid parameters
CS_INVALID_CALLING_TN,
LINEERR_INVALPARAM,
//CS_INVALID_CALLING_TN,
LINEERR_OPERATIONFAILED,
13. CS_INVALID_CALLING_DN,
LINEERR_INVALPARAM,
//CS_INVALID_CALLING_DN,
LINEERR_OPERATIONFAILED,
14. // Unsuccessful call origination
CS_ORIGINATION_PARTY_BUSY,
LINEERR_INUSE,
//CS_ORIGINATION_PARTY_BUSY,
LINEERR_CALLUNAVAIL,
15. CS_ORIGINATION_RESOURCE_BLOCKING,
LINEERR_RESOURCEUNAVAIL,
//CS_ORIGINATION_RESOURCE_BLOCKING,
LINEERR_OPERATIONFAILED,
16. CS_INCOMPLETE_CALLING_DN,
LINEERR_INVALPARAM,
//CS_INCOMPLETE_CALLING_DN,
LINEERR_OPERATIONFAILED,
17. CS_INVALID_CALLED_DN,
LINEERR_INVALADDRESS,
//CS_INVALID_CALLED_DN,
LINEERR_OPERATIONFAILED,
18. CS_INCOMPLETE_CALLED_DN,
LINEERR_INVALADDRESS
//CS_INCOMPLETE_CALLED_DN,
LINEERR_OPERATIONFAILED,
19. CS_INVALID_CALLED_TN,
LINEERR_INVALPARAM,
//CS_INVALID_CALLED_TN,
LINEERR_OPERATIONFAILED,
20. CS_INVALID_ORIGINATION_MANNER,
LINEERR_INVALPARAM,
//CS_INVALID_ORIGINATION_MANNER,
LINEERR_OPERATIONFAILED,
21. CS_INVALID_DESTINATION_MANNER,
LINEERR_INVALPARAM,
//CS_INVALID_DESTINATION_MANNER,
LINEERR_OPERATIONFAILED,
22. CS_INVALID_ORIGINATION_USER_TYPE,
LINEERR_INVALPARAM,
//CS_INVALID_ORIGINATION_USER_TYPE,
LINEERR_OPERATIONFAILED,
23. CS_INVALID_CUSTOMER_NUMBER,
LINEERR_INVALPARAM,
//CS_INVALID_CUSTOMER_NUMBER,
LINEERR_OPERATIONFAILED,
24. CS_SYSTEM_OR_DATABASE_ERROR,
LINEERR_INVALPARAM
//CS_SYSTEM_OR_DATABASE_ERROR,
LINEERR_OPERATIONFAILED,