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...
ihardgrave
Mar 21, 2024Copper Contributor
We recently had a ticket opened with Microsoft and a few engineers called us to ask for more info and then they said it was out of scope for Microsoft teams support. We use Audiocodes phones, so we have opened a ticket with them to see where that gets us. Please reply if you find a solution. 🙂
IanG562
Mar 21, 2024Brass Contributor
I ended up moving off the CAP accounts and using normal user accounts. Which stinks as it comes at a cost. But when our yealink phones are signed in with normal user accounts they stay Available 99% of the time. So far there have been no complaints but it's still early our specific deployment.
I find using a contact center built on Teams to be pretty frustrating. There seems to be quite a few odd issues that come up that affect some users but not others. Then when attempting to troubleshoot it will work some calls, but other calls have issues.
We use Landis Contact Center which is great. But whenever we open a case, they point to MS. Then opening a case with MS takes forever to explain the issues again. Then MS will point to the phone vendor or back to Landis.
My failback plan is to just not use Presence-base routing as it does not seem to be reliable in Teams call queues. We will have to change how we work but hopefully a lot of these odd presence related issues will go away.
I am interested to see what you find.
I find using a contact center built on Teams to be pretty frustrating. There seems to be quite a few odd issues that come up that affect some users but not others. Then when attempting to troubleshoot it will work some calls, but other calls have issues.
We use Landis Contact Center which is great. But whenever we open a case, they point to MS. Then opening a case with MS takes forever to explain the issues again. Then MS will point to the phone vendor or back to Landis.
My failback plan is to just not use Presence-base routing as it does not seem to be reliable in Teams call queues. We will have to change how we work but hopefully a lot of these odd presence related issues will go away.
I am interested to see what you find.