[cisco-voip] SME Codec Issue

[Brian Meade]

Yea, every endpoint is going to support G.711 but the problem comes when
you have a region relationship that doesn't allow enough bandwidth for
G.711 or you can also hit issues with codec lock if doing recording on any
of the phones.

On Mon, Sep 15, 2014 at 1:22 AM, Anthony Holloway <
avholloway+cisco-voip at gmail.com> wrote:

> Correct Brian. I was assuming his endpoint could support g711. After all,
> it is the de facto VoIP codec.
>
> Dennis, It's also worth mentioning that if the UAC offers g711, the UAS
> has every right to choose it. Plan your BW, QoS and CAC accordingly.
>
> If the telco requires g711 to be offered, it's possible that's how the
> trunk was ordered. I know verizon allows you to use either g729 or g711 but
> CenturyLink makes you choose one or the other and then you're locked into
> that one codec.
>
>
> On Thursday, September 11, 2014, Brian Meade <bmeade90 at vt.edu> wrote:
>
>> From my experience with ACPL, the endpoint still needs to report that
>> capability.  The ACPL is just for filtering or changing order so this
>> wouldn't work if a phone only advertised G.729 support for instance.
>>
>> On Thu, Sep 11, 2014 at 6:03 PM, Anthony Holloway <
>> avholloway+cisco-voip at gmail.com> wrote:
>>
>>> Are you connected directly to ITSP via SME or via an SBC?  If not, what
>>> version of CUCM?  In 9x you have audio codec preference lists (think voice
>>> class codec in IOS).  So you would still set your bitrate to 64kbps, but
>>> your ACPL would list g729 then g711.
>>>
>>> On Thu, Sep 11, 2014 at 11:04 AM, Heim, Dennis <Dennis.Heim at wwt.com>
>>> wrote:
>>>
>>>> We have an SME design, so leaf clusters connected to an SME via SIP.
>>>> The SIP trunks go to the carrier and those terminate on the SME. The
>>>> carrier requires that regardless of the codec that g.711 is an option. Any
>>>> thoughts on how to make SME always advertise g.711 as an option?
>>>>
>>>>
>>>>
>>>> *Dennis Heim | Collaboration Solutions Architect*
>>>>
>>>> World Wide Technology, Inc. | +1 314-212-1814
>>>>
>>>> [image: twitter] <https://twitter.com/CollabSensei>
>>>>
>>>> [image: chat][image: Phone] <+13142121814>[image: video]
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> 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/20140915/389ac927/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 1389 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140915/389ac927/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 1292 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140915/389ac927/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 3876 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140915/389ac927/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 1391 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140915/389ac927/attachment-0003.png>