Release Number | AIX | HP-UX | Linux | Solaris | Tru64 UNIX | Windows |
---|---|---|---|---|---|---|
7.6.001.00 [08/29/08] – General | X | |||||
7.6.000.05 [03/28/08] – General | 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 Avaya INDeX.
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.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 section describes new features that were introduced in this initial 7.6 release of T-Server for Avaya INDeX:
There are no corrections or modifications in this release.
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 section describes new features that were introduced in this initial 7.6 release of T-Server for Avaya INDeX:
nas-indication
has been
introduced to enable T-Server to indicate in EventReleased
whether an overflow
has occurred as a result of No-Answer Supervision.EventReleased
rather than EventAbandoned
.correct-connid
correct-rqid
restart-period
restart-cleanup-limit
quiet-cleanup
quiet-startup
restart-cleanup-dly
TRegisterAddress
from its clients for DNs that are
not configured in Configuration Layer, and provides extended handling of
removal/addition of DNs in Configuration Layer. See the following new
configuration options in the
Deployment
Guide:
accept-dn-type
default-dn-type
dn-del-mode
acd-queue
unknown-xfer-merge-udata
.BusinessCall
. Value 1
in this extension key
indicates a business call. agent-group
. As soon as T-Server is able to
determine the agent group for a particular agent, the group is reported in all
agent-related events throughout that agent login session. See the
agent-group
configuration option in the Deployment
Guide.AttributeThirdPartyDN
in scenarios involving Divert/Overflow from
extensions/agents where the PBX provides that information.TRegisterAddress
from its clients for DNs that
are not configured in Configuration Layer, and provides extended handling of
removal/addition of DNs in Configuration Layer. See the following new
configuration options in the Deployment Guide:accept-dn-type
default-dn-type
dn-del-mode
TQueryServer
is able to provide information about
which agent work modes are supported by T-Server. These extended capabilities
are defined for agent-related events and requests and for
TRouteCall,TApplyTreatment,TCallForwardSet,TQueryAddress,TQueryCall
and
TMonitorNextCall
. AttributeCause
reported in EventReleased
for single-step and two-step transfers
in complex scenarios.OtherDN
content: In release 7.6, when a destination or
origination party is unknown, T-Server now reports that party with DN
Txxxxx
, where xxxxx
is a numeric
and corresponds to a dynamic ID.private
,business
, orwork-related
, using the new
BusinessCall
extension key. Valid values are:0
—Private call1
—Business call2
—Work-related call
There are no corrections or modifications in this release.
This section provides the latest information on known issues and recommendations associated with this product.
It is not possible to snapshot devices on the INDeX PBX. Therefore if there is a call on a device at T-Server startup, T-Server cannot report it. (ER# 175007376)
Found In: 7.6 | Fixed In: |
Four-party conferences are not supported. A maximum of three
parties can be conferenced via CTI. (ER# 178566824)
Found In: 7.6 | Fixed In: |
It is not possible to delete external parties from a conference.
(ER# 180579039)
Found In: 7.6 | Fixed In: |
The PBX supports no queries (device states, agent states and so on)
from T-Server. (ER# 176744014)
Found In: 7.6 | Fixed In: |
The PBX drops a call that has been redirected to an invalid device
or a busy device. Consequently, any chained No-Answer Supervision call that
involves either of these device states will result in the call being dropped
rather than redirected to the next target in the chain. (ER# 176744028)
Found In: 7.6 | Fixed In: |
The INDeX PBX assumes that all DNs are monitored. So, T-Server does
the same. As a result, creating a device in Configuration Manager with option
register
set to value false
will result in T-Server ignoring the value and
registering the device with the switch. Because of the way the switch behaves,
such registrations will always be successful. (ER# 177611915)
Found In: 7.6 | Fixed In: |
Avaya INDeX T-Server is only available for Windows 2000 platforms. Support for WIndows NT is removed in 7.6. (ER 84497, 176858735)
Found In: Not applicable | Fixed In: |
IP soft phones are supported. IP hard phones are not supported because of unreliable CTI reporting. (ER 84486, 87635, 176737536)
Found In: Not applicable | Fixed In: |
The switch does not permit completion of transfer or conference for a picked-up call (ER 86433).
Found In: Switch release 10.1 | Fixed In: |
When a passive T-Server is monitoring calls, it may report emulated routing as a predictive call when routing to an external destination. (ER# 181822456)
Found In: 7.6 | Fixed In: |
INDeX can complete a transfer to a busy destination and automatically camp the call on there. However if a consultation call is camped on a busy destination, the switch fails to complete transfer to the camp-on. Instead the switch releases both main and camped-on consultation calls. (ER 85633, 86361)
Found In: Switch release 10.1 | Fixed In: |
The switch sometimes makes unpredictable reactions to single-step transfer requests (ER 84235).
A workaround for this is implemented in ER 86359.
Found In: Switch release 10.1 | Fixed In: |
Occasionally a MakeCall
request is not actioned. The CTI
Integrator appears to restart for an unknown reason. (ERs 80741,
74272)
Found In: CT Integrator 2.05a6 | Fixed In: |
Disconnection and then reconnection of a previously busy trunk causes T-Server to crash. (ERs 80740, 42398)
Found In: 6.5.100 | Fixed In: |
Very occasional T-Server reconnection problems involving the Avaya dll have been observed during T-Server attempts to reconnect to the network. (ER 50701, 80737)
Found In: 7.0 | Fixed In: |
If a route/redirect request occurs too quickly this could
result in an error, as chained consult calls are not allowed on the switch, and
time needs to be given for a transfer to be completed. You can work around this
problem by setting option use-redirect
. (ER 60383, 86348)
Found In: 7.0 | Fixed In: |
As the PBX does not allow T-Server to query the Do-Not-Disturb and Forward status of devices, T-Server cannot synchronize this with the PBX at startup. The desktop application must achieve synchronization. (ERs 86007, 86005)
Found In: | Fixed In: |
TRouteCall
for a consultation call is not allowed. Transfer
must be completed before routing can take place unless use-redirect is set to
true. (ERs 86349, 86350)
Found In: Switch version 10.1 | Fixed In: |
T-Server cannot report on pilot numbers. T-Server starts reporting for calls passed through the pilot only after they have been delivered to the switch’s subscriber group. (ERs 86346, 86347)
Found In: CT Integrator, any version | 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.
Support for Windows NT is withdrawn.
Discontinued from: 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. Please consult the Deployment Guide first.
The Framework 7.6
T-Server for Avaya INDeX Deployment Guide provides detailed
reference information for the Genesys Framework T-Server for the Avaya INDeX switch including configuration options, known limitations, and switch
functionality.
The Framework 7.6 Deployment Guide helps you configure, install, start, and stop Framework components.