We do have &quot;failed_xml_cdr_prefix&quot;<br><br>you set that on the A leg and any and all failed B originates generate a full XML CDR report and <br>set it as a variable, this includes during a forked dial.<br><br>so say you try to call sofia/profile/<a href="mailto:a@foo.com">a@foo.com</a>,sofia/profile/<a href="mailto:b@foo.com">b@foo.com</a><br>
and it fails completely, before you make the call you set failed_xml_cdr_prefix to &quot;bad_call&quot;<br><br>Then you end up with ${bad_call_1} and ${bad_call_2} which are each a full XML report including all the vars etc.<br>
<br><br><br><br><br><br><div class="gmail_quote">On Mon, Jul 7, 2008 at 6:21 PM, Simon Capper &lt;<a href="mailto:scapper@ooma.com">scapper@ooma.com</a>&gt; wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I&#39;m setting up a bridge call with continue_on_fail=true so I can deal with<br>
failure.<br>
I want to be able to extract the sip variables (including some custom<br>
variables I added to mod_sofia) from the failed call to determine what to do<br>
next in the dialplan/application.<br>
<br>
The channel gets destroyed after the bridge fails and the &quot;import&quot; feature<br>
does not work for a failed call it seems and it only has one parameter.<br>
<br>
I can&#39;t figure out how to use api_hangup_hook to copy variables from the<br>
dying B channel to the A channel as there is no reference to the A channel<br>
in the handler and I&#39;m not sure if it gets called for a failed call anyway.<br>
<br>
Would you accept a submission of a new feature &quot;export_on_fail&quot; used for<br>
bridged calls that takes a list of parameters to be exported from chan B to<br>
A, kind of like the way &quot;export&quot; works? The variables would be &quot;prepended&quot;<br>
with &quot;failed_&quot; so that they did not clash with variable names on the channel<br>
they were being exported to.<br>
<br>
<br>
Thanks,<br>
<br>
Simon<br>
<br>
<br>
<br>
_______________________________________________<br>
Freeswitch-dev mailing list<br>
<a href="mailto:Freeswitch-dev@lists.freeswitch.org">Freeswitch-dev@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-dev" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-dev</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Anthony Minessale II<br><br>FreeSWITCH <a href="http://www.freeswitch.org/">http://www.freeswitch.org/</a><br>ClueCon <a href="http://www.cluecon.com/">http://www.cluecon.com/</a><br>
<br>AIM: anthm<br><a href="mailto:MSN%3Aanthony_minessale@hotmail.com">MSN:anthony_minessale@hotmail.com</a><br>GTALK/JABBER/<a href="mailto:PAYPAL%3Aanthony.minessale@gmail.com">PAYPAL:anthony.minessale@gmail.com</a><br>
IRC: <a href="http://irc.freenode.net">irc.freenode.net</a> #freeswitch<br><br>FreeSWITCH Developer Conference<br><a href="mailto:sip%3A888@conference.freeswitch.org">sip:888@conference.freeswitch.org</a><br><a href="http://iax:guest@conference.freeswitch.org/888">iax:guest@conference.freeswitch.org/888</a><br>
<a href="mailto:googletalk%3Aconf%2B888@conference.freeswitch.org">googletalk:conf+888@conference.freeswitch.org</a><br>pstn:213-799-1400