[asterisk-users] g729a compatibility

[Elliot Murdock]

Hello Kevin,

Gotcha...however, the mime is G.729a with an extra period, so it
doesn't get recognized.

However, as I asked before, does Asterisk map any of the RTP/AVP
profiles or does every format need to be defined in the SDP with a
rtpmap attribute?

You see, the incoming SDP supplies format 18 in the "m=", but there is
no corresponding rtpmap, since the SIP packet assumes it will be using
the conventional format 18 - namely the G729.

Does Asterisk know how to deal with this?

Thank you again,
Elliot

On Thu, Jul 2, 2009 at 3:22 PM, Kevin P. Fleming<kpfleming at digium.com> wrote:
> Philipp Kempgen wrote:
>
>> http://tools.ietf.org/html/rfc3555#section-3
>> ---cut---
>>    Note that the payload format (encoding) names defined in the RTP
>>    Profile are commonly shown in upper case.  MIME subtypes are commonly
>>    shown in lower case.  These names are case-insensitive in both
>>    places.
>> ---cut---
>>
>> Sounds like it should really be case-insensitive but I might easily
>> be mistaken. Didn't dig too deep into RTP/SDP specifications.
>
> It appears I was mistaken; Asterisk's matching of MIME types and
> subtypes in SDP is already case insensitive, so 'g729a' should be accepted.
>
> --
> Kevin P. Fleming
> Digium, Inc. | Director of Software Technologies
> 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
> skype: kpfleming | jabber: kpfleming at digium.com
> Check us out at www.digium.com & www.asterisk.org
>
> _______________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
>