Re: [Ekiga-list] Why does Ekiga not reconnect?

[Christian Jaeger <chrjae gmail com>]

> The best is to start ekiga with "ekiga -d 4 2>output" and post a bug
> report with the output.  We will analyse it and probably send it
> upstream (opal).

I will do that as soon as I find time (I'll be busy and hope I won't 'forget').

>
>> Why is this? It has been this way for a long time, and it was actually
>> one of the major reasons that I moved to using Twinkle about 9 months
>> ago. I would expect that this is easily fixable?
>
> I appreciate, Christian, the comments you make on this list.  But we
> have been in lack of man power from several months (not to say a few
> years).  We would like to do it better, but we do not have enough time.
>  Really.

Now that sound actually works well (thanks to the alternative sound
system), the dreadful locking issues have gone (thanks to the script
or now the alternative sound system) and current Ekiga (Debian package
version 3.2.6-1) never crashed so far and has a nice interface,
there's not much left to be desired for me! This bug is the only
remaining one that bothers me. If there's an improvement I would wish
for then it's to display somehow that someone has called while I was
away (in the taskbar icon, or by leaving open the call popup or so).

(Hm well in one of the networks where I've tried to use it, Ekiga
won't work, while Twinkle does, but I think Twinkle also only manages
to be reachable by the Diamondcard service (by virtue of the periodic
keep alive packets it sends) and not other clients. Anyway I'm
planning to solve these issues and the missing encryption to
Diamondcard soon by using a VPN to my home router/server.)

Christian.