All of lore.kernel.org
 help / color / mirror / Atom feed
From: Margaret Leber <maggie@voicenet.com>
To: Tim Neu <tim@tneu.visi.com>
Cc: linux-hams@vger.kernel.org
Subject: Re: KDE EchoLinux client project
Date: Tue, 08 Apr 2003 11:52:39 -0400	[thread overview]
Message-ID: <3E92F047.4060605@voicenet.com> (raw)
In-Reply-To: 20030408142024.GA3921@leo.tneu.visi.com

Tim Neu wrote:

> I'd say most of us Linux folks would just be happy with something that
> works!    

Me too. I currently have EchoLinux (and EchoGUI, a sample client written 
in Xforms) installed on my 2.4.3-12 Red Hat system. Everything seem so 
work fine, except that I can't get any audio to transmit; receiveing 
works fine. The microphone otherwise works correctly. Linux audio is 
still a bit of a black art.

> Is the source code (or specifications) for Echolink available?    

My understanding is that there's not a lot of additional protocol 
layered on top of an H.323 core; the EchoLinux is built on the 
SpeakFreely project.

  73 de Maggie K3XS

-- 
-----/___.   _)   Margaret Stephanie Leber    / "The art of progress  /
----/(, /|  /| http://voicenet.com/~maggie   / consists of preserving/
---/   / | / |  _   _   _    `  _AOPA 925383/ order amid change and /
--/ ) /  |/  |_(_(_(_/_(_/__(__(/_  FN20hd / change amid order."   /
-/ (_/   '  K3XS  .-/ .-/    ARRL 39280   /___ --A.N.Whitehead ___/
/____ICQ 7161096_(_/_(_/__AMSAT 32844____/ <maggie@voicenet.com>



      parent reply	other threads:[~2003-04-08 15:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-07 21:52 KDE EchoLinux client project Michael Melanson
2003-04-08 11:21 ` John
2003-04-08 12:25   ` w9ya
2003-04-08 13:39     ` Hamish Moffatt
2003-04-08 14:20       ` Tim Neu
2003-04-08 15:26         ` John
2003-04-08 15:52         ` Margaret Leber [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3E92F047.4060605@voicenet.com \
    --to=maggie@voicenet.com \
    --cc=linux-hams@vger.kernel.org \
    --cc=tim@tneu.visi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.