1536551 - WebRTC relay candidate uses relay address for the raddr/rport

Status: NEW

(Core :: WebRTC, defect, P3)

Description

[daginge]

Attachment: safari-rtcstats-dump-of-firefox-call

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.121 Safari/537.36

Steps to reproduce:

We have a dump of a call (sadly, only the Safari-side) where the Firefox client sends an odd looking relay candidate where the raddr and rport match the relay address.

See attached file, which can be opened by going to https://fippo.github.io/webrtc-dump-importer/rtcstats and uploading it there. You want to look at PC_2.

As you can see, the call failed, but I don't know if this issue is related to the call failing or not. The issue can be replicated easily by going to AppRTC, but here the call connects.

Actual results:

When the firefox side sends its relay candidate, it is the following:
candidate:4 1 UDP 92151039 18.197.182.91 51455 typ relay raddr 18.197.182.x rport 51455

Notice that raddr and rport match the relay address.

Expected results:

I would expect the relay candidate to contain the srflx candidate address
candidate:4 1 UDP 92151039 18.197.182.91 51455 typ relay raddr 84.20.99.x rport 51455

Comment 1

[daginge]

Relevant IRC discussion: https://mozilla.logbot.info/media/20190319#c16106356

Comment 2

[Dan Minor [:dminor]]

Setting to confirmed and P3 based upon IRC discussion.