Hi Sammy,
The Event Interface philosophy is to allow external apps to get access
to the events generated by OpenSIPS; basically a data flow from OpenSIPS
to outside world. So, there is no way to trigger an event from outside
(via MI).
Still, your example is valid, so please open a feature request on github
and we could add a "raise_event" MI function.
As really (really) dirty hack, you can use (if possible) some SIP
OPTIONS to trigger the event. From the web send an OPTIONS via UDP, with
a special RURI -> you identify the RURI in script and do a raise_event()
in script.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
OpenSIPS Bootcamp 2018
http://opensips.org/training/OpenSIPS_Bootcamp_2018/
On 10/11/2018 07:35 PM, SamyGo wrote:
Hi,
I'm trying to find out document pages regarding raising events from
outside the OpenSIPS via fifo/mi_* modules. All I have read so far is
opensips can send events and their data OUT to external "subscribing"
applications. There is even a fifo command to subscribe for an event
from FIFO layer.
Kindly guide me as how do I tell OpenSIPS that a particular Event has
triggered.
My usage scenario is (OpenSIPS 2.2.7) a caller is
waiting_on_event("OPENSIPS_BOOTCAMP");
Now some external web monitoring bot just realized Bootcamp has
started and it wants to raise this event to the waiting caller !
opensipsctl fifo raise_event OPENSIPS_BOOTCAMP 22Oct18 Romania
Best Regards,
Sammy
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
