Solved Unable to assign Yealink phones to extensions

Status
Not open for further replies.

Frank86

Bronze Partner
Joined
Jan 18, 2018
Messages
300
Reaction score
26
I have a site where I need to try multiple times before I can assign a phone to an extension. Never seen this before.
I reset a phone to factory settings, say a Yealink T41 or T26; the phone shows up under PHONES. I select it, assign it to an extension, and... nothing. The phone is assigned to the extension, but the extension's still red and the phone still shows up in bold under PHONES.

Sometimes I have to try 3-4 times before I can assign the phone to the extension. Sometimes, with the T26, it doesn't matter how many times I try. Still nothing.

This is for phones on the same LAN as the PBX and for phones connected to an SBC across the WAN.
 
Hi Frank,

Starting from here is important in this case:
https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/

Also since you have remote phones, include whether you use a custom FQDN or a 3CX FQDN

Hi. Good points. Info below.

  • 3CX Version, e.g. Professional Annual 16.0.5.622
  • Server OS, Windows Server 2019
  • Is the 3CX Server Hosted and where? On premises
  • IP Phone Make/Model/Firmware: Yealink T26 with firmware: 6.73.0.50
  • Provisioning Method: Local / VPN / STUN / SBC: Local and SBC
  • Trunk Provider or Gateway Make/Model: Spectrum T1 PRI
  • Has the Firewall Checker passed: YES / NO
  • Are custom Phone Templates being used: YES / NO
  • FQDN: 3CX
 
What kind of LAN do you have? with POE switchs ? VLAN ? phones are plugged into same switch as PBX ?
If you go in phone GUI do you see settings from provisioning or nothing ?
 
Hi Frank,

Once you hit the provisioning button, please wait up to 3 mins, don't press reprovision again.
Some older models are a bit slow so you will see them taking a bit of time before you see any activity.

For the T26
Unless the .50 was a typo. The T26P has an update also which you should install (6.73.0.60) but you should also note that regardless of the firmware, this phone will not provision in SBC mode.
You must disable the option "SSL/SecureSIP Transport and Ciphers" in the PBX security settings*

It should be fine in LAN mode though, as this does not use SSL.
https://www.3cx.com/sip-phones/yealink-t20p-t22p-t26p-t28p/#h.e2e9dlym4hi8

For the T41P
It's an end of life phone, but it should still work. It may be a bit slow to provision.
Ensure you also have the latest 3CX supported firmware.

Use the appropriate guides to take care of the firmware
https://www.3cx.com/sip-phones/
 
Thank you. So, the T26P will not provision in SBC mode no matter what? I was planning on replacing it anyway with a Grandstream GXP2170 anyway once I receive it.

I'll make sure the T41P is running the latest firmware.

Thank you.
 
What kind of LAN do you have? with POE switchs ? VLAN ? phones are plugged into same switch as PBX ?
If you go in phone GUI do you see settings from provisioning or nothing ?

POE switches. Voice VLAN. LAN phones are plugged into the same switch as the PBX. SBC phones are connecting from a couple of other sites across the WAN.
 
Replacing it is a better solution (compatibility and support-wise), but the T26 will provision once you disable the ciphers as mentioned above.

It is not a very good solution though, as this allows older TLS versions to run on your system which are not considered secure any more.
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,962
Messages
589,971
Members
164,864
Latest member
SCarpenter@fifthavenue-la