The dialog module remains the best-practical way of doing this, and it
performs fine under high loads.
It's either that, or build your own dialog state machine using htable or
whatever. Except it won't be as good at dealing with all possible
eventualities in the complex lifecycle of a dialog as the dialog module
itself.
On 07/20/2016 02:46 AM, Grant Bagdasarian wrote:
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
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Alex Balashov | Principal | Evariste Systems LLC
1447 Peachtree Street NE, Suite 700
Atlanta, GA 30309
United States
Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
