Bug tracking
-
ebunyan last edited by
One of customers reported a problem using our WebRTC gateway with Opera a few weeks back which we tracked down to Opera offering H264 when it couldn't decode it, so I raised a bug with Opera (and banned H264 when the browser is Opera using a horrible user agent regex because there appears to be no other way to identify it, though this means the customer has to have extra computing power to transcode).
My problem is there appears to be no way to track that bug. The email I got said they can't reply to questions through the bug tracking system, and I can't see any status, I just have the email. Going forwards I really need to be able to know what happens with that bug, and if it's even likely to be fixed. It's a pretty major bug for us as it cuts the number of calls our customers servers can handle by 80%, and because we have to ban the codec if we don't know when it's fixed that will carry on after it is; I'm hoping it is because without H264 the WebRTC spec isn't being complied with even if the current buggy SDP behaviour is fixed.
Is there any way for me to track it? Do I get notifications on updates to the bug (if yes then presumably it hasn't been looked at in 3 weeks, yay).
Thanks.
Eric
-
-
ebunyan last edited by
So basically we have no way of knowing if, when, or how they are going to fix it (they could ignore the WebRTC spec but comply with the specs for SDP and just not advertise codecs they can't actually receive, or they could add support for H264). It appears we have to advise against our customers using Opera until someone happens to notice if/when they fix a serious spec compliance bug.
-
-
ebunyan last edited by
We tested on Windows 7 and Linux, and in both cases it offered H264 in SDP for WebRTC but couldn't decode it.
