Project

General

Profile

Actions

Task #7992

closed

Make TURN server usable to matrix/synapse instances

Added by Timothée Floure almost 3 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Normal
Target version:
-
Start date:
05/11/2020
Due date:
% Done:

0%

Estimated time:
PM Check date:

Description

We have a coturn instance running at matrix-turn.ungleich.ch but it does not seem to be usable at the moment.

Related cdist types: * __coturn * __matrix-synapse

Actions #1

Updated by Timothée Floure almost 3 years ago

Packets get to coturn but weird debug log on server:

```
41: timer_event_handler: timeout 0x5631ad199e70: timer_handler
42: timer_event_handler: timeout 0x7f837c0036a0: timer_timeout_handler
42: timer_event_handler: timeout 0x7f837c002450: timer_handler
42: timer_event_handler: timeout 0x7f83740036a0: timer_timeout_handler
42: timer_event_handler: timeout 0x7f8374002450: timer_handler
42: timer_event_handler: timeout 0x7f83780025f0: timer_handler
42: timer_event_handler: timeout 0x5631ad199e70: timer_handler
43: timer_event_handler: timeout 0x7f837c0036a0: timer_timeout_handler
43: timer_event_handler: timeout 0x7f837c002450: timer_handler
43: timer_event_handler: timeout 0x7f83740036a0: timer_timeout_handler
43: timer_event_handler: timeout 0x7f8374002450: timer_handler
43: timer_event_handler: timeout 0x7f83780025f0: timer_handler
43: timer_event_handler: timeout 0x5631ad199e70: timer_handler
44: timer_event_handler: timeout 0x7f837c0036a0: timer_timeout_handler
44: timer_event_handler: timeout 0x7f837c002450: timer_handler
44: timer_event_handler: timeout 0x7f83740036a0: timer_timeout_handler
44: timer_event_handler: timeout 0x7f8374002450: timer_handler
44: timer_event_handler: timeout 0x7f83780025f0: timer_handler
44: timer_event_handler: timeout 0x5631ad19b0a0: rtcp_map_timeout_handler
44: timer_event_handler: timeout 0x5631ad199e70: timer_handler
45: timer_event_handler: timeout 0x7f837c0036a0: timer_timeout_handler
45: timer_event_handler: timeout 0x7f837c002450: timer_handler
45: timer_event_handler: timeout 0x7f83740036a0: timer_timeout_handler
45: timer_event_handler: timeout 0x7f8374002450: timer_handler
45: timer_event_handler: timeout 0x7f83780025f0: timer_handler
46: timer_event_handler: timeout 0x5631ad199e70: timer_handler
46: timer_event_handler: timeout 0x7f837c002450: timer_handler
46: timer_event_handler: timeout 0x7f837c0036a0: timer_timeout_handler
46: timer_event_handler: timeout 0x7f83740036a0: timer_timeout_handler
46: timer_event_handler: timeout 0x7f8374002450: timer_handler
46: timer_event_handler: timeout 0x7f83780025f0: timer_handler
46: timer_event_handler: timeout 0x5631ad199e70: timer_handler
47: timer_event_handler: timeout 0x7f837c002450: timer_handler
47: timer_event_handler: timeout 0x7f837c0036a0: timer_timeout_handler
47: timer_event_handler: timeout 0x7f83740036a0: timer_timeout_handler
47: timer_event_handler: timeout 0x7f8374002450: timer_handler
47: timer_event_handler: timeout 0x7f83780025f0: timer_handler
```

Actions #2

Updated by Timothée Floure almost 3 years ago

The above logs are atually normal - at least that's what some chinese website says :-)

Actions #3

Updated by Timothée Floure almost 3 years ago

With some hacking and debugging I got the whole pipeline to work. I will clean it and put it in production tomorrow.

Actions #4

Updated by Timothée Floure almost 3 years ago

  • Status changed from New to Closed

Fixed a long time ago :-) Closing.

Actions

Also available in: Atom PDF