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 7.6 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 Guide.
• The Known Issues and Recommendations section is a cumulative list. It includes information on when individual items were found and, if applicable, corrected.
• The Corrections and Modifications section for each release may list additional issues that were corrected without first being documented as Known Issues.
• The Discontinued Support section is cumulative. It lists functionality that is no longer supported and the release number of the version in which support was discontinued.
• You can find information about changes and corrections to functionality common to all T-Servers in the release note for T-Server Common Part release 7.6.x.
• Your T-Server’s name correlates generally with the name of the switch you intend to use, but vendor switch names often change. For full details on the name(s) of the switch intended for use with this T-Server, see the Genesys Supported Media Interfaces Reference Manual.

Use of Third-Party Software

Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize third-party functionality. For additional information on third-party software used in this product, see the Read Me. Please contact your Customer Care representative if you have any questions.

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 7.6.008.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 now correctly handles UCID (Universal Call ID) propagation between internal call objects for transfer and conference calls. Previously, T-Server did not correctly update the original call's UCID when the switch reported a transfer or a conference call with a UCID persisting from the consultation call. This issue could result in call overflow (COF) failing in some call scenarios. (TS-10578)

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 7.6.008.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 hot fix contains the following new functionality.

• T-Server can now control the serialization of TMakePredictiveCall requests. By default, T-Server does not serialize these requests. In order for T-Server to serialize TMakePredictiveCall requests, set the restricted option serialize-predictive-calls to true.

  serialize-predictive-calls
  Default Value: false
  Valid Values: true, false
  Changes Take Effect: Immediately
  

  When set to true, T-Server serializes all TMakePredictiveCall requests for a particular DN: it will only send a subsequent request to the switch after receiving a response to the previous request. When set to false, T-Server does not serialize TMakePredictiveCall requests.

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

  (ER# 289729847)

Corrections and Modifications

This release does not include any corrections or 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 7.6.008.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 new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

This release of T-Server now supports the use of the configuration option vdn-as-other-queue to add 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

When set to true, the attribute AttributeOtherQueue is added to the supported call events. When set to false, the attribute is not added.

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

(ER# 258889161)

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 7.6.008.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 new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now resolves an HP-UX compile time issue. Previously, this issue sometimes caused T-Server to be unresponsive. (ER# 255327353)

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 7.6.008.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 new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now uses the correct Advanced Disconnect Detection Protocol (ADDP) parameters after a reconnection to the Configuration Server or the Configuration Proxy Server after a reconnection. Previously, ADDP operation might not have resumed after a switchover. (ER# 247934982)

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 7.6.008.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.

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

Corrections and Modifications

This release includes the following corrections and modifications:

This release of T-Server is built with the T-Server Common Part 7.6.008.19, which corrects the following issue:

T-Server now reads and reloads a large number of configured Access Number Codes more efficiently, without disrupting its normal operation. Previously, while reading the codes at startup and after reconnecting to Configuration Server or Configuration Proxy and the subsequent configuration data reloading, T-Server would stop processing messages from a CTI link, which could result in T-Server disconnection. (ER# 244791623)

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 7.6.008.18. 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 new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now correctly processes queue-based TQueryAddress requests. Previously, query address requests sent on behalf of a queue would fail with an EventError timeout. (ER# 240659441)

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 7.6.008.18. 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:

• In this release, the default value of the option ignore-cut-thru-consult has changed from true to false. This change is necessary to ensure that the EventNetworkReached event is generated in all default configurations, even in cases of a missing alerting event from the switch.

  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 cut-through switch event for consult calls.

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

Corrections and Modifications

This release also includes the following corrections and modifications:

T-Server now enables the completion of Mute Transfer requests on the EventNetworkReached event. Previously, in some trunk configurations, T-Server did not receive the alerting event report for outbound calls. This impacted scenarios involving Mute Transfer requests by preventing the completion of the transfer. (ER# 238453420)

The option route-thru-queue-ssfix is supported with this version of T-Server.

route-thru-queue-ssfix
Default Value: false
Valid Values: false, true
Changes Take Effect: Immediately

When this option is set to true, if a call is routed to the DN of an agent who is logged in and ready while the route-thru-queue option is enabled, the EventRouteUsed event is delayed by 500 milliseconds and the ThirdPartyDN attribute is set to the agent DN instead of the automatic call distribution (ACD) queue. This results in the EventRouteUsed event being distributed after the EventRinging event for the agent.

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

(ER# 240130473, ER# 239956489)

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 7.6.008.18. 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:

• T-Server now supports the Windows 2008 operating system.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now correctly interprets the value set in the Register field of the DN properties dialog box in Configuration Manager, as follows:

• False T-Server processes this DN locally, and never registers it on the switch.
• True T-Server always registers this DN on the switch during T-Server startup or CTI link reconnect.
• On Demand T-Server registers this DN on the switch only if a T-Server client requests that it be registered.

T-Server no longer uses External Routing Points that are reported as out of service. (ER# 233980121)

For backwards compatibility with T-Server 7.2, this release introduces a new configuration option, correct-other-dn, which is used to trim from the OtherDN attribute the last space and all subsequent characters in initiating call requests. To enable correct-other-dn, set the value to true (default is false) in the TServer section. (ER# 234620639)

T-Server now correctly reconnects to Configuration Proxy Server and receives updates of configuration data. Previously, in some scenarios, T-Server failed to reconnect to Configuration Layer components, which resulted in a loss of configuration data updates. (ER# 232872252)

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 7.6.008.14. 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 call monitoring through ASAI call control and event notification. This feature allows T-Server to keep a call in memory (up to 10 hours) after all monitored parties have been removed from the call. The following two new restricted options, call-monitoring-for-event-notification and call-monitoring-for-call-control can be used to activate this feature for event notification and call control.

  • The option description and values for call-monitoring-for-event-notification are:

    call-monitoring-for-event-notification
    Default Value: false
    Valid Values: true, false
    Changes Take Effect: Immediately

    When set to true, call monitoring through event notification will be activated. This will cause calls that pass through a monitored VDN to remain active in T-Server memory in cases where no monitored parties exist on the call. The call will persist up to the point where the call is merged, redirected, or ended by the switch.

    Note: Call monitoring with event notification will be deactivated in T-Server with a call that is merged.

  • The option description and values for call-monitoring-for-call-control are:

    call-monitoring-for-call-control
    Default Value: false
    Valid Values: true, false
    Changes Take Effect: Immediately

    When set to true, call monitoring through call control is activated. This will cause calls that have an active call control (see option follow-calls) to remain active in T-Server memory in cases where no monitored parties exist on the call. The call will persist up to the point where the call is ended by the switch or the call control is terminated.

    Note: This feature may be useful in some ISCC scenarios that require a call to persist in order for ISCC to properly propagate party events.

  (ER# 223293786)

• T-Server now supports 10-digit DNs. (ER# 220485256)

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now releases parties that are no longer on calls after a connection to a link is established. (ER# 218857931)

T-Server now sends EventPartyDeleted during conference scenarios involving an established service observer or bridged party when a conference member releases from the call. Previously in this scenario, T-Server did not correctly count the number of party legs after a merge when the consultation call had an established observer or an established bridged party. (ER# 225360442)

T-Server now correctly detects that the first leg of a call is already ended, and does not try to recreate a missing controller party on the main call in a transfer scenario where the external party hangs up at the same moment as the transfer is complete. Previously, this scenario could result in a stuck controller of the call. (ER# 226807651)

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 7.6.008.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.

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 clients can now answer an inbound call after a hook-flash transfer from an analog telephone. Previously in this scenario, T-Server would respond to a RequestAnswerCall request with an EventError of (Timeout). (ER# 191803811)

T-Server corrects a problem with the delay-logout-report option. Previously, T-Server did not properly delay logouts when this option was set to true. (ER# 190114139)

T-Server corrects a problem for Query Address requests. Previously, queries with AddressInfoType requests set to AddressInfoNumberOfIdleTrunks or AddressInfoNumberOfTrunksInUse resulted in an error. (ER# 195947211)

T-Server no longer has the potential to become unstable if a call is transferred to an unmonitored party, and then merged with another call that has only unmonitored parties. (ER# 201918454)

T-Server now properly releases an allocated CRV in cases of a Take Control timeout. Earlier versions of T-Server (7.2.x versions) do not properly release allocated CRV for timeout conditions. (ER# 182449350)

T-Server now sets the Role for the EventPartyAdded event as RoleObserver when an Observer party joins a conference. Previously, the Role was set as RoleConferenceMember. (ER# 177761490)

T-Server now correctly assigns the connection ID from the original call after a transfer is completed manually while the consultation call is held. Previously in this scenario, T-Server incorrectly used the consultation call connection ID. (ER# 180617552)

T-Server now prevents early classification of CallType based on the Originated event report when the set-call-type-on-dialing option is set to false. Previously, T-Server could prematurely set the call type on EventDialing when the set-call-type-on-dialing option was set to false. (ER# 189547026)

T-Server now ignores Connected event reports with a Connected number set to a known VDN. Previously, T-Server sometimes generated an invalid EventAbandoned event when a Connected event report was reported by a Routing Point. (ER# 201458971)

T-Server now correctly routes a call to the destination specified in the AnsMachine Extension key, provided in the TMakePredictiveCall request, when the call is answered by an answering machine. Previously, no such routing was performed. (ER# 208837172)

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 7.6.008.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 allows agent state changes on a physical telephone without interfering with the processing of CTI agent state requests (for example, a TAgentSetNotReady request). Previously, T-Server could not process CTI agent state requests in scenarios where agent state changes were made on a physical telephone at the same time that CTI agent state requests were sent. (ER# 187711334)

T-Server now correctly populates the agent DN for AttributeThirdPartyDn in EventDiverted events when a call is made to an agent through multiple ACD Queues, and the Auto Answer switch feature is active for the agent. (ER# 190431243)

T-Server no longer deletes a call if the call is on a monitored Routing Point which originates from an unmonitored party, and the originating party is placed on hold. (ER# 190227041)

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 7.6.008.07. 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 sends EventDiverted immediately when a default route (switch generated route) occurs. Previously, if a Routing Point default routed directly to an agent, EventDiverted was not sent immediately for the Routing Point. (ER# 189427281)

When a call is redirected by the switch from one VDN to another VDN, T-Server no longer sends EventDiverted and EventRouteUsed messages for the second VDN until the call is actually routed by the switch. (ER# 189241466)

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 7.6.008.07. 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:

• The use-link-bandwidth-backup option is introduced with this version of T-Server.

  use-link-bandwidth-backup
  Default Value: 0
  Valid Values: 0-999
  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.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now corrects a problem related to login audit queries at startup. Previously, login audit queries could be queued twice in flow control, which increased the time a login audit request spent in flow control. This problem could also have produced EventHardwareError messages in the log file. (ER# 187239557)

T-Server can now send a TQueryAddress request when the ThisDN attribute has an AgentID as its value. In addition, for AddressInfoAddressType, the OtherDN attribute will be populated with the extension number associated with the AgentID when an agent is logged in. Previously, TQueryAddress requests with an AgentID in the ThisDN attribute were not supported.

The following query address types can be used with the AgentID attribute:

• AddressInfoDatabaseValue
• AddressInfoAddressStatus
• AddressInfoAgentStatus
• AddressInfoAddressType
• AddressInfoCallsQuery
• AddressInfoNumberOfIdleClassifiers
• AddressInfoNumberOfClassifiersInUse

(ER# 172777949)

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 7.6.008.07. 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 always reports the OtherDN attribute in events for calls to external parties, even when the switch provides this information in only some of the CTI messages. Previously, in some switch configurations, T-Server did not report the OtherDN attribute. (ER# 182320630)

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 7.6.008.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.

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

• T-Server now supports release 5.0 of the Avaya Communication Manager using Application Enablement Services (AES) server.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server no longer becomes unstable in scenarios where a TAgentLogin request is sent with an Agent ID greater than 24 characters, or when a TSendDTMF request is sent with a DTMF digit string longer than 24 characters. (ER# 174138372)

T-Server now releases all parties in a bridged appearance to the transfer controller after the transfer is completed. Previously, parties in a bridged appearance to a DN that initiated a transfer would remain after the transfer was completed. (ER# 162803328)

T-Server now supports attached user data in TSingleStepConference request. (ER# 171238630)

T-Server now corrects a potential problem with inconsistent reporting of agent state during a call. Previously, if any agent status query was sent while the agent was on a call, and the agent was in a pending state change, T-Server would incorrectly report the non-pending agent state. (ER#  172191111)

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 7.6.008.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.

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 inbound call is classified as an internal call in scenarios where the link reports both a local type of address and a numbering plan for an external DN. Also, T-Server now considers, by default, the DN range in Configuration Manager for cases of unmonitored local DNs. Previously, in determining the call type of a call, T-Server only relied on the type of address and the numbering plan of a given number, as reported in event reports, to determine if a DN is of local type.

Note: All unmonitored local DNs should be configured in Configuration Manager to ensure proper CallType classification.

(ER# 175267055)

T-Server no longer becomes unstable if a TQueryAddress request is sent with the InfoType set to AddressInfoAddressType with an empty or missing AttributeThisQueue. (ER# 176602405)

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 7.6.008.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. There are no new features introduced in the initial 7.6 release of T-Server for Avaya Communication Manager.

Corrections and Modifications

This release includes the following corrections and modifications that were made between Release 7.5 or earlier releases and the initial 7.6 release:

This release of T-Server corrects a problem with the TACW timer by utilizing the configured TACW time in all scenarios when the query-on-timer option is disabled. Previously, if the query-on-timer-acw option referenced a time less than the time configured for the TACW, the time set for query-on-timer-acw would be used, even if the option query-on-timer was disabled. This could cause T-Server to send a query to the switch before the TACW state transition was set to Auto-In. (ER# 167747045)

T-Server now provides AttributeThisTrunk in EventEstablished when the switch includes trunk information in the Connected message. Previously, AttributeThisTrunk was not always provided in EventEstablished, even when trunk information was available in the Connected message from the switch. (ER# 131827233)

T-Server now verifies the existence of a call when the TClearCall request fails. In cases where the call does not exist, T-Server generates the correct T-Server events to properly release the call. This feature is helpful in scenarios where the link and T-Server become unsynchronized on a specific call (T-Server shows a call exists when in fact it does not). (ER# 124695760)

T-Server now properly sets AttributeThisDNRole in EventPartyAdded for the call observer model to RoleDestination (or RoleOrigination, as appropriate). Previously, T-Server incorrectly set the role in this event to RoleConferenceMember. (ER# 148333745)

T-Server now correctly performs a reverse merge where a RequestMergeCall is sent and ThisDN on the more recent (consultation) call is the held party. Previously, T-Server did not properly update the Party ID of the parties on the call, which resulted in RequestListenDisconnect failing later for this call. (ER# 160564290)

T-Server now correctly processes incoming disconnect messages in scenarios involving multiple outstanding RequestReleaseCall requests. Previously, T-Server would not send a response to the second RequestReleaseCall. (ER# 146802849)

T-Server no longer changes the agent state to Ready when a call is made to a DN in a hunt group and the agent is logged out. T-Server only performs corrective agent-state changes on agents that are logged in to the hunt group that distributes the call. (ER# 150235394)

T-Server now supports Service Observing from a trunk. Previously, if Service Observing was performed from a trunk, T-Server would not send the required EventPartyAdded message to note that Service Observing had started. These events are now sent as part of the standard Service Observing call model. (ER# 168036093)

T-Server no longer accepts agent login updates from another T-Server if it is the primary T-Server. Previously, a Solution Control Server (SCS) fault could make two T-Servers primary at the same time, resulting in one of the primary T-Servers incorrectly setting the agent login state on the other T-Server. (ER# 63604244)

Top of Page

Known Issues and Recommendations

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

Currently, the Framework 7.6 T-Server for Avaya Communication Manager Deployment Guide omits the following information about the error message 470:

T-Server code: 470
Symbolic name: TERR_PARTY_NOT_ON_CALL
Description: The party is not currently on call

When a T-Server client registers a Routing Point DN and sends a RequestReleaseCall request for a call on that Routing Point, T-Server forwards this request to the switch, possibly causing the switch to stop sending events to T-Server. RequestReleaseCall is not a valid request for a Routing Point, and should not be sent by any client. (ER# 211294251)

T-Server can become unstable if a TQueryAddress request is sent with the InfoType set to AddressInfoAddressType with an empty or missing AttributeThisQueue. (ER# 176602405)

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)

User data provided in RequestSingleStepConference will not be attached to a call. If user data must be attached to a call before a single-step conference, then RequestUpdateUserData can be used as an alternative. (ER# 171238630)

When an external party is routed to an internal unmonitored DN which is not in Configuration Manager and DTMF tones are not sent using RouteTypeOverwriteDNIS, T-Server deletes the call (no monitored parties) before playing DTMF tones. (ER# 164800188)

T-Server does not support more than 10000 DNs or Agent Logins. (ER# 102222223)

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 Solaris 2.6 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 Customer Care website. The following documentation also contains information about this software.

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

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

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

Product documentation is provided on the Customer Care website, the Genesys Documentation website, 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 Genesys Documentation website may be more up-to-date than what is available on disc immediately after a product is released or updated. To determine the version of a document, check the version number that is located on the second page in PDFs or on the About This File topic in Help files.

Top of Page