On 01/13/2011 01:22 PM, R?gis Montoya wrote: > Thanks for sharing :) > > Indeed sounds a good candidate. I changed it in my config_site.h and > I'll keep you in touch about users feedback. > > As it was introduced by revision 3345 : > (http://trac.pjsip.org/repos/changeset/3345/) > I'm wondering if there is not something else to change : > PJMEDIA_RTP_PT_START has been change to (PJMEDIA_RTP_PT_DYNAMIC-1), > instead of 102. > > If we change telephone event type to 101, we may go out of the limits of > dynamic payload type. > Why dynamic payload type not computed when building SDP? (I'm not sure > that's possible but as far as I understood reading SDP docs it should be). > Cause most of the time users/device will not send SDP offers with a long > choice but pjsip will probably support more and more codecs. And having > a static list may break the 127 limit really quickly. > Or at least in codecs maybe it could be interesting to add some > conditions to defs. (For example PJMEDIA_HAS_INTEL_IPP or PASSTHROUGH > for AMR and so on). > RFC2833 defines telephone-event as a dynamic payload type (section 4.4) thus it should work fine with any number >=96. If it doesn't, then the other endpoint is probably doing something wrong. -- Sa?l Ibarra Corretg? AG Projects
