Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 1066286" data-attributes="member: 82144">Hello georgiusThe server doesn't support RTCP. AFAIK this is true for all CableCARD tuners.What Jason said was that the server closed the connection - sent a TCP FIN in packet 4563 which was acknowledged at packet 4564. So, live555 was sending the TEARDOWN on a closed connection. The reset means that the client should open a new connection... but it doesn't do that. The way I read the live555 RTSPClient.cpp code it seems that live555 uses a single connection for communication with the server. It doesn't actually handle the closed connection/socket. There is a function to close the current connection (resetTCPSockets()). If this were called, it would trigger a new connection to be opened to send the next message. Normally that function is only called in error conditions and in the destructor.So, this is why I think we are at fault. We should detect that the server has closed the connection and open a new connection.Do you think your new filter would handle this scenario properly?mm</blockquote>

[QUOTE="mm1352000, post: 1066286, member: 82144"] Hello georgius The server doesn't support RTCP. AFAIK this is true for all CableCARD tuners. What Jason said was that the server closed the connection - sent a TCP FIN in packet 4563 which was acknowledged at packet 4564. So, live555 was sending the TEARDOWN on a closed connection. The reset means that the client should open a new connection... but it doesn't do that. The way I read the live555 RTSPClient.cpp code it seems that live555 uses a single connection for communication with the server. It doesn't actually handle the closed connection/socket. There is a function to close the current connection (resetTCPSockets()). If this were called, it would trigger a new connection to be opened to send the next message. Normally that function is only called in error conditions and in the destructor. So, this is why I think we are at fault. We should detect that the server has closed the connection and open a new connection. Do you think your new filter would handle this scenario properly? mm [/QUOTE]

Verification