Release Number | AIX | HP-UX PA | HP-UX IPF | Linux | Solaris | Windows |
---|---|---|---|---|---|---|
8.1.001.07 [02/15/23] – Hot Fix | X | X | ||||
8.1.000.21 [10/03/18] – Hot Fix | X | |||||
8.1.000.20 [04/12/18] – General | X | X | X | X | ||
8.1.000.19 [05/26/17] – Hot Fix | X | |||||
8.1.000.18 [02/24/17] – Hot Fix | X | X | ||||
8.1.000.17 [08/19/16] – Hot Fix | X | |||||
8.1.000.15 [06/21/16] – Hot Fix | X | |||||
8.1.000.14 [03/28/16] – Hot Fix | X | X | ||||
8.1.000.13 [06/05/15] – Hot Fix | X | |||||
8.1.000.10 [12/06/13] – Hot Fix | X | X | X | |||
8.1.000.09 [11/07/13] – Hot Fix | X | X | ||||
8.1.000.08 [06/18/12] – General | X | X | X | X | X | X |
8.1.000.06 [03/26/12] – General | X | X | X | X | X | X |
8.1.000.02 [09/07/11] – Hot Fix | X | |||||
8.1.000.01 [06/15/11] – General | X | X | X | X | X | X |
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 Network T-Server for GenSpec.
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
Corrections and Modifications
This release of T-Server is built with T-Server Common Part (TSCP) release number 8.1.010.77.
This version was first released as a Hot Fix on 03/28/2022.
There are no restrictions for this release. This release contains the following new features or functionality:
T-Server now supports a new configuration option transaction-state
, in the extrouter
section.
transaction-state
Default Value: default
Valid Values: default, by-islink
Changes Take Effect: On the next ISCC origination transaction
This option enables improved historical reporting of data for multisite scenarios where a call is successfully delivered to the destination site but is not answered by the target agent.
The default
value supports backward compatibility when T-Server reports the origination transaction and the IS-Link as unsuccessful, and stops event propagation (if configured). As a result, in most cases, historical reporting applications do not take into account the calls on different sites that are part of the same interaction.
The by-islink
value forces T-Server to report both the transaction and the IS-Link as successful and to maintain event propagation in those multisite scenarios.
The value of this option must be consistent between all T-Servers participating in multisite transactions.
Limitation: If No-Answer Supervision is used, the agent-no-answer timeout must not exceed the value of the timeout
option in the extrouter
section (the default value of this option is 60
seconds).
(TS-10606)
This release includes no corrections or modifications.
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
This release of Network T-Server is built using TSCP release number 8.1.001.71. 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 release contains the following new features or functionality:
This release includes no corrections or modifications.
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
This release of Network T-Server is built using TSCP release number 8.1.001.71. Consult the TSCP release note for information on changes that may affect the functionality of your particular type of Network T-Server.
This version was first released as a Hot Fix on 12/20/2017.
There are no restrictions for this release. This release contains the following new features or functionality:
This release includes the following corrections and modifications:
After a RequestApplyTreatment event, T-Server now distributes TreatmentEnd for the previous request and then a TreatmentApplied for the current request. Previously, T-Server failed to report EventTreatmentApplied for a second treatment requested while another treatment was in progress. (NETTS-1545)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
This release of Network T-Server is built using TSCP release number 8.1.001.71. 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 release does not contain any new features or functionality.
This release includes the following corrections and modifications:
T-Server no longer quits unexpectedly on receiving a routeRequest message with an empty calledNumber. Such requests are now rejected and generate a MissingDialedNumber error. (NETTS-1539)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
This release of Network T-Server is built using TSCP release number 8.1.001.71. 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 release does not contain any new features or functionality.
This release includes the following corrections and modifications:
T-Server now supports both integer and string values in the CAUSE
extension in reroute messages. Previously, string values were unsupported. (NETTS-1395)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
This release of Network T-Server is built using TSCP release number 8.1.001.71. 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 release does not contain any new features or functionality.
This release includes the following corrections and modifications:
When a treatment request results in the cancellation of an earlier treatment, T-Server now correctly generates EventTreatmentEnd for the earlier treatment, enabling URS to continue with subsequent treatments or routing correctly. Previously, EventTreatmentEnd was not generated for the canceled treatment. (NETTS-1526)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
This release of Network T-Server is built using TSCP release number 8.1.001.71. 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 release does not contain any new features or functionality.
This release includes the following corrections and modifications:
T-Server now correctly encodes the asterisk (*) character in its responses to the SCP. (NETTS-1525)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
This version of T-Server added support for Windows in June, 2016.
This release of Network T-Server is built using TSCP release number 8.1.001.71. 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 release does not contain any new features or functionality.
This release includes the following corrections and modifications:
When sending EventTreatmentEnd events, T-Server now always includes extensions received in the treatment response from SCP. (NETTS-1515)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
This release of Network T-Server is built using TSCP release number 8.1.001.71. 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 release does not contain any new features or functionality.
This release includes the following corrections and modifications:
When ISCC routing occurs with the type route
, T-Server adds the extensions received from the SCP
to the AttributeExtensions of EventRouteRequest generated on the destination route point. (NETTS-1507)
During PSTN routing, T-Server now sends the SCP a response with the correct route type (direct
). (NETTS-1506)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents, above.
This hot fix supports the Solaris operating system as of October 15, 2014.
This release of Network T-Server is built using TSCP release number 8.1.001.68. 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 release does not contain any new features or functionality.
This release includes the following corrections and modifications:
T-Server now correctly deletes old log files according to the value set in the expire
option setting. Previously, when the number of files to be deleted exceeded that internal limit, some older files were not deleted. (NETTS-1485, TS-769)
T-Server now correctly handles NetworkReconnect
requests when a treatment is applied during Universal Routing Server (URS) controlled Network Consultations. Previously, T-Server did not transmit the reconnection requests to the switch if a treatment was active when T-Server received the request. (NETTS-1419)
Supported Operating Systems
New in This Release
Corrections and Modifications
This release of Network T-Server is built using TSCP release number 8.1.001.42. 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 release does not contain any new features or functionality.
This release includes the following corrections and modifications:
Network T-Server now stops the network-response-timeout
timer after the switch responds to a routing attempt with an error. Previously in this scenario, the call sometimes was abandoned because of this timeout while T-Server awaited routing instructions from the Universal Routing Server (URS). (NETTS-1481)
Supported Operating Systems
New in This Release
Corrections and Modifications
This release of Network T-Server is built using TSCP release number 8.1.001.42. 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 release does not contain any new features or functionality.
This release includes the following corrections and modifications:
Network T-Server now correctly responds to all keep-alive requests. Previously, Network T-Server did not respond to keep-alive requests with odd-numbered packets. (ER# 277323596)
Supported Operating Systems
New in This Release
Corrections and Modifications
This release of Network T-Server is built using TSCP release number 8.1.001.36. 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 release contains the following new features:
Network T-Server is now supported on the following platforms:
New options enable the specification of minimum and maximum DTID values:
tid-min-value
tid-max-value
Limited display of sensitive information: In logs, new options enable sensitive data in logs to be marked for post-processing by the user, such as deletion, replacement, or hiding. See the Genesys 8.1 Security Deployment Guide for details.
Compliance with FIPS: TLS as implemented by Genesys meets the Federal Information Processing Standards (FIPS).
This release includes the following correction:
Network T-Server for GenSpec now populates the application
field of the invokeApp
request to the SCP as follows:
RequestApplyTreatment
for an extension key-value pair with key APP_ID
. If that key-value pair is absent, it returns EventError
. Otherwise, it uses the value of this extension to complete Step 2.
RequestApplyTreatment
for an extension whose key equals the value obtained in Step 1. If such a key-value pair exists, the server uses it to populate the application
field. Otherwise, it uses the value obtained in Step 1 to populate the application
field.
This behavior ensures backward compatibility with all earlier versions of the Network T-Server for GenSpec. (ER# 293135319)
Supported Operating Systems
New in This Release
Corrections and Modifications
This release of Network T-Server is built using TSCP release number 8.1.000.12. 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 release does not contain any new features or functionality.
This release includes the following corrections and modifications:
Network T-Server now correctly sets OperationCode
to a value of 2
within the TCAP invoke portion of FlowControl
messages. Previously, OperationCode
was incorrectly set to a value of 1
. (ER# 279843940)
Supported Operating Systems
New in This Release
Corrections and Modifications
This release of Network T-Server is built using TSCP release number 8.1.000.12. 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 8.1 release of Network T-Server for GenSpec.
Network T-Server is now supported on the following platforms:
background-processing
configuration option has been changed to true.
heartbeat-period
hangup-restart
This section provides the latest information on known issues and recommendations associated with this product.
Deleting a connection from another T-Server or a SIP Server to GenSpec Network T-Server could cause ISCC to fail under the following conditions:
To restore ISCC, you must either:
(TS-11687)
Found In: 8.1.x | Fixed In: |
In release 7.6, the Commonlib option common\rebind-delay
affects the operation of Network T-Servers that use the gli-reconnect-delay option
to control server socket. The common\rebind-delay
option overrides the gli-reconnect-delay
option and ignores settings for this option.
Genesys recommends the following:
log\x-conn-debug-open
to 1
.common\rebind-delay
to 0
(zero).Note: Disabling this option may cause problems in cases of multiport usage. Network T-Server will exit if at least one port has not been opened (due to misconfiguration, or a quick restart).
Found In: 7.6.000.07 | Fixed In: |
The Network Attended Transfer and Conference (NAT/C) feature supports a maximum of three parties on a call. After an initial TNetworkConsult
request has been made and a third call participant is present, subsequent TNetworkConsult
requests will result in EventError
messages. After the number of call participants drops back to two parties (due to transfer or disconnection of one party from the conference), subsequent TNetworkConsult
requests are again valid. (ER# 77020182)
Found In: 7.2.002.00 | Fixed In: |
Network T-Servers do not support warm or hot standby. Instead, they use a load sharing redundancy schema. See the Framework 8.1 Network T-Server Deployment Guide for your T-Server for more information.
Found In: 7.0.000.06 | Fixed In: |
Running the Network T-Server for GenSpec on the Solaris operating system requires the installation of certain patches to the C++ runtime libraries. Install the specific patches for the C++ runtime as shown below:
Found In: 6.5.100.03 | Fixed In: |
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.
Red Hat Enterprise Linux 4.0 is no longer supported.
Discontinued As Of: 8.1.000.20 |
Windows 2003 is no longer supported.
Discontinued As Of: 8.1.000.20 |
Solaris 9 is no longer supported.
Discontinued As Of: 8.1.000.20 |
AIX 5.3 is no longer supported.
Discontinued As Of: 8.1.000.20 |
Red Hat Enterprise Linux 3.0 is no longer supported.
Discontinued As Of: 8.1.000.01 |
Solaris 8 is no longer supported.
Discontinued As Of: 8.1.000.01 |
Tru64 UNIX is no longer supported.
Discontinued As Of: 8.1.000.01 |
Information in this section is included for international customers.
There are no known internationalization issues for this product.
Additional information on Genesys Telecommunications Laboratories, Inc. is available on our Customer Care website. The following documentation also contains information about this software.
The Framework 8.1 Network T-Server for GenSpec Deployment Guide contains detailed reference information for the Genesys Framework 8.1 Network T-Server for GenSpec, including configuration options and specific functionality.
The Framework 8.1 Deployment Guide helps you configure, install, start, and stop Framework components.
The Genesys Events and Models Reference Manual contains an extensive collection of events and call models describing core interaction processing in Genesys environments.
The Platform SDK 8.x .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 Customer Care for additional information.
The Genesys Supported Operating Environment Reference Guide contains information about supported operating systems and databases.
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.