Professional Documents
Culture Documents
The above table gives us the detailed account of the SIP call
made from Empathy. We can see that the jitter accounted for
is very stable and is quite acceptable.
Next we will fetch another table like this one for Ekiga
and will be able to analyze in a comparable manner between
these two SIP services.
no green spikes. that the setup information for the session must be in the
trace and the codec
used must be known to the program(with the current
implementation).
The above figure represents the Call graph. Here only one = [in seconds] 0 + (|0.049947| - 0)/16 = 0.0031216875
channel seems to have the spikes. This is because only the frame 626:
operator on the other side of the phone talked. D(1,2) = (R2 - R1) - (S2 - S1)
. Wireshark calculates jitter according to RFC3550 (RTP): = [in seconds] 0.0031216875 + (|-0.016467| - 0.0031216875)/16
= 0.00395576953125
If Si is the RTP timestamp from packet i, and Ri is the time of
arrival in RTP timestamp units for packet i, then for two How bandwidth (BW) is calculated
packets The BW column in RTP Streams and RTP Statistics dialogs shows the
i and j, D may be expressed as bandwidth at IP level for the given RTP stream. It is the sum of all octets,
including IP and UDP headers (20+8 bytes), from all the packets of the
D(i,j) = (Rj - Ri) - (Sj - Si) = (Rj - Sj) - (Ri - Si) given RTP stream over the last second.