[Spce-user] RTPEngine ICE Candidates Exchange

[afshin afzali]

I hope this diagram can explain my point clear!

On Wed, Dec 16, 2015 at 4:41 PM, afshin afzali <a.afzali2003 at gmail.com>
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?
>
> Best
> Afshin
>
> On Wed, Dec 16, 2015 at 4:28 PM, Daniel Grotti <dgrotti at sipwise.com>
> wrote:
>
>> Hi,
>> ICE candidate are part of SDP.
>> You can add rtpproxy as ICE candidate if you want. If you don't, the ICE
>> candidate list contained in the SDP initiating the dialog will go the
>> destination, that's it. So the destination will reply with ICE if
>> support it.
>>
>>
>>
>> --
>> Daniel Grotti
>> VoIP Engineer
>>
>>
>> Sipwise GmbH
>> Europaring F15 | 2345 Brunn am Gebirge, Austria | www.sipwise.com
>>
>> On 12/16/2015 01:55 PM, afshin afzali wrote:
>> > Hi Daniel,
>> >
>> > Thanks for the reply. By doing this I involve rtpengine into the RTP
>> > path (is it right?). But my question is something else. If rtpengine
>> > detects an ICE candidate and wants to share it with its peer how can do
>> it?
>> >
>> > Best,
>> >  Afshin
>> >
>> > On Wed, Dec 16, 2015 at 3:48 PM, Daniel Grotti <dgrotti at sipwise.com
>> > <mailto:dgrotti at sipwise.com>> wrote:
>> >
>> >     Hi,
>> >     you have the possibility to add rtpproxy in the ICE candidate list
>> by
>> >     setting the Domains/subscriber/peer parameter "use_rtpproxy",
>> selecting:
>> >
>> >     - Always with rtpproxy as additional ICE candidate
>> >     - Always with rtpproxy as only ICE candidate
>> >
>> >
>> >     --
>> >     Daniel Grotti
>> >     VoIP Engineer
>> >
>> >
>> >     Sipwise GmbH
>> >     Europaring F15 | 2345 Brunn am Gebirge, Austria | www.sipwise.com
>> >     <http://www.sipwise.com>
>> >
>> >     On 12/16/2015 12:49 PM, afshin afzali wrote:
>> >     > Hi Guys,
>> >     >
>> >     > As a part of WebRTC connection establishment we need to exchange
>> ICE
>> >     > candidates between peers. I was wondering how rtpengine does it?
>> >     Does it
>> >     > use SIP messages to exchange ? or something else ?
>> >     >
>> >     > Appreciate all!
>> >     >
>> >     > Afshin
>> >     >
>> >     >
>> >     > _______________________________________________
>> >     > Spce-user mailing list
>> >     > Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
>> >     > https://lists.sipwise.com/listinfo/spce-user
>> >     >
>> >     _______________________________________________
>> >     Spce-user mailing list
>> >     Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
>> >     https://lists.sipwise.com/listinfo/spce-user
>> >
>> >
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20151216/962cbf79/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 140843 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20151216/962cbf79/attachment-0001.png>