<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
        {font-family:Wingdings;
        panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
        {font-family:Wingdings;
        panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p
        {mso-style-priority:99;
        mso-margin-top-alt:auto;
        margin-right:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
span.EmailStyle17
        {mso-style-type:personal-compose;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
.MsoChpDefault
        {mso-style-type:export-only;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
        {page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Hi,<o:p></o:p></span></b></p>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p> </o:p></span></b></p>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>I
asked this on asterisk-users list but did not get a definitive answer. On 1.6.2,
does Meet-me bridge support native WB mixing (meaning no downscaling to SLIN)
for G722 or any other WB codec ? I tried 1.6.2 Beta3 but it sounded like it was
still doing a downgrade to SLIN first.<o:p></o:p></span></b></p>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p> </o:p></span></b></p>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p> </o:p></span></b></p>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Thanks,<o:p></o:p></span></b></p>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Serhad
Doken<o:p></o:p></span></b></p>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p> </o:p></span></b></p>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>--------</span></b><b><span
style='font-size:10.0pt;font-family:Wingdings'>à</span></b><b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p></o:p></span></b></p>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p> </o:p></span></b></p>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
asterisk-users-bounces@lists.digium.com
[mailto:asterisk-users-bounces@lists.digium.com] <b>On Behalf Of </b>Michael
Graves<br>
<b>Sent:</b> Thursday, June 18, 2009 4:06 PM<br>
<b>To:</b> Asterisk Users Mailing List - Non-Commercial Discussion<br>
<b>Subject:</b> Re: [asterisk-users] Wideband (G722) MeetMe<o:p></o:p></span></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:10.0pt'>I'm
told that Asterisks wideband capability is exclusively based upon 16 khz
sampling. Higher sampling rates, like you might find with CELT, are downsampled
for mixing at 16 khz.<br>
<br>
My guess is that not everyone will be happy with this, especially vendors
trumpeting codecs with higher sampling rates. To handle their output will be more
CPU intensive.<br>
<br>
I'm not an Asterisk insider. I just listen closely when the real insiders speak
up ;-)<br>
<br>
Michael<br>
<br>
--Original Message Text---<br>
<b>From:</b> Doken, Serhad<br>
<b>Date:</b> Thu, 18 Jun 2009 14:15:42 -0700<br>
<br>
<br>
<br>
Thanks Michael. I guess prior to 1.6.2, Asterisk was downgrading streams to
SLIN before mixing and then mixed stream got upgraded to WB. <br>
<br>
<br>
<br>
My question is, with this release, is Asterisk converting WB codecs to SLIN16
and mix them that way ? That seems to be the logical way to me just wanted an
insider expert to confirm/deny that. <br>
<br>
<br>
<br>
Is this the right list to ask that question/find the right contact before I
delve into the code knee deep ? <br>
<br>
<br>
<br>
Serhad Doken <br>
<br>
<br>
<br>
<b>From:</b> asterisk-users-bounces@lists.digium.com
[mailto:asterisk-users-bounces@lists.digium.com] <b>On Behalf Of </b>Michael
Graves<br>
<b>Sent:</b> Thursday, June 18, 2009 6:14 AM<br>
<b>To:</b> Asterisk Users Mailing List - Non-Commercial Discussion<br>
<b>Subject:</b> Re: [asterisk-users] Wideband (G722) MeetMe <br>
<br>
<br>
<br>
<br>
<br>
--Original Message Text---<br>
<b>From:</b> Doken, Serhad<br>
<b>Date:</b> Wed, 17 Jun 2009 16:07:12 -0700<br>
<br>
<br>
<br>
Hi, <br>
<br>
I wanted to follow up on this thread about WB support on the MeetMe bridge that
is in 1.6.2. Does it only work for G722 or any WB codec ? <br>
<br>
I am working with another 16k WB codec that I can transcode to 722 and vice
versa. I was curious if the 1.6.2 MeetMe bridge can also mix 722 with any other
WB codec natively(without downscaling). <br>
<br>
Thanks, <br>
<br>
Serhad Doken <br>
<br>
While not an expert in Asterisk internal, it seems unlikely that Asterisk is
mixing signals in encoded space. It's most likely converting the stream to slin
for mixing then encoding back into whatever is most appropriate for each
end-point.<br>
<br>
Michael <br>
<br>
--<br>
Michael Graves<br>
mgraves<at>mstvp.com<br>
http://blog.mgraves.org<br>
o713-861-4005<br>
c713-201-1262<br>
sip:mgraves@mstvp.onsip.com<br>
skype mjgraves<br>
fwd 54245 <br>
<br>
</span><o:p></o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:10.0pt;
font-family:"Arial","sans-serif";color:#000001'>--<br>
Michael Graves<br>
mgraves<at>mstvp.com<br>
http://blog.mgraves.org<br>
o713-861-4005<br>
c713-201-1262<br>
sip:mgraves@mstvp.onsip.com<br>
skype mjgraves<br>
fwd 54245<o:p></o:p></span></p>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Doken, Serhad <br>
<b>Sent:</b> Wednesday, June 17, 2009 4:07 PM<br>
<b>To:</b> 'asterisk-users@lists.digium.com'<br>
<b>Subject:</b> Re: [asterisk-users] Wideband (G722) MeetMe<o:p></o:p></span></p>
<p class=MsoNormal><o:p> </o:p></p>
<p>Hi,<o:p></o:p></p>
<p>I wanted to follow up on this thread about WB support on the MeetMe bridge
that is in 1.6.2. Does it only work for G722 or any WB codec ? <o:p></o:p></p>
<p>I am working with another 16k WB codec that I can transcode to 722 and vice versa.
I was curious if the 1.6.2 MeetMe bridge can also mix 722 with any other WB
codec natively(without downscaling).<o:p></o:p></p>
<p>Thanks,<o:p></o:p></p>
<p>Serhad Doken<o:p></o:p></p>
<p>----------------<span style='font-family:Wingdings'>à</span><o:p></o:p></p>
<p>Razza wrote: <o:p></o:p></p>
<p>If so, i’ve also read that Joshua Colp was/is working on a replacement
(conf_bridge?) that works with G722. If this is this still in active
development are there any planned timelines? If it’s in 1.6.0.6, and
i’ve just missed it or it’s been renamed please be nice in your
responses! :o) <o:p></o:p></p>
<p>It was just merged into Asterisk SVN trunk, on its way to becoming part of
Asterisk 1.6.2. It's new and still has some limitations, but progress is being
made and we welcome additional testing! <o:p></o:p></p>
<p class=MsoNormal>-- Kevin P. Fleming Digium, Inc. | Director of Software
Technologies 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA skype:
kpfleming | jabber: <a href="mailto:kpfl...@digium.com">kpfl...@digium.com</a>
Check us out at <a href="http://www.digium.com">www.digium.com</a> & <a
href="http://www.asterisk.org">www.asterisk.org</a><o:p></o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p>
</div>
</body>
</html>