Important
Before enabling Voice Translation, confirm that all devices meet the minimum system requirements. This ensures agents can use the feature without performance issues. Check out the Krisp AI Voice Translation system requirements article for more information.
Krisp AI Voice Translation relies on real-time audio streaming. To deploy it across your team, your network needs enough bandwidth per user and access to the domains that carry the translated audio. This article covers both.
Bandwidth requirements
The values below are per user, with Voice Translation active on both inbound and outbound audio.
| Level | Bandwidth (bidirectional, per user) |
|---|---|
| Minimum | ~130 kbps |
| Recommended | ~170 kbps (includes headroom for network variability) |
Voice Translation uses WebRTC with the Opus audio codec. Opus is adaptive and adjusts its bitrate based on network conditions, so actual bandwidth use varies within the range above.
Domain requirements
Krisp AI Voice Translation requires specific domains to be reachable from your agents' workstations. Depending on your setup, Voice Translation uses either Krisp or Daily.co for translation. Your IT team will need to allowlist the corresponding set of domains before deploying the feature.
Hint
If you're unsure which domain set applies to your configuration, contact our Customer Engineering team at support@krisp.ai for guidance.
Krisp domains
If your setup uses Krisp's media infrastructure, allowlist the servers below.
Organizations using firewall or proxy tools that decrypt HTTPS traffic should also ask their IT team to bypass certificate decryption for *.krisp.ai. For a full breakdown of all domains required for the Krisp app to function properly, see the Configuring network firewall or proxy server settings article.
Info
The domains listed in the article above are required not only when Krisp's media infrastructure is used for Voice Translation but also for general app functionality.
| Krisp domains | |
|---|---|
| Domain | Purpose |
|
wss://media-gateway.krisp.ai wss://wss-media.krisp.ai |
Primary WSS server |
| wss://streaming.krisp.ai | Failover WSS server |
Daily.co domains
If your setup uses Daily.co for real-time communication, add the domains below to your network allow-list.
Organizations using firewall or proxy tools that decrypt HTTPS traffic should also ask their IT team to bypass certificate decryption for *.daily.co to maintain end-to-end encryption.
| Web requests | ||
|---|---|---|
| Domain | Port | Purpose |
| krispai.daily.co | TCP/443 | General Daily functionality |
| *.wss.daily.co | TCP/443 | Daily Signaling server |
|
b.daily.co c.daily.co |
TCP/443 | Daily CDN resources |
| gs.daily.co | TCP/443 | Daily Dispatch server |
| prod-ks.pluot.blue | TCP/443 | ICE Negotiation |
| WebRTC requests | ||
|---|---|---|
| Domain | Port | Purpose |
| *.wss.daily.co | TCP/443, UDP/40000-49999 |
UDP direct connection to media servers |
| stun.cloudflare.com | UDP/3478, UDP/53 | STUN Cloudflare |
| global.stun.twilio.com | UDP/3478, UDP/53 | STUN Twilio (optional, for the best call experience) |
| turn.cloudflare.com | UDP/TCP/3478, UDP/53, TCP/80, TCP/5349, TCP/TLS/443 |
TURN Cloudflare |
| *.turn.twilio.com | TCP(TLS)/443, UDP/TCP/3478, TCP(TLS)/5349 |
TURN Twilio (optional, for the best call experience) |
Info
If you encounter any issues during configuration, submit a problem report from an affected device or contact our Customer Engineering team at support@krisp.ai for assistance.