Communication issues on some subnets

[[email protected]]

Hey folks,

I have an issue where some of my subnets do not communicate with 3CX Phone/Softphone wont register.

Phone system is on 172.16.14.x
Windows PC Clients are on 192.168.10.x (These all register fine)
LLDP for phones is 172.16.14 and PC's get 192.168.10 (this works fine)
Main Wifi on 172.16.20.x Phone apps will not register nor will Wifi phones
Secondary Wifi on 172.16.14 (crested specifically for 3CX apps) App register as do Wifi phones
VPN 172.16.2x. Clients her cannot register without a host file update, they get local DNS and it sends them to 172.16.14 but that does not work, however if I put the External IP pointing to our FQDN in the host file they connect fine, this of course causes issues once they are back in the office.

• 3CX Version, e.g. Standard Annual 18
• Server OS, Windows Server 2019, Intel Xeon Gold 6234
• Is the 3CX Server Hosted On-premises
• IP Phone Make/Model/Firmware version, Many, Mostly Yealink T23G on current firmware, issue is mostly with windows app
• Provisioning Method: Local
• Trunk Provider or VoIP Gateway Make/Model, Cogeco (Main Trunks) IXICA (Secondary Trunks)
• Has the Firewall Checker passed: YES
• Are custom Phone Templates being used: NO

 

[Saqqara]

Sounds like your vlan to vlan routing is missing some rules - double check your rules. You need to allow udp port 5090 and https between the vlans for 3cx apps to work

also check your switch trunks are setup correctly

on the vlans that are not working, can you access the 3cx mangement console

on the 3CX provisioning tab, what do you have for the 'Network interface for registration and provisioning' - 3cx server IP address or 3CX FQDN. If 3CX FQDN make sure the 3CX fqdn resolves to the internal IP address of the 3cx server on the vlans

On the vpn connections, make sure you have closed own the 3cx app, connect to the vpn and then start the 3cx app