leg stup failure

Version 1
    This document was generated from CDN thread

    Created by: LEON MCCALLA on 19-02-2013 04:22:14 PM
    How can I get the exact Q931/H323  failure code after a leg setup has
    failed?  LS_007 maps directly to user_busy (Q931 code 17) but do any of the
    other failure codes have direct mappings? is ther a way to get the exact
    cause code?

    Leon

    Subject: RE: leg stup failure
    Replied by: Yaw-Ming Chen on 19-02-2013 06:18:20 PM
    I don't think their is a mapping table. We can use description of leg setup status ls_xxx to correlate with Q931 code. For example, I think ls_004 (invalid number) should map to Q931 invalid number too.

    Subject: Re: New Message from Yaw-Ming Chen in Voice Gateway API (VGAPI) - TCL-API:
    Replied by: LEON MCCALLA on 19-02-2013 11:37:35 PM
    I found that calling [infotag get evt_last_disconnect_cause] immediately after a setup failure gives me the Q931 failure codes...

    Leon

    From: Cisco Developer Community Forums
    Sent: Tuesday, February 19, 2013 7:18 PM
    To: cdicuser@developer.cisco.com
    Subject: New Message from Yaw-Ming Chen in Voice Gateway API (VGAPI) - TCL-API: RE: leg stup failure

    Yaw-Ming Chen has created a new message in the forum "TCL-API": -------------------------------------------------------------- I don't think their is a mapping table. We can use description of leg setup status ls_xxx to correlate with Q931 code. For example, I think ls_004 (invalid number) should map to Q931 invalid number too.
    --
    To respond to this post, please click the following link: or simply reply to this email.