A big amount of calls receive a far end disconnect but AAOD6 app isnt handling.

Over MPP the BBE found the following exception,

@2013-11-11 15:24:04,650|PAVB_03335|INFO|VB|19024|Session=SRVMOMPP1-2013315202344-10|Got VoiceXML exception: connection.disconnect.hangup in http://10.10.16.12:8080/UPC/datEvaluaAes?___DDSESSIONID=8068860B94E50817D0E6F9EC612CF7E4%3A%2FUPC|SRVMOMPP1####

The app named UPC has an OnDisconnect Event Handler over the AppRoot and a return node to terminate the app when a disconnect was received.
It seems the event isn't cached by the app.

I will apreciate your answer or help to make a workaround.
Regards!

The buildt-in event OnDisconnect should handle both connection.disconnect.hangup and connection.disconnect.transfer events. To distinquish between both scenario it may be usefull to create custom events (connection.disconnect.hangup f.e.) and catch them in the App Root. If you are missing the event handling in the AppRoot, it may be because it is not propagated from the sub-module (Return Event).
MB

Miroslav, it is a very simple aplicattion. It hasen't sub-modules.
Only get POM PDC data, set UUI an make a transfer to some skill.
But a 20% of the calls return a Disconnect that seems not to be catched over the app. The question is.
Is there another way to catch those exceptions?

Do you have the VXML that is sent over to the VB to see if the disconnect handler is indeed configured? You would need to enable VXML output in your ddrt.properties file.

You also should look through the sessionslot log on the MPP for the VB to see what further happens when the hangup event is caught. It should either send it to your handler or the default handler.