Re: [GnomeMeeting-devel-list] Can't register to Digisip
- From: Damien Sandras <dsandras seconix com>
- To: GnomeMeeting development mailing list <gnomemeeting-devel-list gnome org>
- Subject: Re: [GnomeMeeting-devel-list] Can't register to Digisip
- Date: Sat, 10 Dec 2005 18:15:10 +0100
Hi,
Le vendredi 09 décembre 2005 à 18:39 +0100, cooky hey shacknet nu a
écrit :
> Hello! I've tried newest build by Thursday late evening. The problem
> with registration lock-up seems solved now. Thanks! I wonder though,
> shouldn't the status field in the account editor get cleared when you
> unregister, instead of leaving the old message?
>
I could put a timeout to clear it. But leaving it with the last status
message is sometimes convenient.
> About the login problem, I learned that I was supposed to provide my
> PSTN phone number as "username" field, rather than the numerical ID that
> I used before. Using the phone number gives a message of "Registered"
> initially, and it enables me to recieve calls.
> But if I restart Gnomemeeting, it will then say "Registration failed:
> Forbidden" even though the same login data is used this second time. And
> I'm not very familiar with how SIP works, but despite the fact that I'm
> supposedly not registered, I can still recieve calls, and there is a
> message about 0 voicemails in the statusbar. Even if I delete the whole
> account, I can still recieve calls. This seems strange, but maybe it's
> how it's supposed to be?
It is strange. I guess your old registration is still active when it
happens. That would explain things.
> Anyway, I have noticed that I can obtain a correct login response again
> by:
> - switching back to the erroneous numerical user ID
> - try to log in, which naturally fails
> - change user ID back to my phone numer
> - try to log in, now it looks OK
> Could there be some bug in updating status changes for an account?
>
Actually not.
> Furthermore, I can't place outgoing calls at all. The error is "Security
> check failed". There is no difference when I try directly after a
> correct "Registered" status, or when in the dubious state as described
> before.
I need a debug 4 output :
gnomemeeting -d 4 > output.txt 2>&1
Without that, it is just blind guessing :)
> Also, when trying to place a call, the ringing-tone (native to GM) just
> goes on, but it's impossible to hang up. The GUI is still responsive,
> but it doesn't hang up when I choose that option from the menu. Then
> there will be a segfault automatically after some 40 seconds.
> What do you think is the problem?
I need a backtrace.
gdb gnomemeeting
run
(make it crash, then type:)
thread apply all bt
> /Eric
>
>
> ons 2005-12-07 klockan 12:52 +0100 skrev Damien Sandras:
> > Hello,
> >
> > Can you try again tomorrow with the new gnomemeeting version?
> > I have fixed something while eating my sandwich that will at least
> > prevent it to stay in the "Registering" state in your case :)
> _______________________________________________
> Gnomemeeting-devel-list mailing list
> Gnomemeeting-devel-list gnome org
> http://mail.gnome.org/mailman/listinfo/gnomemeeting-devel-list
--
_ Damien Sandras
(o-
//\ GnomeMeeting: http://www.gnomemeeting.org/
v_/_ FOSDEM 2006 : http://www.fosdem.org
SIP Phone : sip:dsandras gnomemeeting net
sip:600000 gnomemeeting net
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]