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 622477 - H.323 accounts do not register properly.
H.323 accounts do not register properly.
Status: RESOLVED DUPLICATE of bug 592363
Product: ekiga
Classification: Applications
Component: Account stack
3.9.x
Other Linux
: Normal major
: ---
Assigned To: Ekiga maintainers
Ekiga maintainers
Depends on:
Blocks:
 
 
Reported: 2010-06-23 09:45 UTC by David Dahlberg
Modified: 2012-11-19 17:56 UTC
See Also:
GNOME target: ---
GNOME version: 2.29/2.30


Attachments
Ekiga 3.2.6 (Ubuntu Lycid) debug output (32.24 KB, text/plain)
2010-06-24 07:52 UTC, David Dahlberg
Details
Debug log of recent GIT version (24.00 KB, text/plain)
2010-06-24 08:00 UTC, David Dahlberg
Details
Debug (-4) log of 3.9.90 (Debian/experimental) (29.66 KB, text/plain)
2012-10-29 15:18 UTC, David Dahlberg
Details

Description David Dahlberg 2010-06-23 09:45:58 UTC
If I configure an H.323 account, this will not register properly at the gatekeeper.

What happens sometimes (ca. 50%+ of the cases):

On startup or on disabling enabling a H.323 account, it is shown as "registered", while in reality it is not registerd (no RAS messages are sent out by Ekiga, accordingly the Gatekeeper shows nothing either).

What happens on other times (ca. 50%- of the cases):

If I am disabling and enabeling the H.323 account, Ekiga finally registeres 
(sends RAS GRQ, RRQ, receives GCF, RCF).

Used version: 3.2.6-1ubuntu1 (from Ubuntu Lucid). Other versions which I do not remember at the moment used to have the same problem too, while some very old versions (2 years ago or so) used to work.
Comment 1 Eugen Dedu 2010-06-23 19:18:30 UTC
You need to send us the -d 4 output for such a case (and explain what's happening on this output).
Comment 2 David Dahlberg 2010-06-24 07:52:08 UTC
Created attachment 164476 [details]
Ekiga 3.2.6 (Ubuntu Lycid) debug output

Until 9:46: Startup, H.323 account shows up as "registered", but it is not.
From  9:46: I disabled/enabled the account, this time Ekiga registers correctly.
   While I had the impression, that "registered" shows up slightly earlier, than
   the registration procedure is really finished.
Comment 3 David Dahlberg 2010-06-24 08:00:13 UTC
Created attachment 164478 [details]
Debug log of recent GIT version

Until 9:53: Startup. No registering of the H.323 account.
            But this time at least the Ekiga tray icon shows an error 
            and reports "account inactive".
From  9:53: The account was disabled and enabled again.
            Ekiga stays on "account inactive".
            So no more H.323 :-(
Comment 4 Eugen Dedu 2012-10-27 17:50:38 UTC
David, sorry for taking so long to answer, I will be fast now.

There were many changes in the new release 3.9.90 (even compared to 3.0.0), please tell us if the bug is still there.  If yes, please post a -d 4 log.
Comment 5 David Dahlberg 2012-10-29 15:18:49 UTC
Created attachment 227543 [details]
Debug (-4) log of 3.9.90 (Debian/experimental)

Ekiga still does not register/does not send any packets to the
gatekeeper. All I can see, which looks a bit suspicious, is the
following debug message during startup:

| 2012/10/29 15:59:47.924         0:00.164
|    Error: cannot create presentity for h323:12345@127.0.0.1

Disabling/enabling the account fails without any output, not
even with "-d 999".

Used software version:
 * ekiga(-dbg) 3.9.90 from recent Debian/experimental
How to reproduce:
  * Create H.323 account "12345@127.0.0.1"
 (* Disable/enable account)

Regards
        David
Comment 6 Eugen Dedu 2012-11-19 17:56:56 UTC
Very likely a duplicate of 592363.

*** This bug has been marked as a duplicate of bug 592363 ***