(Application) Meetme

Meetme is Asterisk’s long-standing, now-being-phased-out conferencing subsystem. While technically a part of Asterisk’s core, it’s specialised enough that pystrix treats it as a module.

Members

All of the following objects should be accessed as part of the ami.app_meetme namespace, regardless of the modules in which they are defined.

Actions

class ami.app_meetme.MeetmeList(conference=None)

Bases: _Request

Lists all participants in all (or one) conferences.

A series of ‘MeetmeList’ events follow, with one ‘MeetmeListComplete’ event at the end.

Note that if no conferences are active, the response will indicate that it was not successful, per https://issues.asterisk.org/jira/browse/ASTERISK-16812

__init__(conference=None)

conference is the optional identifier of the bridge.

class ami.app_meetme.MeetmeListRooms

Bases: _Request

Lists all conferences.

A series of ‘MeetmeListRooms’ events follow, with one ‘MeetmeListRoomsComplete’ event at the end.

__init__()

action is the type of action being requested of the Asterisk server.

class ami.app_meetme.MeetmeMute(meetme, usernum)

Bases: _Request

Mutes a participant in a Meetme bridge.

Requires call

__init__(meetme, usernum)

meetme is the identifier of the bridge and usernum is the participant ID of the user to be muted, which is associated with a channel by the ‘MeetmeJoin’ event. If successful, this request will trigger a ‘MeetmeMute’ event.

class ami.app_meetme.MeetmeUnmute(meetme, usernum)

Bases: _Request

Unmutes a participant in a Meetme bridge.

Requires call

__init__(meetme, usernum)

meetme is the identifier of the bridge and usernum is the participant ID of the user to be unmuted, which is associated with a channel by the ‘MeetmeJoin’ event. If successful, this request will trigger a ‘MeetmeMute’ event.