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 details.
This release note applies to all 8.1 releases of T-Server for Alcatel A4400/OXE.
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 More Release Information/Legal Notices for 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.5.000.28. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information about 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 Windows Server 2022. See the Supported Operating Environment: T-Server Alcatel A4400/OXE page for more detailed information and a list of all supported operating systems. (UKTS-18016)
This release includes no corrections.
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.5.000.28. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information about 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 8 operating system. See the Supported Operating Environment: T-Server Alcatel A4400/OXE page for more detailed information and a list of all supported operating systems. (UKTS-17872)
Starting with this release, T-Server requires FlexNet Publisher License Manager version 11.16.5 or later for Windows and Linux platforms. (UKTS-17872)
This release includes no corrections.
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.001.79. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information about 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 Windows Server 2019 operating system and Windows 2019 Hyper-V virtualization (added December 2020). See the Supported Operating Environment: T-Server Alcatel A4400/OXE page for more detailed information and a list of all supported operating systems.
This release includes the following corrections and modifications:
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.001.79. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information about 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.
This release includes the following corrections and modifications:
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.001.79. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information about 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:
A new configuration option, override-call-type, specifies a call type for internal calls that land on a routing point and have not been yet assigned a call type. This option specifically addresses the need to assign a call type of outbound to calls initiated during predictive campaigns, but also enables the assignment of inbound and internal call types.
override-call-type
Setting: DN object, Annex tab, [TServer] section
Default: default
Valid values:
Sets the call type of internal calls arriving at the specified routing point or routing queue object.
(UKTS-17704)
This release includes the following corrections and modifications:
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.001.79. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information about 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.
This release includes the following corrections and modifications:
T-Server can now tolerate no response to a connection attempt within a configurable time. Previously, such tolerance was inflexible and set to 2000 milliseconds. A new option allows control over the interval.
link-start-tout
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.001.79. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information about 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:
This release includes the following corrections and modifications:
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.001.74. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information about 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:
You can now set the headset-mode option at the agent level. Previously, you could set the option only globally, for all agents.
Enables or disables headset mode at the agent level. Set the configuration option in the section [TServer] under Agent Login:
headset-modetrue/falsefalse, T-Server disables headset mode for an agent. true, T-Server enables headset mode for an agent.At the agent level, the option value overrides the value set globally. However, you can still override the agent value by Extension in a RequestAgentLogin request.
(UKTS-17555)
This release includes the following corrections and modifications:
Request incompatible with object. Previously, query requests for such devices might have resulted in no response from T-Server. (UKTS-17552)
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.001.74. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information about changes to the Common Part that may affect the functionality of your particular type of T-Server.
This version was first released as a Hot Fix on 07/26/16. This release contains no new features or functionality.
This release includes the following corrections and modifications:
T-Server now correctly performs transitions on agents from NotReady to NotReady/AfterCallWork and to NotReady if the Not Ready Activation feature is enabled and if different codes are used in the request to change the agent to NotReady. Previously, on transition to the NotReady/AfterCallWork state, T-Server did not indicate that an agent had the Not Ready Activation code set and failed a request to change the agent state from NotReady/AfterCallWork to NotReady with a different Not Ready Activation code. (UKTS-17454)
T-Server now properly reports an agent state event in scenarios where a call from an agent device is made immediately after the agent is logged in and T-Server has smart monitoring mode activated. Previously, T-Server might have reported only EventAgentLogin before EventDialing if the PBX did not provide an agent state event. (UKTS-17450)
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.001.74. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information about 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:
This release includes the following corrections and modifications:
T-Server now correctly handles the following scenario:
T-Server now correctly handles reconnection of the consultation call that is made to an emulated routing point and routed with supervision. Previously, T-Server sometimes failed if the consultation call was reconnected too quickly after execution of routing. (UKTS-17417)
T-Server now correctly resolves a state of a real agent in scenarios where a link to the PBX disconnects. Previously, T-Server incorrectly updated the state of the agent who had logged out while T-Server was disconnected from the PBX. (UKTS-17413)
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.001.74. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information about 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:
T-Server can now provide reporting that is compatible with Interaction Concentrator (ICON) requirements. Previously, when a call passed a non-monitored device or a device
that was not defined in Configuration Database, T-Server reported EventQueued/EventRinging with CallStateRedirected,
which affected ICON and InfoMart reporting.
New configuration option in the section [TServer]:
icon-compat-reporttrue/falsefalsefalse, T-Server provides
reporting based on reporting from the PBX (backward-compatible reporting). true, T-Server provides reporting compatible with ICON.(UKTS-17314)
This release includes the following corrections and modifications:
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.001.74. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information about 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.
This release includes the following corrections and modifications:
T-Server now correctly handles overflows from busy ACD pilots to Hunting Groups that are used as emulated supervised routing points. Previously, T-Server might have incorrectly handled such a scenario when:
active state resulted in no events.
(UKTS-17292)
T-Server now correctly ignores synchronization messages from the primary T-Server while in backup mode, if connection to the PBX has not yet
been re-established after a link outage. Previously, T-Server might have improperly handled synchronization requests while the link to the PBX
was disconnected, and thus might have failed to enter a proper service state, leading to generation of EventLinkConnected.
(UKTS-17266)
T-Server now correctly generates reporting for scenarios where a Hunting Group with members configured in the PBX as physical station devices receives a consult
call, distributes the call to one of the members and completes a conference. Previously, T-Server might have incorrectly omitted reporting of
EventPartyAdded when:
(UKTS-17273)
T-Server can now report correlator data in events using a string value when the new configuration option correlator-as-string is
set to value true. Previously, T-Server attached a key with binary value if the first character of the correlator was non-printable.
New configuration option in T-Server:
correlator-as-string
true/false
false
AttributeExtensions.
(UKTS-17272)
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.001.74. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information about 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 Windows Server 2012.
This release includes the following corrections and modifications:
T-Server now properly handles rejection of registration on agent devices that are not defined in Configuration Database, if T-Server is running in agent substitution mode and if the monitoring of agent devices (option agent-smart-monitor) is set to strict. Previously, T-Server might have quit when it:
(UKTS-17257)
T-Server now postpones a RequestHoldCall if the time between the call being established and request execution is greater than the value set in the option min-xfer-init-dly. Previously, a PBX might have rejected such a request if the request was submitted too quickly. (UKTS-17254)
After a RequestAgentNotReady with LegalGuard mode is requested for a real agent, T-Server now generates an EventAgentNotReady with work mode Unknown. Previously, if a T-Server client requested a transition, T-Server suppressed generation of events during transitions between AfterCallWork and LegalGuard. (UKTS-17253)
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.001.74. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information about 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 new features or functionality.
This release includes the following corrections and modifications:
When an agent is logged in with a password, T-Server now correctly handles the NAS logout action. Previously, T-Server might have entered an endless loop when the password was unknown. (UKTS-17252)
T-Server now logs out an agent with the PBX if the agent logged in using a password. In version 8.1.004.09, T-Server could not do so. (UKTS-17247)
In conference scenarios, T-Server no longer fails when the PBX generates incorrect events. Previously, some PBX versions might have produced reporting that could lead to T-Server failure. (UKTS-17165)
T-Server no longer fails when the PBX generates events in incorrect order and with incorrect content. (UKTS-17148)
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.001.74. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information about 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 new features or functionality.
This release includes the following corrections and modifications:
T-Server now consistently handles calls and registrations on devices where substitution is activated. Previously, due to inconsistent handling of registration and unregistration on devices involved in substitution, T-Server might have:
If you are running T-Server in High Availability mode, then both the primary and backup T-Servers must use this release.
T-Server now correctly handles release of a supervisor from a monitoring conference when neither supervisor nor proACD device are in Configuration Server. Previously, T-Server might have failed after the supervisor left the conference, logged out, and then logged in on another proACD device. (UKTS-17119)
T-Server again supports the option legal-guard-acw.
Previously, the option was available in T-Server 7.6 and disabled in T-Server 8.0.
legal-guard-acw
Valid values: true, false
Default: false
Specifies whether CCD pause time is reported as part of the AfterCallWork phase:
true, instructs T-Server to ignore a transition on agents from NotReady/AfterCallWork to NotReady/LegalGuard,
so T-Server reports a separate CCD pause time as part of the AfterCallWork phasefalse, instructs T-Server to report AfterCallWork and LegalGuard phases separately(UKTS-17114)
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 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 about 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.
This release includes the following corrections and modifications:
T-Server now correctly reports a scenario where calls are transferred to a non-supervised RSI and PBX incorrectly reports a change to the Global Call ID in the event on the RSI. Previously, T-Server might have become unstable in such a scenario. (UKTS-17074)
After the loss of a link to the PBX, T-Server no longer immediately generates an EventAgentLogout for real agents, and reports the correct agent state after the connection to the PBX is restored. Previously, T-Server immediately generated an EventAgentLogout and reported the state only after the link was restored. (UKTS-17063)
T-Server now correctly processes a PBX event that is queued on start-up. Previously, T-Server could become unstable in scenarios where a call was queued on a call processing group and connection to the PBX was disconnected and reconnected. (UKTS-17027)
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 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 about 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.
This release includes the following corrections and modifications:
T-Server now correctly handles the Agent Smart Monitor feature during the login of a real agent when substitution mode is enabled. Previously, T-Server sometimes incorrectly updated the internal state of a substituted device while unregistering with the PBX, which sometimes resulted in T-Server blocking event generation on this device when a real agent logged in and a new client registered on the device. (UKTS-16851)
T-Server now correctly handles execution of TAgentSetNotReady with mode AfterCallWork
for real agents when an agent device is in idle state. Previously, T-Server passed
such a request to the PBX for execution only if both of the following conditions were
met:
WrapUpTime was not present in the request.
wrap-up-time option was not configured at the Application level or in the annex
of an agent or DN.(UKTS-16856)
T-Server no longer forces processing of a pending logout until the login-logout timeout expires. Previously, T-Server might have left an agent in a state that was inconsistent with the agent state in the PBX, when the PBX reported a logout notification for the agent and immediately after an agent state changed event. (UKTS-16857)
T-Server now correctly handles synchronization of real agents after a link disconnect in an HA environment. Previously, T-Server sometimes incorrectly updated the state of real agents after a link reconnect, which left the real agents in a state that was inconsistent with their state in the PBX. (UKTS-16932)
T-Server now correctly handles scenarios in which consultation calls are camped
on a busy device. Previously, T-Server sometimes terminated unexpectedly if the
PBX did not provide information regarding other parties of the camped-on call in
the Delivered or Queued events. (UKTS-16950)
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.001.71. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information about 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.
This release includes the following corrections and modifications:
T-Server now correctly handles a business call type change in scenarios where a transfer of an Inter Service Call Control (ISCC) transaction occurs when No-Answer-Supervision (NAS) is configured and the value of the propagated-call-type option is set to true. Previously, T-Server might have disconnected such a transferred call or transferred this call to a NAS destination, if the call was established before the completion of the transfer and the resulting call was of a business call type. (UKTS-16746)
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.001.70. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information about 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.
This release includes the following corrections and modifications:
T-Server now adds specific private data into requests sent to the PBX when executing TQueryAddress requests (type equals EventAddressInfoType) for ACD Pilot devices. T-Server only adds this data if the value of the prioritary-transfer configuration option is set to true, or the GCTI_PRIORITARY_TRANSFER Extensions attribute with a value of either true, on, or 1 is provided in the request.
Previously, T-Server always added the private data to the Query Device request for ACD Pilot devices sent to the PBX. (UKTS-16640)
T-Server now correctly reports scenarios involving the handling of agent devices logins and reports EventDNOutOfService events in scenarios where:
agent-substitute option is set to true.agent-smart-monitor option is set to strict.
When an agent device is added to the configuration environment, T-Server generates an EventAgentLogin event, followed by the relevant state of the agent device.
Previously, T-Server generated an EventAgentLogin event with a relevant agent state, followed by an additional EventAgentLogin event, an EventQueueLogout event, and a relevant agent state after the agent device was added to the configuration environment. (UKTS-16689)
T-Server now correctly handles the transfer of calls to a Routing Service Interface (RSI) device in the following scenario:
EventPartyChanged event on RSI devices.
Previously, T-Server ignored such transfers and did not generate any reporting events. (UKTS-16383)
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.001.68. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information about 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.
This release includes the following corrections and modifications:
T-Server now correctly handles the following scenario:
retain-call-tout configuration option.
Previously in this scenario, T-Server, while connected to the first node, incorrectly handled the last step, a Redirect on No Answer (RONA) by the PBX, and left a stuck call in the alerting state. (UKTS-16652)
T-Server now correctly reports scenarios involving single-step conference calls initiated from an unmonitored DN, if the PBX reports this event as the first event for a call (only the supervisor device is monitored). Previously, T-Server ignored such scenarios and did not report any events on a supervisor device. (UKTS-16627)
T-Server now correctly performs the registration of Routing Services Interface (RSI) devices. Previously (in version 8.1.003.05 only), T-Server unregistered the RSI devices after the first successful registration to the PBX and then re-registered the device after the expiration of the timeout interval, as defined by the reg-delay option. (UKTS-16620)
T-Server now correctly performs an agent action in the following scenario:
Previously, if this switchover occurred when NAS was in progress, the new primary T-Server did not apply the agent action after the NAS redirect was completed. (UKTS-16617)
T-Server now correctly handles user data updates when events from the PBX have correlator data. Previously, T-Server created a data object that was used for updating this user data, but it was not freed for reuse after the user data was updated. (UKTS-16602)
T-Server now correctly handles connections to a PBX with two CPU boards. Previously, T-Server might have experienced problems connecting to this type of PBX due to a potential issue when incorrectly executing an initial handshake. (UKTS-16437)
T-Server now correctly reports the ANI attribute, if the calling party cannot be identified. Previously, in this scenario, T-Server might have reported a value starting with T in the ANI attribute. (UKTS-16434)
T-Server now requests information from the PBX prior to generating responses when a client executes a TQueryAddress request of type AddressInfoType for Automated Call Distribution (ACD) and RSI devices. Previously, the T-Server 8.x releases generated a response without first retrieving the information from the PBX.
Note: This functionality was not available in the T-Server 8.x releases, but was available for the T-Server 7.x releases. (UKTS-16389)
T-Server now correctly sends a TUpdateUserData request with the updated account code data when a business call is released. Previously, T-Server incorrectly sent this request, with the account code data and the correlator data, if they were both present in the User Data attribute, to the PBX. This request was then rejected by the PBX. (UKTS-16366)
T-Server now correctly reports scenarios where a call is abandoned on a RSI Routing Point, if there is a TRouteCall request in progress. Previously, T-Server reported an EventRouteUsed event, followed by EventError and EventAbandoned events, instead of only the EventError and EventAbandoned events. (UKTS-16364)
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.001.60. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information about 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.
This release includes the following corrections and modifications:
T-Server now correctly reports the values in the AttributeExtensions and AttributeReason attributes of agent-related events when a real agent has set a NotReady reason code on the phone, regardless of the agent work mode. Previously, T-Server reported the values in the AttributeExtensions and AttributeReason attributes only when an agent was in the NotReady state with an Unknown work mode. (ER# 318013275)
T-Server now correctly handles the following scenario:
Previously, T-Server might have entered into an endless loop in these scenarios. (ER# 317515567)
T-Server now correctly populates the AttributePreviousConnectionID attribute value in EventPartyChanged and sends the next DN-related event in the following scenario:
report-local-connid-changes configuration option was set to true.
Warning! Do not use the report-local-connid-changes option unless you are instructed to do so by Genesys Technical Support.
Previously in this scenario, T-Server generated an EventPartyChanged event with the AttributePreviousConnectionID attribute value incorrectly set to ffffffffffffffff and failed to generate the first DN-related event for the call (EventRinging, EventQueued, or EventRouteRequest events, depending on the type of DN at which the call arrived). (ER# 316888704)
T-Server now correctly handles scenarios involving the completion of transfer or conference calls on unmonitored devices when the resulting call has at least one monitored party. Previously, when a conference was initiated from an unmonitored device, T-Server ignored the conference events and did not correctly update the resulting call information. (ER# 316492476)
T-Server, when running in High-Availability (HA) backup mode, now executes a recovery procedure for predictive dialing device scenarios. Previously, T-Server might have failed due to incomplete synchronized handling of the data received from the primary T-Server. (ER# 316137898)
T-Server now prevents the generation of events and access to released memory, if a device is deleted from the configuration environment and the last client is disconnected or unregistered. Previously, T-Server might have failed or stopped when a device that was previously deleted from the configuration environment, became idle and T-Server tried to release the memory used by the device structures. (ER# 315603856)
T-Server now correctly handles scenarios involving the completion of two-step transfer scenarios on non-monitored devices. Previously in this scenario, the UserData attribute information was lost and the EventPartyChanged message was not generated. (ER# 310963878)
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.001.47. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information about 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.
This release includes the following corrections and modifications:
T-Server now correctly handles scenarios involving transfers to a CCD Pilot when the PBX reports an unexpected order of events related to the scenario. Previously, T-Server may have failed due to the incorrect processing of calls. (ER# 309311671)
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.001.47. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information about 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.
This release includes the following corrections and modifications:
T-Server now correctly reports EventRinging events with the NetworkCallID attribute for incoming calls.
Previously, T-Server failed to match calls made through the ABCF trunk interface in Inter Server Call Control (ISCC) scenarios when the transaction type direct-network-callid strategy was used. (ER# 309250451)
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.001.47. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information about 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.
This release includes the following corrections and modifications:
T-Server now correctly handles scenarios where a call overflows from one member of a Hunt Group used for Emulated Routing to another member before the call is routed. Previously, T-Server did not report an EventRouteUsed event when the call was routed after an overflow occurred. (ER# 306975645)
T-Server now correctly handles TAgentNotReady requests for real agents when the real agent is already in the NotReady agent state. Previously, T-Server generated an EventAgentNotReady event without providing the correct agent workmode from the request. (ER# 306754309)
T-Server now correctly handles calls in transfer scenarios, where T-Server has calls with the same CallID, but are not related to the scenario. Previously in this scenario, T-Server left devices with these calls in the off hook state. (ER# 306135591)
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.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 the following new features or functionality:
T-Server now supports the computer-supported telecommunications applications (CSTA) protocol Bypass license feature on Microsoft Windows (32-Bit) platforms when an Alcatel A4400/OXE specific dynamic-link library (.dll) file is present in the execution directory. (ER# 301262771)
This release includes the following corrections and modifications:
T-Server now correctly handles transfer events reported on transferred devices if the resulting call has a call identifier (ID), which is equal to the call identifier of a call that already exists in the memory. Previously, T-Server may have incorrectly merged unrelated calls in transfer or conference call scenarios. (ER# 304086611)
T-Server now correctly reports agent-related events for agent supervisors when an agent supervisor is only logged into an ACD (Automated Call Distribution) that is not assigned to any processing groups, and the value of the configuration option, preassign-agent-compat, is set to true. Previously, T-Server reported the AttributeThisQueue attribute with a value of ACD in agent events for these agent supervisors. (ER# 302977603)
T-Server, when running in substitution mode, now correctly reports the CallStateOk attribute for calls routed from an Emulated Routing Point to an agent device. Previously, T-Server may have reported the CallStateRedirected attribute to an agent device in the same scenario. (ER# 302056312)
T-Server, when running in substitution mode, now correctly handles TRegisterAddress requests on agent devices. Previously, T-Server may have become unstable when unregistering the agent device. (ER# 301709402)
T-Server now automatically reports after-call work (ACW) wrap-up time after the release of PBX business calls regardless of the value of the configuration option, real-agent-pause-time. Previously, T-Server only automatically reported ACW wrap-up time for these calls when the value of the configuration option, real-agent-pause-time, was set to a non 0 (zero) value. (ER# 300497156)
T-Server now correctly handles scenarios with the release of business calls on agent supervisors that are logged into an ACD, but not assigned to any processing groups. Previously, T-Server left an agent supervisor in a persistent Legal Guard state after releasing an established business call. (ER# 299768866)
T-Server now correctly reports EventAgentNotReady events with agent work modes from requests when a real agent is set to NotReady as a result of an executed request.
Previously in this scenario, T-Server:
AttributeWorkMode attribute (except for the value of AgentAfterCallWork) in TAgentNotReady requests for real agents and generated an EventAgentNotReady event with the AttributeWorkMode attribute equal to the AgentWorkModeUnknown attribute.
(ER# 299733167)
T-Server now correctly accesses the values of configuration options defined on the Annex tab of the TServer section of an Agent Login object in Configuration Manager. Previously, T-Server had an issue when trying to retrieve these values. (ER# 299319046)
T-Server now correctly handles calls on Routing Service Interface (RSI) devices, if the PBX reports duplicate routing reference for these calls. Previously in this scenario, T-Server terminated unexpectedly. (ER# 298879341)
T-Server now correctly reports the ISCC error message to clients in Inter Server Call Control/Call Overflow (ISCC/COF) scenarios where the call overflows during ISCC routing. Previously, T-Server did not report the ISCC error message and incorrectly reported the following error message, Invalid connection ID, in the same scenario. (ER# 295803431)
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.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.
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:
T-Server now correctly handles scenarios involving logins of the real agent. Previously, if the preassign-agent-compat configuration option was set to true, T-Server generated an incorrect EventAgentLogout message before processing the login sequence. (ER# 297864296)
T-Server now correctly handles No Answer Supervision (NAS) scenarios in which a TAnswerCall request is received during NAS execution for a PBX Business Call. Previously, T-Server sometimes became unstable in this scenario. (ER# 295523033)
T-Server now provides a workaround to address PBX reporting, if the PBX reports an agent device as being idle during a login, while no login events have yet been generated. Previously, T-Server generated an EventOnHook message for an agent device while it was running in substitution mode. (ER# 297627122)
T-Server now first reports an EventAgentNotReady/AfterCallWork message, then EventReleased for the release of a PBX business call, if the business call type is set as a result of the agentBusy PBX event.
Previously, T-Server did not report EventAgentNotReady/AfterCallWork. (ER# 298479923)
T-Server now correctly handles the registration of agent devices during startup or when devices, while running in substitution mode, are added to the configuration environment. Previously, T-Server enabled client registration on agent devices and seized a license if the registration was requested before T-Server identified a device as an agent device. (ER# 296472841)
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.001.37. 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.
This release includes the following corrections and modifications:
T-Server now correctly handles login reporting from the PBX. Previously, in some cases, T-Server incorrectly generated an additional EventAgentLogout and EventAgentLogin sequence following the initial login. The subsequent login event did not contain AttributeThisQueue. (ER# 295904185)
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.001.36. 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:
T-Server is now able to route calls from the Routing Services Interface (RSI) to a user's Voice Mail if the RouteToVoiceMail key of AttributeExtensions is present in the TRouteCall request with a value of true or 1.
RouteToVoiceMail1, true, on, yes—T-Server routes calls to a Voice Mail of the device specified in AttributeOtherDN0, false, off, no—T-Server performs regular call routingTRouteCall (on the RSI)Route Select.
Note: If the call is to be routed to the Voice Mail of a relevant device, the other RSI extensions (RSIBypassFwdDND and RSIDisplaySelector) are ignored.
(ER# 290025719)
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 corrections and modifications:
T-Server no longer prevents setting ReasonCode (in the TAgentNotReady request) in the PBX. Previously, T-Server rejected this request if an agent already had a ReasonCode set as a result of the legal guard process (based on the legal-guard-reason configuration option). (ER# 284945918)
T-Server now correctly handles correlator data if it is specified in binary format. Previously, T-Server sometimes added invalid characters to the correlator field in the request that was sent to the PBX. (ER# 289903035)
T-Server now correctly handles scenarios involving devices with a secret identity feature activated. Previously, T-Server sometimes became unstable if a call was redirected from such a device. (ER# 289953838)
T-Server now correctly reports a PBX scenario where the PBX does not report call progress on an internal call but does report that the call is established. Previously in this scenario, T-Server provided incorrect call reporting and sometimes became unstable. (ER# 286345215)
T-Server now rejects a TAnswerCall request from a T-Server client on a device where No Answer Supervision is in progress. Previously, T-Server accepted TAnswerCall which sometimes caused the device being stuck in the held state. (ER# 287507179)
For PBX inbound business calls that are identified at startup, T-Server now places a party on an agent device in the established state, and then in the AfterCallWork (ACW) state after the call is released (if ACW handling is configured). Previously, T-Server did not report ACW for such a party. (ER# 291781211)
T-Server now correctly starts when the agent-smart-monitor configuration option is set to false. Previously, T-Server incorrectly reported the status of a proACD device with the logged agent if the agent-smart-monitor was set to false, and the PBX only reported a busy status on the agent device without providing call information in a snapshot. (ER# 286309471)
T-Server now correctly handles configuration updates in which DNs are disabled and enabled in quick succession in the configuration environment. Previously, T-Server sometimes entered into an infinite loop during such a configuration update. (ER# 288913091)
T-Server now correctly handles registration on an agent device that is not configured in the configuration environment where the agent-smart-monitor configuration option is set to true and a manual login was performed shortly before the registration attempt. Previously, T-Server entered into an infinite loop during registration. (ER# 288913091)
T-Server now correctly performs configuration updates in which an agent device is deleted from the configuration environment. Previously, T-Server might have become unstable if an agent logged in and logged out, and an agent device was removed from the configuration environment. (ER# 291187703)
T-Server now correctly handles treatment events while in the backup mode. Previously in this scenario, T-Server sometimes became unstable. (ER# 291187703)
T-Server now correctly handles a login request from the real agent if the agent-related event is reported by the PBX before the login is completed. Previously in this scenario, T-Server reported EventAgentLogin and a corresponding agent event without the AttributeThisQueue parameter. (ER# 292016917)
In a scenario where agent substitution is enabled and an agent device is disconnected and then reconnected (the PBX reports OutOfService and BackInService respectively), T-Server now correctly generates an EventDNBackInService message when the device is reconnected. Previously in this scenario, T-Server did not generate EventDNBackInService if an agent-related event was reported by the PBX between OutOfService and BackInService events. (ER# 291876074)
T-Server now correctly rejects a login request from an emulated agent if the real agent with the same ID has already logged in at the device. Previously, T-Server incorrectly generated EventAgentLogin and a relevant agent state event for the emulated agent, overriding real agent properties. (ER# 294307931)
T-Server now correctly reports the GCTI_NETWORK_TIMESLOT extension key on the destination party in the following messages:
EventPartyChanged– in scenarios involving a two-step transfer of an external call.EventRinging/EventQueued– in scenarios involving an emulated single-step transfer or emulated supervised routing that is requested for an external call.
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.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.
This release includes the following corrections and modifications:
T-Server now correctly completes supervised routing of an inbound call from an emulated Routing Point to a supervised RSI (Native Routing Point). Previously in this scenario, T-Server canceled supervised routing when the supervised timeout expired, and it did not allowed routing of the call from RSI. (ER# 282167967)
T-Server now correctly handles a PBX response to a Snapshot Device request if the PBX reports incorrect call data, including the list of Global CallIDs. Previously, T-Server sometimes became unstable while processing such a PBX response. (ER# 280668009)
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.000.24. 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.
This release includes the following corrections and modifications:
T-Server now correctly processes attempts to register agent devices when agent substitution is enabled. Previously, T-Server might have entered a continuous processing loop if an agent device was defined in the Configuration Layer, the link to the switch was lost and then reestablished, and the T-Server client attempted to register such a device. (ER# 280807925)
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.000.24. 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.
This release includes the following corrections and modifications:
T-Server now correctly handles requests containing extension/user data keys GCTI_SKILL_NUMBER_xx and other related keys. Previously, T-Server terminated unexpectedly when a request contained such keys in AttributeExtensions or AttributeUserData. (ER# 280784161)
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.000.23. 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.
This release includes the following corrections and modifications:
T-Server now correctly reports agent events when wrap-up and legal-guard are disabled and the agent is released from a business call. Previously, ACW Prediction could cause T-Server to leave the agent in an unavailable state after the agent was released from a conference. (ER# 278991412)
T-Server now correctly reports AttributeReason in events. Previously, T-Server could add a duplicate AttributeReason in events when a request from a client contained AttributeReason and T-Server added its own information to AttributeReason. (ER# 278945401)
T-Server no longer monitors an agent device with the PBX if the option agent-smart-monitor is set to true or strict, the agent is logged out, and the register flag in Configuration Manager is changed from false to true. Previously, T-Server incorrectly started the monitor on such an agent device and did not stop after identifying that the agent device was in the logout state, thus consuming an additional PBX license. (ER# 279694821)
T-Server no longer monitors devices with the PBX that are not present in the Configuration Layer and have no registered clients. Previously, T-Server registered such devices with the PBX on reconnection of the link or on role change, thus incorrectly consuming PBX licenses. (ER# 277649517)
T-Server now correctly processes information provided in a snapshot response on a proACD device after logout if: (a) there was a failed call for an agent that was previously logged in, and (b) the PBX moved the call from the agent device to the proACD device. Previously, T-Server could terminate if the PBX moved a call from a monitored agent device to a proACD device upon logout. (ER# 277601479)
T-Server now correctly handles changes of agent state when the PBX first distributes events and then acknowledgement for the requested service. Previously, T-Server generated an incorrect second agent event which might override some desktop application settings (Reasons). (ER# 277233571)
This release of T-Server is built with TSCP 8.1.000.23, which corrects the following issue:
T-Server no longer shuts down if it fails to obtain an ISCC license. (ER# 278678036)
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.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 Alcatel A4400/OXE.
background-processing configuration option has been changed to true.
heartbeat-period
- hangup-restart
bsns-call-dev-types which allows inclusion of External Routing Points to the list of devices that business call handling is applied to. T-Server now accepts the AttributeExtensions key BusinessCallType in the request TRouteCall. Previously, T-Server excluded External Routing Points from the list of devices where business call handling was applied to and did not accept the BusinessCallType key. (ER# 274601466)
This release includes the following corrections and modifications that were made between Release 8.0 or earlier releases and the initial 8.1 release:
T-Server now correctly releases a party in conference on behalf of the conference controller if it is specified via agentId and resides on a real agent when substitution is enabled.
Previously, such a request was rejected. (ER# 267089812)
T-Server now correctly handles the scenario where a call is routed with supervision from an emulated Routing Point to a device with forwarding set to RSI. Previously, T-Server did not complete supervision on the emulated Routing Point, thus taking the call back to the emulated Routing Point and generating an error. (ER# 274097941)
T-Server now correctly handles the scenario where a PBX keeps a call on an extension device before the agent has logged in, after the agent has logged in, and after the agent logs out. Previously, T-Server might have left the extension device in an incorrect state in such a scenario. (ER# 272460779)
T-Server now correctly processes information provided in snapshot response if a call was already known in the system. Previously, T-Server might have failed if a call from a monitored device was transferred or diverted to a device that did not pass idle state since T-Server connected to the PBX. (ER# 275550639)
T-Server now correctly performs routing on External Routing Points via divert if emulated Routing Point is used. Previously, T-Server always performed routing via answer-transfer. (ER# 275136179)
The option kpl-loss-rate has been removed from T-Server. (ER# 274609821)
This section provides corrections and updates for issues found in Framework 8.1 T-Server for Alcatel A4400/OXE Deployment Guide.
In the procedure Configuring supervisor call behavior in T-Server, ignore step 1 ("In the PBX configuration...").
Table 34: RSI Reroute Authorization includes incorrect values. Table 41 contains the correct values for RSI Reroute Authorization.
The guide incorrectly identifies the option rsi-xfer-tout as rsi-xfer-ftout.
The guide incorrectly states that the options kpl-interval and kpl-tolerance (detailed below) were removed in version 8.1.
kpl-interval
Default Value: 40
Valid Values: Any integer from 0 to 600
Changes Take Effect: Immediately
Specifies a "keep-alive" interval (in seconds). To check network connectivity,
T-Server issues a dummy CTI request at the interval specified when there is no
other activity on the link. A value of 0 (zero) disables this feature.
The value of this option may need to be increased to avoid false restarts if the switch is sometimes slow to respond, for example, during busy periods.
kpl-tolerance
Default Value: 3
Valid Values: Any integer from 0 to 10
Changes Take Effect: Immediately
Specifies the threshold number of accumulated KPL request failures. When the threshold is reached T-Server may consider the CTI link either:
The guide omits the following option description:
legal-guard-reason
Default Value: 0
Valid Values: 0–254
Changes Take Effect: Immediately
Specifies the value of the Reason Code key in AttributeExtensions that T-Server will report in an EventAgentNotReady message that is sent as a consequence of the legal pause phase.
This section provides the latest information on known issues and recommendations associated with this product.
The expiration check triggered by the option rq-expire-tout is performed every half the interval of the setting, so if the expiration timeout option rq-expire-tout is set to 10000 msec, the check is performed every 5000 msec. Every request that is expired at that moment is reported as expired. Actual expiration reaction depends at what point of expiration check request is started/executed. In this example, the reaction value would be at best 10 seconds and at worst 15 seconds (expiration time + half of the value).
| Found In: | Fixed In: |
To ensure backward compatibility, T-Server provides two options that define how many licenses T-Server can check out:
When the values of the two options are different, then T-Server applies the lower one, so Genesys recommends that you leave the option num-sdn-licenses at the default value max and set the option num-of-licenses to the actual number of licenses that you want T-Server to check out. Alternatively, you can set both options to the same value.
num-of-licenses
Default Value: max (equivalent to 9999 licenses)
Valid Values: max (equivalent to 9999) or any integer
Changes Take Effect: Immediately
Specifies the maximum number of DN licenses T-Server can check out. The values max or 0 (zero) is equal to exactly 9999 licenses. To check out any other number of licenses, specify the value as an integer, up to the number of seats supportable in your environment. The sum of all num-of-licenses values for all concurrently deployed T-Servers must not exceed the number of seat-related DN licenses (tserver_sdn) in the corresponding license file. The primary and backup T-Servers share the same licenses, and therefore they need to be counted only once. T-Server checks out the number of licenses indicated by the value for this option, regardless of the number actually in use.
num-sdn-licenses
Default Value: max (all DN licenses are seat-related)
Valid Values: String max (equal to the value of num-of-licenses) or any integer.
Changes Take Effect: Immediately
Specifies how many seat-related licenses T-Server checks out. A value of 0 (zero) means that T-Server does not grant control of seat-related DNs to any client, and it does not look for seat-related DN licenses at all. A value of "max" means that T-Server checks out the number of licenses defined in option num-of-licenses. The sum of all num-sdn-licenses values for all concurrently deployed T-Servers must not exceed the number of seat-related DN licenses (tserver_sdn) in the corresponding license file. The primary and backup T-Servers share the same licenses, and therefore they need to be counted only once. T-Server checks out the number of licenses indicated by the value for this option, regardless of the number actually in use.
T-Server may become unstable if the following conditions are met:
TAnswerCall while the NAS execution is in progress.(ER# 295523033)
| Found In: 8.1.002.01 | Fixed In: |
If the PBX does not report an EventOnHook event in a timely manner, T-Server might delay reporting this event after releasing a call that is parked on the established device (a device other than that on which the primary call is parked). (ER# 295165575)
| Found In: 8.1.002.01 | Fixed In: |
For an established call, instead of a TSingleStepTransfer request, T-Server may execute a TMuteTransfer request after T-Server restarts. (ER# 295356492)
| Found In: 8.1.002.01 | Fixed In: |
T-Server shuts down if it fails to obtain an ISCC license. (ER# 278678036)
| Found In: 8.1.000.05 | Fixed In: 8.1.000.07 |
T-Server incorrectly handles agents that login in a pre-assigned state if the PBX timer 238 is set to value higher than 11. In order to avoid this issue, verify that the value of the PBX timer 238 does not exceed a value of 11. (ER# 261524426)
| Found In: 8.0.101.00 | Fixed In: 8.1.002.01 |
When using ANI-related ISCC strategies (direct-ani, match-ani) and a call is initiated or a consultation call is initiated from an agent in substitution mode, T-Server is not able to match the calls. This is because the call is made from a substituted device (ProACD number), and delivered with the ANI of the agent device, which do not match. (ER# 235145471)
| Found In: 8.0.001.00 | Fixed In: |
In some circumstances, when routing a call from an emulated Routing Point with supervision, the switch completes the transfer on the Hunt Group member before T-Server can request a transfer completion or reconnection. The emulated routing is successfully performed, but this switch behavior results in T-Server returning an EventError call has disconnected message in addition to RouteUsed/Diverted on the emulated Routing Point. The RefID from the TRouteCall is returned in the EventError and not the EventRouteUsed. (ER# 231294614)
| Found In: 8.0.001.00 | Fixed In: |
If call forwarding is set on a remote extension to another internal device, and a call is made to that remote extension, the Call State is Ok instead of Forwarded when the call is delivered to the forwarded destination. (ER# 233146460)
| Found In: 8.0.001.00 | Fixed In: |
T-Server 8.0 only supports the PBX starting with Release 7.1. (ER# 244001815)
| Found In: 8.0.001.00 | Fixed In: |
If a call is made between two pro-ACD devices while T-Server is not running, and then T-Server is started, the PBX provides no information to T-Server's snapshot query for these devices. As a consequence, the call is invisible to T-Server. (ER# 208985444)
| Found In: 7.6.003.03 | Fixed In: |
When reporting is required for Hunt Group members, T-Server does not support the use of parallel Hunt Groups. (ER# 107538491)
| Found In: 7.5 | Fixed In: |
When reporting is required for Hunt Group members, the Hunt Group itself must not be configured in Configuration Manager. (ER# 107387229)
| Found In: 7.5 | Fixed In: |
High-availability (HA) synchronization is not supported for versions of T-Server released before 7.2.000.05 and, therefore, rolling upgrades of the backup T-Server are not successful until the primary T-Server is running at least version 7.2.000.05. (ER# 33467940).
| Found In: 7.2.000.02 | Fixed In: |
There is no support of emulation during switchover from 7.2 to 6.5 T-Server. An answered call is reported as a consultation call, thus creating a phantom ringing primary call. Switchover in the opposite direction does support emulation. (ER# 32974849)
| Found In: 7.2.000.02 | Fixed In: |
There is no support of emulation during switchover from 7.2 to 7.0 T-Server. An answered call is reported as a consultation call, thus creating a phantom ringing primary call. Switchover in the opposite direction does support emulation. (ER# 32974833)
| Found In: 7.2.000.02 | Fixed In: |
In the following scenario, an incorrect value of 2 is returned, instead of the value of 3.
2 is returned (Dialing).
PBX reporting does not allow you to distinguish between established and dialing states. Both are reported as connected. (ER# 31665149)
| Found In: 7.2.000.02 | Fixed In: |
When a consultation call is made over ABC-F to a RSI and the overflow timer is configured on the RSI, and no overflow destination is configured, the PBX should drop the consultation call when the timer expires. However, the PBX actually drops the call on the RSI, but not on the transferred device. If the transfer is then completed, the call shows up again on the RSI. (ER# 44404261)
| Found In: 7.2 | Fixed In: |
T-Server does not issue an EventOnHook/EventOffHook event for devices configured as PCM ports. (ER# 74176)
| Found In: 7.0 | Fixed In: |
In a scenario where an agent receives a CCD call and issues a request for supervisor assistance by CTI with a TPrivateService request equal to 6, the switch correctly responds with an EventAssistRq message with a requestStatus with a value of TRUE.
When the agent issues a second request, again using the TPrivateService equal to 6, a EventAssistRq message with the requestStatus with a value of FALSE is returned even though there is still an outstanding supervisor request, and the ACD Listening key on the supervisor's set is alerting.
If the call is then released, the request remains present on the supervisor's ACD Listening key. (ER# 234763632)
| Found In: R9.0 h1.301.31 | Fixed In: |
In some scenarios involving several hybrid link transfers to pilots during the life of one call, the switch fails to report the alerting device in messages to T-Server. In such circumstances, T-Server reports the OtherDN attribute as the trunk for devices receiving messages where the alerting device is missing. (ER# 234763641)
| Found In: R9.0 h1.301.31 | Fixed In: |
In the following scenario, when the call is delivered to Pilot2, the switch is changing the global Call ID. Thus, T-Server cannot maintain the Connection ID and all the attached data is lost.
supervised-route-timeout option is set to a value of 0 (zero).
Since the supervised-route-timeout option is set to 0 (zero), T-Server issues a redirect to move the call off the Hunt Group member and this results in the switch changing the Global Call ID. (ER# 234763648)
| Found In: R9.0 h1.301.31 | Fixed In: |
In a scenario where two calls are made to a twinset, and the first call is queued and the second call is ringing, if the origination DN of the first call releases, the switch sends no connection cleared for the twinset. T-Server therefore continues to report that there are two calls on the twinset. The switch will only send a connection cleared for the first call, once the second call is released. (ER# 234763657)
| Found In: R9.0 h1.301.31 | Fixed In: |
In the following scenario, the switch drops the call instead of transferring the original inbound call to the RSI.
(ER# 234763664)
| Found In: R9.0 h1.301.31 | Fixed In: |
In the following scenario, the call from GVP will fail.
INVITE with Require:timer.
At this point the switch incorrectly returns a 420 Bad extension message and the call will fail.
(ER# 234763681)
| Found In: R9.0 h1.301.31 | Fixed In: |
The following scenario prevents GVP from being able to complete the transfer, which results in the voice path between the agent and the caller being broken.
re-INVITE to OXE to bridge the RTP (voice path) between the agent and the caller.
re-INVITE with SDP on the outbound leg to GVP.
re-INVITE on the inbound leg to OXE.
re-INVITE on the inbound leg to GVP.
re-INVITE on the inbound leg with a 491 Request Pending response.
re-INVITE sent by GVP, and does not attempt another retry of the re-INVITE.
(ER# 234763688)
| Found In: R9.0 h1.301.31 | Fixed In: |
If a hybrid link call is made to a Routing Services Interface (RSI), and routed to the tandem set of the twinset, then the switch changes the GCID. This is an invalid scenario as the call should be routed to the main set.
However, a workaround has been implemented in T-Server in order to handle this scenario should it occur. The following limitations apply to the workaround:
ThisQueue attribute does not reflect the routed calls, and so on).
Call Control is retained on both the origination and the destination T-Servers.
(ER# 233727437)
| Found In: R9.0 h1.301.31 | Fixed In: |
When transferring from a Thomson ST2030 SIP extension, before the REFER (SIP transfer), the ST2030 puts both legs on hold using RE-INVITE. This means that before the standard Genesys transfer call flow, T-Server reports EventHeld for the active consultation call and EventRetrieved for the held primary call. (ER# 227362583)
| Found In: r9.0 h1.301.28 | Fixed In: |
When a call is camped on a SIP extension and answered so that the first call is held, neither leg can be released by CTI. The switch rejects the request. (ER# 227362592)
| Found In: R9.0 h1.301.28 | Fixed In: |
In the following scenario, on the SIP phone, the consultation call is dropped and the primary call is retrieved. However, the switch sends a transferred event to T-Server, so T-Server reports the transfer and now believes that there is no call on the SIP phone.
Note: This only occurs on an inbound call to a SIP extension. It is not a problem for internal calls. (ER# 227362598)
| Found In: R9.0 h1.301.28 | Fixed In: |
When an inbound call is made to a SIP extension and the reject button is pressed on the phone, the switch incorrectly sends EventDiverted instead of EventConnectionCleared. This means T-Server reports EventReleased with CallStateNoAnswer instead of EventAbandoned. (ER# 226343661)
| Found In: R9.0 h1.301.28 | Fixed In: |
The PBX reporting on a transfer to RSI is different for multiline/MEA devices than for other devices. As a result, T-Server reports an EventAbandoned on the RSI when the transfer from the multiline/MEA device is completed. (ER# 77051971)
| Found In: R7.1 f5.401.1 | Fixed In: |
A supervisor has permanent listening enabled on an agent. The agent receives a CCD call and redirects it (T-Server emulates the redirection). If the redirection occurs too quickly (approximately under a second after the call appears on the agent) then a timing problem can occur as a result of the mechanism used by the PBX to report supervisor monitoring.
This results in the PBX sending conference events for the agent and the supervisor in some instances, and transferred events in other instances. This means that T-Server is not able to consistently provide the correct reporting for supervisor monitoring. (ER# 44404273)
| Found In: PBX v. 7.0 | Fixed In: |
After a failed route, if the transferring device reconnects then the PBX does not provide either the proper Retrieve event or a Connection Cleared for the consultation dialing leg. However, on the phone set, the consultation leg is dropped, and the primary leg is retrieved, which results in T-Server being desynchronized with the phone set. (ER# 37371452)
| Found In: PBX v 7.0 | Fixed In: |
The PBX does not allow a hybrid link transfer to RSI to be completed if the phone set is in DTMF state. This means that it is impossible to complete a hybrid link transfer if a collect digits treatment or an interruptible Play Announcement treatment is playing. (ER# 37371446)
| Found In: PBX v 7.0 | Fixed In: |
In PBX version 7, the PBX changes the routing reference in the routing dialog when a transfer from an unmonitored device, or a transfer is made over ABC-F trunks, is completed on the RSI. T-Server relies on this routing reference to match the calls. As a result of this change, T-Server can no longer correctly report this scenario. (ER# 37252571)
| Found In: PBX v 7.0 | Fixed In: |
When an emulated predictive dial is made from a busy pilot (RSI without supervised routing enabled), the PBX incorrectly reports the supervised transfer status to T-Server. This means that if any timeout is configured in prd-dist-call-ans-time configuration option, it cannot be invoked. (ER# 2759501)
| Found In: PBX 6.1 | Fixed In: |
T-Server does not support CCD Routing Pilots (CCD Pilots with the routing flag enabled). (ER# 36422)
| Found In: All switch versions | Fixed In: |
The PBX does not send any events to T-Server when forwarding is set manually on any device. (ER# 11009)'
| Found In: 5.1.011, all switch versions | Fixed In: |
If the progress of a single-step transfer is interrupted by any request, T-Server may not be able to correctly report the scenario. (ER# 74183)
| Found In: Unspecified | Fixed In: |
Prior to T-Server release 8.0, a TMakePredictiveCall request cannot be made to an internal destination. (ER# 107590864)
| Found In: Unspecified | Fixed In: |
There is an incompatibility between A4400 T-Server behavior regarding chained consultation calls and the OCS option, call_transfer_type =
two_step. On the A4400 it is not possible to chain consultation calls, therefore in that situation, T-Server completes the transfer. However, when OCS
is using two-step transfer and waiting for the agent to answer, it attempts to complete the transfer. This leads to the two applications clashing when agent-no-answer-overflow = recall to the queue.
With a consultation call on the agent, agent-no-answer-timeout expires, and this forces T-Server to perform an emulated redirect. This involves
answering the call on the agent, T-Server completing the transfer, and then T-Server transferring the call back to the queue. However, because OCS sees an
EventReleased on the consultation call (due to completion of the transfer) it attempts to reconnect the call, assuming the call has failed. (ER# 36839060)
| Found In: Unspecified | Fixed In: |
The PBX does not support the Do Not Disturb (DND) functionality via CTI, so setting the DND functionality can only be done from the phoneset. The PBX also does not provide any CSTA reporting to T-Server when the DND functionality is set manually on a telephone set. (ER# 31943037)
| Found In: Unspecified | Fixed In: |
Chained consultation calls are not supported by the PBX. (ER# 14800088)
| Found In: Unspecified | Fixed In: |
Four-party and blind conference calls are not supported by the PBX. (ER# 14800090, 14800092)
| Found In: Unspecified | Fixed In: |
When a hot-standby pre-release 8.0 of T-Server is started, the status of the active emulated agents is not accurately reported. (ER# 74180)
| Found In: Unspecified | 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.
The following operating systems:
| Discontinued As Of:�December 17, 2020; 8.1.008.03 |
Solaris 9 and Windows 2003 operating systems
| Discontinued As Of: 8.1.006.01 |
Red Hat Enterprise Linux 3.0 operating system
| Discontinued As Of: 8.1.000.05 |
Solaris 8 operating system
| Discontinued As Of: 8.1.000.05 |
Tru64 UNIX operating system
| Discontinued As Of: 8.1.000.05 |
AIX 5.1 and 5.2 operating systems
| Discontinued As Of: 8.1.000.05 |
Information in this section is included for international customers.
There are no known restrictions specific to international customers.
Additional information on Genesys Cloud Services, Inc. is available on our Customer Care website. The following documentation also contains information about this software.
The Framework 8.1 T-Server for Alcatel A4400/OXE Deployment Guide provides detailed reference information for the Genesys Framework T-Server for the Alcatel A4400/OXE 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 (orJava) 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 the 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.