- 최신
- 최다 투표
- 가장 많은 댓글
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.
관련 콘텐츠
- AWS 공식업데이트됨 일 년 전