After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 711042 - Ekiga not registering ekiga.net account
Ekiga not registering ekiga.net account
Status: RESOLVED NOTGNOME
Product: ekiga
Classification: Applications
Component: OPAL
4.0.x
Other Linux
: Normal major
: ---
Assigned To: Ekiga maintainers
Ekiga maintainers
Depends on:
Blocks:
 
 
Reported: 2013-10-28 23:37 UTC by el_gallo_azul
Modified: 2014-04-27 17:41 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
My Ekiga accounts (24.85 KB, image/png)
2013-10-28 23:37 UTC, el_gallo_azul
Details
My settings for ekiga.net (30.26 KB, image/png)
2013-10-28 23:38 UTC, el_gallo_azul
Details
-d 4 log (181.83 KB, text/plain)
2013-10-29 08:53 UTC, el_gallo_azul
Details
Another -d 4 log (181.62 KB, text/plain)
2013-10-30 01:17 UTC, el_gallo_azul
Details
Comment 14: Fritz!Box port forwarding screen (51.17 KB, image/png)
2013-10-30 07:39 UTC, el_gallo_azul
Details
Comment 14: Fritz!Box New Port Forwarding (23.33 KB, image/png)
2013-10-30 07:40 UTC, el_gallo_azul
Details
Comment 14: Eki8ga registration error (again) (15.23 KB, image/png)
2013-10-30 07:40 UTC, el_gallo_azul
Details
Fritz!Box Port Forwarding Settings screen after configuring port forwarding (70.39 KB, image/png)
2013-10-30 21:39 UTC, el_gallo_azul
Details
All three SIP accounts registered in my FritzBox (33.99 KB, image/png)
2013-11-03 06:55 UTC, el_gallo_azul
Details
FritzBox SIP accounts with the ekiga.net SIP account disabled (33.90 KB, image/png)
2013-11-03 06:56 UTC, el_gallo_azul
Details
Ekiga application successfully registering my diamondcard SIP account, despite my FritzBox having also just registered it successfully seconds beforehand (29.03 KB, image/png)
2013-11-03 06:57 UTC, el_gallo_azul
Details
-d 4 log for Ekiga 3.3.2 on Ubuntu 12.04 on my old computer (513.92 KB, text/plain)
2013-11-04 01:21 UTC, el_gallo_azul
Details
-d 4 log after accidentally setting the port range (187.80 KB, text/plain)
2013-11-24 03:42 UTC, el_gallo_azul
Details
-d 4 log after enabling Virtualization on computer (193.65 KB, text/plain)
2013-12-03 07:43 UTC, el_gallo_azul
Details

Description el_gallo_azul 2013-10-28 23:37:11 UTC
Created attachment 258359 [details]
My Ekiga accounts

Ekiga 4.0.1
Ubuntu 13.04 for 64 bit

Ekiga>Edit>Accounts

Name: Ekiga.net
Registrar: ekiga.net
User: Greg Flint
Authentication user: el_gallo_azul
Password: Is correct. I changed it about 12 hours ago and use the new one.
Timeout: 3600

My Ekiga account says Processing... including when I leave it for 30 minutes.

I tried removing the ekiga.net account, and then adding a new one, and got the message Globally not acceptable.

Then when I changed my User: to my name, and left the Authentication user: el_gallo_azul, it changed back to Processing....

My diamondcard call-out account is registered OK.
Comment 1 el_gallo_azul 2013-10-28 23:38:10 UTC
Created attachment 258360 [details]
My settings for ekiga.net
Comment 2 el_gallo_azul 2013-10-28 23:47:48 UTC
PS This is after freshly installing Ekiga (on Sunday 27.10.2013) on my new computer. It had always registered correctly on my old computer using Ubuntu 12.04 (32-bit).
Comment 3 Eugen Dedu 2013-10-29 06:52:35 UTC
Try using the same text in User and AutenticationUser fields (1) el_gallo_azul, and 2) Greg Flint) for ekiga.net account, and restart ekiga to test.
Comment 4 el_gallo_azul 2013-10-29 08:44:07 UTC
1. If I put my Ekiga user name in both fields, I get the message "Could not register (Globally not acceptable)".

(restart ekiga)

2. If I use my name in both fields, it says "Processing...".

