QMS Configuration

This document explains how to configure QMS to push content to Enghouse Vecko (voice of the customer) for text-based media, including voice call transcripts, email, webchat, SMS and UC-messages. This configuration is file-based, using the data service and media processing service configuration files.

The data service configuration file can be found in the QMS data service installation directory, and is a file called DataServiceHost.dll.config. Open the DataServiceHost.dll.config file using any text editor (e.g. Notepad), and find the section enclosed by the <appSettings> …​ </appSettings> XML tags. Within these tags you must add the following new keys:

<add key="VeckoPush.ClientId" value="?" />
<add key="VeckoPush.ClientSecret" value="?" />
<add key="VeckoPush.TokenUrl" value="?"/>
<add key="VeckoPush.ApiUrl" value="?"/>
<add key="VeckoPush.RecordingProfiles" value="?" />

The values of these keys will depend on the customer’s environment and the client details that have been supplied to you by Vecko.

  • ClientId - the OAuth client identifier used to connect your application to the Vecko servers (supplied by Vecko)

  • Client Secret - the client secret of the account used to connect your application to the Vecko servers (supplied by Vecko)

  • TokenUrl - the OAuth identity server token URL used to obtain a security context to connect to the Vecko servers (usually an eptica.cloud address) e.g.
    https://idp.dev.eptica.cloud/auth/realms/envps/protocol/openid-connect/token

  • ApiUrl - the vecko server endpoint which accepts the push requests from QMS (usually a vecko.com address) e.g.
    https://envps.dev.vecko.com

  • RecordingProfiles - is the set of names of the recording profiles from which recordings should be sent to Vecko. In a multi-tenant QMS environment each profile name is prefixed with the tenant name. A comma should be used to seperate profile names, and a colon should be used to seperate tenant and profile names. e.g.
    Multi-tenant example: tenantname1:profilename1, tenantname1:profilename2, tenantname2:profilename1
    Non-tenant example: profilename1, profilename2, profilename3

The data service and vecko push media processing servers will need to be restarted after making any DS configuration changes. In an HA environment, enter this configuration into both the primary and secondary data service files.

The media processing service configuration file can be found in the QMS media processing service installation directory, and is a file called MediaProcessingService.dll.config. Open the MediaProcessingService.dll.config file using any text editor (e.g. Notepad), and find the section enclosed by the <appSettings> …​ </appSettings> XML tags. Within these tags you must add the following new key:

<add key="VeckoPush.Enabled" value="?" />

  • Enabled - A value of true will enable the Vecko push feature on this media processing server.

The media processing server will need to be restarted after making this configuration change.