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 7.6 releases of Network T-Server for MCI.

• 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.
• The T-Server Common Part is common code used by all T-Servers, Network T-Servers, and the IVR Server's TServer_IVR and TServer_IVR_Network applications. 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 7.6.x.

Use of Third-Party Software

Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize functionality of commercial or non-commercial third parties. For specific information on any third-party software used in this product, see the Read Me.

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This release of Network T-Server was built using TSCP release number 7.6.008.11. Consult the TSCP release note for information on changes that may affect the functionality of your particular type of Network T-Server.

There are no restrictions for this release. This section describes new features that were introduced in this release of Network T-Server for MCI.

• The Network T-Server for MCI is able to determine the method in which calls are default-routed and can report this information to Stat Server using the new mci-max-ack-nack-wait option.

  The option description and values for mci-max-ack-nack-wait are:

  mci-max-ack-nack-wait
  
  Default Value: 100
  Valid Values: Any positive integer, or 0
  Changes Take Effect: Immediately

  Specifies the interval (in milliseconds) that T-Server waits for an Acknowledged or Not Acknowledged message from the Gateway, if options mci-ack-flag, and mci-nack-flag are set to a value of true. To disable this option, set it to a value of 0 (zero).

• When the mci-max-ack-nack-wait option has a positive value and the mci-ack-flag and mci-nack-flag options are set to true, the EventRouteUsed event for default-routed calls will contain in the Extensions attribute the key DEFAULT_ROUTE_REASON with one of four possible values:

  Key	Value	Description
  DEFAULT_ROUTE_REASON	ROUTER	Universal Routing Server caused the call to be default-routed, and the Gateway sent an Acknowledged message to T-Server.
  	ROUTER_TIMEOUT	T-Server has timed out waiting for a response from Universal Routing Server.
  	SCP	A Not Acknowledged message was sent from the Gateway to T-Server.
  	SCP_TIMEOUT	T-Server did not receive an Acknowledged, or Not Acknowledged message from the Gateway within the time specified by the mci-max-ack-nack-wait option.

  (ER# 220658006)

Corrections and Modifications

There are no corrections or modifications in this release of Network T-Server for MCI.

Top of Page

Supported Operating Systems

New in This Release

This release of Network T-Server was built using TSCP release number 7.6.008.06. Consult the TSCP release note for information on changes that may affect the functionality of your particular type of Network T-Server.

This is a hot fix for this product. This section describes new features that were introduced in this release of Network T-Server for MCI.

• Support for ANI II Originating Line Information (OLI). Beginning with version 91, the MCI Gateway protocol includes the Originating Line Information (OLI) specification. Network T-Server includes the Originating Line Information from such messages in four key-value pairs in the AttributeExtensions attribute of the EventRouteRequest event:


• Key: DIALEDCC
  Value: A string containing the Country Code of the dialed number, maximum length: 15.
  This key-value pair is optional.
• Key: ANICC
  Value: A string containing the Country Code of the ANI digits, maximum length: 15.
  This key-value pair is optional.
• Key: OLT
  Value: An integer containing the Originating Line Type.
  This key-value pair is optional.
• Key: ACCESSTYPE
  Value: An integer which identifies the type of network access.
  This key-value pair is optional.

Corrections and Modifications

There are no corrections or modifications in this release of Network T-Server for MCI.

Top of Page

Supported Operating Systems

New in This Release

This release of Network T-Server was built using TSCP release number 7.6.008.06. Consult the TSCP release note for information on changes that may affect the functionality of your particular type of Network T-Server.

There are no restrictions for this release. There are no new features introduced in this release of Network T-Server for MCI.

Corrections and Modifications

There are no corrections or modifications in this release of Network T-Server for MCI.

Top of Page

Supported Operating Systems

New in This Release

This release of Network T-Server was built using TSCP release number 7.6.008.03. Consult the TSCP release note for information on changes that may affect the functionality of your particular type of Network T-Server.

There are no restrictions for this release. This section describes new features that were introduced in the initial 7.6 release of Network T-Server for MCI.

• The Network T-Server for MCI now supports the Red Hat Enterprise Linux OS.

Corrections and Modifications

There are no corrections or modifications in the initial 7.6 release of Network T-Server for MCI.

Top of Page

Known Issues and Recommendations

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

When the mci-max-ack-nack-wait option is used, and T-Server does not receive a RequestRouteCall within the configured timeout, it issues a default-routing instruction to the SCP and sends EventRouteUsed without awaiting SCP acknowledgement. When a subsequent Acknowledged or Not Acknowledged response is received, an EventHardwareError message is generated. (ER# 223293995)

For Network T-Server for MCI, the value of the customer-id configuration option must be an 8-character numeric value. (ER# 100154)

Network T-Servers do not support warm or hot standby. Instead, they use a load sharing redundancy schema. See the Framework 7.6 Network T-Server Deployment Guide for your Network T-Server for more information.

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.

Tru64 UNIX 4.0F is no longer supported.

Windows NT operating system is no longer supported.

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 Deployment Guide first.

• The Framework 7.6 Network T-Server for MCI Deployment Guide contains detailed reference information for the Genesys Framework 7.6 Network T-Server for MCI, including configuration options and specific functionality.

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

• The Genesys 7 Events and Models Reference Manual contains an extensive collection of events and call models describing core interaction processing in Genesys environments.

• The Voice Platform SDK 7.6 .NET (or Java) API Reference contains technical details of T-Library functions.

• The 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.

• Genesys Supported Operating Environment Reference Manual contains information about supported operating systems and databases.

Top of Page

Data Encryption Standard (DES) Copyright Information

Copyright � 1995 Eric Young (eay@mincom.oz.au) All rights reserved.

This package is an DES implementation written by Eric Young (eay@mincom.oz.au). The implementation was written so as to conform with MIT's libdes.

This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to all code found in this distribution.

Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed.

If this package is used in a product, Eric Young should be given attribution as the author of that the SSL library. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. All advertising materials mentioning features or use of this software must display the following acknowledgement: This product includes software developed by Eric Young (eay@mincom.oz.au).

THIS SOFTWARE IS PROVIDED BY ERIC YOUNG "AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

The license and distribution terms for any publicly available version or derivative of this code cannot be changed, i.e. this code cannot simply be copied and put under another distribution license [including the GNU Public License.]

The reason behind this being stated in this direct manner is past experience in code simply being copied and the attribution removed from it and then being distributed as part of other packages. This implementation was a non-trivial and unpaid effort.

Top of Page