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 |
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.
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.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain any new features or functionality.
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)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This section describes new features that were introduced in this release of CSTA Connector for BroadSoft BroadWorks.
CSTA Connector now fully supports the BroadSoft BroadWorks Application Controller feature for Routing Point Failover control.
The Application Controller feature for Routing Point Failover control is configured using the following options:
app-controller
Default Value: CSTA Connector Application
name in Configuration Manager
Valid Values: Any character string
Changes Take Effect: Immediately
Specifies a required identifier used by BroadSoft BroadWork's routing functionality. See "Route Point Failure Policy" in the BroadSoft BroadWorks CTI documentation for more information.
channel-set-name
Default Value: CSTA Connector Application
name in Configuration Manager
Valid Values: Any character string
Changes Take Effect: Immediately
Specifies a logical name for a CTI link to BroadSoft BroadWorks. For example, multiple TCP/IP ports opened on BroadSoft BroadWorks CTI servers with the channel-set-name
configuration option set to the same value are treated as a single CTI link. BroadSoft BroadWorks uses this Application
name value to provision the identity of the Application Controller.
These configuration options can be configured in the Connector
section of the Application
object.
Note: T-Server for CSTA Connector should be at least version 8.1.102.03 to achieve full compatibility with CSTA Connector for BroadSoft BroadWorks.
(ER# 298489738)
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)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This section describes new features that were introduced in this release of CSTA Connector for BroadSoft BroadWorks.
CSTA Connector now supports active keep-alive which is controlled by the CSTA Connector configuration options kpl-interval
and kpl-tolerance
.
CSTA Connector now sends BroadWorks keep-alive requests on an established XSP link when the interval from the last message received from the XSP link is greater than the value specified by the configuration option kpl-interval
. Setting the value to 0
(zero) will disable the active KPL functionality.
For each keep-alive request, CSTA Connector expects to receive a BroadWorks keepaliveResponse
message from the XSP link. An XSP link is considered as unresponsive when the number of missing KPL responses become greater than the value specified by the kpl-tolerance
option. This means that setting kpl-tolerance
set to 0
will mark a link as unresponsive after a single KPL response is missing.
The active keep-alive feature is configured using the following new options:
kpl-interval
Default Value: 10
Valid Values: 0-600
Changes Take Effect: Immediately
Specifies a KPL interval (in seconds). To check network connectivity, CSTA Connector issues a dedicated KPL request to BroadWorks XSP at the interval specified when there is no other activity on the link.
kpl-tolerance
Default Value: 0
Valid Values: 0-10
Changes Take Effect: Immediately
Specifies the number of failed KPL requests that CSTA Connector tolerates before considering the XSP link as unresponsive. When an unresponsive link is detected, CSTA Connector closes and reopens the particular XSP link.
The configuration options can be configured in the Connector
section, and in the link-%s
section. Options configured in the link-%s
section will take precedence over the options configured in the Connector
section and are applied to the particular link.
(ER# 296646678)
CSTA Connector now uses the BroadWorks RoutePointDistributeCallRequest
as the preferred method of routing. When routing is requested to BroadWorks Agents, CSTA Connector now attempts to execute RoutePointDistribute
requests on the BroadWorks level. CSTA connector uses this request for supervised and non-supervised routing.
Original CSTA Connector behavior, where supervised routing is performed using Distribute and non-supervised routing is performed using Blind Transfer, can be restored by setting the backward compatibility configuration option enable-distribute
to false
.
Error handling:
BroadWorks routing using the Distribute mechanism succeeds only when the target agent has Call Center Premium service assigned. Attempts to use the Distrubute method for agents with Basic or Standard Call Center services will fail with the BroadWorks error 110108 "Agent is not assigned the Call Center-Premium service"
.
On receiving BroadWorks error 110108
, CSTA Connector marks the target agent as non-distributable and internally re-invokes BroadWorks Routing using Blind Transfer mechanism. CSTA Connector does not report an error to the CSTA client (T-Server) if a Blind Transfer is performed successfully. LMS message 40001 "Agent on DN %s does not support Routing Distribute"
is sent to Genesys Management Layer. All consecutive routings to non-distributable
agents are performed as a Blind Transfer. CSTA Connector clears the non-distributable property on the agent when the last CSTA client stops monitoring the agent device.
New LMS messages introduced:
40001 STANDARD BWCC_RT_001 "Agent on DN %s does not support Routing Distribute"
40002 STANDARD BWCC_RT_002 "Agent on DN %s Routing Distribute support is unknown"
enable-rp-distribute
Default Value: true
Valid Values: true, false
Changes Take Effect: Immediately
When set to true
, CSTA Connector selects Distribute as default method for non-supervised routing, otherwise
Blind Transfer is used.
CSTA Connector recognizes the following Private KV List extension supplied by T-Server in CSTA requests.
RPDistributeType
Type: String (BWDistribute
or BWTransfer
)
Valid Values: BWDistribute
, BWTransfer
When this extension, with the value BWDistribute
, is supplied by T-Server, CSTA Connector uses a
RoutePointDistributeCallRequest
as the preferred method for routing from a Routing Point. A value of BWTransfer
instructs CSTA Connector to use Blind Transfer for routing. Any other values for this extension are ignored.
Restrictions and Limitations:
Transfer to phone number
should not use an External Routing Point (including itself).
(ER# 299007985)
Treatment implementation is modified to enable proper integration with Universal Routing Server (URS).
A RequestApplyTreatment
(AttributeTreatmentType
= PlayAnnouncement
and PlayAnnouncementAndCollectDigits
) now has provisioning to provide multiple PROMPTs. Up to four PROMPTs can be converted to URI. The conversion rule is specified by the new configuration option treatment-uri-pattern
.
When the configuration option is not set, CSTA Connector uses the value supplied in the configuration option def-treatment-uri
and provides that value in the first Treatment URI.
The URI pattern is specified in the CSTA Connector configuration option treatment-uri-pattern
.
treatment-uri-pattern
Default Value: no default value
Valid Values: String
Changes Take Effect: Immediately
Provides a pattern to create a URI for an announcement Audio file in BroadWorks. When a value is provided, the PROMPT format pattern is replaced with the provided value. When a value is not provided, the pattern is removed from the final URI.
Supported formats:
%i
- is replaced by the ID
value
%u
- is replaced by the USER_ANN_ID
value
%t
- is replaced by the USER_ID value
%%
- a single %
character
For example:
Given ID = 1000
, the pattern http://cti_provider.com/media/tones/%tAnn%i%u.wav
is translated to http://cti_provider.com/media/tones/Ann1000.wav
Given USER_ANN_ID = 999
and USER_ID = BWTenant
, the same pattern is transformed to http://cti_provider.com/media/tones/BWTenantAnn999.wav
Restrictions and Limitations:
RoutePointPlayTreatmentRequest
can have up to four entries. Up to four
PROMPTs can be configured for use with treatment-uri-pattern
. Prompts with more than four numbers are ignored.
TEXT
and DIGITS
are not supported. Prompts containing these are considered as invalid and further PROMPT conversion to URI will be stopped.
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)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This section describes new features that were introduced in this release of CSTA Connector for BroadSoft BroadWorks.
The enable-controller-release
configuration option has been introduced in this release.
enable-controller-release
Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately
When a conference controller has initiated two or more conferences, and this option is set to true
, a TReleaseCall
is accepted and all the parties are dropped from the call. If set to false
, a TReleaseCall
is rejected with an EventError
.
The ReleaseController
extension overrides this option. A value of 0
(zero) for the extension corresponds to the option value of false
, and a positive integer for the extension corresponds to the option value of true
.
There are no corrections or modifications in this initial release.
Supported Operating Systems
New in This Release
Corrections and Modifications
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.
There are no corrections or modifications in this initial release.
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 |
This section documents features that are no longer supported in this software.
There are no discontinued features or functions for this product.
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.
Framework 8.0 CSTA Connector for BroadSoft BroadWorks Deployment Guide contains detailed reference information for the Genesys Framework 8.0 CSTA Connector for BroadSoft BroadWorks including configuration options and specific functionality.
Framework 8.0 Deployment Guide helps you configure, install, start, and stop Framework components.
The Voice Platform SDK 8.0 .NET (or Java) API Reference and the Genesys 7 Events and Models Reference Manual and contains the T-Library API, information on TEvents, and an extensive collection of call models.
Genesys Migration Guide contains a documented migration strategy for each software release. Please refer to the applicable portion of this guide or contact Genesys Technical Support for additional information.
Genesys Licensing Guide contains information about the licensing requirements for this software. Please refer to the applicable portion of this guide or contact Genesys Technical Support for additional information.
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.