From: "hank smith" <hanksmith4@earthlink.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: VOIP and asterisk
Date: Thu, 22 Sep 2005 10:56:23 -0700 [thread overview]
Message-ID: <00a501c5bf9e$f2e06f60$821a3fce@ron0wrfld8igzk> (raw)
In-Reply-To: <20050922151138.GA3957@lnx3.holmesgrown.com>
www.voip-info.org
not .com
thanks
hank
----- Original Message -----
From: "Steve Holmes" <steve@holmesgrown.com>
To: <speakup@braille.uwo.ca>
Sent: Thursday, September 22, 2005 8:11 AM
Subject: Re: VOIP and asterisk
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
>
> I just tried this site and all I got was a line or two of German or some
> such, no links or anything. The header was "Untitled Document." Is
> this the correct address below? I tried this in elinks and lynx the cat
> with similar results. Haven't tried a winblows client yet.
>
> On Thu, Sep 22, 2005 at 10:07:45AM -0400, Janina Sajka wrote:
>> Go to http://www.voip-info.com and buy yourself a Snom 320. You'll never
>> look back.
>>
>> It's a desk phone that you configure using your web browser. The phone
>> runs Linux, and several of us are currently hacking on it to make it
>> even more accessible than it already is.
>>
>> Scott Howell writes:
>> > Some folks were good enough to share some info on list about VOIP, but
>> > what I am really interested in knowing is what hardware if any folks
>> > have used with Asterisk, is it wise to look at external hardware vs
>> > cards in the box, or any other bits I should know. Please write off
>> > list
>> > if you wish to save on list traffic.
>> > I'm looking into this as it seems for what I'm paying for regular
>> > service, I could do better with VOIP perhaps.
>> >
>> > tia
>> > Scott
>> >
>> >
>> > _______________________________________________
>> > Speakup mailing list
>> > Speakup@braille.uwo.ca
>> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>
>> --
>>
>> Janina Sajka Phone: +1.202.494.7040
>> Partner, Capital Accessibility LLC http://www.CapitalAccessibility.Com
>> Bringing the Owasys 22C screenless cell phone to the U.S. and Canada. Go
>> to http://www.ScreenlessPhone.Com to learn more.
>>
>> Chair, Accessibility Workgroup Free Standards Group (FSG)
>> janina@freestandards.org http://a11y.org
>>
>> _______________________________________________
>> Speakup mailing list
>> Speakup@braille.uwo.ca
>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>
>>
>
> - --
> HolmesGrown Solutions
> The best solutions for the best price!
> http://ld.net/?holmesgrown
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.7 (GNU/Linux)
>
> iD8DBQFDMsmqWSjv55S0LfERA0NAAJ9KbcLMkiqafgP+ZsJFnGP1wHymmwCgqQXA
> 0YN0CXOeXpSh5edSwKzUYkk=
> =5fPB
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
> --
> No virus found in this incoming message.
> Checked by AVG Anti-Virus.
> Version: 7.0.344 / Virus Database: 267.11.5/110 - Release Date: 9/22/2005
>
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
Scott Howell
` Janina Sajka
` Steve Holmes
` hank smith [this message]
` Janina Sajka
Dawes, Stephen
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='00a501c5bf9e$f2e06f60$821a3fce@ron0wrfld8igzk' \
--to=hanksmith4@earthlink.net \
--cc=speakup@braille.uwo.ca \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).