[cisco-voip] iLBC and Gateways

Wed Apr 15 21:19:09 EDT 2009

That seems dumb...

I got it to work fine with MGCP...

Also, I am noticing that my 7965s are not switching to 711 for conf calls
and we just get dead air...

J

On Mon, Jan 19, 2009 at 11:17 AM, Ryan Ratliff <rratliff at cisco.com> wrote:

> Apparently IOS supports it (for H.323) but for some reason CUCM doesn't.
> Not sure if it's a roadmapped feature or not.
>
> -Ryan
>
> On Jan 19, 2009, at 11:11 AM, Ryan Ratliff wrote:
>
> I suspect H.245 doesn't support iLBC (yet).
> Looking in the ASN description from
> http://www.packetizer.com/ipmc/h323/standards.html the latest H.245
> version doesn't seem to list iLBC.
> I could be reading it wrong though...
>
> -Ryan
>
> On Jan 19, 2009, at 10:53 AM, STEVEN CASPER wrote:
>
> TAC just sent me an email that iLBC is not supported on h323
> gateways....strange I wonder why?
>
>
> http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/6x/trunks.html#wp1044377
>
> I checked the SRND for CUCM 7.x Ilbc is not listed as a supported codec
> there either.
>
> Steve
>
>
> STEVEN CASPER <SCASPER at mtb.com> 01/16/09 8:34 AM >>>
>
> Got this to work with a MGCP gateway. Had to add/do the following:
>
> mgcp codec ilbc
> ccm-manager mgcp codec-allno mgcp mgcp Still can not negotiate using H323,
> opened a TAC case, will post fix when I get it. Steve
> Please consider the impact on our environment before printing this e-mail.
>
>
> Ryan Ratliff <rratliff at cisco.com> 12/22/2008 11:18 AM >>>
>
> What type of gateway is it? If H.323 make sure iLBC is either set on the
> voip dial-peer or in a codec class applied to the dial-peer.
>
> If MGCP check out
> http://www.cisco.com/en/US/docs/ios/12_4t/12_4t15/it_amrnb.html.
>
>
>
> -Ryan
>
> On Dec 22, 2008, at 11:06 AM, STEVEN CASPER wrote:
>
> Doing some testing with iLbc. I can place a call from IP phone (7962) to IP
> phone 7962 using iLbC and 7962 to IP Communicator 7 and I see I am using the
> iLBC codec on each end of the connection. I negotiate G729 when I use a
> gateway to reach the PSTN. Far as I can tell all is set up correctly with my
> regions, locations, device pools etc. Is iLBC supported in the following
> path between the phone and gateway?
> 7962 --IP------2851-------PRI-------PSTN
> Gateway is running 12.4.20T and CUCM is 6.1.1
> Thanks
> Steve
> ************************************ This email may contain privileged
> and/or confidential information that is intended solely for the use of the
> addressee. If you are not the intended recipient or entity, you are strictly
> prohibited from disclosing, copying, distributing or using any of the
> information contained in the transmission. If you received this
> communication in error, please contact the sender immediately and destroy
> the material in its entirety, whether electronic or hard copy. This
> communication may contain nonpublic personal information about consumers
> subject to the restrictions of the Gramm-Leach-Bliley Act and the
> Sarbanes-Oxley Act. You may not directly or indirectly reuse or disclose
> such information for any purpose other than to provide the services for
> which you are receiving the information. There are risks associated with the
> use of electronic transmission. The sender of this information does not
> control the method of transmittal or service providers and assumes no duty
> or obligation for the security, receipt, or third party interception of this
> transmission.
> ************************************_______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> ************************************
> This email may contain privileged and/or confidential information that is
> intended solely for the use of the addressee.  If you are not the intended
> recipient or entity, you are strictly prohibited from disclosing, copying,
> distributing or using any of the information contained in the transmission.
> If you received this communication in error, please contact the sender
> immediately and destroy the material in its entirety, whether electronic or
> hard copy.  This communication may contain nonpublic personal information
> about consumers subject to the restrictions of the Gramm-Leach-Bliley Act
> and the Sarbanes-Oxley Act.  You may not directly or indirectly reuse or
> disclose such information for any purpose other than to provide the services
> for which you are receiving the information.
> There are risks associated with the use of electronic transmission.  The
> sender of this information does not control the method of transmittal or
> service providers and assumes no duty or obligation for the security,
> receipt, or third party interception of this transmission.
> ************************************
>
> Please consider the impact on our environment before printing this e-mail.
> ************************************
> This email may contain privileged and/or confidential information that is
> intended solely for the use of the addressee.  If you are not the intended
> recipient or entity, you are strictly prohibited from disclosing, copying,
> distributing or using any of the information contained in the transmission.
> If you received this communication in error, please contact the sender
> immediately and destroy the material in its entirety, whether electronic or
> hard copy.  This communication may contain nonpublic personal information
> about consumers subject to the restrictions of the Gramm-Leach-Bliley Act
> and the Sarbanes-Oxley Act.  You may not directly or indirectly reuse or
> disclose such information for any purpose other than to provide the services
> for which you are receiving the information.
> There are risks associated with the use of electronic transmission.  The
> sender of this information does not control the method of transmittal or
> service providers and assumes no duty or obligation for the security,
> receipt, or third party interception of this transmission.
> ************************************
>
>
>
>
>
> _______________________________________________
> 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/20090415/ebc2a42c/attachment.html>