warioishere
commented
1 month ago additional info, our coturn server should work without problems:
turnutils_uclient -p 5349 -W xyz -v -y coturn.mydomain.ch
0: : IPv4. Connected from: 192.168.1.84:39630
0: : IPv4. Connected from: 192.168.1.84:39630
0: : IPv4. Connected to: 82.165.65.57:5349
0: : allocate sent
0: : allocate response received:
0: : allocate sent
0: : allocate response received:
0: : success
0: : IPv4. Received relay addr: 82.165.65.57:56644
0: : clnet_allocate: rtv=14186039741895531052
0: : refresh sent
0: : refresh response received:
0: : success
0: : IPv4. Connected from: 192.168.1.84:34058
0: : IPv4. Connected to: 82.165.65.57:5349
0: : IPv4. Connected from: 192.168.1.84:33738
0: : IPv4. Connected to: 82.165.65.57:5349
0: : IPv4. Connected from: 192.168.1.84:45996
0: : IPv4. Connected to: 82.165.65.57:5349
0: : IPv4. Connected from: 192.168.1.84:49300
0: : IPv4. Connected to: 82.165.65.57:5349
0: : allocate sent
0: : allocate response received:
0: : allocate sent
0: : allocate response received:
0: : success
0: : IPv4. Received relay addr: 82.165.65.57:56645
0: : clnet_allocate: rtv=0
0: : refresh sent
0: : refresh response received:
0: : success
0: : allocate sent
0: : allocate response received:
0: : allocate sent
0: : allocate response received:
0: : success
0: : IPv4. Received relay addr: 82.165.65.57:55852
0: : clnet_allocate: rtv=6301046898216256877
0: : refresh sent
0: : refresh response received:
0: : success
0: : allocate sent
0: : allocate response received:
0: : allocate sent
0: : allocate response received:
0: : success
0: : IPv4. Received relay addr: 82.165.65.57:55853
0: : clnet_allocate: rtv=0
0: : refresh sent
0: : refresh response received:
0: : success
0: : allocate sent
0: : allocate response received:
0: : allocate sent
0: : allocate response received:
0: : success
0: : IPv4. Received relay addr: 82.165.65.57:58186
0: : clnet_allocate: rtv=5524863492269791289
0: : refresh sent
0: : refresh response received:
0: : success
0: : channel bind sent
1: : cb response received:
1: : success: 0x5b52
1: : channel bind sent
1: : cb response received:
1: : success: 0x5a83
1: : channel bind sent
1: : cb response received:
1: : success: 0x4cb1
1: : channel bind sent
1: : cb response received:
1: : success: 0x7375
1: : Total connect time is 1
1: : start_mclient: msz=4, tot_send_msgs=0, tot_recv_msgs=0, tot_send_bytes ~ 0, tot_recv_bytes ~ 0
2: : start_mclient: msz=4, tot_send_msgs=0, tot_recv_msgs=0, tot_send_bytes ~ 0, tot_recv_bytes ~ 0
3: : start_mclient: msz=4, tot_send_msgs=0, tot_recv_msgs=0, tot_send_bytes ~ 0, tot_recv_bytes ~ 0
4: : start_mclient: msz=4, tot_send_msgs=10, tot_recv_msgs=10, tot_send_bytes ~ 1000, tot_recv_bytes ~ 1000
5: : start_mclient: msz=4, tot_send_msgs=10, tot_recv_msgs=10, tot_send_bytes ~ 1000, tot_recv_bytes ~ 1000
6: : start_mclient: msz=4, tot_send_msgs=15, tot_recv_msgs=15, tot_send_bytes ~ 1500, tot_recv_bytes ~ 1500
6: : done, connection 0x740d1c77d010 closed.
6: : done, connection 0x740d1c75c010 closed.
6: : done, connection 0x740d1c73b010 closed.
6: : done, connection 0x740d1c71a010 closed.
7: : start_mclient: tot_send_msgs=20, tot_recv_msgs=20
7: : start_mclient: tot_send_bytes ~ 2000, tot_recv_bytes ~ 2000
7: : Total transmit time is 6
7: : Total lost packets 0 (0.000000%), total send dropped 0 (0.000000%)
7: : Average round trip delay 35.700000 ms; min = 31 ms, max = 39 ms
7: : Average jitter 2.000000 ms; min = 0 ms, max = 5 ms
S7evinK
Description
Hey, since a year I am having an issue that calling notifications dont work when using a own ntfy push server with our own matrix synapse server instance. Message notifications do work generally but as know by others not really reliable and with huge delays sometimes Using an matrix.org with our own ntfy server do work , both on messages and both on calls. We use a own coturnserver, I just switched from letsencrypt certs to zerossl certs as somebody suggested.
Still, we dont get call notifications to work. With Letsencrypt certs. nothing happens. With zerossl certs, elements crashes after opening the phone after a not notified call. I have been searching for almost a year now and nobody can help. I checked ntfy docks, checked with the devs there, my ntfy server seems to work. Also because it works with matrix.org servers.
This is the logs from element-android:
This is the issue I openend on element-android to see more details:
https://github.com/element-hq/element-android/issues/8761
I would be sooo happy to get this to work after months and almost years of trying. I always hoped, gonna be fixed with new synapse Versions. But not, nothing fixes our issue.
We are on latest synapse version, and latest f-droid element version
Thanks in advance
Steps to reproduce
Calling on matrix.org account with own ntfy server works, we get call notification Calling on our own matrix instance (matrix.yourdevice.ch) doesnt work, no notification
Homeserver
matrix.yourdevice.ch
Synapse Version
{"server_version":"1.108.0"}
Installation Method
Debian packages from packages.matrix.org
Database
PostgresSQL
Workers
Single process
Platform
Ubuntu Server 22.04 virtualized on proxmox 8.2.2
Configuration
no
Relevant log output
Anything else that would be useful to know?
No response