Additional Platform Information

Oct 13, 2025 by pinkandtrash.com 109 views

Introduction

Are you experiencing issues making calls from Eturnal on your iOS device? You're not alone. Many users have reported similar problems, and it's essential to understand the root cause of the issue to find a solution. In this article, we'll delve into the details of the problem, explore the possible causes, and provide a step-by-step guide to troubleshoot and resolve the issue.

Bug Description

The issue at hand is related to making calls from Eturnal on iOS devices. When a user clicks on the phone icon, it's expected to connect to another user. However, the call fails to connect, and the user is unable to make a call.

Steps to Reproduce

To reproduce the issue, follow these steps:

Go to the chat interface on your iOS device.
Click on the phone icon to initiate a call.

Expected Behavior

When a user clicks on the phone icon, it should connect to another user, allowing for a successful call.

App Version

The app version being used is 1.25.0.

Additional Platform Information

The issue is specific to iOS devices.

Additional Context

To better understand the issue, let's take a closer look at the configuration settings for Matrix, TURN, and NGINX.

Matrix

Matrix Server: Synapse
Matrix Server Version: 1.125.0
Config Matrix:

turn_uris:
  - "turns:turn.domen.net:5349?transport=tcp"  # TURNS (TCP + TLS)
  - "turn:turn.domen.net:3478?transport=udp"   # TURN (UDP)
  - "turn:turn.domen.net:3478?transport=tcp"   # TURN (TCP)
turn_shared_secret: "secret"
turn_user_lifetime: 86400000
turn_allow_guests: true

TURN

TURN Server: Eturnal
TURN Server Version: 1.12.1
Config TURN:

eturnal:

  listen:
    -
      port: 3479
      transport: udp
    -
      port: 3479
      transport: tcp
      proxy_protocol: true

  ## UDP relay port range (usually, several ports per A/V call are required):
  relay_min_port: 49152     # This is the default.
  relay_max_port: 65535     # This is the default.

  blacklist_peers:
    - recommended
  strict_expiry: false      

  ## Logging configuration:
  log_level: debug          # critical | error | warning | notice | info | debug
  log_rotate_size: 1048576  # 10 MiB (default: unlimited, i.e., no rotation).
  log_rotate_count: 1       # Keep 10 rotated log files.

NGINX

Reverse Proxy Server: NGINX
Reverse Proxy Server Version: 1.22.1
Config Reverse Proxy:

# TURN (TCP/UDP)
server {
    listen 3478 udp reuseport;
    listen 3478 ;
    proxy_pass 127.0.0.1:3479;
    proxy_protocol on; 
}

# TURNS (TLS)
server {
    listen 5349 ssl;
    proxy_pass 127.0.0.1:3479;
    proxy_protocol on;
    proxy_ssl on;

    ssl_certificate /home/user/.acme.sh/turn.domen.net_ecc/turn.domen.net.cer;
    ssl_certificate_key /home/user/.acme.sh/turn.domen.net_ecc/turn.domen.net.key;
}

Troubleshooting Steps

To troubleshoot the issue, follow these steps:

Check the TURN server configuration: Ensure that the TURN server is properly configured and listening on the correct ports.
Verify the Matrix server configuration: Check that the Matrix server is correctly configured and communicating with the TURN server.
Check the NGINX configuration: Verify that the NGINX configuration is correct and proxying the traffic to the TURN server.
Check the iOS device configuration: Ensure that the iOS device is properly configured to use the TURN server for making calls.
Check the network connectivity: Verify that the network connectivity is stable and not causing any issues.

Resolving the Issue

To resolve the issue, follow these steps:

Update the TURN server configuration: Update the TURN server configuration to use the correct ports and protocols.
Update the Matrix server configuration: Update the Matrix server configuration to communicate with the updated TURN server.
Update the NGINX configuration: Update the NGINX configuration to proxy the traffic to the updated TURN server.
Update the iOS device configuration: Update the iOS device configuration to use the updated TURN server for making calls.
Check the network connectivity: Verify that the network connectivity is stable and not causing any issues.

Conclusion

Q: What is the issue with making calls from Eturnal on iOS devices?

A: The issue is related to the TURN server configuration, which is not properly set up to handle the traffic from the iOS devices. This is causing the calls to fail and not connect.

Q: What is the TURN server configuration?

A: The TURN server configuration is a set of settings that determine how the TURN server handles incoming traffic from the iOS devices. It includes settings such as the ports to use, the protocols to support, and the logging configuration.

Q: Why is the TURN server configuration important?

A: The TURN server configuration is important because it determines how the TURN server handles incoming traffic from the iOS devices. If the configuration is not set up correctly, it can cause issues with making calls and affect the overall performance of the system.

Q: What are the common issues with the TURN server configuration?

A: Some common issues with the TURN server configuration include:

Incorrect port numbers
Incorrect protocols supported
Incorrect logging configuration
Incorrect proxy protocol configuration

Q: How can I troubleshoot the issue with the TURN server configuration?

A: To troubleshoot the issue with the TURN server configuration, you can follow these steps:

Check the TURN server configuration file for any errors or inconsistencies.
Verify that the TURN server is listening on the correct ports and protocols.
Check the logging configuration to ensure that it is set up correctly.
Verify that the proxy protocol is configured correctly.
Check the network connectivity to ensure that it is stable and not causing any issues.

Q: How can I resolve the issue with the TURN server configuration?

A: To resolve the issue with the TURN server configuration, you can follow these steps:

Update the TURN server configuration file to correct any errors or inconsistencies.
Update the TURN server to listen on the correct ports and protocols.
Update the logging configuration to ensure that it is set up correctly.
Update the proxy protocol configuration to ensure that it is set up correctly.
Check the network connectivity to ensure that it is stable and not causing any issues.

Q: What are the benefits of having a properly configured TURN server?

A: The benefits of having a properly configured TURN server include:

Improved call quality and reliability
Increased system performance and efficiency
Reduced latency and packet loss
Improved security and authentication

Q: How can I ensure that my TURN server is properly configured?

A: To ensure that your TURN server is properly configured, you can follow these best practices:

Regularly review and update the TURN server configuration file.
Verify that the TURN server is listening on the correct ports and protocols.
Check the logging configuration to ensure that it is set up correctly.
Verify that the proxy protocol is configured correctly.
Check the network connectivity to ensure that it is stable and not causing any issues.

Q: What are the common mistakes to avoid when configuring the TURN server?

A: Some common mistakes to avoid when configuring the TURN server include:

Incorrect port numbers
Incorrect protocols supported
Incorrect logging configuration
Incorrect proxy protocol configuration
Incorrect network connectivity settings

Q: How can I troubleshoot issues with the TURN server?

A: To troubleshoot issues with the TURN server, you can follow these steps:

Check the TURN server logs for any errors or inconsistencies.
Verify that the TURN server is listening on the correct ports and protocols.
Check the logging configuration to ensure that it is set up correctly.
Verify that the proxy protocol is configured correctly.
Check the network connectivity to ensure that it is stable and not causing any issues.

Q: How can I resolve issues with the TURN server?

A: To resolve issues with the TURN server, you can follow these steps:

Update the TURN server configuration file to correct any errors or inconsistencies.
Update the TURN server to listen on the correct ports and protocols.
Update the logging configuration to ensure that it is set up correctly.
Update the proxy protocol configuration to ensure that it is set up correctly.
Check the network connectivity to ensure that it is stable and not causing any issues.