Brian Peters wrote:
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.
------------------------------------------------------------------------
_______________________________________________
Users mailing list
Users(a)lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/users
You have a config file to share?
Are your network settings correct?
Are you doing the dump on the OpenSER box, or the Asterisk?
How are your system resources on the box (e.g. running 'top')?
10 invites per second is really nothing for OpenSER, so something else
must be going on.