Cytowanie Rick Jones [EMAIL PROTECTED]:
I'm trying to use SIPp ti simulate about 5 clinets. I'm using
UDP with one socket per IP address mode (-t ui) and I found some
problems. First I set file descriptors limit to 65536, but SIPp
still was limited to 1024 connections. So I found
Hello Peter,
Friday, September 7, 2007, 9:33:01 AM, you wrote:
PH I don't want to discourage you but I did spend quite a time
PH looking at this on Linux a couple of years ago and failed.
PH
PH I came to the conclusion that the 1024 sockets is a C library
PH restriction and without recompiling
I don't want to discourage you but I did spend quite a time looking at this
on Linux a couple of years ago and failed.
I came to the conclusion that the 1024 sockets is a C library restriction
and without recompiling the library there is not much you can do for a
single process. I did try
Hi all!
I just updated SIPp to the most current version, but as I wanted to run
my scenarios, I noticed, that the auth-error is back again:
the line
[authentication username=[field4] password=[field1]]
creates as a
Hi Stephan,
It is best to let SIPp generate and assign the Call ID so that SIPp
can track the individual calls. You can do this by using the [call_id]
key word. I'm also not sure if you are using the concept of the
remote_ip/port correctly - it is not really used to populate the to
address field
