<div dir="ltr">Try with this before the bridge:<div><br></div><div><action application="set" data="hangup_after_bridge=true"/></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 18 September 2014 12:23, mbo <span dir="ltr"><<a href="mailto:mbodbg@gmx.net" target="_blank">mbodbg@gmx.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I’m originating a call from FREESWITCH1 to FREESWITCH2, which bridges the call via a gateway to a carrier.<br>
<br>
FREESWITCH1 -> FREESWITCH2 -> CARRIER<br>
<br>
Freeswitch2 only executes a simple dialplan like:<br>
<br>
<extension name="bt"><br>
<condition field="destination_number" expression="^(\\+\d{5,20})$"><br>
<action application="bridge" data="sofia/gateway/bt/${destination_number}"/><br>
</condition><br>
</extension><br>
<br>
<br>
When the destination is BUSY, I can see in the logs<br>
<br>
...<br>
[NOTICE] switch_core_state_machine.c:313 sofia/internal/XXXXXXXXXX has executed the last dialplan instruction, hanging up.<br>
[NOTICE] switch_core_state_machine.c:315 Hangup sofia/internal/XXXXXXXXXX [CS_EXECUTE] [NORMAL_CLEARING]<br>
…<br>
<br>
FREESWITCH2 hangs up with cause NORMAL_CLEARING after the bridge, and then sends<br>
<br>
...<br>
<br>
SIP/2.0 486 Busy Here<br>
Via: SIP/2.0/UDP 192.168.154.100:5080;rport=5080;branch=z9hG4bK18gUcH38BXQ8H<br>
Max-Forwards: 65<br>
From: „XXXXXXXXXXXXX>;tag=S4SS3j0HyUv2Q<br>
To: <XXXXXXXXXXXXX>;tag=B7XU8ZtQUDvrF<br>
Call-ID: b61b6f21-b9ab-1232-5abc-00163e6b3124<br>
CSeq: 65177338 INVITE<br>
User-Agent: FreeSWITCH-mod_sofia/1.4.6+git~20140603T193516Z~9479729340~64bit<br>
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE<br>
Supported: timer, path, replaces<br>
Allow-Events: talk, hold, conference, presence, as-feature-event, dialog, line-seize, call-info, sla, include-session-description, presence.winfo, message-summary, refer<br>
Reason: Q.850;cause=16;text="NORMAL_CLEARING"<br>
Content-Length: 0<br>
X-FS-Display-Name: Outbound Call<br>
X-FS-Display-Number: XXXXXXXXXXXX<br>
Remote-Party-ID: "Outbound Call“ <XXXXXXXXXXXX>;party=calling;privacy=off;screen=no<br>
…<br>
<br>
to FREESWITCH1. In the CDR on FREESWITCH1, the hangup cause for the call is NORMAL_CLEARING and not USER_BUSY.<br>
Does this really works as designed or shouldn’t it hangup with hangup cause „USER_BUSY" and then set "Reason: Q.850;cause=17;text=„USER_BUSY“" in the SIP/2.0 486 Busy Here message, which is sent to FREESWITCH1?<br>
<br>
<br>
<br>
<br>
<br>
<br>
_________________________________________________________________________<br>
Professional FreeSWITCH Consulting Services:<br>
<a href="mailto:consulting@freeswitch.org">consulting@freeswitch.org</a><br>
<a href="http://www.freeswitchsolutions.com" target="_blank">http://www.freeswitchsolutions.com</a><br>
<br>
Official FreeSWITCH Sites<br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
<a href="http://confluence.freeswitch.org" target="_blank">http://confluence.freeswitch.org</a><br>
<a href="http://www.cluecon.com" target="_blank">http://www.cluecon.com</a><br>
<br>
FreeSWITCH-powered IP PBX: The CudaTel Communication Server<br>
<a href="http://www.cudatel.com" target="_blank">http://www.cudatel.com</a><br>
<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</blockquote></div><br></div>