<!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"> 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> </body> </html>