[asterisk-bugs] [JIRA] (ASTERISK-26311) [patch] rtp_engine: Allow more than 32 dynamic payload types.

[Alexander Traud (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-26311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexander Traud updated ASTERISK-26311:
---------------------------------------

    Description: 
Since adding [all remaining rates|https://issues.asterisk.org/jira/browse/ASTERISK-24274] of Signed Linear (Asterisk 14.0) and [SILK|https://gerrit.asterisk.org/3136] (Asterisk 13.11), only one [RTP Payload Type|http://www.iana.org/assignments/rtp-parameters/rtp-parameters.xhtml#rtp-parameters-1] in the dynamic range (96-127) is left. That is going to be taken by [Codec 2|https://issues.asterisk.org/jira/browse/ASTERISK-26217]. One approach would be to assign only those types which are allowed in {{/etc/asterisk/sip.conf}} (or {{pjsip.conf}}). However for example, when all codecs are allowed, the issue persists.

[RFC 3551 section 3|https://tools.ietf.org/html/rfc3551#section-3] offers an alternative: ‘\[…\] 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.’

The attached patch fixes this issue giving room for at least another 54 RTP Payload Types.

  was:
Since adding all remaining rates of Signed Linear (Asterisk 14.0) and [SILK|https://gerrit.asterisk.org/3136] (Asterisk 13.11), only one [RTP Payload Type|http://www.iana.org/assignments/rtp-parameters/rtp-parameters.xhtml#rtp-parameters-1] in the dynamic range (96-127) is left. That is going to be taken by [Codec 2|https://issues.asterisk.org/jira/browse/ASTERISK-26217]. One approach would be to assign only those types which are allowed in {{/etc/asterisk/sip.conf}} (or {{pjsip.conf}}). However for example, when all codecs are allowed, the issue persists.

[RFC 3551 section 3|https://tools.ietf.org/html/rfc3551#section-3] offers an alternative: ‘\[…\] 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.’

The attached patch fixes this issue giving room for at least another 54 RTP Payload Types.


> [patch] rtp_engine: Allow more than 32 dynamic payload types.
> -------------------------------------------------------------
>
>                 Key: ASTERISK-26311
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26311
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 13.10.0
>            Reporter: Alexander Traud
>            Severity: Minor
>
> Since adding [all remaining rates|https://issues.asterisk.org/jira/browse/ASTERISK-24274] of Signed Linear (Asterisk 14.0) and [SILK|https://gerrit.asterisk.org/3136] (Asterisk 13.11), only one [RTP Payload Type|http://www.iana.org/assignments/rtp-parameters/rtp-parameters.xhtml#rtp-parameters-1] in the dynamic range (96-127) is left. That is going to be taken by [Codec 2|https://issues.asterisk.org/jira/browse/ASTERISK-26217]. One approach would be to assign only those types which are allowed in {{/etc/asterisk/sip.conf}} (or {{pjsip.conf}}). However for example, when all codecs are allowed, the issue persists.
> [RFC 3551 section 3|https://tools.ietf.org/html/rfc3551#section-3] offers an alternative: ‘\[…\] 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.’
> The attached patch fixes this issue giving room for at least another 54 RTP Payload Types.



--
This message was sent by Atlassian JIRA
(v6.2#6252)