Reply to thread

Message

<blockquote data-quote="georgius" data-source="post: 1112759" data-attributes="member: 107951">It's feature, not bug. But it's little bit complicated. Filter sends OPTIONS or GET_PARAMETER request to remote server in regular intervals (half of timeout specified by server (default timeout value is 60 seconds, so each 30 seconds is sent request)). Each request has its own timeout (default is 20 seconds). And now what happend: filter sent OPTIONS request with timeout 20 seconds at 29-11-2014 12:19:21.994 (so timeout will occure at 29-11-2014 12:19:41.994). Problem with received text &quot;i'm not dead yet&quot; occured at 29-11-2014 12:19:25.098. So, filter need to wait at least 16.896 seconds to issue new request. At 2014-11-29 12:19:38,673 was pressed stop in MP - 3.321 seconds before filter OPTIONS request timeout. After that filter closed and opened new connection, but in that time it was irrelevant.It will be great when specifying filter RTSP url is url created with reasonable parameters, especially for timeouts - as I saw in logs, 500 ms is sufficient value. This is also little bit complicated, because we have standard MP IPTV filter and this new one. In theory is also possible to separate filter IPTV and OnlineVideos settings, but I don't have any idea about reasonable values (except of UDP protocol, which I'm using).</blockquote>

[QUOTE="georgius, post: 1112759, member: 107951"] It's feature, not bug. But it's little bit complicated. Filter sends OPTIONS or GET_PARAMETER request to remote server in regular intervals (half of timeout specified by server (default timeout value is 60 seconds, so each 30 seconds is sent request)). Each request has its own timeout (default is 20 seconds). And now what happend: filter sent OPTIONS request with timeout 20 seconds at 29-11-2014 12:19:21.994 (so timeout will occure at 29-11-2014 12:19:41.994). Problem with received text "i'm not dead yet" occured at 29-11-2014 12:19:25.098. So, filter need to wait at least 16.896 seconds to issue new request. At 2014-11-29 12:19:38,673 was pressed stop in MP - 3.321 seconds before filter OPTIONS request timeout. After that filter closed and opened new connection, but in that time it was irrelevant. It will be great when specifying filter RTSP url is url created with reasonable parameters, especially for timeouts - as I saw in logs, 500 ms is sufficient value. This is also little bit complicated, because we have standard MP IPTV filter and this new one. In theory is also possible to separate filter IPTV and OnlineVideos settings, but I don't have any idea about reasonable values (except of UDP protocol, which I'm using). [/QUOTE]

Verification