25 May
2006
25 May
'06
7:26 a.m.
Hello,
I am deploying OpenSER to distribute calls for a number of Asterisk boxes. I
believe there are some people on this list to have a similar setup. I'd like
to know what kind of hardware do you guys run OpenSER on and how many calls
per second can you set up with your specs. I am looking to set up about
30-40 calls per second so I was wondering what kind of hardware I'd need.
ScriptHead
26 May
26 May
12:08 a.m.
Hello,
On 05/25/06 07:26, Script Head wrote:
Hello,
I am deploying OpenSER to distribute calls for a number of Asterisk
boxes. I believe there are some people on this list to have a similar
setup. I'd like to know what kind of hardware do you guys run OpenSER
on and how many calls per second can you set up with your specs. I am
looking to set up about 30-40 calls per second so I was wondering what
kind of hardware I'd need.
a usual pc nowadays should do it without any
problems. The amount of
registered users influence the memory usage, the 30-40 call setups per
second has no big impact in the system.
Cheers,
Daniel
ScriptHead
------------------------------------------------------------------------
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
4:33 a.m.
Hi,
How about using openser to handle over several hundred calls per
second? If not possbile, what is the limitation of openser to handle
call?
On 5/26/06, Daniel-Constantin Mierla <daniel(a)voice-system.ro> wrote:
Hello,
On 05/25/06 07:26, Script Head wrote:
Hello,
I am deploying OpenSER to distribute calls for a number of Asterisk
boxes. I believe there are some people on this list to have a similar
setup. I'd like to know what kind of hardware do you guys run OpenSER
on and how many calls per second can you set up with your specs. I am
looking to set up about 30-40 calls per second so I was wondering what
kind of hardware I'd need.
a usual pc nowadays should do it without any
problems. The amount of
registered users influence the memory usage, the 30-40 call setups per
second has no big impact in the system.
Cheers,
Daniel
ScriptHead
------------------------------------------------------------------------
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
10:58 a.m.
unplug wrote:
Hi,
How about using openser to handle over several hundred calls per
second? If not possbile, what is the limitation of openser to handle
call?
Probably the bottle neck is all the backend processing (database lookups
for AVPs, authentication, ...)
regards
klaus
On 5/26/06, Daniel-Constantin Mierla <daniel(a)voice-system.ro> wrote:
Hello,
On 05/25/06 07:26, Script Head wrote:
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users Hello,
I am deploying OpenSER to distribute calls for a number of Asterisk
boxes. I believe there are some people on this list to have a similar
setup. I'd like to know what kind of hardware do you guys run OpenSER
on and how many calls per second can you set up with your specs. I am
looking to set up about 30-40 calls per second so I was wondering what
kind of hardware I'd need.
a usual pc nowadays should do it without any
problems. The amount of
registered users influence the memory usage, the 30-40 call setups per
second has no big impact in the system.
Cheers,
Daniel
ScriptHead
------------------------------------------------------------------------
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
12:31 p.m.
On 05/26/06 04:33, unplug wrote:
Hi,
How about using openser to handle over several hundred calls per
second?
Very important is your configuration script. If you run openser just as
a simple proxy, then it can go up to thousands of call setups per
second. The performances increase if you use it in stateless mode -
suitable for load balancing/dispatching.
The only way to measure the real capacity of your platform is to set it
up in a lab and then perform some tests using tools like sipp.
Daniel
If not possbile, what is the limitation of openser to
handle
call?
On 5/26/06, Daniel-Constantin Mierla <daniel(a)voice-system.ro> wrote:
Hello,
On 05/25/06 07:26, Script Head wrote:
Hello,
I am deploying OpenSER to distribute calls for a number of Asterisk
boxes. I believe there are some people on this list to have a similar
setup. I'd like to know what kind of hardware do you guys run OpenSER
on and how many calls per second can you set up with your specs. I am
looking to set up about 30-40 calls per second so I was wondering what
kind of hardware I'd need.
a usual pc nowadays should do it without any
problems. The amount of
registered users influence the memory usage, the 30-40 call setups per
second has no big impact in the system.
Cheers,
Daniel
ScriptHead
------------------------------------------------------------------------
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
2:45 p.m.
Hi ,
I have done some tests in the environment below.
PC1: sipp
PC2: openser+mediaproxy (NAT)
script: nat-mediaproxy.5.0.cfg from configs.GettingStarted.tar.gz
Below is the testing parameter shown in sipp
3 calls / second
concurrent call: 30
Over 30 concurrent calls, message 481 begins to happen. The CPU usage
of PC2 is almost 90% and then PC2 will hang.
As I expect openser should handle over thousand of calls but there is
a different between my testing. What I miss to configure for getting
more concurrent call?
On 5/26/06, Daniel-Constantin Mierla <daniel(a)voice-system.ro> wrote:
On 05/26/06 04:33, unplug wrote:
Hi,
How about using openser to handle over several hundred calls per
second?
Very important is your configuration script. If you run openser just as
a simple proxy, then it can go up to thousands of call setups per
second. The performances increase if you use it in stateless mode -
suitable for load balancing/dispatching.
The only way to measure the real capacity of your platform is to set it
up in a lab and then perform some tests using tools like sipp.
Daniel
If not possbile, what is the limitation of
openser to handle
call?
On 5/26/06, Daniel-Constantin Mierla <daniel(a)voice-system.ro> wrote:
Hello,
On 05/25/06 07:26, Script Head wrote:
Hello,
I am deploying OpenSER to distribute calls for a number of Asterisk
boxes. I believe there are some people on this list to have a similar
setup. I'd like to know what kind of hardware do you guys run OpenSER
on and how many calls per second can you set up with your specs. I am
looking to set up about 30-40 calls per second so I was wondering what
kind of hardware I'd need.
a usual pc nowadays should do it without any
problems. The amount of
registered users influence the memory usage, the 30-40 call setups per
second has no big impact in the system.
Cheers,
Daniel
ScriptHead
------------------------------------------------------------------------
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
2:49 p.m.
unplug wrote:
Hi ,
I have done some tests in the environment below.
PC1: sipp
PC2: openser+mediaproxy (NAT)
script: nat-mediaproxy.5.0.cfg from configs.GettingStarted.tar.gz
Below is the testing parameter shown in sipp
3 calls / second
concurrent call: 30
Over 30 concurrent calls, message 481 begins to happen. The CPU usage
of PC2 is almost 90% and then PC2 will hang.
Make a single call any watch how long the processing of the message
takes (ngrep -t)
regards
klaus
As I expect openser should handle over thousand of calls but there is
a different between my testing. What I miss to configure for getting
more concurrent call?
On 5/26/06, Daniel-Constantin Mierla <daniel(a)voice-system.ro> wrote:
On 05/26/06 04:33, unplug wrote:
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users Hi,
How about using openser to handle over several hundred calls per
second?
Very important is your configuration script. If you run openser just as
a simple proxy, then it can go up to thousands of call setups per
second. The performances increase if you use it in stateless mode -
suitable for load balancing/dispatching.
The only way to measure the real capacity of your platform is to set it
up in a lab and then perform some tests using tools like sipp.
Daniel
If not possbile, what is the limitation of
openser to handle
call?
On 5/26/06, Daniel-Constantin Mierla <daniel(a)voice-system.ro> wrote:
> Hello,
>
> On 05/25/06 07:26, Script Head wrote:
> > Hello,
> >
> > I am deploying OpenSER to distribute calls for a number of Asterisk
> > boxes. I believe there are some people on this list to have a
similar
> > setup. I'd like to know what kind of
hardware do you guys run
OpenSER
> > on and how many calls per second can you
set up with your specs.
I am
> > looking to set up about 30-40 calls per
second so I was wondering
what
> > kind of hardware I'd need.
> a usual pc nowadays should do it without any problems. The amount of
> registered users influence the memory usage, the 30-40 call setups per
> second has no big impact in the system.
>
> Cheers,
> Daniel
>
> >
> > ScriptHead
> >
>
------------------------------------------------------------------------
>
> _______________________________________________
> Users mailing list
> Users(a)openser.org
> http://openser.org/cgi-bin/mailman/listinfo/users
>
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
3:28 p.m.
what about the type of server used? (processor(s) memory,...)
Olivier
unplug a écrit :
Hi ,
I have done some tests in the environment below.
PC1: sipp
PC2: openser+mediaproxy (NAT)
script: nat-mediaproxy.5.0.cfg from configs.GettingStarted.tar.gz
Below is the testing parameter shown in sipp
3 calls / second
concurrent call: 30
Over 30 concurrent calls, message 481 begins to happen. The CPU usage
of PC2 is almost 90% and then PC2 will hang.
As I expect openser should handle over thousand of calls but there is
a different between my testing. What I miss to configure for getting
more concurrent call?
On 5/26/06, Daniel-Constantin Mierla <daniel(a)voice-system.ro> wrote:
On 05/26/06 04:33, unplug wrote:
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
Hi,
How about using openser to handle over several hundred calls per
second?
Very important is your configuration script. If you run openser just as
a simple proxy, then it can go up to thousands of call setups per
second. The performances increase if you use it in stateless mode -
suitable for load balancing/dispatching.
The only way to measure the real capacity of your platform is to set it
up in a lab and then perform some tests using tools like sipp.
Daniel
If not possbile, what is the limitation of
openser to handle
call?
On 5/26/06, Daniel-Constantin Mierla <daniel(a)voice-system.ro> wrote:
> Hello,
>
> On 05/25/06 07:26, Script Head wrote:
> > Hello,
> >
> > I am deploying OpenSER to distribute calls for a number of Asterisk
> > boxes. I believe there are some people on this list to have a
similar
> > setup. I'd like to know what kind of
hardware do you guys run
OpenSER
> > on and how many calls per second can you
set up with your specs.
I am
> > looking to set up about 30-40 calls per
second so I was
wondering what
> > kind of hardware I'd need.
> a usual pc nowadays should do it without any problems. The amount of
> registered users influence the memory usage, the 30-40 call setups
per
> second has no big impact in the system.
>
> Cheers,
> Daniel
>
> >
> > ScriptHead
> >
>
------------------------------------------------------------------------
>
> _______________________________________________
> Users mailing list
> Users(a)openser.org
> http://openser.org/cgi-bin/mailman/listinfo/users
>
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
4:53 p.m.
olivier.taylor wrote:
what about the type of server used? (processor(s)
memory,...)
Of course the processor matters. But if you get only 3 calls/second on a
decent system, you may get 10 calls per second on a high performance
system. But you did not eliminate the bottleneck.
If you have slow backends (DB, DNS, radius) you may also try to increase
the number of thread (childrens) to allow more concurrent transactions.
regards
klaus
Olivier
unplug a écrit :
Hi ,
I have done some tests in the environment below.
PC1: sipp
PC2: openser+mediaproxy (NAT)
script: nat-mediaproxy.5.0.cfg from configs.GettingStarted.tar.gz
Below is the testing parameter shown in sipp
3 calls / second
concurrent call: 30
Over 30 concurrent calls, message 481 begins to happen. The CPU usage
of PC2 is almost 90% and then PC2 will hang.
As I expect openser should handle over thousand of calls but there is
a different between my testing. What I miss to configure for getting
more concurrent call?
On 5/26/06, Daniel-Constantin Mierla <daniel(a)voice-system.ro> wrote:
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
On 05/26/06 04:33, unplug wrote:
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
Hi,
How about using openser to handle over several hundred calls per
second?
Very important is your configuration script. If you run openser just as
a simple proxy, then it can go up to thousands of call setups per
second. The performances increase if you use it in stateless mode -
suitable for load balancing/dispatching.
The only way to measure the real capacity of your platform is to set it
up in a lab and then perform some tests using tools like sipp.
Daniel
If not possbile, what is the limitation of
openser to handle
call?
On 5/26/06, Daniel-Constantin Mierla <daniel(a)voice-system.ro> wrote:
> Hello,
>
> On 05/25/06 07:26, Script Head wrote:
> > Hello,
> >
> > I am deploying OpenSER to distribute calls for a number of Asterisk
> > boxes. I believe there are some people on this list to have a
similar
> > setup. I'd like to know what kind of
hardware do you guys run
OpenSER
> > on and how many calls per second can you
set up with your specs.
I am
> > looking to set up about 30-40 calls per
second so I was
wondering what
> > kind of hardware I'd need.
> a usual pc nowadays should do it without any problems. The amount of
> registered users influence the memory usage, the 30-40 call setups
per
> second has no big impact in the system.
>
> Cheers,
> Daniel
>
> >
> > ScriptHead
> >
>
------------------------------------------------------------------------
> >
> > _______________________________________________
> > Users mailing list
> > Users(a)openser.org
> > http://openser.org/cgi-bin/mailman/listinfo/users
> >
>
> _______________________________________________
> Users mailing list
> Users(a)openser.org
> http://openser.org/cgi-bin/mailman/listinfo/users
>
5:13 p.m.
You are right, of course, but that doesn't w-tell me what processor has
been used for the previous tests.
If if was a double xeon(64 bits), 3.2Ghz, raid disks 8Gb memory, it
means I better to buy a more than decent machine for 30 calls/seconds :)
kind regards,
Olivier
Klaus Darilion a écrit :
olivier.taylor wrote:
what about the type of server used? (processor(s)
memory,...)
Of course the processor matters. But if you get only 3 calls/second on
a decent system, you may get 10 calls per second on a high performance
system. But you did not eliminate the bottleneck.
If you have slow backends (DB, DNS, radius) you may also try to
increase the number of thread (childrens) to allow more concurrent
transactions.
regards
klaus
Olivier
unplug a écrit :
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
Hi ,
I have done some tests in the environment below.
PC1: sipp
PC2: openser+mediaproxy (NAT)
script: nat-mediaproxy.5.0.cfg from configs.GettingStarted.tar.gz
Below is the testing parameter shown in sipp
3 calls / second
concurrent call: 30
Over 30 concurrent calls, message 481 begins to happen. The CPU usage
of PC2 is almost 90% and then PC2 will hang.
As I expect openser should handle over thousand of calls but there is
a different between my testing. What I miss to configure for getting
more concurrent call?
On 5/26/06, Daniel-Constantin Mierla <daniel(a)voice-system.ro> wrote:
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
On 05/26/06 04:33, unplug wrote:
> Hi,
> How about using openser to handle over several hundred calls per
> second?
Very important is your configuration script. If you run openser
just as
a simple proxy, then it can go up to thousands of call setups per
second. The performances increase if you use it in stateless mode -
suitable for load balancing/dispatching.
The only way to measure the real capacity of your platform is to
set it
up in a lab and then perform some tests using tools like sipp.
Daniel
> If not possbile, what is the limitation of openser to handle
> call?
>
> On 5/26/06, Daniel-Constantin Mierla <daniel(a)voice-system.ro> wrote:
>> Hello,
>>
>> On 05/25/06 07:26, Script Head wrote:
>> > Hello,
>> >
>> > I am deploying OpenSER to distribute calls for a number of
Asterisk
>> > boxes. I believe there are some people on this list to have a
similar
>> > setup. I'd like to know what kind of hardware do you guys run
OpenSER
>> > on and how many calls per second can you set up with your
specs. I am
>> > looking to set up about 30-40 calls per second so I was
wondering what
>> > kind of hardware I'd need.
>> a usual pc nowadays should do it without any problems. The
amount of
>> registered users influence the memory usage, the 30-40 call
setups per
>> second has no big impact in the system.
>>
>> Cheers,
>> Daniel
>>
>> >
>> > ScriptHead
>> >
>>
------------------------------------------------------------------------
>> >
>> > _______________________________________________
>> > Users mailing list
>> > Users(a)openser.org
>> > http://openser.org/cgi-bin/mailman/listinfo/users
>> >
>>
>> _______________________________________________
>> Users mailing list
>> Users(a)openser.org
>> http://openser.org/cgi-bin/mailman/listinfo/users
>>
>
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
6:07 p.m.
I think the problem in this test is the mediaproxy. It's extremely slow, in
my experience it's much slower than rtpproxy. That is no way a problem with
SER.
On 5/26/06, unplug <maillisting(a)gmail.com> wrote:
Hi ,
I have done some tests in the environment below.
PC1: sipp
PC2: openser+mediaproxy (NAT)
script: nat-mediaproxy.5.0.cfg from configs.GettingStarted.tar.gz
Below is the testing parameter shown in sipp
3 calls / second
concurrent call: 30
Over 30 concurrent calls, message 481 begins to happen. The CPU usage
of PC2 is almost 90% and then PC2 will hang.
As I expect openser should handle over thousand of calls but there is
a different between my testing. What I miss to configure for getting
more concurrent call?
On 5/26/06, Daniel-Constantin Mierla <daniel(a)voice-system.ro> wrote:
On 05/26/06 04:33, unplug wrote:
similar
Hi,
How about using openser to handle over several hundred calls per
second?
Very important is your configuration script. If you run openser just as
a simple proxy, then it can go up to thousands of call setups per
second. The performances increase if you use it in stateless mode -
suitable for load balancing/dispatching.
The only way to measure the real capacity of your platform is to set it
up in a lab and then perform some tests using tools like sipp.
Daniel
> If not possbile, what is the limitation of openser to handle
> call?
>
> On 5/26/06, Daniel-Constantin Mierla <daniel(a)voice-system.ro> wrote:
>> Hello,
>>
>> On 05/25/06 07:26, Script Head wrote:
>> > Hello,
>> >
>> > I am deploying OpenSER to distribute calls for a number of Asterisk
>> > boxes. I believe there are some people on this list to have a >> > setup. I'd like to know what
kind of hardware do you guys run
OpenSER
>> > on and how many calls per second
can you set up with your specs. I
am
>> > looking to set up about 30-40 calls
per second so I was wondering
what
>> > kind of hardware I'd need.
>> a usual pc nowadays should do it without any problems. The amount of
>> registered users influence the memory usage, the 30-40 call setups
per
>> second has no big impact in the system.
>>
>> Cheers,
>> Daniel
>>
>> >
>> > ScriptHead
>> >
>>
------------------------------------------------------------------------
>
> _______________________________________________
> Users mailing list
> Users(a)openser.org
> http://openser.org/cgi-bin/mailman/listinfo/users
>
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
29 May
29 May
6:22 a.m.
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
Call making over the above limitatioin will cause the system unstable
and busy with message 481 and 408.
I have already using the basic configuration file downloaded from
http://www.onsip.org/modules/mydownloads/singlefile.php?cid=7&lid=24
From the above result, I wonder the performance of
openser that it can
handle the calls. I may test it in the wrong way but it is what
I
have done in the simple way. Anyone can tell me how you can do the
load test of openser with sipp?
On 5/26/06, Script Head <scripthead(a)gmail.com> wrote:
I think the problem in this test is the mediaproxy.
It's extremely slow, in
my experience it's much slower than rtpproxy. That is no way a problem with
SER.
On 5/26/06, unplug <maillisting(a)gmail.com> wrote:
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
Hi ,
I have done some tests in the environment below.
PC1: sipp
PC2: openser+mediaproxy (NAT)
script: nat-mediaproxy.5.0.cfg from configs.GettingStarted.tar.gz
Below is the testing parameter shown in sipp
3 calls / second
concurrent call: 30
Over 30 concurrent calls, message 481 begins to happen. The CPU usage
of PC2 is almost 90% and then PC2 will hang.
As I expect openser should handle over thousand of calls but there is
a different between my testing. What I miss to configure for getting
more concurrent call?
On 5/26/06, Daniel-Constantin Mierla <daniel(a)voice-system.ro> wrote:
>
> On 05/26/06 04:33, unplug wrote:
> > Hi,
> > How about using openser to handle over several hundred calls per
> > second?
>
> Very important is your configuration script. If you run openser just as
> a simple proxy, then it can go up to thousands of call setups per
> second. The performances increase if you use it in stateless mode -
> suitable for load balancing/dispatching.
>
> The only way to measure the real capacity of your platform is to set it
> up in a lab and then perform some tests using tools like sipp.
>
> Daniel
>
> > If not possbile, what is the limitation of openser to handle
> > call?
> >
> > On 5/26/06, Daniel-Constantin Mierla < daniel(a)voice-system.ro> wrote:
> >> Hello,
> >>
> >> On 05/25/06 07:26, Script Head wrote:
> >> > Hello,
> >> >
> >> > I am deploying OpenSER to distribute calls for a number of Asterisk
> >> > boxes. I believe there are some people on this list to have a
similar
> >> > setup. I'd like to know
what kind of hardware do you guys run
OpenSER
> >> > on and how many calls per
second can you set up with your specs. I
am
> >> > looking to set up about 30-40
calls per second so I was wondering
what
> >> > kind of hardware I'd
need.
> >> a usual pc nowadays should do it without any problems. The amount of
> >> registered users influence the memory usage, the 30-40 call setups
per
> >> second has no big impact in the
system.
> >>
> >> Cheers,
> >> Daniel
> >>
> >> >
> >> > ScriptHead
> >> >
> >>
------------------------------------------------------------------------
> >
> > _______________________________________________
> > Users mailing list
> > Users(a)openser.org
> > http://openser.org/cgi-bin/mailman/listinfo/users
> >
>
> _______________________________________________
> Users mailing list
> Users(a)openser.org
> http://openser.org/cgi-bin/mailman/listinfo/users
>
8:24 a.m.
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
30 May
30 May
4:23 a.m.
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:
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
4: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
11:55 a.m.
What do you mean a 'simple' SIP-Proxy?
Is it UA -- SIPproxy -- UA?
I have also tested openser without using NAT (All device is in the
same network). But the maximum number of current calls is only around
80.
For the configuration file, I use those files download from
http://www.onsip.org/. I think they are the simple configuration that
I can trust.
Finally, just want to say the target usage of openser. Does it target
for a small group of users instead of a global voip environment?
On 5/30/06, Edson <4lists(a)gmail.com> wrote:
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
31 May
31 May
12:23 p.m.
Hi,
simple SIP-Proxy refer to a simple config file, like the one provided
by default by openser.
Performance will decrease once your script complexity increases.
but notice that if you do not use any kind of media relay, the proxy is
not affected by the number of parallel calls since it;s transaction
stateful and not dialog stateful....so you can have hundred of thousands
of call in parallel with 0 load on the proxy.
regards,
bogdan
unplug wrote:
What do you mean a 'simple' SIP-Proxy?
Is it UA -- SIPproxy -- UA?
I have also tested openser without using NAT (All device is in the
same network). But the maximum number of current calls is only around
80.
For the configuration file, I use those files download from
http://www.onsip.org/. I think they are the simple configuration that
I can trust.
Finally, just want to say the target usage of openser. Does it target
for a small group of users instead of a global voip environment?
On 5/30/06, Edson <4lists(a)gmail.com> wrote:
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.
use_mediaproxy/end_mediaproxy
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
-----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:
> 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 are the
bottleneck?
-- juha
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users 
30 May
30 May
3:10 p.m.
On P4 3.0 GHz, we use RTPProxy, and on 80 concurent calls CPU is 5%.
In start we have used Media proxy, but we have problems, and we switch to
RTPProxy.
6756
days inactive
6762
days old
17 comments
9 participants
participants (9)
-
Bogdan-Andrei Iancu -
Daniel-Constantin Mierla -
Edson -
Juha Heinanen -
Klaus Darilion -
olivier.taylor -
Script Head -
Taras Bendik -
unplug