Re: [Ekiga-list] Echo Test Failing



On 04/07/11 20:13, Rob Stone wrote:
On 04/07/11 11:34, Robert M. Riches Jr. wrote:
Date: Mon, 04 Jul 2011 09:57:03 +1000
From: Rob Stone<robstone mira net>
To: Ekiga mailing list<ekiga-list gnome org>

On 04/07/11 01:06, Eugen Dedu wrote:
On 01/07/11 19:36, Rob Stone wrote:
Running Ekiga 3.2.7 on Debian Linux Toshiba A200 laptop.

Output of uname -a

Linux roblaptop 2.6.39-2-686-pae #1 SMP Wed Jun 8 11:33:14 UTC 2011
i686
GNU/Linux

roblaptop:/var/log# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 002: ID 046d:0a01 Logitech, Inc. USB Headset
Bus 006 Device 002: ID 15ca:00c3 Textech International Ltd. Mini
Optical
Mouse
Bus 006 Device 003: ID 046d:089d Logitech, Inc. QuickCam E2500 series
Bus 002 Device 005: ID 03f0:5b11 Hewlett-Packard OfficeJet J2100
series
roblaptop:/var/log#


Start up Ekiga and it finally loads / appears. Initially it displays
that it cannot register my sip address, then it seems to register and
then it displays it cannot register another sip address
1 sip diamondcard us which has nothing to do with me.

You have certainly entered a "1" during Assistant Configuration by
error. Please remove that account from Edit->Accounts dialog.

If I then try to run the echo test nothing happens and the message
"call
failed" appears.

There is nothing in the logs to indicate exactly what "failed".

So, I cannot test out speech latency or whether the web cam is
functioning.

Please advise what other information you need.

We need -d 4 output to analyse the problem.



Hi Eugen,

I ran Ekiga as suggested and the output is humungous. I tried "catting"
it to a file but nothing was written to the file.
Even with the terminal window at its deepest, I can't copy and paste the
content from the very beginning.
As a rough guess, I'd say the last 4/5ths of the output is copyable.
Is that enough??

Cheers,
Rob

It appears Ekiga writes its debug to stderr. The method to
direct stderr to a file is shell-dependent. If you're using csh
or tcsh, this works:

ekiga -d 4> & ztest2

If you're using bash or one of its close relatives, this works:

ekiga -d 4 2&>ztest6

With a bit of luck, that will give you the complete output.

HTH

Robert Riches
rm riches jacob21819 net
_______________________________________________
ekiga-list mailing list
ekiga-list gnome org
http://mail.gnome.org/mailman/listinfo/ekiga-list


O.K. Debug log file attached.

After Ekiga started up I clicked on the "Echo Test", the little handset
image turned green and a few seconds later turned red and the message
"Call Completed" appeared in the status bar.
I then did Ctl+Q to end the program.

Hope this helps.

Sorry to answer so late.

There was a problem with echo test on the server, sometimes it brokes, we will hopefully upgrade it in 1-2 months. It has been working for a few days, so it should work now on your machine.

--
Eugen


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