<Conference> XML element, and you control participants out-of-band through a REST API (mute, kick, play, record). The XML verb and most attributes line up one-to-one - the main differences are header auth and the SDK resource split (conference, conference_members, conference_recording).
Plivo → Vobiz mapping
XML element & attributes
REST API (room + member operations)
Vobiz base URL:https://api.vobiz.ai/api/v1. Auth via X-Auth-ID + X-Auth-Token request headers (Plivo uses HTTP Basic with the same Auth ID/Token).
Before / after: join a moderated conference (XML)
Plivo -plivoxml builder:
vobizxml builder (bundled in every Vobiz SDK):
Key differences & gotchas
- Auth. Plivo uses HTTP Basic; Vobiz uses
X-Auth-ID/X-Auth-Tokenrequest headers (the SDK sets these, but rawcurl/HTTP clients must switch). - Member ops are split across SDK resources.
client.conference(kick / hangup / play / deaf),client.conference_members(mute / unmute),client.conferences(room list / get / delete),client.conference_recording(start / stop) - but the REST paths stay under one/Conference/...tree. - Rename
maxMembers→maxParticipants, and noteenterSound/exitSoundmap to a singlebeepboolean; recording format moves from XML tostart_conference_recording(file_format=...). - Callback params differ in name. Vobiz posts
ConferenceAction(enter/exit/start/end),ConferenceUUID,ConferenceName,CallUUID,ConferenceCurrentSize, andRecordingUrl. See Conference Callbacks.