<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <title>leg stup failure</title>
  <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_thread?p_l_id=&amp;threadId=12139552" />
  <subtitle>leg stup failure</subtitle>
  <id>http://developer.cisco.com/c/message_boards/find_thread?p_l_id=&amp;threadId=12139552</id>
  <updated>2013-05-22T17:28:04Z</updated>
  <dc:date>2013-05-22T17:28:04Z</dc:date>
  <entry>
    <title>Re: New Message from Yaw-Ming Chen in Voice Gateway API (VGAPI) - TCL-API:</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=12147320" />
    <author>
      <name>LEON MCCALLA</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=12147320</id>
    <updated>2013-02-20T05:37:35Z</updated>
    <published>2013-02-20T05:37:35Z</published>
    <summary type="html">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.</summary>
    <dc:creator>LEON MCCALLA</dc:creator>
    <dc:date>2013-02-20T05:37:35Z</dc:date>
  </entry>
  <entry>
    <title>RE: leg stup failure</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=12139653" />
    <author>
      <name>Yaw-Ming Chen</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=12139653</id>
    <updated>2013-02-20T00:18:20Z</updated>
    <published>2013-02-20T00:18:20Z</published>
    <summary type="html">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.</summary>
    <dc:creator>Yaw-Ming Chen</dc:creator>
    <dc:date>2013-02-20T00:18:20Z</dc:date>
  </entry>
  <entry>
    <title>leg stup failure</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=12135889" />
    <author>
      <name>LEON MCCALLA</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=12135889</id>
    <updated>2013-02-19T22:22:14Z</updated>
    <published>2013-02-19T22:22:14Z</published>
    <summary type="html">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</summary>
    <dc:creator>LEON MCCALLA</dc:creator>
    <dc:date>2013-02-19T22:22:14Z</dc:date>
  </entry>
</feed>

