Jump to: navigation, search

tenant-dbid

Section: channel-any_name
Default Value:
Valid Values: An integer value with DBID
Changes Take Effect: After restart


Specifies the DBID of a tenant associated with a channel. This option is required if option inbound-route is not set.

inbound-route

Section: channel-any_name
Default Value: An empty string
Valid Values: A comma-separated list of endpoints
Changes Take Effect: After restart


Specifies the endpoints for inbound messages arriving from the media. These endpoints must exist in the Chat Server configuration. If this option is not specified or empty, the channel type is "no inbound", so inbound messages will not be ignored.
For example:
101:paging_endpoint—The endpoint for inbound messages, which is processed in "paging" mode.
101:paging_endpoint, 101:chat_endpoint—The same as previous, plus an additional endpoint for "session" mode. The endpoint for "session" mode is an endpoint specified in the Chat Server configuration. Chat Server will use this endpoint to place interactions into the interaction queue.

9.0.001.10

Digital Messaging Server Release Notes



Digital Messaging Server is part of 9.x starting in 9.0.000.07.
Release Date Release Type Restrictions AIX Linux Solaris Windows
09/26/18 General X X

Helpful Links

Releases Info

Product Documentation

Genesys Products


What's New

This release contains the following new features and enhancements:

  • Support for the latest releases of Apple Business Chat Plugin for Workspace Desktop Edition and Genesys Driver for use with Apple Business Chat via Hub.
  • The configuration option inbound-route is no longer mandatory. If this option is not set, you must set a new option, tenant-dbid, with the database ID for a tenant associated with this channel.


Resolved Issues

This release contains the following resolved issues:


Digital Messaging Server now correctly handles long messages in chat conversations. Previously, in certain conditions, these long messages were lost. (DMS-190)




Upgrade Notes

No special procedure is required to upgrade to release 9.0.001.10.

This page was last edited on December 19, 2018, at 18:28.
Comments or questions about this documentation? Contact us for support!