[Ekiga-list] Incoming call failure with 3.1.1

["Mark T.B. Carroll" <mtbc ixod org>]

I have run through the configuration assistant thing from start to
finish. I can call the 500 ekiga net echo test and that works just fine.
However, calling the 520 ekiga net callback service has it hang up on me
and then ... nothing, though the -d 5 output shows that it is indeed
getting a callback initiated from from sip:500 ekiga net which is then
aborted. I am behind NAT and the router forwards incoming UDP from port
5060 to 5100 to the machine I'm using and acts as a gateway to let all
my outgoing packets out.

Should I gzip my -d 4 output and send it to somebody? I can also sniff
packets and send pcap files. I use Debian; software versions are,

ekiga-snapshot 0-20090214-1
evolution-data-server 2.22.3-1.1 
gconf2 2.24.0-6 
libatk1.0-0 1.22.0-1 
libavahi-client3 0.6.23-3lenny1 
libavahi-common3 0.6.23-3lenny1 
libavahi-glib1 0.6.23-3lenny1 
libc6 2.7-18 
libebook1.2-9 2.22.3-1.1 
libedataserver1.2-9 2.22.3-1.1 
libgcc1 1:4.3.2-1.1 
libgconf2-4 2.24.0-6 
libglib2.0-0 2.18.4-2 
libgtk2.0-0 2.14.7-2 
libldap-2.4-2 2.4.11-1 
libnotify1 0.4.4-3 
libopal-snapshot 0-20090214-1 
libpango1.0-0 1.22.4-2 
libpt-snapshot 0-20090214-1 
libpt-snapshot-plugins-a 0-20090214-1 
libpt-snapshot-plugins-v 0-20090214-1 
libsasl2-2 2.1.22.dfsg1-23
libsigc++-2.0-0c2a 2.0.18-2 
libstdc++6 4.3.2-1.1 
libx11-6 2:1.1.5-2 
libxext6 2:1.0.4-1 
libxml2 2.6.32.dfsg-5 
libxv1 2:1.0.4-1 

(Incidentally, quitting from Ekiga seems to cause a segfault. I don't
much mind that though.)

It's entirely plausible that I'm simply doing something dumb, as I've
never managed to get incoming calls working before.

Thanks,

Mark