Release Note

CSTA Connector for BroadSoft BroadWorks

8.0.x

Genesys Telecommunications Laboratories, Inc. © 2011–2012

Contents

Introduction

Release Number AIX HP-UX PA HP-UX IPF Linux Solaris Windows
8.0.102.05 [10/18/12] – Hot Fix       X X X
8.0.102.04 [07/13/12] – General X X X X X X
8.0.102.02 [05/23/12] – General X X X X X X
8.0.101.07 [09/30/11] – General X X X X X X
8.0.101.03 [08/02/11] – General X X X X X X

Known Issues and Recommendations
Discontinued Support
Internationalization
Additional Information


Introduction

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 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 the Read Me. Please contact your technical support representative if you have any questions.


Release Number 8.0.102.05 [10/18/12] – 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 does not contain any new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


CSTA Connector for BroadSoft BroadWorks now correctly handles the recreation of an event channel after receiving an EventChannelTerminated message, which is not generated when restoring the TCP/IP connection. Previously during this scenario, CSTA Connector for BroadSoft BroadWorks sometimes unnecessarily reset the TCP/IP connection if the termination of an event channel occurred. (ER# 308423333)


CSTA Connector for BroadSoft BroadWorks now correctly handles fragmented XML stream data in a scenario where the fragmentation occurs in specific places in the XML stream. Previously in this scenario, CSTA Connector for BroadSoft BroadWorks would stop processing this fragmented XML stream data. (ER# 308010348)


CSTA Connector for BroadSoft BroadWorks now correctly handles call transfers when the PBX reports that the transferred call party digits are the same as the transferring call party digits. Previously in this scenario, CSTA Connector for BroadSoft BroadWorks would go into an infinite recursive loop after completing a call transfer. (ER# 308000828)


The default value for the -cfglib-connect-tmout command-line parameter has been modified. CSTA Connector for BroadSoft BroadWorks now supports the default value of 10 seconds, if the cfglib-connect-timeout configuration option is not provided. (ER# 305196559)


Top of Page


Release Number 8.0.102.04 [07/13/12] – 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 sets the Active flag when making Hotel Guest associations.

This modified behavior of the CSTA Connector is controlled using the following option:

force-hoteling-guest
Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately

Specifies whether CSTA Connector will forcibly associate and/or dissociate a Hoteling Guest association in a ModifyHotelingGuest request. This configuration option can be configured in the Connector section of the Application object.

Previously, CSTA Connector always set the Active flag to true when setting a Hoteling Guest association, and set the flag to false when removing a Hoteling Guest association. CSTA Connector was modified so that by default it will no longer pass the Active flag in a ModifyHotelingGuest request, although backwards compatibility can be maintained with the new option.

(ER# 301944983)


Top of Page


Release Number 8.0.102.02 [05/23/12] – 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 responses on RequestPlayAnnouncementAndCollectDigits if two and more requests are made simultaneously. (ER# 291183837)


Top of Page


Release Number 8.0.101.07 [09/30/11] – 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

There are no corrections or modifications in this initial release.

Top of Page


Release Number 8.0.101.03 [08/02/11] – 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.0 release of CSTA Connector for BroadSoft BroadWorks.

Corrections and Modifications

There are no corrections or modifications in this initial release.

Top of Page


Known Issues and Recommendations

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


If an inbound call is picked up on a device while ringing, the switch reporting for the call pickup is not correct. This will result in a new Connection ID being generated for the device performing the pickup, and any existing User Data on the call will be lost. (ER# 283316521)

Found In: 8.0.101.07 Fixed In: 

If the switch for a call center is configured to play a Call Whisper Message, and a call is distributed through the call 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, call pickup will not be 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: 

In order to ensure correct reporting of inbound calls made to call centers, the switch call 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 BroadWorks CTI will not allow Conference reporting if Conference controller is not a Monitored subscriber. The conference model, used by BroadWorks CTI only allows Conference related requests on behalf of the Conference controller. (ER# 265876985)

Found In: 8.0.101.03 Fixed In: 

Predictive dialing feature on BroadWorks Connector can only be initiated through a Routing Point. Predictive dialing on BroadWorks provides no inbound call progress detection; therefore, interception of a predictive call by a fax, answering machine, silence or other automated interaction will not be detected. (ER# 265876988)

Found In: 8.0.101.03 Fixed In: 

A whisper operation prevents the agent device being held by CTI request from being used until the whisper has completed. (ER# 265876991)

Found In: 8.0.101.03 Fixed In: 

BroadWorks Connector does support the following aspects of the Collect Digit Treatment:

(ER# 278538090)

Found In: 8.0.101.03 Fixed In: 

Issuing a RequestSingleStepConference 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 in EventQueued will be 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, the CSTA Connector will report the call as a conference to T-Server when it is distributed to an agent. (ER# 278538119)

Found In: 8.0.101.03 Fixed In: 

An EventError can only be generated on a Routing Point when making a supervised route (T-Server option supervised-route-timeout is greater than 0) to a busy or DND device. This also means that the Failed Routing Alarm feature is only available when routing with supervision, and that the alarm count will only be 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 for the ThirdPartyDN to be reported in the EventReleased on the alerting device. (ER# 278538217)

Found In: 8.0.101.03 Fixed In: 

It is not possible to send an Account Code through CTI while the agent is in the After Call Work state. (ER# 278538220)

Found In: 8.0.101.03 Fixed In: 

If a call is made from site-1 to site-2 through ISCC, and then transferred back to site-1 using COF, call matching will not contain OtherDN in EventPartyChanged. (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 cleared for the consultation call. This results in T-Server reporting EventHeld on the consultation call and EventRetrieved on the primary call before EventReleased on the consultation call. (ER# 278538246)

Found In: 8.0.101.03 Fixed In: 

In a scenario where a supervisor issues RequestMonitorNextCall on a Routing Point, if any call is mute transferred to the Routing Point being monitored by the supervisor, the switch will drop 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 will report the call as a conference to T-Server. (ER# 278538281)

Found In: 8.0.101.03 Fixed In: 

If forwarding is set manually on an End Point, CSTA Connector is unable to report that the call has been forwarded to T-Server. This will result in Call State Ok being reported in the EventRinging event on the forwarding destination instead of Call State 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 Route Point, or a consultation call is made to the Route Point, a new Connection ID is incorrectly generated for the EventQueued, EventRouteRequest on the Route Point, and for the EventEstablished 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 RequestReconnectCall, and cannot transfer the conference. (ER# 278538084)

Found In: 8.0.101.03 Fixed In: 

If a conference controller releases a conference, all the remaining parties are dropped. As a consequence, any RequestDeleteFromConference request made by a non-conference controller will be rejected if that request deletes the conference controller. (ER# 278538081)

Found In: 8.0.101.03 Fixed In: 8.0.101.07

Top of Page


Discontinued Support

This section documents features that are no longer supported in this software.


There are no discontinued features or functions for this product.


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 Technical Support website. The following documentation also contains information about this software.

Product documentation is provided on the Technical Support website, the Genesys Documentation wiki, and the Documentation Library DVD (produced monthly) or the Developer Documentation CD.

Note: For the DVD/CD, the New Documents on this DVD/CD page indicates the production date for that disc. Due to disc production schedules, documentation on the Technical Support 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