I got it. Thank you very much!
Regards,
Patrice
El jue, 06-10-2011 a las 15:38 +0200, RUOFF, LARS (LARS)** CTR **
escribió:
> Hi,
>
> The "X" on the stream appears if at least one packet is marked non-OK.
> non-OK currently includes:
> * Comfort noise (PT=13 or PT=19)
> * Wrong sequence nr.
> * Changes in Payload type (PT)
> * Incorrect timestamp
> * Marker missing?
>
> for details, see gtk/rtp_analysis.c
> As you can see, there's no check concerning the latency or framing.
>
> For other info around RTP analysis, see http://wiki.wireshark.org/RTP_statistics
>
> Regards,
> Lars
>
>
> -----Original Message-----
> From: wireshark-users-bounces@xxxxxxxxxxxxx [mailto:wireshark-users-bounces@xxxxxxxxxxxxx] On Behalf Of Patrice Bertin
> Sent: jeudi 6 octobre 2011 15:19
> To: wireshark-users@xxxxxxxxxxxxx
> Subject: [Wireshark-users] Latency in RTP streams
>
> Hi everybody,
>
> I have a capture example of a SIP call with G711 codec.
> Looking at the RTP streams, the final field shows an X which normally means that we have a VoIP related problem.
> By selecting the problematic stream and analysing it, wireshark provides a packet-by-packet look at the stream.
> The thing I don't understand, is why does it give me the status "OK"
> everywhere if I have the famous X and especially when I have a latency of 5843.74 ms (cf the screencapture joined in the mail).
> Other thing, which values Wireshark put for the latency and jitter? Is it possible to modify it?
>
> I hope this is understandable enough.
>
> Thanks for your reply
>
>
> Patrice
> ___________________________________________________________________________
> Sent via: Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
> Archives: http://www.wireshark.org/lists/wireshark-users
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
> mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe