Media Resource Control Protocol: Difference between revisions

Revision as of 17:59, 8 November 2006

Revision as of 11:16, 11 November 2006

Line 5:

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 [[TCP and UDP port|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 [[Real-time Transport Protocol|RTP]]).

==External links==

{{Uncategorized|November 2006}}

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

[[Category: Internet protocols]]

{{compu-soft-stub}}