Firewall Configuration

Welcome to Firewall Configuration!

To ensure smooth operation of KonPro's Interactive Avatar (powered by LiveKit), your corporate network firewall needs to allow traffic to specific hosts and ports. This guide outlines exactly what to open up for signal and media traffic.

What Needs Access?

LiveKit uses WebSocket (WSS) and WebRTC (TLS/DTLS) protocols over both TCP and UDP. All connections are encrypted.

Minimum Required (For Basic Functionality)

Minimum Required Configuration
HostPortPurpose
*.livekit.cloudTCP 443Secure signaling via WebSocket
*.turn.livekit.cloudTCP 443TURN over TLS - fallback when UDP is blocked
*.host.livekit.cloudUDP 3478TURN/UDP for establishing peer-to-peer connections
*://api.konpro.aiTCP 443Avatar API and Signaling via WebSocket and HTTPS

Wildcards Not Allowed?

If your corporate firewall does not support wildcard domains (like *.livekit.cloud), you'll need to allow traffic to specific hostnames.

Please visit: https://docs.livekit.io/home/cloud/firewall/ for latest list of hostnames, replace with konpro-feapbkvq.

IT Notes

  • TLS encryption (port 443) ensures secure media and signaling.
  • UDP is strongly recommended for low-latency audio/video performance.
  • If UDP is blocked, TURN over TCP (443) will be used as a fallback but may degrade quality.

Additional Troubleshooting Tools:

Test Browser Compatibility: https://livekit.io/webrtc/browser-test

Test Connections:

Using the response from: https://docs.konpro.ai/reference/new-session#response, take note of the url and access_token.

Enter in url and access_token here: https://livekit.io/connection-test

Conclusion

Proper firewall configuration is essential for the smooth operation of KonPro's Interactive Avatar system. By following the minimum required settings and implementing the recommended configurations, you can ensure optimal performance and reliability for your avatar interactions.

Updated: about 2 months ago

Did this page help you?

Table of Contents