Element Call and federated Matrix callers
Last updated: August 2026
When you use Liman with federated Matrix contacts (other homeservers, e.g. with Element Call or Element Server Suite / ESS), they may call you via Element — not via the Liman call button. Liman and Element use different signaling; Liman can optionally answer Element Call rings in the Liman UI (MatrixRTC join) or only decline / notify.
What happens on an Element call?
| Call type | Typical source | Liman behavior |
|---|---|---|
| Liman call | Call button in Liman chat | Normal incoming call with ringtone and Accept/Decline |
| Legacy Matrix VoIP | Older Element clients (m.call.invite) | Depending on settings: auto-decline + chat hint or desktop notification only |
| Element Call (MatrixRTC) | Modern Element clients (m.rtc.notification) | Depending on Element Call (MatrixRTC) setting: ignore, decline, notify only, or ring and answer in Liman |
With “Ring and answer in Liman”, you get the same call dialog as for Liman calls. After accept, you join the caller’s LiveKit (basic audio/video; advanced meeting features such as recording or breakout rooms are not available in this interop mode).
Settings
Path: Settings → Chats and channels (Ctrl+. / Cmd+.)
Element / Matrix native calls (legacy VoIP)
Applies to older Matrix calls via m.call.invite:
| Option | Behavior |
|---|---|
| Automatically reject and suggest Liman | Liman declines and posts a chat message (e.g. “Please use Liman for calls …”) |
| Only notify (accept in Element) | Desktop notification; answer in Element — no automatic decline |
Element Call (MatrixRTC)
| Option | Behavior |
|---|---|
| Ignore | No reaction to MatrixRTC ring events (default / safe rollout) |
| Decline and suggest Liman | Protocol decline to Element + optional chat hint |
| Only notify (accept in Element) | Desktop notification; caller gets no decline |
| Ring and answer in Liman | Call dialog + ringtone; accept opens the Liman meeting UI (foreign LiveKit, interop) |
Details: Settings – Chat
Admin note: For answering federated Element Calls, the caller’s homeserver (ESS) must allow tokens for your Liman homeserver. Without that, join fails — decline and notify still work.
Starting calls inside Liman
For calls between Liman users, use the Call or Video button in the Matrix chat. Everyone uses the same Liman/LiveKit infrastructure (including advanced meeting features).
FAQ
Why doesn’t Liman ring when someone calls me from Element?
Modern Element calls use MatrixRTC. With Ignore, Liman does nothing. Choose Only notify or Ring and answer in Liman.
Does the caller see that I declined?
For legacy VoIP (reject) and MatrixRTC Decline: yes — Liman sends a protocol-level decline. With Only notify, the caller gets no automatic decline.
Can I still answer in Element?
Yes — with Ignore, Decline, or Only notify, open Element (or the caller’s Matrix client). With Ring and answer in Liman, you can join directly in Liman.
What about Microsoft Teams calls?
Teams calls appear in the Teams app, not in Liman. See Parallel meeting apps for using both at once.
Further Matrix / Element interop (chat)
Besides calls, Liman also supports (as of August 2026):
- Blocked contacts ↔ Element ignore list (
m.ignored_user_list) — Privacy - Chat favourites / low priority as Matrix tags — Chat
- Join requests when knocking — Room settings
- Voice messages (MSC3245), stickers (
m.sticker), incoming Element polls (MSC3381) - System lines for transcript and recording in the meeting chat — Call log
Related pages
- Dialog: Incoming call — Liman-native calls (and MatrixRTC when set to answer)
- Area: Calls
- Settings – Chat
- End-to-end encryption