11 Oct
2005
11 Oct
'05
1:31 a.m.
Impossible to say!
ser is really fast if it only does stupid forwarding.
In real life scenarios the performance depends on the whole system.
Probably you will have db lookups for authentication, user preferences,
accounting... Further you will DNS lookups for domain resolution and ENUM.
These tasks are much more time consuming than the plain SIP processing
in ser. Thus, any value someone will give you, 10-100000 are all values
for a certain scenario and valid in this scenario.
Thus, try to avoid exec and multiple db lookups. Use good performing
recursive nameservers.
rtp proxies: I was told that on Linux the limit is caused by the Linux
kernel which does not handle high packet rates very well.
If you want to test your proxy: use sipp and make sure you have real
life scenarios (with db lookups and DNS lookups)
regards
klaus
Martin, Peter wrote:
Let's say, just sip proxy...
Regards,
Peter Martin
-----Original Message-----
From: Daryl Sanders [mailto:daryl.sanders@gmail.com]
Sent: Monday, October 10, 2005 3:35 PM
To: Martin, Peter
Subject: Re: [Serusers] SER Calls Per Second
This depends on if you will be proxying the media stream or if you are
just handling call setup with SER. If you plan to carry the media you
will need to use rtpproxy or mediaproxy along with SER. It will also
matter if you are using SER as the registrar on the same box or just
routing calls. In addition, the specs of the box/boxes you'll be using
will have a huge effect on the number of calls.
- Daryl
On 10/10/05, Martin, Peter <Peter.Martin(a)ipc.com> wrote:
Anyone know what is the most calls per second that has been tested
and verified using SER?
Peter Martin
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers