4.40 - Cognigy Documentation

Documentation Index

Fetch the complete documentation index at: /llms.txt

Use this file to discover all available pages before exploring further.

With release 4.30.0, we have officially marked our Kubernetes repository as deprecated. If you are an on-premises customer and you are running Cognigy.AI/Cognigy Insights yourself, have a look at our Helm Chart, which we have crafted for Cognigy.AI/Cognigy Insights! Our Kubernetes repository will still receive updates until 31st December 2022.

4.40.3

Cognigy.AI

Released December 5, 2022

Bug Fixes

4.40.2

Cognigy.AI

Released November 30, 2022

Bug Fixes

4.40.1

Cognigy.AI

Released November 29, 2022

Bug Fixes

4.40.0

Cognigy.AI

Released November 29, 2022

Improvements

Bug Fixes

Cognigy Insights

Released November 29, 2022

Improvements

Bug Fixes

Cognigy Live Agent

Released November 29, 2022

Improvements

Bug Fixes

Webchat Widget

You can find the release notes for our Webchat Widget on GitHub as usual. The latest release of our Webchat Widget at the time of releasing all other Cognigy products is v2.44.0.

Infrastructure (AI + IN)

Stateful services

To improve the functionality and fix known security vulnerabilities in the dependencies of Cognigy.AI/Cognigy Insights uses, we have updated the following dependencies:

Important: Once you have upgraded to the new release containing the new RabbitMQ version, run the following command to rollout (restart) all Pods that run in your cluster:

for i in $(kubectl get deployment --namespace <target_namespace> --template '{{range .items}}{{.metadata.name}}{{"\n"}}{{end}}'|grep service-)
do
kubectl --namespace <target_namespace> rollout restart deployment $i
done

New service

This release also adds a new service called service-collector. This microservice will be used in the neare future to collect analytics information for Cognigy Insights so we can also ingest data from other Cognigy products such as Cognigy Live Agent and Cognigy Voice Gateway. Important: In case you have overwritten the replica-count (or other aspects) for specific services in your own values file, make sure that you also apply the same configuration for the new serviceCollector section in your values.

Config change

In case you are already using the call capabilities within the Cognigy.AI Interaction Panel, you have to make sure that you change the following ENV variable in the cognigyEnv configmap section:

VOICE_GATEWAY_PREPARE_CALL_API

from value: /api/v1/call/prepare to value: /api/v2/call/prepare. In addition, you have to set the following ENV variable so Cognigy Live Agent will be able to display attachments that have been uploaded through Cognigy.AI endpoints:

RUNTIME_FILE_MANAGER_CORS_WHITELIST

the value should be at least set to the frontend DNS name of the Cognigy Live Agent installation - an example value would be: https://dev-live-agent.cognigy.ai