[asterisk-app-dev] ARI Channel-Exec Suggestion

[Ben Langfeld]

Some thinking has gone into an interface like this as part of the Rayo
protocol (
http://xmpp.org/extensions/xep-0327.html#session-component-execution-prompt),
and might be useful as a template for a similar ARI/AMI interface.


On 7 March 2014 12:11, Matthew Jordan <mjordan at digium.com> wrote:

>
>
>
> On Fri, Mar 7, 2014 at 8:59 AM, Paul Belanger <
> paul.belanger at polybeacon.com> wrote:
>
>> On Fri, Mar 7, 2014 at 8:09 AM, Ben Merrills
>> <b.merrills at mersontech.co.uk> wrote:
>> > Can I pick back up on this then, and ask if there are any plans to
>> incorporate speech into ARI?
>> >
>> > We're using unimrcp at the moment for both ASR and TTS, and would love
>> to be able to access that functionality from ARI too.
>> >
>> > In terms of TTS, a short cut might be to include URIs in the audio
>> schema for Play(). This would allow you to easily integrate 3rd party TTS
>> engines that export wav/mp3 etc via a URI. Just a thought :)
>> >
>> I'll be actually going down this path sooner then later. Some of our
>> clients have been asking for this functionality and I've been checking
>> out unimrcp too. Like you I'm trying to best figure out how to
>> interface ARI with TTS / ARS.  I'd be interested to see how others are
>> doing this and see if we could get some sort of spec going.
>>
>>
> Prefacing this with IANAL...
>
> With regards to the unimrcp library in particular: The unimrcp library is
> licensed under the Apache license 2.0 [1]. This license is not compatible
> with the GPLv2 [2]. Linking to the unimrcp library would - as best as I can
> tell - violate the GPLv2 license due to the patent termination and
> indemnification provisions. Merely licensing an Asterisk module that uses
> said library as GPLv2 does not prevent the linkage from that module to said
> library from creating a derivative work - so releasing said modules as
> GPLv2 does not, as best as I can tell [3], remove the licensing issues.
> Based on this, using said modules in Asterisk is a violation of the GPL.
>
> More generally, yes, I would be interested in exposing Asterisk's generic
> speech recognition API through ARI. The first step on that would be to
> propose the API on this mailing list - preferably, a wiki page should be
> made on the Asterisk wiki here [4] as well.
>
> Matt
>
> [1] http://www.apache.org/licenses/LICENSE-2.0
> [2] http://www.apache.org/licenses/GPL-compatibility.html
> [3]
> http://www.unimrcp.org/announcements/unimrcppackageforasterisk100released
> [4] https://wiki.asterisk.org/wiki/display/AST/Asterisk+13+Projects
>
> --
> 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 at lists.digium.com
> http://lists.digium.com/cgi-bin/mailman/listinfo/asterisk-app-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-app-dev/attachments/20140307/8881c940/attachment.html>