Re: [GnomeMeeting-list] ekiga: registration failed/Nat detection

[Damien Sandras <dsandras seconix com>]

Le vendredi 17 mars 2006 à 19:15 +0100, Anthony Mahé a écrit :
> Actually, my current situation has changed a bit today. I've installed
> the 2.0.1 for breezy version and now, the NAT detection works and
> detects "cone NAT" so that STUN has been enabled (don't know if it's a
> good news or not). My ekiga account is now recognized as well as the
> voipbuster one, which is amazing. Then, i've tried to call
> 500 ekiga net  I hear the ring tones, but it never stops ringing,
> something like my call never reaches its goal.
> 
> Should I try the -d 4 anyway?

Sure!

> 
> On 3/17/06, Damien Sandras <dsandras seconix com> wrote:
>         
>         Hi!
>         
>         Le vendredi 17 mars 2006 à 11:50 +0100, Anthony Mahé a écrit :
>         
>         > I have installed th cvs deb packages for breezy using the
>         repositories
>         > found on this website
>         (http://snapshots.gnomemeeting.net/#debian)
>         > My problem is that I can't register with my ekiga.net
>         account with
>         > ekiga. I have checked the password several times, checked I
>         can 
>         > connect to my account on the internet with the same one,
>         also tried
>         > with a simpler one (since I found in the archives somebody
>         fixed his
>         > problem that way), however, I still receive that
>         "registration failed" 
>         > timeout. Seems like I had no internet connection.
>         > Then, I remembered that, during the configuration Druid,
>         when I click
>         > on the "Detect Nat Type" button, nothing happens, I waited
>         for 10
>         > minutes without any change or response. This could be the
>         reason of my
>         > problem.
>         > I tried several tricks found on the internet such a "not
>         clicking the
>         > ekiga registration during the wizard and adding it
>         afterwards", but it 
>         > still fails.
>         
>         Wouldn't you be using Accessibility? Try deactivating it if it
>         is the
>         case. If not, then mail us a -d 4 debug output.
>         
>         > Is there a way to find out more precisely where does the
>         problem come 
>         > from (there is no error message in the terminal) and to fix
>         the
>         > problem?
>         >
>         > Thank you by advance
>         >
>         >
>         > Anthony
>         >
>         >
>         > _______________________________________________ 
>         > GnomeMeeting-list mailing list
>         > GnomeMeeting-list gnome org
>         > http://mail.gnome.org/mailman/listinfo/gnomemeeting-list
>         --
>         _      Damien Sandras
>         (o-
>         //\     Ekiga Softphone: http://www.ekiga.org/
>         v_/_    FOSDEM 2006    : http://www.fosdem.org/
>                 SIP Phone      : sip:dsandras ekiga net
>                                  sip:600000 ekiga net
>         
> _______________________________________________
> GnomeMeeting-list mailing list
> GnomeMeeting-list gnome org
> http://mail.gnome.org/mailman/listinfo/gnomemeeting-list
-- 
 _      Damien Sandras
(o-     
//\     Ekiga Softphone: http://www.ekiga.org/
v_/_    FOSDEM 2006    : http://www.fosdem.org/
        SIP Phone      : sip:dsandras ekiga net
                         sip:600000 ekiga net