Hi solarmon,
I don't immediately recall such a mechanism in any of the modules / core
logic.
However, you have the often underrated $shv global variables, which
allow you
can implement some remarkable piece of logic! For example:
* "drain" mode, where the server stops accepting new calls, in preparation
for maintenance
* test out a feature or a change in production while retaining the
ability to quickly
revert back if things go south (optionally, you can do this for a
subset of users!)
Best regards,
[1]: https://opensips.org/html/docs/modules/3.1.x/cfgutils.html#mi_shv_set
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS Summit, Amsterdam, May 2020
www.opensips.org/events
OpenSIPS Bootcamp, Miami, March 2020
www.opensips.org/training
On 20.01.2020 16:54, solarmon wrote:
Hi,
I have an opensips two node cluster, and using the dispatcher module
for 'internal' and 'external' endpoints.
What is the recommended graceful method to put this opensips cluster
in maintenance so that current calls are not affected. The overall
effect I am looking for is for the opensips cluster not to respond to
SIP Options pings from the endpoints.
Is it a simple case of making these endpoints 'inactive'? Will this
tell opensips not to respond to SIP Options pings FROM those endpoints?
Thank you.
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
