[OpenSIPS-Users] Drouting and gateway monitoring

[alexandre Moutot]

Hi,

I was speaking about failure from drouting probing. Do you think that failure_block is reached when drouting probing failed ?

Regards,


MOUTOT Alexandre
a.moutot at alphalink.fr
+33 (0)6 62 91 95 14

----- Original Message -----
> From: "Binan AL Halabi" <binanalhalabi at yahoo.com>
> To: "OpenSIPS users mailling list" <users at lists.opensips.org>
> Cc: "a moutot" <a.moutot at alphalink.fr>
> Sent: Friday, September 21, 2012 11:32:51 AM
> Subject: Re: [OpenSIPS-Users] Drouting and gateway monitoring
> hej Alexandre,
> 
> 
> somthing like:
> 
> 
> 1- Add this to failure_route (this for 408 locally generated)
> 
> if(t_check_status("408") && (t_local_replied("all"))
> //cache here
> 
> 
> 2- To get something like global variable , use cache_store from
> localcache module
> //Binan
> 
> 
> 
> 
> From: alexandre Moutot <a.moutot at alphalink.fr>
> To: OpenSIPS users mailling list <users at lists.opensips.org>
> Sent: Thursday, September 20, 2012 2:20 PM
> Subject: Re: [OpenSIPS-Users] Drouting and gateway monitoring
> 
> Hi
> 
> With probing mode a gateway could go down without failure_route
> processing.
> When you write "save in cache then number of timeouts", do you mean to
> save it into an AVP var ? AVP var aren't shared with different
> opensips process, isn'it ?
> 
> Regards,
> 
> MOUTOT Alexandre
> 
> ----- Original Message -----
> > From: "Flavio Goncalves" < flavio at asteriskguide.com >
> > To: "OpenSIPS users mailling list" < users at lists.opensips.org >
> > Sent: Thursday, September 20, 2012 1:33:08 AM
> > Subject: Re: [OpenSIPS-Users] Drouting and gateway monitoring
> > Hi
> >
> >
> > 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.
> >
> >
> > Flavio E. Goncalves
> > CEO - SipPulse, www.sippulse.com
> >
> >
> >
> >
> > 2012/9/15 Engineer voip < forvoip4 at gmail.com >
> >
> >
> > Hi,
> > I think the easiest way is to use a script with cron and send an
> > email
> > following the result of the command fifo opensipsctl dr_status
> > GatewayID without using the databases.
> >
> >
> >
> >
> > 2012/9/14 alexandre Moutot < a.moutot at alphalink.fr >
> >
> >
> > Hi,
> >
> > 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.
> >
> >
> > Regards,
> >
> > MOUTOT Alexandre
> > a.moutot at alphalink.fr
> > +33 (0)6 62 91 95 14
> >
> >
> >
> > ----- Original Message -----
> > > From: "Max Mühlbronner" < mm at 42com.com >
> > > To: "OpenSIPS users mailling list" < users at lists.opensips.org >
> > > Sent: Friday, September 14, 2012 3:39:13 PM
> > > Subject: Re: [OpenSIPS-Users] Drouting and gateway monitoring
> > > Hello,
> > >
> > > Afaik there is no option for logging the disabled gateways (except
> > > at
> > > higher debug levels?).
> > >
> > > But you can actively check via fifo interface: "opensipsctl fifo
> > > dr_status GatewayID" which shows current status of the queried
> > > gateway.
> > >
> > >
> > > Best Regards
> > >
> > > Max M.
> > >
> > > On 09/14/2012 02:14 PM, alexandre Moutot wrote:
> > > > Hello,
> > > >
> > > > I'm using Opensips with the drouting module. All is ok and works
> > > > good. I'm using the probe_mode for several gateways : it works
> > > > good
> > > > but i don't have any feedback about gateways status. Is there a
> > > > capability to have a log or to execute an action when a gateway
> > > > status is modified or otherwise when a gateway goes down.
> > > >
> > > > Regards,
> > > >
> > > > MOUTOT Alexandre
> > > > a.moutot at alphalink.fr
> > > > +33 (0)6 62 91 95 14
> > > >
> > > > _______________________________________________
> > > > Users mailing list
> > > > Users at lists.opensips.org
> > > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> > >
> > >
> > > --
> > > Max Mühlbronner
> > >
> > > 42com Telecommunication GmbH
> > > Straße der Pariser Kommune 12-16
> > > 10243 Berlin
> > >
> > > E-Mail: mm at 42com.com
> > > Web: www.42com.com
> > >
> > > Firmenangaben/Company information:
> > > Handelsregister/Commercial register: Amtsgericht Berlin HRB 99071
> > > B
> > > Umsatzsteuer-ID/VAT-ID: DE223812306
> > > Geschäftsführer/CEO: Thomas Reinig, Alexander Reinig
> > >
> > > Diese E-Mail enthält Informationen von 42com Telecommunication
> > > GmbH.
> > > Diese sind möglicherweise vertraulich und ausschließlich für den
> > > Adressaten bestimmt. Sollten Sie diese elektronische Nachricht
> > > irrtümlicherweise erhalten haben, so informieren Sie uns bitte
> > > unverzüglich telefonisch oder per E-Mail.
> > >
> > > This message is intended only for the use of the individual or
> > > entity
> > > to which it is addressed. If you have received this message by
> > > mistake, please notify us immediately.
> > >
> > >
> > > _______________________________________________
> > > Users mailing list
> > > Users at lists.opensips.org
> > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >
> > _______________________________________________
> > Users mailing list
> > Users at lists.opensips.org
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >
> >
> >
> > --
> >
> > Best Regards
> >
> >
> > _______________________________________________
> > Users mailing list
> > Users at lists.opensips.org
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >
> >
> >
> > _______________________________________________
> > Users mailing list
> > Users at lists.opensips.org
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> 
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users