Call Studio VXML Gateway Type and using TTS for bad fetch failures

[AudraShumaker57878]

Need some help understanding some interactions that are not well documented.

The expectation is that if there is a media 'bad fetch' event, that Nuance TTS will play the audio transcribed in the audio element. The gateways and OAMP are configured per the CVP guide for Nuance TTS- however inside the studio application there are questions.

1) Does the voicexml gateway type in the General properties need to be set to VoiceXML2.1 with Nuance 10 to make TTS function or is this built in? (License concerns here)
2) would the TTS function still work if the voicexml gateway type is set to VoiceXML2.1 with Cisco DTMF since there is no explicit reference in the call studio application?

3) would catching the 'badfetch event' break this TTS as a backup mechanism ? 

The standard Cisco document describes using TTS as backup but doesn't cover the voicexml gateway setting.

[janinegraves · Accepted solution]

1) Does the voicexml gateway type in the General properties need to be
set to VoiceXML2.1 with Nuance 10 to make TTS function or is this built
in? (License concerns here) -

NO - the General Settings in Call Studio Project/Properties is just for
caller input. Not for outgoing audio.
If your VVB or IOS VXML GW is configured to know where the TTS server
is, then you can just enter text in the TTS box in Studio and it'll play.


2) would the TTS function still work if the voicexml gateway type is set
to VoiceXML2.1 with Cisco DTMF since there is no explicit reference in
the call studio application?

It doesn't matter. VXML 2.1 or VXML 2.0 should work. There may be a few
VXML2.1 markup tags (like a 'foreach' or setting a marker within a long
TTS prompt) but Studio elements don't use these, so it shouldn't matter.

3) would catching the 'badfetch event' break this TTS as a backup
mechanism ?

NO - if you have audio with backup TTS configured, the error.badfetch
event won't be thrown to Studio/VXMLServer because the caller was able
to hear something. So it's treated as success. You'll see 404 in the IIS
logs, but that's all.