Connectivity Overview

in order to have a conversation between a user and a digital human, a media stream from the digital human rendering application to the user's browser must be established this uses what is broadly known as the webrtc api high level networking communication paths for webrtc connection behaviours & deployment options 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 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 more information on turn want to run your own? turn servers act as intermediaries that relay audio and video data between devices that are behind nats or firewalls (like our cloud platform) there are different implementations of turn, but uneeq recommends https //github com/coturn/coturn for customers self hosting digital humans the coturn application defaults to port 3478 for the initial communication setup before media relay will start for each individual media session, a random udp port is chosen from a preconfigured range of ports depending on your setup learn about firewall configuration > docid\ iethnbk vusyhmrjgybyi