This document was generated from CDN thread
Created by: null on 01-11-2006 10:47:34 PM
Hi
Currently we made some changes in our lab. Now we have ICM 6.0, SR 8 and our Gateway version is 12.4(3b) in our lab environment.
We had a CVP application in our lab which was catching a bad fetch event thrown and was doing some processing after that. After the recent changes we made, we were just testing our that application again. We found that the Hotevent element is not being recognized in any case.
I have tested in sveral ways, but looks like it does not recognize the Hotevent element at all.
Can you please help us with this ?
Thanks
Mamta
Subject: RE: Hotevent element not working
Replied by: Michael Bochynski on 01-11-2006 11:30:05 PM
Hi Mamta,
Please contact Cisco TAC Support for support related to the Cisco CVP VoiceXML Server as well as Cisco voice browser.
Regards,
Michael
Subject: RE: Hotevent element not working
Replied by: Janine Graves on 16-11-2006 03:17:21 AM
If you look at the root document that's created by audium, you'll see that they catch error.badfetch.http before error.badfetch.
If you have a hotlink that catches error.badfetch but an error.badfetch.http event occurs - then the event will be handled by the audium handler for error.badfetch.http, not yours for error.badfetch.
So, to get around this, you must have a hotlink that catches error.badfetch.http (and another for error.badfetch.https - if you're using https).
I've tried this and it catches all the error.badfetch.http (like 401, 404, etc) events.
Good luck, Janine
