** Changed in: ekiga
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/423461
Title:
Call out fails if there is multiple network interfaces
To manage notifications
** Changed in: ekiga
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/423461
Title:
Call out fails if there is multiple network interfaces
To manage notifications
** Changed in: ekiga
Status: Fix Released = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/423461
Title:
Call out fails if there is multiple network interfaces
--
ubuntu-bugs mailing
** Changed in: ekiga
Status: New = Fix Released
** Changed in: ekiga
Importance: Unknown = High
--
Call out fails if there is multiple network interfaces
https://bugs.launchpad.net/bugs/423461
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: ekiga (Ubuntu)
Status: Confirmed = Triaged
--
Call out fails if there is multiple network interfaces
https://bugs.launchpad.net/bugs/423461
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
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
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
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
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
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?
--
Call out fails if there is multiple network interfaces
https://bugs.launchpad.net/bugs/423461
You received this bug notification because
Hi Yannick Defais,
I have just found with ekiga -d2, when I try to connect:
2009/09/26 01:05:27.728 0:10.612Aggregator: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
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
--
Call out fails if there is multiple network interfaces
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
--
Call out fails if there is multiple network interfaces
https://bugs.launchpad.net/bugs/423461
You received this bug notification because you are a member of Ubuntu
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.
** Attachment added: Log for wlan interface
http://launchpadlibrarian.net/32341391/ekiga.log
--
Call out fails if there is multiple network
** Changed in: ekiga
Status: Unknown = New
--
Call out fails if there is multiple network interfaces
https://bugs.launchpad.net/bugs/423461
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Thank you.
--
Call out fails if there is multiple network interfaces
https://bugs.launchpad.net/bugs/423461
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
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.
** Attachment added: ekiga -d 4
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
** Attachment added: ekiga -d 4
18 matches
Mail list logo
