We’re looking for a MediaSoup specialist to help resolve issues in our spatial audio/video conferencing platform.
Our Architecture:
Backend (Node.js/TypeScript):
-
MediaSoup v3.14.12 SFU with custom adapter pattern
-
Multi-pod Kubernetes deployment with cross-pod PipeTransport
-
Redis-based state management and WebSocket signaling
-
Participant lifecycle management with device ID persistence
Frontend SDK (TypeScript):
-
mediasoup-client v3.6.90 integration
-
Drop-in replacement for Dolby/Voxeet SDK
-
Custom SDP mid conflict detection and consumer deduplication
-
WebRTC transport management with automatic reconnection
Integration:
-
Real-time cross-pod media routing
-
Stale participant cleanup with device migration
-
Consumer/Producer lifecycle coordination across multiple code paths
Current Issues:
-
SDP Mid Conflicts: Multiple consumers getting assigned identical MID values, causing WebRTC negotiation failures.
-
Consumer Duplication: Race conditions between methods.
-
Cross-Pod Media Routing: PipeTransport connections working but consumer creation failing for cross-pod producers.
-
Participant State Synchronization: Between Redis state, MediaSoup local registry, and WebRTC transport reconstruction.
What we need:
An expert who can-
-
Review our MediaSoup integration patterns and identify architectural issues
-
Optimize consumer/producer creation flows to eliminate race conditions
-
Debug cross-pod media routing scenarios
-
Provide best practices for multi-pod MediaSoup deployments
-
Help resolve SDP negotiation conflicts at the WebRTC level