In the case of playing audio we can supply TTS content like::
<prosody rate="-10%"> This is an existing element test </prosody>
Where the prosody element is injected into a <prompt> and passed to the TTS support.
Is it possible to define a custom element like ::
<resolve-as treatment="new"> This is a new element test </resolve-as>
and have the interpreter not throw and exception and inject the resolve-as element into a <prompt> and passed to the TTS support.?
Appreciate any ideas you might have for custom element support.
Some additional thoughts, questions.
In the case of the custom SSML element <resolve-as> is it possible to update the supporting SSML namespace to include the new element so it passes validation, or is there an option to prevent validation from being applied to the custom SSML element, or the parent element that contains the SSML?
Our objective is to simply have the <resolve-as> element pass validation and be passed to the configured TTS support.
CVP Passes the SSML to TTS for treatment, the SSML is verified against the syntax at TTS, did you tried using this tag in CVP studio, my guess is CVP and VXML Gateway will pass it but TTS will fail it, you need to check with TTS configuration to enable such element extension into TTS.
Please sign in to leave a comment.