- Joined
- Aug 15, 2019
- Messages
- 2
- Reaction score
- 0
Hi
We have a ~200 extension v18 Windows system hosted in Azure with Yealink IP Phones in the offices connected via ipsec/site to site VPNs. Currently phones are provisioned using option 66 in Local LAN mode, with a local DNS zone and A record to send the 3cx FQDN traffic up the VPN to the Azure server LAN IP.
We have a large number of Yealink T46G that need to be replaced, and we are also wanting to introduce hotdesking.
I've not done a hotdesking set up in quite some time, and I'm wanting to clarify the supported provisioning methods - Documentation says we need to assign phones using PnP, but this won't work due to multicast not traversing the VPN. They always worked over DHCP option 66 in the past, is this still valid?
If we were to replace all the T46G with T46U would these support hotdesking over IPSEC VPN in Local LAN mode, with DHCP 66 auto provisioning? The 3CX provisioning guide doesn't say if the 'U' supports hotdesking or not.
Thanks in advance
We have a ~200 extension v18 Windows system hosted in Azure with Yealink IP Phones in the offices connected via ipsec/site to site VPNs. Currently phones are provisioned using option 66 in Local LAN mode, with a local DNS zone and A record to send the 3cx FQDN traffic up the VPN to the Azure server LAN IP.
We have a large number of Yealink T46G that need to be replaced, and we are also wanting to introduce hotdesking.
I've not done a hotdesking set up in quite some time, and I'm wanting to clarify the supported provisioning methods - Documentation says we need to assign phones using PnP, but this won't work due to multicast not traversing the VPN. They always worked over DHCP option 66 in the past, is this still valid?
If we were to replace all the T46G with T46U would these support hotdesking over IPSEC VPN in Local LAN mode, with DHCP 66 auto provisioning? The 3CX provisioning guide doesn't say if the 'U' supports hotdesking or not.
Thanks in advance