Integrations
- 19 Jul 2024
- 2 Minutes to read
- Contributors
- Print
- PDF
Integrations
- Updated on 19 Jul 2024
- 2 Minutes to read
- Contributors
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Integration Methods Comparison
When integrating text-to-speech (TTS) capabilities into your applications, it's essential to choose the right integration method that best suits your needs. Below, we compare two primary integration methods: HTTP (REST) and MRCP. Each method has its unique advantages and drawbacks, as well as specific use cases where they shine.
This table will help you understand which method to use under different circumstances, ensuring optimal performance and compatibility for your TTS tasks.
| Integration Method | Description | Use Cases | Pros | Cons | Availability |
|---|---|---|---|---|---|
| HTTP (REST) | REST (Representational State Transfer) is an architectural style for designing networked applications. In the context of Knovvu TTS, REST integration involves using HTTP requests to interact with the TTS system and obtain synthesized speech output. | ▪️ Simple, request-response-based TTS applications. ▪️ Web applications needing speech synthesis. ▪️ Mobile apps converting text to speech. ▪️ Systems requiring batch processing of text data. ▪️ Any system with limited real-time requirements. | ▪️ Easy to implement. ▪️ Wide compatibility. ▪️ Stateless operations. ▪️ Well-suited for both on-premises and cloud solutions. ▪️ Works with systems supporting HTTP requests. | ▪️ Limited to request-response communication. ▪️ Not ideal for real-time or continuous speech processing. ▪️ Potential latency issues for large text data. | ▪️ On-premises ▪️ Cloud solutions |
| MRCP | MRCP (Media Resource Control Protocol) is designed for controlling media processing resources in real-time communication applications. In the context of Knovvu TTS, MRCP integration allows your application to request and control the synthesis of speech in a more interactive manner. It is the recommended integration method for IVR systems (e.g., Avaya, Genesys, Cisco). | ▪️ IVR systems (e.g., Avaya, Genesys, Cisco). ▪️ Voice-enabled virtual assistants. ▪️ Speech analytics platforms. ▪️ Call center solutions. ▪️ Telephony applications. ▪️ Any application requiring standardized control over media resources. | ▪️ Industry-standard for IVR. ▪️ Seamless integration with telephony systems. ▪️ High performance for voice-based applications. ▪️ Real-time speech processing. ▪️ Scalability in telephony environments. | ▪️ Complex to implement. ▪️ Requires IVR systems with MRCP support. ▪️ Not available in cloud solutions. ▪️ High implementation cost. ▪️ Longer development time. | ▪️ On-premises solutions only |
Integration Methods Overview
1. HTTP (REST)
REST (Representational State Transfer) is an architectural style for designing networked applications. In the context of Knovvu TTS, REST integration involves using HTTP requests to interact with the TTS system and obtain synthesized speech output.
2. MRCP
MRCP (Media Resource Control Protocol) is a protocol designed for controlling media processing resources in real-time communication applications. In the context of Knovvu TTS, MRCP integration allows your application to request and control the synthesis of speech in a more interactive manner. It is the recommended integration method for IVR systems (e.g., Avaya, Genesys, Cisco).
IVR Compatibility Note: 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.
Was this article helpful?