Release Note

CSTA Connector for BroadSoft BroadWorks

8.1.x

Genesys Telecommunications Laboratories, Inc. © 2013–2018

Contents

Introduction

Release Number AIX HP-UX PA HP-UX IPF Linux Solaris Windows
8.1.109.01 [11/07/18] – Update X     X X X
8.1.109.00 [12/01/17] – General X     X X X
8.1.108.02 [08/23/17] – Hot Fix       X X X
8.1.108.01 [05/10/17] – Hot Fix       X X X
8.1.108.00 [03/24/17] – General X     X X X
8.1.107.02 [12/14/16] – Hot Fix       X X X
8.1.107.01 [08/25/16] – General X     X X X
8.1.107.01 [08/25/16] – General X     X X X
8.1.106.01 [03/30/16] – Hot Fix       X   X
8.1.106.00 [12/03/15] – General X     X X X
8.1.105.00 [09/01/15] – General X     X X X
8.1.104.00 [06/25/15] – General X     X X X
8.1.103.00 [11/07/14] – General X X X X X X
8.1.102.03 [05/19/14] – Hot Fix       X X X
8.1.102.02 [04/11/14] – Hot Fix         X X
8.1.102.01 [02/20/14] – General X X X X X X
8.1.101.02 [10/11/13] – General X X X X X X
8.1.100.06 [04/09/13] – General X X X X X X

Link to 8.0 Product Release Note (Cumulative)
Known Issues and Recommendations
Discontinued Support
Internationalization
Additional Information


Introduction

This release note applies to all 8.1 releases of CSTA Connector for BroadSoft BroadWorks.

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 More Release Information/Legal Notices for T-Servers. Please contact your Customer Care representative if you have any questions.


Release Number 8.1.109.01 [11/07/18] – Update

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

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

Corrections and Modifications

This release includes the following corrections or modifications:


T-Server no longer fails to control the state of a Monitored (substituted) Agent when the Agent is logged in or out during CSTA Connector unavailability (such as a restart or network interruption). (UKTS-17629)


CSTA Connector no longer becomes unstable when properties of the host where CSTA Connector is running are changed in Genesys Configuration Database. (UKTS-17627)


Top of Page


Release Number 8.1.109.00 [12/01/17] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

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

Corrections and Modifications

This release includes the following corrections or modifications:


The connector now correctly handles timeout errors during channel creation, deleting channels created after the request to create an event has expired. (UKTS-17590)


Following BroadSoft recommendations, CSTA Connector now resets the TCP channel to Broadworks XSP server upon receiving a "500 Internal Server Error" on request to update the Event Channel. Previously, the connector took no action for such errors. (UKTS-17525)


Top of Page


Release Number 8.1.108.02 [08/23/17] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


When a call is routed from a conference to an external destination, T-Server can now delete an external party from the conference. Previously, a phantom party could be created and interfere with call control. (UKTS-17567)


CSTA Connector no longer becomes unstable when a RequestMuteTransfer is requested and the switch does not respond to the request for a very long time. CSTA Connector now handles a delayed response to a Mute Transfer request without affecting further CSTA event reporting. (UKTS-17559)


CSTA Connector logs contain a revised message: BWConnector::ParseXml: expecting more data from BWXSPServerHost:BWXSPServerPort. The previous message misleadingly referred to "incomplete XML". (UKTS-17543)


Top of Page


Release Number 8.1.108.01 [05/10/17] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


CSTA Connector no longer becomes unstable after receiving an event from BroadWorks XSP that includes a SIP URI that lacks a SIP User name (in other words, the event reports the SIP URI in the format sip:domain.com rather than the expected sip:user@domain.com). (UKTS-17548)


Top of Page


Release Number 8.1.108.00 [03/24/17] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

There are no restrictions for this release. This release contains no new features or functionality, but supports T-Server for CSTA Connector 8.1.108.00.

Corrections and Modifications

This release includes no corrections or modifications.

Top of Page


Release Number 8.1.107.02 [12/14/16] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


T-Server and CSTA Connector now correctly report an EventPartyDeleted when an external party leaves a conference in the following scenario:

(UKTS-17506)


Top of Page


Release Number 8.1.107.01 [08/25/16] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

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

Corrections and Modifications

This release includes the following corrections and modifications:


