WebRTC configuration on Prod

Question

Hi everyone,

I'm encountering an issue with WebRTC video functionality that's causing some headaches. Here's the situation:

Problem:
The WebRTC video feature works perfectly fine in our UAT environment. However, when we move to production, it's failing to function as expected.

Symptoms:

- Video streams fail to establish.
- Users experience long delays or timeouts when attempting to connect.

Additional Context:

- Both UAT and production environments are set up similarly, with identical configurations wherever possible.
- This issue seems to have arisen after a recent deployment to production, but no significant changes were made to the WebRTC implementation.

Request for Assistance:

Any insights on potential differences between UAT and production environments that could affect WebRTC functionality?
Suggestions for additional troubleshooting steps we can take to pinpoint the root cause?
Any similar experiences or known issues with WebRTC in production environments?
Any help or guidance would be greatly appreciated. Thanks in advance!

Answer

It seems like the main difference between your UAT and production environments is the network configuration.
Please try the following:

Confirm there are no firewalls or network restrictions blocking WebRTC traffic in production that are not present in UAT. WebRTC uses multiple ports for signaling, media, and ICE candidates that need to be open.

Verify the production environment has working STUN and TURN servers configured identically to UAT. You can use the AWS CLI to describe the Kinesis Video Streams signaling channel endpoints.
```
aws kinesisvideo describe-signaling-channel
```
Review WebRTC logs from the production issue and compare to successful UAT logs. Check for errors establishing candidate pairs or timeouts during ICE negotiation.

Try reducing the ICE connection timeout to see if it helps troubleshoot connectivity issues.

Confirm client and server WebRTC implementations are the same in both environments. Minor changes could impact compatibility.

WebRTC configuration on Prod

Relevant content