30 May
2006
30 May
'06
6:40 a.m.
My two cents:
OpenSER/SER can handle hundreds of concurrent calls, but as a 'simple'
SIP-Proxy not as a media-proxy (RTP-Proxy). Your numbers would be clearer if
You could aggregate information on the loads only from OpenSER/SER, without
MediaProxy or RTPProxy. You would get some very impressive numbers,
unfortunately dropped by the [Media|RTP]proxy presence.
Try to review Your configuration, so that You forward to media-aware servers
only calls that needed it (with one UA sitting behind a NAT box,p.ex.), not
all. It would give a 'little' more headache for design and maintenance, but
would permit a higher concurrent call number... ;)
Edson.
-----Original Message-----
From: users-bounces(a)openser.org [mailto:users-bounces@openser.org] On
Behalf Of unplug
Sent: segunda-feira, 29 de maio de 2006 22:23
To: Juha Heinanen
Cc: OpenSER-users
Subject: Re: [Users] OpenSER dimensioning. How many calls/sec can it set
up?
You are right that you can have 10 servers installed mediaproxy to
handle 300 concurrent calls. However, it is not a practical way to
implement a system to support several hundred concurrent calls using
several servers. As someone said, openser can handle several hundred
calls, maybe thousand. Comparing to my testing result, I have no idea
the capacity of openser can handle. Anyone can tell me the real
capacity that openser can handle?
On 5/29/06, Juha Heinanen <jh(a)tutpro.com> wrote:
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
unplug writes:
> mediaproxy spends much of the CPU to handle the call compared with
> rtpproxy. From the result that I made in the load test, the number
of
> concurrent call is much much less than we
expected.
> maximum concurrent call using mediaproxy (openser & mediaproxy in the
> same server): 30
> maximum concurrent call using rtpproxy (openser & rtpproxy in the
same
server):
60
you can distribute mediaproxy to as many host you want. or are you
saying that mediaproxy module functions use_mediaproxy/end_mediaproxy
are the bottleneck?
-- juha