This is regarding CVP 9.0, here Media server is a dedicated separate server(not co-resident).
If any prompt gets missed out in Media server by user mistake, then VXML gateway(iOS browser) returns an error badfetch and caller is getting dropped abruptly after survivability.
Is there any option where this situation can be handled more gracefully through 'CVP studio' and 'VXML code', like caller moves to the next option bypassing that audio prompt and such event is logged so that necessary action can be taken timely?
I have received one problem regarding to the approach suggested by Chintan as below, your views ??
"We used Hot events in case of bad fetch due to communication problem between the components and bad fetch due to unavailability of resource.
But currently for any CVP application it is not recommended to handle bad fetch from application and same is not followed for any of the projects,
It is recommended to handle any bad fetch issues from ICM and the same is followed in current TTSL production system.
Cause : We found multiple call issue due to handling of bad fetch in the application which effected the reporting."
we are also using Hot event in CVP application to capture the error and will take appropriate action according to call flow.
But my CVP application quite complex and we want to know the name of audio file which is missing, so my support team can see the name of audio file in logs and replace the same in media server .
Could you please help, how to capture missing audio file name in cvp application instead of voice gateway?
Unfortunately, the VoiceXML Gateway doesn't return the URI of the
missing audio file to VXML Server.
So you have 3 options
1) Instead of looking in the VXML Server logs, monitor the IIS logs and
look for the 404 errors (C:\inetpub\logs\Logfiles\W3SVC1)
or 2) Instead of using the Audio element in Studio, use the element that
Paul Tindall posted on the DevNet forum - it allows you to specify that
the VXML Gateway should play the modified Audio element's audio to
completion. Therefore, 404 badfetch.http exceptions will be logged with
the audio element requesting them. This will at least point you in the
right direction - you'll know which Studio element requested the missing
or 3) Request the cisco modify the VXML Gateway's voice browser to
return the URI of the missing audio back to VXML Server to report.