[OpenSIPS-Users] Mediaproxy ICE negotiations

[John Quick]

I mean if only one end point supports ICE, then there will be no ICE
negotiation. In that case, the "c=" parameter will determine the path for
the RTP.

John


-----Original Message-----
From: Saúl Ibarra Corretgé [mailto:saul at ag-projects.com] 
Sent: 02 March 2012 15:14
To: john.quick at smartvox.co.uk
Cc: 'OpenSIPS users mailling list'
Subject: Re: [OpenSIPS-Users] Mediaproxy ICE negotiations

Hi,

On Mar 2, 2012, at 4:07 PM, John Quick wrote:

> Many thanks. I had not seen the slideshare.net information before. It 
> is very good.
> 

Thanks!

> I have another question on the same subject.  In a call like this:
> UAC (supports ICE) -- INVITE -->  OpenSIPS/Mediaproxy  -- --> UAS 
> (does not support ICE)
> 
> ..if OpenSIPS calls engage_mediaproxy() for every call, then 
> Mediaproxy will be used because the SDP "c=" parameter will have been
modified.
> For a similar call where the UAS *does* support ICE, then "c=" will be 
> ignored in favour of using ICE negotiation. Is that right?
> 

No. The "c=" line is always modified by OpenSIPS, in addition to adding the
"relay" candidates. You may choose a lower priority to prefer host
candidates instead of the "relay" ones though.


Regards,

--
Saúl Ibarra Corretgé
AG Projects