Once in record mode, after the beep, the disconnect handling is caught properly. That has always worked fine.
It is not unusual for a user to hang up during a prompt, and it is essential that the handler is run to submit the recording - since this may occur when appending to a recording, this is not necessarily an empty bit of recording...there's backend processing that must occur for previously recorded portions.
I would expect that the catch event would apply to the prompt here, or does must there be another catch event w/i the prompt tags perhaps - looking at the VXML spec, catch is not a valid child of prompt.
Any insight would be greatly appreciated! Thanks.
Code: Select all
<form id="record">
<record name="recording" beep="true" dtmfterm="true"
maxtime="600s" finalsilence="60s" type="audio/basic">
<prompt bargein="false">
<voice name="audrey">Dictate at the beep.</voice>
</prompt>
<catch event="connection.disconnect">
<var name="disconnect" expr="1"/>
<submit next="record-save.xml" method="post"
namelist="recording position disconnect"/>
</catch>
</record>
...
</form>