On Sun, Feb 16, 2014 at 8:27 PM, Matthew Jordan <mjordan@xxxxxxxxxx> wrote: > On Sun, Feb 16, 2014 at 10:45 AM, Ben Merrills > <b.merrills@xxxxxxxxxxxxxxxx> wrote: <snip> > I would much rather add resources for the kinds of functionality that > is needed, rather than expose the dialplan equivalents. TTS would be > fantastic to expose as a resource with supporting operations using > Asterisk's res_speech engine, which would make it agnostic of the TTS > engine. I *think* the UniMRCP libraries are built on this, since they > provide a res_speech_unimrcp library. Wrong acronym. This should say "Speech recognition would be fantastic to expose..." Text to speech would be nice as well, but a res_speech compatible module would not help you with that... -- Matthew Jordan Digium, Inc. | Engineering Manager 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA Check us out at: http://digium.com & http://asterisk.org _______________________________________________ asterisk-app-dev mailing list asterisk-app-dev@xxxxxxxxxxxxxxxx http://lists.digium.com/cgi-bin/mailman/listinfo/asterisk-app-dev
