close actual rtmp connection after sending publish error

close actual rtmp connection after sending publish error

Support ForumCategory: Installation and Basic Operationclose actual rtmp connection after sending publish error
rajkosto asked 9 years ago
Sometimes the encoder client will try to publish a stream after reconnect and receive Badname, after this, it will just wait forever since the rtmp connection is still open. There’s no way in the API to close actual connections, only shutdownStream, but the stream has expired way way long ago, while the client is just waiting there for connection close. Is there a way to enforce a idle-rtmp-connection timeout after a specified amount of seconds ? Or somehow explicitly close the connection to the recipient of Badname and other such errors ?



Offcanvas

Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.