As of February 1, 2012, Genesys is no longer an affiliate of Alcatel-Lucent; any indication of such affiliation within Genesys products or packaging is no longer applicable. Please see the Genesys website at http://www.genesys.com for more details.
This release note applies to all 8.1 releases of T-Server for NEC NEAX/APEX.
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.5.000.25. TSCP is the shared software that all T-Servers and SIP Server 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 an update for this product. This release contains no new features or functionality.
This release includes the following corrections and modifications:
T-Server no longer ignores the release message from the switch during a race condition involving RequestReconnectCall followed immediately by RequestRedirectCall. (TS-12086)
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.25. TSCP is the shared software that all T-Servers and SIP Server 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 an update for this product. This release contains the following new features or functionality.
This release includes the following corrections and modifications:
Hot Standby high-availability functionality now works correctly. Previously, starting with version 8.1.011.06, the Hot Standby HA was incorrectly disabled by an internal setting. (TS-12053)
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.011.13. 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 distributes EventOnHook on receiving SMFN 3
for an off-hook device, even if the corresponding party is no longer on the call. One scenario where this could happen is when a call is released while one of its legs is on hold and a second call arrives on one of the DNs involved. You can disable this behavior by setting the new option onhook-without-party to false
. (TS-11934)
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.011.09. 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. See the Supported Operating Environment: T-Server for NEC NEAC/APEX page for more detailed information and a list of all supported operating systems.
This release includes the following corrections and modifications:
T-Server now correctly generates an EventOnHook message after previously generating an EventOffHook message, when a DN returns to the onhook state. This issue applied to a scenario where an internal DN dials another internal DN which also has the call waiting feature enabled. (TS-11541)
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.011.09. 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 now supports the call model Rejected Call (Route Point). See Rejected Call in the Events and Models Reference. Previously, T-Server did not properly specify CallStateDropped in the EventDiverted event for this call model. (TS-11562)
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.011.09. 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 2016.
Support for Red Hat Enterprise Linux 7, 64-bit.
T-Server adds support for AttributeTimeout on RequestPredictiveCall in accordance with the T-Library specification for TMakePredictiveCall. The timeout specifies the time in seconds after which the call should be considered unanswered. This timeout is in effect the moment after EventDialing is processed in NEC T-Server and up to the point a call is classified as answered. In the event the timer fires, NEC T-Server attempts to drop the call.
Important: This timeout value does not override any default call drop timeout set by the NEC switch. Also, for this feature to work, the option suppress-trunk-events must not be set to true. (TS-11496)
This release includes no corrections or 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.78. 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 no longer becomes unstable when processing OAI acknowledge messages for SCF FID=8 (OAI_SCF_CONFERENCE_CALL) requests, after the corresponding TSingleStepConference request is destroyed in memory. (TS-11104)
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.78. 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 now correctly processes TReconnectCall
requests
by correctly specifying the third-party parameter of the OAI SCF10 request,
when such a request follows call redirection via OAI SCF10 where the third-party parameter is required.
Previously, the switch rejected erroneous SCF 10 call reconnection requests. (TS-11082)
The distribution of the ANI
attribute is now enabled for internal calls to a Split Routing Point device and is controlled
by the common T-Server option ani-distribution
.
By default, this option allows the ANI attribute for only inbound calls. Setting this option to all-calls
enables ANI to be distributed for
internal calls to a Split RP. Previously, T-Server didn't distribute the ANI
attribute for such calls. (TS-11011)
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.78. 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 no longer specifies an unexpected 3rd-Party Information
parameter in the OAI SCF 10 (Ringstop) message to the PBX in processing a TRedirectCall request.
Previously, an unexpected parameter could have been inherited from the previous SCF 10 request, causing the PBX to reject the subsequent SCF 10 request with
the invalid parameter. (TS-10958)
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.78. 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 now correctly handles MakePredictiveCall requests from a Split device. Previously, T-Server used the split instead of the pilot number in the 1st-Party Terminal Info of the OAI SCF Trunk Call request, causing the switch to reject such requests. (TS-10935)
T-Server no longer deletes ISCC calls when two parties simultaneously update UserData with the same key and value, and the option consult-user-data has the value joint. Previously, T-Server treated this situation as a data propagation loop, resulting in ISCC call deletion. (TS-10913)
T-Server now correctly processes an unsuccessful single-step transfer of a consultation call, when the PBX sends an OAI SMFN 3 (Release) message for the transfer originator but the call never reaches the transfer destination. Previously, T-Server misinterpreted this scenario, causing the DN initiating the transfer to remain in the off-hook state when the call was released. (TS-10875)
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.77. 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 correctly handles OAI SMFN FID=2 (Answer) on the call origination party in the following scenario:
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.77. 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 now correctly handles OAI SMFN FID=2 (Answer) messages with empty 2nd-party information on an Attendant Console device. Previously, such messages caused an invalid call ID mapping inside T-Server, which eventually led T-Server to terminate abnormally. (TS-10878)
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.76. 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:
A new option, switch-system, specifies a switch system family, to prevent the rejection of certain requests by small switch systems.
switch-system Default value:large
Changes take effect: Immediately
Valid values:
large
- Use this value for large switch systems such as the NEAX/APEX 2400, SV7000, SV8500, and SV9500.small
- Use this value for small switch systems such as the NEAX 2000 and APEX 3600.When the setting is large
, T-Server specifies a sub-line of a main-line device in the 2nd Party Term Info parameter of the
SCF FID=2 (Release) request. T-Server sends an SCF FID=2 (Release) request when it releases a call or completes a call transfer.
When the setting is small
, T-Server encodes FID=2 (Release) requests in call release or transfer
completion scenarios on the small system switches. No device line substitution occurs.
Previously, for small switches, T-Server incorrectly substituted the 2nd Party Term Info parameter for a sub-line device in SCF FID=2 (Release) requests, which caused the switch to reject the request. (TS-10816)
T-Server now provides enhanced handling of RequestAgentLogin requests in scenarios when a switch responds with the Infolink negative response IY code 09. The response IY 09 (Logon not vacant) means that either:
Previously, T-Server always raised an EventAgentLogin in response to IY 09, which resulted in inconsistent reporting of reported and actual agent state for the second condition. Now, to report a consistent state, T-Server queries an agent state in response to IY 09. If the query response indicates that an agent is logged in, T-Server raises an EventAgentLogin or an EventError. (TS-10805)
This release includes the following corrections and modifications:
For Handyphone devices reported as type "a" (ACD position), T-Server no longer tries to look up sub-line association in Infolink Iq and IW messages. Previously, T-Server ignored such messages. (TS-10802)
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 the NEC UNIVERGE SV9500 switch. See Known Issues and Recommendations for switch limitations.
Support for new business features — Call Parking, Call Pickup, and Multi-line Operation — on the NEC UNIVERGE SV8500 switch. (TS-10678, TS-791)
Support for RTP Monitoring API. T-Server now supports the standard
Genesys Real-Time Protocol (RTP) stream monitoring API to allow
integration with third-party recording solutions. A new
configuration option, rtp-info-password
, specifies the
password to allow voice-monitoring applications to monitor any call. Another new option,
report-dterm-ip-addr
, discovers D-Term IP addresses. (TS-9698)
Support for SCF Calling Party Number Selection. T-Server now supports the
SCF Calling Party Number Selection to enable you to use the NEC
UNIVERGE SV8500 switch to specify your calling party number
according to your needs. The configuration option,
scf-calling-nbr-encoding
, specifies the encoding method
of the calling party number information. (TS-10525)
Addition of the 3rd-Party Terminal Info
parameter to the SCF 10 (Ring Stop) OAI request. The parameter requires
a party to remain on the call after a redirect, eliminating the unexpected
disconnection of an external caller from an agent. (TS-759)
This release includes the following corrections and modifications:
T-Server now correctly handles Agent state synchronization messages sent by the backup T-Server. Previously, after a switchover, incorrect handling caused the backup T-Server to lose the ReasonCode
extension in EventAgentNotReady
. (TS-10701)
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.73. 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 accepts up to 9999 seat licenses newly issued by License Manager when the option num-sdn-licenses
is changed from a previous finite value to max
. Previously, T-Server did not accept these new licenses. (TS-10640)
In multisite scenarios, T-Server now properly propagates EventPartyAdded
when an Observer
party connects to the call. Previously, T-Server propagated EventPartyAdded
in conference calls only. (TS-850)
T-Server no longer incorrectly generates a second EventError with the same ReferenceID when two agents simultaneously disconnect from a consultation call. (TS-10618)
T-Server now correctly applies dynamic changes for string array options. Previously, T-Server might have incorrectly applied dynamic changes for these options. (TS-9629, ER# 256449305)
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.54. 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 specifies the second-party terminal information parameter in SCF FID=2
(Release Call
) OAI requests in single-step transfer scenarios, when T-Server sends an SCF FID=2
(Release Call
) OAI request before the call reaches the transfer destination party. Previously, this OAI request failed and an EventError
event was sent with the following error message: Connection terminal mismatch - 1st to 2nd mismatch
. (ER# 310123981)
T-Server now implements the enhanced handling of transfer-reconnect
and transfer-complete
scenarios when establishing a consultation call between an Attendant Console device and a transfer destination. Previously, T-Server was unable to differentiate these scenarios and handled these reconnections as call transfers, causing a call state de-synchronization between T-Server and the actual state on the switch. (ER# 295615201)
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.54. 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 no longer prevents its clients from registering DNs of type Unknown
that are not configured in the Configuration Layer. However, T-Server still restricts DN registration of types Extension, ACD Position, ACD Queue,
and Routing Point
that are not configured in the Configuration Layer. (ER# 302652935)
T-Server now correctly generates an EventRetrieved
message after a TReconnectCall
request from a monitored DN. (ER# 310123981)
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.50. 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:
This release of T-Server is built with TSCP 8.1.001.50, which corrects the following issue:
T-Server now correctly sends Local Control Agent (LCA) heartbeat messages. Previously, in scenarios where T-Server was built with TSCP version 8.1.001.47, T-Server could become unstable, if it was running on the same host as LCA 8.1.0 operating in Unresponsive Process Detection mode. (ER# 309597081, ER# 308202408)
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 contains no new features or functionality.
This release includes the following corrections and modifications:
T-Server now correctly performs User Data propagation for Inter Server Call Control (ISCC) calls in deployments where two or more T-Servers monitor DNs on the same switch and have the value of the match-call-once
configuration option set to false
. Previously, T-Server stopped the User Data propagation for the ISCC calls. (ER# 302446516)
T-Server now enables more efficient monitored DN deletion processing. Previously, in environments with a large set of DNs under the switch, DN deletion caused T-Server to use an excessive amount of the central processing unit (CPU) resources, which resulted in an overload. (ER# 299721798, ER# 299626400)
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.42. 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 correction and modification:
T-Server now correctly handles backup synchronization message processing in the following scenario:
Previously in this scenario, the synchronization messages for an agent in the Ready
state were incorrectly processed, which led to the agent state being incorrectly reported as NotReady
. (ER# 305838728)
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.42. 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 now correctly distributes an EventRetrieved
event for the original call after the following scenario is complete:
Previously, T-Server did not distribute an EventRetrieved
event after a call reconnection attempt.
(ER# 299025227, 296563839)
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 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:
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 also includes the following corrections and modifications:
When a T-Server running as a Windows service is stopped, the snapshot log is now correctly deleted. Previously, when a T-Server running as a Windows service was stopped from the Solution Control Interface and no links to the PBX were open, the snapshot log was not deleted. (ER# 262180943)
When TRouteCall
disconnects a call with AttributeRouteType 7
(RouteTypeReject
), T-Server now correctly generates an EventOnHook
message. (ER# 281618625)
T-Server now correctly decodes "1st Party information" of an SMFN message when the DN length is 2 bytes. Previously, following a TSingleStepTransfer
request, T-Server skipped the decoding of 2-byte DNs (analog station 8#
, for example), causing incorrect OAI message processing and consequently stranding the DN On-Hook. (ER# 276564146)
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.31. 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.
T-Server now specifies the second-party terminal information parameter in SCF FID=2 (Release Call)
requests when T-Server releases a call or completes a transfer and the designated party is in the connected state. Otherwise, the second-party information parameter is not specified.
Specifying the second-party information parameter can prevent an unwanted call disconnection in case of race conditions that may occur when T-Server completes a transfer request and the consultation destination party disconnects simultaneously. (ER# 285751174)
propagated-call-type
. (ER# 273722944)
This release includes the following corrections and modifications:
This release of T-Server is built with TSCP 8.1.000.31, which corrects the following issue:
In multi-site conference scenarios involving call path (trunk) optimization at one of the call locations, T-Servers at other call locations now correctly generate EventPartyDeleted
messages when an external party leaves the conference. (ER# 291027891, 284077422)
This release of T-Server also includes the following corrected TSCP issue:
In a multi-site environment, when due to delays in messaging between sites, T-Server simultaneously receives two different user data updates for the same call or for a consultation call and its main call, and if the consult-user-data
option is set to joint
, T-Server no longer alters the internal structures that determine the sequence in which call data updates are performed. Previously, in the rare case of such a collision, T-Server could alter these structures in order to prevent an incorrectly detected data propagation loop and this could break down subsequent user data updates for this call or for this pair of a consultation and a main call. Note the colliding updates are rejected as before, since it is impossible to determine their order of precedence. An important but extremely infrequent limitation: when such user data updates have identical contents, they cannot be distinguished from an actual data propagation loop and a breakdown of subsequent user data updates remains possible. (ER# 286135992, 285906677)
When operating in backup mode, T-Server no longer sends a JL (query agent data) request if the agent logon ID is unknown. (ER# 274734657)
T-Server now sends an EventOnHook
message in the following scenario:
SCF FID=7 (OAI_SCF_TRANSFER_CALL)
OAI request.EventOffHook
and EventEstablished
messages for party B.SCF FID=2 (Release call)
request.EventOnHook
after Step 5.
(ER# 275403500)
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 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 also includes the following corrections and modifications:
The primary T-Server now correctly synchronizes Agent states and DN statuses with the backup T-Server. Previously, after a switchover, the new primary T-Server (former backup) reported invalid Agent states and DN statuses in response to respective queries from T-Server clients. This issue only applied to T-Server version 8.1.000.16 and later. (ER# 283834041)
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 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.
TSetMutOff
request. To invoke the Barge-in operation via the Infolink IG (Manipulate Call)
request, a new T-Server configuration option, mute-off-using
, must be set to infolink
.ssfr
ssfr, infolink
TSetMuteOff
request when an ACD Supervisor attempts to barge-in into a monitored call. When this option is set to ssfr
, T-Server uses the SSFR FID=32 (Mute Set/Reset)
request for barge-in. When this option is set to infolink
, T-Server uses the Infolink IG (Manipulate Call)
request with the b
attribute for barge-in.This release does not contain any corrections or 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.000.25. 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 feature:
11
(KeepingOfSubscribe
), the switch may instantly reset devices that are in an “unmatched”
state. If the primary T-Server is not available, the backup T-Server processes SFN 3
(Release
), IW z
(Forced Logoff
), and SSFN
directly from the link. (ER# 281924241)
This release also includes the following corrections and modifications:
T-Server now correctly parses Infolink IV
(Call Transfer
) messages if a message contains the call identifier
attribute. Previously, an error parsing such messages caused incorrect message handling when a party was released from a conference and T-Server received a SMFN3
(Release
) event followed by IV
(Call Transfer
). The reverse order of events did not result in a problem. (ER# 282998601)
A T-Server in backup mode now correctly handles the IW z
(Forced Logoff
) message from a switch in “dual-redundancy” mode when there is no Primary server with a connected link and an agent state is reset. Previously, this message was ignored, leaving an incorrect agent state.
(ER# 283442822)
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 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:
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 this release of T-Server for NEC NEAX/APEX.
T-Server now supports the Genesys RTP stream monitoring API. This API allows integration with third-party recording solutions. Two new configurations options, report-dterm-ip-addr
and rtp-info-password
, have been introduced to support this feature:
report-dterm-ip-addr
false
true
, false
When set to a value of true
, T-Server invokes OAI SSFN/SSFM facilities to discover the IP address of a monitored IP DTerm.
The discovered IP address is reported in the RTP monitoring events by the X-PI-RTP
parameter. When set to a value of false
,
IP address discovery is disabled.
rtp-info-password
This option specifies the password to allow voice-monitoring applications to monitor any call. If a password is not provided, no applications will be able to perform monitoring. Note that this password is not secure. It is passed as text to the voice-monitoring application.
Note: The RTP monitoring API is only available on NEC PBX releases supporting SSM/SSNF MOID=16 (IP Registration) OAI messages, and is only provided for IP terminals. The T-Server options report-dterm-ip-addr
and rtp-info-password
must be properly configured to enable this feature.
There are no corrections or modifications for this release.
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 NEC NEAX/APEX.
Infolink heartbeat functionality. T-Server is able to simulate heartbeat polling of an ACD link. The new configuration option enable-infolink-heartbeat
has been introduced to implement this functionality.
Enhanced agent state notification. The new configuration option trigger-agent-state-response-by
has been introduced to modify the distribution of agent state notifications.
Support of the NEC dual redundancy feature. In dual redundancy mode, in the event of a failover, the switch is able to preserve T-Server subscription data. This functionality is controlled by the new configuration option, aarq-logical-port
.
Multi-ACD processor support on an FCCS network. T-Server fully supports a multi-ACD processor on a Fusion Call-Control System (FCCS) network.
Enhanced handling of rapid link restoration for the OAI association open results (AARE Result=10)
and (AARE Result=11)
. T-Server disables flow control if DN registration is not required, which allows the link startup procedure to occur more quickly. (ER# 271911975)
heartbeat-period
hangup-restart
T-Server is now supported on the following platforms:
T-Server no longer connects to applications that have disabled status in the configuration environment.
background-processing
configuration option has been changed to true.
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 properly distributes EventRetrieved
events for a transferred party on the original call in a two-step transfer call scenario. Previously in this scenario, T-Server failed to properly distribute EventRetrieved
events. (ER# 265305044)
T-Server now encodes the reason
parameter of the RLRQ (0x62) OAI
message as a one byte integer field. Previously, T-Server encoded this parameter as a two-byte field. (ER# 263418864)
T-Server no longer becomes unstable when an ACD Position object associated with an Extension is removed from the configuration layer, and another ACD Position object associated to the same Extension is subsequently added. (ER# 268759489)
T-Server now correctly specifies the UserData
attribute in SingleStepTransfer
scenarios. Previously, T-Server incorrectly attached user data from the second call in scenarios where two consecutive calls utilized a SingeleStepTransfer
, and the first call failed, because the transferred party hung up. (ER# 265534053)
T-Server now re-sends requests for the monitoring of Hold notifications, (SMFR FID=0x85 (HOLD))
, if the previous request has failed. The SMFR FID=0x85
notification is sent during the DN registration process of the link startup when the configuration option oai-hold
is set to a value of true
. (ER# 264457048)
T-Server now correctly reports the ReferenceID
attribute within the EventError
event in the following scenario:
TReconnectCall
request at the same time that Agent-2 hangs up.
EventError
.
THoldCall
request.
Previously in this scenario, T-Server generated an EventError
event containing the ReferenceID
from the Hold request (Step 4), and the EventHeld
event at Step 4 was missing the ReferenceID
attribute. The EventError
and EventHeld
events now contain the correct ReferenceID
attribute from the matching requests.
(ER# 270635613)
This section provides corrections and updates for issues found in currently released documentation for this product.
The following limitation is added:
AttributeCallState may not be propagated according to the call model as CallStateBridged in TEvents in supervision scenarios that involve multiple T-Servers. Typically, CallStateOk will be used instead. This is because this T-Server does not fully support cross-site supervision. (TS-12098)
The configuration options cleanup-idle-tout and notify-idle-tout use values in seconds.
In the Switch Configuration Requirements section of the Switch-Specific Configuration chapter of the T-Server for NEC NEAX/APEX Deployment Guide, step 1 (Enable Answer (Connection) Notification for external trunks) incorrectly instructs you to set Bit 3
. The correct setting is Bit 7
.
In Table 19, Setting the DN Properties for the NEC NEAX/APEX Switch, of the T-Server for NEC NEAX/APEX Deployment Guide, the entry for SPLIT_ROUTE_POINT incorrectly states "Do not use this type of Routing Point for External Routing Points." You can in fact use SPLIT_ROUTE_POINT for an External Routing Point.
This section provides the latest information on known issues and recommendations associated with this product.
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.
If a DN puts an active call on hold and tries make another call, the switch sends an error message. (TS-10680)
Found In: 8.1.001.02 | Fixed In: |
When a single-step conference is requested to a DN where forwarding is set, the call rings at the destination of the request rather than at the forwarding target. (TS-10679)
Found In: 8.1.001.02 | Fixed In: |
On NEC 2000 systems, the release of a consultation call by the external party results in a ringing call that cannot be answered through a CTI request. (TS-10629)
Found In: | Fixed In: |
T-Server does not support single-step conferencing to external numbers. (TS-11114)
Found In: 8.1.000.09 | Fixed In: |
T-Server shuts down if it fails to obtain an ISCC license. (ER# 278678036)
Found In: 8.1.000.09 | Fixed In: 8.1.000.15 |
Switch limitation: The RequestAlternateCall
is not supported by T-Server working with an SV8500 switch. (ER# 257517024)
Found In: 8.0.300.09 | Fixed In: |
T-Server may improperly clean an internal Call ID table when T-Servers operate in high-availability mode and a primary-to-backup switchover coincides with a switch link failure. (ER# 164945761)
Found In: 7.6.003.03 | Fixed In: |
Switch limitation: Because of a limitation of CTI support of the Recall
call scenarios on Large-System NEC NEAX/APEX switches, T-Server may incorrectly report the state of a telephony device. (ER# 25873710)
Found In: 7.2.004.00 | Fixed In: |
In some configurations of the NEC NEAX SV7000 PABX and CallWorX (an external ACD),
there is a known deficiency of ACD behavior during an attempt to route a call to a busy destination
from a SPLIT_ROUTE_POINT
device via an Infolink IF
request.
T-Server receives a positive acknowledgement from the ACD, and thus cannot recognize
a call routing failure. This behavior affects external call routing to default
destinations specified in the extrouter-default-dn
or router-default-dn
options. (ER# 6372854)
Found In: 7.1.007.01 | Fixed In: |
Because of deficient Infolink messaging, T-Server does not support the call-recovery feature on Large-System NEC NEAX/APEX switches where calls distributed from a Split to an agent and not answered within a timeout determined by the switch are re-queued to the Split. In this scenario, the Infolink does not notify T-Server that the call has been re-queued. (ER# 92841)
Found In: 7.1.001.01 | Fixed In: |
Service Observing limitations include the following:
For correct call handling by T-Server, only one Observer may monitor a call at a time.
T-Server has limited support for conferences with Service Observing. When a call is monitored, a 3-way connection is established (caller, destination, and observer) via a TCT trunk, so a simultaneous conference (that is, an additional participant) is not possible without a multi-way conference card.
To activate Service Observing via the "ACD Supervisor" feature,
the supervisor must be off-hook and must not use the SPEAKER
key of a Dterm
to monitor an agent.
Found In: 6.5.200.03 | Fixed In: |
If you must use an IP address (such as 180.170.9.150
)
or a full host name including the domain name (such as server.genesyslab.com), expect to receive
a warning during the installation of any application on this host.
The warning message informs you that the installation cannot find the specified
object; as a result, the installation script does not update the configuration
data for this application. If you see this warning, continue with the installation.
After completing the installation, update the configuration data for the application you installed on this host, as follows:
Properties
dialog box for the Application object in Configuration Manager. Working Directory, Command Line,
and Command Line Arguments
on the Start Info
tab. Apply
and OK
to save configuration updates. run.sh
file to start the application, verify that the Working Directory,
Command Line,
and Command Line Arguments
are specified correctly in
the run.sh
file. Found In: 6.5.100.04 | Fixed In: |
In a T-Server multi-site environment where a call may be
routed or transferred several times between different T-Servers, the T-Server where a previous
instance of the call is still active may not preserve the Connection ID
of the call when it arrives back at this T-Server. The original Connection ID is reported
in the FirstTransferConnID
attribute and can be used by T-Server, instead
of the ConnID
attribute when backward compatibility mode is enabled. In
addition, the LastTransferConnID
attribute contains the Connection ID
of the call from the previous location.
Found In: 6.5.100.04 | 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: 8.1.500.02 as of June 18, 2021 |
Red Hat Enterprise Linux 5
Discontinued As Of: 8.1.010.02 |
Red Hat Enterprise Linux 3.0
Discontinued As Of: 8.1.000.09 |
Solaris 8
Discontinued As Of: 8.1.000.09 |
Tru64 UNIX
Discontinued As Of: 8.1.000.09 |
Information in this section is included for international customers.
There are no known internationalization issues for this product.
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 NEC NEAX/APEX Deployment Guide contains detailed reference information for the Genesys Framework 8.1 T-Server for NEC NEAX/APEX, including configuration options and specific functionality.
The Framework 8.1 Deployment Guide helps you configure, install, start, and stop Framework components.
The Voice Platform SDK 8.x .NET (or Java) API Reference and the Genesys Events and Models Reference Manual and contains the T-Library API, information on TEvents, and an extensive collection of call models.
The Genesys Migration Guide contains a documented migration strategy for each software release. Please refer to the applicable portion of this guide or contact Genesys Technical Support for additional information.
The Genesys Supported Operating Environment Reference Manual 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.