> On Dec. 23, 2014, 7:41 a.m., Joshua Colp wrote: > > /trunk/main/rtp_engine.c, line 2193 > > <https://reviewboard.asterisk.org/r/4286/diff/1/?file=69966#file69966line2193> > > > > Yeah, put this in the 96-127 rang instead.
Wouldn't that cause ast_rtp_engine_load_format() to fail because no dynamic rtp mapping is available? - Scott ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviewboard.asterisk.org/r/4286/#review14028 ----------------------------------------------------------- On Dec. 19, 2014, 2:24 p.m., Scott Griepentrog wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviewboard.asterisk.org/r/4286/ > ----------------------------------------------------------- > > (Updated Dec. 19, 2014, 2:24 p.m.) > > > Review request for Asterisk Developers. > > > Bugs: ASTERISK-24367 > https://issues.asterisk.org/jira/browse/ASTERISK-24367 > > > Repository: Asterisk > > > Description > ------- > > Valid payload type codes are between 0 and 127 to allow for being stored in 7 > bits. During call setup, pjsip validates the SDP and will assert if it > encounters an invalid payload type code (see pjmedia_sdp_validate() in > pjmedia/src/pjmedia/sdp.c). This assert will be hit if a call is placed to a > pjsip endpoint with allow=all set. > > To avoid this, the previous use 128 for the slin192 format has been changed > to 95. > > > Diffs > ----- > > /trunk/main/rtp_engine.c 429845 > > Diff: https://reviewboard.asterisk.org/r/4286/diff/ > > > Testing > ------- > > Tested with pjsip calls to allow=all configured extensions. > > > Thanks, > > Scott Griepentrog > >
-- _____________________________________________________________________ -- 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
