[Spce-user] RTPEngine ICE Candidates Exchange
Richard Fuchs
rfuchs at sipwise.com
Wed Dec 16 08:20:26 EST 2015
On 12/16/2015 08:11 AM, afshin afzali wrote:
> Guys,
>
> The thing which I understand from your comments is that all will be done
> by exchanging the offer and answer SDPs between two peers. Lets assume
> that the peer which is engaged to the rtpengine is a WebRTC client and
> after exchanging the offer and answer SDPs, (before ICE completion)
> detects a new ICE candidate. The specification says it should send that
> ICE candidate to its peer via the signaling server (in our case it is
> SIP server). My question is here. In case of using SIP as a signaling
> protocol for WebRTC we do not have this mechanism to exchange the new
> detected ICE candidates?
I assume you're talking about Trickle ICE. Trickle ICE over SIP uses (or
ought to use) SIP INFO messages to send updates of the list of ICE
candidates. While rtpengine supports these kinds of updates, I don't
believe NGCP supports INFO messages yet.
Cheers
More information about the Spce-user
mailing list