Re: [GnomeMeeting-list] Security check fail 2 ;(

["W.P." <laurentp poczta onet pl>]

Użytkownik Damien Sandras napisał:

> Le dimanche 21 mai 2006 à 15:44 +0200, W.P. a écrit :
>  
>
> > > The realm is incorrect, it should be sip.actio.pl.
> > >
> > > You should report it to them.
> > >
> > >
> > >      
> > But have You remarked, that X-Lite sends INVITE WITH! authentication 
> > (same data that for REGISTER) BUT Ekiga sends INVITE WITHOUT! auth?
> > Don't know SIP protocol, so I don't which is correct.
> >
> >    
>
> Both are correct. However, when receiving the 401 Unauthorized, Ekiga
> doesn't know which one to use as it doesn't find a corresponding realm
> to the one in the response.
>
>  
I). By the way I found something that looks like bug:
When interface used by Ekiga is shut down and restarted with new IP 
address (likely case of ppp & mine) two things happen:
1). Ekiga still remembers old address, not just the interface name, so 
trying to do anything other than restart app is impossible.
2). Trying to stop Ekiga normally doesn't work, it partially desapears 
from system tray but still id on precess list. Normal kill helps.

II). Still awaiting response from operator. I've run one more test: I've 
replaced realm in configuration with digital IP address. Registeration 
works,
call-out fails as earlier and in trace there is STILL message:
"Couldn't find authentication information for realm 81.15.209.199, will 
use SIP Outbound Proxy authentication settings, if any"

III).
1). I've finally solved(?) problem with Sec.check message: I've put the 
REGISTAR field in Actio account IN NUMERCAL FORM!!!!!!
I think there is bug somewhere (may on both sides?) and consider it just 
as WORK-AROUND. Why? It seems Ekiga uses REGISTRAR field for looking up 
realm name, NOT the REALM field provided in configuration.
2). It worked for calling out address in xxxxxx sip actio pl (my GSM 
handset - at least signalling, didn't checked voice) but, this time 
trying to call echo proxy01 sipphone com failed with "Remote user 
rejected call" didn't traced it yet, so no more info. Call to this 
address was SUCCESFUL without PROXY ;)

I also got in trace that message (repeated several times) just after 
detection messages. Glib2 is 2.6.4-1.
---------- trace msg.
(ekiga:6833): GLib-GObject-CRITICAL **: g_object_unref: assertion 
`G_IS_OBJECT (object)' failed
---------- end trace msg.
What is this?