Provision Yealink on Vlan

[GrahamBell1!]

I know there are posts on this but they don't make sense. Is there a dummy guide to get a phone working on a network that has VLAN's

I have tried Local Debian, amazon and 3cx hosted servers. The Yealink will not provision on stun or lan at all. If I try provision it on SBC it plug and plays but will not connect.



On 3cx hosted PBX I took the phone offsite and it provisioned and worked when I brought it back on site.

My pc's subnet is 10.10.60.* the phones are 10.10.61.*

 

[cobaltit]

So you've scattered several scenarios into one email. Which setup are you currently trying to make work? Are you still on 3CX hosted?

Ultimately this doesn't sound like a VLAN issue, unless you have a VLAN only network with no internet access.

 

[GrahamBell1!]

Sorry - lets go with Amazon - installed 3cx and went through the motions - all firewalls pass, no Sip alg etc. Can make and receive calls via soft phones after entering correct rules.
Factory defaulted Yealink T43U, logged into the phone via web - added mac address to 3cx and tried Stun Lan and sbc options. Phone does not provision. Tried manual provision just get provision failed.

 

[Saqqara]

Are you still using a sbc server, if so put it on the same vlan as the phones

make sure you are allowing https (port 43) and 3cx tunnel port udp 5090 , ntp port (udp port 13) out to the internet

if you have configured dhcp option 66 remove it

note : on the softphone you can configure it by sending the welcome email , importing the config file or scanning qr code

 

[Saqqara]

All the info on configuring this phone is here https://www.3cx.com/sip-phones/yealink-t4-series/

 

[GrahamBell1!]

Seems to be the network. Voip cannot configure on PC subnet and I cant put a pc on the Voip subnet, so my network is the issue. I would have thought using stun would work but doesn't onsite. I can take the phone off this network and it will provision for Amazon or 3cx but not for onsite PBX.

Rather a nuisance.

 

[JohnS_3CX]

It sounds like your VLAN does not have internet access, NTP or DNS. If one of these fails the phone will have trouble getting provisioned.

If I may ask, what was the reasoning behind building VLANs originally?

 

[GrahamBell1!]

I inherited a very complicated system - they run through a data centre and have separated clients via vlans. Cisco phone system works ok but I think you are right there is no internet access. I don't like putting phones on a different LAN personally.

 

[Saqqara]

For stun to work, follow the 3cx support way

Make you life easy, install a 3cx sbc server

 

[JohnS_3CX]

Understood. It sounds like you will have to do some work in first demystifying and documenting the current network, then working your way through a new VLAN that will allow the phones the acces they need (DHCP / DNS / NTP / Internet).

As it is currently, SBC and STUN will 100% fail from the get go because the phone cannot even provision itself. And even if you provisioned a phone off-site then brought it back in, it would fail to register.

Don't waste your time troubleshooting the phones/PBX for now, try to focus on building a VLAN that provides what I mentioned earlier. Once this is ready, you can drop an SBC in that network and see if it will connect to 3CX. Once that is done, you can start resetting phones and they should appear in your management console Phones page. You can now assign them and they should begin to work as expected

 

[GrahamBell1!]

For stun to work, follow the 3cx support way

Make you life easy, install a 3cx sbc server

sbc server- You are right but no device will configure on the same vlan as the phones. Hence all the other comments - no internet on that subnet. Thanks for the advice.

 

[GrahamBell1!]

Understood. It sounds like you will have to do some work in first demystifying and documenting the current network, then working your way through a new VLAN that will allow the phones the acces they need (DHCP / DNS / NTP / Internet).

As it is currently, SBC and STUN will 100% fail from the get go because the phone cannot even provision itself. And even if you provisioned a phone off-site then brought it back in, it would fail to register.

Don't waste your time troubleshooting the phones/PBX for now, try to focus on building a VLAN that provides what I mentioned earlier. Once this is ready, you can drop an SBC in that network and see if it will connect to 3CX. Once that is done, you can start resetting phones and they should appear in your management console Phones page. You can now assign them and they should begin to work as expected

Good advice and a lot clearer now. Thanks for you advice - will post WHEN I get this sorted.

 

[JohnS_3CX]

Sure thing, and we can take another look if you still have any issues after that gets sorted