[asterisk-dev] Audio to/from Asterisk
Borja SIXTO
borja.sixto at ulex.fr
Fri Aug 23 14:54:00 CDT 2019
Hi George,
Can you send the link (to the source for example) to check how it really
works ?
We already done streaming audio to/from Asterisk with MRCP (uniMRCP) or
with other Asterisk modules for example.
We want to evaluate the options from this new interface... to create
interactive services using STT/TTS, NLU/Chatbot or external processing APIs.
Regards,
Borja
Le 23/08/2019 à 19:43, George Joseph a écrit :
> The first implementation of External Media is up on Gerrit for review
> and testing.
> More information is on the wiki...
> https://wiki.asterisk.org/wiki/display/AST/External+Media+and+ARI
>
> The capability will be in 16.6 but since we're past the feature freeze
> date for Asterisk 17.0, the capability will be in Asterisk 17.1.
> Within the next few weeks, we should also have a sample ARI
> application available that sends the media off to Google for
> transcription and just dumps the text to a file.
>
> Please review! We need feedback!
>
>
>
>
> On Fri, Aug 16, 2019 at 4:58 AM Dan Jenkins <dan at nimblea.pe
> <mailto:dan at nimblea.pe>> wrote:
>
> Just caught up on this - makes sense to me.
>
> DNS is important
>
> transport - WSS to make it easy to just send binary down a WSS and
> have it secure.
>
> Dan
>
> On Wed, Aug 7, 2019 at 4:41 PM Seán C. McCord <ulexus at gmail.com
> <mailto:ulexus at gmail.com>> wrote:
>
> Sounds like good reasoning to me.
>
> On Wed, Aug 7, 2019, 11:23 Joshua C. Colp <jcolp at digium.com
> <mailto:jcolp at digium.com>> wrote:
>
> On Wed, Aug 7, 2019, at 12:18 PM, Seán C. McCord wrote:
> > I don't think checking channel events is too onerous,
> considering that
> > IP-based connections would be able to fail, too.
> >
> > As far as the ARI API: I don't really care that much,
> but is there a
> > reason to not simply use the existing channel
> tech/target syntax (e.g.
> > ExternalMedia/media.host.example.com:6645
> <http://media.host.example.com:6645>)?
>
> Cramming options in the future in a dial string makes
> things rather unfriendly (see chan_sip) - this is why I
> pushed for an explicit API to create such a thing. It's
> also more approachable, and easier to document.
>
> --
> Joshua C. Colp
> Digium - A Sangoma Company | Senior Software Developer
> 445 Jan Davis Drive NW - Huntsville, AL 35806 - US
> Check us out at: www.digium.com <http://www.digium.com> &
> www.asterisk.org <http://www.asterisk.org>
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by
> http://www.api-digital.com --
>
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-dev
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by
> http://www.api-digital.com --
>
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-dev
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-dev
>
>
>
> --
> *George Joseph*
> Digium - A Sangoma Company | Software Developer | Software Engineering
> 445 Jan Davis Drive NW - Huntsville, AL 35806 - US
> direct/fax: +1 256 428 6012
> Check us out at: https://digium.com <https://digium.com/> ·
> https://sangoma.com <https://sangoma.com/>
>
>
--
Borja SIXTO (co-founder/manager)
Mail: borja.sixto at ulex.fr
Tel: +33(0)4 28 35 03 44 Ext. 11
Cel: +33(0)6 77 37 90 42
Ulex Innovative Systems | 4 rue des Prairies, 38460 St Romain de Jalionas, France
www.ulex.fr
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20190823/6b48efb5/attachment-0001.html>
More information about the asterisk-dev
mailing list