V16 Update 2 Problems with Yealink

[eryp]

Fresh install for a new customer. Installed 3CX on server yesterday. Go to provision phones this morning and I'm having trouble. 3CX Linux Version 16.0.2.910

1. Yealink T46S on recommended firmware 66.84.0.35 does not register.
2. CSTA session fails so no BLF activity
3. Server thinks phone is registered but phone shows "No Service"
4. Old firmware 66.83.0.55 seems to register and work as expected.

Any advice here? It's time consuming to roll phone firmware back. Recommended version does not seem to work.

 

[Saqqara]

Need info on setup - 3CX hosted locally to phones or in the cloud, If local are there any vlans ?

Couple of things to try if local.

Remove the config of the T46s from the 3CX management console

Factory default the phone, after the reboot does it appear in phone list and are you able to assign it to an extension.

 

[eryp]

Cloud Server

I rolled the firmware back to 66.83.0.35 and it appears to work as expected.

@3cx Please take note. Recommended firmware for T46S does not seem to work with update 2. I can provide more details and assistance if you contact me directly.

 

[Evolute IT]

Cloud Server

I rolled the firmware back to 66.83.0.35 and it appears to work as expected.

@3cx Please take note. Recommended firmware for T46S does not seem to work with update 2. I can provide more details and assistance if you contact me directly.

Can you see an error in the Activity Log when the phone tries to register but fails?

I am using V16 SP2 with a Yealink T46S and I have no issues at all on the latest supported firmware...

 

[AWS2P]

So as your phones are in STUN, did you opened properly all the needed ports on phone side?

are the phones all in static ip adress?

 

[eryp]

I have not dug into this any further as it was easiest just to roll firmware back and it works. I'll test and collect logs or packet capture in a few weeks when my schedule opens up. No time for it right now.

 

[JohnS_3CX]

Cloud Server

I rolled the firmware back to 66.83.0.35 and it appears to work as expected.

@3cx Please take note. Recommended firmware for T46S does not seem to work with update 2. I can provide more details and assistance if you contact me directly.

We took note, but we don't yet have enough info on what your setup is , you might have to go into further detail so we can help. Rolling back the firmware and having it work doesn't tell us the "why", it only tells us that the phones work again in your specific deployment as-is now. When you can, please elaborate further:

• Server? you mentioned Cloud, what cloud and are all necessary ports opened on the VM firewall?
• Phones setup SBC/STUN/VPN?
• Any VLANs involved?
• If STUN, do all devices have unique non overlapping ports?
• Remote site SIP ALG disabled and ports opened as per guide? https://www.3cx.com/docs/ports/
• How does the remote site reach the internet, ISP modem restrictions?

 

[Sergio Fernandez]

Hi

I had similar issues with 70 Yealink T21P E2 when on the recommended V16.2 firmware of 52.84.0.35 downgrading to 52.83.0.55 works fine

 

[eryp]

We took note, but we don't yet have enough info on what your setup is , you might have to go into further detail so we can help. Rolling back the firmware and having it work doesn't tell us the "why", it only tells us that the phones work again in your specific deployment as-is now. When you can, please elaborate further:

• Server? you mentioned Cloud, what cloud and are all necessary ports opened on the VM firewall?
• Phones setup SBC/STUN/VPN?
• Any VLANs involved?
• If STUN, do all devices have unique non overlapping ports?
• Remote site SIP ALG disabled and ports opened as per guide? https://www.3cx.com/docs/ports/
• How does the remote site reach the internet, ISP modem restrictions?

Answers below:
-Server passes firewall checks. Same firewall config that I have on 10+ other servers. Running on Vultr.
-Phones are all setup STUN, first phone on the system - no other phones provisioned or even setup in server yet so there could not be any NAT or port conflicts.
-Unique ports as there are no other phones setup.
-Remote site confirmed that there is no SIP ALG. Mikrotik Router.
-No restrictions from ISP (we are the ISP for this customer)

I tested the phone that would not register on another 3CX server - 3CX windows version 15.5.15502.6 and the phone provisioned and registered as expected. Moved back to the 3CX Linux Version 16.0.2.910 and the phone would provision and fail to register. Roll firmware back to 66.83.0.55 and the phone would register as expected with no other changes. I verified this from 2 ISP networks to make sure it was not a routing issue from the remote site.

Any other info or testing you'd like to see let me know.