Revision as of 05:22, May 22, 2024 by Xavier (talk | contribs) (Reverted edits by Xavier (talk) to last revision by Umamaheswari.85)
Jump to: navigation, search

Limitations

Currently, the following limitations are present for EX Engage Connector:

  • Currently, EX Engage Connector supports only single SIP Server deployments. Multi-site support is not available.
  • EX Engage Connector can connect to the Engage contact center where configuration is stored in Oracle, PostgreSQLs or Microsoft SQL Server databases.
  • EX Engage Connector can work only with a single Engage tenant. If customers use Engage multi-tenant Config DB and have multiple tenants provisioned, then they should select one of the tenants for the EX integration and provision this tenant accordingly.
  • EX Engage Connector requires a call routed to an agent to go through a VQ DN, which is configured to be mapped to the GC EX Org as an ACD Queue. Call distributed to agents without involving a VQ DN (e.g. through an Engage ACD queue) may not be injected into the GC EX Org correctly.
  • EX integration supports injection of voice interactions only. To optimize efficiency of the WFM and Gamification services it is recommended to avoid adding digital or blended (voice/digital) agents to the EX integration scope.
Comments or questions about this documentation? Contact us for support!