VXML EndClass not being called when caller Hang up

[ehtasham.malik]

We have VXML application . lets suppose 3 nodes

• Weclome
• Action (We are calling a web service )
• EndCall (Updating the status calling a web)

Customer call , and it reaches on  Action Element (java class), where we call a web service, Now we have logic in which web service can take some time (we have some more integration in web service ) , So we wait there until we receive any output from the webservice, In the meanwhile we play MOH to customer.
End Class Interface: According to documentation End class event occur when ever a caller hang up.

Now when caller comes on IVR and reach up to Action Element, its wait there , even if caller hang up the call it still hold on the same node , until webservice respond or vxml session timeout occur.

Theoretically when caller hang up the call, it should end the Java Action Class and call END Class Event and end the vxml session .

So is there any way out to get the notification when caller hang up the call in VXML>

[ptindall]

The EndCall class will be invoked on the VoiceXML server once hangup has been detected.  The problem is that if hangup happens while control is server-side (waiting on a backend action to complete), you won't detect it until the next VoiceXML document is served.  If you want to detect both backend and hangup events concurrently and immediately then you have to go custom.  There is a custom element here that may help you but be aware that I haven't published a VVB compatible version yet.

https://cisco.box.com/v/cvp-asynchttp

[piyush aghera]

Hi,

I am not able to access above location, could you please re-share the custom element.

Thank you.

[ptindall]

Refreshed link will last for a few days:  https://cisco.box.com/s/1ihebwfx750rk1isjjyp5whhjjnal972

[piyush aghera]

Thank you Paul.

Have you published the VVB compatible version yet ?  I also have VVB in my other setup.

[ptindall]

Yes, but had actually forgotten I'd done it.   Temp link to VVB compatible elements is https://cisco.box.com/s/nilv5cba1nq0ecp8nb6175vbw2l3xs55

See the Box note; the VVB would require you have an IOS device in the call signalling path.

Best to use Twitter @tindallpaul to check what gets published off the workbench.

Paul

[piyush aghera]

Thank you Paul for sharing.