No, no my meaning is, what if i want to implement for example AMR-NB . Other than the codec interface in pjsip, it's required also to implement an RTP profile specific for such codec? Like http://www.rfc-editor.org/rfc/rfc4867.txt ( http://www.cs.columbia.edu/~hgs/rtp/ ) Fabio Nanang Izzuddin wrote: > Hi Fabio, > > If you mean the G723.1 bitrate setting (actual 6300kbps should be > written 6400), then it was bug and it has been fixed in 0.9.0, you > should be able to specify 6300 now. The integer calculation causes > flooring, i.e: stream.c calculates encoded frame size for jitter > buffer, it would result 23.xxx bytes and it is floored to 23 bytes, > this may cause decoder get bad input frame (1 byte in the end is > random, since it is not stored by jitter buffer) and it may cause > decoder producing noise or fail to decode. > Regards, > nanang > > > 2008/6/30 Fabio Pietrosanti (naif) <lists at infosecurity.ch>: > > Hi, > > implementing a codec means also implementing a customized RTP profile > for such codec? > > Nanang Izzuddin wrote: > > Hi, > > > > Sorry for the late response. The wrapper looks fine except for these > > parts: > > _______________________________________________ > Visit our blog: http://blog.pjsip.org <http://blog.pjsip.org/> > > pjsip mailing list > pjsip at lists.pjsip.org <mailto: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 >
