Skip to content

OpenTalk Administration

OpenTalk consists of several components that provide different services, some mandatory, some optional. Each of these services is documented in a separate section.

Component Required Description
OpenTalk Controller Yes Web API and meeting signaling which is accessed by the frontend
OpenTalk Obelisk No Service for participating in a meeting through call-in services, e.g. through SIP
OpenTalk Recorder No Service for recording and streaming meetings
OpenTalk SMTP Mailer No Service for sending out invitation and other notification mails to participants

Deployment

For a ready-to-use deployment that ties the components above together, see OpenTalk Compose. It provides a Docker Compose setup covering the controller and the optional services.

Community

Feel free to interact with other administrators of OpenTalk instances in one of our community channels:

Please be aware that these channels are purely community-driven, and even though some of the OpenTalk developers are occasionally present on their own initiative, there is no guarantee for timely answers.