Release Number | AIX | HP-UX | Linux | Solaris | Tru64 UNIX | Windows |
---|---|---|---|---|---|---|
7.6.002.01 [08/18/10]–Hot Fix | X | X | X | X | ||
7.6.002.00 [03/17/08]–General | X | X | X | X | X | X |
7.6.001.03 [01/30/08]–General | X | X | X | X | X | X |
As of February 1, 2012, Genesys is no longer an affiliate of Alcatel-Lucent; any indication of such affiliation within Genesys products or packaging is no longer applicable. Please see the Genesys website at http://www.genesyslab.com for more details.
This release note applies to all 7.6 releases of T-Server for Aspect ACD.
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
Corrections and Modifications
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 section describes new features that were introduced in this release:
This release includes the following corrections and modifications:
This release has been built with the latest libraries. (ER# 256969712)
T-Server now sends the EventError
message Invalid origination address
when a client requests to register a DN with more than 100 characters in the name. Previously, T-Server sometimes terminated when processing such a request. (ER# 256752983)
T-Server now correctly handles invalid DNs of type Extension
when the configuration option poll-dn-tout
is set to a value other than zero (0
).
Previously, T-Server sometimes terminated if a DN of type Extension
was configured with a value not in the range of 1-3000
and the configuration option poll-dn-tout
had a value other than zero (0
).
(ER# 248298176)
Supported Operating Systems
New in This Release
Corrections and Modifications
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.
This release has been built with the latest libraries. (ER# 178717087)
Supported Operating Systems
New in This Release
Corrections and Modifications
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 section describes new features that were introduced in the initial 7.6 release of T-Server for Aspect ACD:
CPNDigits
has been implemented.route-uses-ctimr
now has default value false,
which disables forced use of the CTIMR type of routing.
station-svc-evt
now has default value no
, which disables generation of EventDNOutOfService/EventDNBackInService
.There are no corrections and modifications in this initial 7.6 release.
This section provides the latest information on known issues and recommendations associated with this product.
Deployment Guide erratum
In the T-Server Functionality table, the following footnote should appear for TRouteType Reject
:
"From 7.6, subtype Reject
no longer requires the SupervisedRoute = 1
extension to clear the call, because T-Server intelligently clears the call in the best manner for the switch."
Found In: 7.6 | Fixed In: |
When installing T-Server on a 64-bit UNIX host, the 32-bit executable can only be installed on the following platforms:
(ER# 258302891)
Found In: 7.6.002.01 | Fixed In: |
T-Server creates a secondary thread during connection to Contact Server through the API library, which synchronously connects to the Contact Server to prevent a communication blockage with T-Server clients. This secondary thread exists only until a connection to the Contact Server is established. In the rare circumstances when logging is used in both the main T-Server thread and in the secondary thread, T-Server may stop responding. (ER# 258096348)
Found In: 7.6.002.01 | Fixed In: |
In release 9.1.1 and higher of the Aspect ACD,
the default configuration parameters for consult calls have
been changed.Previously, the default maintenance flag #9
was set to
on
(checked). From release 9.1.1, the default
setting of maintenance flag #9
is off
(unchecked).
With the 9.1.1+ default setting (off
) it may be necessary to press a
phoneset key at the end of a consult call in order to come out of permanent
ACW, or before being able to continue.
Please note that this parameter can normally be changed only by Aspect Engineering personnel. (ER# 128670380)
Found In: Aspect ACD 9.1.1 | Fixed In: |
Blind transfer, mute transfer, redirect, divert, forwarding and internal single-step transfer are not supported. Consultation calls to Routing Point (Inbound/Outbound only), and single-step transfer (Inbound/Outbound only) have limited support. (ER# 25000141)
Found In: Unspecified | Fixed In: |
Alerting calls cannot be released in the Aspect switch. (ER# 35449788)
Found In: Aspect 9.1 CS 5.2 | Fixed In: |
DTMF cannot be sent from a conference controller. (ER# 107848526)
Found In: Unspecified | Fixed In: |
Aspect Call Center responds to DN Status request message ESR
with ESRR
status value X = Busy/Other
after a physical trunk disconnect. As ESRR
status value X
is also used for other unavailable states, such as dialing or
releasing, T-Server will not generate EventDNOutOfService
to clients. (ER# 16897903)
Found In: 7.1 | Fixed In: |
On Aspect 9.x ACD, when one analog phone calls another, the switch does not report anything except CDEM when the phones are placed on hook. (ER# 33227139)
Found In: Switch version 9.1 | Fixed In: |
On Aspect 9.x ACD, TAgentNotReady
when an agent is already in NotReady
state
places the agent into Ready
state. (ER# 31945167)
Found In: Switch version 9.1 | Fixed In: |
Calls via CTI from analog sets cannot be answered via CTI. (ER# 60770)
Found In: Switch version 8.4 | Fixed In: |
At startup, T-Server recognizes when trunk lines are unavailable. However, as no status change message is provided by the switch, T-Server cannot correctly reflect trunk synchronization. (ER# 97402, ER# 16897317)
Found In: 7.0.2 | Fixed In: |
Four-party conference is not supported. (ER# 107848335)
Found In: Unspecified | Fixed In: |
Parties can only be deleted from a conference call with a DN number, not with an Agent ID
. (ER# 104162626)
Found In: Unspecified | Fixed In: |
In the following scenario,
no CCEM (call connected) message is issued by the switch, and so no
EventEstablished
is issued for device 2:
cast-type = direct-notoken
, make call from device 1 (7.0 T-Server) to device 2 (7.1 T-Server).
(ER# 95680, ER# 95086)
Found In: 7.1 | Fixed In: |
In the following scenario, retrieval of the call via CTI is not possible. It must be retrieved manually.
TQueryAddress
results, the held device is reported as
0
(idle).As a workaround, T-Server clients can use Private Service 'Free the line 0
and/or 1'
.
(ER# 95703, ER# 95070)
Found In: 7.1 | Fixed In: |
When a manual consult call
is made to an invalid internal device, T-Server distributes
EventHeld
, then EventDialing
, but no other event
is generated to indicate call failure, because the switch reports abandoned.
(ER# 100889, ER# 100890).
Found In: 7.1 | Fixed In: |
In the following scenario,
T-Server does not show any call information, but displays the agent as Not
Ready
:
(ER# 101005, ER# 101010)
Found In: 7.1 | Fixed In: |
Outbound calls from analog devices to invalid numbers might be reported as busy by the switch. (ER# 92766, ER# 92765)
Found In: Switch 8.4_SP01_CM03 | Fixed In: |
When the Event Party
Propagation (EPP) feature is activated and single-step transfer is used,
Aspect T-Server does not distribute EventPartyChanged
on a remote
location. (ER# 91309, ER# 91778)
Found In: 7.0.203.06 | Fixed In: |
CTI monitoring and control of analog extensions is limited with the Aspect switch.
EventReleased
when call is released
from the originator (However, a workaround has been implemented if the call is
released by CTI from the analog set.)
(ER# 66070, ER# 88369, ER# 60764, ER# 88368)
Found In: CS 5.2, Switch R 8.4 | Fixed In: |
In two-step transfer scenarios, the switch does not allow blind transfer. As a result, the consultation call has to be answered before the transfer can be completed. (ER# 78197, ER# 78271)
Found In: PBX 8.4, CS5.2 | Fixed In: |
The switch can only single-step transfer a call if at least one of the parties in the main call is a trunk party (for example, inbound call or outbound call followed by single-step transfer to an agent). (ER# 78198, ER# 78272)
Found In: PBX 8.4, CS 5.2 | Fixed In: |
The ISCC feature with cast type direct-ani
is supported but limited. The supported scenarios
are:
No other scenario is supported. (ER# 60848)
Found In: 7.0 | 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.
The Solaris 2.6 operating system is no longer supported.
Discontinued As Of: 7.6 |
Information in this section is included for international customers. There are no known restrictions specific to international customers.
Additional information on Genesys Telecommunications Laboratories, Inc. is available on our Technical Support website. The following documentation also contains information about this software.
The Framework 7.6
T-Server for Aspect ACD Deployment Guide provides detailed
reference information for the Genesys Framework T-Server for the Aspect
ACD switch including configuration options, known limitations, and switch
functionality.
The Framework 7.6 Deployment Guide helps you configure, install, start, and stop Framework components.
Product documentation is also provided on a Documentation Library DVD, which is produced monthly. The New Documents on this DVD page on the DVD indicates the DVD production date. Because the DVD is produced monthly, documentation on the Technical Support website may be more up-to-date than that on the DVD. To verify the latest version of a document, check the version number, located on the second page in PDFs and on the "About This File" topic for Help files.