| Release Number | AIX | HP-UX | Linux | Solaris | Tru64 UNIX | Windows |
|---|---|---|---|---|---|---|
| 7.6.003.08 [10/01/10] � Hot Fix | X | X | ||||
| 7.6.003.05 [05/14/10] � Hot Fix | X | X | ||||
| 7.6.003.03 [10/17/08] � General | X | X | X | X | X | X |
| 7.6.002.00 [03/28/08] � General | X | X | X | X | X | X |
| 7.6.001.04 [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 Alcatel A4400/OXE.
Note: Genesys follows applicable third party redistribution policies to the extent that Genesys solutions utilize functionality of commercial or non-commercial third parties.
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 release contains the following new feature or functionality.
T-Server now reports AttributeCallID in call-related events that corresponds to the current Call ID reported by the PBX for a device party. Previously, T-Server reported AttributeCallID containing the Call ID assigned to the call by the PBX after the call was initially created, transferred, or conferenced. (ER# 259742496)
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 the T-Server Common Part (TSCP) release number 7.6.008.10. 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 contains no new features or functionality.
This release includes the following corrections and modifications:
Inter-T-Server messaging in multi-site scenarios where connections between servers failed has been corrected. Previously, some disconnection messaging was not being correctly generated. (ER# 226653671)
T-Server has been modified to ensure that it can correctly handle scenarios in which synchronization between two PBXs fails. (ER# 218405483 )
T-Server has been modified to ensure that switchover messaging between hot standby T-Servers and URSs is correctly synchronized. Incorrect synchronization was previously causing URS to lose calls. (ER# 227091837)
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.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 release contains the following new features and functionality:
This release includes the following corrections and modifications:
T-Server has been modified to correct a problem with Redirect scenarios if the call
was distributed from an unmonitored ACD Queue. Previously, T-Server did
not take into account whether the party on the terminal device was from an unmonitored ACD
Pilot, even if the PBX reported ACDInfo in private data. Now this data
is processed by T-Server in simple, camp-on and blind-transfer scenarios. (ER# 192134041)
T-Server has been modified to correct a problem with postponed requests. When the PBX link was slow, or there was a race condition for a requested service, T-Server was experiencing problems when it attempted to update internal data for a party object which was already deleted, where the request related to more than one party. T-Server now correctly updates internal object states. (ER# 197641373)
T-Server has been modified to correct a problem with pending requests. The order of cleanup processing has been changed to prevent this causing T-Server failure. (ER# 185748922)
T-Server has been modified to enable the reporting of Extension ReasonCode
when a local agent enters legal-guard time. Configuration option legal-guard-acw
must be set to false and option legal-guard-time must be set to a nonzero value
for this workaround to function correctly. (ER# 195963661)
A new configuration option has been implemented:
max-ext-xfer-dly00-1000EventPartyChanged on an external party when a
transfer is made over an ABC-F enhanced trunk. If there is a client request to
be executed on the external party, then T-Server will force processing of
postponed events. EventPartyChanged on transfers to such devices.
(ER# 195889569)
T-Server processing of call cleanup internal structures has been corrected to prevent access violations. These occurred when a party that was created, but was not required, was deleted. (ER# 208252921)
T-Server processing of EventAttachedDataChanged has been modified to ensure
correct subsequent reporting of EventCallDataChanged and
AttributeThirdPartyDN for use by call-monitoring or reporting clients. (ER# 204241339)
T-Server has been modified to ensure that DNIS information is correctly populated from switch events in scenarios where the DNIS field is empty. (ER# 206820886)
T-Server processing of emulated requests in HA scenarios involving transfer has been modified to prevent the backup T-Server stopping unexpectedly. (ER# 206078261)
T-Server processing of error messages from the switch has been improved to ensure that messages are reported correctly in T-Server snapshots. (ER# 210218969)
T-Server has been modified to correctly save a cause on a monitored party (a party on a predictive device) when the PBX reports the release of the remote party. T-Server will also use the cause correctly later when the predictive call is destroyed. (ER# 191392600)
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 contains no new features or functionality.
This release includes the following corrections and modifications:
T-Server has been built using the latest libraries. (ER# 178717113)
T-Server reporting has been modified to ensure that correct DNOutOf/BackInService messages are generated after a
link (re)connect. When the link is (re)established, after generating EventLinkConnected, T-Server will report
EventDNBackInService/EventDNOutOfService to all clients that are registered for the DN. If no clients are registered
for the DN, no service messages will be generated. (ER# 172204687)
T-Server has been modified to ensure release of the correct (temporary) party on completion of dialing in scenarios involving secret identity. Previously, T-Server was releasing the originating party in error. (ER# 174541125)
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-Serve for Alcatel A4400/OXE.
TSendDTMF support: In this release, T-Server now supports request TSendDTMF for internal calls. snapshot-mon-opt is set to true.This release includes the following corrections and modifications that were made between the most recent 7.5 release and the initial 7.6 release:
T-Server has been amended to prevent failure due to incorrect usage of a pointer. Previously T-Server tried to retrieve an object using a pointer from a party that had already been removed. Additional checks for invalid pointers have been added to prevent failure in such situations. (ER# 138040257)
T-Server has been modified to prevent an incorrect EventError (Service Busy) message in scenarios where an agent logged in and is defined in Local mode. T-Server incorrectly requested a snapshot for an unmonitored device and did not stop snapshot when the request failed, which resulted in T-Server rejecting some CTI requests with this error. Now T-Server will stop the snapshot if it encounters this problem. (ER# 145462997)
T-Server has been corrected to prevent re-use of Conn IDs. This was caused by the stopping of a timer responsible for cleanup of calls if T-Server lost its link connection and the timer was not restarted. The failure of the timer led to a build-up of old call and internal T-Server data. (ER# 154744498)
T-Server has been corrected to prevent incorrect generation of EventDNOutOfService messages for DNs that are in fact still in service. This was caused by a race condition when an agent login request was made while a previous logout request was still in progress and snapshot was requested. (ER# 164781531)
A race condition in T-Server, that occurs when a call routed via RSI is redirected at the same time as the origination releases, has been corrected to ensure that the call flow is reported correctly. (ER# 150481125)
A problem with incorrect EventDNOutOfService messages on GVP ports has been corrected. T-Server now sends a forced EventDNBackInService message after a DN successfully registers with the PBX and there are clients on the DN. (ER# 143471768)
T-Server handling of EventTreatmentEnd in transfers to RSI from unmonitored devices has been modified to be the same as for monitored devices. T-Server now checks for the presence of private data supervised transfer. Where this is present T-Server considers the transferred call to be a consult call and reports in the same way as for monitored devices. (ER# 164800391)
T-Server has been modified to prevent generation of an incorrect EventError (No active call) where no EventReleased has been generated. This was occurring in scenarios where a call was disconnected on a PCM port or analog device prior to the PBX acknowledgement of a T-Server InitiateTransfer request. (ER# 130465351)
This section provides the latest information on known issues and recommendations associated with this product.
When transferring from a Thomson ST2030 SIP extension, before the REFER ( SIP
transfer), the ST2030 puts both legs on hold using RE-INVITE. This means that
before the standard Genesys transfer call flow T-Server will report EventHeld
for the active consultation call and EventRetrieved for the held primary call.
(ER# 227362583)
| Found In: r9.0 h1.301.28 | Fixed In: |
When a call is camped on a SIP extension and answered so that the first call is held, neither leg can be released by CTI. The switch rejects the request. (ER# 227362592)
| Found In: r9.0 h1.301.28 | Fixed In: |
In the following scenario, on the SIP phone the consult call is dropped and
the primary is retrieved. However, the switch sends a transferred event to
T-Server, so T-Server reports the transfer and now believes that there is no
call on the SIP phone.
Note: This only occurs on an inbound call to a SIP extension. It is not a problem for internal calls. (ER# 227362598)
| Found In: r9.0 h1.301.28 | Fixed In: |
When an inbound call is made to a SIP extension and the 'reject' button is
pressed on the phone, the switch incorrectly sends EventDiverted instead of
EventConnectionCleared. This means T-Server reports EventReleased with
CallStateNoAnswer instead of EventAbandoned. (ER# 226343661)
| Found In: r9.0 h1.301.28 | Fixed In: |
When an ISDN call is made to a multiline device that then initiates a transfer to RSI, the multiline device then reconnects, but the PBX transfers the call instead of reconnecting it. (ER# 2759591)
| Found In: PBX 6.1 | Fixed In: r9.0 h1.301.28 |
Supervisor permanent monitoring fails to work in the following scenario:
15.
The ringing tone for the ACD Listening key
on the supervisor continues, even though there is no call on the key. If
the supervisor presses the ACD Listening button the ringing stops. However, any
attempts made by the supervisor to monitor the same
agent (either by CTI or manually) are rejected by the switch. (ER# 211602811)
| Found In: r9.0 h1.301.14 | Fixed In: |
The switch does not release internal calls when they are redirected to RSI. (ER# 211602841)
| Found In: r9.0 h1.301.14 | Fixed In: |
If a call is made between two pro-ACD devices while T-Server is not running, and then T-Server is started, the PBX provides no information to T-Server's snapshot query for these devices. As a consequence, the call is invisible to T-Server. (ER# 208985444)
| Found In: 7.6.003.03 | Fixed In: |
A device has immediate forwarding set to a Hunt Group. When an internal call
is redirected to the forwarding device then the redirection and forwarding is
performed correctly. However, the PBX fails to report a diverted event
for the redirecting device as a result of the successful redirection.
Instead it returns a RequestIncompatibleWithObject error, causing
an EventError in T-Server in response to the
TRedirectCall. (ER# 77051894)
| Found In: R7.1 f5.401.1 | Fixed In: R9.0 h1.301.14 |
Because of timing issues in the PBX, T-Server may send consecutive
TApplyTreatment requests too quickly and they may fail in the PBX.
Please update any client applications so that either:
EventTreatmentEnd as the indication of a
completed treatment. (ER# 133595138)| Found In: 7.5 | Fixed In: |
When reporting is required for Hunt Group members, T-Server does not support the use of parallel Hunt Groups. (ER# 107538491)
| Found In: 7.5 | Fixed In: |
When reporting is required for Hunt Group members, the Hunt Group itself must not be configured in Configuration Manager. (ER# 107387229)
| Found In: 7.5 | Fixed In: |
If a CCD agent that the PBX has placed in AfterCallWork (wrap-up) makes a call to another CCD agent that the PBX has placed in AfterCallWork, then the PBX does not send any CSTA events to T-Server for the origination of this call. Once the agents are out of AfterCallWork, the PBX reporting is correct. (ER# 103699875)
| Found In: 7.5 | Fixed In: |
T-Server will not allow TMakePredictiveCall to an internal destination. (ER#
107590864)
| Found In: Unspecified | Fixed In: |
If a transfer is made via ABC-F trunks to an agent who is logged in, and on
the PBX the option proACD forwarded to agent at logon is enabled, the switch
incorrectly distributes a Connection Cleared with cause CallForwardAlways before
the delivered event. This causes T-Server to return an EventError in response to
the transfer request, although the rest of the consult is then reporting
correctly. This problem is most noticeable with TSingleStepTransfer. (ER#
103699861)
| Found In: 7.5 | Fixed In: |
In some circumstances, T-Server can fail when the primary T-Server is removed from the network. (ER# 80915271)
| Found In: 7.2 | Fixed In: |
When a hybrid link call is made to a pilot, then mute, blind or single-step transferred to a RSI, and routed to a pilot, after the call is delivered to the agent, the PBX drops the call. (ER# 77051928)
| Found In: R7.1 f5.401.1 | Fixed In: |
The PBX reporting on a transfer to RSI is different for multiline/MEA devices
than for other devices. As a result, T-Server reports an
EventAbandoned on the RSI when the transfer from the multiline/MEA
device is completed. (ER# 77051971)
| Found In: R7.1 f5.401.1 | Fixed In: |
When a consult call is made over ABC-F to a RSI and the overflow timer is configured on the RSI, and no overflow destination is configured, the PBX should drop the consult call when the timer expires. However, the PBX actually drops the call on the RSI but not on the transferred device. If the transfer is then completed the call shows up again on the RSI. (ER# 44404261)
| Found In: 7.2 | Fixed In: |
A supervisor has permanent listening enabled on an agent. The agent receives a CCD call and redirects it (T-Server emulates the redirection). If the redirection occurs too quickly (approximately under a second after the call appears on the agent) then a timing problem can occur as a result of the mechanism used by the PBX to report supervisor monitoring.
This will result in the PBX sending conference events for the agent and the supervisor in some instances, and transferred events in other instances. This means that T-Server is not able to consistently provide the correct reporting for supervisor monitoring. (ER# 44404273)
| Found In: PX v. 7 | Fixed In: |
After a failed route, if the transferring device reconnects then the PBX does
not provide either the proper Retrieve event or a Connection
Cleared for the consult dialing leg. However, on the phone set the
consult leg is dropped, and the primary leg retrieved, which results
in T-Server being desynchronized with the phone set. (ER#
37371452)
| Found In: PBX v 7.0 | Fixed In: |
The PBX will not allow a hybrid link transfer to RSI be completed if the phone set is in DTMF state. This means that it is impossible to complete a hybrid link transfer if a collect digits treatment or an interruptible Play Announcement treatment is playing. (ER# 37371446)
| Found In: PBX v 7.0 | Fixed In: |
In PBX version 7, the PBX changes the routing reference in the routing
dialog when a transfer from an unmonitored device, or a transfer is made
over ABC-F trunks, is completed on the RSI. T-Server relies on this routing
reference to match the calls. As a result of this change T-Server can no
longer correctly report this scenario. (ER# 37252571)
| Found In: PBX v 7.0 | Fixed In: |
There is an incompatibility between A4400 T-Server behavior regarding chained
consult calls and the OCS option call_transfer_type =
two_step. On the A4400 it is not possible to chain consult calls,
therefore in that situation T-Server completes the transfer. However, when OCS
is using two-step transfer and waiting for the agent to answer, it attempts
to complete the transfer. This leads to the two applications clashing when
agent-no-answer-overflow = recall to the queue.
With a consult call on the agent, agent-no-answer-timeout
expires, and this forces T-Server to perform an emulated redirect. This involves
answering the call on the agent, T-Server completing the transfer and then
T-Server transferring the call back to the queue. However, because OCS sees an
EventReleased on the consult call (due to completion of the
transfer) it attempts to reconnect the call, assuming the call has failed.
(ER# 36839060)
| Found In: Unspecified | Fixed In: |
The PBX does not support Do Not Disturb (DND) functionality via CTI, so setting DND can only be done from the phoneset. The PBX also provides no CSTA reporting to T-Server when DND is set manually on a telset. (ER# 31943037)
| Found In: Unspecified | Fixed In: |
You cannot set forwarding to an ABC destination by a CTI request. (ER# 923721)
| Found In: PBX 6.1 | Fixed In: |
Chained consultation calls are not supported by the PBX. (ER# 14800088)
| Found In: Unspecified | Fixed In: |
Four-party and blind conferences are not supported by the PBX. (ER# 14800090, 14800092)
| Found In: Unspecified | Fixed In: |
When an emulated predictive
dial is made from a busy pilot (RSI without supervised routing enabled), the PBX
incorrectly reports the supervised transfer status to T-Server. This means that
if any timeout is configured in prd-dist-call-ans-time it cannot be
invoked. (ER# 2759501)
| Found In: PBX 6.1 | Fixed In: |
HA Synchronization is not supported before T-Server 7.2.000.05 and therefore rolling upgrades of the backup T-Server will not be successful until the primary T-Server is running at least version 7.2.000.05. (ER# 33467940).
| Found In: 7.2.000.02 | Fixed In: |
If an HA switchover is performed during an emulated supervised route and the route destination does not answer, T-Server is not able to report an EventError when it recalls the call to the Routing Point. (ER# 33389065)
| Found In: 7.2.000.02 | Fixed In: |
There is no support of emulation during switchover from 7.2 to 6.5 T-Server. An answered call is reported as a consultation call, thus creating a phantom ringing primary call. Switchover in the opposite direction does support emulation. (ER# 32974849)
| Found In: 7.2.000.02 | Fixed In: |
There is no support of emulation during switchover from 7.2 to 7.0 T-Server. An answered call is reported as a consultation call, thus creating a phantom ringing primary call. Switchover in the opposite direction does support emulation. (ER# 32974833)
| Found In: 7.2.000.02 | Fixed In: |
In the following scenario, incorrect value 2 is returned, instead of value 3.
PBX reporting does not allow you to distinguish established and dialing states. Both are reported as connected. (ER# 31665149)
| Found In: 7.2.000.02 | Fixed In: |
Genesys does not support the use of hybrid link with PBX release 5.1.2. We recommend that hybrid link is disabled with this release of the PBX. (ER# 85793, 74280)
| Found In: PBX 5.1.2 | Fixed In: |
T-Server does not issue
EventOnHook/EventOffHook for devices configured as PCM ports.
(ER# 74176)
| Found In: 7.0 | Fixed In: |
Predictive dialing in HA configurations only works with releases 7.0.1x of T-Server and higher. It is not supported in prior releases. (ER# 65036)
| Found In: 7.0.1 | Fixed In: |
For switch versions prior to 5.1,
when using predictive dialing from RSI, you must set the value of configuration
option prd-dist-call-ans-time to 0 (zero).
(ER# 74178)
| Found In: 7.0 | Fixed In: |
T-Server does not support CCD Routing Pilots (CCD Pilots with the routing flag enabled). (ER# 36422)
| Found In: All switch versions | Fixed In: |
The PBX does not send any events to T-Server when forwarding is set manually on any device. (ER# 11009)
| Found In: 5.1.011, all switch versions | Fixed In: |
When a hot-standby backup T-Server is started, the status of active emulated agents is not accurately reported. (ER# 74180)
| Found In: | Fixed In: |
The monitoring of Intrude and Call Back features is not supported. Call Park is supported from release 6.5.301.00 and switch version 4.2 and higher. (ER# 74184, 64533)
| Found In: 6.5.302 | Fixed In: |
Call scenarios and call tracking will not be accurate unless all devices taking part in call distribution are monitored. (ER# 74185)
| Found In: | Fixed In: |
If the progress of
SingleStepTransfer is interrupted by any request, T-Server may not
be able to report the scenario correctly. (ER# 74183)
| Found In: | 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 internationalization issues for this product.
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 Alcatel A4400/OXE
Deployment Guide provides detailed
reference information for the Genesys Framework T-Server for the Alcatel
A4400/OXE switch including configuration options, known limitations, and switch
functionality.
The Framework 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.