The following list explains the MRCP capabilities that are supported with VBVoice:
Separate configurations for ASR and TTS resources: this gives the application developer the freedom to pick the ASR and TTS servers that best suit their needs.
Multiple MRCP servers: applications can use multiple MRCP servers at the same time to equally balance their loads. VBVoice, by default, will round-robin through them while the application can apply any load balancing algorithm to override the default.
Separation between Pronexus MRCP Client (called VbvMrcpClient) and the VBVoice application: this offers more reliability by decoupling the VBVoice applications from the client so the applications would keep working using DTMF if MRCP functionality fails for any reason.
Pronexus MRCP Client provides its own logs and is able to operate on its own. It provides extensive logs and errors and can do its own self test (the self test functionality is currently only provided for TTS resources).
Many settings to tweak responsiveness and quality of recognition and TTS play back.