Summary:	ASTERISK-26515: rtp_engine: Allocate RTP payloads on a per-session basis
Reporter:	Joshua C. Colp (jcolp)	Labels:
Date Opened:	2016-10-28 10:50:23	Date Closed:	2017-03-24 16:24:07
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	Core/RTP
Versions:		Frequency of Occurrence
Related Issues:	is related to ASTERISK-26311 [patch] rtp_engine: Allow more than 32 dynamic payload types.
Environment:		Attachments:	( 0) ASTERISK-26515.diff
Description:	Dynamic payloads are currently statically set upon the format registration. This restricts how many payloads can be registered to a maximum of 32 and makes it so payloads are static within sessions. This issue is for changing the RTP engine code to allocate a payload on a per-session basis as formats are needed. This means that dynamic payloads would no longer be static. The DTMF payload for rfc2833 should remain at 101, as it has been that way for quite a long time. Attached is a patch which implements this behavior. It probably needs additional work.
Comments:	By: Friendly Automation (friendly-automation) 2017-03-24 16:24:08.176-0500 Change 5260 merged by zuul: rtp_engine: allocate RTP dynamic payloads per session [https://gerrit.asterisk.org/5260|https://gerrit.asterisk.org/5260] By: Friendly Automation (friendly-automation) 2017-03-24 17:48:40.630-0500 Change 5261 merged by zuul: rtp_engine: allocate RTP dynamic payloads per session [https://gerrit.asterisk.org/5261|https://gerrit.asterisk.org/5261] By: Friendly Automation (friendly-automation) 2017-03-24 17:48:46.691-0500 Change 5259 merged by Joshua Colp: rtp_engine: allocate RTP dynamic payloads per session [https://gerrit.asterisk.org/5259|https://gerrit.asterisk.org/5259]