same problem here, and rolling back to old default ssl allows me to connect, but import button not working as certificate is detected as invalid...so im stuck. the new certificate is working ok for the https part, but not for flashphoner...
resolution is 320*240, i've limited the bitrate server side according to the tuning page recommandations, not sure about transcoding but probably no transcoding
Hello, what would be the buffer parameters to play with to try to reduce latency at start. As finally i noticed that there is 4/5 seconds latency just when a stream start to be published until it start playing, but afterward the latency is not more than 1 second. So i think proper workaround...
so i can confirm that all caracters with accent (typically in french language) cause this utf8 error in logs, and messages are not sent. any workaround before a futur fix ?
i have been able to reproduce the pb in the video chat example. if only one person connected, no error when sending "à". if 2 persons connected, "à" dont reach destintion and there is error in logs
ok i can confirm the error: if the following text is sent, message dont reach clients and there is the error:
the same message without accents reach clients and dont generate this error in logs
Hello, i have a stranger behavior with some messages send t the chat in conference.
It seems that there is a related error message in logs:
so it looks like there is an utf8 issue, but i really dont understand how it can happen. any clue ?
will check. by the way which build is latest version. here is what i had this morning:
service webcallserver update
>>> You have latest version: 5.2.183
im using webrtc example. iwas comparing performance of the previous version of the same app, which was relying on rtmp with wowza. im publishing in 320*240, with max bandwith set to 1000 as specified in the tuning instructions. i have 64gb of ram so my wcs-core look like -Xmx32g -Xms32g. not...
Hello
i'm uysing wcs mainly for my conference app, based on most features from your conference demo. However, while im using the same "mecanism" i was using for the same app when i was still using wowza, the UI is very slow and unresponsive, particularly for everything related to start...
looks like it is happening when a user join the room, more precisely when issuing rest request to retrieve all strams:
edit: after trying to narrow the source of this error, it appears its not this...but it happens during the connection/joiningRoom process...been trying to call manually all...
Hello, had to refrtesh my ssl certificate after expiration. using letsencrypt. using the same cert im using for apache on the server, and get this error:
any clue ?
thanks