>>>>> "J" == Joshua C Colp <jc...@digium.com> writes:
J> It's not as tolerant/forgiving as chan_sip. It's following this from the RFC I believe: J> For each media format of that type supported by the J> agent, there SHOULD be a media format listed in the "m=" line. In J> the case of RTP, if dynamic payload types are used, an rtpmap J> attribute MUST be present to bind the type to a specific format. J> There is dynamic payload 100 in the SDP, but no rtpmap to state what J> it is thus violating that part of the SDP, and likely why the J> pjmedia-sdp code doesn't like it. Ah. That bug in the sdp should have jumped out at me. [SIGH] Still it would be better to ignore any dynamic payload from m= which lack a matching a=. Liberal in accept and all. -JimC -- James Cloos <cl...@jhcloos.com> OpenPGP: 0x997A9F17ED7DAEA6 -- _____________________________________________________________________ -- 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
