Irving Ruan wrote: > On Mon, Feb 8, 2010 at 2:11 AM, Eugen Dedu > <eugen.d...@pu-pm.univ-fcomte.fr>wrote: > >> Irving Ruan wrote: >>> On Wed, Feb 3, 2010 at 1:25 PM, Eugen Dedu >>> <eugen.d...@pu-pm.univ-fcomte.fr>wrote: >>> >>>> Irving Ruan wrote: >>>>> Hello ekiga devs, >>>>> >>>>> I am currently attempting to try and test video/audio throughput, >> delay, >>>>> etc. with Ekiga softphone via a two person conference. Are there any >>>>> programs out there that will allow me to analyze network traffic that's >>>>> specific to Ekiga's utilization of resources? Or, is there a way to >>>> better >>>>> "hook" the network packets while running Ekiga, say, from the command >>>> line >>>>> via some tool? >>>> Well, I do not think there is such a program, but you have two >>>> possibilities: >>>> >>>> - use wireshark and filter messages from and to your computer >>>> >>>> - or use ekiga -d 4 2>blahblah, and afterwards you look into this >>>> blahblah file, which contain SIP packets (not audio/video packets) and >>>> other information. If you use the program at >>>> http://git.gnome.org/browse/ekiga/plain/src/ekiga-debug-analyser, you >>>> can remove the "other information" to see only SIP packets. >>>> >>> Eugen, >>> >>> Thanks for the help. Is there an advantage to using Wireshark over the >>> command-line output option? >> with -d 4 you have only SIP headers, with wireshark you have everything. >> > > > I got some SIP and UDP packet information; I am currently attempting to do > live testing on Ekiga (user-to-user videoconferencing) and trying to obtain > the timestamps on RTP packets so I can observe the delay/jitter of one > packet from source to dest. Is there a way to obtain this information from > an ekiga debug log or some kind of udp packet analyzer?
Ekiga log does not have RTP packets. wireshark does. -- Eugen _______________________________________________ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list