CVG 1.26.1 (23-Jan-2023)

A small update to add a new endpoint to stop playbacks and to fix some login issues.

Stop a Playback

New Endpoint to stop a Playback

Sometimes it is necessary to stop a running playback. This makes it possible, for example, to play music on hold while the bot fetches information from slowly responding back-end systems. Once this information is available, the bot can stop the playback and respond.

You can now use the new endpoint /call/play/stop to stop a playback.

Stops all Playbacks of given Audio File immediately

/call/play/stop stops all playbacks with the given URL (= audio file), regardless of whether they're currently active or still queued.

This operation is not subject to queuing. I.e. running and queued playbacks with the specified URL are immediately stopped / taken out of the queue.

New Node in “VIER Voice” extension for Cognigy to stop a Playback

A new node to stop playing an audio file has been made available in our “VIER Voice” extension in Cognigy.

If version “VIER Voice, 4.3.0” is available in the Cognigy Marketplace (in Cognigy select an Agent and then “Manage -> Extensions”) just install / update to this version.

As long as the new version is not yet available in the Cognigy Market Place for Extensions, it can also be downloaded here. You can update to this version in Cognigy as follows:

  • If the “VIER Voice” extension is not yet installed in the agent in Cognigy, install it (”Manage -> Extensions”).

  • Click on the installed extension “VIER Voice”, select “Update” and confirm with “Confirm”.

  • Select the file vier_voice.tar.gz downloaded as described above and click “Open”.

  • Wait until the new version 4.3.0 of the “VIER Voice” extension from Cognigy is installed. That’s it. Have fun.

Don’t worry if you have built your flows with an older version of the “VIER Voice” extension - your existing nodes will be updated automatically.

Bug Fixes

UI: Login stopped while loading

In rare cases it happened that a login to the UI did not work. A reload or even deletion of all parameters at the URL https://cognitivevoice.io was necessary. This error has now been fixed.