<div>Hi </div><div><br></div><div>You can use failure_route to generate events for gateway timeouts (Internal 408), save in cache the number of timeouts and after a certain thershold raise an event. Seems simpler and more effective than checking all the time using fifo. </div>
<div><br></div><div>Flavio E. Goncalves</div><div>CEO - SipPulse, <a href="http://www.sippulse.com">www.sippulse.com</a></div><div> </div><br>
<br><br><div class="gmail_quote">2012/9/15 Engineer voip <span dir="ltr"><<a href="mailto:forvoip4@gmail.com" target="_blank">forvoip4@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi, <br><span lang="en"><span>I think</span> <span>the</span> <span>easiest way</span> <span>is to use a</span> <span>script</span> <span>with</span> <span>cron</span> <span>and</span> <span>send an email</span> <span>following the</span> <span>result of the command</span> <span>fifo</span> <span>opensipsctl</span> <span>dr_status</span> <span>GatewayID</span></span> without using the databases.<div class="HOEnZb">
<div class="h5"><br>
<br><div class="gmail_quote">2012/9/14 alexandre Moutot <span dir="ltr"><<a href="mailto:a.moutot@alphalink.fr" target="_blank">a.moutot@alphalink.fr</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
Thank you for your answer. Yes i can actively check via fifo interface. To have some alert, i need to keep all gateways status in a cache and check all the time through the fifo. I can do that with a simple script, a little database and cron. I'm looking for the other way to do that.<br>
<div><br>
Regards,<br>
<br>
MOUTOT Alexandre<br>
<a href="mailto:a.moutot@alphalink.fr" target="_blank">a.moutot@alphalink.fr</a><br>
<a href="tel:%2B33%20%280%296%2062%2091%2095%2014" value="+33662919514" target="_blank">+33 (0)6 62 91 95 14</a><br>
<br>
</div><div><div>----- Original Message -----<br>
> From: "Max Mühlbronner" <<a href="mailto:mm@42com.com" target="_blank">mm@42com.com</a>><br>
> To: "OpenSIPS users mailling list" <<a href="mailto:users@lists.opensips.org" target="_blank">users@lists.opensips.org</a>><br>
> Sent: Friday, September 14, 2012 3:39:13 PM<br>
> Subject: Re: [OpenSIPS-Users] Drouting and gateway monitoring<br>
> Hello,<br>
><br>
> Afaik there is no option for logging the disabled gateways (except at<br>
> higher debug levels?).<br>
><br>
> But you can actively check via fifo interface: "opensipsctl fifo<br>
> dr_status GatewayID" which shows current status of the queried<br>
> gateway.<br>
><br>
><br>
> Best Regards<br>
><br>
> Max M.<br>
><br>
> On 09/14/2012 02:14 PM, alexandre Moutot wrote:<br>
> > Hello,<br>
> ><br>
> > I'm using Opensips with the drouting module. All is ok and works<br>
> > good. I'm using the probe_mode for several gateways : it works good<br>
> > but i don't have any feedback about gateways status. Is there a<br>
> > capability to have a log or to execute an action when a gateway<br>
> > status is modified or otherwise when a gateway goes down.<br>
> ><br>
> > Regards,<br>
> ><br>
> > MOUTOT Alexandre<br>
> > <a href="mailto:a.moutot@alphalink.fr" target="_blank">a.moutot@alphalink.fr</a><br>
> > <a href="tel:%2B33%20%280%296%2062%2091%2095%2014" value="+33662919514" target="_blank">+33 (0)6 62 91 95 14</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" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><span style="padding-right:16px;width:16px;min-height:16px"></span><br>
><br>
><br>
> --<br>
> Max Mühlbronner<br>
><br>
> 42com Telecommunication GmbH<br>
> Straße der Pariser Kommune 12-16<br>
> 10243 Berlin<br>
><br>
> E-Mail: <a href="mailto:mm@42com.com" target="_blank">mm@42com.com</a><br>
> Web: <a href="http://www.42com.com" target="_blank">www.42com.com</a><span style="padding-right:16px;width:16px;min-height:16px"></span><br>
><br>
> Firmenangaben/Company information:<br>
> Handelsregister/Commercial register: Amtsgericht Berlin HRB 99071 B<br>
> Umsatzsteuer-ID/VAT-ID: DE223812306<br>
> Geschäftsführer/CEO: Thomas Reinig, Alexander Reinig<br>
><br>
> Diese E-Mail enthält Informationen von 42com Telecommunication GmbH.<br>
> Diese sind möglicherweise vertraulich und ausschließlich für den<br>
> Adressaten bestimmt. Sollten Sie diese elektronische Nachricht<br>
> irrtümlicherweise erhalten haben, so informieren Sie uns bitte<br>
> unverzüglich telefonisch oder per E-Mail.<br>
><br>
> This message is intended only for the use of the individual or entity<br>
> to which it is addressed. If you have received this message by<br>
> mistake, please notify us immediately.<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" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><span style="padding-right:16px;width:16px;min-height:16px"></span><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" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><span style="padding-right:16px;width:16px;min-height:16px"></span><br>
</div></div></blockquote></div><br><br clear="all"><br></div></div><span class="HOEnZb"><font color="#888888">-- <br><br>Best Regards<br><br>
</font></span><br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div><br>