Hyunjun Jang

@JonasPrimbs Thank you for your opinion! As you mentioned, WebRTC signalling can be implemented in many other ways besides WebSocket, and the reason why we used WebSocket as a signalling...

@dva-re I just found a way to reproduce the hang problem. Thank you very much for your help, and I will tell you again when the bug is fixed!

@dva-re I fixed this problem and will release a new version when the stress test is completed. https://github.com/AirenSoft/OvenMediaEngine/commit/fd74fec49b2e5dd16bb868a131800714b72c9f40

Hi, @veramarvin We have a plan to implement this feature. The feature is not just restreaming, it's mainly used to make sure that the stream is being ingested properly. So,...

Nothing has been updated yet. We don't have time to implement the RTMP Pull feature right now while developing other features.

@naanlizard I agree that restarting daemon for TLS certificate replacement is not a good idea. OME uses ```SIGHUP``` signal for config update (now only supports reloading ```logger.xml```), and I will...

@lassos For TLS to work, `````` should be specified as ```xxx.com```, not ```*```. The URL values listed in ```CrossDomains``` must be the URL of the page calling the OME API....

@lassos I checked the URL you posted, and the browser is not sending the ```Origin``` header in request header. (```Origin``` header must be present for CORS processing in OME.) Is...

@lassos I just found the path to this problem! If there is an ```Authorization``` header when Chrome requests the API, Chrome will send a preflight request before the API request,...

@lassos Yes, you're right. You've already given me enough hints, but it took me a while to collect and understand the fragmented hints. And I wanted to find out the...