[Ekiga-list] Calls die after a couple of minutes
- From: alex <alex schlossadler net>
- To: ekiga-list gnome org
- Subject: [Ekiga-list] Calls die after a couple of minutes
- Date: Wed, 10 Oct 2007 23:32:10 +1000
Hi Guys,
Not real sure what is going on with this issue I have, but I will
attempt to describe it s best as I can. Me and another person both
registered on ekiga.net. I am using Ekiga 2.0.9 Under OpenSolaris x86.
The other person is using the current MS Windows (Under XP SP2) version
(downloaded today). After talking for a couple of minutes, I hear a loud
screeching sound, followed by a fast clicking noise and I can no longer
hear them. When this happens the other party doesn't hear the screeching
or clicking, it just appears I have gone 'silent' to them, and the only
way for them to be able to hear me, and for me to be to be able to hear
them again, is to hang up and start again. This seems to happen no
matter which codec I am using. The other party using the windows version
has advised me that when this happens, the program occasionally crashes
"Program has encountered a problem and needs to close". I have had no
crashes on my end. This issue has also occurred and the other party on
Windows has had NO crash and I have been able to call them straight back.
I don't know if the issue is on my side or theirs, I suspect theirs but
I am guessing.
I am unable to test with Ekiga 2.0.11 because pwlib refuses to build
under Solaris (its author has not tested adequately or has only tested
with an old version of solaris), ie: it does some really stupid things,
like try to use the -xO3 instead of -O3 flag with GCC, when that flag
only works with Sun's Compiler (which I am unable to get pwlib to build
with either), I got around this by editing one of the makefiles, only to
find that "gmake install" stuff's up too, and cant "stat" this file or
"stat" that directory and some other nonsense. So I have hit a brick
wall there. How do I contact the author of pwlib? Im, even willing to
give them ssh access to a Solaris 11 machine for testing if need be.
A bit of googling indicates others have reported similar issues, but I
could never really find any answer on resolving it. I guess the first
step is to find out who's side is having the issue, me or them?
Any suggestions appreciated.
Kind Regards
Alex
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]