If you use hangup after a bridge FreeSWITCH overrides the cause with the cause recieved from the bridge application. You can avoid this using sip_ignore_remote_cause=true On Wed, Nov 10, 2010 at 12:25 PM, Ross McKillop <ross@ossiantelecom.co.uk> wrote:
I have a FreeSWITCH box acting as a gateway between other servers and a TDM switch, primarily for accounting purposes - The TDM switch accurately sets a Reason header as follows;
SIP/2.0 480 Temporarily Unavailable. Reason: Q.850;cause=31.
This is then passed by FreeSWITCH back to the A party as
SIP/2.0 480 Temporarily Unavailable. Reason: Q.850;cause=16;text="NORMAL_CLEARING".
Is there any way to get FreeSWITCH to use the Reason header from the failed B leg when replying to the A party ?
I tried setting continue_on_fail=true and hangup_after_bridge=false and then adding a line after the bridge in the dialplan to hangup with the bridge hangup cause e.g.;
<action application="hangup" data="${bridge_hangup_cause}" />
But that hasn't affected the behaviour at all.
Regards, Ross
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- Eduardo Nunes Pereira cel.: (48) 9989-2997 email: eduardonunesp@gmail.com