Created by: Vijay Jayaraman on 04-03-2009 11:58:22 AM Hi, I would like to know if the Cisco Voice browser sends the hangup event to the VXML Server, for call disconnect , the VXML2.0 specification defines the event "connection.disconnect.hangup". I'm trying to use the 'Hotevent' element to do a after call logging and mentioned the above event name. I know there is other way of doing it, is using the CallEndAPI class, but is it possible to use the call disconnect event to do some logging. thanks, Vijay
Subject: RE: Disconnect event in CVP Replied by: Ranjana Narayan on 06-03-2009 10:50:15 AM Hi Vijay,
I believe, you should be able to write a Hotevent for connection.disconnect.hangup, and override the default behavior provided in the rootdoc of the application. But, you will need to take care that the exit callflow of the hotevent or the hotevent itself doesnot generate any audio vxml since there is no caller, and the callflow should end with a Subdialog return or an element that would generate a disconnect event. One thing to note would be that the "how call ended" willnot be "hangup" anymore.
I would still suggest making use of the CallEndAPI to do the logging instead of making use of the Hotevent, since its easier to understand the flow, and if required easier to debug/troubleshoot.
Hope this helps, Ranjana.
Subject: RE: Disconnect event in CVP Replied by: Vijay Jayaraman on 11-03-2009 06:19:32 PM Hi Ranjana, I've the Hotevent defined for "connection.disconnect.hangup", which has the exit state to a Action element doing the logging followed by the Subdialog Return element. I'm pretty much aware that once the VXML hangup event is triggered in the Voice browser(the life of the call ends there), jus the event is notified to the VXML Server(CallServices) and NO audio related stuff could be executed. On testing the callflow, I purposefully hangup the call during the call traversal, and the app logs DOESN'T show the Hotevent is triggered or no such signs. The log jus shows, 12:49:03,,end,how,hangup 12:49:03,,end,result,normal 12:49:03,,end,duration,93 Ofcourse, I do agree the simple workaround would be using the CallEnd API class. But I'm little curious to figure out why the CVP is not behaving as expected, or is it anything that I'm missing. Btw, I didn't get from your statement, "One thing to note would be that the "how call ended" willnot be "hangup" anymore." thanks, Vijay
Subject: Re: New Message from Vijay Jayaraman in Customer Voice Portal (CVP) - Gener Replied by: Janine Graves on 11-03-2009 06:36:57 PM The event you have to catch is telephone.disconnect.hangup
Cisco Developer Community Forums wrote: > Vijay Jayaraman has created a new message in the forum "General > Discussion - All Versions": > > -------------------------------------------------------------- > Hi Ranjana, >  >          I've the Hotevent defined for > "connection.disconnect.hangup", which has the exit state to a Action > element doing the logging followed by the Subdialog Return > element.  I'm pretty much aware that once the VXML hangup event is > triggered in the Voice browser(the life of the call ends there), jus > the event is notified to the VXML Server(CallServices) and NO audio > related stuff could be executed. >  >          On testing the callflow, I purposefully hangup the > call during the call traversal, and the app logs DOESN'T show the > Hotevent is triggered or no such signs.  The log jus shows, >  > 12:49:03,,end,how,hangup > 12:49:03,,end,result,normal > 12:49:03,,end,duration,93 >  >         Ofcourse, I do agree the simple workaround would be > using the CallEnd API class. But I'm little curious to figure out > why the CVP is not behaving as expected, or is it anything that I'm > missing. >  >         Btw, I didn't get from your statement, "*One thing > to note would be that the "how call ended" willnot be "hangup" anymore."* >  > thanks, > Vijay > -- > To respond to this post, please click the following link: > > <http://developer.cisco.com/web/cvp/forums/-/message_boards/message/1175063> > > or simply reply to this email.
Subject: Re: New Message from Vijay Jayaraman in Customer Voice Portal (CVP) - Gener Replied by: Janine Graves on 19-03-2009 05:36:57 PM Vijay, Thanks for the feedback.
I think telephone.disconnect.hangup was the event name for hangup in vxml 1.0 - so perhaps cisco just hasn't gotten around to updating to the Vxml 2.0 event name yet.
Cisco Developer Community Forums wrote: > Vijay Jayaraman has created a new message in the forum "General > Discussion - All Versions": > > -------------------------------------------------------------- > Janine, >  >          Thanks for the right event name, YES , it works > for 'telephone.disconnect.hangup", so why is that VXML2.0 > specficiation shows the disconnect event as > 'connection.disconnect.hangup". >  >  > regards, > Vijay > -- > To respond to this post, please click the following link: > > <http://developer.cisco.com/web/cvp/forums/-/message_boards/message/1199898> > > or simply reply to this email.
Subject: RE: Re: New Message from Vijay Jayaraman in Customer Voice Portal (CVP Replied by: Vijay Jayaraman on 19-03-2009 05:31:18 PM Janine, Thanks for the right event name, YES , it works for 'telephone.disconnect.hangup", so why is that VXML2.0 specficiation shows the disconnect event as 'connection.disconnect.hangup". regards, Vijay
Subject: RE: Re: New Message from Vijay Jayaraman in Customer Voice Portal (CVP Replied by: Ranjana Narayan on 20-03-2009 03:03:24 AM Hi,
Thanks Janine for the info.
The Cisco GW IOS has not be been updated to throw connection.disconnect.hangup when working with VXML 2.0, it still throws telephone.disconnect.hangup as per pre-vxml 2.0
The "how call ended" without the Hotevent would be "hangup", but with the Hotevent in the picture, the "how call" would vary based on how you choose to end the call after handling the hangup event.
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:
