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 585287 - only registers with one SIP account, other is unauthorized
only registers with one SIP account, other is unauthorized
Status: RESOLVED FIXED
Product: ekiga
Classification: Applications
Component: Account stack
GIT master
Other All
: Normal normal
: ---
Assigned To: Ekiga maintainers
Ekiga maintainers
Depends on:
Blocks:
 
 
Reported: 2009-06-09 21:34 UTC by Mark Carroll
Modified: 2009-11-11 22:05 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
registered with iptel, not ekiga (77.82 KB, text/plain)
2009-06-09 21:35 UTC, Mark Carroll
Details
registered with ekiga, not iptel (81.57 KB, text/plain)
2009-06-09 21:36 UTC, Mark Carroll
Details

Description Mark Carroll 2009-06-09 21:34:16 UTC
Please describe the problem:
Ekiga SVN used to register happily with both my iptel.org and ekiga.net SIP accounts. Now it only does one or the other: always one, never both.

Steps to reproduce:
Start Ekiga. Observe its account registration stuff. Peek in the accounts dialog to make sure.

Actual results:
It says `Could not register (Unauthorised)' for one account and `Registered' for the other.

Expected results:
Registers both, as it used to.

Does this happen every time?
Yes. It only registers one. Sometimes ekiga, sometimes iptel, no obvious pattern to which it'll be each time.

Other information:
I shall add -d 4 attachments for registering one and registering the other. Account details and other settings were the same for both runs.
Comment 1 Mark Carroll 2009-06-09 21:35:13 UTC
Created attachment 136232 [details]
registered with iptel, not ekiga
Comment 2 Mark Carroll 2009-06-09 21:36:07 UTC
Created attachment 136233 [details]
registered with ekiga, not iptel
Comment 3 Mark Carroll 2009-06-09 21:46:30 UTC
I ought to have mentioned that I am using the 20090603 SVN snapshot packaged for Debian.
Comment 4 Eugen Dedu 2009-07-25 20:24:26 UTC
Yes, I noticed it too, thanks Mark!

We will analyse the problem.
Comment 5 Eugen Dedu 2009-11-11 19:53:39 UTC
Hi Mark,

I think this bug has been fixed, could you please test with latest snapshots?

Thanks,
Eugen
Comment 6 Mark Carroll 2009-11-11 20:48:16 UTC
It already seems to be okay with the 3.2.6 I'm using from Debian. Sorry I didn't mention - I thought I had, but obviously not!
Comment 7 Eugen Dedu 2009-11-11 22:05:25 UTC
Well, this bug appeared on snapshots only, not on the stable branch.  Anyway, it was reproducible for me, and now it is not.  So letting it fixed.

Cheers,
Eugen