Eric Bishop
2007-Feb-15 14:42 UTC
[asterisk-users] Meetme - is this statement from the Wiki still true?
"The conference bridge runs Ulaw codec by default. If you let people connect with GSM or other codecs, Asterisk will use CPU power to convert audio between codecs" ... What about alaw channels is there any transcoding work being done there? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20070215/b81a7011/attachment.htm
Matthew Rubenstein
2007-Feb-15 15:51 UTC
[asterisk-users] Meetme - is this statement from the Wiki still true?
I don't know whether the Asterisk default codec is still ulaw or not, though I believe it is. But it doesn't matter. Any connection in the same call between multiple legs which each use a different codec, whether GSM or otherwise, will of course require Asterisk to consume CPU in transcoding between the two different encodings. Each leg gets a codec which transcodes to Asterisk's native encoding (which I believe is ulaw), in which encoding mixing and other signal processing is performed, before reencoding back into the encoding each leg uses. On Thu, 2007-02-15 at 15:31 -0700, asterisk-users-request@lists.digium.com wrote:> Date: Fri, 16 Feb 2007 08:42:49 +1100 > From: "Eric Bishop" <asterisk.eric@gmail.com> > Subject: [asterisk-users] Meetme - is this statement from the Wiki > still true? > To: "Asterisk Users Mailing List - Non-Commercial Discussion" > <asterisk-users@lists.digium.com> > Message-ID: > <4acda1b40702151342s5fccad40r5c47499b4675ed84@mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > "The conference bridge runs Ulaw codec by default. If you let people > connect > with GSM or other codecs, Asterisk will use CPU power to convert audio > between codecs" ... What about alaw channels is there any transcoding > work > being done there?-- (C) Matthew Rubenstein