You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current implementation, instead, provides the full TURN configuration while encapsulating the ideal output underneath iceServers: [], making our implementation incompatible with other applications.
I believe that (1) the TURN-REST subproject should conform to specifications, and (2) the rest (/turn endpoint, WebRTC interface for __main__.py etc.) of the stack should stay as-is, but allow the flexibility of the Python application to parse the TURN REST API script by identifying the existence of the key iceservers: directly underneath the JSON output.
The text was updated successfully, but these errors were encountered:
ehfd
added
bug
Something isn't working
transport
Underlying media or data transport protocols
web
Web components including gst-web
labels
Jan 16, 2025
According to draft-uberti-behave-turn-rest-00, the adequate output for the TURN REST API server is like the following:
The current implementation, instead, provides the full TURN configuration while encapsulating the ideal output underneath
iceServers: []
, making our implementation incompatible with other applications.I believe that (1) the TURN-REST subproject should conform to specifications, and (2) the rest (
/turn
endpoint, WebRTC interface for__main__.py
etc.) of the stack should stay as-is, but allow the flexibility of the Python application to parse the TURN REST API script by identifying the existence of the keyiceservers:
directly underneath the JSON output.The text was updated successfully, but these errors were encountered: