Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

coturn configuration #3

Open
localguru opened this issue Apr 26, 2020 · 0 comments
Open

coturn configuration #3

localguru opened this issue Apr 26, 2020 · 0 comments

Comments

@localguru
Copy link

localguru commented Apr 26, 2020

Hi Jens-Christian!

Thanks for sharing your configuration, great! After reviewing the coturn configuration I ask myself some questions about your setup:

  1. coturn recommends two public IPs. There is a listening-ip=0.0.0.0 option in your /etc/turnserver.conf file. Did you configure your coturn host with multiple IPs and if so do all IPs point/resolve to the same DNS name? Or do you run multiple coturn stun/turn servers with different IPs and DNS names like coturn1.domain.tld, coturn2.domain.tld etc.?

  2. there is no tls-listening-port=443 setting in your /etc/turnserver.conf, but you set cert and pkey in your /etc/turnserver.conf and in prosody_config.j2 you set turns with port = "443", transport = "tcp". Could you explain please?

  3. Did you set SRV records for stun/turn in your DNS?

  4. On videobridge side, it's just setting

    org.ice4j.ice.harvest.STUN_MAPPING_HARVESTER_ADDRESSES

    in sip-communicator.properties, right?

  5. Is port 443 configured to tcp only or tcp and udp and is port 443 the only open incoming port for coturn on your firewall or do ports 10000-20000/udp have to be open too?

Cheers!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant