-
-
Notifications
You must be signed in to change notification settings - Fork 123
Open
Labels
bugSomething isn't workingSomething isn't workingtransportUnderlying media or data transport protocolsUnderlying media or data transport protocolswebWeb components including gst-webWeb components including gst-web
Description
According to draft-uberti-behave-turn-rest-00, the adequate output for the TURN REST API server is like the following:
{
"username" : "12334939:mbzrxpgjys",
"password" : "adfsaflsjfldssia",
"ttl" : 86400,
"uris" : [
"turn:1.2.3.4:9991?transport=udp",
"turn:1.2.3.4:9992?transport=tcp",
"turns:1.2.3.4:443?transport=tcp"
]
}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.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingtransportUnderlying media or data transport protocolsUnderlying media or data transport protocolswebWeb components including gst-webWeb components including gst-web