Release Number | AIX | HP-UX | Linux | Solaris | Tru64 UNIX | Windows |
---|---|---|---|---|---|---|
8.0.100.06 [01/18/11] – General | X | X | X | X | X | X |
8.0.001.00 [09/22/09] – 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 8.0 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 8.0.101.08. 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 Aspect ACD.
T-Server now supports Aspect ACD Data Interlink protocol version 8. (ER# 244890055)
T-Server's communication with the PBX has been modified in order to increase performance of T-Server. (ER# 244890093)
T-Server now supports a connection to Contact Server on each supported platform. There are no limitations in regards to supporting Contact Server on the following platforms:
(ER# 263186010)
T-Server now supports Call Control Table (CCT) numbers in the following range: 0
–2499
. T-Server checks the current Data Interlink protocol and appropriately updates the used CCT numbers. If T-Server discovers that the protocol number set in the PBX configuration is less than 8
, then all of the CCTs used for routing are checked against the following range: 0
–999
.
If the CCT number is outside of this range, then the default value (none
) is used as the CCT in the request.
If the Data Interlink protocol is set to the value 8
, the range of the CCT numbers that can be used is expanded and the valid values of the following configuration options will be changed:
internal-call-cct
outbound-call-cct
route-call-cct
single-step-transfer-cct
The valid values for these configuration options are:
Value | Description |
---|---|
none |
The PBX uses the default CCT for the service. |
000 –999
| This range of CCTs must be used when the Data Interlink protocol is set in the PBX configuration to a value less than 8 . |
0000 –2499 |
This range of CCTs must be used when the Data Interlink protocol is set in the PBX configuration to a value equal or greater than 8 .
|
Note: The PBX may still fail requests with a CCT value in a range of 1000
–2499
if the PBX version is less than 9.3.
(ER# 244890059)
T-Server now supports routing through the redirect service, which is available for inbound calls waiting in the CCT. This feature enables the rerouting of the call if the routing destination is not available or busy.
The following conditions must be met to use this method of routing:
The Data Interlink protocol must be set in the PBX to a value equal to or greater than 7
.
The configuration option route-call-method
must be set to the following value: CIMR-and-redir
.
The correct value of the configuration option redirect-call-cct
must be set. The value of this configuration option may also be set to a value equal to the configuration option route-call-cct
.
The inbound call has to be made to the CCT.
The following configuration option has changed due to the implementation of this feature:
route-call-method
Default Values: CIMR-or-CCR
Valid Values:
Value | Description |
---|---|
CIMR-or-CCR |
T-Server uses the Call Completion Rate (CCR) command if the route destination is an agent extension. |
CIMR-only |
Forces T-Server to route calls exclusively through the Call Control Table (CCT). |
CIMR-and-CCR |
T-Server uses the CCR command for routing, but forces the CIMR method for internal calls. |
CIMR-and-redir |
T-Server uses the RCCR command for routing, but forces the CIMR method for internal calls. |
This configuration option specifies the route-call method.
T-Server now supports the use of the configuration option redirect-call-cct
to provide the ability to specify the CCT for using routing through redirection.
redirect-call-cct
Default Value: none
Valid Values: none
, 0—2499
Value | Description |
---|---|
none |
The PBX uses the default CCT for the service. |
000—999 |
The range of CCTs that will be used when the Data Interlink protocol is set in the PBX configuration to a value less than 8 .
|
0000—2499 |
The range of CCTs that will be used when the Data Interlink protocol is set in the PBX configuration to a value equal or greater than 8 .
|
This configuration option specifies the CCT that T-Server uses for routing calls via redirection.
Note: If the configuration option is not set in the Configuration Layer, it is assigned the valid value of the internal-call-cct
configuration option.
In order to use routing through redirection, the PBX version must be greater or equal than 9.1 (this is not supported in previous versions).
(ER# 257643858)
If the Data Interlink protocol in the PBX is set to 8
, T-Server now supports the use of the configuration options orig-rtp-ext-name
and dest-rtp-ext-name
to provide information regarding Real-time Transport protocol (RTP) streams in the event that such information is reported by the PBX. As soon as the PBX reports this information, the extensions keys that are defined by the configuration options orig-rtp-ext-name
and dest-rtp-ext-name
are attached to the call.
orig-rtp-ext-name
Default Value: X-PI-RTP
Valid Value: Any valid string
Changes Take Effect: Immediately
This configuration option defines the extension name of the originating RTP extension assigned to the call and reported in the events if the PBX provides such information. The RTP extension value is reported as a string in the following format @host:port
, where:
host—the hostname of the origination RTP stream
port—port of origination RTP stream.
dest-rtp-ext-name
Default Value: X-RTP
Valid Value: Any valid string
Changes Take Effect: Immediately
This configuration option defines the extension name of the destination RTP extension assigned to a call and reported in the events if the PBX provides such information. The RTP extension value is reported as a string in the foformat @host:port
, where:
host—hostname of destination RTP stream
port—port of destination RTP stream.
(ER# 244929488)
T-Server now supports longer Agent ID
values, which is provided by the PBX, version 9.3 or higher, when the Data Interlink protocol is set to a value of 8
. T-Server provides the configuration option dial-plan-length
, which specifies the length of the Agent ID
that is currently configured in the PBX to identify the correct CCT usage in requests.
5
3
–7
This configuration option specifies the dial plan length for agents as it is set in the PBX configuration.
(ER# 244890091)
T-Server now supports the use of the configuration option kpl-loss-rate
to fully implement the keep-alive mechanism with the switch including the loss rate processing. This option is set in the link-control
section.
kpl-loss-rate
Default Values: 10
, 100
Valid Values:
Value | Description |
---|---|
0 |
KPL counter accumulates indefinitely. |
Single integer value | T-Server restarts connection to switch when a specified loss rate is exceeded. |
Two comma-separated integer values | If two values are configured, the higher value determines the rate at which the LMS message: GCTI_LST_009, 'keep-alive failing' , is generated. The lower value determines the rate at which link restart is triggered. The two values can be in any order.Note: This method of rate determination means that a static value can be configured to keep track of the connectivity between T-Server and the switch, causing a more tolerant value to absorb intermittent connectivity failures. Because the effect of value 0 is the same as infinity, it is always interpreted as the high value unless both values are 0 , in which case the result is the same as setting a single 0 .
|
This configuration option specifies how many Keep-Alive Protocol (KPL) responses are needed to cancel one KPL failure (a non-response).
Note: This configuration option does not have any effect if the kpl-tolerance
configuration option is set to 0
. In this scenario, a single KPL failure triggers a link restart, thus there is no time to calculate the loss rate.
(ER# 132757462)
This release includes the following corrections and modifications that were made between Release 7.6 or earlier releases and the initial 8.0 release:
T-Server now supports the configuration of Routing Points with the DN type RouteQueue
in Configuration layer. Previously, this configuration was not supported. (ER# 245565589)
T-Server now uses the PBX message Call Intermediate Event Message
(CINEM) to update the call information when the Call ID changes without notification. The CINEM message is generated when the Data Interlink protocol is set to a value of 7
or greater in the PBX configuration and the step New Transaction
is used in the CCT programming. Previously, CCT programming required to wrap the New Transaction
step with the Send Track Data
steps in order to provide correct reporting in T-Server. (ER# 244890087)
T-Server now reports the extensions key PBXTimeStampS
in events when the CTI events received from the PBX contains this information. Previously, this extension key was not reported.
Note: This information is provided by the PBX only when the Data Interlink protocol set to 8
in the PBX configuration. (ER# 214052699)
T-Server no longer supports the use-track-id
configuration option. A Track ID (when reported by the PBX) is now automatically assigned to the relevant call as a Network Call ID. (ER# 260261894)
T-Server now rejects the registration of a DN of more than 100 characters in length with EventError 168:'Invalid origination address'
. Previously, T-Server would fail when a client attempted to register a DN of more than 100 characters in length. (ER# 239556644)
T-Server now only rejects a routing service when in backup mode and a routing device is configured in Configuration Manager, or if it has clients registered to it. Previously, T-Server, in high-availability (HA) mode, always rejected routing whether a device was configured in Configuration Manager or not, or if it had clients registered to it. (ER# 261594054)
T-Server now prevents occasional failures when connecting to Contact Server. Previously, T-Server May have failed during the connection phase if the configuration was updated. (ER# 258096348)
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 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 Aspect ACD.
Support for call release tracking: T-Server now provides information about which party initiated the release of a call. This can be valuable for different applications to provide historical and real-time call reporting. This can be configured using the new configuration option releasing-party-report
.
Support for failed route notification: T-Server now supports alarm messages for unsuccessful routing scenarios.
Support for link bandwidth monitoring: T-Server now provides bandwidth monitoring on a CTI link and can notify the Genesys Management Layer when Configuration Layer limits are exceeded.
Improvements to T-Server logging performance have been implemented.
Support for new operating systems: The following new operating systems are supported:
This release includes the following corrections and modifications that were made between Release 7.6 or earlier releases and the initial 8.0 release:
T-Server now reacts on receiving event CCM/RINGING
if all parties in the call are trunk parties. Scenarios involving at least one station device are reported correctly by the PBX (Call Offered Event
message is generated) so they are not reacted upon in T-Server when connected to Contact Server. (ER# 221217535)
This section provides the latest information on known issues and recommendations associated with this product.
Due to hardware limitations, a Place Call Request to #8CCT
fails when using 4
digit CCTs. All transfer CCTs must be in the in the 1
-999
range. (ER# 261242111)
Found In: 8.0.100.06 | Fixed In: |
An ISCC call transfer between T-Servers that are connected to two different PBXs with different CTI link versions result in Trunk Thromboning. Aspect T-Servers report more than one EventPartyChanged
for the same DN when the transfer is completed. This scenario will only work correctly if three T-Servers are involved. (ER# 262261255)
Found In: 8.0.100.06 | Fixed In: |
The Inter Server Call Control/Call Overflow (ISCC/COF) feature is not supported if the ISCC Call OverFlow Parameter
property is set to match-ani
. (ER# 263487783)
Found In: 8.0.100.06 | Fixed In: |
Switch-specific behavior: If the configuration option route-call-method
equals CIMR-and-redir
, an outbound call cannot be diverted when transferred on to a Routing Point. (ER# 262361381)
Found In: 8.0.100.06 | Fixed In: |
If the configuration option route-call-method
, set in the TServer
section, equals CIMR-and-redir
, then the RCCR method of routing is not used for an internal or a consultation call to a Routing Point. (ER# 261997871)
Found In: 8.0.100.06 | Fixed In: |
T-Server does not correctly support a connection to the Aspect PBX where the Data Interlink protocol is set to 7
. (ER# 261069019)
Found In: 8.0.100.06 | Fixed In: |
Switch-specific behavior: If the conguration option releasing-party-report
, set in the TServer
section, equals true
, T-Server will report the ReleasingParty
information based on the information provided by the PBX. Also, if the PBX reporting is inconsistant, the T-Server reporting of the ReleasingParty
information will sometimes also be inconsistant. (ER# 260678041)
Found In: 8.0.100.00 | Fixed In: |
When an unmonitored DN is used to make a call, the PBX releases the call. To avoid this, use the Agent ID logged on to that DN to make a call, instead of the DN number. (ER# 227117446)
Found In: 8.0.001.00 | Fixed In: |
Initiating transfer of a conference call is not supported. (ER# 226425215)
Found In: 8.0.001.00 | Fixed In: |
Only the 32-bit T-Server executable can be installed on the following 64-bit UNIX operating systems.
(ER# 224639193)
Found In: 8.0.001.00 | Fixed In: 8.0.100.06 |
In the following scenario, a TAgentSetNotReady
generates two EventAgentNotReady
. One has a correct REASON
, but the other one is wrong.
walk-away-bck-compat
is set to true
.
AgentNotReady
is sent with extension
REASON=1
.
EventAgentNotReady
(this is due to switch behavior).
EventAgentNotReady
has REASON = 1000
.
EventAgentNotReady
has REASON=1
.
(ER# 228874763)
Found In: 8.0.001.00 | Fixed In: |
In the following scenario, when upgrading 7.0 primary (T-Server1) and backup (T-Server2) T-Servers to 8.0, T-Server2 does not synchronize with T-Server1:
ha-sync-dly-link-conn
set to true
.
(ER# 229884491)
Found In: 8.0.001.00 | Fixed In: |
In the following scenario, the ReleasingParty
has an incorrect value when the External DN releases the call:
releasing-party-report
option is set to true
.
CallEstablish
with external DN.
InitiateConference
with internal DN3.
EventReleased
, the Attribute Extension ReleasingParty
is 1 Local
. This is correct.
EventReleased
, the Attribute Extension ReleasingPart
is 1 Local
, which is incorrect.
(ER# 234508947)
Found In: 8.0.001.00 | 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: |
In the following scenario, retrieval of the call via CTI is not possible. It must be retrieved manually.
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: |
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: |
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: |
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: |
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: |
Alerting calls cannot be released in the Aspect switch. (ER# 35449788)
Found In: Aspect 9.1 CS 5.2 | 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: |
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: |
Calls via CTI from analog sets cannot be answered via CTI. (ER# 60770)
Found In: Switch version 8.4 | Fixed In: |
CTI monitoring and control of analog extensions is limited with the Aspect switch.
EventRinging
once the call is established.
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# 60764, ER# 88368)
Found In: Switch R 8.4, CS 5.2 | 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: |
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: |
DTMF cannot be sent from a conference controller. (ER# 107848526)
Found In: Unspecified | Fixed In: |
Four-party conference is not supported. (ER# 107848335)
Found In: Unspecified | Fixed In: |
Parties can only be deleted from conference with DN Number, not with Agent Login ID. (ER# 104162626)
Found In: Unspecified | 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.
Application Bridge connectivity is no longer supported. Please use Contact Server for Genesys integrations.
The following configuration options in the TServer
section have been removed and are no longer in use:
process-connect-subtype
use-event-bridge
primary-port
link-id
field-separator
Discontinued As Of: 8.0.100.06 |
HP-UX 11.00 is no longer supported.
Discontinued As Of: 8.0.001.00 |
Solaris 7 is no longer supported.
Discontinued As Of: 8.0.001.00 |
Windows 2000 is no longer supported.
Discontinued As Of: 8.0.001.00 |
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. Please consult the Deployment Guide first.
The Framework 8.0
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 8.0 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.