9.1.000.03
Genesys Driver for use with Apple Business Chat Release Notes
| Release Date | Release Type | Restrictions | AIX | Linux | Solaris | Windows |
|---|---|---|---|---|---|---|
| 06/26/19 | General | Under Shipping Control | X | X |
Helpful Links
Releases Info
Product Documentation
Genesys Products
What's New
This release contains the following new features and enhancements:
- An option, msg-not-delivered, is introduced to allow users to customize the auto-reply message in case of Genesys Hub outage. (MSGA-1998)
- Agents can now initiate an outbound session with their customers. (MSGA-1373)
- The following new configuration options are added:
- inbound-route-by-call
- Default Value: An empty string
- Valid Values: A valid endpoint
- Changes Take Effect: After restart
- Specifies the endpoint for outbound chat sessions created by invite to chat requests. This endpoint must exist in the Chat Server configuration. Chat Server will use this endpoint to place interactions to an interaction queue. If the option is not confirued or empty, the channel does not support invite to chat requests.
- inbound-route-by-call
For example: inbound-route-by-call = 101:chat_endpoint
- media-type-chat-by-call
- Default Value: applebcsession
- Valid Values: A ny valid string
- Changes Take Effect: After restart
- Specifies the media type assigned to interactions that are submitted to Interaction Server by Chat Server created by invite to chat requests (outbound chat sessions).
- Default Value: applebcsession
- x-hub-pull-reserve-time
- Default Value: 10
- Valid Values: 1-300
- Changes Take Effect: After restart
- Specifies how long, in seconds, fetched messages are reserved by Hub.
- Default Value: 10
Resolved Issues
This release contains the following resolved issues:
An issue that prevented the driver from connecting to Genesys Hub via proxy is fixed. Now, basic authentication over HTTP is supported between Apple Business Chat driver and proxy. (MSGA-2121)
Upgrade Notes
No special procedure is required to upgrade to release 9.1.000.03.
Comments or questions about this documentation? Contact us for support!
