<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:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
        {font-family:Helvetica;
        panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
        {font-family:Helvetica;
        panose-1:2 11 6 4 2 2 2 2 2 4;}
@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.EmailStyle18
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.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><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I was informed that the CCM-ACT’s will not support this Codec
either, so I was a bit annoyed by this as well. I would guess that the 6608
will probably fall in the same boat. It looks like DSP farms in routers
running IOS is the way that Cisco wants us to transcode in the future.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>MAtt<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<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"'>
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <b>On
Behalf Of </b>Jonathan Charles<br>
<b>Sent:</b> Friday, December 19, 2008 2:56 PM<br>
<b>To:</b> Ryan Ratliff<br>
<b>Cc:</b> cisco-voip@puck.nether.net<br>
<b>Subject:</b> Re: [cisco-voip] iLBC and Cisco 7965s...<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>Right, I found the same info...
it seems well supported in 12.4.15T and above in IOS (MGCP and H.323) but I
have been unable to find any info on transcoding/support on a 6608... my guess
is the DSPs can't handle the codec...<br>
<br>
Annoying.<br>
<br>
<br>
Jonathan<o:p></o:p></p>
<div>
<p class=MsoNormal>On Fri, Dec 19, 2008 at 1:31 PM, Ryan Ratliff <<a
href="mailto:rratliff@cisco.com">rratliff@cisco.com</a>> wrote:<o:p></o:p></p>
<div>
<p class=MsoNormal>Can't seem to find the 6608 downloads on <a
href="http://cisco.com" target="_blank">cisco.com</a> but the first place I see
that 6608 load is in a devpack from May of this year. That's actually a
lot newer than I would have thought.<o:p></o:p></p>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>The gist of my first email is that I don't think you're
going to see support for iLBC on the 6608. <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>Unity Connections 7.0(1) I can see supports iLBC, not sure
on the Unity TSP.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='color:#888888'><o:p> </o:p></span></p>
<div>
<p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:9.0pt;
font-family:"Helvetica","sans-serif";color:#888888'>-Ryan</span><span
style='color:#888888'><o:p></o:p></span></p>
</div>
<div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<div>
<p class=MsoNormal>On Dec 19, 2008, at 12:45 PM, Jonathan Charles wrote:<o:p></o:p></p>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><br>
Well, I am running CCM 7.0.1<br>
<br>
The 6608 is running D00404000032 (base load from ccm 7)<br>
<br>
Unity TSP is 8.3.1<br>
<br>
7965 is running 8.4.1S (iLBC was supported in 8.3)<br>
<br>
Not sure what TSP or 6608 load supports iLBC... <br>
<br>
<br>
<br>
Jonathan<br>
<br>
<br>
<o:p></o:p></p>
<div>
<p class=MsoNormal>On Fri, Dec 19, 2008 at 11:41 AM, Ryan Ratliff <<a
href="mailto:rratliff@cisco.com" target="_blank">rratliff@cisco.com</a>>
wrote:<o:p></o:p></p>
<div>
<p class=MsoNormal>What load is your 6608 running? What date was that
load released?<o:p></o:p></p>
<div>
<p class=MsoNormal>When did the IP phones start supporting iLBC?<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>I think the answer to those questions will tell you why you
can't get calls to your 6608 to use iLBC.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>As for Unity it just depends on if they have a TSP that
supports iLBC.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<div>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica","sans-serif"'>-Ryan</span><o:p></o:p></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<div>
<div>
<div>
<p class=MsoNormal>On Dec 19, 2008, at 12:33 PM, Jonathan Charles wrote:<o:p></o:p></p>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><br>
OK, so how do we get this to work...?<br>
<br>
I have Cisco 7965s at remote sites (user's homes) and when they make calls,
their codec is showing up as G.729, even tho their region is iLBC (G.728).<br>
<br>
My voice gateway is a 6608 (single PRI, rest are transcoders, conf bridges)...<br>
<br>
Calls to Unity use G.729 as well...<br>
<br>
Calls to other 7965s (on net) are iLBC...<br>
<br>
So, how do I support this codec<br>
<br>
<br>
<br>
<br>
Jonathan<o:p></o:p></p>
</div>
</div>
<div>
<p class=MsoNormal>_______________________________________________<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>cisco-voip mailing list<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><a href="https://puck.nether.net/mailman/listinfo/cisco-voip"
target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
</div>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<P><FONT face=Arial color=#808080 size=1>
<HR>
</FONT></P>
<P><FONT color=#808080><FONT face=Arial size=1>CONFIDENTIALITY STATEMENT<BR>This
communication and any attachments are CONFIDENTIAL and may be protected by one
or more legal privileges. It is intended solely for the use of the addressee
identified above. If you are not the intended recipient, any use, disclosure,
copying or distribution of this communication is UNAUTHORIZED. Neither this
information block, the typed name of the sender, nor anything else in this
message is intended to constitute an electronic signature unless a specific
statement to the contrary is included in this message. If you have received this
communication in error, please immediately contact me and delete this
communication from your computer. Thank you.</FONT> </FONT></P>
<P><FONT color=#808080>
<HR>
</FONT></P>
</body>
</html>