Co-authored-by: Suguru Hirahara <luixxiul@users.noreply.github.com>element-call-integration
| @@ -25,7 +25,7 @@ See the project's [documentation](https://github.com/element-hq/element-call) to | |||||
| ## Decide on a domain and path | ## Decide on a domain and path | ||||
| By default, Element Call is configured to be served on the `call.element.DOMAIN` domain. | |||||
| By default, Element Call is configured to be served on the `call.element.example.com` domain. | |||||
| If you'd like to run Element Call on another hostname, see the [Adjusting the Element Call URL](#adjusting-the-element-call-url-optional) section below. | If you'd like to run Element Call on another hostname, see the [Adjusting the Element Call URL](#adjusting-the-element-call-url-optional) section below. | ||||
| @@ -43,7 +43,7 @@ In addition to the HTTP/HTTPS ports (which you've already exposed as per the [pr | |||||
| ## Adjusting the playbook configuration | ## Adjusting the playbook configuration | ||||
| Add the following configuration to your `inventory/host_vars/matrix.DOMAIN/vars.yml` file: | |||||
| Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: | |||||
| ```yaml | ```yaml | ||||
| matrix_element_call_enabled: true | matrix_element_call_enabled: true | ||||
| @@ -237,7 +237,7 @@ Services that help you in administrating and monitoring your Matrix installation | |||||
| Various services that don't fit any other categories. | Various services that don't fit any other categories. | ||||
| - [Setting up Element Call](configuring-playbook-element-call.md) - a native Matrix video conferencing application (optional) | |||||
| - [Setting up Element Call](configuring-playbook-element-call.md) — a native Matrix video conferencing application (optional) | |||||
| - [Setting up LiveKit JWT Service](configuring-playbook-livekit-jwt-service.md) (optional) | - [Setting up LiveKit JWT Service](configuring-playbook-livekit-jwt-service.md) (optional) | ||||
| @@ -6329,12 +6329,12 @@ livekit_server_config_keys_auto: |- | |||||
| # The playbook intentionally uses a non-standard port than the default used by the role (5349), | # The playbook intentionally uses a non-standard port than the default used by the role (5349), | ||||
| # because Coturn is already using that port. | # because Coturn is already using that port. | ||||
| # Note that TURN is not enabled by default, see `livekit_server_config_turn_enabled`. | |||||
| # Note that TURN is not enabled by default. See `livekit_server_config_turn_enabled`. | |||||
| livekit_server_config_turn_tls_port: 5350 | livekit_server_config_turn_tls_port: 5350 | ||||
| # The playbook intentionally uses a non-standard port than the default used by the role (3478), | # The playbook intentionally uses a non-standard port than the default used by the role (3478), | ||||
| # because Coturn is already using that port. | # because Coturn is already using that port. | ||||
| # Note that TURN is not enabled by default, see `livekit_server_config_turn_enabled`. | |||||
| # Note that TURN is not enabled by default. See `livekit_server_config_turn_enabled`. | |||||
| livekit_server_config_turn_udp_port: 3479 | livekit_server_config_turn_udp_port: 3479 | ||||
| ######################################################################## | ######################################################################## | ||||