Networking, WebRTC + TURN

context in order to have a conversation between a user and a digital human, a media stream from the digital human renderering application to the user's browser must be established this uses what is broadly know as the webrtc api high level networking communication paths for webrtc connection behaviours direct (miniprem) in order for the uneeq platform to be able to negotiate a direct connection between the digital human renderer and the browser, each party needs to send the other its own ip address the browser needs to be able to access the ip address sent by the renderer application, and vice versa indirect (cloud) for communication between our cloud hosted renderers and end users, we must use a turn server to relay the media stream between the renderer and the end users browser with the turn protocol, the turn server connects to both the renderer and to the browser the renderer sends all of its streamed data to the turn server, which forwards the data on to the browser in this case, there is no direct connection between the renderer and the browser this is very common in webrtc, in general if you need to support mobile devices over wireless carrier networks or clients on secured enterprise networks, you may have no choice but to use a turn server mobile and enterprise networks can sometimes prevent clients from successfully connecting using webrtc protocols what networking configuration do i need? depending on your region, you will require users to be able to access region status url ports all current uneeq io 443 (tcp) global / us current turn uneeq io 3478 and 5349 (both udp and tcp) 22000 23000 udp eu current turn uneeq io 3478 and 5349 (both udp and tcp) 22000 23000 udp if you have any questions, reach out to your customer service manager for assistance