Meta has launched a new calling service for businesses, where an SDP offer is sent to the business whenever a user initiates a call from WhatsApp.
We currently use a WebRTC calling infrastructure based on mediasoup, but recently discovered that mediasoup does not support sdp-lite, which Meta uses for its SDP offers.
I’m looking for guidance on how to bridge this compatibility gap. What are the available options to handle or convert Meta’s sdp-lite offers to work with a mediasoup-based setup?
Two ICE Lite agents cannot establish a connection on their own.
One peer must be a Full ICE agent to perform connectivity checks (STUN Binding requests).
Two passive peers (ICE Lite + ICE Lite) = deadlock.
As @BronzedBroth said this is not possible because mediasoup doesn’t send ICE Binding requests so this is not something that you can fix at SDP level. I understand there are some use cases for supporting full ICE in mediasoup but honestly it’s lot of work and we have other priorities.
@Sunil I created a service in Golang which acts as a bridge between Meta and Mediasoup. It helps me fullfill my requirement for the time being but I would also like remove this dependency in future if possible.
Hope this helps!