14 Mar
2007
14 Mar
'07
2:19 p.m.
Hi everybody,
based on the newly 1.2.0 OpenSER release, we ran some tests in order to
give some realistic numbers about the performances of OpenSER. I think
it is a very useful information for our community or other interested
people.
For more, please refer to the news bulletin:
http://www.openser.org/mos/view/News/NewsItem/OpenSER-1.2.0---Perfomance-Te…
or directly to the tests results web page:
http://www.openser.org/docs/openser-performance-tests/
regards,
bogdan
14 Mar
14 Mar
3:14 p.m.
On Wednesday 14 March 2007 13:19, Bogdan-Andrei Iancu wrote:
Hi everybody,
based on the newly 1.2.0 OpenSER release, we ran some tests in order to
give some realistic numbers about the performances of OpenSER. I think
it is a very useful information for our community or other interested
people.
[..]
First of all congratulation to the successful release!
The numbers from your tests looks really good, over 8000 request per second
with standard hardware is very impressive. Have you run some of the tests
against e.g 1.1 or 0.9.5, to see how fast is the old version in comparison to
the new code?
Also, nice documentation work, it should be easy to reproduce the test with
other hardware or another release.
Regards,
Henning
4:12 p.m.
Hi Henning,
Henning Westerholt wrote:
On Wednesday 14 March 2007 13:19, Bogdan-Andrei Iancu
wrote:
thanks you.
Hi everybody,
based on the newly 1.2.0 OpenSER release, we ran some tests in order to
give some realistic numbers about the performances of OpenSER. I think
it is a very useful information for our community or other interested
people.
[..]
First of all congratulation to the successful release!
The numbers from your tests looks really good, over
8000 request per second
with standard hardware is very impressive.
This is a common mistake (no offence :)
) - we got 8000 *CALLS* per
second, where a call is formed of INVITE + reply + ACK + BYE + reply
(see call-related section).
For simple transactions for second, we got 15000 - a transaction is
counted as request + reply.
I notice in several other tests this confusion about a call and
transaction - and that was why we decided to do separate tests for each,
to avoid any doubts about what actually was measured.
Have you run some of the tests
against e.g 1.1 or 0.9.5, to see how fast is the old version in comparison to
the new code?
unfortunately no, because of time restrains :(
Also, nice documentation work, it should be easy to
reproduce the test with
other hardware or another release.
regards,
Bogdan
15 Mar
15 Mar
2:42 p.m.
On 14 Mar 2007, at 12:19, Bogdan-Andrei Iancu wrote:
based on the newly 1.2.0 OpenSER release, we ran some
tests in
order to give some realistic numbers about the performances of
OpenSER. I think it is a very useful information for our community
or other interested people.
http://www.openser.org/mos/view/News/NewsItem/OpenSER-1.2.0---
Perfomance-Tests/
I'm not trying to stir up trouble (honest), but it would be useful to
people who are new to [Open]SER if you published performance results
for your new stable release against the current stable release of SER.
cheers
Andy
3:04 p.m.
Hi Andy,
Andy Davidson wrote:
On 14 Mar 2007, at 12:19, Bogdan-Andrei Iancu wrote:
to be honest
I do not intend to do it and I do found it unethical to run
tests against other similar projects - I do not have the enough
knowledge or understanding to run relevant tests for other softwares
than openser.
we try to provide for the users the best info about openser - comparison
and decision should be the users's taks ;)
regards,
bogdan
based on the newly 1.2.0 OpenSER release, we ran
some tests in order
to give some realistic numbers about the performances of OpenSER. I
think it is a very useful information for our community or other
interested people.
http://www.openser.org/mos/view/News/NewsItem/OpenSER-1.2.0---Perfomance-Te…
I'm not trying to stir up trouble (honest), but it would be useful to
people who are new to [Open]SER if you published performance results
for your new stable release against the current stable release of SER. 
8:52 p.m.
New subject: [Users] config file syntax
Hi,
Is there a document that outlines the syntax rules used in openser.cfg?
Thanks,
Scott Yagel
PacketCall, Inc.
syagel(a)packetcall.net
11:09 p.m.
New subject: [Users] config file syntax
Hello,
On 03/15/07 20:52, Scott Yagel wrote:
Hi,
Is there a document that outlines the syntax rules used in openser.cfg?
there is work ongoing to get such a document, but was not with very high
priority so far. Now you get such details spread in several documents.
The dokuwiki is the place where you get the core variables and functions
(core cookbook), index for what modules exports, index for
pseudo-variables and transformations.
http://openser.org/dokuwiki/doku.php
Cheers,
Daniel
Thanks,
Scott Yagel
PacketCall, Inc.
syagel(a)packetcall.net
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
21 Mar
21 Mar
3:45 p.m.
New subject: [Users] config file syntax
I'm still looking for some help in understanding the syntax used in the cfg
files, such as what the following statement fragment really is doing:
if(uri =~"^sip:[0-9]{10}@")
etc, etc,
Is there a manual that interprets this in detail so that I can make changes
to the checking of dialed digits, for example?
The cookbook has helped some, but I have not found this type of detail in
it. Maybe I have just not looked in the right section?
Thanks,
Scott Yagel
PacketCall, Inc.
syagel(a)packetcall.net
5:42 p.m.
New subject: [Users] config file syntax
Scott Yagel wrote:
I'm still looking for some help in understanding
the syntax used in the cfg
files, such as what the following statement fragment really is doing:
if(uri =~"^sip:[0-9]{10}@")
uri is the request URI of the request, e.g:
INVITE sip:syagel@packetcall.net SIP/2.0
then uri would be "sip:syagel@packetcall.net"
=~ means regular expression comparison, thus the following regular
expression will be applied and if it matches the if condition returns
TRUE, otherwise false.
^sip:[0-9]{10}@
this is the regular expression. The uri must start (^) with "sip:". Then
there must be 10 digits followed by an "@". In short: the username must
be a 10 digit phone number.
regards
klaus
etc, etc,
Is there a manual that interprets this in detail so that I can make changes
to the checking of dialed digits, for example?
The cookbook has helped some, but I have not found this type of detail in
it. Maybe I have just not looked in the right section?
Thanks,
Scott Yagel
PacketCall, Inc.
syagel(a)packetcall.net
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
11:43 p.m.
New subject: [Users] config file syntax
Thanks, Klaus.
Scott Yagel
PacketCall, Inc.
syagel(a)packetcall.net
-----Original Message-----
From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at]
Sent: Wednesday, March 21, 2007 10:43 AM
To: syagel(a)packetcall.net
Cc: daniel(a)voice-system.ro; 'users openser.org'
Subject: Re: [Users] config file syntax
Scott Yagel wrote:
I'm still looking for some help in understanding
the syntax used in the
cfg
files, such as what the following statement fragment
really is doing:
if(uri =~"^sip:[0-9]{10}@")
uri is the request URI of the request, e.g:
INVITE sip:syagel@packetcall.net SIP/2.0
then uri would be "sip:syagel@packetcall.net"
=~ means regular expression comparison, thus the following regular
expression will be applied and if it matches the if condition returns
TRUE, otherwise false.
^sip:[0-9]{10}@
this is the regular expression. The uri must start (^) with "sip:". Then
there must be 10 digits followed by an "@". In short: the username must
be a 10 digit phone number.
regards
klaus
etc, etc,
Is there a manual that interprets this in detail so that I can make
changes
to the checking of dialed digits, for example?
The cookbook has helped some, but I have not found this type of detail in
it. Maybe I have just not looked in the right section?
Thanks,
Scott Yagel
PacketCall, Inc.
syagel(a)packetcall.net
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
22 Mar
22 Mar
6:57 p.m.
New subject: [Users] config file syntax
Klaus,
Is this syntax documented anywhere?
For instance, I want to catch all 1xx (exactly 3 digits, starting with 1)
and send them to the SEMS conference application. So would I use something
like:
if(uri =~"^sip:1[0-9]{3}@")
etc,etc
Thanks,
Scott Yagel
PacketCall, Inc.
syagel(a)packetcall.net
-----Original Message-----
From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at]
Sent: Wednesday, March 21, 2007 10:43 AM
To: syagel(a)packetcall.net
Cc: daniel(a)voice-system.ro; 'users openser.org'
Subject: Re: [Users] config file syntax
Scott Yagel wrote:
I'm still looking for some help in understanding
the syntax used in the
cfg
files, such as what the following statement fragment
really is doing:
if(uri =~"^sip:[0-9]{10}@")
uri is the request URI of the request, e.g:
INVITE sip:syagel@packetcall.net SIP/2.0
then uri would be "sip:syagel@packetcall.net"
=~ means regular expression comparison, thus the following regular
expression will be applied and if it matches the if condition returns
TRUE, otherwise false.
^sip:[0-9]{10}@
this is the regular expression. The uri must start (^) with "sip:". Then
there must be 10 digits followed by an "@". In short: the username must
be a 10 digit phone number.
regards
klaus
7:10 p.m.
New subject: [Users] config file syntax
Scott Yagel wrote:
Klaus,
Is this syntax documented anywhere?
For instance, I want to catch all 1xx (exactly 3 digits, starting with 1)
and send them to the SEMS conference application. So would I use something
like:
if(uri =~"^sip:1[0-9]{3}@")
you need: if(uri =~"^sip:1[0-9]{2}@")
you have to learn "regular expressions". Just google for it. openser
uses POSIX regular expressions.
regards
klaus
etc,etc
Thanks,
Scott Yagel
PacketCall, Inc.
syagel(a)packetcall.net
-----Original Message-----
From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at]
Sent: Wednesday, March 21, 2007 10:43 AM
To: syagel(a)packetcall.net
Cc: daniel(a)voice-system.ro; 'users openser.org'
Subject: Re: [Users] config file syntax
Scott Yagel wrote:
I'm still looking for some help in
understanding the syntax used in the
cfg
files, such as what the following statement
fragment really is doing:
if(uri =~"^sip:[0-9]{10}@")
uri is the request URI of the request, e.g:
INVITE sip:syagel@packetcall.net SIP/2.0
then uri would be "sip:syagel@packetcall.net"
=~ means regular expression comparison, thus the following regular
expression will be applied and if it matches the if condition returns
TRUE, otherwise false.
^sip:[0-9]{10}@
this is the regular expression. The uri must start (^) with "sip:". Then
there must be 10 digits followed by an "@". In short: the username must
be a 10 digit phone number.
regards
klaus
6456
days inactive
6464
days old
11 comments
6 participants
participants (6)
-
Andy Davidson -
Bogdan-Andrei Iancu -
Daniel-Constantin Mierla -
Henning Westerholt -
Klaus Darilion -
Scott Yagel