John, I sent this email a year ago. There was a discussion about how to fix the problem (caused by the change to mnemonic labels) and I don't think anything was done. It may help. Peter If you look in the email archive you will find that ontimeout is broken in 3.1. This was my last email in the exchange: >I had another look at this and the nextLabels map already has a strdup >(leaking memory >of course). So a crude fix to the problem is to change: >line 739 of scenario.cpp to: > labelMap[strdup(ptr)] = length; >and line 1639 of scenario.cpp to: > ontimeoutLabels[length] = strdup(ptr);
>and put a note on the TODO list about the leaking memory. I have tested it and >it does >fix Sumeet's issue. The memory loss is one off not continuous. So you can use the fix, use 3.0 and/or prod the maintainers to fix it. Peter From: john.mcnam...@emutex.com To: sipp-users@lists.sourceforge.net Date: Thu, 24 Feb 2011 15:56:36 +0000 Subject: Re: [Sipp-users] Timeout attribute on initial recv request From: mayamatakeshi [mailto:mayamatake...@gmail.com] On Fri, Feb 25, 2011 at 12:11 AM, John McNamara <john.mcnam...@emutex.com> wrote: From: John McNamara [mailto:john.mcnam...@emutex.com] >> I can't get the timeout to work with a recv message in a simplified server >> scenario such as the following: >> I never use this. But the behavior you describe looks reasonable to me (not >> a bug). >> Why would you want it to timeout before receiving the initial message? Hi, I want it to timeout before receiving an initial message in case it *never* receives an initial message. I am testing a scenario where 2 SIPp instances are simulating both ends of a call with the system under test in the middle. If the A party call fails then the SIPp scenario will fail and we can catch the failure under automated testing. However, in this case the B party SIPp instance won't receive an initial INVITE and will continue running indefinitely. It seems reasonable (to me) to expect the recv timeout to work regardless of its position in the call flow. It isn't documented that it doesn't work that way. So to me this looks like a bug. If it is then I'll try fix it. If it isn't then I'll work around it. John. ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev _______________________________________________ Sipp-users mailing list Sipp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sipp-users
------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev
_______________________________________________ Sipp-users mailing list Sipp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sipp-users
