On 15-10-04 11:06 PM, Matthew Jordan wrote: <snip>
2) Another option would be to just store the framing on the frame itself. Frames are not immutable; they are created by the RTP instance (which has the framing for that instance available on it), and could easily be set in ast_rtp_read. Since the framing negotiated is not dependent on the format but on the media session itself, it seems more appropriate to store it on the frames generated by that media session. What's nice about this is that codec modules are fed frames already; that means there's no additional lookups you'll have to do in your codec module. Of the two approaches I like #2 best, but some others may want to chime in on this as well.
I also like #2 best. -- Joshua Colp Digium, Inc. | Senior Software Developer 445 Jan Davis Drive NW - Huntsville, AL 35806 - US Check us out at: www.digium.com & www.asterisk.org -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
