<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=UTF-8" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> 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 : <pre wrap="">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 </pre> pierre dantzer wrote: <blockquote cite="mid4661B728.3090509@wanadoo.fr" type="cite"> <meta content="text/html;charset=UTF-8" http-equiv="Content-Type"> <title></title> I will follow yours advices and let you know about the results, many thanks for your help Damien Sandras wrote: <blockquote cite="mid1180801862.20693.10.camel@scorpion" type="cite"> <pre wrap="">Le samedi 02 juin 2007 à 17:49 +0200, pierre dantzer a écrit : </pre> <blockquote type="cite"> <pre wrap="">What a fast answer. I wish I could analyse the file so quickly. </pre> </blockquote> <pre wrap=""> 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. </pre> <blockquote type="cite"> <pre wrap="">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? </pre> </blockquote> <pre wrap=""> Yes. </pre> <blockquote type="cite"> <pre wrap="">In that case how to recover the former login/pass, how to remake an initialisation? </pre> </blockquote> <pre wrap=""> I think you can do : stop ekiga ekiga-config-tool --clean killall gconfd-2 start ekiga Hope it helps... </pre> </blockquote> <pre wrap=""> <hr size="4" width="90%"> _______________________________________________ ekiga-list mailing list <a class="moz-txt-link-abbreviated" href="mailto:ekiga-list@gnome.org">ekiga-list@gnome.org</a> <a class="moz-txt-link-freetext" href="http://mail.gnome.org/mailman/listinfo/ekiga-list">http://mail.gnome.org/mailman/listinfo/ekiga-list</a></pre> </blockquote> </body> </html>