Port Range or any Port for a specific Ressource

I found the answer in the known Bugs List. "Dynamic Portranges are not supported"

Is the use of Dynamic Port range on the roadmap, or is it technical impossible?

Hi Silvio, While we can add multiple ports for a resource at the time of creating it, you cannot add a range of ports that would typically be needed in the case of VOIP resources. This is there as a part of our backlog.

With respect to the second scenario, yes, as of now we do not support resources/applications that involve dynamic port allocation. As an admin, you need to define the actual ports that are going to be used at the time of creating resources. Which applications or protocols are you looking for that would potentially involve usage of dynamic ports?

Our VOIP System is using the following dynamic RTP Ports for audio data

What kind of VOIP Service do you use? is it a own Premise VOIP System? Just curious as i talked to plenty of customers in the past days and some uses SAAS Solutions like Teams and other have such (legacy?) VOIP applications. 

For internal Communication we are using TEAMS. For all the other Communication we are using Starface onpremises. unfortunately there is no webrtc client available for this system and all the other possibilities to route this traffic via 443 are pain in the ass. So we have to open all the Ports if we want to use Starface without VPN and that is not gonna happen. 

For internal Communication we are using TEAMS. For all the other Communication we are using Starface onpremises. unfortunately there is no webrtc client available for this system and all the other possibilities to route this traffic via 443 are pain in the ass. So we have to open all the Ports if we want to use Starface without VPN and that is not gonna happen. 

An individual question, why do you split Teams vs Starface and use both solutions? 

Wir sind Sparbrötchen und Teams als Ersatz für eine TK-Anlage ist einfach zu teuer.

PS: Ich soll dir Grüße von Daniel bestellen.