From 9b103e7bea40c300f89de67cc23c1015fc03db76 Mon Sep 17 00:00:00 2001 From: Kevin Harwell Date: Mon, 20 Mar 2017 13:27:31 -0500 Subject: rtp_engine: allocate RTP dynamic payloads per session Dynamic payload types were statically defined in Asterisk. This unfortunately limited the number of dynamic payloads that could be registered. With this patch dynamic payload type numbers are now assigned dynamically and per RTP instance. However, in order to limit any issues where some clients expect the old statically defined value this patch makes it so the value Asterisk used to pre- designate is used for the dynamic assignment if available. An option, "rtp_use_dynamic", has also been added (can be set in asterisk.conf) that turns the new dynamic behavior on or off. When off it reverts back to using statically defined payload values. This option defaults to "yes" in Asterisk 15. ASTERISK-26515 #close patches: ASTERISK-26515.diff submitted by jcolp (license 5000 Change-Id: I7653465c5ebeaf968f1a1cc8f3f4f5c4321da7fc --- configs/samples/asterisk.conf.sample | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'configs') diff --git a/configs/samples/asterisk.conf.sample b/configs/samples/asterisk.conf.sample index e13a944b0..30934e4a9 100644 --- a/configs/samples/asterisk.conf.sample +++ b/configs/samples/asterisk.conf.sample @@ -97,6 +97,10 @@ documentation_language = en_US ; Set the language you want documentation ; This is currently is used by DUNDi and ; Exchanging Device and Mailbox State ; using protocols: XMPP, Corosync and PJSIP. +;rtp_use_dynamic = yes ; When set to "yes" RTP dynamic payload types + ; are assigned dynamically per RTP instance vs. + ; allowing Asterisk to globally initialize them + ; to pre-designated numbers (defaults to "yes"). ;rtp_pt_dynamic = 35 ; Normally the Dynamic RTP Payload Type numbers ; are 96-127, which allow just 32 formats. The ; starting point 35 enables the range 35-63 and -- cgit v1.2.3