CSTA Connector now attempts to recreate an event Channel on receiving any error from BroadWorks, for any conditions where BroadWorks does not respond to an Add Channel request, or when CSTA Connector does not recognize a response. Previously, the connector handled only specific errors. (UKTS-17453)


The connector no longer goes into an indefinite loop when two BroadWorks calls are established between the same two User Endpoints and both Users have started conferences. However, though the connector now handles such calls correctly, call reporting for such a scenario is not valid in the Genesys call model. To avoid situations where Genesys cannot provide call reporting, the connector now releases conferences created between two SIP End Points. When the connector decides to release such calls, it generates a new LMS message:

40022|STANDARD|BWCC_USER_002|All parallel calls between DN %s and DN %s will be released

The LMS message is for information only, however, so call center scenarios may require review if this message appears in the log too often. (UKTS-17437)


Top of Page


Release Number 8.1.106.01 [03/30/16] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


GCTI services are now restored on DNs associated with re-created users. Previously, after deletion and and re-creation of the same user, the connector did not restore GCTI services. (UKTS-17424)


Installation of the connector on Red Hat Linux 5 is now supported. (UKTS-17400)


Top of Page


Release Number 8.1.106.00 [12/03/15] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

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

Corrections and Modifications

This release includes the following corrections and modifications:


The connector now correctly reports events for the "Call distributed to Agent with 1PCC Answer" scenario. CSTA Connector version 8.1.105.00 reported incorrect call information to T-Server. (UKTS-17372)


T-Server and CSTA Connector for BroadSoft BroadWorks now start correctly even under BroadWorks XSP server overload conditions (when the XSP server rejects random requests with the error "Service Unavailable"). (UKTS-17340)


Top of Page


Release Number 8.1.105.00 [09/01/15] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

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

Corrections and Modifications

This release includes the following corrections and modifications:


CSTA Connector now uses SubscriptionResync events to update call configuration and inform T-Server about call state changes. SubscriptionResync events are available in BroadWorks version 20.sp1 and higher and distributed by BroadWorks when the system detects an Application Server failover condition. (UKTS-17320)


In a supervisor monitoring scenario, CSTA Connector no longer becomes unstable when a supervisor requests to monitor a consultation call on an agent who initiates a call to a routing point with a forced route to the new destination. (UKTS-17307)


For all completed XML data packets sent to and received from XSP, a new dedicated message in the log shows following information:

(UKTS-17303)


Corrected issue where CSTA Connector might have created an incorrect CSTA message (or failure) when two legs of the same internal call established between appearances of the same SIP endpoint join a conference. However, while this reporting is now correct, call reporting for such scenario is not valid in the Genesys call model. To avoid these situations, the system now releases internal calls established between appearances of the same SIP endpoint. These call releases generate a new log event message, #40021:

40021|STANDARD|BWCC_USER_001|Internal Call %s between appearances on DN %s will be released

This log event message is for information only, but call center scenarios may require review if this message appears in the log too often. (UKTS-17301)


Invalid XML messages received from XSP servers may cause a CTI service outage. CSTA Connector cannot handle these invalid messages, but introduces a new log event message, #40011, to make troubleshooting easier:

40011|STANDARD|BWCC_XML_001|Invalid XML message received from XSP link

The connector generates this log event message when the XML message cannot be parsed. This message is for information only and a service outage should be expected. The event reporting channel will be terminated on the BroadWorks side. (UKTS-17299)


Changes to XSP link configuration allow more flexibility:

(UKTS-17296)


Corrected issue where CSTA Connector could delete the wrong event reporting channel when an XSP link is disconnected and the connector has multiple established XSP links. (UKTS-17295)


Top of Page


Release Number 8.1.104.00 [06/25/15] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

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

Corrections and Modifications

This release includes the following corrections and modifications:


To avoid slowdowns after incorrect switch reporting, where a PBX did not provide valid call information in response to a DialRequest, CSTA Connector now supplies "dummy" call information to T-Server. (UKTS-17288)


CSTA Connector now re-creates a partially failed Reporting Channel even when the channel is functioning properly on other PBX links. Previously, the connector did not re-create the channel until it failed across all PBX links. (UKTS-17238, UKTS-17264)


Top of Page


Release Number 8.1.103.00 [11/07/14] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

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

