On 7/22/16 4:52 AM, [email protected] wrote:
On Thursday, March 24, 2016 at 6:34:51 PM UTC+5:30, Byron Campen wrote:
I believe we'll tolerate that.
Best regards,
Byron Campen
On 3/24/16 6:10 AM, Alexander Abagian wrote:
Would it be OK if I use 0.0.0.0 as a raddr ?
On Thursday, March 17, 2016 at 8:31:57 PM UTC+3, Byron Campen wrote:
On 3/17/16 12:18 PM, Alexander Abagian wrote:
Hi,
I've got the following warning in FF 45 :
(ice/ERR) peer received no media stream attributes
(ice/ERR) peer specified too many components
(ice/WARNING) specified bogus candidate
(ice/WARNING) Error parsing attribute: candidate:1316968211 1 UDP 2130706430
91.224.14.66 8001 typ srflx generation 0
What's wrong with this ICE candidate ? Firefox wants raddr & rport ?
Yes, raddr and rport are required on srflx, prflx, and relay
candidates according to RFC 5245.
Best regards,
Byron Campen
_______________________________________________
dev-media mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-media
Hi, Is there any work around for this error?
I am also getting the same issue when trying to call FF from Chrome.
(ice/ERR) ICE(PC:1469173555764000 (id=2147483755
url=http://172.16.120.203/mbsclient/subodh/#/call)): peer (PC:1469173555764000
(id=2147483755 url=http://172.16.120.203/mbsclient/subodh/#/call):default)
specified too many components
(ice/WARNING) ICE(PC:1469173555764000 (id=2147483755
url=http://172.16.120.203/mbsclient/subodh/#/call)): peer (PC:1469173555764000
(id=2147483755 url=http://172.16.120.203/mbsclient/subodh/#/call):default)
specified bogus candidate
I am trying on FF 48+.
_______________________________________________
dev-media mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-media
That just looks like a case where a candidate wasn't used because
of rtcp-mux. Is ICE failing in this case?
Best regards,
Byron Campen
_______________________________________________
dev-media mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-media
