Created by: Mert Guray on 13-12-2009 02:08:28 PM Hello, On our ASR Call Studio application (V 6.0) we were catching hotEvents of -error.com.cisco.media.resource.unavailable.asr-. This is because gateway is receiving "speech-too-early" from ASR engine (Nuance 8.5) frequently and this reaches our VXML application as the event above. After realising that we are also receiving no-resource error as well, we added the error.noreasource as a hot event too. After that no unavailbale.asr was caught. Instead all the events appeared as error.noresource. I wouldn't think of these two events having a hierarchical relation. Is there? Is there anyone who has an idea?
Subject: Re: New Message from Mert Guray in Customer Voice Portal (CVP) - General Di Replied by: Janine Graves on 13-12-2009 02:26:10 PM Here are 2 possible explanations, perhaps someone at Cisco can verify or clarify.
Possibility 1) I would agree that in general VXML events are distinct. But, the error.com.cisco.media.resource.unavailable.asr is a Cisco-specific event. And it's possible that this event is only returned to the VXMLServer if the standard events (.eg., error.noresource) aren't handled.
Possibility 2) If you look in the 'root document' (which I'll paste below) that VXML Server creates for each application and each phone call, it has a <catch> handler for every possible 'event' that can occur.
In that root document, <catch event="error.noresource"> is above <catch event="error.com.cisco.media.resource.unavailable.asr"> in 'document order' (the order the code appears on the page). In VXML, only one catch handler is executed when an error occurs, and it's the one with the best match, 'in document order'.
Cisco Developer Community Forums wrote: > Mert Guray has created a new message in the forum "General Discussion > - All Versions": > > -------------------------------------------------------------- > Hello, > On our ASR Call Studio application (V 6.0) we were catching hotEvents > of -error.com.cisco.media.resource.unavailable.asr-. This is because > gateway is receiving "speech-too-early" from ASR engine (Nuance 8.5) > frequently and this reaches our VXML application as the event above. > After realising that we are also receiving no-resource error as well, > we added the error.noreasource as a hot event too. After that no > unavailbale.asr was caught. Instead all the events appeared as > error.noresource. I wouldn't think of these two events having a > hierarchical relation. Is there? > Is there anyone who has an idea? > -- > To respond to this post, please click the following link: > > <http://developer.cisco.com/web/cvp/forums/-/message_boards/message/1837757> > > or simply reply to this email.
Subject: RE: Re: New Message from Mert Guray in Customer Voice Portal (CVP) - Genera Replied by: Mert Guray on 13-12-2009 03:42:48 PM I understand the first explanation. So according to that there is nothing to be done. If we want to catch a cisco specific event then we have to take off all the standart event handlers. It doesn't sound good to me. For the second explanation, i couldn't see the "<catch event="error.com.cisco.media.resource.unavailable.asr">" expression. sorry if i am missing something. And is this root documentation a general one or is it being specified with the application.
Subject: Re: New Message from Mert Guray in Customer Voice Portal (CVP) - General Di Replied by: Janine Graves on 13-12-2009 04:34:10 PM As part of the VXML Specification, it says that if an event like error.com.cisco.media.resource.unavailable.asr is also eligible to be handled by a <catch> handler that specifies any prefix (up to a dot in the event name) of the event that occurs.
So, if error.com.cisco.media.resource.unavailable.asr occurs, then all of the following event handlers are eligible to catch that event: <catch event="error.com.cisco.media.resource.unavailable.asr"> <catch event="error.com.cisco.media.resource.unavailable"> <catch event="error.com.cisco.media.resource"> <catch event="error.com.cisco.media"> <catch event="error.com.cisco"> <catch event="error">
And the first one in document order (assuming they're all listed in the root document) will be the one that 'wins' and handles that event when it occurs.
The RootDocument that I pasted is standard for all Studio applications. It's created by VxmlServer.
But, if you have HotLinks or HotEvents in your application, or if you set Root Docuement Properties (under Project/Properties of the Studio app) then the root doc is altered.
The sample that you saw showed some custom HotLinks that I had in my Studio application (and the documentation notes were mine).
Similarly, if you have a custom handling for a HotEvent (like to re-direct the code to send the caller back to ICM or to an agent), then you'd see your HotEvent show up as a specific handler (eg, <catch event="error.noresource">), rather than seeing Cisco's handler.
What you'd actually see is something that does a <submit> back to '/CVP/Server' the name of your HotEvent element which handles that event. Then Vxml Server knows to jump to your HotEvent element.
Again, I don't work for Cisco and don't know how its voice browser decides which event to handle or which event name to return to the application. I'm hoping someone at Cisco can fill in more details.
Cisco Developer Community Forums wrote: > Mert Guray has created a new message in the forum "General Discussion > - All Versions": > > -------------------------------------------------------------- > I understand the first explanation. So according to that there is > nothing to be done. If we want to catch a cisco specific event then we > have to take off all the standart event handlers. It doesn't sound > good to me. > For the second explanation, i couldn't see the "<catch > event="error.com.cisco.media.resource.unavailable.asr">" expression. > sorry if i am missing something. And is this root documentation a > general one or is it being specified with the application. > -- > To respond to this post, please click the following link: > > <http://developer.cisco.com/web/cvp/forums/-/message_boards/message/1837797> > > or simply reply to this email.
Subject: RE: Re: New Message from Mert Guray in Customer Voice Portal (CVP) - Genera Replied by: Mert Guray on 14-12-2009 07:42:48 AM Thanks Janine. I got your point. One last question, where can i get my own root document? Did you get it from debugger log? I would like to check how is it like on our side.
Subject: RE: Re: New Message from Mert Guray in Customer Voice Portal (CVP) - Genera Replied by: Ranjana Narayan on 14-12-2009 10:26:40 AM Mert, Yes, you can look at the Root doc by enabling Debugger. With certain ES applied, the root doc content might vary. Hth, Ranjana.
Subject: Re: New Message from Mert Guray in Customer Voice Portal (CVP) - General Di Replied by: Janine Graves on 14-12-2009 06:23:10 PM you have to turn on debug logging. the root document will be near the top of the log.
Cisco Developer Community Forums wrote: > Mert Guray has created a new message in the forum "General Discussion > - All Versions": > > -------------------------------------------------------------- > Thanks Janine. > I got your point. One last question, where can i get my own root > document? Did you get it from debugger log? I would like to check how > is it like on our side. > -- > To respond to this post, please click the following link: > > <http://developer.cisco.com/web/cvp/forums/-/message_boards/message/1838371> > > or simply reply to this email.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: