On Fri, Feb 25, 2011 at 12:11 AM, John McNamara <john.mcnam...@emutex.com>wrote:
> *From:* John McNamara [mailto:john.mcnam...@emutex.com] > *Sent:* 21 February 2011 15:53 > *To:* sipp-users@lists.sourceforge.net > *Subject:* [Sipp-users] Timeout attribute on initial recv request > > > > > I can't get the timeout to work with a recv message in a simplified > server scenario such as the following: > > > > Hi, > > > > Any takers on this. > > > > I found that the timeout does work as expected when it isn't the first recv > in a call flow. > > > > Is this a bug? If not could someone let me know before I start digging > into the code. > 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? Using the -timeout in the command line doesn't timeout the test call. It causes sipp to quit (terminate) after x seconds.
------------------------------------------------------------------------------ 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
