فارسی · Components · Home
Calls & extras
Group calls, video meetings, shared documents, push notifications without Google, and a few specialist tools.
How to add any of these: Components.
Element Call
Group voice and video calls built into Matrix, and the calls of Element X on phones. It brings LiveKit, the media server calls go through, with it. Part of the Friends & family preset.
DNS: call.element.example.org.
Ports: besides Coturn's, LiveKit's: 7881/tcp, 7882/udp, 3479/udp,
5350/tcp and 30000-30020/udp. Review's z lists them.
After deploy: in Element Web or Element X, start a call in any room (the
camera or phone button). It also works on its own at
https://call.element.example.org.
Playbook doc
Matrix RTC stack
LiveKit and its login service without the Element Call web app: calls work in
Element Web and Element X (which carry Element Call inside), just not from
the standalone call.element page. Pick this or Element Call.
Ports: LiveKit's, as above. Playbook doc
Jitsi Meet
Video meetings in the browser, also for people without a Matrix account.
DNS: jitsi.example.org. Ports: Review's z lists the ones it needs
(UDP 10000 above all).
After deploy: open https://jitsi.example.org and start a meeting, or
start a call in an Element Web room with more than two members: Element uses
your Jitsi for it. Anyone with the link can start a meeting until you turn on
Jitsi's authentication (see the doc; the lines go under Advanced on
Settings).
Playbook doc
Etherpad
Documents several people write in at once, which you can pin in a room.
DNS: etherpad.example.org.
After deploy: make a pad at https://etherpad.example.org, copy its
address, and in an Element room send /addwidget THE_ADDRESS. It shows in
the room's Widgets on the right.
Playbook doc
Pantalaimon
A go-between that lets bots and programs without encryption support read and write in encrypted rooms. Only reachable from inside the server; only needed when a bot's doc asks for it. Playbook doc
Sygnal push gateway
Push notifications for a phone app you build yourself. Published apps (Element, FluffyChat…) use their makers' gateways; this is only for your own app with your own Firebase and Apple keys.
DNS: sygnal.example.org.
Settings: Apps: one block per app ID, with its type (gcm for
Android, apns for iOS) and keys, as in
Sygnal's notes for app developers.
Playbook doc
ntfy push server
Notifications on Android without Google's services: where Google is blocked, or on phones without it, Matrix apps can't wake you through Google, but they can through your own ntfy (UnifiedPush). Doesn't help on iPhones.
DNS: ntfy.example.org.
After deploy, on each Android phone:
- Install the ntfy app (from F-Droid or Google Play) and, in its settings,
set the default server to
https://ntfy.example.org. - Then in the Matrix app:
- FluffyChat: nothing; it finds ntfy by itself.
- Element (classic Android app): Settings › Notifications › Notification method › ntfy.
- SchildiChat: Settings › Notifications, turn on UnifiedPush: Force custom push gateway, then Re-register push distributor. If it asks FCM Fallback or ntfy, choose ntfy.
interzone's Alerts can send to an ntfy topic too:
https://ntfy.example.org/my-alerts.
Playbook doc
Matrix Corporal
Synapse only, not with MAS, advanced. Runs your users and rooms from one policy file: who exists, which rooms they're in, what they may do. For companies that manage accounts centrally; if you're unsure, you don't need it.
Settings: Shared secret (made up for you) and Policy provider:
where the policy comes from; the default reads /etc/matrix-corporal/policy.json,
which you write as Corporal's docs
describe.
Playbook doc