In Audium 3.3, SSML is partially supported and in the next version of Audium it is fully supported. Let me explain;

In Audium 3.3, you can enter SSML directly in the TTS text box in the Builder. The Server will then take this content as is and place it inside a CDATA tag within the <prompt> tag. Now, your browser and TTS engine must be able to understand how to read this SSML, since it is not part of the VoiceXML page itself (the SSML would need to be parsed separately once it is extracted from the CDATA). That is why we say it is partially supported as it will only work with browsers that can take SSML this way. If a browser required the SSML to be found directly within the VoiceXML, Audium 3.3 does not support this.

In the next version of Audium, any SSML you enter in the Studio TTS text box will be put directly in the VoiceXML produced by Call Services. If you are using a browser that still requires SSML within CDATA, the user can enter the CDATA himself in Studio and it will be put into the produced VoiceXML that way. So we leave the choice up to the user of what to do. Note that Audium does not parse the SSML to check for mistakes (Call Services will complain if the data types does not make correct XML and the browser will complain if the data does not make correct SSML) so the user is responsible for making sure that content is correct. Additionally, the user is responsible for typing in the SSML themselves, there is no editor or code generator for SSML.

Elam