Ids for channels subscribed to.
Names of the devices subscribed to.
{tech}/{resource} for endpoints subscribed to.
Event types sent to the application.
Event types not sent to the application.
Name of this application.
Base type for errors and events.
Error event sent when required params are missing.
Base type for asynchronous events from Asterisk.
Detailed information about a contact on an endpoint.
Detailed information about a remote peer that communicates with Asterisk.
Notification that a device state has changed.
Event showing the start of a media playback operation.
Event showing the continuation of a media playback operation from one media URI to the next in the list.
Event showing the completion of a media playback operation.
Event showing the start of a recording operation.
Event showing the completion of a recording operation.
Event showing failure of a recording operation.
Notification that trying to move a channel to another Stasis application failed.
Notification that another WebSocket has taken over for an application. An application may only be subscribed to by a single WebSocket at a time. If multiple WebSockets attempt to subscribe to the same application, the newer WebSocket wins, and the older one receives this event.
Notification that a bridge has been created.
Notification that a bridge has been destroyed.
Notification that one bridge has merged into another.
Notification that the source of video in a bridge has changed.
Notification that a blind transfer has occurred.
Notification that an attended transfer has occurred.
Notification that a channel has been created.
Notification that a channel has been destroyed.
Notification that a channel has entered a bridge.
Notification that a channel has left a bridge.
Notification of a channels state change.
DTMF received on a channel. This event is sent when the DTMF ends. There is no notification about the start of DTMF.
Channel changed location in the dialplan.
Channel changed Caller ID.
User-generated event with additional user-defined fields in the object.
A hangup was requested on the channel.
Channel variable changed.
A channel initiated a media hold.
A channel initiated a media unhold.
Talking was detected on the channel.
Talking is no longer detected on the channel.
The state of a contact on an endpoint has changed.
The state of a peer associated with an endpoint has changed.
Endpoint state changed.
Dialing state has changed.
Notification that a channel has left a Stasis application.
Notification that a channel has entered a Stasis application.
A text message was received from an endpoint.
Channel changed Connected Line.
Filter application events types. Allowed and/or disallowed event type filtering can be done. The body (parameter) should specify a JSON key/value object that describes the type of event filtering needed. One, or both of the following keys can be designated: "allowed" - Specifies an allowed list of event types "disallowed" - Specifies a disallowed list of event types Further, each of those keys value should be a JSON array that holds zero, or more JSON key/value objects. Each of these objects must contain the following key with an associated value: "type" - The type name of the event to filter The value must be the string name (case sensitive) of the event type that needs filtering. For example: { "allowed": [ { "type": "StasisStart" }, { "type": "StasisEnd" } ] } As this specifies only an allowed list, then only those two event type messages are sent to the application. No other event messages are sent. The following rules apply: * If the body is empty, both the allowed and disallowed filters are set empty. * If both list types are given then both are set to their respective values (note, specifying an empty array for a given type sets that type to empty). * If only one list type is given then only that type is set. The other type is not updated. * An empty "allowed" list means all events are allowed. * An empty "disallowed" list means no events are disallowed. * Disallowed events take precedence over allowed events if the event type is specified in both lists.
Filter application events types. Allowed and/or disallowed event type filtering can be done. The body (parameter) should specify a JSON key/value object that describes the type of event filtering needed. One, or both of the following keys can be designated: "allowed" - Specifies an allowed list of event types "disallowed" - Specifies a disallowed list of event types Further, each of those keys value should be a JSON array that holds zero, or more JSON key/value objects. Each of these objects must contain the following key with an associated value: "type" - The type name of the event to filter The value must be the string name (case sensitive) of the event type that needs filtering. For example: { "allowed": [ { "type": "StasisStart" }, { "type": "StasisEnd" } ] } As this specifies only an allowed list, then only those two event type messages are sent to the application. No other event messages are sent. The following rules apply: * If the body is empty, both the allowed and disallowed filters are set empty. * If both list types are given then both are set to their respective values (note, specifying an empty array for a given type sets that type to empty). * If only one list type is given then only that type is set. The other type is not updated. * An empty "allowed" list means all events are allowed. * An empty "disallowed" list means no events are disallowed. * Disallowed events take precedence over allowed events if the event type is specified in both lists.
Filter application events types. Allowed and/or disallowed event type filtering can be done. The body (parameter) should specify a JSON key/value object that describes the type of event filtering needed. One, or both of the following keys can be designated: "allowed" - Specifies an allowed list of event types "disallowed" - Specifies a disallowed list of event types Further, each of those keys value should be a JSON array that holds zero, or more JSON key/value objects. Each of these objects must contain the following key with an associated value: "type" - The type name of the event to filter The value must be the string name (case sensitive) of the event type that needs filtering. For example: { "allowed": [ { "type": "StasisStart" }, { "type": "StasisEnd" } ] } As this specifies only an allowed list, then only those two event type messages are sent to the application. No other event messages are sent. The following rules apply: * If the body is empty, both the allowed and disallowed filters are set empty. * If both list types are given then both are set to their respective values (note, specifying an empty array for a given type sets that type to empty). * If only one list type is given then only that type is set. The other type is not updated. * An empty "allowed" list means all events are allowed. * An empty "disallowed" list means no events are disallowed. * Disallowed events take precedence over allowed events if the event type is specified in both lists.
Get details of an application.
Get details of an application.
List all applications.
List all applications.
Base type for errors and events.
Error event sent when required params are missing.
Base type for asynchronous events from Asterisk.
Detailed information about a contact on an endpoint.
Detailed information about a remote peer that communicates with Asterisk.
Notification that a device state has changed.
Event showing the start of a media playback operation.
Event showing the continuation of a media playback operation from one media URI to the next in the list.
Event showing the completion of a media playback operation.
Event showing the start of a recording operation.
Event showing the completion of a recording operation.
Event showing failure of a recording operation.
Notification that trying to move a channel to another Stasis application failed.
Notification that another WebSocket has taken over for an application. An application may only be subscribed to by a single WebSocket at a time. If multiple WebSockets attempt to subscribe to the same application, the newer WebSocket wins, and the older one receives this event.
Notification that a bridge has been created.
Notification that a bridge has been destroyed.
Notification that one bridge has merged into another.
Notification that the source of video in a bridge has changed.
Notification that a blind transfer has occurred.
Notification that an attended transfer has occurred.
Notification that a channel has been created.
Notification that a channel has been destroyed.
Notification that a channel has entered a bridge.
Notification that a channel has left a bridge.
Notification of a channels state change.
DTMF received on a channel. This event is sent when the DTMF ends. There is no notification about the start of DTMF.
Channel changed location in the dialplan.
Channel changed Caller ID.
User-generated event with additional user-defined fields in the object.
A hangup was requested on the channel.
Channel variable changed.
A channel initiated a media hold.
A channel initiated a media unhold.
Talking was detected on the channel.
Talking is no longer detected on the channel.
The state of a contact on an endpoint has changed.
The state of a peer associated with an endpoint has changed.
Endpoint state changed.
Dialing state has changed.
Notification that a channel has left a Stasis application.
Notification that a channel has entered a Stasis application.
A text message was received from an endpoint.
Channel changed Connected Line.
Base type for errors and events.
Error event sent when required params are missing.
Base type for asynchronous events from Asterisk.
Detailed information about a contact on an endpoint.
Detailed information about a remote peer that communicates with Asterisk.
Notification that a device state has changed.
Event showing the start of a media playback operation.
Event showing the continuation of a media playback operation from one media URI to the next in the list.
Event showing the completion of a media playback operation.
Event showing the start of a recording operation.
Event showing the completion of a recording operation.
Event showing failure of a recording operation.
Notification that trying to move a channel to another Stasis application failed.
Notification that another WebSocket has taken over for an application. An application may only be subscribed to by a single WebSocket at a time. If multiple WebSockets attempt to subscribe to the same application, the newer WebSocket wins, and the older one receives this event.
Notification that a bridge has been created.
Notification that a bridge has been destroyed.
Notification that one bridge has merged into another.
Notification that the source of video in a bridge has changed.
Notification that a blind transfer has occurred.
Notification that an attended transfer has occurred.
Notification that a channel has been created.
Notification that a channel has been destroyed.
Notification that a channel has entered a bridge.
Notification that a channel has left a bridge.
Notification of a channels state change.
DTMF received on a channel. This event is sent when the DTMF ends. There is no notification about the start of DTMF.
Channel changed location in the dialplan.
Channel changed Caller ID.
User-generated event with additional user-defined fields in the object.
A hangup was requested on the channel.
Channel variable changed.
A channel initiated a media hold.
A channel initiated a media unhold.
Talking was detected on the channel.
Talking is no longer detected on the channel.
The state of a contact on an endpoint has changed.
The state of a peer associated with an endpoint has changed.
Endpoint state changed.
Dialing state has changed.
Notification that a channel has left a Stasis application.
Notification that a channel has entered a Stasis application.
A text message was received from an endpoint.
Channel changed Connected Line.
Removes all listeners, or those of the specified event type.
Removes the event listener for the specified event type.
The event type.
The event listener function.
Subscribe an application to a event source. Returns the state of the application after the subscriptions have changed.
URI for event source (channel:{channelId}, bridge:{bridgeId}, endpoint:{tech}[/{resource}], deviceState:{deviceName}.
Subscribe an application to a event source. Returns the state of the application after the subscriptions have changed.
URI for event source (channel:{channelId}, bridge:{bridgeId}, endpoint:{tech}[/{resource}], deviceState:{deviceName}.
Unsubscribe an application from an event source. Returns the state of the application after the subscriptions have changed.
URI for event source (channel:{channelId}, bridge:{bridgeId}, endpoint:{tech}[/{resource}], deviceState:{deviceName}.
Unsubscribe an application from an event source. Returns the state of the application after the subscriptions have changed.
URI for event source (channel:{channelId}, bridge:{bridgeId}, endpoint:{tech}[/{resource}], deviceState:{deviceName}.
Generated using TypeDoc
Ids for bridges subscribed to.