Freeswitch retries same call 4 times for no reason - incorrect treatment of timers by mod sofia?
Hello, Looking for help or comments on this. Reproducible on the FS system that was updated about a month ago. Call scenario: SIP call comes in on "a" leg, SIP call is attempted on the "b" leg. "b" leg replies "404". Description of the problem: FS tries same SIP destination 4 times on the "b" leg instead of doing it once. It does not respond "404" to the "a" leg until it finishes all 4 attempts on the "b" leg. This occurs when "b" leg takes longer than usual to return "404". For example, if "b" leg takes 1.3 seconds until we get "404", FS tries the call on "b" leg 3 more times. When this happens each consequent call attempt on the "b" leg is exactly 2 seconds apart from when the previous call attempt ends. For comparison, in the same scenario and using exact same config, if "b' leg replies "404" sooner (e.g. within 0.3 seconds) FS does not retry this call on the "b" leg anymore. "404" is returned to the "a" leg instantaneously as it should be. I suspect this is a bug in Sofia such that is somehow related to 500ms timer. Is this known behavior? Do you need any more details to be able to verify or comment? Thank you, Victor
A complete console log attached to a new jira issue. http://jira.freeswitch.org sofia global siptrace on console loglevel debug On Wed, Nov 21, 2012 at 11:30 AM, Victor Chukalovskiy < victor.chukalovskiy@gmail.com> wrote:
Hello,
Looking for help or comments on this. Reproducible on the FS system that was updated about a month ago. Call scenario:
SIP call comes in on "a" leg, SIP call is attempted on the "b" leg. "b" leg replies "404".
Description of the problem: FS tries same SIP destination 4 times on the "b" leg instead of doing it once. It does not respond "404" to the "a" leg until it finishes all 4 attempts on the "b" leg. This occurs when "b" leg takes longer than usual to return "404". For example, if "b" leg takes 1.3 seconds until we get "404", FS tries the call on "b" leg 3 more times. When this happens each consequent call attempt on the "b" leg is exactly 2 seconds apart from when the previous call attempt ends.
For comparison, in the same scenario and using exact same config, if "b' leg replies "404" sooner (e.g. within 0.3 seconds) FS does not retry this call on the "b" leg anymore. "404" is returned to the "a" leg instantaneously as it should be.
I suspect this is a bug in Sofia such that is somehow related to 500ms timer.
Is this known behavior? Do you need any more details to be able to verify or comment?
Thank you, Victor
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
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
-- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire AIM: anthm MSN:anthony_minessale@hotmail.com GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org googletalk:conf+888@conference.freeswitch.org pstn:+19193869900
Sounds more like someone is using a stacked dial with continue_on_fail=true On 11/21/12 7:09 PM, "Anthony Minessale" <anthony.minessale@gmail.com> wrote:
A complete console log attached to a new jira issue.
sofia global siptrace on console loglevel debug
On Wed, Nov 21, 2012 at 11:30 AM, Victor Chukalovskiy <victor.chukalovskiy@gmail.com> wrote:
Hello,
Looking for help or comments on this. Reproducible on the FS system that was updated about a month ago. Call scenario:
SIP call comes in on "a" leg, SIP call is attempted on the "b" leg. "b" leg replies "404".
Description of the problem: FS tries same SIP destination 4 times on the "b" leg instead of doing it once. It does not respond "404" to the "a" leg until it finishes all 4 attempts on the "b" leg. This occurs when "b" leg takes longer than usual to return "404". For example, if "b" leg takes 1.3 seconds until we get "404", FS tries the call on "b" leg 3 more times. When this happens each consequent call attempt on the "b" leg is exactly 2 seconds apart from when the previous call attempt ends.
For comparison, in the same scenario and using exact same config, if "b' leg replies "404" sooner (e.g. within 0.3 seconds) FS does not retry this call on the "b" leg anymore. "404" is returned to the "a" leg instantaneously as it should be.
I suspect this is a bug in Sofia such that is somehow related to 500ms timer.
Is this known behavior? Do you need any more details to be able to verify or comment?
Thank you, Victor
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
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
-- Ken http://www.FreeSWITCH.org http://www.ClueCon.com http://www.OSTAG.org irc.freenode.net #freeswitch
participants (3)
-
Anthony Minessale
-
Ken Rice
-
Victor Chukalovskiy