Zou,
You may also find that setting a call limit (-l) and a maximum number of
sockets (-max_multi_socket) will help your situtation.
Charles
[EMAIL PROTECTED] wrote on 07/13/2007 04:04:45 AM:
> Hello Zou
>
> -t tn implies using TCP with one socket per call, so it's probable
> you faced sipp/system limitations at high call rate (which call rate
> ?). If you could avoid using this mode, it will be better.
>
> Regards,
> Olivier Boulkroune
>
> -----Message d'origine-----
> De : [EMAIL PROTECTED] [mailto:sipp-users-
> [EMAIL PROTECTED] De la part de ??
> Envoyé : vendredi 13 juillet 2007 08:17
> À : [email protected]
> Objet : [Sipp-users] Problem of SIPp and OpenSER in -t tn mode
>
>
>
> Hi, Dear all!
>
> We need to test a scenario that many clients connect to OpenSER
> proxy server. So, we used the
> -t tn mode. However, when call rate increases to some level, the
> SIPp will stop sending packets.
> Did anybody also encounter such problem? Or any suggestions to test
> such scenario for OpenSER?
> Thanks very much!
>
>
> Yours,
> Zou Jia
>
>
>
-------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Sipp-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/sipp-users
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
