Hi I have been testing Flashphoner in my UAT server across various browsers and devices to confirm that they successfully stream and save the video to the server. All browsers have been working except for Safari (12.1.1) on Mac (Mojave 10.14.5). I've been getting two different errors and both errors don't always occur (Occurs about 10% of the time). Issue 1: No Video Saved This one seems to happen on my UAT site but not on the Flashphoner demo page. Flashphoner establishes a session, creates and starts publishing a stream, returning a status of "Publishing", and the local video is displaying correctly. When stopping the stream I get a status of "Unpublished" and therefore assume that the video has successfully been published but when I try to find the video on the server it isn't there. I've gone over the logs for it and found a couple of error logs + inconsistent logs: Code: 23:37:47,025 ERROR H264AccessUnit - STUN-UDP-pool-38-thread-103 Failed to parse H264 bitstream, Failed to parse H264 frame, no packets In "issue1-client-flashhphoner.txt" log, line 59. Code: 23:38:56,905 INFO WSClient - WSClientsKeepaliveThread-72 Close connection for channel [id: 0x548bb1e4, /***.***.***.***:51998 => /10.0.0.140:443] with status code: 1000 ; reason: Disconnected by keep alive In "issue1-server-flashphoner.txt" log, line 628 (which is different from the usual "Disconnected by closed channel" messages). Issue 2: Corrupted Video Duration This one was easier to recreate on the Flashphoner demo page but also didn't happen all the time. Again Flashphoner successfully goes through establishing a session and publishing then "Unpublished" the stream, the difference being the this time the video can be found in the media server. The issue this time is that it saved with a duration of ~600,000 hours for a video that roughly went for 10 seconds. Again I've gone over the logs for it and found this: Code: 02:07:34,086 ERROR RtpVideoPlayer - STUN-UDP-pool-38-thread-105 Full buffer and no synchronization, force it In "issue2-client-flashphoner.txt" log, line 59. Some additional configurations made to the server are: Setting the WSS port to be on 443 instead of 8443. Setting the stream_record_policy to use the stream name. Any help on either of these issues will be greatly appreciated.