4Differences between TAPI 3.0 and TAPI 3.1 for CCT 5.0OverviewThe purpose of this document is to list the changes in the TAPI 3.1 core component ofNortel Communication Control Toolkit 5.0.List of Changes1. Licence file modification for TAPI 3.1TAPI 3.1 licensing has been updated and 3.0 licenses are no longer valid. If ‘CCT’ is notenabled in the TAPI 3.1 license then TAPI will not work and no lines can be opened. TheTAPI environment type (Knowledge Worker or MLSM) is now also a license feature.2. Route Selected MessagingTAPI 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 RouteSelected message.The CDN call waits in a queue until a Route Selected message is received and will not beremoved 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 androuted to an agent.3. CDN Acquire/De-AcquireTAPI 3.1 for CCT allows a user to acquire and de-acquire an existing CDN using thelineDevSpecific function.4. Event Log Messaging ModifiedEvent Log Messages has been added for time outs on the Nortel TSP startup andshutdown.