In my case, I was trying to phone the ekiga echo service through a siproxd
server, but had
accidentally left my NAT set to "STUN" instead of "None". I therefore had no
hope of ever getting
a connection, and so ekiga just rang and rang... And I couldn't hang up. Ekiga
gave up eventually,
but it felt like longer than my configured 45 second timeout before it did so.
--- Damien Sandras <[EMAIL PROTECTED]> wrote:
> Le lundi 13 mars 2006 à 20:34 -0500, Allan a écrit :
> > On Monday 13 March 2006 20:05, Chris Rankin wrote:
> > > I have now installed ekiga, with siproxd on my NAT router as an outgoing
> > > proxy.
> > >
> > > First impressions are OK, although ekiga does seem unwilling to abort
> > > making a new connection when told to. I had forgotten to disable NAT when
> > > I
> > > switched to using siproxd, which meant that ekiga was trying in vain to
> > > create a new connection. However, it proved very difficult to tell ekiga
> > > to
> > > hang up - basically, it ignored the "hang-up" button.
> > >
> >
> > I have exactly the same problem.
> >
>
> I'm interested on a test case to reproduce that.
___________________________________________________________
To help you stay safe and secure online, we've developed the all new Yahoo!
Security Centre. http://uk.security.yahoo.com
_______________________________________________
GnomeMeeting-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/gnomemeeting-list
