cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

Cisco Community Designated VIP Class of 2020

Handling Disconnect Event's

520
Views
0
Helpful
0
Comments

Subject: Re: New Message from prince christopher joseph in Customer Voice Portal (CV
Replied by: Janine Graves on 10-03-2011 06:20:10 PM
You do NOT need to handle any conditions or events in Studio if you want
to release the vxml server license. The ICM script exits immediately
when the caller hangs up by default.

If you need to do logging from the VxmlServer app or to pass data back
to ICM when the caller hangs up, then you'll have to add some custom
EndOfCall Java code to the Studio application (see Project
/Properties/EndPoint Settings in Studio or in the Programming Guide for
Studio and VxmlServer'). On end of call, the java code has access to
'how the call ended' so it can determine if the caller hung up.




On 3/10/2011 5:54 PM, Cisco Developer Community Forums wrote:
> prince christopher joseph has created a new message in the forum "CVP
> - All Versions":
>
> --------------------------------------------------------------
> What is the best practive in Cisco CVP to handle disconnect events ? 
> Iam using HotEvent block to capture "connection.disconnect.hangup" the
> event and use hangup block to end the session , The CVP application is
> been invoked by ICM Scripts.
> Â
> Also facing issue with this methodology , when ever i disconnect the
> call , the vmxl session is not ending so we lose one of CVP port.
> Â
> Do i need to send a response back to ICM about the disconnect ???
> Â
> Need your suggestions
> Â
> Thanks
> Â
> Â
> --
> To respond to this post, please click the following link:
>
> <http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/3159794>
>
> or simply reply to this email.

--
Janine Graves
This document was generated from CDN thread

Created by: prince christopher joseph on 10-03-2011 05:54:33 PM
What is the best practive in Cisco CVP to handle disconnect events ?  Iam using HotEvent block to capture "connection.disconnect.hangup" the event and use hangup block to end the session , The CVP application is been invoked by ICM Scripts.
 
Also facing issue with this methodology , when ever i disconnect the call , the vmxl session is not ending so we lose one of CVP port.
 
Do i need to send a response back to ICM about the disconnect ???
 
Need your suggestions
 
Thanks
 
 

Subject: RE: Handling Disconnect Event's
Replied by: prince christopher joseph on 11-03-2011 04:32:09 PM
What is the best practive in Cisco CVP to handle disconnect events ?  Iam using HotEvent block to capture "connection.disconnect.hangup" the event and use hangup block to end the session , The CVP application is been invoked by ICM Scripts.
 
Also facing issue with this methodology , when ever i disconnect the call , the vmxl session is not ending so we lose one of CVP port.
 
Do i need to send a response back to ICM about the disconnect ???
 
Need your suggestions
 
Thanks
 
 

Subject: Re: New Message from prince christopher joseph in Customer Voice Portal (CV
Replied by: Janine Graves on 11-03-2011 04:43:10 PM
As I mentioned, you should NOT handle telephone.disconnect.hangup or
connection.disconnect.hangup - the VXML Server will know if the caller
hangs up and will free the VxmlServer license immediately. If you then
execute status.bat script - you will see the license has been freed and
'one session is ending' - this is just a delay on vxmlserver in case you
are executing some 'end of call' java code and need access to the
variables from the call flow - so they don't delete the session's
variables for about 60seconds. BUT - the license is definitely freed
immediately.

Simultaneously, the gateway automatically alerts ICM that the caller
hung up and ends the ICM routing script immediately.

By default, you can't send anything back to ICM on a hangup.

If you need to respond in some way when the caller hangs up (either by
writing to a DB, or by sending data back to ICM into its FromExtVxml
array) - then you must write custom java that executes OnEndCall. This
code executes no matter how the visit to the application ends (hangup,
error, app transfer, normal, etc).

See the CVP VXMLServer and Studio Programmers Guide for more information
on this.

Janine





On 3/11/2011 4:32 PM, Cisco Developer Community Forums wrote:
> prince christopher joseph has created a new message in the forum "CVP
> - All Versions":
>
> --------------------------------------------------------------
> What is the best practive in Cisco CVP to handle disconnect events ? 
> Iam using HotEvent block to capture "connection.disconnect.hangup" the
> event and use hangup block to end the session , The CVP application is
> been invoked by ICM Scripts.
> Â
> Also facing issue with this methodology , when ever i disconnect the
> call , the vmxl session is not ending so we lose one of CVP port.
> Â
> Do i need to send a response back to ICM about the disconnect ???
> Â
> Need your suggestions
> Â
> Thanks
> Â
> Â
> --
> To respond to this post, please click the following link:
>
> <http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/3161415>
>
> or simply reply to this email.

--
Janine Graves

Subject: RE: Re: New Message from prince christopher joseph in Customer Voice Portal
Replied by: prince christopher joseph on 14-03-2011 04:46:03 PM
Thanks Janine , your explanation gives me good understanding
 
 
 
 
 
 
 
As I mentioned, you should NOT handle telephone.disconnect.hangup or
connection.disconnect.hangup - the VXML Server will know if the caller
hangs up and will free the VxmlServer license immediately. If you then
execute status.bat script - you will see the license has been freed and
'one session is ending' - this is just a delay on vxmlserver in case you
are executing some 'end of call' java code and need access to the
variables from the call flow - so they don't delete the session's
variables for about 60seconds. BUT - the license is definitely freed
immediately.

Simultaneously, the gateway automatically alerts ICM that the caller
hung up and ends the ICM routing script immediately.

By default, you can't send anything back to ICM on a hangup.

If you need to respond in some way when the caller hangs up (either by
writing to a DB, or by sending data back to ICM into its FromExtVxml
array) - then you must write custom java that executes OnEndCall. This
code executes no matter how the visit to the application ends (hangup,
error, app transfer, normal, etc).

See the CVP VXMLServer and Studio Programmers Guide for more information
on this.

Janine





On 3/11/2011 4:32 PM, Cisco Developer Community Forums wrote:
> prince christopher joseph has created a new message in the forum "CVP
> - All Versions":
>
> --------------------------------------------------------------
> What is the best practive in Cisco CVP to handle disconnect events ?Â
> Iam using HotEvent block to capture "connection.disconnect.hangup" the
> event and use hangup block to end the session , The CVP application is
> been invoked by ICM Scripts.
> Â
> Also facing issue with this methodology , when ever i disconnect the
> call , the vmxl session is not ending so we lose one of CVP port.
> Â
> Do i need to send a response back to ICM about the disconnect ???
> Â
> Need your suggestions
> Â
> Thanks
> Â
> Â
> --
> To respond to this post, please click the following link:
>
> <http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/3161415>
>
> or simply reply to this email.

--
Janine Graves

CreatePlease to create content
Content for Community-Ad
FusionCharts will render here