<div dir="ltr"><div dir="ltr">Hi,<div><br></div><div>Just an update/correction. I notice that when I make a call through opensips, the recheck_ticks value does reduce slightly to 928855, but it seems to stay at that for subsequent calls. In Control Panel. The memory state does turn to Green.</div><div><br></div><div># opensipsctl fifo rtpproxy_show<br>Set:: 0<br> node:: udp:<IP:port> index=0 disabled=0 weight=1 recheck_ticks=928855<br> node:: udp:<IP:port> index=1 disabled=0 weight=1 recheck_ticks=0<br> node:: udp:<IP:port> index=2 disabled=0 weight=1 recheck_ticks=0<br></div><div><br></div><div>Please can you explain what recheck_ticks is and does and how it relates to any timeouts and health checks.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 20 Aug 2019 at 09:16, solarmon <<a href="mailto:solarmon@one-n.co.uk">solarmon@one-n.co.uk</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"><div dir="ltr">Hi Razvan,<div><br></div><div>I'm using opensips 2.4.6 (x86_64/linux) so I don't think opensips-cli is available?</div><div><br></div><div>I'm using opensipsctl to show the rtpproxy status.</div><div><br></div><div>This is the output of the command after I have turned off rtpproxy with index 0:</div><div><br></div><div><font face="monospace"># opensipsctl fifo rtpproxy_show<br>Set:: 0<br> node:: udp:<IP:port> index=0 disabled=0 weight=1 recheck_ticks=0<br> node:: udp:
<IP:port> index=1 disabled=0 weight=1 recheck_ticks=0<br> node:: udp:
<IP:port> index=2 disabled=0 weight=1 recheck_ticks=0</font><br></div><div><br></div><div>OpenSIPS Control Panel shows the same - the status does not change.</div><div><br></div><div>When it does change, based on my quick testing, is:</div><div><br></div><div>1. On Reload</div><div>2. When the is a call setup goes through it.</div><div><br></div><div>I'm expecting the health/status to be checked on a regular basis, so as to provide for early detection of failure.</div><div><br></div><div>After I perform a reload (of rtpproxy config):</div><div><br></div><div><font face="monospace"># opensipsctl fifo rtpproxy_show<br>Set:: 0<br> node:: udp:
<IP:port> index=0 disabled=1 weight=1 recheck_ticks=926858<br> node:: udp:
<IP:port> index=1 disabled=0 weight=1 recheck_ticks=0<br> node:: udp:1
<IP:port> index=2 disabled=0 weight=1 recheck_ticks=0</font><br></div><div><br></div><div>The status of rtpproxy node with index 0 shows a value (926858) for recheck_ticks. However this value never changes - it always shows 926858.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 19 Aug 2019 at 15:25, Răzvan Crainea <<a href="mailto:razvan@opensips.org" target="_blank">razvan@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">Hi, Solarmon!<br>
<br>
The parameter you should use is exactly the one you are using, <br>
rtpproxy_disable_tout[1]. That parameter says that after OpenSIPS <br>
detects the node as being down, it re-tries to send them requests after <br>
20 seconds (according to your configuration).<br>
Are you checking the rtpproxy status using the `opensips-cli mi`? Does <br>
the disable timeout change? If not, what's the output of the status command?<br>
<br>
[1] <br>
<a href="https://opensips.org/html/docs/modules/3.0.x/rtpproxy.html#param_rtpproxy_disable_tout" rel="noreferrer" target="_blank">https://opensips.org/html/docs/modules/3.0.x/rtpproxy.html#param_rtpproxy_disable_tout</a><br>
<br>
Best regards,<br>
Răzvan<br>
<br>
On 8/13/19 4:14 PM, solarmon wrote:<br>
> Hi,<br>
> <br>
> Can somebody clarify when the rtpproxy status and health checks are done <br>
> and what configuration is required.<br>
> <br>
> I am finding that the status/health of an rtprpoxy node is only <br>
> done/checked during opensips startup or rtpproxy module config reload. <br>
> If the rtprpoxy node goes down or comes back up, the status indicated by <br>
> opensips for that rtpproxy does not change until another restart or <br>
> reload is done.<br>
> <br>
> My rtpproxy module config is as below:<br>
> <br>
> loadmodule "rtpproxy.so"<br>
> modparam("rtpproxy", "db_url", <br>
> "mysql://<username:password>@<a href="http://127.0.0.1:3306/opensips" rel="noreferrer" target="_blank">127.0.0.1:3306/opensips</a> <br>
> <<a href="http://127.0.0.1:3306/opensips" rel="noreferrer" target="_blank">http://127.0.0.1:3306/opensips</a>>")<br>
> modparam("rtpproxy", "rtpproxy_disable_tout", 20)<br>
> <br>
> Thank you in advance for any help provided.<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>
Răzvan Crainea<br>
OpenSIPS Core Developer<br>
<a href="http://www.opensips-solutions.com" rel="noreferrer" target="_blank">http://www.opensips-solutions.com</a><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>
</blockquote></div>
</blockquote></div></div>