is payload type of g726 correct?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Exactly as Gang Liu said. IIRC, it was using dynamic PT in the
development phase, but when it came into (compatibility) testing with
other sip endpoints, we decided to use static PT.

Regards,
nanang


2009/3/20 Gang Liu <gangban.lau at gmail.com>:
> but many hardphone/softswitch still use 2 for G.726 payload.
> If change to dynamic payload,? it will be problem when talking to these
> devices.
> There are some devices which use static payload 2 and dynamic payload for
> G.726 at the same time.
>
> regards,
> Gang
>
> 2009/3/20 Benny Prijono <bennylp at teluu.com>
>>
>> 2009/3/19 Rafael Maia <rmaia_lcm at hotmail.com>
>>>
>>>
>>> Hi all,
>>>
>>> the RFC?3551 ( http://www.ietf.org/rfc/rfc3551.txt?) states the the PT 2
>>> is reserved but it is being set to G726.
>>> And the same RFC says that G726 should have a dynamic PT.
>>>
>>
>> You're right, upon reading it again it seems that the use of PT=2 has been
>> deprecated, and dynamic pt should be used.
>>
>> Thanks!
>>
>> ?-benny
>>
>>
>>>
>>> Rafael Maia
>>>
>>
>>
>> _______________________________________________
>> Visit our blog: http://blog.pjsip.org
>>
>> pjsip mailing list
>> pjsip at lists.pjsip.org
>> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>>
>
>
> _______________________________________________
> Visit our blog: http://blog.pjsip.org
>
> pjsip mailing list
> pjsip at lists.pjsip.org
> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>
>



[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux