Forum Discussion
IanG562
Jan 08, 2024Brass Contributor
Common area phone account presence
Hello Everyone, I have a few CAP accounts setup and only have them logged into Yealink MP54s. Most of them I notice the account status on the phone is Available (Green). However, I have a few t...
IanG562
Jul 01, 2024Brass Contributor
MChevalier13 Thats a good find using Graph/PowerShell. I never found a fix for this and still see our Yealink phones randomly switch to Away at time. The only solution that is working for us to moving away from Teams Presence-Based Routing.
From what I understand the MS Teams Presence API is not really reliable when it comes to call queues. I am even seeing presence sync issues within our MS certified call center solution. Our users Teams presence will be Available after a call, but the call center solution still shows them as In a Call a few mins after they hang up.
MChevalier13
Jul 02, 2024Copper Contributor
IanG562, I have noticed the same delay. I'm also seeing a randomly long delay when sending restarts, sign-out, sign-in, configuration, and/or updates to the various phones. Sometimes I have seen a simple restart take a day to process. Currently all of our phones are Yealink, so I cannot speak on any other manufacture's devices.
I find the lack of quick control of the phones, and the fact that Microsoft keeps deprecating PowerShell cmdlets, very frustrating.
I found out from the case I have open that the Get-MgCommunicationPresence is in beta and there is no Set-MgCommunicationPresence at this time. SO, turning off the Teams Presence-Based Routing in the Call Queues is the only thing working for us as well, but this may cause an issue, if someone is on vacation and does not want to receive calls from a call queue, as we would have to remove that user from the call queue while they are on vacation, then add them back.
I find the lack of quick control of the phones, and the fact that Microsoft keeps deprecating PowerShell cmdlets, very frustrating.
I found out from the case I have open that the Get-MgCommunicationPresence is in beta and there is no Set-MgCommunicationPresence at this time. SO, turning off the Teams Presence-Based Routing in the Call Queues is the only thing working for us as well, but this may cause an issue, if someone is on vacation and does not want to receive calls from a call queue, as we would have to remove that user from the call queue while they are on vacation, then add them back.