Re: [Ekiga-list] pb ekiga



Hello,

Last mail related to this� Dell laptop, Ekiga is connected and is working since this morning 1am!
Many thanks, without your help, i was going to wait the following version.

I did as you wrote :
1. ekiga-config-tool --clean
2. killall gconfd-2
3. I had to re-boot
4. it was OK

Conclusions/questions/suggestions
1. I did follow the route given by Ubuntu doc to load Ekiga 2.0.9
2. some time ago, Ekiga ver 2.0.3 was installed on this laptop without success, I gave up waiting for Feisty and installed the last Ekiga version with synamtic.
3. I did run a 'new' configuration for this 'new' version. It did not work. May I conclude that the 'old' configuration was still present (login was changed moving from the old to the new config).
4. support from ekiga provided the solution.
5. In terminal mode : ekiga debug -d > output.txt (gives all the informations for the experts)
6. solutions : see above
7. May I say that uninstalling Ekiga did not remove the old config. (this might happen for other applications and create the same pb?)
8. It might be a good thing to point out that possible config problem in the doc related to Ekiga (Ubuntu)? 

Now, I just have to convince more people to use Ekiga.  

Good work and thank's again,
Sinceraly

�

pierre dantzer wrote:
I will follow yours advices� and let you know about the results,

many thanks for your help


Damien Sandras wrote:
Le samedi 02 juin 2007 �7:49 +0200, pierre dantzer a �it :
  
What a fast answer. I wish I could analyse the file so quickly. 
    

You can see this :
-> REGISTER 
<- 401
-> REGISTER (authenticated)
<- 401

The server sends a second 401 after the authenticated REGISTER. This can
only be possible for 2 reasons :
- a bug in ekiga
- a bug in the server
- something wrong with the login / password

If there was a bug in ekiga or in the server, I suspect you would not be
the only one to complain about it, so I really think there is a problem
with the login/pass.

But as Jure explained, it is possible that some router in between is
rewriting the SIP packets, leading to the failure.

  
Then I must understand :
I have tried Ekiga some time ago, with the former  version 2.0.3. (may
be with edgy). I decided to comeback with the new version. Does it
mean that the former configuration was kept in memory, in some place?
    

Yes.

  
In that case how to recover the former login/pass, how to remake an
initialisation?

    

I think you can do :
stop ekiga
ekiga-config-tool --clean
killall gconfd-2
start ekiga

Hope it helps...
  


_______________________________________________ ekiga-list mailing list ekiga-list gnome org http://mail.gnome.org/mailman/listinfo/ekiga-list



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]