Closed duratm closed 1 week ago
the peer connection configurations are not what they should be. The IceTransportPolicy is not where he belongs
Read the readme and compare to actual documentations
Expected behavior: peer connection configuration in elixir:
@opts [ ice_servers: [%{urls: "turn:<STUNNERIP>:3478?transport=udp", "username": "user-1", "credential": "pass-1"}], ice_transport_policy: :relay, audio_codecs: @audio_codecs, video_codecs: @video_codecs ]
peer connection configuration in Javascript or typescript:
{ iceServers: [{ urls: 'turn:<STUNNERIP>:3478?transport=udp', username: 'user-1', credential: 'pass-1'}], iceTransportPolicy: "relay" }
Actual behavior: [What actually happened] peer connection configuration in elixir:
@opts [ ice_servers: [%{urls: "turn:<STUNNERIP>:3478?transport=udp", "username": "user-1", "credential": "pass-1", "iceTransportPolicy": "relay"}], audio_codecs: @audio_codecs, video_codecs: @video_codecs ]
{ iceServers: [{ urls: 'turn:<STUNNERIP>:3478?transport=udp', username: 'user-1', credential: 'pass-1',iceTransportPolicy: 'relay'}] }
[Which version of STUNner you are using]
It is leading stunner to refuse connections
Description
the peer connection configurations are not what they should be. The IceTransportPolicy is not where he belongs
Steps to Reproduce
Read the readme and compare to actual documentations
Expected behavior: peer connection configuration in elixir:
peer connection configuration in Javascript or typescript:
Actual behavior: [What actually happened] peer connection configuration in elixir:
peer connection configuration in Javascript or typescript:
Versions
[Which version of STUNner you are using]
Info
It is leading stunner to refuse connections