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.genesys.com for more details.

This release note applies to all 8.1 releases of T-Server for Aspect ACD.

• 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 operating systems available for use with each component release are listed in the table at a high level only. For more detailed information about the supported operating environments, including requirements, supported versions, and any conditions or limitations, see the T-Server Aspect ACD page in the Genesys Supported Operating Environment Reference Guide.
• 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.1.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 T-Servers. Please contact your Customer Care representative if you have any questions.

Supported Operating Systems

New in This Release

This release of T-Server is built with T-Server Common Part (TSCP) release number 8.1.001.74. 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 release contains the following new features or functionality:

• Support for the Red Hat Enterprise Linux 6 and 7 operating systems (added June 15, 2018). See the T-Server Aspect ACD page for more detailed information and a list of all supported operating systems.

• Compliance with FIPS: TLS as implemented by Genesys meets the Federal Information Processing Standards (FIPS). (UKTS-15966)

Corrections and Modifications

This release includes the following corrections and modifications:

This release is built with TSCP 8.1.001.74, which contains the correction of an issue fixed in 8.1.3 Framework libraries. (UKTS-17079)

T-Server now correctly processes calls originating on trunk devices. Previously, T-Server discarded originating events on trunk devices. (UKTS-17097)

T-Server now correctly discards events from the PBX with incomplete or missing mandatory attributes. Previously, T-Server might have failed when it received such an event from the PBX. (UKTS-16943)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with T-Server Common Part (TSCP) release number 8.1.001.71. 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 contains no new features or functionality.

Corrections and Modifications

This release includes the following correction and modification:

T-Server now postpones the distribution of EventLinkConnected events until the PBX sends back the information regarding which version of the link protocol is used. Previously, T-Server distributed EventLinkConnected events immediately upon connection to the PBX, which disallowed the correct registration of devices that corresponded to the CCTs enabled in the Data Interlink Protocol 8, until a response regarding the version of the link protocol was received. (UKTS-16727)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with T-Server Common Part (TSCP) release number 8.1.001.69. 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 contains no new features or functionality.

Corrections and Modifications

This release includes the following correction and modification:

T-Server now correctly performs registration requests for devices of type ACD Queue that correspond to the Call Control Table (CCT) number range of 1000 to 2499, if the Data Interlink Protocol in the PBX is set to a value of 8. Previously, T-Server rejected the registration on devices of type ACD Queue with numbers in range of #81000 to #82499. (UKTS-16692)

T-Server now correctly handles calls on T3/Uniphi Connect IP phones that were connected to the PBX via an external network, regardless of the PBX configuration settings for the voice path. Previously, T-Server did not correctly handle calls on these phones when the connection to the PBX was temporarily disrupted, and might have created artificial calls. (UKTS-16683)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with T-Server Common Part (TSCP) release number 8.1.001.57. 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 contains no new features or functionality.

Corrections and Modifications

This release includes the following correction and modification:

T-Server now correctly deletes old log files according to the value set in the expire option setting. Previously, the internal log file list had a limited amount of entries and when new files were added to a list longer than these limits, some older files were not deleted. (ER# 318306795)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with T-Server Common Part (TSCP) release number 8.1.001.55. 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 contains the following new features or functionality:

• T-Server can now track parallel IP Network InterQueue (NIQ) calls involving the Call Overflow (COF) function by using a tracking node number (TRACKNODE) to request the original call information from the originating node only, thus avoiding the race conditions and obliterating the existing call context data when a call is made via IP NIQ and delivered to several different nodes. Plain NCID matching is replaced by flexible call matching, which allows T-Server to check both the node information and perform directed COF queries instead of propagating COF requests to all connected T-Servers. Previously, T-Server was using only a call tracking number (TRACKNUM) and ignored the node information.

  While T-Server now supports parallel call tracking in IP NIQ scenarios with the COF, Genesys cannot guarantee that other solutions and components will work in IP NIQ scenarios.

  Configuration
  
  

  Aspect PBX: Call Control Tables (CCT) in Aspect ACD have to be programmed, so that the Send Track Data step precedes the NIQ step.

  T-Server: The following configuration changes must be done to correctly support the COF with multiple call center nodes:

  • Only one T-Server (or two in an HA environment) must be connected to a call center node.
  • The extrouter/cof-feature configuration option must be set to true.
  • The extrouter/default-network-call-id-matching configuration option must be set to ts-aspect.
  • If access codes are configured, then the ISCC Call Overflow Parameters value in the Access Codes configuration must have match-flexible=ts-aspect setting.
  • The extrouter/report-local-connid-changes configuration option must not be set to true.
  • The Switch object assigned to T-Server must have the TServer/pbx-node-id option on the Annex tab set to a value that corresponds to the node ID assigned to the Aspect Call Center during installation.

  pbx-node-id
  Default Value: An empty string
  Valid Values: A positive integer
  Changes Take Effect: Immediately
  
  

  Specifies the node ID of the Aspect Call Center assigned during installation of the PBX. The option must be configured in the TServer section on the Annex tab of the Switch object.

  (ER# 313241711, 312879047)

Corrections and Modifications

This release does not include any corrections.

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with T-Server Common Part (TSCP) release number 8.1.001.45. 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 release contains no new features or functionality.

Note: Following the initial Hot Fix release of this version of T-Server on the Solaris and Windows platforms, T-Server 8.1.002.03 was tested on the AIX, HP-UX, Linux, and HP-UX on Itanium platforms. On August 20, 2012, the release type for all platforms changed from Hot Fix to General.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now supports scenarios involving agent logins on Aspect TeleSet 3 (T3) IP phone sets that are configured in the PBX with the Voice Path set only to NailedUp by hiding the calls generated by the PBX during these logins. Previously, T-Server reported these calls instead of hiding them. (ER# 302372624)

T-Server now correctly routes calls using the Connect Call Request (CCR) method of routing from the Call Control Tables (CCT), which are also configured to handle call overflow. Previously, T-Server may have incorrectly attached a TRouteCall request reference to the overflowed call, thus reporting the routed call with the incorrect reference information. (ER# 300994461)

T-Server now correctly handles the following scenario:

1. Two incoming calls are conferenced on a device.
2. One of the calls is released.
3. A consultation call is then initiated.

Previously in this scenario, T-Server sometimes exited.

(ER# 300416859)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with T-Server Common Part (TSCP) release number 8.1.001.40. 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 contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server is built with the TSCP that corrects the following issue of this T-Server:

In multi-site scenarios involving the pullback ISCC transaction type, T-Server now distributes EventCallDeleted and EventAbandoned in the correct order in scenarios where the transaction expires at the origination site due to the call having already ended at the destination location of the transaction. (ER# 297184114, 297178631)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with T-Server Common Part (TSCP) release number 8.1.000.27. 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 contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now correctly generates all attributes for a Make Predictive Call Request (MPCR) message. Previously, T-Server incorrectly encoded the fields (RNA_TIMEOUT, ANSWER_MODE, AMS_DELAY, AMR_MODE, and Originated Line Identity) in the MPCR, because of the incorrect order of fields in the definition file. (ER# 289247831)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with T-Server Common Part (TSCP) release number 8.1.000.26. 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 contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now provides the AttributeThirdPartyDN attribute in the EventDiverted event when it is generated as result of routing a call through the Connect Call Request (CCR) method if the information is provided by the PBX. Previously, T-Server provided only the AttributeThirdPartyDN attribute value in the EventRouteUsed event, and not in the EventDiverted event when routing a call through the CCR method. (ER# 286888991)

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.1.000.26. 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 release does not contain any new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

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

T-Server no longer provides an incorrect access number for an External Routing Point after the following changes have been made in the configuration environment:

1. For an External Routing Point on Switch 1, the Use Override flag is selected and the override number is provided.
2. On Switch 2, an Access Code is configured to access Switch 1, or a new Access Code to another Switch is added.

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.1.000.25. 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 release does not contain any new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now correctly generates EventDTMFSent. Previously, T-Server did not add call-related attributes, such as AttributeConnID, to the event. (ER# 281433985)

T-Server no longer shuts down if it fails to obtain an ISCC license. (ER# 278678036)

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.1.000.19. 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.1 release of T-Server for Aspect ACD.

• T-Server no longer connects to applications that have disabled status in the configuration environment.
• The default value of the background-processing configuration option has been changed to true.
• T-Server now supports the Unresponsive Process Detection feature. The following configuration options enable this feature:

  • heartbeat-period
  • hangup-restart

  See option descriptions in your T-Server Deployment Guide. For more information, refer to the Framework 8.0 Management Layer User’s Guide.
• T-Server now supports IPv6. For more information, refer to the Framework 8.1 Deployment Guide.
• T-Server now supports vSphere 4 Hypervisor.
• T-Server now supports Acresso FLEXNet Publisher 11.9 license manager.
• T-Server is now supported on the following platforms:

  • AIX 7.1 64-bit
  • HP-UX Itanium (version 11i v3)
  • Red Hat Enterprise Linux 5 64-bit

Corrections and Modifications

This release includes the following modification that was made between Release 8.0 or earlier releases and the initial 8.1 release:

The option kpl-loss-rate has been removed from T-Server. (ER# 274609665)

Top of Page

Known Issues and Recommendations

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

Switch-specific behavior: T-Server can only provide correct reporting for Aspect T3 IP phone sets that are configured in the PBX with the Voice Path set to NailedUp. Any other Voice Path setting in the PBX is not supported and will result in inconsistent T-Server reporting for these phone sets. (ER# 303349629)

When agents log in to an Aspect T3 IP phone, the PBX generates a call that is reported as part of the login procedure and is immediately cleared after the login is completed. This means that T-Server generates call-related events in addition to the login-related events and agent desktops may briefly see call-related activity as part of the login procedure on such phone sets. (ER# 301135031)

T-Server shuts down if it fails to obtain an ISCC license. (ER# 278678036)

After T-Server has started and logging has been configured, T-Server might exhibit a failure if there is no disk space available for a prolonged period of time. (ER# 276845171)

Starting with 8.0.1, T-Server for Aspect ACD works only with Contact Server. Direct connection to Application Bridge is no longer possible. Contact Genesys Customer Care for further information.

Due to hardware limitations, a Place Call Request to #8CCT fails when using 4 digit CCTs. All transfer CCTs must be in the in the 1-999 range. (ER# 261242111)

An ISCC call transfer between T-Servers that are connected to two different PBXs with different CTI link versions result in Trunk Thromboning. Aspect T-Servers report more than one EventPartyChanged for the same DN when the transfer is completed. This scenario will only work correctly if three T-Servers are involved. (ER# 262261255)

The Inter Server Call Control/Call Overflow (ISCC/COF) feature is not supported if the ISCC Call OverFlow Parameter property is set to match-ani. (ER# 263487783)

Switch-specific behavior: If the configuration option route-call-method equals CIMR-and-redir, an outbound call cannot be diverted when transferred on to a Routing Point. (ER# 262361381)

If the configuration option route-call-method, set in the TServer section, equals CIMR-and-redir, then the RCCR method of routing is not used for an internal or a consultation call to a Routing Point. (ER# 261997871)

T-Server does not correctly support a connection to the Aspect PBX where the Data Interlink protocol is set to 7. (ER# 261069019)

Switch-specific behavior: If the configuration option releasing-party-report, set in the TServer section, equals true, T-Server will report the ReleasingParty information based on the information provided by the PBX. Also, if the PBX reporting is inconsistent, the T-Server reporting of the ReleasingParty information will sometimes also be inconsistent. (ER# 260678041)

When an unmonitored DN is used to make a call, the PBX releases the call. To avoid this, use the Agent ID logged on to that DN to make a call, instead of the DN number. (ER# 227117446)

Initiating transfer of a conference call is not supported. (ER# 226425215)

In the following scenario, a TAgentSetNotReady generates two EventAgentNotReady. One has a correct REASON, but the other one is wrong.

• The option walk-away-bck-compat is set to true.
• When a request AgentNotReady is sent with extension REASON=1.
• T-Server reports two EventAgentNotReady (this is due to switch behavior).
• One EventAgentNotReady has REASON = 1000.
• The other EventAgentNotReady has REASON=1.

(ER# 228874763)

In the following scenario, when upgrading 7.0 primary (T-Server1) and backup (T-Server2) T-Servers to 8.0, T-Server2 does not synchronize with T-Server1:

• T-Server2 is stopped and upgraded to 8.0.
• 8.0 T-Server2 has option ha-sync-dly-link-conn set to true.
• No calls are on T-Server1.
• T-Server2 is started.

(ER# 229884491)

In the following scenario, the ReleasingParty has an incorrect value when the External DN releases the call:

1. The releasing-party-report option is set to true.
2. DN1 CallEstablish with external DN.
3. DN1 InitiateConference with internal DN3.
4. DN3 answers and a conference is established.
5. DN1 completes conference.
6. DN1 releases the call. In EventReleased, the Attribute Extension ReleasingParty is 1 Local. This is correct.
7. Now the external DN releases the call.
8. But for DN3, in EventReleased, the Attribute Extension ReleasingPart is 1 Local, which is incorrect.

(ER# 234508947)

Aspect Call Center responds to DN Status request message ESR with ESRR status value X = Busy/Other after a physical trunk disconnect. As ESRR status value X is also used for other unavailable states, such as dialing or releasing, T-Server will not generate EventDNOutOfService to clients. (ER# 16897903)

In the following scenario, retrieval of the call via CTI is not possible. It must be retrieved manually.

1. Internal call is Established.
2. Place the call on Hold.
3. Start T-Server.
4. When checking QueryAddress results, the Held device is reported as 0 (idle).

As a workaround, T-Server clients can use Private Service 'Free the line 0 and/or 1'.

(ER# 95703, ER# 95070)

When a manual consult call is made to an invalid internal device, T-Server distributes EventHeld, then EventDialing, but no other event is generated to indicate call failure, because the switch reports abandoned. (ER# 100889, ER# 100890).

In the following scenario, T-Server does not show any call information, but displays the agent as Not Ready:

1. Agent logged in and Ready.
2. Either establish a call or press one of the line buttons.
3. Start T-Server.

(ER# 101005, ER# 101010)

When the Event Party Propagation (EPP) feature is activated and single-step transfer is used, Aspect T-Server does not distribute EventPartyChanged on a remote location. (ER# 91309, ER# 91778)

At startup, T-Server recognizes when trunk lines are unavailable. However, as no status change message is provided by the switch, T-Server cannot correctly reflect trunk synchronization. (ER# 97402, ER# 16897317)

The ISCC feature with cast type direct-ani is supported but limited. The supported scenarios are:

• Inbound, outbound call then single-step transfer to a remote location
• Inbound call routed to a remote location

No other scenario is supported. (ER# 60848)

In release 9.1.1 and higher of the Aspect ACD, the default configuration parameters for consult calls have been changed. Previously, the default maintenance flag #9 was set to on (checked). From release 9.1.1 the default setting of maintenance flag #9 is off (unchecked).

With the 9.1.1+ default setting (off) it may be necessary to press a phoneset key at the end of a consult call in order to come out of permanent ACW, or before being able to continue.

Please note that this parameter can normally be changed only by Aspect Engineering personnel. (ER# 128670380)

Alerting calls cannot be released in the Aspect switch. (ER# 35449788)

On Aspect 9.x ACD, when one analog phone calls another, the switch does not report anything except CDEM when the phones are placed on hook. (ER# 33227139)

On Aspect 9.x ACD, TAgentNotReady when an agent is already in NotReady state places the agent into Ready state. (ER# 31945167)

Outbound calls from analog devices to invalid numbers might be reported as busy by the switch. (ER# 92766, ER# 92765)

Calls via CTI from analog sets cannot be answered via CTI. (ER# 60770)

CTI monitoring and control of analog extensions is limited with the Aspect switch.

• No COEM (Call Offered Event Message) is distributed by the switch when an inbound call is made to an analog extension. Hence, T-Server only distributes EventRinging once the call is established.
• No CDEM (Call Disconnect Event Message) is distributed by the switch when an inbound call is established to an analog extension then released. Hence, T-Server does not distribute EventReleased when call is released from the originator (However, a workaround has been implemented if the call is released by CTI from the analog set.)
• A CTI call from an analog extension cannot be answered by CTI.

(ER# 60764, ER# 88368)

In two-step transfer scenarios, the switch does not allow blind transfer. As a result, the consultation call has to be answered before the transfer can be completed. (ER# 78197, ER# 78271)

The switch can only single-step transfer a call if at least one of the parties in the main call is a trunk party (for example, inbound call or outbound call followed by single-step transfer to an agent). (ER# 78198, ER# 78272)

Blind transfer, mute transfer, redirect, divert, forwarding and internal single-step transfer are not supported. Consultation calls to Routing Point (Inbound/Outbound only), and single-step transfer (Inbound/Outbound only) have limited support. (ER# 25000141)

DTMF cannot be sent from a conference controller. (ER# 107848526)

Four-party conference is not supported. (ER# 107848335)

Parties can only be deleted from conference with DN Number, not with Agent Login ID. (ER# 104162626)

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. For more information on discontinued support for operating environments and databases, see Discontinued Support in the Genesys Supported Operating Environment Reference Guide.

The Red Hat Enterprise Linux 3.0 operating system is no longer supported.

The Solaris 8 operating system is no longer supported.

The Tru64 UNIX operating system is no longer supported.

The AIX 5.1 and 5.2 operating systems are 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 Genesys Customer Care website. The following documentation also contains information about this software.

• The Framework 8.1 T-Server for Aspect ACD Deployment Guide provides detailed reference information for the Genesys Framework T-Server for the Aspect ACD switch including configuration options, known limitations, and switch functionality.
  

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

• The Platform SDK 8.x .NET (or Java) API Reference and the Genesys Events and Models Reference Manual contain 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 Customer Care for additional information.

• The Genesys Licensing Guide contains information about the licensing requirements for this software. Please refer to the applicable portion of this guide or contact Genesys Customer Care for additional information.

Product documentation is provided on the Customer Care website, the Genesys Documentation website, and the Documentation Library DVD.

Note: For the DVD, the New Documents on this DVD page indicates the production date for that disc. Due to disc production schedules, documentation on the Genesys Documentation 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