Release Note

Contents

Introduction

As of February 1, 2012, Genesys is no longer an affiliate of Alcatel-Lucent; any indication of such affiliation within Genesys products or packaging is no longer applicable. Please see the Genesys website at http://www.genesyslab.com for more details.

This release note applies to all 8.0 releases of T-Server for Avaya Communication Manager.

• Links in the Contents section enable you to access information regarding a specific release. Releases are listed by version number rather than in date order. For this reason, a recent release may be listed after earlier releases, if the version number is lower. Except when otherwise noted in the information for a specific release, each release includes all of the features and corrections that were introduced for the applicable operating system at earlier dates, regardless of the version numbering.
• The Release Number table lists the supported operating systems for each release at a high level. For more detailed information, see the Genesys Supported Operating Environment Reference Manual.
• The Known Issues and Recommendations section is a cumulative list. It includes information on when individual items were found and, if applicable, corrected.
• The Corrections and Modifications section for each release may list additional issues that were corrected without first being documented as Known Issues.
• The Discontinued Support section is cumulative. It lists functionality that is no longer supported and the release number of the version in which support was discontinued.
• You can find information about changes and corrections to functionality common to all T-Servers in the release note for T-Server Common Part release 8.0.x.
• Your T-Server's name correlates generally with the name of the switch you intend to use, but vendor switch names often change. For full details on the name(s) of the switch intended for use with this T-Server, see the Genesys Supported Media Interfaces Reference Manual.

Use of Third-Party Software

Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize functionality of commercial or non-commercial third parties. For specific information on any third-party software used in this product, see the Read Me.

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.0.101.20. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

This is a hot fix for this product. This release does not contain any new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

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

HA T-Server no longer becomes unstable in an environment where a new application object is created with a connection to the running HA T-Server. This issue was applicable only to HA deployments, and could occur in any of the following scenarios:

• If an application created in the manner above was deleted from the configuration environment while HA T-Server was running.
• If a connection to HA T-Server was deleted from the application created in the manner above, while HA T-Server in question was running.
• If one of the HA T-Servers was stopped via Solution Control Server (SCS) after the client's application and its connections were created dynamically.

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.0.101.16. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

This is a hot fix for this product. This release does not contain any new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

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

