On 09/25/2012 11:49 AM, Jonathan Rose wrote:
Jonathan Rose wrote:

Sean Darcy wrote:

I'm building asterisk 11 beta 2. I've been using silk a lot. I
don't
see
silk listed in menuselect as a codec. But I also don't see an
asterisk
11 silk codec on
http://downloads.digium.com/pub/telephony/codec_silk.

Do we use the asterisk 10 codec_silk.so ?

sean

https://wiki.asterisk.org/wiki/display/AST/Asterisk+10+Codecs+and+Audio+Formats

See the bottom blurb in particular --

* The SILK licensing, like the licensing for Polycom's Siren 7
G.722.1 and Siren 14 G.722.1C codecs, requires that the distribution
of binary codec modules that can be used by Asterisk. To download
the SILK codec module for Asterisk, browse to
http://downloads.digium.com/pub/telephony/codec_silk/unsupported/asterisk-10.0/
and drop the untar'd .so file into /usr/lib/asterisk/modules and
issue an Asterisk restart, or simply load the codec module from the
Asterisk CLI

Actually, it seems that link provided is a little incorrect and the
actual codec modules are available here:
http://downloads.digium.com/pub/telephony/codec_silk/asterisk-10.0/

These modules are actually compiled for Asterisk 10 rather than 11,
but the architecture for codec translators remains largely
unchanged, so I would guess it'll probably work. Probably.

I've been informed that this probably won't actually work due to other
changes that were probably made in resources that codecs tend to rely
on, so take the above with a grain of salt. However, I'm also hearing
that a SILK codec for 11 may be released once 11 is out of beta.


OK. I'll wait on 11 for the silk codec.

Thanks for the quick response.

sean


--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
              http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users

Reply via email to