Re: [MMUSIC] ICE and RTCP host components

[Roman Shpount <[e-mail]>]

On Sat, Oct 24, 2015 at 7:22 PM, Paul Kyzivat <[e-mail]> wrote:

> On 10/24/15 12:05 PM, Christer Holmberg wrote:
>
>> Hi,
>>
>> Note that on a separate thread we are concluding that if you do bundle
>>> you must to rtcp-mux.
>>>
>>> If we don't already have a problem with legacy ICE, I think it might
>>> also make sense to require that if you do ICE you must to rtcp-mux.
>>>
>>
>> I would not like to take that step yet. There ARE deployments that do ICE
>> (or, at least ICE lite), but that do NOT do rtcp-mux.
>>
>
> Fine. Can you find another way out of this problem?
>
>
Original question was if originating end point needs to listen on two ports
-- the answer is, it does not. It is supposed to allocate port rtp+1 for
RTCP and put it in the SDP rtcp attribute. The only time you end up with
port and address not being rtp+1 is if you need to use server reflexive
candidates. If you need to interop with non-ICE legacy end points, your
best solution is not to use server reflexive candidates and use relay. So
make sure to deploy TURN servers and everything will work. If you want to
make sure end point will only communicate with ICE enabled end points
(disable legacy support), put IN IP4 0.0.0.0 in the c= line. No new
problems here, but some language to clarify this might be necessary.

In general I consider SDP rtcp attribute in case of ICE unnecessary. It is
only used when TURN servers are not used where things break often anyway.
_____________
Roman Shpount