[Serusers] Sipp and SER using TCP protocol

[Vaclav Kubart]

Hello,
I saw this behaviour in my SER performance tests related to presence
too. I guess that under heavy load SER sometimes closes TCP connection
and it needs to be reopened. I was not able to do this with sipp (an
older version). My solution was to write my own testing utility.

	Vaclav


On Mon, Jan 08, 2007 at 04:47:03AM -0800, Zeeshan Sajid wrote:
> Hey ppl,
> 
> I am trying to find out the peak number of calls that ser supports using sipp running the default scenario. I am using SER-0.9.6 and sipp version1.8 for this purpose.
> Now my setup on a local lan is 
> 
> SIpp (UAC)  ----------------------->    SER   -------------------->    Sipp (UAS)
> 192.168.0.8                                  192.168.0.200                      192.168.0.2
> 
> the commands that i have used are 
> for Sipp (UAC)
> ulimit -n 99999
> ./sipp -sn uac -rsa 192.168.0.200:5060 -i 192.168.0.8 -p 5061 192.168.0.2:5060 -t t1 -r 1000 -rp 10 
> 
> for Sipp (SER)
>  default settings
> 
> for Sipp (UAS)
>  ulimit -n 99999
> ./sipp -sn uas -i 192.168.0.2 -p 5060 -rsa 192.168.0.200:5060 -t tn
> 
> now the problem is that after a while the UAS crashes saying 
>  "Broken pipe on TCP connection, remote peer probably closed the socket."
> 
> my understanding is that SER is unable to handle the messages burst to the Sipp UAS and 
> 
> so please tell me how can i solve this problem .... thanks in advance
> 
> regards
> Zeeshan Sajid
> 
> 
>  __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 
> _______________________________________________
> Serusers mailing list
> Serusers at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers