Documentation |
Documentation.Interface-Events-1-9 HistoryShow minor edits - Show changes to markup August 05, 2013, at 04:22 PM
by
- Changed line 4 from:
to:
(:allVersions Interface-Events 1.9 :) May 29, 2013, at 12:54 PM
by
- Added lines 50-55:
Events SubscriptionYou can subscribe for an event either at startup (using the subscribe_event() command in the script) or during runtime, using the event_subscribe MI command. May 29, 2013, at 12:41 PM
by
- Changed lines 34-35 from:
to:
Changed lines 55-56 from:
In order to configure a RabbbitMQ server to be notified when a custom event is triggered, first you have to subscribe it to the event, using the subscribe_event() command: to:
In order to configure a RabbbitMQ server to be notified when a custom event is triggered, first you have to subscribe it to the event, using the subscribe_event() command: Changed line 63 from:
Then, in order to trigger the event from the script, call the raise_event() command when needed: to:
Then, in order to trigger the event from the script, call the raise_event() command when needed: May 29, 2013, at 11:28 AM
by
- Changed line 4 from:
to:
May 29, 2013, at 11:26 AM
by
- Changed line 32 from:
to:
Changed lines 34-35 from:
to:
Changed lines 55-56 from:
In order to configure a RabbbitMQ server to be notified when a custom event is triggered, first you have to subscribe it to the event, using the subscribe_event() command: to:
In order to configure a RabbbitMQ server to be notified when a custom event is triggered, first you have to subscribe it to the event, using the subscribe_event() command: Changed line 63 from:
Then, in order to trigger the event from the script, call the raise_event() command when needed: to:
Then, in order to trigger the event from the script, call the raise_event() command when needed: May 29, 2013, at 11:24 AM
by
- Changed lines 1-2 from:
Documentation -> Manuals -> Manual 1.9 -> Interface -> Events Interfaceto:
Documentation -> Manuals -> Manual 1.9 -> Events Interface(:title Events Interface - ver 1.9 :) Added lines 4-12:
May 28, 2013, at 08:28 PM
by
- Changed line 49 from:
subscribe_event("E_PIKE_BLOCKED", "rabbitmq:127.0.0.1/pike"); to:
subscribe_event("E_SCRIPT_CUSTOM_EVENT", "rabbitmq:127.0.0.1/opensips"); Changed line 57 from:
raise_event("E_SCRIPT_EVENT"); # raises an event without any parameters to:
raise_event("E_SCRIPT_CUSTOM_EVENT"); # raises an event without any parameters May 28, 2013, at 08:27 PM
by
- Added lines 39-40:
An external application can subscribe to any of the exported module and can be notified using any of the loaded transport modules/protocols. Added lines 44-59:
In order to configure a RabbbitMQ server to be notified when a custom event is triggered, first you have to subscribe it to the event, using the subscribe_event() command: startup_route { subscribe_event("E_PIKE_BLOCKED", "rabbitmq:127.0.0.1/pike"); } Then, in order to trigger the event from the script, call the raise_event() command when needed: .... raise_event("E_SCRIPT_EVENT"); # raises an event without any parameters ... May 28, 2013, at 06:55 PM
by
- Changed lines 4-5 from:
The Events Interface is an OpenSIPS interface that provides different ways to notify external applications about certain events that occur inside OpenSIPS. to:
The Events Interface is an OpenSIPS interface that provides different ways to notify external applications about certain events triggered inside OpenSIPS. Added lines 7-41:
In order to notify an external application about OpenSIPS internal events, the Event Interface provides the following functions:
More detailed information about OpenSIPS Event Interface can be found in the Event Interface Tutorial. EventsThere are several types of events that can be exported by OpenSIPS:
Transport ProtocolsExternal applications can be notified about the events triggered using various transport protocols. While the interface itself is provided by OpenSIPS core, each transport protocol is implemented by a separate OpenSIPS module. Multiple transport modules can be loaded simultaneously in order to provide different ways of notifications. Available transport protocols are :
ExamplesMay 28, 2013, at 06:12 PM
by
- Changed line 4 from:
The Events Interface (or MI) is an OpenSIPS interface that ......... to:
The Events Interface is an OpenSIPS interface that provides different ways to notify external applications about certain events that occur inside OpenSIPS. May 28, 2013, at 01:22 PM
by
- Added lines 1-6:
Documentation -> Manuals -> Manual 1.9 -> Interface -> Events InterfaceThe Events Interface (or MI) is an OpenSIPS interface that ......... Overview |