<div dir="ltr"><div>Another approach you may consider is to drop inbound OPTIONS packets by means of iptables (if you'd prefer not to touch the OpenSIPS configuration).<br></div><div>Just run from CLI the command like this:</div><div>iptables -I INPUT -p udp -m udp --dport 5060 -m string --string "OPTIONS sip:" --algo bm --to 65535 -j DROP<br><br>And then delete this rule when not needed anymore:<br>iptables -D INPUT -p udp -m udp --dport 5060 -m string --string "OPTIONS sip:" --algo bm --to 65535 -j DROP</div><div><br></div><div>Of course, the parameters will be pertinent to your specific implementation - protocol, port and optionally source IP(s).</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jan 21, 2020 at 8:09 AM <<a href="mailto:users-request@lists.opensips.org">users-request@lists.opensips.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Send Users mailing list submissions to<br>
<a href="mailto:users@lists.opensips.org" target="_blank">users@lists.opensips.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:users-request@lists.opensips.org" target="_blank">users-request@lists.opensips.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:users-owner@lists.opensips.org" target="_blank">users-owner@lists.opensips.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Users digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: opensips - graceful maintenance mode? (solarmon)<br>
2. Re: opensips - graceful maintenance mode? (Liviu Chircu)<br>
3. Re: opensips - graceful maintenance mode? (solarmon)<br>
4. Re: opensips - graceful maintenance mode? (Liviu Chircu)<br>
5. Re: opensips - graceful maintenance mode? (solarmon)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 21 Jan 2020 12:21:56 +0000<br>
From: solarmon <<a href="mailto:solarmon@one-n.co.uk" target="_blank">solarmon@one-n.co.uk</a>><br>
To: OpenSIPS users mailling list <<a href="mailto:users@lists.opensips.org" target="_blank">users@lists.opensips.org</a>><br>
Subject: Re: [OpenSIPS-Users] opensips - graceful maintenance mode?<br>
Message-ID:<br>
<CAOXfywMsyQ27Y78O=<a href="mailto:GO-AnxyGgSPZXTg9bjMsUtAF1-C3JCUFw@mail.gmail.com" target="_blank">GO-AnxyGgSPZXTg9bjMsUtAF1-C3JCUFw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi Liviu,<br>
<br>
Apologies, I should be more clear.<br>
<br>
The dispatcher endpoints that I have configured are used for routing the<br>
SIP calls to. They are also the endpoints that we are receiving SIP calls<br>
from.<br>
<br>
I understand that opensips are sending SIP Options pings to these<br>
endpoints. And these endpoints are sending SIP Options pings to opensips<br>
and getting a response.<br>
<br>
I would like to understand if I set these endpoints to 'inactive' whether<br>
that means opensips will stop responding to SIP Options pings from that<br>
particular endpoint.<br>
<br>
However, now I have checked our opensips.cfg script (that was created for<br>
us) it looks like it has been hardcoded in:<br>
<br>
route[handle_pings]<br>
{<br>
# keepalive notifies replied ok<br>
if ( is_method("NOTIFY|OPTIONS") && !has_totag() && $rU==NULL) {<br>
send_reply("200", "OK");<br>
exit;<br>
}<br>
}<br>
<br>
<br>
<br>
<br>
On Tue, 21 Jan 2020 at 11:58, Liviu Chircu <<a href="mailto:liviu@opensips.org" target="_blank">liviu@opensips.org</a>> wrote:<br>
<br>
> On 21.01.2020 13:47, solarmon wrote:<br>
> ><br>
> > So to be clear, I cannot use the dispatcher endpoint method to stop<br>
> > responding to SIP Options pings? If I can do that, then that is the<br>
> > equivalent - since our platform would see opensips as unhealthy and<br>
> > not send calls to it.<br>
><br>
> What do you mean by "dispatcher endpoint method"? Also, the dispatcher<br>
> module<br>
> ORIGINATES pings to its destinations, it does not RESPOND to them.<br>
> Maybe I'm<br>
> not on par with your terminology here :)<br>
><br>
> --<br>
> Liviu Chircu<br>
> <a href="http://www.twitter.com/liviuchircu" rel="noreferrer" target="_blank">www.twitter.com/liviuchircu</a> | <a href="http://www.opensips-solutions.com" rel="noreferrer" target="_blank">www.opensips-solutions.com</a><br>
><br>
> OpenSIPS Summit, Amsterdam, May 2020<br>
> <a href="http://www.opensips.org/events" rel="noreferrer" target="_blank">www.opensips.org/events</a><br>
> OpenSIPS Bootcamp, Miami, March 2020<br>
> <a href="http://www.opensips.org/training" rel="noreferrer" target="_blank">www.opensips.org/training</a><br>
><br>
><br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
> <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.opensips.org/pipermail/users/attachments/20200121/7e426355/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.opensips.org/pipermail/users/attachments/20200121/7e426355/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Tue, 21 Jan 2020 14:28:20 +0200<br>
From: Liviu Chircu <<a href="mailto:liviu@opensips.org" target="_blank">liviu@opensips.org</a>><br>
To: OpenSIPS users mailling list <<a href="mailto:users@lists.opensips.org" target="_blank">users@lists.opensips.org</a>><br>
Subject: Re: [OpenSIPS-Users] opensips - graceful maintenance mode?<br>
Message-ID: <<a href="mailto:6377cb24-0509-1435-bffa-888c5f282228@opensips.org" target="_blank">6377cb24-0509-1435-bffa-888c5f282228@opensips.org</a>><br>
Content-Type: text/plain; charset=utf-8; format=flowed<br>
<br>
On 21.01.2020 14:21, solarmon wrote:<br>
> However, now I have checked our opensips.cfg script (that was created <br>
> for us) it looks like it has been hardcoded in:<br>
><br>
> route[handle_pings]<br>
> {<br>
> # keepalive notifies replied ok<br>
> if ( is_method("NOTIFY|OPTIONS") && !has_totag() && $rU==NULL) {<br>
> send_reply("200", "OK");<br>
> exit;<br>
> }<br>
> }<br>
><br>
Exactly! That's where the ping responses are generated. You should <br>
hook the "drain mode"<br>
login somewhere before that block.<br>
<br>
Best regards,<br>
<br>
-- <br>
Liviu Chircu<br>
<a href="http://www.twitter.com/liviuchircu" rel="noreferrer" target="_blank">www.twitter.com/liviuchircu</a> | <a href="http://www.opensips-solutions.com" rel="noreferrer" target="_blank">www.opensips-solutions.com</a><br>
<br>
OpenSIPS Summit, Amsterdam, May 2020<br>
<a href="http://www.opensips.org/events" rel="noreferrer" target="_blank">www.opensips.org/events</a><br>
OpenSIPS Bootcamp, Miami, March 2020<br>
<a href="http://www.opensips.org/training" rel="noreferrer" target="_blank">www.opensips.org/training</a><br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Tue, 21 Jan 2020 13:01:18 +0000<br>
From: solarmon <<a href="mailto:solarmon@one-n.co.uk" target="_blank">solarmon@one-n.co.uk</a>><br>
To: OpenSIPS users mailling list <<a href="mailto:users@lists.opensips.org" target="_blank">users@lists.opensips.org</a>><br>
Subject: Re: [OpenSIPS-Users] opensips - graceful maintenance mode?<br>
Message-ID:<br>
<<a href="mailto:CAOXfywPCHgKmGaox-m8HuzzMz_mNrv1E5MwYyuV8ojVFoyBrxw@mail.gmail.com" target="_blank">CAOXfywPCHgKmGaox-m8HuzzMz_mNrv1E5MwYyuV8ojVFoyBrxw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi Liviu,<br>
<br>
Can the drain_mode code just be put at the very start of the route {} block?<br>
<br>
Thank you<br>
<br>
On Tue, 21 Jan 2020 at 12:29, Liviu Chircu <<a href="mailto:liviu@opensips.org" target="_blank">liviu@opensips.org</a>> wrote:<br>
<br>
> On 21.01.2020 14:21, solarmon wrote:<br>
> > However, now I have checked our opensips.cfg script (that was created<br>
> > for us) it looks like it has been hardcoded in:<br>
> ><br>
> > route[handle_pings]<br>
> > {<br>
> > # keepalive notifies replied ok<br>
> > if ( is_method("NOTIFY|OPTIONS") && !has_totag() && $rU==NULL) {<br>
> > send_reply("200", "OK");<br>
> > exit;<br>
> > }<br>
> > }<br>
> ><br>
> Exactly! That's where the ping responses are generated. You should<br>
> hook the "drain mode"<br>
> login somewhere before that block.<br>
><br>
> Best regards,<br>
><br>
> --<br>
> Liviu Chircu<br>
> <a href="http://www.twitter.com/liviuchircu" rel="noreferrer" target="_blank">www.twitter.com/liviuchircu</a> | <a href="http://www.opensips-solutions.com" rel="noreferrer" target="_blank">www.opensips-solutions.com</a><br>
><br>
> OpenSIPS Summit, Amsterdam, May 2020<br>
> <a href="http://www.opensips.org/events" rel="noreferrer" target="_blank">www.opensips.org/events</a><br>
> OpenSIPS Bootcamp, Miami, March 2020<br>
> <a href="http://www.opensips.org/training" rel="noreferrer" target="_blank">www.opensips.org/training</a><br>
><br>
><br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
> <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.opensips.org/pipermail/users/attachments/20200121/399b96f6/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.opensips.org/pipermail/users/attachments/20200121/399b96f6/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Tue, 21 Jan 2020 15:04:23 +0200<br>
From: Liviu Chircu <<a href="mailto:liviu@opensips.org" target="_blank">liviu@opensips.org</a>><br>
To: OpenSIPS users mailling list <<a href="mailto:users@lists.opensips.org" target="_blank">users@lists.opensips.org</a>><br>
Subject: Re: [OpenSIPS-Users] opensips - graceful maintenance mode?<br>
Message-ID: <<a href="mailto:930a8df3-25d6-0c2b-f817-ec8dc37bb7a3@opensips.org" target="_blank">930a8df3-25d6-0c2b-f817-ec8dc37bb7a3@opensips.org</a>><br>
Content-Type: text/plain; charset=utf-8; format=flowed<br>
<br>
On 21.01.2020 15:01, solarmon wrote:<br>
> Can the drain_mode code just be put at the very start of the route {} <br>
> block?<br>
<br>
If you don't mind letting SIP scanners know when you're doing <br>
maintenance, sure.<br>
<br>
-- <br>
Liviu Chircu<br>
<a href="http://www.twitter.com/liviuchircu" rel="noreferrer" target="_blank">www.twitter.com/liviuchircu</a> | <a href="http://www.opensips-solutions.com" rel="noreferrer" target="_blank">www.opensips-solutions.com</a><br>
<br>
OpenSIPS Summit, Amsterdam, May 2020<br>
<a href="http://www.opensips.org/events" rel="noreferrer" target="_blank">www.opensips.org/events</a><br>
OpenSIPS Bootcamp, Miami, March 2020<br>
<a href="http://www.opensips.org/training" rel="noreferrer" target="_blank">www.opensips.org/training</a><br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Tue, 21 Jan 2020 13:08:19 +0000<br>
From: solarmon <<a href="mailto:solarmon@one-n.co.uk" target="_blank">solarmon@one-n.co.uk</a>><br>
To: OpenSIPS users mailling list <<a href="mailto:users@lists.opensips.org" target="_blank">users@lists.opensips.org</a>><br>
Subject: Re: [OpenSIPS-Users] opensips - graceful maintenance mode?<br>
Message-ID:<br>
<CAOXfywM6bmVt4u+s1=<a href="mailto:TA-3_o9VmTiLRHWh7_oMbYN8uW%2Bp7%2B0A@mail.gmail.com" target="_blank">TA-3_o9VmTiLRHWh7_oMbYN8uW+p7+0A@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Very good point! I'll try to figure out a more suitable place for it.<br>
<br>
Thanks so much for your help!<br>
<br>
On Tue, 21 Jan 2020 at 13:06, Liviu Chircu <<a href="mailto:liviu@opensips.org" target="_blank">liviu@opensips.org</a>> wrote:<br>
<br>
> On 21.01.2020 15:01, solarmon wrote:<br>
> > Can the drain_mode code just be put at the very start of the route {}<br>
> > block?<br>
><br>
> If you don't mind letting SIP scanners know when you're doing<br>
> maintenance, sure.<br>
><br>
> --<br>
> Liviu Chircu<br>
> <a href="http://www.twitter.com/liviuchircu" rel="noreferrer" target="_blank">www.twitter.com/liviuchircu</a> | <a href="http://www.opensips-solutions.com" rel="noreferrer" target="_blank">www.opensips-solutions.com</a><br>
><br>
> OpenSIPS Summit, Amsterdam, May 2020<br>
> <a href="http://www.opensips.org/events" rel="noreferrer" target="_blank">www.opensips.org/events</a><br>
> OpenSIPS Bootcamp, Miami, March 2020<br>
> <a href="http://www.opensips.org/training" rel="noreferrer" target="_blank">www.opensips.org/training</a><br>
><br>
><br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
> <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.opensips.org/pipermail/users/attachments/20200121/b2919641/attachment.html" rel="noreferrer" target="_blank">http://lists.opensips.org/pipermail/users/attachments/20200121/b2919641/attachment.html</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br>
<br>
------------------------------<br>
<br>
End of Users Digest, Vol 138, Issue 48<br>
**************************************<br>
</blockquote></div>