The Media Resource Control Protocol is a standard method for communicating across multiple applications. It is used primarily for telephony platforms to control applications like automatic speech recognition engines (ASR) and text-to-speech engines (TTS). MRCP provides a standards-based alternative to API-level integration of these resources. For more information, please see our whitepaper describing the differences between API and MRCP integrations.
Note that you will not need to use MRCP if your platform has already done an API-level integration of LumenVox. If you are uncertain, please contact your platform provider or LumenVox technical support for more information.
In order to use the LumenVox Speech Engine over MRCP, you must install the Speech Engine and License Server as usual, but you must also install a LumenVox MRCP Server. This server sits between an MRCP client (the application platform) and the Speech Engine, handling MRCP communications from the client and passing requests to the Engine for decode.
MRCP comes in two versions, version one and version two. The two are similar, but incompatible. MRCPv1 uses RTSP as its control protocol while MRCPv2 uses SIP, so you must download the correct MRCP Server for the version you wish to use.
For the complete MRCPv1 specification, you may refer to RFC #4463.
MRCPv2 is still a working draft, but the latest revision is available online. As it is a working draft, the LumenVox MRCPv2 Server should be considered something of a beta product whose behavior may change as the standard does.
To get started working with MRCP, please see Installing the MRCPv1 Server or Installing the MRCPv2 Server.
Complete Help Topic List | Speech Engine Product Information