> On 17/10/2016, at 9:51 AM, Jonathan H <lardconce...@gmail.com> wrote:
> Ah, no, you misunderstand. Asterisk wouldn't care one little bit what
> is on the page - Chromevox would do all that.
> A screenreader usually tabs or arrows their way about, selecting
> headings to read content.
> Thus, Asterisk ONLY needs to be able to hear content FROM the browser
> and pipe it to the channel, and pass keypresses back TO the browser.
> The human is the parser, if that makes sense?

Right, so you're using a prebuilt browser to do the parsing.

You'd really want to see if you can get ChromeVox as a library rather than as a 
browser though - otherwise you're going to be limiting yourself to using one 
concurrent channel and hacks like jack audio to move the audio from the browser 
to the channel.


Matt Riddell

http://www.venturevoip.com/news.php (Daily Asterisk News)
http://www.venturevoip.com/pabx_on_disk.php (PABX on a Disk)
http://www.venturevoip.com/exchange.php (Full ITSP Solution)
http://www.venturevoip.com/cc.php (Call Centre Solutions)

-- Bandwidth and Colocation Provided by http://www.api-digital.com --

Join the Asterisk Community at the 13th AstriCon, September 27-29, 2016

New to Asterisk? Start here:

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:

Reply via email to