Ubuntu
telepathy-sofiasip package

Network error for SIP accounts

Bug #392682 reported by Guy Van Sanden
This bug report is a duplicate of:  Bug #294994: NAT traversal for SIP using Empathy. Edit Remove
78
This bug affects 14 people
Affects Status Importance Assigned to Milestone
telepathy-sofiasip (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: empathy

I'm testing the PPA packages that are set to go into Karmic. I created an ekiga.net account and connected with ekiga without a problem.

Empathy gives 'network error' on connection with identical settings

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: empathy 2.27.3-2ubuntu1~ppa9.04+1
ProcEnviron:
 LC_CTYPE=C
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/usr/bin/zsh
SourcePackage: empathy
Uname: Linux 2.6.28-13-generic i686
UnreportableReason: This is not a genuine Ubuntu package

Revision history for this message
Guy Van Sanden (gvs) wrote :
Revision history for this message
Corey Kearney (snkiz-deactivatedaccount) wrote :

confirmed same error on Ubuntu 9.04

Brian Curtis (bcurtiswx)
Changed in empathy (Ubuntu):
status: New → Confirmed
Revision history for this message
Brian Curtis (bcurtiswx) wrote :

This bug has to deal with telepathy-sofiasip connection manager for empathy. Changing package

affects: empathy (Ubuntu) → telepathy-sofiasip (Ubuntu)
Revision history for this message
Robert Grønning (slimg) wrote :

This isn't a crash like in bug #351541, this is a errormessage saying "network error" when trying to connect

Revision history for this message
Afterlifesol (afterlifesol) wrote :

Also agree no crash, can't get to the point to even try to make a call, this is trying to get the account to connect. not like bug # 351541

Revision history for this message
Nathaniel Homier (mechamechanism) wrote :

Hooray! No activity on this bug since 2009. I have this bug. When should I expect developers to take a crack at solving this? Maybe the developers will get around to it sometime in the year 2032 A.D.?

Revision history for this message
Nathaniel Homier (mechamechanism) wrote :

OK, my comment above was a little harsh. ^^^^^

So on Twitter, I re-tweet the tweet by Cali Lewis, so I think of this comment.
@CaliLewis: Nothing seems impossible for the person who doesn't have to do it himself.

So if you need logs, build from src and run debuggers, upgrade libraries, I'm happy to do it. This bug very annoying as I have to continue using Ekiga. I much prefer the intregated approach with Emapathy. So what ever you need I'm happy to help.

Revision history for this message
David Ayers (ayers) wrote :

I can confirm the inability to connect to my ekiga.net account:

Karmic:
I can confirm the "disconnected - network error" message for my ekiga.net account
I get an "authentication failed" (translated from german) message for my a1.net account
I am able to connect to my turbocat.net account and receive calls (well at least one then I need to reconnect).

Lucid
On all three accounts I get a "disconnected - network error" message.

I am using the standard packages:
karmic: telepathy-sofiasip 0.5.18-1
lucid: telepathy-sofiasip 0.6.2-1ubuntu1

Revision history for this message
tobias_t (linuxert) wrote :

I have the same Problem

Revision history for this message
Stefan Fisches (stefan-fisches) wrote :

I just stumbled upon this here
"My Ekiga account doesn't work:
This is a problem in the ekiga.net server. Unfortunately this can't be fixed in Telepathy because it will break the compatibility with other SIP servers. "

http://live.gnome.org/Empathy/FAQ#My_Ekiga_account_doesn.27t_work.

Revision history for this message
David Ayers (ayers) wrote :

If I use a GSM/UMTS/USB-Stick to connect directly (i.e. without NAT traversal) I can connect to my ekiga.net with empathy/telepathy/sofiasip. Therefore I'll mark this report a duplicate of Bug #294994

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.