RTP PORT management

[Brandan Hermo]

Since the upgrade to version 15.5 SP5 the range of RTP ports has varied and now they are from 9000-10743.

This is too large a range for PBXs that are not for 1024 concurrent calls. In clients of 4, 8, 16, 32, 64 it is not necessary to use such a wide range of ports. This generates implementation problems in clients because they do not want to open so many ports, or because within that range there are other services that already occupy the ports. Normally we modify the file 3cxmediaserver.ini to solve this and adapt the range of ports to the client, but in the new SP5 this file, although it is modified, it rewrites the original after a reboot of the machine.

At the end we solve it by modifying the FIRSTEXTPORT and LASTEXTPORT parameters but from the Support Department of 3CX tell us that it is not recommended, good operation is not guaranteed and the central is no longer supported. This is a very big problem for the clients and an uncertainty for the partners.

We ask that these parameters be editable and 3CX provide support on this issue. It is basic to be able to make deployments in small-medium clients.

 

[Benedikt Machens]

Sometimes it would be nice to change the used ports anyway to not use the default ports. Or you have to move the port range because other systems need those ports.

A default feature of every VoIP component that the RTP port range is configureable (like SIP-, SIPS-, HTTP-, HTTPS-,... port)


+1

 

[timmbo]

+1

 

[jonpennell]

+1

 

[CodyRigg]

I would also like to see this implemented.

 

[Patrick Clemens]

Fully agree. Most times you don't need the big range of ports.

 

[CodyRigg]

I would love to see this implemented.
Our SIP provider only opens ports above 10,000 and so whenever 3cx updates the config file automatically, we have to go in and update this manually to be lower, or else outgoing audio doesn't work. This should be added as a feature ASAP!

 

[cobaltit]

If a client says they don't want this many ports open you should tell them they are being stupid. Either you trust 3CX to be secure or you don't. 100 UDP ports pointing ONLY at 3CX verses 1500 doesn't change the security stance.

If it's an issue of port range conflict I assume you've already gone over to the other vendors page and complained over there because that can't be changed? The other option is to use different public IPs for the conflicting services. This was something those of us who have been around for a while used to do a lot back in the day when most people hosted their own servers in-house. I guess with so much moving to the cloud people forgot about that . Speaking of which, are you guys still doing premise installs because this really should be a non-issue with a cloud install.

And don't forget, it's not only calls using that range but WebRTC as well, so you may need more than you think.

While I understand it would be nice to adjust it, there's clearly a very low percentage of folks that run into this issue. The more common issues are with the web ports and SIP ports for obvious reasons, and you can change those.

I would love to see this implemented.
Our SIP provider only opens ports above 10,000 and so whenever 3cx updates the config file automatically, we have to go in and update this manually to be lower, or else outgoing audio doesn't work. This should be added as a feature ASAP!

Huh? Unless your SIP provider is also your ISP this shouldn't matter. The ports 3CX listens on has no bearing on the ports your SIP provider uses.