|
|
@@ -46,9 +46,10 @@ matrix_livekit_server_dev_key: 'your-secure-livekit-key' |
|
|
After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: `just install-all` or `just setup-all` |
|
|
After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: `just install-all` or `just setup-all` |
|
|
|
|
|
|
|
|
## Usage |
|
|
## Usage |
|
|
Once installed, Element Call integrates seamlessly with Matrix clients like Element Web. When the Element Call service is installed, the `/.well-known/matrix/client` file is also updated. A new `org.matrix.msc4143.rtc_foci` section is added to point to your JWT service URL (e.g., `https://sfu-jwt.DOMAIN`). |
|
|
|
|
|
|
|
|
|
|
|
Additionally, the `/.well-known/element/element.json` file is created to help Element clients discover the Element Call URL (e.g., `https://call.DOMAIN`). |
|
|
|
|
|
|
|
|
Once installed, Element Call integrates seamlessly with Matrix clients like Element Web. When the Element Call service is installed, the `/.well-known/matrix/client` file is also updated. A new `org.matrix.msc4143.rtc_foci` section is added to point to your JWT service URL (e.g., `https://sfu-jwt.example.com`). |
|
|
|
|
|
|
|
|
|
|
|
Additionally, the `/.well-known/element/element.json` file is created to help Element clients discover the Element Call URL (e.g., `https://call.example.com`). |
|
|
|
|
|
|
|
|
## Required Firewall and Port Forwarding Rules |
|
|
## Required Firewall and Port Forwarding Rules |
|
|
|
|
|
|
|
|
|