[cisco-voip] iLBC and Cisco 7965s...

[Ryan Ratliff]

The CMM has higher PRI port density than the 6608 (up to 3 6-port T1  
modules) so I believe you can consider it a replacement for the  
6608.   You can also run native IOS on your 6500 with the CMM.

Doesn't help that it was just EOS'd as well but you can at least buy  
them through June of 2009.
http://www.cisco.com/en/US/prod/collateral/modules/ps2706/ 
end_of_life_notice_c51-495784.html

-Ryan

On Dec 27, 2008, at 12:30 PM, Jonathan Charles wrote:

Well, I have a lot of customers who are aggregating a LOT of PRIs on  
6608s... what is Cisco going to replace it with?


Jonathan

On Sat, Dec 27, 2008 at 10:37 AM, <lelio at uoguelph.ca> wrote:
I'm gonna miss being able to register one port to one cluster and  
another port to a different cluster.

Lelio Fulgenzi, Senior Analyst
Computing & Communications
University of Guelph
519-824-4120 x56354

...sent from my iPod - please pardon my fat fingers ;)

[XKJ2000]

On Dec 27, 2008, at 10:25 AM, "Jonathan Charles" <jonvoip at gmail.com>  
wrote:

> Yeah, that sucks... I kind of like the 6608... but we just got a  
> 2821 so, we will use that instead...
>
>
> Jonathan
>
> On Mon, Dec 22, 2008 at 8:41 AM, Linsemier, Matthew  
> <MLinsemier at apassurance.com> wrote:
> 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.
>
>
> MAtt
>
>
> From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip- 
> bounces at puck.nether.net] On Behalf Of Jonathan Charles
> Sent: Friday, December 19, 2008 2:56 PM
> To: Ryan Ratliff
> Cc: cisco-voip at puck.nether.net
> Subject: Re: [cisco-voip] iLBC and Cisco 7965s...
>
>
> 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...
>
> Annoying.
>
>
> Jonathan
>
> On Fri, Dec 19, 2008 at 1:31 PM, Ryan Ratliff <rratliff at cisco.com>  
> wrote:
>
> Can't seem to find the 6608 downloads on cisco.com 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.
>
>
> The gist of my first email is that I don't think you're going to  
> see support for iLBC on the 6608.
>
>
> Unity Connections 7.0(1) I can see supports iLBC, not sure on the  
> Unity TSP.
>
>
> -Ryan
>
> On Dec 19, 2008, at 12:45 PM, Jonathan Charles wrote:
>
>
> Well, I am running CCM 7.0.1
>
> The 6608 is running D00404000032 (base load from ccm 7)
>
> Unity TSP is 8.3.1
>
> 7965 is running 8.4.1S (iLBC was supported in 8.3)
>
> Not sure what TSP or 6608 load supports iLBC...
>
>
>
> Jonathan
>
>
> On Fri, Dec 19, 2008 at 11:41 AM, Ryan Ratliff <rratliff at cisco.com>  
> wrote:
>
> What load is your 6608 running?  What date was that load released?
>
> When did the IP phones start supporting iLBC?
>
>
> I think the answer to those questions will tell you why you can't  
> get calls to your 6608 to use iLBC.
>
>
> As for Unity it just depends on if they have a TSP that supports iLBC.
>
>
> -Ryan
>
>
> On Dec 19, 2008, at 12:33 PM, Jonathan Charles wrote:
>
>
> OK, so how do we get this to work...?
>
> 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).
>
> My voice gateway is a 6608 (single PRI, rest are transcoders, conf  
> bridges)...
>
> Calls to Unity use G.729 as well...
>
> Calls to other 7965s (on net) are iLBC...
>
> So, how do I support this codec
>
>
>
>
> Jonathan
>
> _______________________________________________
>
> cisco-voip mailing list
>
> cisco-voip at puck.nether.net
>
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
>
>
>
> CONFIDENTIALITY STATEMENT
> 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.
>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20081229/d6663768/attachment-0001.html>