Release Note

Contents

Introduction

As of February 1, 2012, Genesys is no longer an affiliate of Alcatel-Lucent; any indication of such affiliation within Genesys products or packaging is no longer applicable. Please see the Genesys website at http://www.genesyslab.com for more details.

This release note applies to all 8.0 releases of T-Server for Tadiran Coral.

• Links in the Contents section enable you to access information regarding a specific release. Releases are listed by version number rather than in date order. For this reason, a recent release may be listed after earlier releases, if the version number is lower. Except when otherwise noted in the information for a specific release, each release includes all of the features and corrections that were introduced for the applicable operating system at earlier dates, regardless of the version numbering.
• The Release Number table lists the supported operating systems for each release at a high level. For more detailed information, see the Genesys Supported Operating Environment Reference Manual.
• The Known Issues and Recommendations section is a cumulative list. It includes information on when individual items were found and, if applicable, corrected.
• The Corrections and Modifications section for each release may list additional issues that were corrected without first being documented as Known Issues.
• The Discontinued Support section is cumulative. It lists functionality that is no longer supported and the release number of the version in which support was discontinued.
• You can find information about changes and corrections to functionality common to all T-Servers in the release note for T-Server Common Part release 8.0.x.
• Your T-Server's name correlates generally with the name of the switch you intend to use, but vendor switch names often change. For full details on the name(s) of the switch intended for use with this T-Server, see the Genesys Supported Media Interfaces Reference Manual.

Use of Third-Party Software

Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize third-party functionality. For additional information about third-party software used in this product, see the Read Me. Please contact your technical support representative if you have any questions.

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.0.101.08. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

This is a hot fix for this product. This release does not contain any new features or functionality.

Corrections and Modifications

This release includes the following correction and modification:

T-Server no longer rejects TSingleStepTransfer requests issued by devices in a three-way conference call. Previously, T-Server would sometimes reject the TSingleStepTransfer request and would send the following message: Conference member limit exceeded. (ER# 306996958)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.0.101.08. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

There are no restrictions for this release. This section describes new features that were introduced in this release.

• T-Server now supports Account code and WalkAway code features. The following configuration options have been added to support these features:

  • accode-agent—notifies T-Server to use Account codes as agent WalkAway codes.
  • accode-data—specifies how T-Server maps the switch Account codes.
  • accode-index—allows T-Server to attach multiple Account codes to the call.
  • accode-name—specifies the data key name (UserData or Extensions) under which T-Server attaches the Account code to the call.
  • accode-private-event—enables or disables the use of EventPrivateInfo events for reporting Account and/or WalkAway codes.
  • acw-retain-call—notifies T-Server to retain the last agent business call while the agent is in the ACW (after-call work) state for user data updates after the call is released.
  • acw-retain-lock—specifies the time (in seconds) that T-Server locks the call for Call Concentrator using the EventUserEvent event.

  accode-agent
  Default Value: false
  Valid Values: true, false
  Changes Take Effect: Immediately

  This configuration option notifies T-Server to use Account codes as agent WalkAway codes. If this configuration option is set to true and the agent is in the NotReady state when the switch reports an Account code, T-Server sends another EventAgentNotReady event with the Extensions attribute ReasonCode set to the value of the reported Account code.

  accode-data
  Default Value: none
  Valid Values:

  none:	T-Server does not map the switch Account codes to the call user data.
  udata:	T-Server attaches reported Account codes as user data by using configured keys.
  ext:	T-Server attaches user data as an Extensions attribute to all call events.

  Changes Take Effect: Immediately

  This configuration option specifies how T-Server maps the switch Account codes.

  accode-index
  Default Value: false
  Valid Values: true, false
  Changes Take Effect: Immediately

  This configuration option allows T-Server to attach multiple Account codes to the call. Each new unique Account code is attached to the call (as either UserData or Extensions) with the data key name configured by the configuration option accode-name with an appended underscore and an incremental integer index, starting from 1 (for example, AccountCode_1). T-Server keeps the non-indexed key updated with the latest value obtained, regardless of the setting of this configuration option.

  accode-name
  Default Value: AccountCode
  Valid Values: Any valid key name
  Changes Take Effect: Immediately

  This configuration option specifies the data key name (UserData or Extensions) under which T-Server attaches the Account code to the call.

  accode-private-event
  Default Value: false
  Valid Values: true, false
  Changes Take Effect: Immediately

  This configuration option enables or disables the use of EventPrivateInfo events for reporting Account and/or WalkAway codes.

  acw-retain-call
  Default Value: false
  Valid Values: true, false
  Changes Take Effect: Immediately

  This configuration option specifies whether T-Server retains the last agent business call while the agent is in the ACW state for user data updates after the call is released. Used in conjunction with the configuration option accode-data, this configuration option allows any subsequent Account code to be attached to the previous call.

  When this configuration option is enabled, T-Server uses a Call Locking mechanism (see Call Concentrator 7 Deployment Guide) so that the Account code can be added to the Global Call Details Records (GCDR) table after the call has been released. T-Server sends the Account code in the EventUserEvent event rather than the code in the EventAttachedDataChanged event, so as to not confuse existing desktop applications.

  Warning! Use this option with caution. Unsolicited call events on behalf of a released call may cause problems with other applications.

  acw-retain-lock
  Default Value: 0 (zero)
  Valid Values: Any positive integer
  Changes Take Effect: Immediately

  This configuration option specifies the time (in seconds) that T-Server locks the call for Call Concentrator by using the EventUserEvent event.

  When this configuration option is enabled,T-Server uses a Call Locking mechanism (see Call Concentrator 7 Deployment Guide) so that the Account code can be added to the Global Call Details Records (GCDR) table after the call has been released. T-Server sends a EventUserEvent event with the reserved extension key LockCall and the value provided. Normally, this value should be greater than the value of ACW. A value of 0 (zero) signifies that call locking is not used.

(ER# 262640483, ER# 262640481)

• T-Server now supports the configuration option allow-external-redirect to specify whether the redirection to external and unmonitored destinations is allowed by T-Server.

  allow-external-redirect
  Default Value: false
  Valid Values: true, false
  Changes Take Effect: Immediately

  This configuration option specifies whether the redirection to external and unmonitored destinations is allowed by T-Server. When the redirection to an external destination is not allowed, T-Server uses a transfer to redirect calls to an external destination. T-Server also blocks the routing of calls to external destinations as this functionality depends on redirection. When redirection to an external destination is allowed, the redirect to an external destination is performed normally and routing to external destinations is not blocked.

  Note: If the redirection to an external destination is allowed in T-Server, but not configured in the switch, stuck calls may result in some scenarios where an emulated Routing Point is used to route a call to an invalid destination.

  (ER# 262535634)

• T-Server now supports the configuration option legal-guard-reason to indicate that the agent is in legal guard.

  legal-guard-reason
  Default Value: LegalGuard
  Valid Values: Null or any valid string
  Changes Take Effect: Immediately

  This configuration option specifies the extension key used by T-Server to indicate that the agent is in legal guard. T-Server adds this extension key to the EventAgentNotReady event, signalling the start of legal guard. If this configuration option is set to a null string then no extension key is added.

  (ER# 256528383)

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now handles an agent-requested change in agent mode from an emulated ACW (after-call work) state to a NotReady state when WorkMode = 0 (Unknown). Previously, T-Server did not generate a required event that matched the requested agent state on the switch; T-Server treated the request as an extended ACW request. (ER# 266521647)

T-Server now supports CTI link (CLA) version 8.02.14. (ER# 265049431, ER# 262640485)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.0.101.07. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

This is a hot fix for this product. This release does not contain any new features or functionality.

Corrections and Modifications

This release includes the following correction and modification:

T-Server no longer exits unexpectedly in any of the following scenarios:

• An access violation occurring during the processing of a conference switch event.

• An access violation occurring during the processing of an established switch event, where the event was the first one for the call.

• An access violation occurring during the processing of a device snapshot or switch delivered events.

Previously, T-Server incorrectly handled the switch messaging, which caused T-Server to exit unexpectedly in the first two scenarios. The third scenario occurred only as a result of memory corruption following one of the other two scenarios.

(ER# 266384546)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.0.101.03. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

There are no restrictions for this release. This section describes new features that were introduced in this release.

• T-Server now supports CTI link (CLA) version 8.02.06.

• T-Server now supports the configuration option legal-guard-reason.

  legal-guard-reason
  Default Value: LegalGuard
  Valid Values: Any valid string
  Changes Take Effect: Immediately

  Specifies the value of the extension used by T-Server to indicate that the agent is in legal guard. T-Server adds this extension to the EventAgentNotReady event, which signals the start of legal guard. If this option is set to an empty string then no extension is added.

(ER# 256678181)

Corrections and Modifications

This release includes the following correction and modification:

T-Server no longer uses excessive memory (up to 20 bytes per call) when releasing a call. (ER# 256163761)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.0.100.12. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

There are no restrictions for this release. This section describes new features that were introduced in the initial 8.0 release of Tadiran Coral. Refer to Framework 8.0 T-Server for Tadiran Coral Deployment Guide for feature descriptions.

• T-Server now supports a call type prediction procedure to assign a call type on a "best possible guess" basis on occasions where the CTI information is either insufficient or arrives too late for T-Server to assign a definite call type.

• T-Server now supports call release tracking to provide information about which party initiated the release of a call. This can be configured using the releasing-party-report configuration option.

• T-Server now supports alarm messages for unsuccessful routing scenarios.

• T-Server now supports bandwidth monitoring on a CTI link and can notify Genesys Management Layer when Configuration Layer limits are exceeded.

• T-Server now supports two major new enhancements to queue handling: request conflict resolution and a new device queue.

• T-Server now supports enhanced emulated agent functionality.

• T-Server now supports enhanced business call processing. This can be configured using the agent-only-private-calls configuration option.

Corrections and Modifications

This release does not include any corrections and modifications.

Top of Page

Known Issues and Recommendations

This section provides the latest information on known issues and recommendations associated with this product.

When T-Server, running on Windows Server 2008 32-bit or 64-bit, exits due to a SIGBREAK, T-Server does not close the *.snapshot.log file before exiting. (ER# 250960526)

When installing T-Server on UNIX, the following message will appear:

Unable to find configuration information.
Either you have not used configuration wizards and the GCTISetup.ini file was not created or the file is corrupted.

This is an informational message indicating that the Configuration Server login information has not been populated in the installation script, and will be requested during the installation. (ER# 251199034)

Single-step transfer over ISCC is not possible when the configuration option cast-type value is set to direct-ani. (ER# 250835963)

The installation of T-Server using the Wizard is not supported for this release. (ER# 250174539)

T-Server does not support deletion of an external party from a conference call in the following scenario:

1. A three-party conference call is established. One of the members of the conference call is an external party.
2. A request to delete the external party from the conference call is made.
3. T-Server returns an error with an invalid ConnID attribute.

(ER# 249680073, 249680035)

Switch-specific behavior: Call-forwarding requests to an external DN is not supported. (ER# 248766503)

T-Server reports the incorrect OtherDN value in the following scenario:

1. A call from an unmonitored DN to an external DN is established and answered. The unmonitored DN is not configured in Configuration Manager, nor is it registered with T-Server.
2. A transfer (either two-step or blind) to a monitored DN is initiated and completed. The call is now between the external DN and the monitored DN. The OtherDN value equals the unmonitored DN for the rest of the call.

(ER# 247960823, 247960811)

TRedirectCall to an unmonitored destination is transformed to a supervised transfer request (TAnswercall, TInitiateTransfer, and TCompleteTransfer). This is to overcome the problem of the switch dropping the call if the destination of a redirect request cannot be reached. (ER# 247713830)

Switch-specific behavior: If a consultation call is made to an ACD Queue with no agents ready, it is not diverted once an agent becomes ready. (ER# 247428928)

Switch-specific behavior: A call which has been diverted from a queue to an agent cannot be redirected back to the queue using TRedirectCall. Therefore, the configuration option agent-np-answer-overflow, when set to the value recall, cannot be used for real agents where the destination of the recall is to a Coral Hunt Group. (ER# 246886831)

Switch-specific behavior: The switch does not report silent monitoring information in the CSTA events. (ER# 245733935)

When performing an upgrade from 7.x to 8.0, the CTI Link must be updated to CSTA III. For this reason, a service interruption will be needed. (ER# 244505181)

Top of Page

Discontinued Support

This section documents features that are no longer supported in this software. This cumulative list is in release-number order with the most recently discontinued features at the top of the list.

There are no discontinued features or functions for this product.

Top of Page

Internationalization

Information in this section is included for international customers.

There are no known internationalization issues for this product.

Top of Page

Additional Information

Additional information on Genesys Telecommunications Laboratories, Inc. is available on our Technical Support website. The following documentation also contains information about this software. Please consult the Framework 8.0 T-Server for Tadiran Coral Deployment Guide first.

• Framework 8.0 T-Server for Tadiran Coral Deployment Guide contains detailed reference information for the Genesys Framework 8.0 T-Server for Tadiran Coral including configuration options and specific functionality.

• Framework 8.0 Deployment Guide helps you configure, install, start, and stop Framework components.

• The Voice Platform SDK 8.0 .NET (or Java) API Reference and the Genesys Events and Models Reference Manual contains the T-Library API, information on TEvents, and an extensive collection of call models.

• Genesys Migration Guide contains a documented migration strategy for each software release. Please refer to the applicable portion of this guide or contact Genesys Technical Support for additional information.

Product documentation is provided on the Technical Support website, the Genesys Documentation wiki, and the Documentation Library DVD (produced monthly) or the Developer Documentation CD.

Note: For the DVD/CD, the New Documents on this DVD/CD page indicates the production date for that disc. Due to disc production schedules, documentation on the Technical Support website may be more up-to-date than what is available on disc immediately after a product is released or updated. To determine the version of a document, check the version number that is located on the second page in PDFs or on the About This File topic in Help files.

Top of Page