Jul 23 2021 03:55 AM
Jul 23 2021 03:55 AM
1. Is it supported to use a CAP license with a conference phone? (And critically have the conference phone show the calendar)
2. If the above is still supported (which has been my experience till now). How do I get the phone to honor the teamsipphonepolicy with the mode, SignInMode: MeetingSignIn
3. is anyone else having issues with conference phones\teams and CAP licenses?
Till now the phones have been working fine but now the phones always sign in in CommonAreaPhoneSignIn mode
Issue relates to conference phone Yealink CP960 running the latest supported teams code
Key is there appears to be a change in experience
AAD object created, and a CAP license assigned to the account
“A common area phone is typically placed in an area like a lobby or another area that is available to many people to make a call; for example, a reception area, lobby, or conference phone. Common area phones are signed in with accounts tied to a Common Area Phone license. The TeamsIPPhone policy must also be appropriately set for the phone to have a common area user experience.”
On signing into the phones there are three modes expected to be available
This has been my experience in the past
Then by granting a teamsipphonepolicy with the mode
SignInMode : MeetingSignIn
The expectation and previous experience was that the middle interface shown above would be displayed on the phone
However in testing the right hand display is always displayed no matter what what iphonepolicy is applied
(I would note using an older Polycom Trio 8800 the mode is the expected middle one but the Trio has “limitations” and only supports certain modes. Key is there is a calendar associated with the account etc)
Any thoughts or advice welcome
In the logs from the phone the following is seen
<134>Jul 23 17:58:30 805ec03b5554.073 GUI [2040:2159]: ANDR<6+info > 3402 3402 D TeamsBroadcastListener: onReceive com.microsoft.skype.teams.ipphone.APP_USER_STATE (1:sign in), is cap:true
<134>Jul 23 17:58:30 805ec03b5554.073 GUI [2040:2159]: ANDR<6+info > 3402 3402 D TeamsStateHelper: setIsCap: true, mIsUserCap:true
Jul 25 2021 08:40 AM
Jul 26 2021 02:31 AM
Jul 27 2021 06:26 AM
My observed behaviour is as follows
All I can conclude is that there is a change in behaviour.
If you are putting a conference phone in a meting room (Yealink CP960, Poly Trio c60 etc) you have to assign a "Microsoft Teams Rooms Standard".
Using a CAP license MS is locking to "CommonAreaPhoneSignIn" mode
I would love to hear what other people experience _ is this a fault or a license shift in position from MS.
Jul 27 2021 11:41 PM
Jul 28 2021 04:12 AM
Jul 28 2021 06:47 AM - edited Jul 28 2021 09:53 AMSolution
You seems to be using the latest firmware on the phone and Microsoft did another "great" solution to take your money.
Now phones with the latest firmware are enforcing signin via based on license plan assigned to account.
Before this time it was possible to use normal Common Area Phone without CAP ipphonepolicy which was the solution for the main issue with CAP interface >> speed dials.
And microsoft was telling that they will add speed dial for CAPs.
Well, they've found different approach. Now you have to pay more for another bundle of license (which one? good question) and CAP license becomes quite useless.
If you want you can try to downgrade one of your phone (factory reset afterwards is must).
With old teams agent in the firmware it should not change the interface automatically.
Aug 01 2021 12:49 PM
Aug 04 2021 05:14 AM
Aug 05 2021 09:29 AM
Aug 11 2021 02:45 AM
Same issue here. We were using some Phone devices in small conference rooms with CAP licenses for quite a while but now no calendar anymore after latest updates. I had the same idea and assigned a "Teams Room Standard" which worked for a day ... but after signing out the account and rebooting the phone even this does not work anymore and I tried it now with a spare E5 license which works as it should. Did you ever sign the account out of all devices, reboot the device and sign back in with a Teams Room license? Seems I have to give it another try if this works for others ...
Aug 16 2021 03:38 AM