Re: [Ekiga-list] Incoming call failure with 3.1.1

[Alec Leamas <leamas alec gmail com>]

Damien Sandras wrote:
> Le jeudi 26 février 2009 à 10:30 +0100, Alec Leamas a écrit :
>  
> > Damien Sandras wrote:
> >    
> > > Le mercredi 25 février 2009 à 21:02 -0500, Mark T.B. Carroll a écrit :
> > >        
> > > > Damien Sandras <dsandras seconix com> writes:
> > > >
> > > >            
> > > > > Le jeudi 19 février 2009 à 00:32 -0500, Mark T.B. Carroll a écrit :
> > > > >                
> > > > > > 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,
> > > > > >                     
> > > > > There is a known problem with incoming calls and the current 
> > > > > snapshot. I
> > > > > will fix it this week-end.
> > > > >                 
> > > > Now with the 20090225 one, the incoming call does arrive (yay!), I hit
> > > > `accept', and it segfaults.
> > > >
> > > > I can still send my -d 4 output to somebody. (-:
> > > >             
> > > A gdb backtrace would be more useful.
> > >         
> > waiting for some kind of customer "service", taking a backtrace (yes, 
> > same problem, trunk as of yesterday).
> >     
>
> Despite trying 50 times, I can not reproduce it. Are you sure something
> is not corrupted?
>
> Eugen, can you reproduce it?
>   
Hm... I'm not the only one with this issue, seems to pop up now and 
then, last this morning. Is it the build options? It's all very simple 
for me: call 520 ekiga net, wait until there is a incoming call, see a 
coredump for either "Accept" or "Reject", doesn't seem to matter which.

configure:      dummy
      export PTLIBDIR=$$PWD;    \
      ./configure               \
         --prefix=/usr          \
         --libdir=/usr/lib64    \
         --enable-debug         \
         --enable-tracing       \
         --disable-static       \
         --enable-plugins       \
         --disable-oss          \
         --enable-v4l2          \
         --disable-avc          \
         --disable-v4l
hemulen ptlib-2.7.0$ svnversion
22117M            # Some trace/logging changes, I think they are under 
control...


./configure --prefix=/usr --libdir=%{_libdir} --enable-debug    # OPAL
hemulen opal-3.7.0$ svnversion
22117

================ Final configuration ===================
        Installing into prefix  :  /usr

                 GNOME support  :  disabled
                 GConf support  :  enabled
 Evolution-Data-Server support  :  enabled
                NOTIFY support  :  disabled
                  LDAP support  :  enabled

                XVideo support  :  enabled

                 H.323 support  :  yes
                   SIP support  :  yes

                  DBUS support  :  enabled
          DBUS service support  :  enabled
           mDNS/DNS-SD support  :  enabled
             GStreamer support  :  disabled
          KAddressBook support  :  disabled
                   KDE support  :  disabled
                  XCAP support  :  disabled
             libnotify support  :  disabled

                       OS Type  :  linux-gnu
                  Machine Type  :  x86_64
                    Byte Order  :  little endian

If all settings are OK, type make and make install
========================================================
$ svnversion
7694