Call out fails if there is multiple network interfaces

[Jacek Grzebyta]

Binary package hint: ekiga

When I choose a tel. number I have a message on ekiga that the connection was finished. I can call to echo test.
Moreover the Voip provider's account tracking shows error no 200. It is described as the unknown bug.

Also I can receive a connection from other phones. I run ekiga with options -d 4 2>log and the log file I attached.

Income connection's the voice quality is ok.
with best wishes,
Jacek

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/ekiga
Package: ekiga 3.2.0-0ubuntu2
ProcEnviron:
 SHELL=/bin/bash
 LANG=pl_PL.UTF-8
 LANGUAGE=pl_PL.UTF-8
SourcePackage: ekiga
Uname: Linux 2.6.28-15-generic x86_64

[Jacek Grzebyta (jacol-deactivatedaccount)]

and connection from outside to ekiga. Log file. The connection is OK with good voice quality.

[Yannick Defais (sevmek)]

Hi Jacol,

Thank you for reporting this issue.

I saw 2 possible culprits (too many codecs issue or too many interfaces issue).

Please try this setup:
In Ekiga preferences, in audio codecs, disable all G726 codecs (4 occurences) and retry to call out. Please add a log file even if it success (I would like to compare even if that works).

Best regards,
Yannick

[Jacek Grzebyta (jacol-deactivatedaccount)]

Hi Yanick,

I did. No change. The same problem. I called to my mobile phone which is in UK. The account provider is Polish.

With best wishes,
Jacek

[Yannick Defais (sevmek)]

Thank you Jacek Grzebyta,

It seems there is something wrong in the way Ekiga deals with multiple interfaces. I'll push your report upstream.

I would like to know the reason why you have 2 network interfaces in your setup, "wlan0" and "br0"? Do you use virtualization?

Best regards,
Yannick

[Jacek Grzebyta (jacol-deactivatedaccount)]

Hi Yannick,

You are wright. The br0 is the bridge used in the virtualization. I use
kvim for that. I setup this interface in /etc/netork/interfaces:

auto br0
iface br0 inet static
address 10.0.100.1
netmask 255.255.255.0
getway 192.168.1.1
bridge_ports tap0 tap1

Best wishes,
Jacek

Yannick Defais, 06.09.2009 07:08:
> Thank you Jacek Grzebyta,
>
> It seems there is something wrong in the way Ekiga deals with multiple
> interfaces. I'll push your report upstream.
>
> I would like to know the reason why you have 2 network interfaces in
> your setup, "wlan0" and "br0"? Do you use virtualization?
>
> Best regards,
> Yannick
>
> ** Bug watch added: GNOME Bug Tracker #587504
> http://bugzilla.gnome.org/show_bug.cgi?id=587504
>
> ** Also affects: ekiga via
> http://bugzilla.gnome.org/show_bug.cgi?id=587504
> Importance: Unknown
> Status: Unknown
>

[Jacek Grzebyta (jacol-deactivatedaccount)]

and route -v gives:

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
10.0.100.0 * 255.255.255.0 U 0 0 0 br0
192.168.1.0 * 255.255.255.0 U 2 0 0
wlan0
link-local * 255.255.0.0 U 1000 0 0 br0
default 192.168.1.1 0.0.0.0 UG 0 0 0
wlan0

Yannick Defais, 06.09.2009 07:08:
> Thank you Jacek Grzebyta,
>
> It seems there is something wrong in the way Ekiga deals with multiple
> interfaces. I'll push your report upstream.
>
> I would like to know the reason why you have 2 network interfaces in
> your setup, "wlan0" and "br0"? Do you use virtualization?
>
> Best regards,
> Yannick
>
> ** Bug watch added: GNOME Bug Tracker #587504
> http://bugzilla.gnome.org/show_bug.cgi?id=587504
>
> ** Also affects: ekiga via
> http://bugzilla.gnome.org/show_bug.cgi?id=587504
> Importance: Unknown
> Status: Unknown
>

[Yannick Defais (sevmek)]

Thank you.

[Jacek Grzebyta (jacol-deactivatedaccount)]

Probably another bug.

I have switched off another interfaces like br0 and eth1 and I left lo, wlan0 and wmaster0 only (which looks like the firewire) only. After that I have a message that 'remote user broke connection' and I attached log file.

[Jacek Grzebyta (jacol-deactivatedaccount)]

Probably another bug.

I have switched off another interfaces like br0 and eth1 and I left lo, wlan0 and wmaster0 only (which looks like the firewire) only. After that I have a message that 'remote user broke connection' and I attached log file.

Best wishes,
Jacek

[Yannick Defais (sevmek)]

Hi Jacek Grzebyta,

Ekiga 3.2.6 was released yesterday. I builded packs here:
https://launchpad.net/~sevmek/+archive/ekiga-released

Could you give it a try to check if your issue is fixed with it?

Best regards,
Yannick

[Jacek Grzebyta (jacol-deactivatedaccount)]

Hi Yannick,

No. I tested on wlan and eth. Logs for both I attached. For eth0 I off wlan0 and for both the bridge interface.
with kind regards.

[Jacek Grzebyta (jacol-deactivatedaccount)]

ps for both tests I switched off firewall.

PPs I have just realised the log file for eth0 is empty. :o I do test tomorrow.
Jacek

[Yannick Defais (sevmek)]

Jacek Grzebyta,

I looked at your latest debug output. I do not see the interface selection issue anymore.

The issue there is about codec negociation:

Your ekiga client sent an INVITE including your codecs like this:
a=rtpmap:9 G722/8000/1

a=rtpmap:117 Speex/16000/1

../..

a=rtpmap:0 PCMU/8000/1

a=rtpmap:8 PCMA/8000/1

a=rtpmap:3 gsm/8000/1

a=rtpmap:116 Speex/8000/1

Your contact client answer like this:
a=rtpmap:0 pcmu/8000

a=rtpmap:3 gsm/8000

a=rtpmap:8 pcma/8000

AFAIK, the codecs on top have priority and the one calling have priority too.

In this case the top codec for both is PCMU, thus the audio codec choosen based on this negociation should be PCMU for both.

When opening the media stream Ekiga found the codec it receives is *not* PCMU and ekiga drops those frames:

2009/09/23 23:16:25.316 0:05.829 Media Patch:0x1d54b950 Patch Removing frame with mismatched payload type PCMA - should be PCMU

IMHO, either Ekiga

[Yannick Defais (sevmek)]

oops... I continue here...

IMHO, either Ekiga has a bug and wrongly confuse PCMU and PCMA or your contact client has a bug and send wrongly PCMA when it should send PCMU.

A workaround is probably to simplify the codec negociation proposing only one codec, e.g. PCMA (to do this disable all other audio codecs in ekiga preferences).

Best regards,
Yannick

[Yannick Defais (sevmek)]

btw, in your latest log, was the virtualization in use? Can I close this bug for "Call out fails if there is multiple network interfaces" using Ekiga 3.2.6?

[Jacek Grzebyta (jacol-deactivatedaccount)]

Hi Yannick Defais,

I have just found with ekiga -d2, when I try to connect:

2009/09/26 01:05:27.728 0:10.612 Aggregator:0xb3775950 SIP PDU is
likely too large (1459 bytes) for UDP datagram.
2009/09/26 01:05:27.731 0:10.615 Opal Liste...0xb54ee950 MonSock Read
UDP packet too large for buffer of 65536 bytes.
2009/09/26 01:05:27.756 0:10.640 Aggregator:0xb3775950 SIP
Authentication already performed using current credentials, not trying
again.
2009/09/26 01:05:28.820 0:11.704 OPAL
Attempting to close recording on call bdd83336d1 when not recording.
2009/09/26 01:05:45.152 0:28.036 Aggregator:0xb3775950 SIP PDU is
likely too large (1459 bytes) for UDP datagram.

What do you think about that?

On debug 3 I found:
2009/09/26 01:22:28.723 0:02.397 Aggregator:0xe38c5950 SIP
PDU is likely too large (1459 bytes) for UDP datagram.

I send you -d 3 log.

with best wishes,
Jacek

PS I off eth0:avahi for that but left br0.
PPS I am not sure it was a problem i tested with off eth0, eth:avahi and
br0 and the same. But im thinking about that too large udp datagram.

 > Yannick Defais, 25.09.2009 23:03:
> btw, in your latest log, was the virtualization in use? Can I close this
> bug for "Call out fails if there is multiple network interfaces" using
> Ekiga 3.2.6?
>

[Jacek Grzebyta (jacol-deactivatedaccount)]

Dear Yannick,

A few days ago I switched off all interfaces eth0 and eth0:avahi
including except wlan0 and lo. When I call to my mobile I had correct
connection from time to time only. But it happened once for 3-4 errors.
When I have more time I send you logs (I'll try to find some more during
weekend).

with best wishes,
Jacek

[Jacek Grzebyta (jacol-deactivatedaccount)]

Dear Yannick,

As I promised. I have your version of Ekiga and.
I off eth0 and br0 (with them I had difficulties to log in) and this log is after -d 4.

So 1st connection was correct than 3 or 4 connections with this bug/error and than the last one valid as well. All were to my mobile.

with best wishes,
and enjoy the big download in 23 days :P
Jacek