1136102 - rtcp-mux and RTCP candidates included in answer SDP.

Status: RESOLVED FIXED

(Core :: WebRTC: Signaling, defect, P2)

Description

[Sumesh]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.115 Safari/537.36

Steps to reproduce:

A call from PBX to firefox browser based client end up with ice failure. Gateway includes rtcp-mux and candidates ( Both RTP and RTCP) in the Offer sdp. But firefox answers with rtcp-mux and RTCP candidate in SDP which caused gateway runs into connectivity check failure due to connectivity check had not triggered from RTCP candidate of firefox browser.

v=0
o=Mozilla-SIPUA-35.0.1 25562 0 IN IP4 0.0.0.0
s=SIP Call
t=0 0
a=ice-ufrag:bb844f25
a=ice-pwd:47490e0415d32df8ed2c3425bfb90793
a=fingerprint:sha-256 5D:B4:CD:2B:A9:E1:37:A3:BF:C0:25:12:3F:EF:C8:A6:83:5C:C5:A2:C7:64:DD:EB:97:A3:72:9E:E2:CA:18:51
m=audio 9 RTP/SAVPF 8 126
c=IN IP4 0.0.0.0
a=rtpmap:8 PCMA/8000
a=rtpmap:126 telephone-event/8000
a=fmtp:126 0-15
a=sendrecv
a=setup:active
a=rtcp-mux
a=candidate:0 1 UDP 2128609535 192.168.1.32 53645 typ host 
a=candidate:0 2 UDP 2128609534 192.168.1.32 53646 typ host 



Actual results:

End up in ICE connectivity check failure.

Comment 1

[:shell escalante]

found in triage - can one of you guys take a look at this?

Comment 2

[Nils Ohlmeier [:drno]]

I just verified that Firefox 39 only emits one ICE candidate in case rtcp-mux has been agreed to.

Comment 3

[Byron Campen [:bwc]]

This should also work in 38, as this was fixed in the renegotiation patches.

Comment 4

[Nils Ohlmeier [:drno]]

Reproduce the problem with Firefox 36.

Comment 5

[Nils Ohlmeier [:drno]]

This is already fixed in Firefox 37.