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 NEC NEAX/APEX.

• 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 on 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.300.04. 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 corrections and modifications:

This version of T-Server is built with TSCP 8.0.300.04, which corrects the following issue:

When completing a single-step transfer in a multi-site environment using the ISCC transaction type pullback, T-Server now correctly propagates the ReferenceID attribute in EventReleased only to the client that originated the request. Previously, T-Server propagated ReferenceID in EventReleased to all its clients. (ER# 275435784)

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.300.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.

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 corrections and modifications:

T-Server now properly processes the following scenario:

1. An agent makes a blind call transfer from an Attendant Console.
2. After a period of time, the unanswered call is returned to the Attendant Console.

In the scenario above, the switch sends an SMFN 2 (STS=2) Answer Holding event for the Attendant Console.

Previously, T-Server was unable to process such events, therefore, subsequent events were incorrectly handled causing T-Server states inconsistent with the switch.

(ER# 262378351)

T-Server now correctly encodes the InvokeID parameter in the 0x0080 to 0x00FF, and the 0xFF80 to 0xFFFF ranges in OAI messages sent to the PBX.

The InvokeID in the 0x0080 to 0x00FF range is now encoded in 2 bytes with 00 padding . Previously, T-Server encoded the InvokeID value in 1 byte without 00 padding.
The InvokeID in the 0xFF80 to 0xFFFF range is now encoded in 1 byte, and the higher bits are trimmed. Previously, T-Server encoded the InvokeId in 2 bytes.

(ER# 262641807)

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.300.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 a new configuration option, backup-reset-threshold-interval.
  
  backup-reset-threshold-interval
  Default Value: 0
  Valid Values: 0, or any positive integer
  Changes Take Effect: Immediately
  
  Specifies the time interval (in seconds) that T-Server, when operating in Backup mode, waits before releasing its internal state after it has lost a synchronization link with the primary T-Server. When set to 0, the backup T-Server reset is disabled.
  
  (ER# 255165268)

• T-Server now supports NEC SV8500.

Corrections and Modifications

This release also includes the following corrections and modifications:

T-Server now correctly distributes an EventHeld message in the following scenario:

1. An agent establishes a consultation call.
2. The agent places the consultation call on hold and returns to the original caller.
3. The original caller places the agent on hold.
4. The switch sends a SMFN6 � Hold event notification.
5. T-Server distributes an EventHeld message for the correct party (the original caller of the initial call).

The alive-message-timer option now works correctly, as described in the following description. Previously, the alive-message-timer did not work as expected. Sometimes it took up to six minutes for T-Server to detect a link failure.

alive-message-timer
Default Value: 60000
Valid Values: Any integer from 0�100000
Changes Take Effect: Immediately

Specifies the time interval (in milliseconds) that T-Server waits before sending an alive message (heartbeat) to the switch. T-Server sends the alive message only when there is no request/response activity within the alive-message-timer interval. A corresponding heartbeat response is expected from the switch within the alive-message-timer interval. If the heartbeat response is not received for three consecutive heartbeat requests, T-Server resets the link. If set to 0, T-Server stops sending alive messages to the switch.

(ER# 256300891)

T-Server no longer reads unrelated Agent Login information from the configuration database. Previously, if a large number of Agent Logins were configured, T-Server sometimes became unresponsive, resulting in incorrect CTI request handling, and, in some cases, preventing T-Server from establishing connection to the PBX. (ER# 256399680)

T-Server no longer sends CTI requests to the switch with the incorrect Invoke ID attribute set to 0xFFFF when it runs out of available Invoke IDs. The maximum value of Invoke ID, which T-Server allocates for an OAI request, has been increased to 65534 (0xFFFE). Previously, the maximum value of Invoke ID was limited to 9999. (ER# 256600818)

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.01. 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 section describes new features that were introduced in this release:

• Log event 01-40005 is triggered by a T-Server operating in backup mode when it attempts to create a consultation call with a non-synchronized CallID attribute.

  01-40005
  Level:	Standard
  Text:	No consult callid provided in BACKUP mode, using non-sync callid ([call-id])
  Attributes:	[call-id] - CallID of the consultation call that could not be synchronized
  Description:	A consultation call CallID is not provided when T-Server, operating in backup mode, uses a non-synchronized CallID attribute.
  Action:	None

  (ER# 255208561)

• The postpone-dn-registration-msec option has been introduced to implement a configurable timer between the last Facility Subscription response and the first SMFR/SSFM request.

  postpone-dn-registration-msec
  Default Value: 0
  Valid Values: 0 - 180000
  Changes Take Effect: Immediately

  Specifies the timeout (in milliseconds) that T-Server waits before initiating DN registration on the switch at link startup. In Fusion (FCCS) configuration, the switch propagates all of the Facility Subscription requests from T-Server to all of the Fusion nodes. T-Server must wait until the subscription propagation in the Fusion network is complete before initiating the DN registration. The recommended option value for Fusion configuration is 90000 milliseconds. If, at link re-start, the Facility Subscription response indicates "Fast restart" ReturnCode = 10, T-Server does not delay DN registration. If this option is set to 0, T-Server does not postpone DN registration.

  (ER# 255115005)

Corrections and Modifications

This release also includes the following corrections and modifications:

T-Server, when configured as a backup server, now correctly handles transfer scenarios to a split ACD (Automated Call Distribution) Queue. Previously, the CallID attribute of the consultation call on the primary and backup T-Servers became desynchronized. As a result, the backup T-Server might have incorrectly associated unrelated calls, which led to incorrect call processing. (ER# 255208561)

T-Server now implements immediate dynamic re-configuration of the TServer options flow-control-rate-startup and flow-control-rate-runtime. Previously, re-configuration of these options took effect only after T-Server was restarted. (ER# 255114987)

Because of the desynchronization of call states and CallID attributes between primary and backup T-Servers, the multiple party cleanup process and subsequent call creation could cause T-Server to stop responding until restarted. (ER# 255014011)

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.001.17. 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.

• Two flow-control configuration options, flow-control-rate-runtime and flow-control-rate-startup, were added to T-Server. The old configuration option flow-control-rate is now disabled.

  flow-control-rate-runtime
  Default Value: 0
  Valid Values: 0-10000
  Changes Take Effect: Immediately

  The configuration option flow-control-rate-runtime sets the maximum number of requests per second that T-Server will send to the switch for processing during the regular runtime after the initialization phase is complete. A value of 0 sets no restriction to this number.

  flow-control-rate-startup
  Default Value: 20
  Valid Values: 0-10000
  Changes Take Effect: After the link is restarted

  The configuration option flow-control-rate-startup sets the maximum number of requests per second that T-Server will send to the switch for processing during the link start-up when DNs are registered. A value of 0 sets no restriction to this number.

• The configuration option enable-dnd-monitor was added to T-Server. This feature provides unsolicited EventDndOn and EventDndOff event notifications when the Extensions attribute's DND (Do-Not-Disturb) status is changed.

  enable-dnd-monitor
  Default Value: false
  Valid Values: true, false
  Changes Take Effect: After the link is restarted

  If the enable-dnd-monitor option is set to true, T-Server requests DND monitoring for digital terminals when a link is restarted by sending a SSFM FID+2(DND) monitoring request to the switch during DN registration. If the DND monitoring request was successful, the PBX sends out a SSFN FID=3 OAI event notification when the DTerm�s DND status is changed. This request is then translated by T-Server into the corresponding EventDNDOn and EventDNDOff events. If the enable-dnd-monitor option is set to false, then DND monitoring is disabled.

Corrections and Modifications

This release also includes the following corrections and modifications:

T-Server now invokes the Route Advanced feature to correctly handle consultation calls when the PBX (Public Branch Exchange) changes to an alternate route trunk group. Previously, these types of calls caused incorrect event reporting by T-Server. (ER# 236406273)

T-Server now correctly processes TSetMuteOn requests sent out from a consultation call destination. Previously, T-Server incorrectly rejected such requests by sending an EventError to the client. (ER# 238135901)

T-Server now correctly processes THoldCall requests invoked from a party in a conference established by TSingleStepConference requests. (ER# 236626906)

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.001.15. 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 T-Server for NEC NEAX/APEX.

• Switch capability support. The new monitor-call-using option specifies which capability T-Server uses for certain clients.

• Configuring external trunks. The configuration procedure for external trunks with a Trunk Route number greater than 255 has changed, and is no longer compatible with the previous method of configuring external trunks less than 255.

• Enhanced Attendant Console support. Certain scenarios are not supported due to switch limitations; these are listed in the Framework 8.0 T-Server for NEC NEAX/APEX Deployment Guide.

Corrections and Modifications

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

T-Server now correctly processes a call-reconnect scenario. Previously, T-Server generated an EventError message after failing to process a THoldCall request because of a timeout. (ER# 213143714)

T-Server now correctly processes the scenario where an agent attempts to re-synchronize the terminal state in a call reconnect scenario. T-Server now sends a request to the switch and immediately reports an EventError message if the terminal state is inconsistent with the request. Previously, T-Server allowed a TRetrieveCall request containing the ForceFunc parameter in AttributeExtensions to expire after a timeout, and as a result, an agent was unable to control his terminal until the timeout expired. (ER# 214402835)

T-Server now conforms to the Genesys Call Model and reports proper event messages when a call is transferred to an ACD Split by a TSingleStepTransfer request. Previously in this scenario, T-Server incorrectly distributed an EventNetworkReached message. (ER# 216574286)

T-Server now validates the held_conn_id and current_conn_id parameters in a TAlternateCall request. If these parameters are incorrect, T-Server immediately returns an EventError message to the T-Server client, preventing the request from timing out. (ER# 217106817)

This release solves a backup T-Server synchronization issue that occurred when T-Server was processing single-step transfer and redirect requests from a consultation call leg. Previously, this issue caused the backup T-Server to become unstable. (ER# 218990265)

T-Server now reports ThisTrunk, OtherTrunk, and ThirdPartyTrunk attributes for an external call when this information is available. Previously, this information was missing in T-Events distributed to T-Server clients. (ER# 219864565)

T-Server now correctly applies the value of the alive-message-timer parameter. Previously, if the alive-message-timer was set to the default value (60 secs), T-Server incorrectly sent heartbeats every five seconds. (ER# 220299926)

Top of Page

Known Issues and Recommendations

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

Switch limitation: The RequestAlternateCall is not supported by T-Server working with an SV8500 switch. (ER# 257517024)

T-Server may improperly clean an internal Call ID table when T-Servers operate in high-availability mode and a primary-to-backup switchover coincides with a switch link failure. (ER# 164945761)

Switch limitation: Because of a limitation of CTI support of the Recall call scenarios on Large-System NEC NEAX/APEX switches, T-Server may incorrectly report the state of a telephony device. (ER# 25873710)

In some configurations of the NEC NEAX SV7000 PABX and CallWorX (an external ACD), there is a known deficiency of ACD behavior during an attempt to route a call to a busy destination from a SPLIT_ROUTE_POINT device via an Infolink IF request. T-Server receives a positive acknowledgement from the ACD, and thus cannot recognize a call routing failure. This behavior affects external call routing to default destinations specified in the extrouter-default-dn or router-default-dn options. (ER# 6372854)

Because of deficient Infolink messaging, T-Server does not support the call-recovery feature on Large-System NEC NEAX/APEX switches where calls distributed from a Split to an agent and not answered within a timeout determined by the switch are re-queued to the Split. In this scenario, the Infolink does not notify T-Server that the call has been re-queued. (ER#  92841)

Service Observing limitations include the following:

• For correct call handling by T-Server, only one Observer may monitor a call at a time.

• T-Server has limited support for conferences with Service Observing. When a call is monitored, a 3-way connection is established (caller, destination, and observer) via a TCT trunk, so a simultaneous conference (that is, an additional participant) is not possible without a multi-way conference card.

• To activate Service Observing via the "ACD Supervisor" feature, the supervisor must be off-hook and must not use the SPEAKER key of a Dterm to monitor an agent.

If you must use an IP address (such as 180.170.9.150) or a full host name including the domain name (such as server.genesyslab.com), expect to receive a warning during the installation of any application on this host. The warning message informs you that the installation cannot find the specified object; as a result, the installation script does not update the configuration data for this application. If you see this warning, continue with the installation.

After completing the installation, update the configuration data for the application you installed on this host, as follows:

1. Open the Properties dialog box for the Application object in Configuration Manager.
2. Enter the correct values for Working Directory, Command Line, and Command Line Arguments on the Start Info tab.
3. Click Apply and OK to save configuration updates.
4. If you are using the run.sh file to start the application, verify that the Working Directory, Command Line, and Command Line Arguments are specified correctly in the run.sh file.

In a T-Server multi-site environment where a call may be routed or transferred several times between different T-Servers, the T-Server where a previous instance of the call is still active may not preserve the Connection ID of the call when it arrives back at this T-Server. The original Connection ID is reported in the FirstTransferConnID attribute and can be used by T-Server, instead of the ConnID attribute when backward compatibility mode is enabled. In addition, the LastTransferConnID attribute contains the Connection ID of the call from the previous location.

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.

The Windows 2000 operating system is no longer supported.

The Solaris 7 operating system is no longer supported.

The HP-UX 11.00 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.

• The Framework 8.0 T-Server for NEC NEAX/APEX Deployment Guide contains detailed reference information for the Genesys Framework 8.0 T-Server for NEC NEAX/APEX, including configuration options and specific functionality.

• The 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 7 Events and Models Reference Manual and contains the T-Library API, information on TEvents, and an extensive collection of call models.

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

Product documentation is also provided on a Documentation Library DVD, which is produced monthly. The New Documents on this DVD page on the DVD indicates the DVD production date. Because the DVD is produced monthly, documentation on the Technical Support website may be more up-to-date than that on the DVD. To verify the latest version of a document, check the version number, located on the second page in PDFs and on the "About This File" topic for Help files.

Top of Page