[Freeswitch-users] G729 coded issues

[Steve Underwood]

On 01/20/2010 12:36 AM, Brian West wrote:
> g729a is 100% INVALID in the sdp fix the param in your cisco SPA or your Linksys SPA phone and it will stop doing that.  Hopefully they'll fix this "bug" soon in the cisco phones to not include the a in the sdp.  The fmtp is the proper way to specify annex a or any other options for g729.
>    
Annex A only affects the inner workings of the codec. There is 
absolutely no difference whatsoever between G.729 and G.729A on the 
wire. The SDP has no reason to mention it, and the standards say it 
shouldn't.
> /b
>
> On Jan 19, 2010, at 10:31 AM, Ahmed Naji wrote:
>
>    
>> Hi everyone,
>>
>> I have the following scenario and a major customer-affecting issue thereof.
>>
>> Here is the scenario: customer traffic encoded as G.729 from a cisco gateway
>> ->  our FS (G729 passthrough) ->  remote end gw (G729)
>>
>> Calls were failing at an alarming rate, so I looked at the debug logs. It
>> transpired that the Cisco is offering G729 annex b, while the remote end can
>> only do G729a.
>>
>> Besides changing source or destination preferences, is there a way to ensure
>> that G729a is used end-end ?
>>
>> Thanks in advance.
>>      
>
Steve