If you can do this,it may help to resolve: - ekiga-config-tool --clean
 - ekiga-config-tool --fix-permissions
 - ekiga-config-tool --clean-schemas
 - ekiga-config-tool --install-schemas


--Disable the STUN support while running the configuration wizard;

--Make 2 new sip accounts and while running the configuration
wizard,register with one of the new users.

--Add a sip account to ekiga with authentication user being the same as user
name. If this doesn't help, probably there might be some library to be
installed to keep the values in the respective fields.

I have been able to run Ekiga 3.0.2 with H264 enabled on Ubuntu 8.10,8.04
without any similar issues.



On Fri, Jan 30, 2009 at 5:08 PM, Alec Leamas <leamas.a...@gmail.com> wrote:

> Thanks for your reply!
>
> First of all I should add that I'm on Fedora/X86_64.
>
> Did the ekiga-config-tool thing. After a reinstall, and disabling the stun
> server,  there is only two accounts: my ekiga account and an account at
> sip.mysecretary.net. Situation after a Chat | Quit + restart:
>
> - The data for both accounts is corrupted (password moved to
>  "Authentication User",  Password + Timeout set to random values).
>
> - The account is presented as "Registered" despite that it isn't logged in
> at the
>  server  (I can verify this on the server side  for the mysecretary
> account).
>
> - Invoking the Account | Edit Account dialog with correct, unchanged data
>  effectively toggles the account between Registered and Unregistered.
>
> - With data OK, successfully logged in to mysecretary.net and making
>  a Chat | Quit the server does not understand that the client is
> disconnected (still
>  presented as present/logged in by server). Possibly a server issue?
>
> - The server eventually understands that the client has disconnected after
> the
>  timeout specified fot the account.
>
> I have a feeling that there are at least two things here: data corruption
> and presence mgmt. But, I'm a newbie and should thus not have any feelings
> ;-)
>
> Damien Sandras wrote:
>
>> Le jeudi 29 janvier 2009 à 13:45 +0100, Alec Leamas a écrit :
>>
>>
>>> Oops, forgot...  Ekiga 3.0.2 on Fedora 10, updated as of today. The
>>> install is a clean install from Fedora's repositories.
>>>
>>>
>>>
>>
>> Try purging the configuration totally (ekiga-config-tool --clean) and
>> start from scratch. There is no known bug corrupting the accounts data.
>>
>>
>
> _______________________________________________
> ekiga-list mailing list
> ekiga-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/ekiga-list
>
_______________________________________________
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

Reply via email to