Search results

  1. S

    AWS EC2 Flashphoner image Yum update failed

    Thanks Max. Since it's not installed by Flashphoner, I've removed the okay-release package and now yum continues as expected.
  2. S

    AWS EC2 Flashphoner image Yum update failed

    Just launched an Amazon EC2 AMI with Flashphoner license. It started and is running but when trying to sudo yum update the instance, I get the following error: Transaction Summary...
  3. S

    WCS 5.2.1431 Firefox 320x240 H264 stream not working

    Hi Max, Thank you for the fix. It works great.
  4. S

    WCS 5.2.1431 Firefox 320x240 H264 stream not working

    use_strict_jitter_buffer=true jitter_buffer_capacity=30 Unfortunately this also makes no difference. What is the consequence of forcing publish to VP8 ? Doesn't that mean a lot of transcoding?
  5. S

    WCS 5.2.1431 Firefox 320x240 H264 stream not working

    The two settings did not help. The issue remains the same.
  6. S

    WCS 5.2.1431 Firefox 320x240 H264 stream not working

    Sorry about that, I already wondered why the log was so small. Forgot to include the pcap, which I sent via Wetransfer just now. Later today I will test the two settings mentioned above.
  7. S

    WCS 5.2.1431 Firefox 320x240 H264 stream not working

    Also note that : 1. this issue does NOT happen on WCS 5.2.1299 (publishes and streams correctly at 320x240 H264 in FF) 2. publishing a 320x240 H264 stream on a server with WCS 5.2.1299 plays fine in the demo player in FF on a server with WCS 5.2.1431 3. the same issue happens with an external...
  8. S

    WCS 5.2.1431 Firefox 320x240 H264 stream not working

    I've sent the report tar. Tested: FF publish and play (not displaying stream) with twowaystreaming demo FF publish and play 640x480 with Media Devices demo (works fine) Chrome publish and play with twowaystreaming demo (works fine) and display same stream in FF (works fine)
  9. S

    WCS 5.2.1431 Firefox 320x240 H264 stream not working

    Video stats Codec: H264 Codec Rate: 90000 Bytes Sent: 717022 Packets Sent: 1002 Fir Count: 0 Nack Count: 0 Pli Count: 6 Height: 240 Width: 320 Bitrate: 389352 Audio stats Codec: opus Codec Rate: 48000 Bytes Sent: 37022 Packets Sent: 914 Nack Count: 0 Bitrate: 16888 ---...
  10. S

    WCS 5.2.1431 Firefox 320x240 H264 stream not working

    Situation is reproduced on your demo server. Tested FF at 13:02 Amsterdam time, stream 6f1d - FAIL Tested Chrome at 13:04, stream d1db - OK Played stream d1fb on FF - OK Tested FF with Media Devices 640x480 at 13:06, stream eff6 - OK Tested FF with Media Devices 320x240 at 13:08 stream 9d9a -...
  11. S

    WCS 5.2.1431 Firefox 320x240 H264 stream not working

    Just updated WCS to 5.2.1431 and tested it with the demo tools. Using Firefox 105.0.2 tried the Two way streaming demo. It fails although without errors. Publishing seems to work, clicking on Available reports that the stream is indeed available, and it also said 'Playing', but no stream is...
  12. S

    Ghost session after WCS 5.2.1109 update

    Unfortunately, this issue is back in FF version 1193.
  13. S

    UBlock on chrome trigger Failed by ICE keep alive

    Hi Max. Can you tell me what the cause is of the error "Distributor stopped" ? We received the following error in the API: [mediaSessionId] => 501c5b60-9928-11ec-860f-5f8131bcfea3 [name] => 9911d6d7a99541b041aea2b4d672c3ed [published] => [hasVideo] => [hasAudio] => 1...
  14. S

    missing videoCodec item in json

    Sometimes there's no videoCodec item in the returned json of rest-api/stream/find, although there is videostream. As far as I can see, this only happens when the videostream is 'pending', but I'm not sure. It would be preferable however if the videoCodec item was still listed but empty or set...
  15. S

    Flashphoner.init() multiple times

    See also this topic regarding Android (Samsung) device and ICE timeout: https://forum.flashphoner.com/threads/samsung-browser.13825/ This problem is still not fixed. Chrome is increasingly producing more errors with Flashphoner while Firefox does not. We used to advise people to use Chrome for...
  16. S

    Ghost session after WCS 5.2.1109 update

    Thanks Max
  17. S

    Ghost session after WCS 5.2.1109 update

    After updating to WCS 5.2.1109 and checking the demo's in the admin console to see if everything works, a ghost session is left on the server which I cannot kill with /rest-api/connection/terminate Session info is limited to the following: { "appKey": "defaultApp", "sessionId"...
  18. S

    systemctl restart webcallserver hangs b/c of chown process

    Note: After using sudo rm -rf /usr/local/FlashphonerWebCallServer/logs/* and restarting wcs, the admin console password of WCS gets changed
  19. 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...
Top