QoS FQDN Clarification

[vrheartland]

This is likely going to sound elementary - but given the fluid development process, I want to make sure we aren't missing something...

Deployment models vary - from on-premise to private cloud to Amazon/Google

In our deployments, we use the LightSail deployment - QoS is not normally something we concern ourselves with on these platforms - does the QoS FQDN need to be configured inside these deployments as well - or is it pretty well limited to those using on-premise deployments?

Would the QoS FQDN also be something that should be configured at each remote site's firewall as well? Do the Webmeeting requests ever hit the PBX or do they go directly to the MCU since its a separate WebRTC connection?

 

[LeonidasG_3CX]

Hi there,

• Your PBX MyPhone service on port typically on 5001 or 443 must be able to reach the MCU's if you want certain WebMeeting capabilities to work at all.
  
  
• Similarly, your PBX must be able to reach webmeeting-director.3cx.net for Webmeeting to work at all.
  
  
• QoS. This is something you'd set on your firewall to tell it to give more bandwidth priority when WebMeeting MCU's are contacted/connected by someone in your network.