Page 1 of 1

not able to catch disconnect.hangup event

Posted: Mon Dec 18, 2006 8:39 am
by awaneeshp
Hi,

I m not able to catch the disconnect.hangup event when I disconnect the call after transferring the call to a tel number.

Below is the VXML for the same please suggest.


Code: Select all

<?xml version="1.0"?>
<vxml version="2.1">
    <catch event="connection.disconnect.hangup">
    <prompt>
      <voice name="crystal">
        <break size="medium" />
      </voice>
    </prompt>
    <submit namelist="session.id" next="http://66.109.47.37/Captira.ADI.UI/errorpage.aspx" method="post" fetchtimeout="3s" />
  </catch>
  <catch event="error.semantic">
    <prompt>
      <voice name="crystal">
        <break size="medium" />We cannot complete your request. Please contact your bonding company directly or try again later.
      </voice>
    </prompt>
    <submit namelist="session.id" next="http://66.109.47.37/Captira.ADI.UI/errorpage.aspx" method="post" fetchtimeout="3s" />
  </catch>
  <form id="calltransfer">
    <block>
      <prompt>
        <voice name="crystal">
          <break size="medium" />transferring your call...Please Wait
        </voice>
      </prompt>
    </block>
    <transfer name="T_1" connecttimeout="10s" dest="+15184460680">
      <filled>
        <if cond="T_1 == 'noanswer' || T_1 == 'network_busy' || T_1 == 'unknown' || T_1 == 'busy'">
          <prompt bargein="false">
            <voice name="crystal">
              <break size="medium" />I was unable transfer you to a representative at this time.Please contact your bonding company directly or try again later
            </voice>
          </prompt>
          <submit namelist="session.id" next="http://66.109.47.37/Captira.ADI.UI/errorpage.aspx" method="post" fetchtimeout="3s" />
        </if>
      </filled>
    </transfer>
  </form>

</vxml>
[/b]

Please suggest so that after disconnecting the call we should be able to terminate the callers session on the application server by catching the disconnect event.

Thanks,
-Awaneesh

IVR error caused by prompt inside connection.disconnect.hang

Posted: Mon Dec 18, 2006 11:11 am
by support
The <prompt> inside your hangup catch will never be played because the IVR call has been hung up. That prompt, in turn, causes an IVR error to be thrown which is caught by the error.semantic catch. Try removing that prompt inside the connection.disconnect.hangup block.