I always include this at the bottom of my ccxml pages:


<transition event="" >
<log expr="'-- missed ' + event$.name +' -- [' + state +']'"/>
<log expr="' eventdata... \n' + objectToString(event$)"/>
</transition>

</eventprocessor>
</ccxml>

I believe that I have located the source of the issue here. My predecessor had added a <transition event=connection.connected"> step in which he triggered on a connect and did not test for call progress. I believe that the trigger on this event negated the subsequent events. I still need to think on this a bit more but for now, commenting this out in the CCXML did the trick.