ok both methods work now.<br>your jira was fixed in r16311 and the non bypass equivalent was fixed in the previous commit <br><br><div class="gmail_quote">On Thu, Jan 14, 2010 at 11:00 AM, Sergey Okhapkin <span dir="ltr"><<a href="mailto:sos@sokhapkin.dyndns.org">sos@sokhapkin.dyndns.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">"hangup_after_bridge=false" is the default setting.<br>
<div><div></div><div class="h5"><br>
On Thursday 14 January 2010, Mathieu Rene wrote:<br>
> One way you could fix it is set "hangup_after_bridge=false" and then<br>
> set "execute_on_answer=set\shangup_after_bridge=true". That will make<br>
> it continue executing the dialplan atter a failure that came in after<br>
> 183. Note that there is a side effect to this method, since audio was<br>
> being relayed, you are forced to use the same codec on the 2nd<br>
> carrier, best to tell them they are wrong failing a call after 183.<br>
><br>
> Mathieu Rene<br>
> Avant-Garde Solutions Inc<br>
> Office: + 1 (514) 664-1044 x100<br>
> Cell: +1 (514) 664-1044 x200<br>
> <a href="mailto:mrene@avgs.ca">mrene@avgs.ca</a><br>
><br>
> On 14-Jan-10, at 11:41 AM, Sergey Okhapkin wrote:<br>
> > Anthony, I apology, I didn't expect you'll be annoyed. As for the<br>
> > issue, the<br>
> > issue is not in "proxy_media" setting, same happens when both<br>
> > "proxy_media"<br>
> > and "bypass_media" are not set. The code does explicit leg A hangup in<br>
> > switch_ivr_bridge.c, line 513. The condition there is "if leg A is<br>
> > up and leg<br>
> > A is not in answered state, then hangup leg A", this prevents<br>
> > dialplan to<br>
> > continue execution on early media bridge termination.<br>
> ><br>
> > Issue when "bypass_media=true" is completely different, I'll open<br>
> > the issue on<br>
> > jira.<br>
> ><br>
> > On Thursday 14 January 2010, Anthony Minessale wrote:<br>
> >> Sergey,<br>
> >><br>
> >> The bug you reference was closed because proxy_media mode by design<br>
> >> send's<br>
> >> the B leg's codec to the A<br>
> >> LEG so if there is a failure condition there is no easy graceful<br>
> >> way to<br>
> >> back out and try another call.<br>
> >> I will try to make it possible if yo post a bounty, I estimate a<br>
> >> minimum of<br>
> >> $1000USD in consulting time.<br>
> >><br>
> >> The other one I might look at once you have apologized.<br>
> >><br>
> >> I can probably add some code to make the bridge exit without<br>
> >> terminating<br>
> >> the A leg even when hangup_after_bridge=true in the case where the<br>
> >> the B<br>
> >> leg is not answered but right now I am sort of annoyed with your<br>
> >> attitude<br>
> >> in this thread.<br>
> >><br>
> >><br>
> >> On Thu, Jan 14, 2010 at 6:19 AM, Sergey Okhapkin<br>
> >><br>
> >> <<a href="mailto:sos@sokhapkin.dyndns.org">sos@sokhapkin.dyndns.org</a>>wrote:<br>
> >>> Case 1 (bypass_media is off) is already on jira,<br>
> >>> <a href="http://jira.freeswitch.org/browse/FSCORE-257" target="_blank">http://jira.freeswitch.org/browse/FSCORE-257</a> , I will prepare a test<br>
> >>> installation with latest trunk to reproduce case 2, when<br>
> >>> bypass_media=true and 10 seconds delay happens when 18X and then<br>
> >>> error<br>
> >>> are received on leg b.<br>
> >>><br>
> >>> On Wednesday 13 January 2010, Michael Jerris wrote:<br>
> >>>> On Jan 13, 2010, at 11:08 PM, Sergey Okhapkin wrote:<br>
> >>>>> Critical issues are when SIP error come after 18X provisional<br>
> >>>>> response.<br>
> >>>>><br>
> >>>>> - if bypass_media is false then dialplan stops and leg a is<br>
> >>>>> explicitly hang up (switch_ivr_bridge.c, line 513).<br>
> >>>><br>
> >>>> behavior can be modified with continue_on_fail and<br>
> >>>> hangup_after_bridge<br>
> >>>> channel vars, perhaps ignore_early_media as well<br>
> >>>><br>
> >>>>> - if bypass_media is true, then dialplan continue, but there is 10<br>
> >>>>> seconds delay before next bridge application sends INVITE to<br>
> >>>>> gateway<br>
> >>>>> (<br>
> >>><br>
> >>> <a href="http://lists.freeswitch.org/pipermail/freeswitch-users/2010-January/024" target="_blank">http://lists.freeswitch.org/pipermail/freeswitch-users/2010-January/024</a><br>
> >>>35<br>
> >>><br>
> >>>>> 4.html ) I didn't track down yet why this happens looking at FS<br>
> >>>>> sources.<br>
> >>>><br>
> >>>> see response on that thread<br>
> >>>><br>
> >>>>> Why I didn't open a bug on jira? Because FS behaves according to<br>
> >>>>> the<br>
> >>>>> design and specs :-) But not according to real world<br>
> >>>>> requirements...<br>
> >>>><br>
> >>>> Really, people are trying to help you and your going to be snarky<br>
> >>>> in<br>
> >>>> response?<br>
> >>>><br>
> >>>>> On Wednesday 13 January 2010, Brian West wrote:<br>
> >>>>>> Can you elaborate on these "Critical" issues you seem to be<br>
> >>>>>> having?<br>
> >>><br>
> >>> Why<br>
> >>><br>
> >>>>>> aren't you opening a jira for them if they are that critical to<br>
> >>>>>> your<br>
> >>>>>> needs?<br>
> >>>><br>
> >>>> Mike<br>
> >>>><br>
> >>>><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-use" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-use</a><br>
</div></div>> >>>>r s <a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
<div><div></div><div class="h5">> >>><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-user" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-user</a><br>
> >>>s <a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
> ><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>
><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>
<br>
<br>
<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>
</div></div></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>
Twitter: <a href="http://twitter.com/FreeSWITCH_wire">http://twitter.com/FreeSWITCH_wire</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:+19193869900<br>