Media Resource Control Protocol: Difference between revisions

Revision as of 14:18, 19 October 2011

Revision as of 09:30, 14 November 2012

Line 6:

Like HTTP, MRCP uses a request (usually issued by the client) and response model. Responses 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 message containing a suitable [[port number]] to send the data, since MRCP does not have support for audio data specifically as this would have to be handled by some other protocol, such as [[Real-time Transport Protocol]] (RTP).

Currently an [[InternetRequest Draftfor Comments|RFC]] has been approved of MRCP protocol version 2 has been submitted. Version 2 uses [[Session Initiation Protocol|SIP]] for managing sessions and audio streams between the server and the clients, whereas version 1 did not specify the underlying protocol.

MRCP has been adopted by a wide range of commercial voice applications, such as [[IBM WebSphere Voice Server]], [[Microsoft Speech Server]], [[LumenVox Speech Engine]], [[Nuance Recognizer]], and [[Nuance Vocalizer]].

Line 12:

==External links==

* RFC 4463, A Media Resource Control Protocol (MRCP)

* RFC 6787, A Media Resource Control Protocol version 2 (MRCPv2)

* [http://www.unimrcp.org UniMRCP], An open source cross-platform MRCP implementation