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