Share via

Yealink A24 shows 'available' slots instead of meetings after an upgrade

Carey Knighton-Fitt 2 Reputation points
2026-03-31T07:48:20.5266667+00:00

Hi,

Weird scenario no one wants to take by the horns.

We have an A24 deployed to for senior member of staff, after recent upgrades on the various firmware.

All meetings prior to 11AM SAST are ignored and rather shows available. When we factory reset and firmware versions are reverted - it works fine.

With the latest firmware in place the diary looks perfect for the NEXT day, prior - Evening

BUT when when that day rolls around it blanks out the all meeting prior to 11AM. Image (6)

Microsoft are pointing at Yealink -> <- Yealink point to Microsoft.

And the poor end user is stuck in the middle.

Microsoft Teams | Microsoft Teams for business | Meetings and calls | Other
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Julie Huynh 740 Reputation points Independent Advisor
    2026-03-31T14:39:12+00:00

    Dear @Carey Knighton-Fitt,

    Good day! Welcome to Microsoft Q&A forum!

    Based on your description and the screenshots, I understand that after upgrading to the latest Yealink A24 firmware, meetings scheduled before 11:00 AM (SAST) are shown as “Available” instead of appearing on the calendar. The issue only affects the current day, meetings display correctly the night before and for future days. Reverting the firmware and factory resetting fixes the issue, but it consistently returns on the latest firmware. Microsoft and Yealink are each attributing the problem to the other, leaving no clear resolution.

    Since this behavior appears to occur within the Microsoft Teams calendar integration after the firmware update, the best next step would be to raise a support ticket directly with Microsoft, as they’re best positioned to investigate how meetings are being surfaced on Teams devices.

    For detailed instructions on how to get support, please refer to Get support - Microsoft 365 admin

    If you don’t have the required admin permissions, I recommend reaching out to your IT Administrator and asking them to log the ticket on your behalf. They can include the symptoms you’ve outlined, along with the confirmation that the issue does not occur when reverting to an older firmware version.

    This will help ensure the issue is reviewed by the appropriate Microsoft support team and escalated if needed. Thank you for your kindness and understanding!

    If you have extra questions about this answer, please click "Comment". 

    Note: Please follow the steps in [our documentation] to enable e-mail notifications if you want to receive the related email notification for this thread. 

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.