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.

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.

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.

Depending on your region, you will require users to be able to access:

If you have any questions, reach out to your customer service manager for assistance.

Networking, WebRTC + TURN

Frequently Asked Questions

Push to Talk Deprecation Notice

Feature: Enhanced Speech Recognition

Announcements

UneeQ Docs

Overview

Getting Started