[OpenSIPS-Devel] NEW: Event Notification Interface feature
Hello all, An alpha version of the new OpenSIPS Event Notification Interface was released today. This will allow external application to subscribe to OpenSIPS and receive notifications when some events are internally raised. This version provides end to end communication between OpenSIPS (core, script and modules) and external applications using UDP and UNIX datagrams. It includes two parts: the core of event interface and the 'event_datagram' module used to notify the events. Among the supplied features you can find: - subscribe for events through the MI interface - push different events from script, modules and even core - internal events from core and modules - custom information appended to events (depending on the nature of the event) A few events have already been implemented: - E_CORE_THRESHOLD event will be raised when using debugging bottleneck detection and the limit is exceeded. - an E_PIKE_BLOCKED event will be notified if 'pike' module is used and an IP address should be blocked. - nathelper module raises an E_RTPPROXY_STATUS event every time a RTPProxy connects or disconnects. - an E_DISPATCHER_STATUS event will be raised by the 'dispatcher' module when a destination address becomes active/inactive. You can find more information about implementation and usage at [1]. Regards, -- Razvan Crainea OpenSIPS Developer [1] http://www.opensips.org/Development/EventNotification ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] NEW: Event Notification Interface feature
Hello all, I want to announce you that I am going to develop an Event Notification Interface feature for OpenSIPS. This will allow external applications to be notified by OpenSIPS when different internal events are raised, such as dialog creation, new user registration, address detected by pike, peer detected as failed (dispatcher, drouting, LB) etc. You can find more information here[1]. This topic will be discussed in the next IRC meeting[2], on March 9th, 2011. Regards, Razvan [1] http://www.opensips.org/Development/EventNotification [2] http://www.opensips.org/Resources/IRCmeeting20110309 ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] NEW: Event Notification Interface feature
Il 08/03/11 12.33, Olle E. Johansson ha scritto: 8 mar 2011 kl. 11.28 skrev Razvan Crainea: Hello all, I want to announce you that I am going to develop an Event Notification Interface feature for OpenSIPS. This will allow external applications to be notified by OpenSIPS when different internal events are raised, such as dialog creation, new user registration, address detected by pike, peer detected as failed (dispatcher, drouting, LB) etc. You can find more information here[1]. Sounds great. I hope you will base this on SIP subscribe/notify. I agree. The SIP presence status change events would be the key for the next generation routing logic. Regards, Carlo Dimaggio ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] NEW: Event Notification Interface feature
Hello, Multiple transport protocols will be available, probably including SIP. Each protocol will be implemented in a different module, so it is up to you what kind of transport to use. Presence module will definitely export some events, including status change. Regards, Razvan On 03/08/2011 02:09 PM, Carlo Dimaggio wrote: Il 08/03/11 12.33, Olle E. Johansson ha scritto: 8 mar 2011 kl. 11.28 skrev Razvan Crainea: Hello all, I want to announce you that I am going to develop an Event Notification Interface feature for OpenSIPS. This will allow external applications to be notified by OpenSIPS when different internal events are raised, such as dialog creation, new user registration, address detected by pike, peer detected as failed (dispatcher, drouting, LB) etc. You can find more information here[1]. Sounds great. I hope you will base this on SIP subscribe/notify. I agree. The SIP presence status change events would be the key for the next generation routing logic. Regards, Carlo Dimaggio ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