Corrections and Modifications

This release includes the following corrections and modifications:


Previously the connector delayed its reporting of call delivery to an agent and kept the Routing dialog open for a short interval. If a call was abandoned during that interval, T-Server reported the scenario correctly but could generate unexpected LMS messages about request expiration. The connector now correctly reports call delivery to an agent. (UKTS-17124)


The connector now correctly returns the callOriginated state for a device when a snapshot is requested on device with the BroadWorks Click-To-Dial personality. In BroadWorks this state is the temporary Alerted state, which can progress only into the Originated (or Failed) state. Previously the connector reported the callReceived state, which caused T-Server to assign an incorrect call type to the call. (UKTS-17154)


Upon receiving an xsi:ChannelTerminatedEvent from PBX, the connector now always informs T-Server that the PBX link is out of service. Previously, the connector took no action. The issue occurred after the connector recovered from a network failure on the same PBX link. (UKTS-17167)


Top of Page


Release Number 8.1.102.03 [05/19/14] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


When a CTI link to BroadWorks has failed and been re-established, T-Server now restarts all monitors for controlled DNs as soon as it receives a BroadWorks ChannelTerminatedEvent. Previously, on receiving a ChannelTerminatedEvent, CSTA Connector could fail to inform the T-Server about the failed CTI link. (UKTS-17059)


When a call bounces quickly from the ACD queue to an agent and then back to the ACD queue after no answer, CSTA Connector now correctly indicates that the call has returned to the queue. Previously in such scenarios, CSTA Connector could fail to notify T-Server that the call had been diverted from the ACD queue or that the call had been delivered to an agent. (UKTS-17014, UKTS-17072)


CSTA Connector now generates the correct events when an agent becomes unavailable immediately after the call is routed to that agent. Previously, when a call was returned to the routing point, incorrect reports triggered the creation of new calls in T-Server. (UKTS-17071)


Top of Page


Release Number 8.1.102.02 [04/11/14] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


CSTA Connector now always reports new destination information in a CSTA Diverted event when routing is performed using the Distribute mechanism. (UKTS-17033)


CSTA Connector no longer occasionally keeps a Routing Point in a Failed state after the communication with a BroadWorks CTI server was lost and re-established. (UKTS-17021)


Top of Page


Release Number 8.1.102.01 [02/20/14] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

There are no restrictions for this release. This section describes new features that were introduced in this release of CSTA Connector for BroadSoft BroadWorks.

Corrections and Modifications

This release includes the following corrections and modifications:


CSTA Connector now correctly handles LogOut Guest from a SIP phone that has no integration with the BroadWorks hoteling feature. Previously, CSTA Connector produced a message informing T-Server that the hoteling guest left the host. (UKTS-16928)


After losing its link to one or more XSP servers, CSTA Connector now enables routing on the switch after the link to the switch is restored. (UKTS-16863)


CSTA Connector now reports a compatible routing state to T-Server when supervised routing is enabled at the switch and T-Server requests unsupervised routing. Previously, this action introduced a routing state incompatibility in T-Server. (UKTS-16854)


CSTA Connector now correctly processes LCA port changes. Previously, CSTA Connector ignored any LCA port changes. (UKTS-16723)


When BroadWorks returns incomplete user information in response to a query guest association, CSTA Connector now uses internal hoteling host information to provide correct reporting for the user. (UKTS-16715)


CSTA Connector no longer prints XML parse error messages in the console log when an XML packet contains one or more complete XML messages followed by an incomplete XML message that was split at the network level. (UKTS-16355)


CSTA Connector now correctly ignores duplicated messages received from the BroadWorks XSP server when passing them to T-Server. (UKTS-16976)


Top of Page


Release Number 8.1.101.02 [10/11/13] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

There are no restrictions for this release. This section describes new features that were introduced in this release of CSTA Connector for BroadSoft BroadWorks.

Corrections and Modifications

This release includes the following corrections and modifications:


CSTA Connector now correctly processes the TreatmentPlayAnnouncementAndDigits and TreatmentPlayAnnouncement treatments in sequence. Previously, the completion of the Digit collection was sometimes not reported. (UKTS-16674)


CSTA Connector now correctly reads Configuration Server's configuration file information when Configuration Server restarts. Previously, after Configuration Server restarted, CSTA Connector might misinterpret the configuration data and terminate unexpectedly. (UKTS-16670)


