home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Support
General Support
HDHomeRun Prime Tuner Locked
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="georgius" data-source="post: 1065983" data-attributes="member: 107951"><p>Hi mm,</p><p></p><p>I carefully read Wireshark log from <a href="https://forum.team-mediaportal.com/threads/hdhomerun-prime-tuner-locked.124328/page-3#post-1062703" target="_blank">post #26</a> and it seems that remote server (HDHomeRun device?) not correctly handles RTSP TEARDOWN request. By Wireshark log (packet 15989, TEARDOWN request) is sent TEARDOWN request to remote server. Remote server can response with sender report goodbye packet, but must response with correct RTSP response (like response on OPTIONS, DESCRIBE, SETUP and PLAY requests). As I can see, the server didn't send any response (except TCP reset which means that connection was reset (e.g. closed socket on remote server)). Also remote server didn't accept any receiver report packets (from client port 50737 to server port 5005) - all returned with ICMP destination unreachable (e.g. packets 948, 949; 1749, 1751; ...; 16000, 16001). It seems that remote server closes main RTSP connection (on port 554) and never opens control channel port (server port 5005). But data channel port is not closed and data are transmitted.So, from my point of view, server has at least bad RTSP protocol implementation.</p></blockquote><p></p>
[QUOTE="georgius, post: 1065983, member: 107951"] Hi mm, I carefully read Wireshark log from [URL='https://forum.team-mediaportal.com/threads/hdhomerun-prime-tuner-locked.124328/page-3#post-1062703']post #26[/URL] and it seems that remote server (HDHomeRun device?) not correctly handles RTSP TEARDOWN request. By Wireshark log (packet 15989, TEARDOWN request) is sent TEARDOWN request to remote server. Remote server can response with sender report goodbye packet, but must response with correct RTSP response (like response on OPTIONS, DESCRIBE, SETUP and PLAY requests). As I can see, the server didn't send any response (except TCP reset which means that connection was reset (e.g. closed socket on remote server)). Also remote server didn't accept any receiver report packets (from client port 50737 to server port 5005) - all returned with ICMP destination unreachable (e.g. packets 948, 949; 1749, 1751; ...; 16000, 16001). It seems that remote server closes main RTSP connection (on port 554) and never opens control channel port (server port 5005). But data channel port is not closed and data are transmitted.So, from my point of view, server has at least bad RTSP protocol implementation. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
General Support
HDHomeRun Prime Tuner Locked
Contact us
RSS
Top
Bottom