Forum Discussion
Common Area Phone License and Meeting Rooms \ SignInMode
You seems to be using the latest firmware on the phone and Microsoft did another "great" solution to take your money.
https://m365log.com/teams/enforcement-of-licenses-on-teams-phones/
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.
Yes my steps are as per the document.
Key is the teamsipphone policy seems to be ignored and the phone switches to CommonAreaPhoneSignIn even though policy is MeetingSignIn
Other quirks. In subsequent testing, with no other change, if I assign a Microsoft Teams Room license the teamsiphonepolicy is honoured and the calendar is shown.
More surprising is if I then downgrade the license back to cap…. MeetingSignIn Continues.
I know one other org seems to be hitting the same issue
My observed behaviour is as follows
- Account created, common are phone license allocated and TeamsIpPhonePolicy, SignInMode set to MeetingSignIn
- Phone signs in
- The phone switches to "CommonAreaPhoneSignIn" mode. This is also seen in the logs from the phone. ie MS are sending this parameter. Key is the setting configured via grant-CsTeamsIPPhonePolicy is not honoured.
- License on the account is changed to "Microsoft Teams Rooms Standard" (Only change)
- The phone switches to "MeetingSignIn" mode
- Changing the license back to common are phone license
- After 24 hours the phone flips back to "CommonAreaPhoneSignIn"
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.You seems to be using the latest firmware on the phone and Microsoft did another "great" solution to take your money.
https://m365log.com/teams/enforcement-of-licenses-on-teams-phones/
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.- Thanks for the reply
Yes I also heard back from MS _ it isn't as clear as what you state but writing is on the wall
"Teams Rooms devices now require device licensing, either Teams Rooms Standard or Teams Rooms Premium (managed services).
All future meeting room capabilities will only be available in Teams Rooms Standard and Premium SKUs.
In your case I assume you want to manage the device so the best option is the Teams Rooms Standard SKU."
I also see another article which echoes the one you call out.
https://pupuweb.com/mc273378-enforcement-licenses-teams-phones/
So it would seem that CAP license have the CAP policy enforced.
I will just need to figure out what license is needed for a reception phone
- I would recommend opening a ticket with Microsoft as the next step and ask them to confirm the position with this.
- I have and initial response is not encouraging… along the lines of we are not trained to support phones.. talk to the vendor etc.
I did point out if teams stops working on an iPhone do I talk to apple? etc..