Presently, the WebRTC code will reject any offer that attempts to use a dynamic payload type less than 96. While values in the range of 96 through 127 are preferred for dynamic use, the AVT/RTP profile (and those derived from it) do allow such types to be sent in SDP. By rejecting them, we are out of compliance with the specification. RFC 3551, section 3: > "This profile reserves payload type numbers in the range 96-127 > exclusively for dynamic assignment. Applications SHOULD first use > values in this range for dynamic payload types. Those applications > which need to define more than 32 dynamic payload types MAY bind > codes below 96, in which case it is RECOMMENDED that unassigned > payload type numbers be used first. However, the statically assigned > payload types are default bindings and MAY be dynamically bound to > new encodings if needed." (With particular emphasis on the final quoted sentence)

I think this should work, but I can check.

/r/8779 - Bug 818640: Test that using dynamic payload types < 96 works. Pull down this commit: hg pull -r 5a6b89a790658884e7d0e262180660690a50a701 https://reviewboard-hg.mozilla.org/gecko/

Comment on attachment 8606023 [details] MozReview Request: bz://818640/bwc /r/8779 - Bug 818640: Test that using dynamic payload types < 96 works. r=mt Pull down this commit: hg pull -r b0445decb23daca43b0be17eac1096abf94d83a1 https://reviewboard-hg.mozilla.org/gecko/

Comment on attachment 8606023 [details] MozReview Request: bz://818640/bwc Carry forward r=mt

Check back on retriggers for infra failures.