Recent content by SLM

  1. S

    Change in updated flashphoner.js causes error

    Since implementing version 2.0.198 of the javascript Flashphoner Web SDK we received "Browser is not defined" javascript errors. It seems that pages/scripts based on this version need to have an extra declaration added to it : var Browser = Flashphoner.Browser; After that, scripts work again...
  2. S

    Samsung browser

    The AppRTC test also doesn't work on Samsung Internet or Chrome but does work in Firefox. The TrickleICE test on https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/ also doesn't work on Samsung Internet or Chrome but again, it does work on Firefox. Switching to TCP has no...
  3. S

    Samsung browser

    Yes I said initially it was only on Samsung Internet browser. This was because I wanted to check if a clean Samsung A22 produced these problems or our customers just had some apps installed that would block certain traffic. This is not the case. The Samsung A22 produces the same problem on the...
  4. S

    Samsung browser

    Hi, I've collected the logs as requested. The total file size is more than 30 MB so I could not use the form. I've sent it via Wetransfer. Tests: 12:14 PM : Samsung Internet browser v14.2.3.14 tested 2-way stream demo. Result publish failed by ICE timeout. 12:18 PM : Chrome browser...
  5. S

    Samsung browser

    It's reproduced on demo.flashphoner as well as our own servers. There are no vpn clients or adblockers installed. As I've said, it's a newly bought, fresh out of the box Samsung A22 5G (SM-A226B/DSN) with the default Chrome like Samsung internet browser version 14.0.1.62. We did not install...
  6. S

    Samsung browser

    This is done on Wifi without any connection problems. It also happens on 3g/4g. No firewall blocking.
  7. S

    Samsung browser

    You were correct. The publish action succeeded but after several seconds went to 'Failed by ICE Timeout'. Tested just now.
  8. S

    Samsung browser

    The demo doesn't work on this new out of the box Samsung A22 5G (SM-A226B/DSN) with SamsungBrowser. It does work on other Android phones and iPhones. Samsung browser version 14.0.1.62 Connect: Ok Publish stream 8ca9 at 12:07 Brussels time: Ok Available? : unavailable / stream not found Play...
  9. S

    Samsung browser

    The built in Chrome mobile browser on Samsung phones will not display a stream and fails with the following error: "Failed by ICE timeout". Switching udp to tcp doesn't help and results in the same error. Regular Google Play store Chrome or Apple iOS Safari does not have this issue. Useragent...
  10. S

    UDP / TCP transport fallback

    Hi, Thank you for your reply. It's not so much the publishing streams that experience this. The publishers do not use a vpn. It's the people that play the streams that sometimes use vpn's and some of those limit or block UDP traffic. Does this result in the same "Failed by ICE timeout" ? Some...
  11. S

    UDP / TCP transport fallback

    It seems that certain VPN providers do not support UDP streaming or limit its bandwidth to levels that basically make it unusable for streaming. Is it possible to detect this and to automatically switch to TCP server side or to detect it client side using the javascript API and use an event /...
  12. S

    syntax error when updating webcallserver

    [ec2-user@ip-xxx-xx-xx-xx tools]$ sudo service webcallserver update >>> New version available: 5.2.971 >>> Your version: 5.2.927 >>> Version 5.2.971 is available, try to update >>> You have to stop FlashphonerWebCallServer before update. >>> Stop now [yes/no] ? yes FlashphonerWebCallServer...
  13. S

    StreamStatusEvent 'failed' after 'playing'

    When a visitor refreshes his browser the streaming session will be reestablished and streaming will continue. However, in our logs we get a StreamStatusEvent with status "Playing" before the StreamStatusEvent with status "failed" of the previous session. Is this a bug or intentional? On both...
  14. S

    Publish not working on Firefox after update to FlashphonerWebCallServer-5.2.859

    It's 83.0. No problem updating my own browser, but it would be better if the bug was fixed so we don't have to force everyone to update their browser. /Edit: Strangely enough, I can now publish in FF83 (did not update yet), so I suspect it's a combination of factors.
Top