A complete console log attached to a new jira issue.<div><br></div><div><a href="http://jira.freeswitch.org">http://jira.freeswitch.org</a><div><br></div><div>sofia global siptrace on</div><div>console loglevel debug</div>
<div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Nov 21, 2012 at 11:30 AM, Victor Chukalovskiy <span dir="ltr"><<a href="mailto:victor.chukalovskiy@gmail.com" target="_blank">victor.chukalovskiy@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
<br>
Looking for help or comments on this. Reproducible on the FS system that<br>
was updated about a month ago. Call scenario:<br>
<br>
SIP call comes in on "a" leg, SIP call is attempted on the "b" leg. "b"<br>
leg replies "404".<br>
<br>
Description of the problem:<br>
FS tries same SIP destination 4 times on the "b" leg instead of doing it<br>
once. It does not respond "404" to the "a" leg until it finishes all 4<br>
attempts on the "b" leg. This occurs when "b" leg takes longer than<br>
usual to return "404". For example, if "b" leg takes 1.3 seconds until<br>
we get "404", FS tries the call on "b" leg 3 more times. When this<br>
happens each consequent call attempt on the "b" leg is exactly 2 seconds<br>
apart from when the previous call attempt ends.<br>
<br>
For comparison, in the same scenario and using exact same config, if "b'<br>
leg replies "404" sooner (e.g. within 0.3 seconds) FS does not retry<br>
this call on the "b" leg anymore. "404" is returned to the "a" leg<br>
instantaneously as it should be.<br>
<br>
I suspect this is a bug in Sofia such that is somehow related to 500ms<br>
timer.<br>
<br>
Is this known behavior? Do you need any more details to be able to<br>
verify or comment?<br>
<br>
Thank you,<br>
Victor<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>
FreeSWITCH-powered IP PBX: The CudaTel Communication Server<br>
<a href="http://www.cudatel.com" target="_blank">http://www.cudatel.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://wiki.freeswitch.org" target="_blank">http://wiki.freeswitch.org</a><br>
<a href="http://www.cluecon.com" target="_blank">http://www.cluecon.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><br clear="all"><div><br></div>-- <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="mailto:googletalk%3Aconf%2B888@conference.freeswitch.org">googletalk:conf+888@conference.freeswitch.org</a><br>
pstn:+19193869900<br>
</div>