RE: [GnomeMeeting-devel-list] Bind to all interfaces

["Roman Skvirsky" <roman_skvirsky mail ru>]

Hello Damien,

Basically there is no problem that INVITE are sent to all interfaces. The
issue is implementation (as usual). I would say that adding synchonization
(mutex) to wait until ann INVITE are sent takes around 4-8 hours.

With best regards,
Roman Skvirsky  

>>-----Original Message-----
>>From: gnomemeeting-devel-list-bounces gnome org 
>>[mailto:gnomemeeting-devel-list-bounces gnome org] On Behalf 
>>Of Damien Sandras
>>Sent: Friday, December 02, 2005 11:34 AM
>>To: GnomeMeeting development mailing list
>>Subject: RE: [GnomeMeeting-devel-list] Bind to all interfaces
>>
>>Hello,
>>
>>Le vendredi 02 décembre 2005 à 01:35 +0300, Roman Skvirsky a écrit :
>>> Hello,
>>> 
>>> I would rather disagree that it is not possible to bind to 
>>all interfaces.
>>> The root cause of this issue is that ACK is received before 
>>the last INVITE
>>> is sent. I tried "durty hack" (am I wrong?) that wait 
>>(simple sleep() solves
>>> the issue) until all INVITEs are sent and only then process 
>>ACK messages.
>>> Where this can be counted a solution...
>>> 
>>
>>
>>Yes it is possible. The problem in such a case is that OPAL 
>>sends a PDU
>>with each of the interfaces as source.
>>
>>I do not know if it is the correct behavior or not. And I do not know
>>what the correct behavior should be. SER reacts reasonably well with
>>this, but not Asterisk, for example.
>>
>>Following Craig and Robert, it is not possible either to 
>>determine what
>>interface to use when a call is done.
>>
>>So I do not say it is not possible, I just do not know any solution to
>>the problem.
>>
>>> With best regards,
>>> Roman Skvirsky  
>>> 
>>> >>-----Original Message-----
>>> >>From: gnomemeeting-devel-list-bounces gnome org 
>>> >>[mailto:gnomemeeting-devel-list-bounces gnome org] On Behalf 
>>> >>Of Damien Sandras
>>> >>Sent: Friday, December 02, 2005 12:23 AM
>>> >>To: GnomeMeeting development mailing list
>>> >>Subject: Re: [GnomeMeeting-devel-list] Bind to all interfaces
>>> >>
>>> >>Le jeudi 01 décembre 2005 à 21:08 +0000, Conrad Beckert a écrit :
>>> >>> > don't know what the SIP behavior should be in that case 
>>> >>and I checked
>>> >>> > several clients that do the same than GnomeMeeting in 
>>such a case
>>> >>> > (kphone for example).
>>> >>> I wouldn't compete with kphone :-)  Would it be possible to 
>>> >>have the interface 
>>> >>> settings with the account configuration rather than globally?
>>> >>> 
>>> >>
>>> >>Unfortunately not...
>>> >>
>>> >>> I have a local gnugk gatekeeper, a gatekeeper at the 
>>> >>office, an Asterisk there 
>>> >>> also (through openvpn tunnel).  I might want to connect to 
>>> >>Sipgate directly 
>>> >>> also. 
>>> >>> 
>>> >>
>>> >>-- 
>>> >> _      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
>>> >>
>>> >>_______________________________________________
>>> >>Gnomemeeting-devel-list mailing list
>>> >>Gnomemeeting-devel-list gnome org
>>> >>http://mail.gnome.org/mailman/listinfo/gnomemeeting-devel-list
>>> >>
>>> 
>>> _______________________________________________
>>> 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
>>
>>_______________________________________________
>>Gnomemeeting-devel-list mailing list
>>Gnomemeeting-devel-list gnome org
>>http://mail.gnome.org/mailman/listinfo/gnomemeeting-devel-list
>>