Release Note

.NET Web API Server and Samples

7.6.x

Genesys Telecommunications Laboratories, Inc. 2008-2009

Contents

Introduction

Release Number AIX HP-UX Linux Solaris Tru64 UNIX Windows
7.6.100.03 [01/30/09] – General           X
7.6.000.07 [02/15/08] – General           X

Link to 7.5 Product Release Note (Cumulative)
Known Issues and Recommendations
Discontinued Support
Internationalization
Additional Information


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 .NET Web API Server and Samples.

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.


Release Number 7.6.100.03 [01/30/09] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

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

New in This Release

The following restrictions apply to this release.

This release does not contain any new features or functionality.

Corrections and Modifications

This release also includes the following corrections and modifications:


When submitting a chat request, .NET Web API Server now correctly sends an endpoint name. Previously, it sent a queue name instead. (ER# 215418841)


Now you are able to install .NET Web API Server on a Windows 2003 Server on .NET 2.0 SP 1. Previously, a severe internal error Microsoft .NET Framework nLevel in-parameter: Unknown release level of Microsoft .Net Framework 9 terminated the installation procedure. (ER# 210075771)


Upon startup, LoadBalancer now connects within the hard-coded timeout, even when the primary Configuration Server is running in Backup mode. (ER# 172630685)


Top of Page


Release Number 7.6.000.07 [02/15/08] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

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

New in This Release

The following restrictions apply to this release.

This section describes new features that were introduced in the initial 7.6 release of .NET Web API Server and Samples.

Corrections and Modifications

This release includes the following corrections and modifications that were made between Release 7.5 or earlier releases and the initial 7.6 release:


Now the TestTool Sample works correctly without any file modification. Previously, for the Test Tool to function properly, you had to manually modify the .aspx files. (ER# 108800185)


This release includes all fixes made in the previous releases of this product (including hot fix releases) at the time of this intial 7.6 release.


Top of Page


Known Issues and Recommendations

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


To create the log file, you must specify the full path to the file in the log/all section on the Options tab of the Web API Server.NET application in Configuration Manager. For example: C:\Program Files\GCTI\MCR 7.6.1\.NET Web API Server and Samples\log\WebApiServerDotNET.

Workaround:

  1. Specify the full path to the log file for the Web API Server .NET application. By default, the Web API Server .NET application does not have rights to create a log file in the default IIS directory.
  2. For the user under which the IIS Server is working, set their permission to full access (read/write/modify) in the directory where the log files are located. The simplest method is to grant full access to Everyone for the log file directory.

MCR .NET Web API Server cannot gather predefined statistics from Stat Server installed on a Windows operating system.

Workaround:

Install and use Stat Server on a UNIX operating system. (ER# 217706766)

Found In: 7.6.100.03 Fixed In: 

On the ChatSelfTest page in the Result Description for Checking chat WebAPI port settings, the webapi-port option should be used instead of the flex-disconnect-timeout option. (ER# 217046611)

Found In: 7.6.100.03 Fixed In: 

.NET Web API Server does not write about the reconnection to the backup message server to the event log. (ER# 211277576)

Found In: 7.6.100.03 Fixed In: 

If changes have been made to tenants in Configuration Manager (for example, names, DBIDs), LoadBalancer might not update this information on startup when it reads information from Configuration Server.

Workaround:

Restart MCR Web API Server if any information related to tenants (for example: names, DBIDs) has been changed in Configuration Server. (ER# 168180935)

Found In: 7.6.000.07 Fixed In: 

During installation, if you set the default-code-page option to a code page not present on the destination server, your selected code page fails to update. In this case, you must manually input the code page value into the file encoding field. However, if you pre-configure your host for the particular local language you want to use (keyboard, language settings, and regional settings all set to your local language in the Windows Control Panel), then the selected code page updates without a problem.

To manually update the code page, use the following workaround.

Workaround:

  1. After installation, open the IIS Manager.
  2. Locate the WebAPIServer761 virtual root, and select the properties of the root.
  3. Click the ASP.NET tab.
  4. Click the Edit Configuration button.
  5. Click Application tab.
  6. Enter desired encoding into the File encoding field. For example, windows-1251, (cyrillic alphabet).
  7. Click Ok.

(ER#  106856255)

Found In: 7.5.000.03 Fixed In: 

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.


Top of Page


Internationalization

Information in this section is included for international customers.


Tenant names in Korean are corrupted on the Loadbalancing page. (ER# 114085802)


Time formats in Korean are corrupted on the Loadbalancing page. (ER# 114085804)


The test tool displays corrupted Tenant names in Korean. (ER# 163994931)


When an e-mail request is sent in a Korean environment while using multiple languages at the same time, some characters may be displayed as ?. (ER# 123328426)


If .NET Web API server samples for chat use multiple languages, some characters may be displayed as ?. (ER# 123328421)


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.

Top of Page