[Voiceglue] A CRITICAL entry

[Doug Campbell]

> Asterisk logs for this call uploaded: http://pastebin.com/m407b4b91

Everything looks fine until:

[Jun  4 13:32:16] VERBOSE[20750] logger.c:     -- Executing [h at mjogrb171_VG:1] NoOp("Local/1154 at confirm-call-56d4,1", "2BA2AE3C5A083D61A4FFAEA5EDB97F85 - AGI status - FAILURE") in new stack

This corresponds to the same timestamp in the voiceglue logs
where the AGI GetDigit ("WAIT FOR INPUT") got a -1 response,
a failure.

So, why is Asterisk failing?  What Asterisk are you using?
Is anything else doing anything to this channel under Asterisk?

> As a best practice, should VoiceXML applications capture disconnects if we do our app
 > clean-up in the h section of the dial plan?

The VXML specification requires that a connection.disconnect event always be
thrown when the call is disconnected from the VXML session.  Voiceglue
supports this by interpreting an AGI connection drop as a disconnect.
Thus, you should be able to handle a call disconnect from both the
VXML connection.disconnect event and from any Asterisk mechanism.
Not catching the connection.disconnect event in VXML should also be
benign, and that session should clean up normally.

> We took ours out (under the mistaken impression that should the callee hang up, VoiceXML
 > should be destroyed) and instead performed clean-up in the hangup section of the dial plan
 > (sounds logical!), it appeared to help, then we started seeing mass hangs of the VoiceGlue
 > process under load at random, with DeadAGI listed for each channel.

DeadAGI?  Voiceglue doesn't even use DeadAGI.
Perhaps the Asterisk logs simply mean that the AGI session has finished.

Doug Campbell