Brian -- Have had similar
problems recently.
1.
Run a netstat –su
and see if you are having “packet errors”. This means the udp
buffer is filling up.
2.
Check out the latest
from SVN. A patch recently implemented will honor the rev_dns=no.
3.
Increase the UDP
buffer size (I used this info: http://www.29west.com/docs/THPM/udp-buffer-sizing.html).
Mine is set to 1 Mb right now, and is now able to handle 10 invites per second.
Before making these changes I was dying at 3 per second.
I posted a message earlier this
week, that said that my OpenSER install is not correctly calculating the buffer
size as far as I can tell, but have not gotten a response on that yet.
Performance is still not as good as previous OpenSER versions with this setup
(we have a 1.2.1 server that is running circles around the three 1.3.2 servers).
I am using dbaliases to route calls on the 1.3.2 servers, and ENUM on the 1.2.1
server, but that is the only difference, and I would not expect that to make
this great of a difference.
Michael
From:
users-bounces@lists.openser.org [mailto:users-bounces@lists.openser.org] On
Behalf Of Brian Peters
Sent: Friday, May 23, 2008 1:15 PM
To: users@lists.openser.org
Subject: [OpenSER-Users] Openser not processing requests at rate being
sent to it
I am doing what I thought was a simple volume test that
OpenSER should be able to handle, but the results I am getting so far show it is
not handling the load I’m sending it.
Here is my configuration:
-
OpenSER 1.3.1
-
Simple script that uses OpenSER as a proxy to forward
requests to a carrier. All it does is rewrite the host and port of the R-URI
and relays to the carrier.
-
children=16
-
shared memory set to 1 G. (-m 1000)
-
using transaction module to handle the requests.
-
Sending 10 INVITE requests per second to OpenSER using
Asterisk.
When I do a “tcpdump” trace of the network
traffic to/from OpenSER, it is clear that a large percentage of the
INVITE requests sent to OpenSER were not handled. Asterisk needed to resend the
INVITE requests several times before OpenSER would handle them, and in about
20% of the cases Asterisk terminated the INVITES because it reached the timeout
of 30 seconds without any response.
If I go directly from asterisk to the carrier, this test
works without any issues. I’m not sure what the limitations are of
OpenSER, but this seems like something it should be able to handle.
Any help or information on how to configure OpenSER so it
will work would be appreciated.
Thanks,
Brian.
No virus found in this incoming message.
Checked by AVG.
Version: 7.5.524 / Virus Database: 269.24.0/1462 - Release Date: 5/23/2008 7:20
AM