I'm assuming the topmost call is the problematic one: Your local SDP
does not show even any host candidates.
Does your service live.amaryllo.eu support trickle ICE at all? E.g. does
you code listen on the onicedandidate event?
Nils
On 12/3/14 6:07 PM, [email protected] wrote:
Here is a full logging message
(https://mega.co.nz/#!lNckgIwD!wFL9yXHbH-U79iaOYHp_MphuKol3-14tA_yRQokWylk)
Actually, I am very sure I had set STUN and TURN in every PeerConnection (I had
checked this with debugging message). But it still doesn't work.
On Wednesday, December 3, 2014 11:40:05 PM UTC+8, Byron Campen wrote:
A couple of things. Firt, that logging is very misleading. It is
complaining that there are no STUN/TURN servers in the global config
store for nICEr. We configure STUN/TURN on a per-context basis, so we
don't actually configure them in the global store. Second, we are
planning on removing that default stun.services.mozilla.com sometime
this coming year. Don't count on it being around forever.
Can you get us some logging for the failure you're seeing, and
perhaps a packet trace?
Best regards,
Byron Campen
On 12/2/14 11:53 PM, [email protected] wrote:
Hi all,
Today, one thing is happened to me, not good. My FF33 can not connect to the
other webrtc client anymore. I check about:webrtc, and find the following error
message:
(ice/WARNING) ICE(PC:1417591976251000 (id=3291
url=https://live.amaryllo.eu/#)): No STUN servers specified
(ice/NOTICE) ICE(PC:1417591976251000 (id=3291 url=https://live.amaryllo.eu/#)):
No TURN servers specified
I think that the root cause in this issue. My question is.. FF33 has its
default STUN Server (stun:stun.services.mozilla.com), why it will report me No
STUN servers?
However, this case is not easy to reproduce, and it will work after restarting
FF33. Anyone can help?
_______________________________________________
dev-media mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-media
On Wednesday, December 3, 2014 11:40:05 PM UTC+8, Byron Campen wrote:
A couple of things. Firt, that logging is very misleading. It is
complaining that there are no STUN/TURN servers in the global config
store for nICEr. We configure STUN/TURN on a per-context basis, so we
don't actually configure them in the global store. Second, we are
planning on removing that default stun.services.mozilla.com sometime
this coming year. Don't count on it being around forever.
Can you get us some logging for the failure you're seeing, and
perhaps a packet trace?
Best regards,
Byron Campen
On 12/2/14 11:53 PM, [email protected] wrote:
Hi all,
Today, one thing is happened to me, not good. My FF33 can not connect to the
other webrtc client anymore. I check about:webrtc, and find the following error
message:
(ice/WARNING) ICE(PC:1417591976251000 (id=3291
url=https://live.amaryllo.eu/#)): No STUN servers specified
(ice/NOTICE) ICE(PC:1417591976251000 (id=3291 url=https://live.amaryllo.eu/#)):
No TURN servers specified
I think that the root cause in this issue. My question is.. FF33 has its
default STUN Server (stun:stun.services.mozilla.com), why it will report me No
STUN servers?
However, this case is not easy to reproduce, and it will work after restarting
FF33. Anyone can help?
_______________________________________________
dev-media mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-media
_______________________________________________
dev-media mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-media
_______________________________________________
dev-media mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-media
