Re: [Ekiga-list] Echo tests on ekiga
- From: ael <law_ence dev ntlworld com>
- To: Ekiga mailing list <ekiga-list gnome org>
- Subject: Re: [Ekiga-list] Echo tests on ekiga
- Date: Mon, 23 Feb 2015 17:21:55 +0000
On Mon, Feb 23, 2015 at 03:43:43PM +0100, Damien Sandras wrote:
Le lundi 23 février 2015 à 14:35 +0000, ael a écrit :
I am trying to understand properly how to navigate firewalls using
ekiga. I have read the wiki and even contributed to it in the past.
I attach the two simple (wide) text flow recordings from wireshark
of the successful and failed calls. Wireshark does not decode the
udp audio packets in the successful call, so that is not shown.
In the failed call to 500 ekiga net, the first INVITE goes out,
and ekiga.net replies with the 407 Authentication request.
ekiga responds with the ACK and the modified INVITE, but ekiga.net
never responds (or is blocked by the firewall) thereafter.
My suspicion would be that too many audio codecs are enabled and you
reach the MTU once the authentication information
has been added : the packet never reaches ekiga.net.
Can you try removing some codecs ?
Yes. I found that all 7 of the video codecs were enabled! I hadn't
thought of looking there because I was just testing audio.
Seems a bit wrong headed that my distribution (debian for now) ship
by default a configuration that can't connect to the standard echo test.
Thanks very much. I should have thought of that myself...
ael
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]