I thought that I should use my name Greg Flint in the User: field so that people would be able to find me in the Ekiga.net Directory, and that I should use my ekiga user name el_gallo_azul in the Authentication user: field to have valid login credentials.
Comment 5 Eugen Dedu 2013-10-29 08:45:41 UTC
Use your ekiga user name in both fields, and check that you have Enable network detection in Preferences.  If it is on and you still have the error, attach the -d 4 log.
Comment 6 Eugen Dedu 2013-10-29 08:48:14 UTC
(In reply to comment #4)
> I thought that I should use my name Greg Flint in the User: field so that
> people would be able to find me in the Ekiga.net Directory, and that I should
> use my ekiga user name el_gallo_azul in the Authentication user: field to have
> valid login credentials.

No.  Ekiga.net directory uses the name put when you created the account on ekiga.net site, and your name in ekiga preferences is seen by people when you call them (cf. http://wiki.ekiga.org/index.php/Manual#Define_your_identity).
Comment 7 el_gallo_azul 2013-10-29 08:53:47 UTC
Created attachment 258419 [details]
-d 4 log

I confirm that "Enable network detection" is enabled in Preferences.
Comment 8 Eugen Dedu 2013-10-29 09:21:46 UTC
I see this line:
2013/10/29 18:18:33.329	  0:01.802	                       	STUN	Failed to bind to local UDP port in range 5060-5060

Do you have another application listening on the same port?  You cannot have two applications listening on the same port.  (Quit ekiga and use lsof -P|grep 5060 for example.)
Comment 9 el_gallo_azul 2013-10-30 01:15:07 UTC
I don't know. I have had my Fritz!Box using the same port in the past, but I checked that my Ekiga account was not registered in my Fritz!Box before starting Ekiga.

I ran lsof -P|grep 5060 with Ekiga running, and these are the results:

ekiga      80135        el_gallo_azul   36u     IPv4             244342      0t0      UDP greg-W2600CR.fritz.box:5060 
dconf      80135  80138 el_gallo_azul   36u     IPv4             244342      0t0      UDP greg-W2600CR.fritz.box:5060 
gdbus      80135  80139 el_gallo_azul   36u     IPv4             244342      0t0      UDP greg-W2600CR.fritz.box:5060 
threaded-  80135  80140 el_gallo_azul   36u     IPv4             244342      0t0      UDP greg-W2600CR.fritz.box:5060 
ekiga      80135  80141 el_gallo_azul   36u     IPv4             244342      0t0      UDP greg-W2600CR.fritz.box:5060 
ekiga      80135  80142 el_gallo_azul   36u     IPv4             244342      0t0      UDP greg-W2600CR.fritz.box:5060 
ekiga      80135  80143 el_gallo_azul   36u     IPv4             244342      0t0      UDP greg-W2600CR.fritz.box:5060 
ekiga      80135  80144 el_gallo_azul   36u     IPv4             244342      0t0      UDP greg-W2600CR.fritz.box:5060 
ekiga      80135  80145 el_gallo_azul   36u     IPv4             244342      0t0      UDP greg-W2600CR.fritz.box:5060 
ekiga      80135  80146 el_gallo_azul   36u     IPv4             244342      0t0      UDP greg-W2600CR.fritz.box:5060 
gmain      80135  80152 el_gallo_azul   36u     IPv4             244342      0t0      UDP greg-W2600CR.fritz.box:5060 
ekiga      80135  80153 el_gallo_azul   36u     IPv4             244342      0t0      UDP greg-W2600CR.fritz.box:5060 
ekiga      80135  80811 el_gallo_azul   36u     IPv4             244342      0t0      UDP greg-W2600CR.fritz.box:5060 
ekiga      80135  80812 el_gallo_azul   36u     IPv4             244342      0t0      UDP greg-W2600CR.fritz.box:5060 
ekiga      80135  80814 el_gallo_azul   36u     IPv4             244342      0t0      UDP greg-W2600CR.fritz.box:5060 
ekiga      80135  80816 el_gallo_azul   36u     IPv4             244342      0t0      UDP greg-W2600CR.fritz.box:5060 
ekiga      80135  80817 el_gallo_azul   36u     IPv4             244342      0t0      UDP greg-W2600CR.fritz.box:5060 

I see that "fritz.box" appears in each of those lines, but I don't know what it means. It's probably just because my Fritz!Box is my ADSL modem, so that is the device using the port.

I also see that all of the lines start with "ekiga", which is probably desirable, but there are other lines that start with "dconf", "gdbus", "threaded-", and "gmain".

The results of the same command after quitting Ekiga: Nothing.

I am still getting "Could not register (Globally not acceptable)" in Ekiga>Edit>Accounts.

I'll submit another -d 4 log.
Comment 10 el_gallo_azul 2013-10-30 01:17:21 UTC
Created attachment 258505 [details]
Another -d 4 log
Comment 11 Eugen Dedu 2013-10-30 06:08:09 UTC
The same error appears in previous attachment.

Can you try http://wiki.ekiga.org/index.php/Troubleshooting#FRITZ.21Box_Fon_users ?
Comment 12 el_gallo_azul 2013-10-30 07:04:02 UTC
My reply to your suggestion in Comment 8 appears in Comment 9, before I attached another -d 4 log.

I will go to the wiki you added to Comment 11.
Comment 13 el_gallo_azul 2013-10-30 07:06:21 UTC
PS Until I installed Ekiga on this new computer, I had used Ekiga 3.2.x for years with my Fritz!Box on Ubuntu 12.04.

Now I'll go that wiki.
Comment 14 el_gallo_azul 2013-10-30 07:38:08 UTC
"Cure: In Fritz!Box Fon, add to the "List of port forwardings" ("Liste der Portfreigaben") five entries: Open ports 5061-5065 for UDP protocol. This will provide a reliable (two-way) telecommunication line when you call Ekiga."

In my Fritz!Box interface, there doesn't seem to be anywhere to specify port numbers.

I attach two screenshots of Fritz!Box 7390 Port Forwarding.

When I create New Port Forwarding, I can change three things:
1. Port forwarding enabled for:
2. To computer:
3. To IP address:

Port forwarding enabled for: drop-down list has seven options: FTP server, HTTP server, eMule TCP, eMule UDP, MS Remote Desktop, Other applications, Exposed Host.

I can choose Other applications, call it "Ekiga", and add from port 5061 through port 5065, but I need to specify "to Port" (default 80) "through port84" (also default).

I did all that, applied the changes, started Ekiga again, but received the same error message from Ekiga and the same Registration status as at the start of this bug 711042.

I attach a screenshot of the error message.
Comment 15 el_gallo_azul 2013-10-30 07:39:27 UTC
Created attachment 258522 [details]
Comment 14: Fritz!Box port forwarding screen
Comment 16 el_gallo_azul 2013-10-30 07:40:18 UTC
Created attachment 258523 [details]
Comment 14: Fritz!Box New Port Forwarding
Comment 17 el_gallo_azul 2013-10-30 07:40:59 UTC
Created attachment 258524 [details]
Comment 14: Eki8ga registration error (again)
Comment 18 el_gallo_azul 2013-10-30 21:39:12 UTC
Created attachment 258615 [details]
Fritz!Box Port Forwarding Settings screen after configuring port forwarding
Comment 19 el_gallo_azul 2013-10-30 21:40:58 UTC
I've tried it with (a) "Allow changes to security settings over UPnP" enabled; and (b) "Allow changes to security settings over UPnP" disabled; with the same result.
Comment 20 el_gallo_azul 2013-11-03 03:19:32 UTC
I am still not able to use Ekiga on this computer.

I tried deleting the port forwarding that I had set up in Comment 14, but it didn't make any difference.

I have no other way set up on this computer to use SIP.
Comment 21 el_gallo_azul 2013-11-03 06:54:31 UTC
PS: I have three SIP accounts:

1. Is my home landline telephone number
2. Is my diamondcard call-out account
3. Is my ekiga.net account.

Using my computer previous to this one, I used to always leave those three SIP accounts enabled, and the Ekiga application would register my ekiga.net account successfully.

Since Comment 1 or 2 of this Bug 711042, I have had the ekiga.net SIP account disabled in my FritzBox, in order to have one less variable in the equation.

I attach screenshots of:

1. All three SIP accounts registered in my FritzBox. The green circle means that the SIP account is registered.
2. The same but with the ekiga.net SIP account disabled.
3. The Ekiga application successfully registering my diamondcard SIP account, despite my FritzBox having also just registered it successfully seconds beforehand.
Comment 22 el_gallo_azul 2013-11-03 06:55:28 UTC
Created attachment 258835 [details]
All three SIP accounts registered in my FritzBox
Comment 23 el_gallo_azul 2013-11-03 06:56:40 UTC
Created attachment 258836 [details]
FritzBox SIP accounts with the ekiga.net SIP account disabled
Comment 24 el_gallo_azul 2013-11-03 06:57:26 UTC
Created attachment 258837 [details]
Ekiga application successfully registering my diamondcard SIP account, despite my FritzBox having also just registered it successfully seconds beforehand
Comment 25 Eugen Dedu 2013-11-03 18:01:54 UTC
Before analysing more this bug, could you tell me if the computer where ekiga works is in the same network?  If yes, could you send me a -d 4 log for that comoputer, so that I compare them?
Comment 26 el_gallo_azul 2013-11-04 01:19:38 UTC
Yes my old computer is in the same network. I will attach the -d 4 log now.

I can confirm that it was successfully registering on my ekiga.net SIP account.
Comment 27 el_gallo_azul 2013-11-04 01:21:57 UTC
Created attachment 258893 [details]
-d 4 log for Ekiga 3.3.2 on Ubuntu 12.04 on my old computer
Comment 28 el_gallo_azul 2013-11-14 01:53:23 UTC
Any news on this one? I am still unable to use Ekiga because I cannot register my ekiga.net account.
Comment 29 Eugen Dedu 2013-11-14 08:40:19 UTC
I will work on it as soon as I find the time...
Comment 30 el_gallo_azul 2013-11-14 22:54:11 UTC
Thanks Eugen you champion.
Comment 31 Eugen Dedu 2013-11-20 16:10:44 UTC
I think there is a timing issue, your new computer is faster than the older one.

What does
gconftool-2 -g /apps/ekiga-snapshot/protocols/ports/udp_port_range
show?

If it shows
5060:5100
please quit ekiga, replace 5060 by 5061 using:
gconftool-2 -s /apps/ekiga-snapshot/protocols/ports/udp_port_range --type string 5061:5100
restart ekiga and attach a new -d 4 log if the issue persists.
Comment 32 el_gallo_azul 2013-11-21 03:48:39 UTC
Yes my new computer is 36506/960 = 38.0271 times faster (based on Geekbench benchmark scores).

With Ekiga running or not running:

gconftool-2 -g /apps/ekiga-snapshot/protocols/ports/udp_port_range

gives

No value set for `/apps/ekiga-snapshot/protocols/ports/udp_port_range'
Comment 33 el_gallo_azul 2013-11-24 03:41:05 UTC
Whoops I ended up trying again today, but I copied the wrong line and set the range to 5060:5100.

I'll get a -d 4 log anyway, in case it's of any use.

...

I attach the -d 4 log after (accidentally) setting the port range.
Comment 34 el_gallo_azul 2013-11-24 03:42:02 UTC
Created attachment 261335 [details]
-d 4 log after accidentally setting the port range
Comment 35 el_gallo_azul 2013-11-24 03:45:46 UTC
PS It still behaves in exactly the same way. ie. It does not register my ekiga.net account.
Comment 36 el_gallo_azul 2013-12-03 07:41:53 UTC
I don't know if it makes any difference, but last week I entered BIOS and enabled Virtualization on my computer. I attach another -d 4 log.
Comment 37 el_gallo_azul 2013-12-03 07:43:47 UTC
Created attachment 263375 [details]
-d 4 log after enabling Virtualization on computer
Comment 38 el_gallo_azul 2014-04-27 02:06:40 UTC
FYI:

I reinstalled Ubuntu 14.04, and Ekiga 4.0.1, two days ago. I have just started Ekiga for the first time, entered my details for my Ekiga account and my diamondcard account, and both accounts are now showing as registered.

This bug no longer occurs, and may be closed.
Comment 39 el_gallo_azul 2014-04-27 02:09:38 UTC
I meant to say 14.04. I had updated from Ubuntu 13.04 to 13.10, and then later from Ubuntu 13.10 to Ubuntu 14.04. A lot of things had stopped working during these two updates but things are working much better now since my re-installation of 14.04.
Comment 40 Eugen Dedu 2014-04-27 17:41:32 UTC
Great!