Poly CCX Models Missing "Auto Answer" when using Teams Base Profile
Working with a customer that currently uses the VVX models deskphones as a paging solution in their environment. (https://greiginsydney.com/public-address-paging-options-for-microsoft-teams-i/) This requires the Auto Answer functionality to be available. They are migrating to Microsoft Teams as their phone system and would like to replace their current VVX models with a CCX model for the paging solution they currently have in place. Unfortunately, there doesn't seem to be a "Auto Answer" functionality on the CCX models with Teams Base profile. I did attempt to modify the configuration file with the attribute "call.autoAnswer.SIP="1"" but the phone ignores that modification. One important thing to note, when the CCX is switched to using the Skype for Business Base profile, the auto answer functionality is present. Poly support has directed me to Microsoft because they said this was a feature of the Microsoft Teams App on the Android phone. Is there any expectation to include this functionality in the CCX Models with the Teams base or a way to enable this feature using the configuration file?
Android Devices and Login challenges
We have been running into an odd problem. We have Intune setup with conditional access policies and when attempting to login Android-based collaboration devices (Poly X50, TC8, Yealink Phones, Poly C60 or Collab Bars etc), the experience differs. *sometimes* after entering the Code generated from the device, when logging in we see either: “You’re Signing in to Microsoft Authentication Broker on another device located in United States, if its not you, close this page” OR “You’re signing in to Microsoft Intune Company Portal on another device located in United States, if not you, close this page” When the former login occurs (MS Auth Broker) the device goes through its motions, looks to be logging in and eventual FAILS every time. While when we get the Intune login, it works everytime. The Device Accounts arnt in play here because the login occurs prior to the account info being entered, and everytime we are logging-in in INCOGNITO mode from a browser regardless. Also seems not device specific, and have no clue why its picking one versus the other for login. Anyone else seen this and any advice? Thank you very much Alan