CSTA Connector now correctly processes the Originated and Delivered CSTA events in any order. Previously, CSTA Connector reversed the order of these events and delayed sending the Delivered event, which caused incorrect reporting. (UKTS-16654)


If a call is returned back to the Routing Point immediately after routing the call, agents no longer continue to be reported in the ringing state, regardless of the sequence of events received from the switch. Previously, depending on the sequence of events, CSTA Connector did not send a connectionCleared event to T-Server and the agent remained in the ringing state.

Note: This functionality requires T-Server version 8.1.101.03, or higher. (UKTS-16644)


Top of Page


Release Number 8.1.100.06 [04/09/13] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

There are no restrictions for this release. This section describes new features that were introduced in the initial 8.1 release of CSTA Connector for BroadSoft BroadWorks.

Corrections and Modifications

This release includes the following corrections and modifications:


CSTA Connector for BroadSoft BroadWorks now generates CSTA-complient events for transfer and conference call scenarios for BroadWorks calls made between different BroadWorks groups. Previously, CSTA Connector might have generated incorrect CSTA transfer events, if the transfer was completed in a consultation call chain and the consolation calls were created between different BroadWorks groups within the same BroadWorks enterprise. (ER# 316546589)


Top of Page


Known Issues and Recommendations

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


BroadWorks allows the configuration of Call Centers (ACDQ) with multiple DNIS numbers. Any of the DNIS numbers provisioned in BroadWorks as well as the primary ACDQ number can be monitored by Genesys. ACDQ with multiple DNIS numbers is handled by BroadWorks as a single monitored object, which means that registering to both the primary ACDQ number and DNIS numbers does not work, as subsequent registration overrides previous registrations with no notification from BroadWorks. Genesys strongly advises that you monitor only the primary ACDQ number. If it is necessary to configure DNIS numbers in Genesys Configuration Database, such devices are created with the Register flag set to False.

Found In: Fixed In:

Call pickup and call intrusion are not supported in environments where the DNs are configured as URIs. (UKTS-17541)

Found In: Fixed In:

If you have installed BroadWorks patch 343621 on the PBX, to enable Mute on conference controllers, Genesys recommends that you upgrade T-Server to version 8.1.106+.

Found In: Fixed In:

CSTA Connector for BroadSoft BroadWorks supports CallRecordingStartedEvent and CallRecordingStoppedEvent (available for BroadWorks v20.sp1 and higher or after installing patch 343621 for older versions). Recording functionality in T-Server remains the same as for previous releases.

Found In: Fixed In:

Genesys recommends configuring DN numbers using one of the following formats: Broadsoft extension numbers or SIP tel: numbers. Do not configure DNs as SIP URIs, which can cause unpredictable results in event reporting.

Found In:  Fixed In: 

The connector cannot correctly report treatments when the switch reports a Treatment Stop without first reporting a Treatment Start.

Found In: 8.1.102.01 Fixed In: 

If an inbound call is picked up on a device while ringing, the switch reporting for the call pickup is not correct, which results in the following:

  1. A new connection ID is generated for the device performing the pickup.
  2. Any existing call user data is lost.

(ER# 283316521)

Found In: 8.0.101.07 Fixed In: 

If the switch for a contact center is configured to play a call whisper message and a call is distributed through the contact center to an agent, and then that call is picked up by another device while still ringing on the agent, the switch reporting for this scenario is incorrect. As a result, the call pickup is not reported according to the Genesys call model. If calls are picked up by agents, it is recommended not to play a call whisper message. (ER# 283086465)

Found In: 8.0.101.07 Fixed In: 

To ensure correct reporting of inbound calls made to contact centers, the switch contact center option, Display DNIS Number to agent when presenting call instead of Calling Number, should not be enabled. (ER# 283086461)

Found In: 8.0.101.07 Fixed In: 

The conference model, used by the BroadWorks computer-telephony integration (CTI) link, does not allow conference reporting, if the conference controller is not a monitored subscriber. This conference model allows conference-related requests on behalf of the conference controller. (ER# 265876985)

Found In: 8.0.101.03 Fixed In: 

BroadSoft Connector's predictive dialing feature is only initiated through a Routing Point. This feature provides no inbound call progress detection; therefore, the interception of a predictive call by fax, answering machine, silence, or other automated interaction is not detected. (ER# 265876988)

Found In: 8.0.101.03 Fixed In: 

The BroadWorks CTI call whisper message feature prevents calls from being placed on hold while the call whisper message is playing. Any CTI link request that would put the call on hold is rejected. (ER# 265876991)

Found In: 8.0.101.03 Fixed In: 

BroadWorks Connector supports the following aspects of the Collect Digit treatment:

(ER# 278538090)

Found In: 8.0.101.03 Fixed In: 

Issuing a TSingleStepConference request to an unmonitored DN is not supported. (ER# 278538111)

Found In: 8.0.101.03 Fixed In: 

When a call is forwarded to a Routing Point, the CallState attribute in the EventQueued event is reported as Ok instead of Forwarded. (ER# 278538116)

Found In: 8.0.101.03 Fixed In: 

If a call is waiting on an ACD Queue and T-Server is restarted, CSTA Connector reports the call as a conference call to T-Server when it is distributed to an agent. (ER# 278538119)

Found In: 8.0.101.03 Fixed In: 

An EventError message is only generated on a Routing Point when using the supervised routing method (if the value of the T-Server option, supervised-route-timeout, is greater (>) than 0 (zero)) to route to a busy or DND device. This also means that the Failed Route Notification feature is only available when using the supervised routing method, and that the alarm count is only increased by failed routes to busy or DND devices. (ER# 278538212)

Found In: 8.0.101.03 Fixed In: 

When an alerting call is picked up by another device, CSTA Connector is unable to provide information to T-Server so that the ThirdPartyDN value is reported in the EventReleased message in the alerting device. (ER# 278538217)

Found In: 8.0.101.03 Fixed In: 

It is not possible to send an account code through the CTI link while the agent is in the after-call work (ACW) state. (ER# 278538220)

Found In: 8.0.101.03 Fixed In: 

If a call is made from one site to another site via Inter Server Call Control (ISCC), and then transferred back to the first site using Call Overflow (COF), the ISCC/COF call matching does not contain the OtherDN attribute in the EventPartyChanged event. (ER# 278538225)

Found In: 8.0.101.03 Fixed In: 

Occasionally, when releasing a consultation call on the transferring device, the switch sends the retrieved event for the held primary call before the connection clears for the consultation call, which results in T-Server reporting an EventHeld event on the consultation call and an EventRetrieved event on the primary call before generating an EventReleased event on the consultation call. (ER# 278538246)

Found In: 8.0.101.03 Fixed In: 

In a scenario where a supervisor issues a TMonitorNextCall request on a Routing Point, if any call is mute transferred to the Routing Point being monitored by the supervisor, the switch drops all parties in the call. (ER# 278538249)

Found In: 8.0.101.03 Fixed In: 

If a device is added to Configuration Manager while there is a call ringing on the device, CSTA Connector reports the call as a conference call to T-Server. (ER# 278538281)

Found In: 8.0.101.03 Fixed In: 

If call forwarding is set manually on an end point, CSTA Connector is unable to report that the call was forwarded to T-Server, so the CallState attribute in the EventRinging event on the forwarding destination is reported as Ok instead of Forwarded. (ER# 278538284)

Found In: 8.0.101.03 Fixed In: 

If a supervisor monitors a Routing Point and either a direct internal call is made to the Routing Point, or a consultation call is made to the Routing Point, a new connection ID is incorrectly generated for the EventQueued and EventRouteRequest events on the Routing Point, and for the EventEstablished event on the supervisor. (ER# 279229961)

Found In: 8.0.101.03 Fixed In: 

First party forwarding cannot be set if the target device is currently hot-desking. (ER# 278538087)

Found In: 8.0.101.03 Fixed In: 

A conference controller cannot issue a TReconnectCall request and cannot transfer the conference call. (ER# 278538084)

Found In: 8.0.101.03 Fixed 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. For more information on discontinued support for operating environments and databases, see Discontinued Support in the Genesys Supported Operating Environment Reference Guide.


Discontinued As Of: 8.1.104.00

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.

Product documentation is provided on the Customer Care website, the Genesys Documentation website, and the Documentation Library DVD.

Note: For the DVD, the New Documents on this DVD 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