Solved Yealink T27G Not Working With 802.1x Auth After v14 to v15.5 Upgrade

[[email protected]]

I have Yealink T22P, T28P, and T27G phones. The T27G is being setup on a switch that does not have 802.1x setup. After we set it up and take it to it's desk, where 802.1x is setup, the phone won't connect to the network. If I provision a old T28P to the same extension and install it the phone boots and works without issue.

We are using NPS on server 2016 for the server that auth's phones and pc's.

I've tried firmware T27G-69.84.0.10 and T27G-69.83.0.20. They both have the issue.

In the Template for the 802.1x configs I see the following configs.
network.802_1x.mode = 3
network.802_1x.identity = Yealink
network.802_1x.md5_password = $mypassword
network.802_1x.root_cert_url = %%PROVLINK%%/TrustCertificatesNorton.cer

When I look at the yealink information I see that the commands should be
static.network.802_1x.mode = 3
static.network.802_1x.identity = Yealink
static.network.802_1x.md5_password = $mypassword
static.network.802_1x.root_cert_url = %%PROVLINK%%/TrustCertificatesNorton.cer

Neither of these configs work and I can't seem to find any other configs that would be the problem. Has anyone run into this problem with Yealink's on 802.1x setups?

 

[cobaltit]

Nope, but that's because I've never setup 802.1x. Doesn't really sound like a 3CX issue so you might be better off on the Yealink forums.

 

[[email protected]]

I'll take it to the Yealink forum. My issue is that I created an account and I can't post until tomorrow due to new account restrictions. If anyone has any ideas from this forum I would be glad to try them while I wait for my yealink account to be able to post.

 

[[email protected]]

I'm not getting any responses from Yealink on their forum. During our testing we've discovered that phones setup prior to the upgrade to v15.5 can be factory reset and will auth just fine. New phones being provisioned through 3cx can not auth via 802.1x. We're thinking that the problem will be related to v15.5 but have run out of ideas what configs in the provisioning may be causing this.

Does anyone have any ideas on any areas of 3cx we can troubleshoot to keep looking for the problem.

 

[[email protected]]

I want to post a followup on this to anyone who may see this thread. The 3cx upgrade was just a coincidence. The last batch of T27G phones that got ordered now have different starting digits to the MAC address. I had to update the NPS policy using the Call Station ID. But when I updated it I could not add a 2nd Call Station ID to the policy. I had to edit the original one and update the regex to include both of them. I ended up using the expression 00-15-65-?|80-5E-C0-? to include the format for both MAC address types.

 

[cobaltit]

@[email protected]

Forest for the trees . Glad you figured it out because I honestly had no idea how 3CX could affect it and I almost setup a lab to test it.

 

[YiannisH_3CX]

Glad to see the issue has been resolved and thank you for updating the thread with your solution.