T-Server now correctly applies option values configured in the log-filter section (hide-first, hide-last, unhide-first, unhide-last) to hide sensitive user data in the T-Server log. Previously, T-Server could become unstable while processing those option values. (ER# 279197231, 279186869)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.0.101.12. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

This is a hot fix for this product. This release does not contain any new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now corrects a problem where a redirected call from one VDN to another VDN, within a time period of less than 500 milliseconds, caused T-Server to generate T-Events which were inconsistent with the associated call on the physical switch. (ER# 261650861)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.0.101.12. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

This is a hot fix for this product. This release does not contain any new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

This release of T-Server incorporates TSCP version 8.0.101.12 that corrects the following issue:

Primary and backup T-Servers now run correctly according to their roles if, during a switchover, the primary and backup T-Servers get disconnected, and the connection is then restored for both. Previously in this scenario, the backup T-Server incorrectly notified its clients that its role changed to primary while it remained running in backup mode.

(ER# 268653432)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.0.101.09. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

This is a hot fix for this product. This release does not contain any new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now corrects a problem where an EventError (timeout), in response to a RequestAgentLogout, was incorrectly generated in the following scenario:

1. A DN that is not in Configuration Manager is dynamically registered.
2. A login is requested for the DN.
3. The DN is unregistered.
4. The DN is registered.
5. A RequestAgentLogout request is made for the DN.

(ER# 265885591)

T-Server no longer incorrectly reports an EventError (timeout) when the AttributeThisQueue attribute is left blank (empty) in the RequestAgentLogout request. Previously, T-Server distributed an EventError (timeout) after both the switch and T-Server (through EventQueueLogout/EventAgentLogout) reported the extension as logged out. (ER# 262614467)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.0.101.06. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

This is a hot fix for this product. This release does not contain any new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

This release of T-Server incorporates TSCP version 8.0.101.06 that corrects the following issue:

T-Server now repeatedly attempts to check out SDN licenses after restoring connection to the License Manager. Previously, after an unsuccessful attempt to check out SDN licenses again, T-Server denied the new DN registration because of a license violation.

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.0.101.03. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

There are no restrictions for this release. This release contains the following new features or functionality:

• T-Server now supports the Call Release Tracking feature, which provides information about which party initiated the release of a call. This feature can be valuable for different applications to provide historical and real-time call reporting. The following restrictions/limitations apply to this feature:

  • Event minimization on Avaya’s link subsystem should not be enabled.
  • Manual or external release identification scenarios are restricted to two-party calls where at least one party is a monitored extension, and the other party is either a monitored extension or is an unmonitored (possibly, external) extension.

  The Call Release Tracking is configured by using the configuration option releasing-party-report. This configuration option enables or disables the reporting of the ReleasingParty key in the Extensions attribute of the EventReleased and EventAbandoned events, and also enables or disables the AttributeCtrlParty reporting in EventCallPartyDeleted and EventCallDeleted events.

  Note: A client must subscribe for call-monitoring events by issuing an TStartCallMonitoring request in order to receive EventCallPartyDeleted and EventCallDeleted messages.

  releasing-party-report
  Default Value: false
  Valid Values: true, false
  Changes Take Effect: Immediately

  This configuration option specifies whether T-Server reports the ReleasingParty key in the AttributeExtensions of EventReleased and EventAbandoned events to indicate which party initiated the call release. Additionally, this option specifies whether T-Server reports AttributeCtrlParty in the EventCallPartyDeleted and EventCallDeleted events to indicate which party initiated the call release (when call monitoring is enabled in T-Server). This option can be configured only in the TServer section of the T-Server Application object. If this configuration option is set to true, the value assigned to AttributeCtrlParty will contain the DN of the party that initiated the release, and the ReleasingParty key will contain one of the following values:

  • 1 Local—the call is released because AttributeThisDN in EventReleased requested a release operation.
  • 2 Remote—the call is released because the other party (which is remote to AttributeThisDN) in EventReleased or EventAbandoned requested a release operation.
  • 3 Unknown—the call is released, but T-Server cannot determine the release initiator.

  If this configuration option is set to false, reporting is disabled.

  Note: The ReleasingParty key is reported on EventReleased and EventAbandoned when AttributeCallState is CallStateOK.

(ER# 258876254)

Corrections and Modifications

This release does not include any corrections and modifications.

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.0.101.03. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

There are no restrictions for this release. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now corrects a problem with TSingleStepConference requests. Previously, T-Server did not include the attached data in TSingleStepConference requests. (ER# 256502231)

When ISCC/COF and ISCC Transaction Monitoring are in effect, T-Server now correctly destroys Target COF transactions and no longer allocates excessive memory while processing ISCC/COF scenarios. (ER# 255575221)

T-Server now corrects a problem which can prevent T-Server from unregistering a DN through the Computer Telephony Integration (CTI) link. This problem is specific to cases where a DN is removed from Configuration Manager with active clients registered on that DN. Previously, T-Server did not unregister the DN through the CTI-link following the last T-Server client request to unregister the DN. (ER# 254888210)

T-Server now corrects a problem with login event reports. Previously, T-Server could inadvertently associate a login event report, resulting from a previous request, to a new unrelated TAgentLogin request. (ER# 253875801)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.0.101.01. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

This is a hot fix for this product. This section describes new features that were introduced in this release:

• T-Server now supports the mapping of ISDN cause codes 18, 19, and 20 (coding standard 0) to CallStateNoAnswer.

• T-Server now includes the raw cause code and coding standard that are provided by the link on the third-party call ended notification in extensions on the related TEvent:

  Key	Value Integer	Description
  CauseCS	0 or 3	The value represents the coding standard 0 or the coding standard 3 used to interpret the provided cause code.
  CauseCode	1-127	The value represents the raw cause code provided by the link.

• T-Server now adds support for the configurable mapping of cause codes to the CallState attribute for predictive dialing scenarios. The mapping of the cause code to the CallState attribute is achieved through a set of semi-hidden options which should be configured in Configuration Manager under a section called cause-to-callstate-map, which is located on the Options tab of the Avaya Communication Manager T-Server application.

  All parameters in this section should take the form cs‹CODING_STANDARD›-‹CAUSE_CODE›:

  • CODING_STANDARD represents the coding standard for a specific cause code (either 0 or 3).
  • CAUSE_CODE represents the cause code in a particular coding standard (starting at 1 and continuing to a maximum of 127).

  Examples of option names:

  • cs0-1 (option name for cause code 1 in coding standard 0)
  • cs0-18 (option name for cause code 18 in coding standard 0)
  • cs3-19 (option name for cause code 19 in coding standard 3)

  Note: There are a total of 127 options in coding standard 0 and a total of 127 options in coding standard 3.

  The value of each option must be an integer that represents a CallState attribute that is related to predictive dialing scenarios. The following is a list of supported values:

  Value	Description
  0	CallStateOk
  3	CallStateGeneralError
  4	CallStateSystemError
  6	CallStateBusy
  7	CallStateNoAnswer
  8	CallStateSitDetected
  9	CallStateAnsweringMachineDetected
  10	CallStateAllTrunksBusy
  11	CallStateSitInvalidnum
  12	CallStateSitVacant
  13	CallStateSitIntercept
  14	CallStateSitUnknown
  15	CallStateSitNocircuit
  16	CallStateSitReorder
  17	CallStateFaxDetected
  18	CallStateQueueFull
  26	CallStateDropped

  It is important to ensure that any configured mappings to the CallState attribute do not inadvertently impact Outbound Contact Server functionality. For example, use of CallStateBusy describes scenarios where the dialed endpoint is found to be busy and should not be used in the mappings of an unrelated cause code.

  The current default mapping of the ISDN cause code to the CallState attribute that is used by Avaya Communication Manager T-Server is as follows:

  Coding Standard 0:	Cause Code:
  NORMAL (0x10)	CallStateOk
  UNSPECIFIED (0x7F)	CallStateOk
  USER_BUSY (0x11)	CallStateBusy
  INVLDNUM (0x1C)	CallStateSitInvalidnum
  UNASSIGNED_NUM (0x01)	CallStateSitVacant
  NUM_CHANGED (0x16)	CallStateSitIntercept
  NO_CIRCUIT (0x22)	CallStateSitNocircuit
  NETCONJ (0x2A)	CallStateSitReorder
  NORMAL_UNSPECIF (0x1F)	CallStateSitUnknown
  BEARER_CAP_UNAVAIL (0x3A)	CallStateFaxDetected
  NOUSE_RESP (0x12)	CallStateNoAnswer
  NO_ANSWER_FROM_USER (0x13)	CallStateNoAnswer
  SUBSCRIBER_ABSENT (0x14)	CallStateNoAnswer

  Coding Standard 3:	Cause Code:
  COVER_BUSY (0x1A)	CallStateOk
  COV_DONT_ANS (0x1C)	CallStateOk
  VOICE_ENERGY_ANSWER (0x12)	CallStateOk
  SERV_UNAVIL (0x3F)	CallStateBusy
  CALLID_TERM (0x56)	CallStateDropped
  NO_ANSWER (0x13)	CallStateNoAnswer
  NO_TRUNKS (0x14)	CallStateAllTrunksBusy
  QUEFULL (0x16)	CallStateQueueFull
  ANSWERING_MACHINE (0x18)	CallStateAnsweringMachineDetected
  RESUNAVL (0x28)	CallStateSystemError
  NO_CLASSIFIERS (0x15)	CallStateSystemError
  NETWORK_OUT_OF_ORDER (0x26)	CallStateSystemError

(ER# 253786995)

Corrections and Modifications

This release does not include any corrections and modifications.

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.0.101.01. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

There are no restrictions for this release. This section describes new features that were introduced in the initial 8.0.1 release of T-Server for Avaya Communication Manager.

• T-Server now supports Call Overflow (COF) interoperability between T-Server for Avaya Communication Manager and T-Server for Avaya TSAPI.

• Flexible call matching has been enhanced to resolve race conditions that previously could interfere with Inter Server Call Control/Call Overflow (ISCC/COF).

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server no longer ignores connected event reports received from the switch in certain call flows that involve external parties and Vector Directory Numbers (VDN). Previously, this issue may have prevented calls from being properly established in T-Server. (ER# 242035717)

T-Server now verifies that any delayed events distributed on a prior Connection ID are properly updated to the new Connection ID. Previously, in some call scenarios involving multi-site conferencing through ISCC to an ACD Queue at another site, it was possible for EventQueued events to be distributed on the wrong (consultation) Connection ID due to delayed processing of EventQueued events; thus creating a stuck call. (ER# 240399203)

T-Server corrects a potential problem in predictive dialing scenarios when the match-calls-by option is set to uui. Previously, T-Server may have incorrectly matched a predictive call with another call (which makes use of the same predictive call UU_DATA key) causing incorrect TEvents, and potentially stuck calls. (ER# 243560331)

T-Server corrects a problem with the predict-agent-work-mode option. Previously, T-Server did not automatically set the agent state to NotReady-Aux in switch forwarding scenarios when this option was set to true. (ER# 244301000)

T-Server now detects scenarios where the switch performs a quick reuse of a CallID by verifying that the previous call is removed from memory before processing the initiated event report. Previously, this scenario caused T-Server to ignore the initiated event report for a new call and could incorrectly show a DN as idle. (ER# 242700447)

T-Server corrects an issue where digits of one (1) character in length were not considered as valid when received from the switch. Previously, this may have impacted the propagation of important event attributes such as ANI. (ER# 246700841)

T-Server now corrects a potential problem that can result in a protocol error being sent from the switch in response to a request (for example a TRouteCall request). Previously, this response was the result of an encoding error, which occurred in cases where the requests carried a large amount of UU_DATA resulting in the incorrect encoding of the message length. (ER# 250028357)

This release incorporates TSCP release version 8.0.101.01 that corrects a memory growth issue. (ER# 249381519)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.0.001.17. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

There are no restrictions for this release. This release contains the following new features or functionality:

• T-Server now supports switch partitioning so that multiple T-Servers can now connect to the same physical switch.

• T-Server now supports the new option enable-dmcc, in order to selectively enable or disable DMCC support for specific DNs. This option is set in the TServer section on the Annex tab of a DN configuration object in Configuration Manager.

  enable-dmcc
  Default Value: true
  Valid Values: true, false
  Changes Take Effect: during next registration

  When this option is set to true, T-Server registers this DN over the DMCC link. Previously, during switchover to the primary T-Server, the new primary T-Server could invoke a registration on a DMCC-enabled DN when the DMCC link was not responding. This could inadvertently cause delays on the primary CTI link. Now T-Server ensures that DN registration on the DMCC link only takes place if the DMCC link is connected.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now supports the completion of mute transfers on EventNetworkReached. Previously in some trunk configurations, T-Server did not receive the alerting event report for outbound calls, which impacted scenarios involving mute transfers by preventing the completion of a transfer.

Starting with this release, the default value of option ignore-cut-thru-consult is changed from true to false. This option's default value change is necessary to ensure that in all default configurations the EventNetworkReached event is generated, even in cases of missing alerting event reports.

ignore-cut-thru-consult
Default Value: false
Valid Values: false, true
Changes Take Effect: Immediately

This option is used to force T-Server to ignore the CutThrough switch event for consult calls.

Note: Use this option only when requested by Genesys Technical Support.

(ER# 237080176)

T-Server now correctly associates multiple calls by using the Universal Call ID (UCID). Previously, in cases where the match-calls-by option is set to UCID, T-Server could incorrectly adjust the internal call ID for calls sent to the VDN domain type with existing calls stored in the memory that match the UCID. (ER# 236070781)

T-Server now filters held and retrieved messages from the link that contain a connected number representing a valid queue. Previously, when the link sent a hold or retrieve message with the connected number set to a queue, T-Server would generate invalid TEvent sequences that might not represent the true call state. (ER# 235210574)

T-Server now correctly generates the EventLinkConnected event in startup scenarios where DNs are removed from Configuration Manager when Flow Control is enabled. Previously in this scenario, T-Server could fail to generate the event. (ER# 234636830)

The option vdn-as-other-queue adds the AttributeOtherQueue attribute to supported call events. Support of the AttributeOtherQueue attribute was added for compatibility with the 7.2 T-Server release.

vdn-as-other-queue
Default Value: false
Valid Values: false, true
Changes Take Effect: Immediately

Note: Use this option only when requested by Genesys Technical Support.

(ER# 234375491)

T-Server now improves the call recovery process during startup or CTI link reconnect. Previously, due to limited information provided in and at the time of receiving snapshot call information (during DN registration), it was possible that T-Server’s generated events were not always synchronized with the real switch state at link connect time. (ER# 227510691)

T-Server now corrects a problem with a missing ThirdPartyDN attribute on an EventReleased event in response to a TRedirectCall request. Previously, in some cases where a call was redirected off the switch, it was possible that a ThirdPartyDN attribute would not be propagated on the corresponding EventReleased event. (ER# 225713771)

T-Server now corrects a problem where it could briefly take a DN out of service. This behavior is related to scenarios involving DNs that are manually registered (not part of Configuration Manager) and then later added to Configuration Manager with the same AddressType. (ER# 219740672)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.0.001.15. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

There are no restrictions for this release. This section describes new features that were introduced in the initial 8.0 release of T-Server for Avaya Communication Manager.

• T-Server now supports new log events to notify about failed routing attempts. Also, T-Server now supports a new log event to notify about failed ISCC transactions.

• T-Server now supports a new option to control what value should be used for DNIS on Offered and Route requests when Interflow information is available.

• T-Server now supports Real Time Agent State reporting using Device, Media and Call Control (DMCC).

• T-Server now supports ESS which provides enhanced availability and survivability for T-Server for Avaya Communication Manager.

• T-Server now supports the new option use-link-bandwidth-backup, introduced in version 7.6.007.00 to control the number of messages that can be sent to a link within a one second period when T-Server is in backup mode.

  use-link-bandwidth-backup
  Default Value: 0
  Valid Values: 0-3000 Changes Take Effect: Immediately

  Controls the number of messages that can be sent to the link within a one second period when T-Server is in backup mode. This option allows the backup T-Server to use less bandwidth preventing the combined primary and backup T-Servers from drawing too much bandwidth from the switch. A value of 0 (zero) means that the use-link-bandwidth option will be used instead.

  Note: The maximum value for the use-link-bandwidth option has been increased to 3000.

• T-Server now supports link bandwidth reporting. Two new log events have been added, to handle alarm conditions that are triggered when the average link bandwidth exceeds or drops below a predefined threshold. The new log events are as follows:
  
  20009 | STANDARD | Link bandwidth: [requests] requests per second exceeded alarm threshold [setting] requests per second on CTI link ID [id].

20010 | STANDARD | Link bandwidth: [requests] requests per second dropped below alarm threshold [setting] requests per second on CTI link ID [id]
  

• T-Server now supports configurations of 10000 or more DNs.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now correctly generates EventRinging and EventAbandoned messages for an agent DN, in the event that a call was abandoned quickly after distribution to the agent. Previously, T-Server sometimes failed to properly distribute EventRinging and EventAbandoned in this scenario. (ER# 222329651)

T-Server now sends an EventPartyDeleted message to all parties in a conference when any member of the conference leaves the call. Previously in some service-observing call flows, T-Server was unable to correctly count the number of call legs after a merge operation, in cases where either an established observer or an established bridged party was involved in the consultation call. With improved party-counting logic, T-Server is now able to tell when a party is in or out of the conference, in all call models. (ER# 187100636)

T-Server now releases all inactive parties after re-connecting to the CTI link. Previously, calls that were active before the link disconnected sometimes persisted in memory after the link was re-established, resulting in stuck calls (as the calls no longer existed on the PBX). (ER# 216381181)

For backwards compatibility with T-Server 7.2, release 8.0 introduces a new semi-hidden option, correct-other-dn, which is used to trim the OtherDN attribute in initiating call requests. To enable correct-other-dn, set the value to true (default is false) in the TServer section. (ER# 233902654)

T-Server now correctly processes multiple merge messages in conference scenarios. Previously, problems in processing these messages could sometimes result in incorrect party ID mapping, which could impact conference scenarios that required the party ID in certain CTI switch requests. For example, RequestDeleteFromConference. (ER# 221475452)

T-Server no longer inadvertently crashes in predictive dialing scenarios when the match-calls-by option is set to uui. This problem is corrected by removing direct caching of the call object in relation to the user-to-user interface (UUI) reference. (ER# 231825270)

T-Server now uses the correct value in the OtherDN attribute when using the VDN return-destination feature. Previously, when a call returning to the VDN was queued and released, T-Server might have used an incorrect value for the OtherDN in corresponding TEvents. (ER# 219913694)

T-Server performance on AIX 5.3 can be improved by including the -conn-provider pollset parameter in the T-Server command line. This improvement works only on AIX 5.3. Attempts to use it on other operating systems or versions will fail. (ER# 209026208)

T-Server now correctly specifies a CallState of 1 (CallStateTransferred) instead of a Call State of 5 (CallStateRemoteRelease) in EventPartyChanged events for transfer scenarios that involve a bridged party controller. (ER# 214044531)

T-Server now correctly disables query-agent-work-mode on-timer queries when the use-link-bandwidth option is set to 0. Previously, T-Server was sometimes unable to disable on-timer queries in this configuration.

Note: Starting with this version, T-Server no longer supports use-link-bandwidth-startup as a valid option.

(ER# 193493697)

T-Server now supports the retry-on-proterr option in cases where T-Server lacks sufficient bandwidth to send abort (unregister) messages. Previously, T-Server could inadvertently cancel this unregister request, resulting in incorrect re-register handling. (ER# 227370793)

Top of Page

Known Issues and Recommendations

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

When the call release tracking feature is enabled (see configuration option releasing-party-report) and T-Server is reporting call events, T-Server only reports AttributeCtrlParty in EventCallPartyDeleted for the releasing party controller. This attribute will be missing from EventCallPartyDeleted for the noncontroller parties dropping from the call. (ER# 260578641)

In scenarios in which T-Server is running with an active Device, Media, and Call Control API (DMCC) link, there is a potential race condition that can occur if the DMCC link and the primary CTI-link become out of sync. This race condition can potentially cause duplications of Agent level events during login, when login is followed by an immediate agent state change request. (ER# 259773691)

When making a conference call from a principal or bridged DN (in a bridging call flow), the resulting conference in T-Server will not result in the bridging DN being dropped from the call. This may create the impression that the bridging party is still a member of the call when in fact it may have been dropped by the switch. (ER# 227237951)

In scenarios where a call is redirected back to the same queue within a short period of time (approximately 2.5 seconds) from which it had previously passed, the EventQueued and EventDiverted event sequences may be missing when the call diverts from the queue. This means that T-Server may only distribute one set of queued and diverted messages for this call flow. (ER# 225250782)

If there are conference members in different partitions, party events may not be reported correctly for single-step conferences. For correct event reporting on partitioned environments, use two-step conferences. (ER# 238262936, 238625235)

T-Server temporarily takes a DN out-of-service in the following scenario:

1. A client registers the DN.
2. The DN is not initially configured in the Management Layer.
3. The DN is subsequently added to the Management Layer.

If T-Server receives an unsolicited hold or retrieved message, and the connected number represents a valid queue, T-Server sometimes generates invalid TEvent sequences that do not represent the true call state. (ER# 235210574)

In some call-coverage scenarios, T-Server sometimes interprets redirect notifications from the principal station as a drop of both the principal and covering stations, resulting in incorrect TEvent generation. (ER# 214050931, 229367441)

There is a slight behavior change in the generation of T-Events for agent logout between 7.2 and 7.5 T-Server. Starting with 7.5, T-Server will report the reference ID, and any associated reasons, in the EventQueueLogout message, rather than EventAgentLogout. (ER# 221411083)

Some call parking scenarios may result in the loss of call visibility in T-Server, causing possible call deletion when calls are parked, as well as new call creation (and deletion of UserData) when calls are unparked. (ER# 193692091)

During the registration phase of the startup process, T-Server can sometimes associate the wrong state for an active party on a call, which can lead to an incorrect TEvent sequence that does not represent the true call state. This problem is specific to unconnected internal parties. (ER# 235413481 )

When T-Server starts, if a phone is already in a dialing state, it will be incorrectly reported by T-Server as in Established state. This problem only occurs on startup and is temporary. It will be resolved when the dialing DN is either released or established. (ER# 150380481)

When a backup T-Server becomes primary, it will send agent status queries in the background for all agents that are logged in.

Top of Page

Discontinued Support

This section documents features that are no longer supported in this software. This cumulative list is in release-number order with the most recently discontinued features at the top of the list.

The HP-UX 11.00 operating system is no longer supported.

The Windows 2000 operating system is no longer supported.

The Solaris 7 operating system is no longer supported.

Top of Page

Internationalization

Information in this section is included for international customers.

There are no known internationalization issues for this product.

Top of Page

Additional Information

Additional information on Genesys Telecommunications Laboratories, Inc. is available on our Technical Support website. The following documentation also contains information about this software.

• Framework 8.0 T-Server for Avaya Communication Manager Deployment Guide contains detailed reference information for the Genesys Framework 8.0 T-Server for Avaya Communication Manager including configuration options and specific functionality.

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

• The Voice Platform SDK 8.0 .NET (or Java) API Reference and the Genesys Events and Models Reference Manual and contains the T-Library API, information on TEvents, and an extensive collection of call models.

• Genesys Migration Guide contains a documented migration strategy for each software release. Please refer to the applicable portion of this guide or contact Genesys Technical Support for additional information.

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

Product documentation is provided on the Technical Support website, the Genesys Documentation wiki, and the Documentation Library DVD (produced monthly) or the Developer Documentation CD.

Note: For the DVD/CD, the New Documents on this DVD/CD page indicates the production date for that disc. Due to disc production schedules, documentation on the Technical Support website may be more up-to-date than what is available on disc immediately after a product is released or updated. To determine the version of a document, check the version number that is located on the second page in PDFs or on the About This File topic in Help files.

Top of Page