> From: catalina oancea [mailto:catalina.oan...@gmail.com]
> Sent: Wednesday, April 15, 2009 7:33 AM
> The problem also occurs if running as uas.
>
> Has anybody tried sipp with rtp for all calls with 200 calls?
Have you checked `netstat -na` (or equivalent) to see if you are
running out of ports? 200 ports per second times 2 minutes (typical) TIME_WAIT
yields 24,000 ports in churn, which tends to increase as resource usage
increases and the OS is slower in getting around to cleaning them up.
To test this theory, change '-t un' to '-t u1', just for test purposes.
A possible workaround is to add multiple IP aliases to the addresses
(make sure they're not in use!) and use the injection file to bind the call
source to different aliases, thus slowing down the churn rate on each address.
HTH,
Mike
------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users
