RE: Actual reason for call disconnection

Version 1
    This document was generated from CDN thread

    Created by: Raghavendra Gutty Veeranagappa on 02-04-2013 05:51:06 AM
    Hi Mark,
     
    please try to use "infotag get evt_last_disconnect_cause" command. for more information refer TCL IVR programming guide.
     
    Thanks,
    Raghavendra

    Subject: RE: Actual reason for call disconnection
    Replied by: Yaw-Ming Chen on 10-04-2013 10:12:35 AM
    1. Is Secure RTP used ? Tcl API won't work with Secure RTP.
    2. I saw to codecs, is codec class configured ?
     
     IP 0.0.0.0:0 SRTP: off rtt:0ms pl:0/0ms lost:0/0/0 delay:0/0/0ms g711ulaw
    11EB : 10 689760ms.9 +-1 +0 pid:18 Originate XXXXXXXXXX
     dur 00:00:00 tx:0/0 rx:0/0 29  (temporary failure (41))
     IP 0.0.0.0:0 SRTP: off rtt:0ms pl:0/0ms lost:0/0/0 delay:0/0/0ms g729r8 pre-ietf

    Subject: Re: New Message from Mark Alliban in Voice Gateway API (VGAPI) - TCL-API: R
    Replied by: LEON MCCALLA on 10-04-2013 11:14:24 AM
    This works just fine for me.

    set status [infotag get evt_status]
    if { $status == "ls_000"} {
    timer start leg_timer $creditTimeLeft leg_incoming
    puts "====== $call_id Connected Maximum Duration: $creditTimeLeft
    ============="
    aaa accounting update leg_outgoing -a avlistSend
    return
    }

    set nDisconnect [infotag get evt_last_disconnect_cause]



    From: Cisco Developer Community Forums
    Sent: Wednesday, April 10, 2013 11:22 AM
    To: cdicuser@developer.cisco.com
    Subject: New Message from Mark Alliban in Voice Gateway API (VGAPI) -
    TCL-API: RE: Actual reason for call disconnection

    Mark Alliban has created a new message in the forum
    "TCL-API": --------------------------------------------------------------
    Everything is working perfectly apart from this 1 issue. When I use an
    outbound carrier that does connect, it all works. When the carrier fails, it
    does as it should, it triggers the ev_setup_done and goes on to try the next
    carrier. The only problem is that I cannot get the actual disconnect cause
    into the TCL code (in this case 102), evt_last_disconnect_code always gets
    the disconnect code from the inbound leg (41).

    --
    To respond to this post, please click the following link:
    http://developer.cisco.com/web/vgapi/forums/-/message_boards/view_message/14105551
    or simply reply to this email.

    Subject: RE: Re: New Message from Mark Alliban in Voice Gateway API (VGAPI) - TCL-AP
    Replied by: Yaw-Ming Chen on 10-04-2013 05:46:28 PM
    Try to get the "infotag set evt_report "ev_transfer_request""
    when you get "ev_disconnected" event