![]() ![]() Safari loves to go out of its way and is very picky with this topic we have observed that sometimes (specifically, on mobile devices with iOS) it won't allow the demo to run, because it rejects using the WebSocket channel that the demo requires to "speak" with the server application. Pushing on "Stop" will terminate both videos and the placeholders will come back to their initial state, with the WebRTC logo.Īs you will notice, the only actual difference between both demos when running on Chrome (and Firefox) is that the user needs to accept a security exception at the beginning, but afterwards everything runs fine. After a while, the remote video arrives from Kurento, and it shows up in the remote video placeholder.Ħ. ![]() Meanwhile, the remote video keeps showing a spinner.ĥ. As soon as permission has been granted, the local video shows up. The browser asks for permission to access the video camera and the microphone. Pushing on "Start" initiates the process. In narrower screens, they will probably rearrange vertically.ģ. Currently, both of them show the WebRTC logo. After loading, there are two video placeholders: the left one is for the local video, and the right one is for the remote video. The demo loads properly, while first requires to accept a security exception due to a misconfigured HTTPS certificate.Ģ. In order to establish what is the expected behavior, I'm going to write a detailed step-by-step description of what happens when you run either of these demos in Chrome, our reference WebRTC browser:ġ. ![]() We want to see what is the effect of this on Safari. > This is exactly the same demo as the previous one, but here the HTTPS certificate is misconfigured. > Here you'll find the Hello-World Kurento demo, which simply fetches the local video and brings it back in loopback. There are two demo sites that have been prepared for this: And for that, we'd like to ask the greater community for a bit of help, as the variety of Apple devices that we'll be able to reach is much higher. After locating all points where it seems that Kurento and its support libraries needed changes, we're now ready to test it. We at Kurento are working on all the necessary changes to bring compatibility with the WebRTC implementation of Safari in a robust and reliable form. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |