
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-12-2016 01:51 AM
Dear members,
I noticed some badfetch errors in one of the deployed vxml applications logs.
After doing some research, I realized that these errors can be handled by using HotEvent nodes in Call Studio but I haven't come across any threads that shows an example of how to use this element and where should it be added in the script.
Attached is a very basic script I was trying to develop in order to catch badfetch errors and let the caller hear an audio file and then be transferred to an agent instead of having his call ended after the badfetch.
Can someone please shed some light on how to correctly use this element.
Any help is highly appreciated.
Thank you in advance.
Lara
Solved! Go to Solution.
- Labels:
-
Customer Voice Portal
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-02-2016 05:39 AM
try to put error.badfetch.http.404 in event.
ideally event should be same as the error you see in your activity log.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-02-2016 05:39 AM
try to put error.badfetch.http.404 in event.
ideally event should be same as the error you see in your activity log.
