Solved Webmeeting / web client firewall assistance

[usti]

This is hosted in a VPS external to our network.

1) With version 16, we've been working through the web client issues. We found we had to open ports 9000-10999 TCP (we already had those UDP ports open prior to using the web client) to get audio. I've not been able to locate anything definitively in the documentation that this is the correct range. May I get confirmation this is indeed correct?

2) Also with version 16, dial-in users to a webmeeting get audio with other dial-in users just fine. However, participants using the webmeeting interface for audio and video do not hear audio from the dial-in users. We have not yet tested if all web interface participants can hear each other. I suspect they can.
--Troubleshooting so far has revealed that disabling the firewall on the 3cx instance resolves this problem. It is clear there is a firewall issue specific to webmeeting ports but we cannot locate specific webmeeting firewall documentation more specific than https://www.3cx.com/docs/ports/.

Note that all other aspects of the system work fine (internal calling, external calling, etc.)

Many thanks in advance for your feedback on this matter.

 

[Saqqara]

There is a sticky post on the ports - https://www.3cx.com/community/threads/3cx-phone-system-audio-ports-increased.60235/

 

[usti]

There is a sticky post on the ports - https://www.3cx.com/community/threads/3cx-phone-system-audio-ports-increased.60235/

I appreciate the feedback and effort to assist. Unfortunately this is a bit of a hunt to go to a sticky thread to them go digging through release notes for a specific release where the change happened.

As it is, we’ve already accounted for the expanded UDP audio port range (9000-10999). We also had to open 9000-10999 TCP to get the webclient to work successfully. I did not see this information documented anywhere either. I’m not even sure this is the correct port range required. I just know it works (so far).

It would be tremendously beneficial to have an update to https://www.3cx.com/docs/ports that show the ports needed for webmeeting as well was webclient audio. A concise document is easier than hunting through release notes.

Thanks.

 

[JohnS_3CX]

Hi usti,

The article on the 3CX ports (even though states its for V15) is indeed correct and should allow for webmeeting to operate whether browser to browser, or whether users dial in from extensions.

The system will use the HTTPS port for browser sessions, and the UDP media ports for the dial in users so I can't tell you why TCP also had to be allowed for the media port range. I suspect some troubleshooting on the firewall is in order now

 

[Shawn]

probably a dumb question but does your firewall checker test pass?

 

[usti]

probably a dumb question but does your firewall checker test pass?

Yes it does. We found an order of operations problem in our firewall rules that was superseding another rule that caused this issue. We are now fully functional for both webmeeting and web client.

Thanks!

 

[JohnS_3CX]

Glad it was resolved!