Re: [Ekiga-list] Why my ekiga is continually trying to subscribe to my contacts telephone numbers ?

[Javier Barroso <javibarroso gmail com>]

Hi,

On Sun, Sep 26, 2010 at 1:07 PM, Jānis Rukšāns <thedogfarted gmail com> wrote:
> Hi,
>
>> I'm viewing too this in wireshark capture (continuously launching SIP
>> SUBSCRIBE REQUEST):
>>  198    6.674571        192.168.101.120 38.223.166.2    SIP     Request: SUBSCRIBE sip:javi xxxxx
>> 199     6.676041        10.4.0.120      38.223.166.2    SIP     Request: SUBSCRIBE sip:javi xxxxxx
>> 202     6.681867        192.168.101.120 38.117.97.125   SIP     Request: SUBSCRIBE
>> sip:javi yyyyyy
>> 203     6.683218        10.4.0.120      38.117.97.125   SIP     Request: SUBSCRIBE sip:javi yyyyy
>>
>> I'm viewing at least 4 ips against ekiga is trying to subscribe my contacts:
>> 38.117.97.125, 38.223.166.2, 40.233.138.214, 39.165.13.136
>>
>> I has only one account in my ekiga, and is to our internal asterisk.
>
> SUBSCRIBEs are sent to the server of the particular contact, not the
> server of your account. Those IPs should correspond to what xxxxxx and
> yyyyyy resolve to. Thus, if you have somecontact ekiga net, then the
> SUBSCRIBE will be sent to 86.64.162.35 (which is the IP of ekiga.net).
>
>> Can I configure ekiga to not do such things (subscribe to externals ips)?
>
> I'm not sure, but I think no, presence status can't be disabled.
Thank you, clarifying this, should be awesome that ekiga could offer this option



>
>> Anther issue, do you know why my linux is logging as two ip different
>> (10.4.0.120 and 192.168.101.120) ?
>>
>> My ip route config is:
>> $ ip route
>> 10.4.0.0/24 dev br-gest  proto kernel  scope link  src 10.4.0.120
>> 192.168.0.0/16 dev br-lan  proto kernel  scope link  src 192.168.101.120
>> default via 192.168.100.1 dev br-lan
>>
>> So I don't understand why connections to 38.223.166.2 goes sometimes
>> with my 10.4.0.120 ip ...
>
> I could be wrong (I'm not Ekiga developer), but here's my guess.
>
> First, SIP requires the sent message to contain the IP of the
> interface through which it was sent (in Via header). Therefore Ekiga
> can't send from 0.0.0.0 and let the kernel decide the source IP.
>
> Second, Ekiga doesn't "know" which interface (and therefore source
> address) will be used by the kernel for packets going to 38.223.166.2.
> AFAIK there is no way to query it; the other way would be to reproduce
> the kernel routing algorithm in Ekiga, which is impossible. Therefore
> Ekiga sends two copies of the message - one w/ 10.4.0.120 in Via and
> as the source address, and the other w/ 192.168.101.120.
>
> I'm not sure about the current version of Ekiga, but in older ones it
> was possible to specify which interface to use.
I will try changing ekiga/protocols/sip/listen_port gconf settings to
ip:port, but I'm not sure it will work.

Thank you very much!