Classification: Company Confidential Hi,
> -----Original Message----- > From: ext voip_v...@web.de [mailto:voip_v...@web.de] > Sent: 15 June, 2011 11:24 > To: Sofia-Sip-Devel > Subject: Re: [Sofia-sip-devel] OPTIONS keep-alive broken? > > >> after updating to sofia-sip 1.12.11 I am facing some problems with > >> NAT keep- alive via options packets. NUA is configured to send > >> these packets every 15 seconds, but they are sent in an interval of > >> about 500ms. In fact sofia is retransmitting the packets, although > >> answers are correctly received. I have seen this behaviour at > >> different sites with > different SIP providers. > >> > >> Downgrading to 1.12.10 helps, packets are sent every 15 seconds. > >> > >> I attach sofia log files (one of 1.12.11 and one of 1.12.10) to > >> this mail. In both logs a nua object is created and the ua > >> registers with the german sip provider sipgate. After successful > >> registration options > keep-alive is started. > >> > >> The logs are almost identical until the first answer to an options > >> keep-alive is received (around line 140). In sofia 1.12.10 register > >> and options transactions are destroyed after timer k has been fired. > >> In sofia 1.12.11 this is missing and the options packet is almost > immediately resent. > >> > >> Is this a known bug or has anyone else seen this behaviour? > > > >Can you check with the latest build off the trunk? > >Also please check with a more realistic keep-alive period, 15 seconds > >is a bit > extreme anyway... > > > Thanks for your reply. I tried the latest build which shows the same > behaviour. > > Your hint about the keep-alive period seems to point into the right direction. > Using a keep-alive period of around 35 seconds packets are sent correctly. > But if i use smaller periods, packets are sent much too fast (30 > seconds lead to a real period of 20 seconds, 18 seconds to 3 seconds > and > 15 seconds or lower to an immediate resent of the options packet). > > I checked this against 1.12.10 release again, where small keep-alive > periods work perfectly. > > Although I agree that 15 seconds are very fast, I would like to fix > this problem. Do you have any pointer into the code? You can start with nua/outbound.c, the code setting the timer. I recently submitted some changes in timer scheduling, and I have to admit that extremely tight refresh periods were not considered an important use case. As a simpler solution, you can try making all timers non-deferrable through a newly available tag, if the battery life is not a concern (as you wish to send pings every 15 seconds, it's probably not something that worries you :-)). Best regards, Mikhail Classification: Company Confidential ------------------------------------------------------------------------------ AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on "Lean Startup Secrets Revealed." This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev _______________________________________________ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
