Oh, nice! Thanks!

Do you also store state in the database?

From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Brooks Bridges
Sent: woensdag 20 juli 2016 23:03
To: Kamailio (SER) - Users Mailing List <sr-users@lists.sip-router.org>
Subject: Re: [SR-Users] Managing concurrent ports

We utilize the dialog module for concurrency control with several tens of thousands of channels at several thousand cps with zero issues.  As long as you spec the hardware suitably and configure the module properly, you won’t have any issues until you hit really crazy levels of traffic.  I think you’ll run out of resources on the network interfaces long before you have problems with the module itself.

Brooks Bridges | Sr. Voice Services Engineer

O¹ Communications

4359 Town Center Boulevard, Suite 217

El Dorado Hills, California 95762

office: 916.235.2097 | main: 888.444.1111, Option 2

email: bbridges@o1.com | web: www.o1.com

From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Grant Bagdasarian
Sent: Tuesday, July 19, 2016 11:46 PM
To: sr-users@lists.sip-router.org
Subject: [SR-Users] Managing concurrent ports

Hello,

Are there any recommended modules for managing concurrent ports for different endpoints/customers/accounts/etc?

I believe the dialog and dialog_ng modules do exactly this, but how is the performance of these modules under high loads?

What is the release time of the ports?

Are there perhaps other modules?

Regards,

Grant