On Mon, Dec 7, 2009 at 3:23 PM, Kevin P. Fleming <[email protected]> wrote: > As far as I am aware, for ITU-T compliance the codec only cares about 14 > significant bits, but the reference source code needs those 14 bits in > the *top* 14 bits of each 16-bit word that it supplies/produces. The > Asterisk implementation does not do any bit-shifting or masking at all, > and seems to interoperate with quite a few endpoints just fine, so > presumably that means it's the correct implementation :-)
Hi Kevin, Thanks for sharing that. What I found odd was that so many clients got distortion. It then became apparent that most were using pjsip. However, since then I spoke to someone who is NOT and they are getting distortion as well, presumably due to a similar problem. I've no experience with the Asterisk implementation, even in pass-though. I've heard that 1.6 can do it, I think. Best, Randy _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
