When integrating SESTEK SR into your application, choosing the right method depends on your architecture, latency requirements, and deployment environment. This page compares the three available integration methods - HTTP, MRCP, and WebSocket - and helps you decide which fits your use case best.
Quick Comparison
.png?sv=2022-11-02&spr=https&st=2026-04-16T19%3A31%3A54Z&se=2026-04-16T19%3A43%3A54Z&sr=c&sp=r&sig=vowV5XlDSecnVPEtWzYcgg21F0wnxRGIZzxkgb6o%2FPA%3D)
HTTP (REST)
The HTTP integration method, also known as REST (Representational State Transfer), is the fastest integration method for your application. It allows communication between the client application and the Sestek SR system over the HTTP protocol. In this method, the client sends HTTP requests to the SR system's API endpoints to perform various speech recognition tasks.
The requests typically include audio data to be transcribed or processed. The SR system responds with the results or appropriate status codes. HTTP integration is commonly used for simple, request-response-based speech recognition applications.
Best for: Applications where the input language is known, the audio is pre-recorded or short, and real-time processing is not required.
MRCP
MRCP (Media Resource Control Protocol) is a protocol specifically designed for integrating speech recognition and synthesis technologies with voice application servers. It operates at the application layer of the TCP/IP stack and provides a standardized way to control media resources, such as speech recognition engines. MRCP is the de facto standard and is the recommended integration method for IVR systems (e.g., Avaya, Genesys, Cisco).
The client sends MRCP commands to the SR system to initiate speech recognition tasks or provide audio data for processing. The SR system responds with the results or appropriate MRCP status messages.
MRCP integration is commonly used in applications such as interactive voice response (IVR) systems, voice-enabled virtual assistants, speech analytics platforms, call center solutions, and various other voice-based services.
In case the IVR system you are using does not already support MRCP protocol, you need to use other integration methods. Implementing MRCP support for an IVR system is not an easy task. If your IVR does not already support MRCP and you have an active project, in most cases it will not be feasible to wait for MRCP support from your IVR vendor. Many IVR systems support making HTTP requests and many of them also provide audio recording functionality. If your IVR fits this case, you may try Rest Service integration.
Best for: IVR systems and call center platforms where telephony integration and real-time performance are critical.
WebSocket
WebSocket provides a persistent, bidirectional communication channel for real-time, full-duplex audio streaming. Unlike HTTP, the connection stays open, allowing continuous audio to be sent and transcribed with minimal delay.
WebSocket integration provides a bidirectional communication channel between the client and the Sestek SR system. It enables real-time, full-duplex communication, allowing both the client and server to send data asynchronously. The WebSocket protocol is designed to overcome the limitations of traditional HTTP by establishing a persistent connection that facilitates instant data exchange.
With WebSocket integration, the client can continuously stream audio data to the SR system, which can provide real-time transcriptions or responses. WebSocket integration is particularly useful for applications that require continuous speech recognition or interactive voice capabilities.
Best for: Applications that require low-latency, continuous speech recognition where results are needed as the speaker talks.
Choosing the Right Method
| If you need… | Use |
|---|---|
| Simple, one-shot transcription | HTTP |
| IVR or telephony integration | MRCP |
| Real-time or continuous streaming | WebSocket |
| Cloud deployment | HTTP or WebSocket |
| On-premises only | Any |
| Lowest implementation effort | HTTP |