53405: Media connection failed or Media activity ceased

Raised by the Client or Server when the media connection fails, or raised by the Client when it detects that media has stopped flowing.

• The Client was unable to establish a media connection.
• An active media connection failed liveliness checks.
• The flow of media on the connection has ceased.
• In a Peer to Peer Room on iOS 14 and later, the Participant declined local network permission which is required when apps opt in to local network candidates.
• Restrictive firewalls or NAT blocked Twilio media traffic or TURN fallbacks preventing or disrupting media, for example UDP 10000–60000 for RTP or TURN on ports 3478 and 443.

• If the problem persists in a Group Room, try connecting to or creating the Room in a different media region to lower latency and packet loss.
• Check the Client's network connectivity and allow required Twilio Video media paths including UDP 10000–60000 and TURN fallbacks on 3478 and 443.
• Ensure STUN and TURN connectivity is available. If you use custom ICE servers, verify the server URLs and credentials are valid.
• For iOS 14 and later in Peer to Peer Rooms, only request Local Network access if your app needs it and otherwise avoid opting in to local network candidates to prevent permission-related failures.
• Use the Video Preflight API to test signaling and media connectivity before joining a Room to catch issues early.
• Implement reconnection handling so the app can recover automatically when the SDK emits a reconnecting event due to a media disruption associated with this error.

• Reconnection States and Events
• Networking Considerations for Video Applications
• Video Regions and Global Low Latency