Created by: Janine Graves on 29-05-2009 10:06:28 PM We have "vxml version 2.0" configured on the Gateways in order to get the beep, for "record after the beep" and to use the fetchaudiodelay vxml property.
However, with the "vxml version 2.0" setting, the Gateway does not throw return event when it cannot access a media file. So there's no way of knowing if the caller is hearing all the audio or not. I would like to receive the error.badfetch or error.badfetch.http event. Is there a workaround to force the gateway to throw the event?
Subject: RE: vxml version 2.0 no badfetch warning on missing audio Replied by: Ranjana Narayan on 04-06-2009 05:48:25 AM Hi Janine,
To have the error event thrown when audio playback fails ( while using vxml version 2.0), make use of the command "vxml audioerror" at global config mode.
Usage Guidelines: Entering this command causes an audio error event, error.badfetch, to be thrown when an audio file cannot be played, for instance, because the file is in an unsupported format, the src attribute references an invalid URI, or the expr attribute evaluates to an invalid URI. The vxml audioerror command overrides the vxml version 2.0 command, so that if both commands are entered, the audio error event will be thrown when an audio file cannot be played.
Hope this helps, Ranjana.
Subject: RE: vxml version 2.0 no badfetch warning on missing audio Replied by: WILLIAM WEBB on 04-06-2009 01:36:06 PM Ranjana - It looks like this comes right from some sort of reference guide. Is this type of information (available vxml parameters/settings) available in a Cisco document somewhere, or is this straight VXML specification, all of which may not necessarily be supported by Call Studio? It would be great to have this level of detailed information on tags, settings, parameters documented somewhere... - Bill
Subject: RE: vxml version 2.0 no badfetch warning on missing audio Replied by: Kamesh Chidambaram on 04-06-2009 04:54:45 PM Just what I was looking for. It worked right away. Thanks.
Subject: RE: vxml version 2.0 no badfetch warning on missing audio Replied by: Janine Graves on 04-06-2009 08:49:16 PM I just searched the ref manuals, and the vxml audioerror command is in the "Cisco IOS Tcl IVR and VoiceXML Application Guide Cisco IOS Release 12.4(15)T" reference manual.
Hi there, Actually I have catched events based on API Guide 12.0.For this lab functions working properly.There is 2 Participants with their states.How to take particular Participant with their state.I have han...
Hi there, Suppose Agent001 is in Ready(userstate) state while Agent002 is in Not_ready(userstate) state. Agent002 makes call to Agent001,Agent001 answers the call & now they are in Talking(userstate) state...
I'm doing an addUser with this content (stripped the soap headers for brevity)<user>
Hi,I don't know if this is the right place to ask that question.Two clients encounter an error when adding a DX80 terminal using the AXL on his CUCM 12.5.The error is "Vendor Configuration is not in correct format for the specified product type".I didn't ...