Media Resource Control Protocol: Difference between revisions

Content deleted Content added
No edit summary
 
m {{compu-soft-stub}}
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 [[port (computing)|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]]).
 
{{compu-soft-stub}}