Juan Navarro

> About the error.log file, here is the details. > > ``` > [OpenH264] this = 0x0x7f3b46394680, Error: the pic_width_in_mbs exceeds the level limits! > ``` This message *Error: the...

Hi, does the Kurento logs show any suspicious Warning or Error message? does this issue happen randomly? You said it fails 1 in each 10 times... is there any difference...

Hi, thanks for the info. Please let me see your SDP Offer and Answers. For this, first configure [Kurento debug logs](https://doc-kurento.readthedocs.io/en/latest/user/configuration.html#debug-logging) to this value: ``` GST_DEBUG="3,Kurento*:4,kms*:4,sdp*:4,webrtc*:4,*rtpendpoint:4,rtp*handler:4,rtpsynchronizer:4,agnosticbin:4,KurentoMediaElementImpl:5,agnosticbin*:5,kmssdpsession:5,webrtcendpoint:5,kmswebrtcsession:5,kmsiceniceagent:5" ``` Then restart Kurento,...

I'm not sure if the previous message got a wrong formatting. Use this value for the debug verbosity: ``` GST_DEBUG="3,Kurento*:4,kms*:4,sdp*:4,webrtc*:4,*rtpendpoint:4,rtp*handler:4,rtpsynchronizer:4,agnosticbin:4,KurentoMediaElementImpl:5,agnosticbin*:5,kmssdpsession:5,webrtcendpoint:5,kmswebrtcsession:5,kmsiceniceagent:5" ```

I see this in the logs: 2021-01-15T06:36:29 Kurento Media Server started 2021-01-15T06:41:35 Process SDP Offer 1 MediaFlowOutStateChange: FLOWING, type: 'audio' MediaFlowInStateChange: FLOWING, type: 'audio' MediaFlowInStateChange: FLOWING, type: 'audio' MediaFlowOutStateChange: FLOWING,...

could you please check the Kurento debug logs to see if there is any related error or warning?

I'm tagging as "not a bug" because this seems like a configuration or signaling issue in the application, not a bug in Kurento

Actually I would like to get rid of all dependencies of KurentoForks, but not sure it it's possible right now. It would be a good change, removing all forks, to...

We focus more on the Java client because that's what is used by OpenVidu. So the JS client is driven by community contributions. I will review your proposal to see...

When Kurento 6.7.1 was released, Safari 14 didn't exist so it wasn't testef d against it. Try with latest versions to see if it works better