Bug#538738: ekiga: Can not register (timeout) on 3.2.1~git20090515.9d0263-1
Eugen Dedu
Eugen.Dedu at pu-pm.univ-fcomte.fr
Fri Oct 9 10:36:52 UTC 2009
This bug might have been fixed, could you please check with the new
3.2.6 ekiga in unstable?
Cheers,
Eugen
ael wrote:
> Eugen Dedu wrote:
>>
>> This is a known issue: http://bugzilla.gnome.org/show_bug.cgi?id=579938
>
> Ok. Maybe this bug is now just a reference to that one.
>
>> In ekiga v3 you can contact people in your network (LAN), through avahi.
>
> Ok. That explains the reserved 192.168.*.* local address.
>
>> According to my limited ekiga knowledge, ekiga v3 starts registration
>> on all the interfaces. However, the SIP server should have retained
>> only one (again, I might be wrong, I do not know much of SIP).
>
> I *think* sipgate are using asterisk, maybe modified, but I am not sure.
> As far as I can tell, sipgate calls are working (echo tests ok), so
> maybe it is harmless.
>
>> So what is bug now? Is it that upon changing version, ekiga should be
>> started twice?
>
> As above, I think it is just a reference to the upstream bug. Perhaps it
> should stay open until the upstream bug is closed?
More information about the pkg-gnome-maintainers
mailing list