MRCP IVR Proxy is meant to be used in scenarios where an on-prem VXML Platform or a telephony platform like FreeSWITCH needs to communicate with Voicegain ASR in the cloud. This is not our recommended setup for production. However, it works fine for testing and low volume apps with up to 5 concurrent sessions. The recommended setup is to deploy the complete Voicegain platform (including MRCP server) on-prem into a Kubernetes cluster or a docker container. While a setup with MRCP IVR Proxy will work, it will by impacted by any Internet packet loss (as it uses UDP/RTP for audio), latencies, etc.
The image above shows how MRCP IVR Proxy fits in-between VXML/Telephony platform and Voicegain Cloud. Note that when you install MRCP IVR proxy using docker-compose you are installing a complete unimrcp server with Voicegain STT plugin and the proxy that talks to Voicegain in the Cloud. The communication from proxy to the Cloud is via TCP for the MRCP command channel, and via UDP for the audio channel.
Install of MRCP IVR Proxy is easy and is described in these two knowledge base articles:
The prerequisite on both platforms is Docker. Once a docker compose is launched using downloaded files it will pull from Voicegain docker repository images for unimrcp and the Proxy. The install requires additional configuration in cases where HTTP traffic goes via HTTP Proxy,
Hardware machine or VMs with 2 CPUs and 4GB RAM is recommended.
[Coming within next few months: We are working on a different version of Voicegain unimrcp plugin which will communicate with Voicegain ASR directly using gRPC thus not requiring a Proxy. If you are particularly interested in that solution, please let us know at email@example.com]