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
Products
MPTvClient (stand alone TV client)
[Announce] MPTvClient V1.2.5 (20.12.2007) II
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="FransO" data-source="post: 285892" data-attributes="member: 79686"><p>Using RTP over TCP requires an acknowledgement of each packet. I tested with the client on the TVServer and that went all right. Put some switches and a wireless accesspoint between server and client and network latency becomes a problem and reception will be choppy yes.</p><p></p><p>I used Ms Netwerk Monitor to see what went on when the 45 second freeze occurred with RTP over UDP. The answer is: Not much. After an RTSP setup there are a lot of UDP packets and after the last UDP packet just two TCP packets: A message from the server and a response from the client. After that no more traffic attributable to RSTP at all.</p><p></p><p>Below some excerpts from the network trace, .32 is the client and .33 is the tvserver, the first IP address is the source, the second the destination. The second column is the time offset in microseconds.</p><p></p><p>302 2.971.170 192.168.2.32 192.168.2.33 TCP TCP: Flags=.S......, SrcPort=49419, DstPort=RTSP(554), Len=0, Seq=3105363208, Ack=0, Win=8192 (scale factor not found)</p><p>303 2.971.170 192.168.2.33 192.168.2.32 TCP TCP: Flags=.S..A..., SrcPort=RTSP(554), DstPort=49419, Len=0, Seq=1280543924, Ack=3105363209, Win=8192 (scale factor not found)</p><p>304 2.972.170 192.168.2.32 192.168.2.33 TCP TCP: Flags=....A..., SrcPort=49419, DstPort=RTSP(554), Len=0, Seq=3105363209, Ack=1280543925, Win=4380 (scale factor not found)</p><p>305 2.973.170 192.168.2.32 192.168.2.33 RTSP RTSP: REQUEST, OPTIONS rtsp://OADT3/stream1.0</p><p>306 2.973.170 192.168.2.33 192.168.2.32 RTSP RTSP: RESPONSE, RTSP/1.0, Status Code = 200 - OK</p><p>309 2.977.171 192.168.2.33 192.168.2.32 UDP UDP: SrcPort = Linklocal Multicast Name Resolution(5355), DstPort = 51864, Length = 52</p><p>310 2.980.171 192.168.2.32 192.168.2.33 RTSP RTSP: REQUEST, DESCRIBE rtsp://OADT3/stream1.0</p><p>315 3.014.173 192.168.2.33 192.168.2.32 SDP SDP: Session Name=Session streamed by "MediaPortal Tv Server v1.0", Version=0</p><p>316 3.023.173 192.168.2.32 192.168.2.33 RTSP RTSP: REQUEST, SETUP rtsp://192.168.2.33/stream1.0/track1</p><p>318 3.045.174 192.168.2.33 192.168.2.32 RTSP RTSP: RESPONSE, RTSP/1.0, Status Code = 200 - OK</p><p>319 3.047.175 192.168.2.32 192.168.2.33 RTSP RTSP: REQUEST, PLAY rtsp://192.168.2.33/stream1.0/</p><p>320 3.065.176 192.168.2.33 192.168.2.32 RTSP RTSP: RESPONSE, RTSP/1.0, Status Code = 200 - OK</p><p>321 3.065.176 192.168.2.33 192.168.2.32 UDP UDP: SrcPort = 6970, DstPort = 51866, Length = 1336</p><p>-</p><p>-</p><p>-A lot of UDP packets in between here</p><p>-</p><p>- </p><p>40913 47.992.745 192.168.2.33 192.168.2.32 UDP UDP: SrcPort = 6970, DstPort = 51866, Length = 1336</p><p>40914 47.994.745 192.168.2.33 192.168.2.32 TCP TCP: Flags=F...A..., SrcPort=RTSP(554), DstPort=49419, Len=0, Seq=1280544933, Ack=3105363815, Win=254 (scale factor not found)</p><p>40915 47.996.746 192.168.2.32 192.168.2.33 TCP TCP: Flags=....A..., SrcPort=49419, DstPort=RTSP(554), Len=0, Seq=3105363815, Ack=1280544934, Win=4128 (scale factor not found)</p><p></p><p>The contents of those last two TCP packets are:</p><p></p><p>From the server to the client:</p><p> Frame: </p><p>+ Ethernet: Etype = Internet IP (IPv4)</p><p>+ Ipv4: Next Protocol = TCP, Packet ID = 19365, Total IP Length = 40</p><p>- Tcp: Flags=F...A..., SrcPort=RTSP(554), DstPort=49419, Len=0, Seq=1280544933, Ack=3105363815, Win=254 (scale factor not found)</p><p> SrcPort: RTSP(554)</p><p> DstPort: 49419</p><p> SequenceNumber: 1280544933 (0x4C5390A5)</p><p> AcknowledgementNumber: 3105363815 (0xB9181767)</p><p> + DataOffset: 80 (0x50)</p><p> - Flags: F...A...</p><p> CWR: (0.......) CWR not significant</p><p> ECE: (.0......) ECN-Echo not significant</p><p> Urgent: (..0.....) Not Urgent Data</p><p> Ack: (...1....) Acknowledgement field significant</p><p> Push: (....0...) No Push Function</p><p> Reset: (.....0..) No Reset</p><p> Syn: (......0.) Not Synchronize sequence numbers</p><p> Fin: (.......1) End of data</p><p> Window: 254 (scale factor not found)</p><p> Checksum: 34220 (0x85AC)</p><p> UrgentPointer: 0 (0x0)</p><p></p><p>response from the client:</p><p> Frame: </p><p>+ Ethernet: Etype = Internet IP (IPv4)</p><p>+ Ipv4: Next Protocol = TCP, Packet ID = 4981, Total IP Length = 40</p><p>- Tcp: Flags=....A..., SrcPort=49419, DstPort=RTSP(554), Len=0, Seq=3105363815, Ack=1280544934, Win=4128 (scale factor not found)</p><p> SrcPort: 49419</p><p> DstPort: RTSP(554)</p><p> SequenceNumber: 3105363815 (0xB9181767)</p><p> AcknowledgementNumber: 1280544934 (0x4C5390A6)</p><p> + DataOffset: 80 (0x50)</p><p> - Flags: ....A...</p><p> CWR: (0.......) CWR not significant</p><p> ECE: (.0......) ECN-Echo not significant</p><p> Urgent: (..0.....) Not Urgent Data</p><p> Ack: (...1....) Acknowledgement field significant</p><p> Push: (....0...) No Push Function</p><p> Reset: (.....0..) No Reset</p><p> Syn: (......0.) Not Synchronize sequence numbers</p><p> Fin: (.......0) Not End of data</p><p> Window: 4128 (scale factor not found)</p><p> Checksum: 43379 (0xA973)</p><p> UrgentPointer: 0 (0x0)</p><p></p><p>I don't know enough of the protocols to be sure, but it looks like the server telling the client: That's all your gonna get.</p></blockquote><p></p>
[QUOTE="FransO, post: 285892, member: 79686"] Using RTP over TCP requires an acknowledgement of each packet. I tested with the client on the TVServer and that went all right. Put some switches and a wireless accesspoint between server and client and network latency becomes a problem and reception will be choppy yes. I used Ms Netwerk Monitor to see what went on when the 45 second freeze occurred with RTP over UDP. The answer is: Not much. After an RTSP setup there are a lot of UDP packets and after the last UDP packet just two TCP packets: A message from the server and a response from the client. After that no more traffic attributable to RSTP at all. Below some excerpts from the network trace, .32 is the client and .33 is the tvserver, the first IP address is the source, the second the destination. The second column is the time offset in microseconds. 302 2.971.170 192.168.2.32 192.168.2.33 TCP TCP: Flags=.S......, SrcPort=49419, DstPort=RTSP(554), Len=0, Seq=3105363208, Ack=0, Win=8192 (scale factor not found) 303 2.971.170 192.168.2.33 192.168.2.32 TCP TCP: Flags=.S..A..., SrcPort=RTSP(554), DstPort=49419, Len=0, Seq=1280543924, Ack=3105363209, Win=8192 (scale factor not found) 304 2.972.170 192.168.2.32 192.168.2.33 TCP TCP: Flags=....A..., SrcPort=49419, DstPort=RTSP(554), Len=0, Seq=3105363209, Ack=1280543925, Win=4380 (scale factor not found) 305 2.973.170 192.168.2.32 192.168.2.33 RTSP RTSP: REQUEST, OPTIONS rtsp://OADT3/stream1.0 306 2.973.170 192.168.2.33 192.168.2.32 RTSP RTSP: RESPONSE, RTSP/1.0, Status Code = 200 - OK 309 2.977.171 192.168.2.33 192.168.2.32 UDP UDP: SrcPort = Linklocal Multicast Name Resolution(5355), DstPort = 51864, Length = 52 310 2.980.171 192.168.2.32 192.168.2.33 RTSP RTSP: REQUEST, DESCRIBE rtsp://OADT3/stream1.0 315 3.014.173 192.168.2.33 192.168.2.32 SDP SDP: Session Name=Session streamed by "MediaPortal Tv Server v1.0", Version=0 316 3.023.173 192.168.2.32 192.168.2.33 RTSP RTSP: REQUEST, SETUP rtsp://192.168.2.33/stream1.0/track1 318 3.045.174 192.168.2.33 192.168.2.32 RTSP RTSP: RESPONSE, RTSP/1.0, Status Code = 200 - OK 319 3.047.175 192.168.2.32 192.168.2.33 RTSP RTSP: REQUEST, PLAY rtsp://192.168.2.33/stream1.0/ 320 3.065.176 192.168.2.33 192.168.2.32 RTSP RTSP: RESPONSE, RTSP/1.0, Status Code = 200 - OK 321 3.065.176 192.168.2.33 192.168.2.32 UDP UDP: SrcPort = 6970, DstPort = 51866, Length = 1336 - - -A lot of UDP packets in between here - - 40913 47.992.745 192.168.2.33 192.168.2.32 UDP UDP: SrcPort = 6970, DstPort = 51866, Length = 1336 40914 47.994.745 192.168.2.33 192.168.2.32 TCP TCP: Flags=F...A..., SrcPort=RTSP(554), DstPort=49419, Len=0, Seq=1280544933, Ack=3105363815, Win=254 (scale factor not found) 40915 47.996.746 192.168.2.32 192.168.2.33 TCP TCP: Flags=....A..., SrcPort=49419, DstPort=RTSP(554), Len=0, Seq=3105363815, Ack=1280544934, Win=4128 (scale factor not found) The contents of those last two TCP packets are: From the server to the client: Frame: + Ethernet: Etype = Internet IP (IPv4) + Ipv4: Next Protocol = TCP, Packet ID = 19365, Total IP Length = 40 - Tcp: Flags=F...A..., SrcPort=RTSP(554), DstPort=49419, Len=0, Seq=1280544933, Ack=3105363815, Win=254 (scale factor not found) SrcPort: RTSP(554) DstPort: 49419 SequenceNumber: 1280544933 (0x4C5390A5) AcknowledgementNumber: 3105363815 (0xB9181767) + DataOffset: 80 (0x50) - Flags: F...A... CWR: (0.......) CWR not significant ECE: (.0......) ECN-Echo not significant Urgent: (..0.....) Not Urgent Data Ack: (...1....) Acknowledgement field significant Push: (....0...) No Push Function Reset: (.....0..) No Reset Syn: (......0.) Not Synchronize sequence numbers Fin: (.......1) End of data Window: 254 (scale factor not found) Checksum: 34220 (0x85AC) UrgentPointer: 0 (0x0) response from the client: Frame: + Ethernet: Etype = Internet IP (IPv4) + Ipv4: Next Protocol = TCP, Packet ID = 4981, Total IP Length = 40 - Tcp: Flags=....A..., SrcPort=49419, DstPort=RTSP(554), Len=0, Seq=3105363815, Ack=1280544934, Win=4128 (scale factor not found) SrcPort: 49419 DstPort: RTSP(554) SequenceNumber: 3105363815 (0xB9181767) AcknowledgementNumber: 1280544934 (0x4C5390A6) + DataOffset: 80 (0x50) - Flags: ....A... CWR: (0.......) CWR not significant ECE: (.0......) ECN-Echo not significant Urgent: (..0.....) Not Urgent Data Ack: (...1....) Acknowledgement field significant Push: (....0...) No Push Function Reset: (.....0..) No Reset Syn: (......0.) Not Synchronize sequence numbers Fin: (.......0) Not End of data Window: 4128 (scale factor not found) Checksum: 43379 (0xA973) UrgentPointer: 0 (0x0) I don't know enough of the protocols to be sure, but it looks like the server telling the client: That's all your gonna get. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
Products
MPTvClient (stand alone TV client)
[Announce] MPTvClient V1.2.5 (20.12.2007) II
Contact us
RSS
Top
Bottom