Hello!

Which RFC specifies the corresponding number of the formats?

Where in the Asterisk source code does it state the SDP formats?

Does Asterisk follow the formats of IANA?
(http://www.iana.org/assignments/rtp-parameters)

Thank you,
Elliot


On Thu, Jul 2, 2009 at 3:44 PM, Elliot Murdock<murdo...@gmail.com> wrote:
> Hello,
>
> Thank you clarifying that.
>
> However, if that is the case, why is Asterisk sending back PCMU
> packets (instead of G729), which the device is not enabled for and
> subsequently, fails the call?
>
> Could the mapping be disabled or not properly mapping to the G729
> driver in a certain versions of Asterisk?
>
> Thanks,
> Elliot
>
> On Thu, Jul 2, 2009 at 3:25 PM, Kevin P. Fleming<kpflem...@digium.com> wrote:
>> Elliot Murdock wrote:
>>> Hello!
>>>
>>> I noticed that the SIP packet contains this line:
>>>
>>> m=audio 60000 RTP/AVP 18 98 96 97 101 13
>>>
>>> However, there is no rtpmap that describes 18.  Media format 18
>>> Apparently refers to G729, but there is no rtpmap in the SDP for it.
>>> Since G729 is a registered and known format is there any way for
>>> Asterisk to negotiate it within an explicit rtpmap?
>>
>> Yes, that is already supported. Asterisk does not require rtpmap entries
>> for well-known (RFC specified) codec mappings.
>>
>> --
>> Kevin P. Fleming
>> Digium, Inc. | Director of Software Technologies
>> 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
>> skype: kpfleming | jabber: kpflem...@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
>>
>

_______________________________________________
-- 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

Reply via email to