New Call Flow Designer for V18 Update 2

[edossantos]

Following the release of v18 Update 2, we have also updated the Call Flow Designer (CFD). Now audio files generated through text to speech are cached in the 3CX server, so subsequent requests to convert the same text are resolved locally. We’ve also added components to allow you to parse CSV text without using a C# script, or to transcribe audio ...

Continue reading the Original Blog Post.

 

[FridayIT]

"When 3CX needs to convert text to speech, it will first check if a WAV file for the same voice and text is already available. If so, the existing WAV file will be played, otherwise the text to speech operation will be triggered, and the result added to cache. This reduces the response time, and allows you to save money, when playing the same text over and over, for example for menu options or any static prompt."

This seems to be a huge win for TTS support. I suspect a large amount of TTS would be "cachable" in a lot of instances.

 

[edossantos]

This seems to be a huge win for TTS support. I suspect a large amount of TTS would be "cachable" in a lot of instances.

Yes, this way users will save a lot of money in TTS charges, especially for those using TTS for static prompts, like menu options.