[asterisk-bugs] [JIRA] (ASTERISK-27406) Infinite loop when out of ports and rtpstart value is odd

[Asterisk Team (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-27406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=239913#comment-239913 ] 

Asterisk Team commented on ASTERISK-27406:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

> Infinite loop when out of ports and rtpstart value is odd
> ---------------------------------------------------------
>
>                 Key: ASTERISK-27406
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27406
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_rtp_asterisk
>    Affects Versions: 13.18.0
>            Reporter: Thomas Guebels
>
> When the rtpstart value configured in rtp.conf parity is odd and all RTP ports are already used, the next call will start an infinite loop.
> ast_rtp_new walks through the RTP port range configured until it finds a free one. It starts at a random position, wraps around at the end of the range and return an error if it comes back to the starting position. 
> Unfortunately, this code assumes an even value was set in rtpstart since we never go back to the starting position otherwise.
> Either a correct value for rtpstart should be enforced when parsing the configuration or the port lookup should not assume anything and never fail to break the loop.



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