| Login | |||||||
|
|
|
HOME | ABOUT US | DOWNLOADS | CONTACT US | SITEMAP |
|
| the technology you need to win! |
|
||||||
|
 |
||||
| Industry Standards |
|
MRCP for Speech MRCP is a protocol for PBX, IVR, Media Servers, etc. to communicate with ASR and TTS engines. Typically, this means the server software (ASR and TTS Engines) will be running on one server / computer and clients (PBX, IVR, Media Servers, etc) can send MRCP messages to the server over a network, usually on top of another protocol, such as RTSP or TCP. In version 1 of the MRCP spec, RTSP is used for session setup and RTP used for media streaming, whereas in version 2 of the MRCP spec, SIP is used instead of RTSP for session setup (RTP still used for media streaming). It is in the same style as HTTP and many other Internet protocols, where each message contains 3 sections: a first-line, a header and a body. The first line indicates the type of message as well as information such as response codes. The header contains a number of lines, each in the format Like HTTP, MRCP has requests (usually issued by the client) and responses, which may simply acknowledge receipt of the request or give other information regarding its processing. For example, an MRCP client may request to send some audio data for processing (say, for speech recognition), to which the server could respond with a suitable port to send the data (since MRCP does not have support for audio data specifically, this would have to be handled by some other protocol, such as RTP). Phonologies will release InterpreXer™ v4.0 in Q2 2008 with support for MRCPv2. |
||
|
©2001-2008 Phonologies (India) Private Limited. All Rights Reserved
Privacy Policy |