Prophecy 2006

Ok, chalk this one up to user error, but with a comment about the inner workings of Prophecy.

I had a "catch" element to catch "connection.disconnect" events, and that catch element had a semantic error in it (a bad "assign" element). Therefore when I hit a "disconnect" element in the VoiceXML script, the catch element would trigger and processing would halt.

This is both reasonable and unreasonable. Reasonable because the error in the catch element caused the interpreter to halt. Unreasonable because the disconnect element should order a disconnect, and the connection.disconnect is the event that follows a disconnect.

My question to Voxeo, which I've asked support: How could it be that the connection.disconnect is received before the event actually completes and the SIP phone disconnects? Or does connection.disconnect.hangup work as I've just said, but a connection.disconnect event has some different meaning?

I'll post the conclusion to this exciting dialog as information becomes available.