Re: [Wireshark-users] Wireshark doesnt recognize RTP packets when i decode
Could you possibly post a capture file that includes the RTSP signalling? We should be configuring the RTP stream with the dynamic payload type so that it can be displayed properly... On Wed, Mar 5, 2008 at 11:08 PM, Fabiana moreno [EMAIL PROTECTED] wrote: Well it's my final year project and i need to analyse the QoS parameters when streaming over wireless lan. I'm streaming an mpeg4 video from a server to my client (the last one is the one where wireshark is installed) So im trying to to capture all the packets im getting when streaming. My server supports rtcp/rtp and i think (correct me if im wrong) that the best way to analyse all these packets are to decode them to udp and then to rtp but im getting the problem mentioned before. But is there some way i can fix this? On 05/03/2008, Jaap Keuter [EMAIL PROTECTED] wrote: Well, I dont' really understand what you do, but the PT=unknown is from the fact that this packet type is dynamically assigned, negotiated between parties. If Wireshark doesn't see the negotiations, it can't make out which codec goes with PT 96. So yes, it can happen you see this. Thanx, Jaap Fabiana moreno wrote: hello!!! I'm streaming an mpeg4 video with darwin streamer server trhough my WLAN. I'm using wireshark to analyse the packets im receiving. I see TCP/RTSP packets but when i decode to UDP and then to RTP to anlyse it, wireshark shows the following in all the packets, here a sample: 340.253327192.168.123.100 http://192.168.123.100/ 192.168.123.101 http://192.168.123.101/RTPPT=Unknown (96), SSRC=0x4B6C00C, Seq=65416, Time=1531529067 is this what i suppose to see? any suggestions in how to analyse packets im receiving while streaming? please help!! im new ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users
Re: [Wireshark-users] Wireshark doesnt recognize RTP packets when i decode
If you dont want to open any attachment..then this is a sample of what i see when im capturing 94 0.695962192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 1356 bytes 95 0.696016192.168.123.101 192.168.123.100 TCP bcs-broker rtsp [ACK] Seq=1 Ack=69353 Win=51200 Len=0 96 0.706464192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 118 bytes 97 0.712661192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 1262 bytes 98 0.712699192.168.123.101 192.168.123.100 TCP bcs-broker rtsp [ACK] Seq=1 Ack=70741 Win=50853 Len=0 99 0.720359192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 1218 bytes 100 0.738111192.168.123.100 192.168.123.101 TCP [TCP Previous segment lost] Interleaved channel 0x00, 898 bytes 101 0.738162192.168.123.101 192.168.123.100 TCP bcs-broker rtsp [ACK] Seq=1 Ack=71963 Win=51200 Len=0 SLE=72979 SRE=73881 102 0.740297192.168.123.101 192.168.123.100 RTSP Continuation 103 0.742967192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 797 bytes 104 0.743031192.168.123.101 192.168.123.100 TCP [TCP Dup ACK 101#1] bcs-broker rtsp [ACK] Seq=1 Ack=71963 Win=51200 Len=0 SLE=72979 SRE=74682 105 0.756244192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 107 bytes 106 0.756283192.168.123.101 192.168.123.100 TCP [TCP Dup ACK 101#2] bcs-broker rtsp [ACK] Seq=1 Ack=71963 Win=51200 Len=0 SLE=72979 SRE=74793 107 0.768215192.168.123.100 192.168.123.101 TCP [TCP segment of a reassembled PDU] 108 0.768269192.168.123.101 192.168.123.100 TCP [TCP Dup ACK 101#3] bcs-broker rtsp [ACK] Seq=1 Ack=71963 Win=51200 Len=0 SLE=72979 SRE=76253 109 0.770532192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 1472 bytes 110 0.770548192.168.123.101 192.168.123.100 TCP [TCP Dup ACK 101#4] bcs-broker rtsp [ACK] Seq=1 Ack=71963 Win=51200 Len=0 SLE=72979 SRE=76269 111 0.777225192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 425 bytes 112 0.777280192.168.123.101 192.168.123.100 TCP [TCP Dup ACK 101#5] bcs-broker rtsp [ACK] Seq=1 Ack=71963 Win=51200 Len=0 SLE=72979 SRE=76698 113 0.797305192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 1420 bytes 114 0.797378192.168.123.101 192.168.123.100 TCP [TCP Dup ACK 101#6] bcs-broker rtsp [ACK] Seq=1 Ack=71963 Win=51200 Len=0 SLE=72979 SRE=78122 115 0.798265192.168.123.100 192.168.123.101 TCP rtsp slingshot [ACK] Seq=1 Ack=657 Win=652 Len=0 116 0.800536192.168.123.100 192.168.123.101 RTSP Reply: RTSP/1.0 200 OK 117 0.800567192.168.123.101 192.168.123.100 TCP [TCP Dup ACK 101#7] bcs-broker rtsp [ACK] Seq=1 Ack=71963 Win=51200 Len=0 SLE=72979 SRE=78261 118 0.815779192.168.123.100 192.168.123.101 TCP [TCP Fast Retransmission] Interleaved channel 0x00, 1012 bytes 119 0.815863192.168.123.101 192.168.123.100 TCP bcs-broker rtsp [ACK] Seq=1 Ack=78261 Win=51200 Len=0 120 0.828061192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 749 bytes 121 0.833133192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 971 bytes 122 0.833169192.168.123.101 192.168.123.100 TCP bcs-broker rtsp [ACK] Seq=1 Ack=79989 Win=51200 Len=0 On 06/03/2008, Fabiana moreno [EMAIL PROTECTED] wrote: That´s is the thing... i am not seeing any udp packets in my capture. just tcp and rtsp. Attached are the capture files(one .pcap and the other in text form) that includes RTSP signalling On 06/03/2008, Martin Mathieson [EMAIL PROTECTED] wrote: Could you possibly post a capture file that includes the RTSP signalling? We should be configuring the RTP stream with the dynamic payload type so that it can be displayed properly... On Wed, Mar 5, 2008 at 11:08 PM, Fabiana moreno [EMAIL PROTECTED] wrote: Well it's my final year project and i need to analyse the QoS parameters when streaming over wireless lan. I'm streaming an mpeg4 video from a server to my client (the last one is the one where wireshark is installed) So im trying to to capture all the packets im getting when streaming. My server supports rtcp/rtp and i think (correct me if im wrong) that the best way to analyse all these packets are to decode them to udp and then to rtp but im getting the problem mentioned before. But is there some way i can fix this? On 05/03/2008, Jaap Keuter [EMAIL PROTECTED] wrote: Well, I dont' really understand what you do, but the PT=unknown is from the fact that this packet
Re: [Wireshark-users] Wireshark doesnt recognize RTP packets when i decode
When we set up RTP streams (including passing information about dynamic payload types), we assume that its over UDP. It would be good to fix this. But in the meantime, can't you configure your RTSP server or client to use UDP/RTP transport for the media? On Thu, Mar 6, 2008 at 11:10 AM, Fabiana moreno [EMAIL PROTECTED] wrote: When i decode to udp and hence to rtp to analyse the jitter, and the delays then i get that problem of unknowns that i mentioned On 06/03/2008, Fabiana moreno [EMAIL PROTECTED] wrote: If you dont want to open any attachment..then this is a sample of what i see when im capturing 94 0.695962192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 1356 bytes 95 0.696016192.168.123.101 192.168.123.100 TCP bcs-broker rtsp [ACK] Seq=1 Ack=69353 Win=51200 Len=0 96 0.706464192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 118 bytes 97 0.712661192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 1262 bytes 98 0.712699192.168.123.101 192.168.123.100 TCP bcs-broker rtsp [ACK] Seq=1 Ack=70741 Win=50853 Len=0 99 0.720359192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 1218 bytes 100 0.738111192.168.123.100 192.168.123.101 TCP [TCP Previous segment lost] Interleaved channel 0x00, 898 bytes 101 0.738162192.168.123.101 192.168.123.100 TCP bcs-broker rtsp [ACK] Seq=1 Ack=71963 Win=51200 Len=0 SLE=72979 SRE=73881 102 0.740297192.168.123.101 192.168.123.100 RTSP Continuation 103 0.742967192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 797 bytes 104 0.743031192.168.123.101 192.168.123.100 TCP [TCP Dup ACK 101#1] bcs-broker rtsp [ACK] Seq=1 Ack=71963 Win=51200 Len=0 SLE=72979 SRE=74682 105 0.756244192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 107 bytes 106 0.756283192.168.123.101 192.168.123.100 TCP [TCP Dup ACK 101#2] bcs-broker rtsp [ACK] Seq=1 Ack=71963 Win=51200 Len=0 SLE=72979 SRE=74793 107 0.768215192.168.123.100 192.168.123.101 TCP [TCP segment of a reassembled PDU] 108 0.768269192.168.123.101 192.168.123.100 TCP [TCP Dup ACK 101#3] bcs-broker rtsp [ACK] Seq=1 Ack=71963 Win=51200 Len=0 SLE=72979 SRE=76253 109 0.770532192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 1472 bytes 110 0.770548192.168.123.101 192.168.123.100 TCP [TCP Dup ACK 101#4] bcs-broker rtsp [ACK] Seq=1 Ack=71963 Win=51200 Len=0 SLE=72979 SRE=76269 111 0.777225192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 425 bytes 112 0.777280192.168.123.101 192.168.123.100 TCP [TCP Dup ACK 101#5] bcs-broker rtsp [ACK] Seq=1 Ack=71963 Win=51200 Len=0 SLE=72979 SRE=76698 113 0.797305192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 1420 bytes 114 0.797378192.168.123.101 192.168.123.100 TCP [TCP Dup ACK 101#6] bcs-broker rtsp [ACK] Seq=1 Ack=71963 Win=51200 Len=0 SLE=72979 SRE=78122 115 0.798265192.168.123.100 192.168.123.101 TCP rtsp slingshot [ACK] Seq=1 Ack=657 Win=652 Len=0 116 0.800536192.168.123.100 192.168.123.101 RTSP Reply: RTSP/1.0 200 OK 117 0.800567192.168.123.101 192.168.123.100 TCP [TCP Dup ACK 101#7] bcs-broker rtsp [ACK] Seq=1 Ack=71963 Win=51200 Len=0 SLE=72979 SRE=78261 118 0.815779192.168.123.100 192.168.123.101 TCP [TCP Fast Retransmission] Interleaved channel 0x00, 1012 bytes 119 0.815863192.168.123.101 192.168.123.100 TCP bcs-broker rtsp [ACK] Seq=1 Ack=78261 Win=51200 Len=0 120 0.828061192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 749 bytes 121 0.833133192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 971 bytes 122 0.833169192.168.123.101 192.168.123.100 TCP bcs-broker rtsp [ACK] Seq=1 Ack=79989 Win=51200 Len=0 On 06/03/2008, Fabiana moreno [EMAIL PROTECTED] wrote: That´s is the thing... i am not seeing any udp packets in my capture. just tcp and rtsp. Attached are the capture files(one .pcap and the other in text form) that includes RTSP signalling On 06/03/2008, Martin Mathieson [EMAIL PROTECTED] wrote: Could you possibly post a capture file that includes the RTSP signalling? We should be configuring the RTP stream with the dynamic payload type so that it can be displayed properly... On Wed, Mar 5, 2008 at 11:08 PM, Fabiana moreno [EMAIL PROTECTED] wrote: Well it's my final year
Re: [Wireshark-users] Wireshark doesnt recognize RTP packets when i decode
When i decode to udp and hence to rtp to analyse the jitter, and the delays then i get that problem of unknowns that i mentioned On 06/03/2008, Fabiana moreno [EMAIL PROTECTED] wrote: If you dont want to open any attachment..then this is a sample of what i see when im capturing 94 0.695962192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 1356 bytes 95 0.696016192.168.123.101 192.168.123.100 TCP bcs-broker rtsp [ACK] Seq=1 Ack=69353 Win=51200 Len=0 96 0.706464192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 118 bytes 97 0.712661192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 1262 bytes 98 0.712699192.168.123.101 192.168.123.100 TCP bcs-broker rtsp [ACK] Seq=1 Ack=70741 Win=50853 Len=0 99 0.720359192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 1218 bytes 100 0.738111192.168.123.100 192.168.123.101 TCP [TCP Previous segment lost] Interleaved channel 0x00, 898 bytes 101 0.738162192.168.123.101 192.168.123.100 TCP bcs-broker rtsp [ACK] Seq=1 Ack=71963 Win=51200 Len=0 SLE=72979 SRE=73881 102 0.740297192.168.123.101 192.168.123.100 RTSP Continuation 103 0.742967192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 797 bytes 104 0.743031192.168.123.101 192.168.123.100 TCP [TCP Dup ACK 101#1] bcs-broker rtsp [ACK] Seq=1 Ack=71963 Win=51200 Len=0 SLE=72979 SRE=74682 105 0.756244192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 107 bytes 106 0.756283192.168.123.101 192.168.123.100 TCP [TCP Dup ACK 101#2] bcs-broker rtsp [ACK] Seq=1 Ack=71963 Win=51200 Len=0 SLE=72979 SRE=74793 107 0.768215192.168.123.100 192.168.123.101 TCP [TCP segment of a reassembled PDU] 108 0.768269192.168.123.101 192.168.123.100 TCP [TCP Dup ACK 101#3] bcs-broker rtsp [ACK] Seq=1 Ack=71963 Win=51200 Len=0 SLE=72979 SRE=76253 109 0.770532192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 1472 bytes 110 0.770548192.168.123.101 192.168.123.100 TCP [TCP Dup ACK 101#4] bcs-broker rtsp [ACK] Seq=1 Ack=71963 Win=51200 Len=0 SLE=72979 SRE=76269 111 0.777225192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 425 bytes 112 0.777280192.168.123.101 192.168.123.100 TCP [TCP Dup ACK 101#5] bcs-broker rtsp [ACK] Seq=1 Ack=71963 Win=51200 Len=0 SLE=72979 SRE=76698 113 0.797305192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 1420 bytes 114 0.797378192.168.123.101 192.168.123.100 TCP [TCP Dup ACK 101#6] bcs-broker rtsp [ACK] Seq=1 Ack=71963 Win=51200 Len=0 SLE=72979 SRE=78122 115 0.798265192.168.123.100 192.168.123.101 TCP rtsp slingshot [ACK] Seq=1 Ack=657 Win=652 Len=0 116 0.800536192.168.123.100 192.168.123.101 RTSP Reply: RTSP/1.0 200 OK 117 0.800567192.168.123.101 192.168.123.100 TCP [TCP Dup ACK 101#7] bcs-broker rtsp [ACK] Seq=1 Ack=71963 Win=51200 Len=0 SLE=72979 SRE=78261 118 0.815779192.168.123.100 192.168.123.101 TCP [TCP Fast Retransmission] Interleaved channel 0x00, 1012 bytes 119 0.815863192.168.123.101 192.168.123.100 TCP bcs-broker rtsp [ACK] Seq=1 Ack=78261 Win=51200 Len=0 120 0.828061192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 749 bytes 121 0.833133192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 971 bytes 122 0.833169192.168.123.101 192.168.123.100 TCP bcs-broker rtsp [ACK] Seq=1 Ack=79989 Win=51200 Len=0 On 06/03/2008, Fabiana moreno [EMAIL PROTECTED] wrote: That´s is the thing... i am not seeing any udp packets in my capture. just tcp and rtsp. Attached are the capture files(one .pcap and the other in text form) that includes RTSP signalling On 06/03/2008, Martin Mathieson [EMAIL PROTECTED] wrote: Could you possibly post a capture file that includes the RTSP signalling? We should be configuring the RTP stream with the dynamic payload type so that it can be displayed properly... On Wed, Mar 5, 2008 at 11:08 PM, Fabiana moreno [EMAIL PROTECTED] wrote: Well it's my final year project and i need to analyse the QoS parameters when streaming over wireless lan. I'm streaming an mpeg4 video from a server to my client (the last one is the one where wireshark is installed) So im trying to to capture all the packets im getting when streaming. My server supports rtcp/rtp and i think (correct me if im wrong) that the best way to analyse all these packets are to decode them to
Re: [Wireshark-users] Wireshark doesnt recognize RTP packets when i decode
In order to help get this implemented, could you please create an enhancement request at http://bugs.wireshark.org and attach a sample trace showing the problem? I don't know how soon I or someone else might find time to work on this, so I would suggest pursuing the UDP/RTP route, if possible On Thu, Mar 6, 2008 at 11:54 AM, Fabiana moreno [EMAIL PROTECTED] wrote: Thanks!! i do think i need that! On 06/03/2008, Martin Mathieson [EMAIL PROTECTED] wrote: When we set up RTP streams (including passing information about dynamic payload types), we assume that its over UDP. It would be good to fix this. But in the meantime, can't you configure your RTSP server or client to use UDP/RTP transport for the media? On Thu, Mar 6, 2008 at 11:10 AM, Fabiana moreno [EMAIL PROTECTED] wrote: When i decode to udp and hence to rtp to analyse the jitter, and the delays then i get that problem of unknowns that i mentioned On 06/03/2008, Fabiana moreno [EMAIL PROTECTED] wrote: If you dont want to open any attachment..then this is a sample of what i see when im capturing 94 0.695962192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 1356 bytes 95 0.696016192.168.123.101 192.168.123.100 TCP bcs-broker rtsp [ACK] Seq=1 Ack=69353 Win=51200 Len=0 96 0.706464192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 118 bytes 97 0.712661192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 1262 bytes 98 0.712699192.168.123.101 192.168.123.100 TCP bcs-broker rtsp [ACK] Seq=1 Ack=70741 Win=50853 Len=0 99 0.720359192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 1218 bytes 100 0.738111192.168.123.100 192.168.123.101 TCP [TCP Previous segment lost] Interleaved channel 0x00, 898 bytes 101 0.738162192.168.123.101 192.168.123.100 TCP bcs-broker rtsp [ACK] Seq=1 Ack=71963 Win=51200 Len=0 SLE=72979 SRE=73881 102 0.740297192.168.123.101 192.168.123.100 RTSP Continuation 103 0.742967192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 797 bytes 104 0.743031192.168.123.101 192.168.123.100 TCP [TCP Dup ACK 101#1] bcs-broker rtsp [ACK] Seq=1 Ack=71963 Win=51200 Len=0 SLE=72979 SRE=74682 105 0.756244192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 107 bytes 106 0.756283192.168.123.101 192.168.123.100 TCP [TCP Dup ACK 101#2] bcs-broker rtsp [ACK] Seq=1 Ack=71963 Win=51200 Len=0 SLE=72979 SRE=74793 107 0.768215192.168.123.100 192.168.123.101 TCP [TCP segment of a reassembled PDU] 108 0.768269192.168.123.101 192.168.123.100 TCP [TCP Dup ACK 101#3] bcs-broker rtsp [ACK] Seq=1 Ack=71963 Win=51200 Len=0 SLE=72979 SRE=76253 109 0.770532192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 1472 bytes 110 0.770548192.168.123.101 192.168.123.100 TCP [TCP Dup ACK 101#4] bcs-broker rtsp [ACK] Seq=1 Ack=71963 Win=51200 Len=0 SLE=72979 SRE=76269 111 0.777225192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 425 bytes 112 0.777280192.168.123.101 192.168.123.100 TCP [TCP Dup ACK 101#5] bcs-broker rtsp [ACK] Seq=1 Ack=71963 Win=51200 Len=0 SLE=72979 SRE=76698 113 0.797305192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 1420 bytes 114 0.797378192.168.123.101 192.168.123.100 TCP [TCP Dup ACK 101#6] bcs-broker rtsp [ACK] Seq=1 Ack=71963 Win=51200 Len=0 SLE=72979 SRE=78122 115 0.798265192.168.123.100 192.168.123.101 TCP rtsp slingshot [ACK] Seq=1 Ack=657 Win=652 Len=0 116 0.800536192.168.123.100 192.168.123.101 RTSP Reply: RTSP/1.0 200 OK 117 0.800567192.168.123.101 192.168.123.100 TCP [TCP Dup ACK 101#7] bcs-broker rtsp [ACK] Seq=1 Ack=71963 Win=51200 Len=0 SLE=72979 SRE=78261 118 0.815779192.168.123.100 192.168.123.101 TCP [TCP Fast Retransmission] Interleaved channel 0x00, 1012 bytes 119 0.815863192.168.123.101 192.168.123.100 TCP bcs-broker rtsp [ACK] Seq=1 Ack=78261 Win=51200 Len=0 120 0.828061192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 749 bytes 121 0.833133192.168.123.100 192.168.123.101 TCP Interleaved channel 0x00, 971 bytes 122 0.833169192.168.123.101 192.168.123.100 TCP bcs-broker rtsp [ACK] Seq=1 Ack=79989 Win=51200 Len=0 On 06/03/2008, Fabiana moreno [EMAIL
Re: [Wireshark-users] Wireshark doesnt recognize RTP packets when i decode
Yes, but have you tried to configure preferences in the RTSP client or server to encourage it to use RTP over UDP instead (the RTSP protocol allows this). On Thu, Mar 6, 2008 at 10:52 AM, Fabiana moreno [EMAIL PROTECTED] wrote: That´s is the thing... i am not seeing any udp packets in my capture. just tcp and rtsp. Attached are the capture files(one .pcap and the other in text form) that includes RTSP signalling On 06/03/2008, Martin Mathieson [EMAIL PROTECTED] wrote: Could you possibly post a capture file that includes the RTSP signalling? We should be configuring the RTP stream with the dynamic payload type so that it can be displayed properly... On Wed, Mar 5, 2008 at 11:08 PM, Fabiana moreno [EMAIL PROTECTED] wrote: Well it's my final year project and i need to analyse the QoS parameters when streaming over wireless lan. I'm streaming an mpeg4 video from a server to my client (the last one is the one where wireshark is installed) So im trying to to capture all the packets im getting when streaming. My server supports rtcp/rtp and i think (correct me if im wrong) that the best way to analyse all these packets are to decode them to udp and then to rtp but im getting the problem mentioned before. But is there some way i can fix this? On 05/03/2008, Jaap Keuter [EMAIL PROTECTED] wrote: Well, I dont' really understand what you do, but the PT=unknown is from the fact that this packet type is dynamically assigned, negotiated between parties. If Wireshark doesn't see the negotiations, it can't make out which codec goes with PT 96. So yes, it can happen you see this. Thanx, Jaap Fabiana moreno wrote: hello!!! I'm streaming an mpeg4 video with darwin streamer server trhough my WLAN. I'm using wireshark to analyse the packets im receiving. I see TCP/RTSP packets but when i decode to UDP and then to RTP to anlyse it, wireshark shows the following in all the packets, here a sample: 340.253327192.168.123.100 http://192.168.123.100/ 192.168.123.101 http://192.168.123.101/RTPPT=Unknown (96), SSRC=0x4B6C00C, Seq=65416, Time=1531529067 is this what i suppose to see? any suggestions in how to analyse packets im receiving while streaming? please help!! im new ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users
Re: [Wireshark-users] Wireshark doesnt recognize RTP packets when i decode
Hey Martin i configured my client to listen to port 7070(udp) So, now in my captures i just see udp packets..that's fine But when i try to decode to rtp...there's the same error... i should be able to decode udp to rtp smoothly right? On 06/03/2008, Martin Mathieson [EMAIL PROTECTED] wrote: Yes, but have you tried to configure preferences in the RTSP client or server to encourage it to use RTP over UDP instead (the RTSP protocol allows this). On Thu, Mar 6, 2008 at 10:52 AM, Fabiana moreno [EMAIL PROTECTED] wrote: That´s is the thing... i am not seeing any udp packets in my capture. just tcp and rtsp. Attached are the capture files(one .pcap and the other in text form) that includes RTSP signalling On 06/03/2008, Martin Mathieson [EMAIL PROTECTED] wrote: Could you possibly post a capture file that includes the RTSP signalling? We should be configuring the RTP stream with the dynamic payload type so that it can be displayed properly... On Wed, Mar 5, 2008 at 11:08 PM, Fabiana moreno [EMAIL PROTECTED] wrote: Well it's my final year project and i need to analyse the QoS parameters when streaming over wireless lan. I'm streaming an mpeg4 video from a server to my client (the last one is the one where wireshark is installed) So im trying to to capture all the packets im getting when streaming. My server supports rtcp/rtp and i think (correct me if im wrong) that the best way to analyse all these packets are to decode them to udp and then to rtp but im getting the problem mentioned before. But is there some way i can fix this? On 05/03/2008, Jaap Keuter [EMAIL PROTECTED] wrote: Well, I dont' really understand what you do, but the PT=unknown is from the fact that this packet type is dynamically assigned, negotiated between parties. If Wireshark doesn't see the negotiations, it can't make out which codec goes with PT 96. So yes, it can happen you see this. Thanx, Jaap Fabiana moreno wrote: hello!!! I'm streaming an mpeg4 video with darwin streamer server trhough my WLAN. I'm using wireshark to analyse the packets im receiving. I see TCP/RTSP packets but when i decode to UDP and then to RTP to anlyse it, wireshark shows the following in all the packets, here a sample: 340.253327192.168.123.100 http://192.168.123.100/ 192.168.123.101 http://192.168.123.101/RTPPT=Unknown (96), SSRC=0x4B6C00C, Seq=65416, Time=1531529067 is this what i suppose to see? any suggestions in how to analyse packets im receiving while streaming? please help!! im new ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users
Re: [Wireshark-users] Wireshark doesnt recognize RTP packets when i decode
Did you turn on the RTP heuristic dissector in the RTP dissector preferences? Could you possibly send a capture file? On Thu, Mar 6, 2008 at 9:02 PM, Fabiana moreno [EMAIL PROTECTED] wrote: Hey Martin i configured my client to listen to port 7070(udp) So, now in my captures i just see udp packets..that's fine But when i try to decode to rtp...there's the same error... i should be able to decode udp to rtp smoothly right? On 06/03/2008, Martin Mathieson [EMAIL PROTECTED] wrote: Yes, but have you tried to configure preferences in the RTSP client or server to encourage it to use RTP over UDP instead (the RTSP protocol allows this). On Thu, Mar 6, 2008 at 10:52 AM, Fabiana moreno [EMAIL PROTECTED] wrote: That´s is the thing... i am not seeing any udp packets in my capture. just tcp and rtsp. Attached are the capture files(one .pcap and the other in text form) that includes RTSP signalling On 06/03/2008, Martin Mathieson [EMAIL PROTECTED] wrote: Could you possibly post a capture file that includes the RTSP signalling? We should be configuring the RTP stream with the dynamic payload type so that it can be displayed properly... On Wed, Mar 5, 2008 at 11:08 PM, Fabiana moreno [EMAIL PROTECTED] wrote: Well it's my final year project and i need to analyse the QoS parameters when streaming over wireless lan. I'm streaming an mpeg4 video from a server to my client (the last one is the one where wireshark is installed) So im trying to to capture all the packets im getting when streaming. My server supports rtcp/rtp and i think (correct me if im wrong) that the best way to analyse all these packets are to decode them to udp and then to rtp but im getting the problem mentioned before. But is there some way i can fix this? On 05/03/2008, Jaap Keuter [EMAIL PROTECTED] wrote: Well, I dont' really understand what you do, but the PT=unknown is from the fact that this packet type is dynamically assigned, negotiated between parties. If Wireshark doesn't see the negotiations, it can't make out which codec goes with PT 96. So yes, it can happen you see this. Thanx, Jaap Fabiana moreno wrote: hello!!! I'm streaming an mpeg4 video with darwin streamer server trhough my WLAN. I'm using wireshark to analyse the packets im receiving. I see TCP/RTSP packets but when i decode to UDP and then to RTP to anlyse it, wireshark shows the following in all the packets, here a sample: 340.253327192.168.123.100 http://192.168.123.100/ 192.168.123.101 http://192.168.123.101/RTPPT=Unknown (96), SSRC=0x4B6C00C, Seq=65416, Time=1531529067 is this what i suppose to see? any suggestions in how to analyse packets im receiving while streaming? please help!! im new ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users
Re: [Wireshark-users] Wireshark doesnt recognize RTP packets when i decode
no i havent done sowhere is the rtp dissector preferences??? thanks On 06/03/2008, Martin Mathieson [EMAIL PROTECTED] wrote: Did you turn on the RTP heuristic dissector in the RTP dissector preferences? Could you possibly send a capture file? On Thu, Mar 6, 2008 at 9:02 PM, Fabiana moreno [EMAIL PROTECTED] wrote: Hey Martin i configured my client to listen to port 7070(udp) So, now in my captures i just see udp packets..that's fine But when i try to decode to rtp...there's the same error... i should be able to decode udp to rtp smoothly right? On 06/03/2008, Martin Mathieson [EMAIL PROTECTED] wrote: Yes, but have you tried to configure preferences in the RTSP client or server to encourage it to use RTP over UDP instead (the RTSP protocol allows this). On Thu, Mar 6, 2008 at 10:52 AM, Fabiana moreno [EMAIL PROTECTED] wrote: That´s is the thing... i am not seeing any udp packets in my capture. just tcp and rtsp. Attached are the capture files(one .pcap and the other in text form) that includes RTSP signalling On 06/03/2008, Martin Mathieson [EMAIL PROTECTED] wrote: Could you possibly post a capture file that includes the RTSP signalling? We should be configuring the RTP stream with the dynamic payload type so that it can be displayed properly... On Wed, Mar 5, 2008 at 11:08 PM, Fabiana moreno [EMAIL PROTECTED] wrote: Well it's my final year project and i need to analyse the QoS parameters when streaming over wireless lan. I'm streaming an mpeg4 video from a server to my client (the last one is the one where wireshark is installed) So im trying to to capture all the packets im getting when streaming. My server supports rtcp/rtp and i think (correct me if im wrong) that the best way to analyse all these packets are to decode them to udp and then to rtp but im getting the problem mentioned before. But is there some way i can fix this? On 05/03/2008, Jaap Keuter [EMAIL PROTECTED] wrote: Well, I dont' really understand what you do, but the PT=unknown is from the fact that this packet type is dynamically assigned, negotiated between parties. If Wireshark doesn't see the negotiations, it can't make out which codec goes with PT 96. So yes, it can happen you see this. Thanx, Jaap Fabiana moreno wrote: hello!!! I'm streaming an mpeg4 video with darwin streamer server trhough my WLAN. I'm using wireshark to analyse the packets im receiving. I see TCP/RTSP packets but when i decode to UDP and then to RTP to anlyse it, wireshark shows the following in all the packets, here a sample: 340.253327192.168.123.100 http://192.168.123.100/ 192.168.123.101 http://192.168.123.101/RTPPT=Unknown (96), SSRC=0x4B6C00C, Seq=65416, Time=1531529067 is this what i suppose to see? any suggestions in how to analyse packets im receiving while streaming? please help!! im new ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users
Re: [Wireshark-users] Wireshark doesnt recognize RTP packets when i decode
Its in Edit | Preferences | Protocols | RTP | 'Try to decode RTP outside of a conversation'. Reading your very first post, however, shows that you've already seen these decoded as RTP... Can you post a UDP capture? On Thu, Mar 6, 2008 at 9:37 PM, Fabiana moreno [EMAIL PROTECTED] wrote: no i havent done sowhere is the rtp dissector preferences??? thanks On 06/03/2008, Martin Mathieson [EMAIL PROTECTED] wrote: Did you turn on the RTP heuristic dissector in the RTP dissector preferences? Could you possibly send a capture file? On Thu, Mar 6, 2008 at 9:02 PM, Fabiana moreno [EMAIL PROTECTED] wrote: Hey Martin i configured my client to listen to port 7070(udp) So, now in my captures i just see udp packets..that's fine But when i try to decode to rtp...there's the same error... i should be able to decode udp to rtp smoothly right? On 06/03/2008, Martin Mathieson [EMAIL PROTECTED] wrote: Yes, but have you tried to configure preferences in the RTSP client or server to encourage it to use RTP over UDP instead (the RTSP protocol allows this). On Thu, Mar 6, 2008 at 10:52 AM, Fabiana moreno [EMAIL PROTECTED] wrote: That´s is the thing... i am not seeing any udp packets in my capture. just tcp and rtsp. Attached are the capture files(one .pcap and the other in text form) that includes RTSP signalling On 06/03/2008, Martin Mathieson [EMAIL PROTECTED] wrote: Could you possibly post a capture file that includes the RTSP signalling? We should be configuring the RTP stream with the dynamic payload type so that it can be displayed properly... On Wed, Mar 5, 2008 at 11:08 PM, Fabiana moreno [EMAIL PROTECTED] wrote: Well it's my final year project and i need to analyse the QoS parameters when streaming over wireless lan. I'm streaming an mpeg4 video from a server to my client (the last one is the one where wireshark is installed) So im trying to to capture all the packets im getting when streaming. My server supports rtcp/rtp and i think (correct me if im wrong) that the best way to analyse all these packets are to decode them to udp and then to rtp but im getting the problem mentioned before. But is there some way i can fix this? On 05/03/2008, Jaap Keuter [EMAIL PROTECTED] wrote: Well, I dont' really understand what you do, but the PT=unknown is from the fact that this packet type is dynamically assigned, negotiated between parties. If Wireshark doesn't see the negotiations, it can't make out which codec goes with PT 96. So yes, it can happen you see this. Thanx, Jaap Fabiana moreno wrote: hello!!! I'm streaming an mpeg4 video with darwin streamer server trhough my WLAN. I'm using wireshark to analyse the packets im receiving. I see TCP/RTSP packets but when i decode to UDP and then to RTP to anlyse it, wireshark shows the following in all the packets, here a sample: 340.253327192.168.123.100 http://192.168.123.100/ 192.168.123.101 http://192.168.123.101/RTPPT=Unknown (96), SSRC=0x4B6C00C, Seq=65416, Time=1531529067 is this what i suppose to see? any suggestions in how to analyse packets im receiving while streaming? please help!! im new ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users ___ Wireshark-users mailing
Re: [Wireshark-users] Wireshark doesnt recognize RTP packets when i decode
that capture is just udp without decoding to RTP.. On 06/03/2008, Fabiana moreno [EMAIL PROTECTED] wrote: the first post was when i already had decoded udp data into rtp... here's my capture On 06/03/2008, Martin Mathieson [EMAIL PROTECTED] wrote: Its in Edit | Preferences | Protocols | RTP | 'Try to decode RTP outside of a conversation'. Reading your very first post, however, shows that you've already seen these decoded as RTP... Can you post a UDP capture? On Thu, Mar 6, 2008 at 9:37 PM, Fabiana moreno [EMAIL PROTECTED] wrote: no i havent done sowhere is the rtp dissector preferences??? thanks On 06/03/2008, Martin Mathieson [EMAIL PROTECTED] wrote: Did you turn on the RTP heuristic dissector in the RTP dissector preferences? Could you possibly send a capture file? On Thu, Mar 6, 2008 at 9:02 PM, Fabiana moreno [EMAIL PROTECTED] wrote: Hey Martin i configured my client to listen to port 7070(udp) So, now in my captures i just see udp packets..that's fine But when i try to decode to rtp...there's the same error... i should be able to decode udp to rtp smoothly right? On 06/03/2008, Martin Mathieson [EMAIL PROTECTED] wrote: Yes, but have you tried to configure preferences in the RTSP client or server to encourage it to use RTP over UDP instead (the RTSP protocol allows this). On Thu, Mar 6, 2008 at 10:52 AM, Fabiana moreno [EMAIL PROTECTED] wrote: That´s is the thing... i am not seeing any udp packets in my capture. just tcp and rtsp. Attached are the capture files(one .pcap and the other in text form) that includes RTSP signalling On 06/03/2008, Martin Mathieson [EMAIL PROTECTED] wrote: Could you possibly post a capture file that includes the RTSP signalling? We should be configuring the RTP stream with the dynamic payload type so that it can be displayed properly... On Wed, Mar 5, 2008 at 11:08 PM, Fabiana moreno [EMAIL PROTECTED] wrote: Well it's my final year project and i need to analyse the QoS parameters when streaming over wireless lan. I'm streaming an mpeg4 video from a server to my client (the last one is the one where wireshark is installed) So im trying to to capture all the packets im getting when streaming. My server supports rtcp/rtp and i think (correct me if im wrong) that the best way to analyse all these packets are to decode them to udp and then to rtp but im getting the problem mentioned before. But is there some way i can fix this? On 05/03/2008, Jaap Keuter [EMAIL PROTECTED] wrote: Well, I dont' really understand what you do, but the PT=unknown is from the fact that this packet type is dynamically assigned, negotiated between parties. If Wireshark doesn't see the negotiations, it can't make out which codec goes with PT 96. So yes, it can happen you see this. Thanx, Jaap Fabiana moreno wrote: hello!!! I'm streaming an mpeg4 video with darwin streamer server trhough my WLAN. I'm using wireshark to analyse the packets im receiving. I see TCP/RTSP packets but when i decode to UDP and then to RTP to anlyse it, wireshark shows the following in all the packets, here a sample: 340.253327192.168.123.100 http://192.168.123.100/ 192.168.123.101 http://192.168.123.101/RTP PT=Unknown (96), SSRC=0x4B6C00C, Seq=65416, Time=1531529067 is this what i suppose to see? any suggestions in how to analyse packets im receiving while streaming? please help!! im new ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users ___
[Wireshark-users] Wireshark doesnt recognize RTP packets when i decode
hello!!! I'm streaming an mpeg4 video with darwin streamer server trhough my WLAN. I'm using wireshark to analyse the packets im receiving. I see TCP/RTSP packets but when i decode to UDP and then to RTP to anlyse it, wireshark shows the following in all the packets, here a sample: 340.253327192.168.123.100192.168.123.101RTPPT=Unknown (96), SSRC=0x4B6C00C, Seq=65416, Time=1531529067 is this what i suppose to see? any suggestions in how to analyse packets im receiving while streaming? please help!! im new ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users
Re: [Wireshark-users] Wireshark doesnt recognize RTP packets when i decode
Hello Fabiana I am not sure what do you mean by trying to decode rtcp/rtp packets to udp. As far as i know rtp/rtcp packets should be carried over udp which should be carried over ip (rtp/udp/ip). Do you see any UDP packets when capturing the data? Regards Jehanzeb Khan - Original Message From: Fabiana moreno [EMAIL PROTECTED] To: Community support list for Wireshark wireshark-users@wireshark.org Sent: Thursday, March 6, 2008 4:08:09 AM Subject: Re: [Wireshark-users] Wireshark doesnt recognize RTP packets when i decode Well it's my final year project and i need to analyse the QoS parameters when streaming over wireless lan. I'm streaming an mpeg4 video from a server to my client (the last one is the one where wireshark is installed) So im trying to to capture all the packets im getting when streaming. My server supports rtcp/rtp and i think (correct me if im wrong) that the best way to analyse all these packets are to decode them to udp and then to rtp but im getting the problem mentioned before. But is there some way i can fix this? On 05/03/2008, Jaap Keuter [EMAIL PROTECTED] wrote: Well, I dont' really understand what you do, but the PT=unknown is from the fact that this packet type is dynamically assigned, negotiated between parties. If Wireshark doesn't see the negotiations, it can't make out which codec goes with PT 96. So yes, it can happen you see this. Thanx, Jaap Fabiana moreno wrote: hello!!! I'm streaming an mpeg4 video with darwin streamer server trhough my WLAN. I'm using wireshark to analyse the packets im receiving. I see TCP/RTSP packets but when i decode to UDP and then to RTP to anlyse it, wireshark shows the following in all the packets, here a sample: 340.253327192.168.123.100 http://192.168.123.100/ 192.168.123.101 http://192.168.123.101/RTPPT=Unknown (96), SSRC=0x4B6C00C, Seq=65416, Time=1531529067 is this what i suppose to see? any suggestions in how to analyse packets im receiving while streaming? please help!! im new ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users -Inline Attachment Follows- ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users
