- Joined
- Mar 7, 2017
- Messages
- 3
- Reaction score
- 0
Hi!
I am evaluating an installation of 3cx V15 together with a Snom D345. Currently I would like to provision and firmware update the phone via the PBX, but it seems to me that I have to constantly work around the requirement of public FQDN access. I want all traffic to stay completely LAN local even though phones and PBX are in different subnets (we have a huge network with branch offices connecte via VPN).
For now I was able to provision the phone from a different subnet with a SBC, however I also had to change the DNS resolution in order for the public FQDN to resolve to the internal IP address of the PBX. Now the next problem is the firmware update URL which always points to downloads.3cx.com instead of the PBX URL.
Is there any way to force the whole infrastructure to stay local even though distributed over several networks? Allowing our phones to access the internet is simply not an option.
Thanks!
I am evaluating an installation of 3cx V15 together with a Snom D345. Currently I would like to provision and firmware update the phone via the PBX, but it seems to me that I have to constantly work around the requirement of public FQDN access. I want all traffic to stay completely LAN local even though phones and PBX are in different subnets (we have a huge network with branch offices connecte via VPN).
For now I was able to provision the phone from a different subnet with a SBC, however I also had to change the DNS resolution in order for the public FQDN to resolve to the internal IP address of the PBX. Now the next problem is the firmware update URL which always points to downloads.3cx.com instead of the PBX URL.
Is there any way to force the whole infrastructure to stay local even though distributed over several networks? Allowing our phones to access the internet is simply not an option.
Thanks!