Thank you for the solid explanation. --- Jayesh On Mar 14, 2013 10:37 PM, "Bogdan-Andrei Iancu" <[email protected]> wrote:
> ** > Hi Jayesh, > > Firing an event is not a problem - the problem is in NAT pinging, there is > no state for the tractions. Basically the modules doing NAT do not care of > the replies (as for pining is not relevant), so you do not know which ping > and for what contact it failed, in order to trigger the event. > > Switching to statefull pinging may be expensive from resources point of > view.... > > Best regards, > > Bogdan-Andrei Iancu > OpenSIPS Founder and Developerhttp://www.opensips-solutions.com > > > On 03/13/2013 08:28 AM, Jayesh Nambiar wrote: > > Hi All, > The 1.9 has an awesome event interface and I really appreciate the great > work by the developers. I was looking at an option to raise an event when a > registered user becomes unreachable. > Say, for eg: I use keep-alive method as OPTIONS in the nat_traversal > module and if I do not get a response from any UA, is it possible that > opensips can raise an event for the same. Is it somehow possible from the > script, or additional work on the code will be required. > I think, this feature might be useful in many ways !! > > Thanks for any pointers. > > --- Jayesh > > > _______________________________________________ > Users mailing > [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
