Comment # 7
on bug 9820
from Jawad
(In reply to comment #1)
> When you say "network delay", obviously Wireshark doesn't really know the
> network delay end-to-end, since it only knows what it sees. Do you mean the
> difference in time between a SIP request and its response? And if so, do you
> mean the time between the INVITE and a 100 trying, or an INVITE and a
> 18x/200? (the former would be the delay to the SIP next-hop, while the
> latter would be the delay to the far-end SIP UAS)
>
> And for "packet loss", do you mean if wireshark sees retransmitted SIP
> requests/responses?
i have a file that is a real time call, definitely it contains the information
of sending time and receiving time of a packet. i am calling the time that a
packet took from caller to callee as "network delay". and its kind of general
thing, not for a specific group of packets (like SIP, RTP etc)
my idea is to find the over all time that a packet take from caller to callee.
the intermediate hopes (UAS caller side, UAS callee side etc) are kind or
irrelevant.
i am interested in the time that a packet takes from UAC(caller) to the other
UAC(callee), they could be registered on same UAS or different.
hope my statement is clear now
You are receiving this mail because:
- You are watching all bug changes.
