Updated Wireshark trace - Talk App cannot establish call connection (Firefox on same Android Phone does)

Hi Devs,

Nextcloud 21.0.1 / 20.0.x
Talk latest
php 7.3.27
mariadb 10.3.27

I have a rather odd problem.
My nextcloud talk app cannot establish a connection with another person when calling.
I have installed a coturn server and the connection check indicates that it works.

I also have tried it from many other locations and network but the issue is always the same. I can establish a connection with firefox on the same mobile device or using a hotspot from the mobile device but i cannot establish a connection with the nextcloud talk app itself.

I see that it is working cause if I press call it imminently rings or if i want to make a call it immediately shows up in the browser. But there is only the spinning and it never really establishes the connection.
With firefox this works in seconds.
It also works with any other device except the Nextcloud Talk App on mobile devices.

I really are out of ideas what this might be cause I waited for the new version and check again but the issue remains.

What is different between the app and Firefox on the same mobile device?
Am I missing any obvious settings and never stumbled over it?

Any advice please.

Thank you,
Florom

1 Like

Hi community,
I could not get it working.

I use nginx as reverse proxy but there is not an Intrusion Prevention.
I use ipfire but even if I deactivate everything (except from NAT) it is not working.

@michi I read your post but could not figure it out.

I made a wireshark dump from the talk app and web app and noticed that in the web talk
there are two more attributes like “Lifetime 3600” and “Fingerprint”.
Another difference I could not see.

Some help would be nice.

Nginx config:

server {
    listen       443 ssl;
    error_log /var/log/nginx/error.log debug;   
  
    server_name  one.example.com;
    ssl_certificate_key /root/.acme.sh/one.example.com/one.example.com.key;
    ssl_certificate     /root/.acme.sh/one.example.com/fullchain.cer;

    ssl_session_cache    shared:SSL:1m;
    ssl_session_timeout  5m;
    
    ssl_protocols  TLSv1.2;

    ssl_ciphers 'EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH';
    ssl_prefer_server_ciphers  on;

    location / {
        proxy_pass https://192.168.5.102;
        root   nextcloud;
        index  index.html index.htm;

        proxy_pass_header Authorization;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_http_version 1.1;
        proxy_set_header Connection "";
    proxy_buffering off;
        client_max_body_size 0;
        proxy_read_timeout 36000s;
        proxy_redirect off;
    }
}

Hi @florom,

I had exactly the same symptoms with my installation.

For me updating the Android Talk App to the latest pre-release version (11.2.0 RC1) did the trick.
Since you did not share much information, I can’t say if our setups are comparable. I have coturn installed on the same server as nextcloud. The instance is hosted behind a NAT router. I was able to use talk via browser on all internal and external devices.

Hope it helps.
Thomas

1 Like

Hi @NextcloudUser ,

that gives me hope that it will work someday.

I understand that I am sparse with information and I will go a little into detail:

I use ipfire als firewall and reverse proxy with nginx and NAT to coturn.
All Domains used are subdomains with a lets encrypt certificate.
Coturn is installed on the same machine where nextcloud is installed only using another physical LAN connection with a different ip address.
The talk app has browser version 11.1.2 and the talk android app 11.1.0.
I use apache2 nextcloud with latetest version on a debian 10 system.

Indeed this is tricky cause I do not have a “working” system I can compare to.
I do not want to connect directly nextcloud to the internet and see if that works.
Well at least not yet if there is still hope.

Thanks for responding.

Hi @NextcloudUser ,

I waited until the new Talk Android Version (12.1.1) was released.

Unfortunatly it still does not work.

Just an info.