public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Tyler Littlefield" <tyler@tysdomain.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: configuring asterisk:cheap phone?
Date: Fri, 17 Jul 2009 08:53:26 -0600	[thread overview]
Message-ID: <206B508E0D4F401B9B5F8A598E07F113@tdsdeb> (raw)
In-Reply-To: <20090717144851.GA23499@braille.uwo.ca>

hello,
I use the apt package, though I wouldn't do that on a production server; 
it's dependencies make no sense at all.
It wants xserver for asterisk, weird. :)

----- Original Message ----- 
From: "Terry D. Cudney" <terry.cudney@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Friday, July 17, 2009 8:48 AM
Subject: Re: configuring asterisk:cheap phone?


> Hi all,
>
>   It looks like there are a number of people here who are using or are 
> interested in voip.
>   Asterisk has a steep learning curve and I wouldn't recommend starting 
> into it if you are only going to use it for a short time. ON the other 
> hand, if you can justify the time to learn it, using straight asterisk 
> 1.4/1.6 is very accessible for us bliind users. All configs are text 
> files. Once you get a handle on it, setting up new phones/lines is very 
> quick and easy. If you are using Debian, there is an asterisk apt package 
> that does quite nicely fo rthe base asterisk installation.
>   I have not looked at the numerous  graphical configuration systems (like 
> pbxinaflash or trixbox). Perhaps some of you who have used some of these 
> could comment on their accessibility using commandline tools/speakup.
>   How many people here have asterisk (or other voip server) running that 
> we could maybe set up a "blinknet" based on iax2 (or even sip)?
>
>   Let's all thank Kirk for his liberality in not restricting postings here 
> to just speakup-related topics!
>
>   --terry
>
> -- 
> Name: Terry D. Cudney
> Phone: 705-812-4949
> SIP: 5000@cudney.homeip.net
> E-mail: terry@octothorp.org
>
> Having a smoking section in a restaurant is like...
> having a peeing sectionin a swimming pool.
>
> Tired of technology? Check this out: http://www.shibumi.org/eoti.htm
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup 


  reply	other threads:[~ UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Tyler Littlefield
 ` Alex Snow
     [not found] ` <20090716185927.GA9020@csy.ca>
   ` Tyler Littlefield
     [not found]     ` <20090716190441.GA9478@csy.ca>
       ` Tyler Littlefield
       ` Brent Harding
       ` Kerry Hoath
         ` Igor Gueths
           ` Tyler Littlefield
           ` Alex Snow
             ` Igor Gueths
   ` Gregory Nowak
     ` Brent Harding
 ` Brent Harding
   ` Tyler Littlefield
     [not found]   ` <20090716221652.GA18261@csy.ca>
     ` Terry D. Cudney
       ` Tyler Littlefield [this message]
     [not found]         ` <20090717153454.GA31988@csy.ca>
           ` Tyler Littlefield
       ` John covici
       ` Bill Cox

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=206B508E0D4F401B9B5F8A598E07F113@tdsdeb \
    --to=tyler@tysdomain.com \
    --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).