Media Resource Control Protocol: Difference between revisions

Revision as of 06:04, 15 May 2009

Revision as of 19:26, 15 May 2009

Line 4:

MRCP uses a similar style of clear-text signaling as [[HTTP]] and many other Internet protocols, in which 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 '''<header>: <data>'''. The body, whose length is specified by the header, contains the details of the message.

Like HTTP, MRCP hasuses requestsa request (usually issued by the client) and responses,response whichmodel. 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 suitablemessage [[TCPcontaining anda UDPsuitable [[port|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).

There are two versions of the MRCP protocol. Version 2 uses SIP as the control protocol, whereas version 1 uses RTSP.

Line 10:

==External links==

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

* [http://tools.ietf.org/html/draft-ietf-speechsc-mrcpv2-18 MRCP version 2 IETF draft specification, version 18] (Internet Draft page expires 06 NOV 2009)

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

[[Category: Internet protocols]]