<div dir="auto">Solutions such as Jack are non-network oriented and severely limited in scalability. There are, of course, many other options, but the closest are chan_rtp and chan_nbs. RTP is a good option except for the difficulty for non-telephony people to interact with it. NBS is deprecated, undocumented, and unsupported by any locatable resources.<div dir="auto"><br></div><div dir="auto">While the original app interface from last year required dialplan, the channel interface does not. It is a plain channel which can be used by ARI directly.</div><div dir="auto"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jul 5, 2019, 15:28 Sylvain Boily <<a href="mailto:sylvain@wazo.io">sylvain@wazo.io</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
Hello Seán,<br>
<br>
<div class="m_-7160625712045487113moz-cite-prefix">On 2019-07-05 4:45 a.m., Seán C. McCord
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">A brief update:
<div><br>
</div>
<div>I have adapted my app_audiosocket from last year to become
chan_audiosocket, a full bidirectional audio channel interface
for Asterisk to any AudioSocket service (which itself is a
dead-simple implementation). I'll be demoing it in my talk
next week at CommCon, for anyone who might be interested. I'm
going to try to have it ready to push to gerrit for review
this weekend.</div>
</div>
</blockquote>
<br>
I'll be there.<br>
<blockquote type="cite">
<div dir="ltr">
<div><br>
</div>
<div>For now, you can see it in the 'channel' branch of <a href="http://github.com/CyCoreSystems/audiosocket" target="_blank" rel="noreferrer">github.com/CyCoreSystems/audiosocket</a>.</div>
</div>
</blockquote>
<br>
This is very different from what we did. You need dialplan to use
it. In our case we don't need any dialplan to use it, it's more ARI
approach.<br>
<br>
Sylvain<br>
</div>
</blockquote></div>