You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 25, 2024. It is now read-only.
We have observerd several restarts of the feature-server - container freeSWITCH.
It seems it it caused through several esacape characters within a text when performing text to speech via streaming and Microsoft.
Expected: freeSWITCH does not crash when using SSML with escape characters
"say": {
"text": "<speak version=\"1.0\" xmlns=\"[http://www.w3.org/2001/10/synthesis\"](http://www.w3.org/2001/10/synthesis%5c%22) xml:lang=\"de-DE\"><voice name=\"de-DE-KatjaNeural\">Kann ich Sie einmal zu einem Mitarbeiter durchstellen?\r</voice></speak>",
"disableTtsCache": false
}
// Microsoft
<speak version="1.0" xmlns="http://www.w3.org/2001/10/synthesis" xml:lang="en-US"><voice name="en-US-AriaNeural">Hello world \r welcome to \t \n a new chapter</voice></speak>
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We have observerd several restarts of the feature-server - container freeSWITCH.
It seems it it caused through several esacape characters within a text when performing text to speech via streaming and Microsoft.
Expected: freeSWITCH does not crash when using SSML with escape characters
The text was updated successfully, but these errors were encountered: