[Ekiga-list] Ekiga very slow disconnecting



This refers to item 3 on the list.
I have noticed that the application actually does not disconnect at all when the called party, either human or answering machine, did not answer (off hook). In the event of no answer, I simply try to disconnect with ctrl D. It does not and I have to force a disconnect (force quit in Linux). This may be an anomaly in the application. I hesitate to call it a bug, since I do not know the inner functionalities of the application. I thought I let the developers know by way of this list.
Thank you for reading it.
Regards,
-hr


ekiga-list-request gnome org wrote:
Send ekiga-list mailing list submissions to
	ekiga-list gnome org

To subscribe or unsubscribe via the World Wide Web, visit
	http://mail.gnome.org/mailman/listinfo/ekiga-list
or, via email, send a message with subject or body 'help' to
	ekiga-list-request gnome org

You can reach the person managing the list at
	ekiga-list-owner gnome org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of ekiga-list digest..."


Today's Topics:

   1. Re: could not connect to remote host (Hazel Russman)
   2. Re: could not connect to remote host (yannick)
   3. Ekiga very slow disconnecting (H.Riesbeck)


----------------------------------------------------------------------

Message: 1
Date: Wed, 31 Oct 2007 16:37:37 +0000 (GMT)
From: Hazel Russman <hazel_russman yahoo co uk>
Subject: Re: [Ekiga-list] could not connect to remote host
To: ekiga-list gnome org
Message-ID: <655635 29604 qm web25009 mail ukl yahoo com>
Content-Type: text/plain; charset=iso-8859-1


   1. Could not connect to remote host (Hazel
Russman)
   2. Re: Could not connect to remote host (yannick)



----------------------------------------------------------------------
Message: 1
Date: Mon, 29 Oct 2007 16:53:06 +0000 (GMT)
From: Hazel Russman <hazel_russman yahoo co uk>
Subject: [Ekiga-list] Could not connect to remote
host
To: ekiga-list gnome org
Message-ID:
<264823 97234 qm web25012 mail ukl yahoo com>
Content-Type: text/plain; charset="iso-8859-1"

I am having difficulty in getting ekiga working. I
have an account at ekiga.net and it appears to be
valid as I can log in there. But when I try the echo
test, I get first "Registration failed - timeout"
and
then "Could not connect to remote host".

My setup: I am using Linux pppoe behind a SMC
Barricade adsl router/modem. This has a built-in
firewall (configurable via the web browser) but I
have
not changed its default settings. As far as I can
see,
it is not doing any packet filtering or nat,
although
there are timing checks to prevent DoS attacks. The
ekiga configuration druid's nat test reported "open
nat". I normally have a simple iptables-based
firewall
on the computer itself but I flushed it away before
testing ekiga.

I have looked at the ekiga manual but have not found
anything that looks relevant (apparently this error
message is sometimes caused by a nat problem but not
with open nat).

I attach the transcript of a level-4 debug run
(slightly edited for privacy) which I hope will be
useful for pinpointing what is going wrong.

Thanks in advance
Hazel


------------------------------
Message: 2
Date: Mon, 29 Oct 2007 18:31:57 +0100
From: yannick <sevmek free fr>
Subject: Re: [Ekiga-list] Could not connect to
remote host
To: Ekiga mailing list <ekiga-list gnome org>
Message-ID: <1193679117 7000 7 camel achille>
Content-Type: text/plain; charset=utf-8

Hi,

Maybe this wont solve your issue, you're using a
*very* old version of
ekiga (2.0.1), we now are up to 2.0.11

Consider upgrading it.

Regards,
Yannick


Thanks, Yannick. but that's not so easy. I am using
Ubuntu Dapper and this version is the latest that it
recognises (at least for my present list of
repositories). I notice that the version available
from ekiga.org is for Feisty. Would that one actually
run on Dapper if I installed it? Or would it be better
to download source and build it myself? I have a
little experience with building packages (though not
on Ubuntu) but I don't want to do anything that
involves upgrading libraries. You can really louse up
your system doing that kind of thing!


      ___________________________________________________________
Yahoo! Answers - Got a question? Someone out there knows the answer. Try it
now.
http://uk.answers.yahoo.com/

------------------------------

Message: 2
Date: Wed, 31 Oct 2007 18:32:52 +0100
From: yannick <sevmek free fr>
Subject: Re: [Ekiga-list] could not connect to remote host
To: Ekiga mailing list <ekiga-list gnome org>
Message-ID: <1193851972 12149 9 camel achille>
Content-Type: text/plain; charset=utf-8


Le mercredi 31 octobre 2007 ? 16:37 +0000, Hazel Russman a ?crit :
   1. Could not connect to remote host (Hazel
Russman)
   2. Re: Could not connect to remote host (yannick)



----------------------------------------------------------------------
Message: 1
Date: Mon, 29 Oct 2007 16:53:06 +0000 (GMT)
From: Hazel Russman <hazel_russman yahoo co uk>
Subject: [Ekiga-list] Could not connect to remote
host
To: ekiga-list gnome org
Message-ID:
<264823 97234 qm web25012 mail ukl yahoo com>
Content-Type: text/plain; charset="iso-8859-1"

I am having difficulty in getting ekiga working. I
have an account at ekiga.net and it appears to be
valid as I can log in there. But when I try the echo
test, I get first "Registration failed - timeout"
and
then "Could not connect to remote host".

My setup: I am using Linux pppoe behind a SMC
Barricade adsl router/modem. This has a built-in
firewall (configurable via the web browser) but I
have
not changed its default settings. As far as I can
see,
it is not doing any packet filtering or nat,
although
there are timing checks to prevent DoS attacks. The
ekiga configuration druid's nat test reported "open
nat". I normally have a simple iptables-based
firewall
on the computer itself but I flushed it away before
testing ekiga.

I have looked at the ekiga manual but have not found
anything that looks relevant (apparently this error
message is sometimes caused by a nat problem but not
with open nat).

I attach the transcript of a level-4 debug run
(slightly edited for privacy) which I hope will be
useful for pinpointing what is going wrong.

Thanks in advance
Hazel


------------------------------
Message: 2
Date: Mon, 29 Oct 2007 18:31:57 +0100
From: yannick <sevmek free fr>
Subject: Re: [Ekiga-list] Could not connect to
remote host
To: Ekiga mailing list <ekiga-list gnome org>
Message-ID: <1193679117 7000 7 camel achille>
Content-Type: text/plain; charset=utf-8

Hi,

Maybe this wont solve your issue, you're using a
*very* old version of
ekiga (2.0.1), we now are up to 2.0.11

Consider upgrading it.

Regards,
Yannick


Thanks, Yannick. but that's not so easy. I am using
Ubuntu Dapper and this version is the latest that it
recognises (at least for my present list of
repositories). I notice that the version available
from ekiga.org is for Feisty. Would that one actually
run on Dapper if I installed it? Or would it be better
to download source and build it myself? I have a
little experience with building packages (though not
on Ubuntu) but I don't want to do anything that
involves upgrading libraries. You can really louse up
your system doing that kind of thing!


Hi,

You can try this repository:
https://help.ubuntu.com/community/Ekiga?action=recall&rev=78#head-57385c7cf79361cbb4d7195b9f43c1bb33c1e94c
Regards,
Yannick

      ___________________________________________________________
Yahoo! Answers - Got a question? Someone out there knows the answer. Try it
now.
http://uk.answers.yahoo.com/ _______________________________________________
ekiga-list mailing list
ekiga-list gnome org
http://mail.gnome.org/mailman/listinfo/ekiga-list



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]