maguoloalceo

Thank you for your answer, what I was trying to do is to make a call from Sipsorcery to another user agent using an RTCPeerConnection object instead of the "standard"...

I'm sorry to not be clear enough, what I'm trying to do is to use STUN (and eventually TURN to handle symmetric NAT scenarios) with SIP, and I thought using...

Yes, I was using the AsteriskIce example and that's why I was trying to use the RTCPeerConnection object.

I rewiewed your example but I didn't found any signficant differences from my code. Can you tell me if the SDP offer on your demo has the m line with...

Looking at your SDP negotiation I see that the difference between your SDP and mine is that I'm trying to implement the "half-trickle" ICE negotiation [https://www.rfc-editor.org/rfc/rfc8838.html#name-half-trickle](url) because the pjsip client...

Forcing the c and m line to a valid value the negotiation completes succesfully. By the way, I get the same `ice-mismatch` error even with Linphone [https://new.linphone.org/technical-corner/linphone?qt-technical_corner=2#qt-technical_corner](url) an open source...

I think both pjsip and Linphone are expecting _real_ values in the m and c parameters. Looking at [https://datatracker.ietf.org/doc/html/rfc8839#section-4.3.1](url) `It is valid for an offer "m=" line to include no...

Yes, exactly.