Microsoft Tech Community Live:  Microsoft Teams Edition
November 09, 2021, 08:00 AM - 12:00 PM (PST)
SOLVED

Common Area Phone License and Meeting Rooms \ SignInMode

%3CLINGO-SUB%20id%3D%22lingo-sub-2579169%22%20slang%3D%22en-US%22%3ECommon%20Area%20Phone%20License%20and%20Meeting%20Rooms%20%5C%20SignInMode%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2579169%22%20slang%3D%22en-US%22%3E%3CP%3EKey%20questions%3CBR%20%2F%3E1.%20Is%20it%20supported%20to%20use%20a%20CAP%20license%20with%20a%20conference%20phone%3F%20(And%20critically%20have%20the%20conference%20phone%20show%20the%20calendar)%3CBR%20%2F%3E2.%20If%20the%20above%20is%20still%20supported%20(which%20has%20been%20my%20experience%20till%20now).%20How%20do%20I%20get%20the%20phone%20to%20honor%20the%26nbsp%3Bteamsipphonepolicy%20with%20the%20mode%2C%26nbsp%3BSignInMode%3A%20MeetingSignIn%3CBR%20%2F%3E3.%20is%20anyone%20else%20having%20issues%20with%20conference%20phones%5Cteams%20and%20CAP%20licenses%3F%3C%2FP%3E%3CP%3E%3CBR%20%2F%3ETill%20now%20the%20phones%20have%20been%20working%20fine%20but%20now%20the%20phones%20always%20sign%20in%20in%20CommonAreaPhoneSignIn%20mode%3CBR%20%2F%3E%3CBR%20%2F%3EIssue%20relates%20to%20conference%20phone%20Yealink%20CP960%20running%20the%20latest%20supported%20teams%20code%3C%2FP%3E%3CP%3EKey%20is%20there%20appears%20to%20be%20a%20%3CU%3Echange%3C%2FU%3E%20in%20experience%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22AlistairKeay_0-1627036960251.jpeg%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F297966i886BD88F7F1D6DA5%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22AlistairKeay_0-1627036960251.jpeg%22%20alt%3D%22AlistairKeay_0-1627036960251.jpeg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAAD%20object%20created%2C%20and%20a%20CAP%20license%20assigned%20to%20the%20account%3C%2FP%3E%3CP%3ERef%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fset-up-common-area-phones%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fset-up-common-area-phones%3C%2FA%3E%3C%2FP%3E%3CP%3E%E2%80%9CA%20common%20area%20phone%20is%20typically%20placed%20in%20an%20area%20like%20a%20lobby%20or%20another%20area%20that%20is%20available%20to%20many%20people%20to%20make%20a%20call%3B%20for%20example%2C%20a%20reception%20area%2C%20lobby%2C%20or%20%3CSTRONG%3Econference%20phone%3C%2FSTRONG%3E.%20Common%20area%20phones%20are%20signed%20in%20with%20accounts%20tied%20to%20a%20Common%20Area%20Phone%20license.%20The%20TeamsIPPhone%20policy%20must%20also%20be%20appropriately%20set%20for%20the%20phone%20to%20have%20a%20common%20area%20user%20experience.%E2%80%9D%3C%2FP%3E%3CP%3EOn%20signing%20into%20the%20phones%20there%20are%20three%20modes%20expected%20to%20be%20available%3C%2FP%3E%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20This%20has%20been%20my%20experience%20in%20the%20past%3C%2FP%3E%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22AlistairKeay_1-1627036960281.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F297967i7F2A122E890719BD%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22AlistairKeay_1-1627036960281.png%22%20alt%3D%22AlistairKeay_1-1627036960281.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThen%20by%20granting%20a%20teamsipphonepolicy%20with%20the%20mode%3C%2FP%3E%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20SignInMode%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3A%20MeetingSignIn%3C%2FP%3E%3CP%3EThe%20expectation%20and%20previous%20experience%20was%20that%20the%20middle%20interface%20shown%20above%20would%20be%20displayed%20on%20the%20phone%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%20in%20testing%20the%20right%20hand%20display%20is%20always%20displayed%20no%20matter%20what%20what%20iphonepolicy%20is%20applied%3C%2FP%3E%3CP%3E(I%20would%20note%20using%20an%20older%20Polycom%20Trio%208800%20the%20mode%20is%20the%20expected%20middle%20one%20but%20the%20Trio%20has%20%E2%80%9Climitations%E2%80%9D%20and%20only%20supports%20certain%20modes.%20Key%20is%20there%20is%20a%20calendar%20associated%20with%20the%20account%20etc)%3CBR%20%2F%3E%3CBR%20%2F%3EAny%20thoughts%20or%20advice%20welcome%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20the%20logs%20from%20the%20phone%20the%20following%20is%20seen%3C%2FP%3E%3CP%3E%26lt%3B134%26gt%3BJul%2023%2017%3A58%3A30%20805ec03b5554.073%20GUI%20%5B2040%3A2159%5D%3A%20ANDR%26lt%3B6%2Binfo%26nbsp%3B%20%26gt%3B%203402%26nbsp%3B%203402%20D%20TeamsBroadcastListener%3A%20onReceive%20com.microsoft.skype.teams.ipphone.APP_USER_STATE%20(1%3Asign%20in)%2C%20is%20cap%3Atrue%3C%2FP%3E%3CP%3E%26lt%3B134%26gt%3BJul%2023%2017%3A58%3A30%20805ec03b5554.073%20GUI%20%5B2040%3A2159%5D%3A%20ANDR%26lt%3B6%2Binfo%26nbsp%3B%20%26gt%3B%203402%26nbsp%3B%203402%20D%20TeamsStateHelper%3A%20setIsCap%3A%20true%2C%20mIsUserCap%3Atrue%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2579169%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EUser%20Interface%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2584729%22%20slang%3D%22en-US%22%3ERe%3A%20Common%20Area%20Phone%20License%20and%20Meeting%20Rooms%20%5C%20SignInMode%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2584729%22%20slang%3D%22en-US%22%3EAre%20you%20assigning%20the%20TeamsIPPhonePolicy%20to%20the%20CAP%20account%3F%20I%20imagine%20you%20are%2C%20but%20just%20wanted%20to%20double%20check.%20Here%20is%20a%20really%20good%20blog%20article%20on%20this%20subject.%20May%20be%20worth%20working%20through%20and%20retracing%20your%20steps%20-%20%3CA%20href%3D%22https%3A%2F%2Fseanmcavinue.net%2F2021%2F05%2F31%2Fconfigure-microsoft-teams-common-area-phones%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fseanmcavinue.net%2F2021%2F05%2F31%2Fconfigure-microsoft-teams-common-area-phones%2F%3C%2FA%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2586186%22%20slang%3D%22en-US%22%3ERe%3A%20Common%20Area%20Phone%20License%20and%20Meeting%20Rooms%20%5C%20SignInMode%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2586186%22%20slang%3D%22en-US%22%3EThanks%20Peter%3CBR%20%2F%3EYes%20my%20steps%20are%20as%20per%20the%20document.%3CBR%20%2F%3EKey%20is%20the%20teamsipphone%20policy%20seems%20to%20be%20ignored%20and%20the%20phone%20switches%20to%20CommonAreaPhoneSignIn%20even%20though%20policy%20is%20MeetingSignIn%3CBR%20%2F%3E%3CBR%20%2F%3EOther%20quirks.%20In%20subsequent%20testing%2C%20with%20no%20other%20change%2C%20if%20I%20assign%20a%20Microsoft%20Teams%20Room%20license%20the%20teamsiphonepolicy%20is%20honoured%20and%20the%20calendar%20is%20shown.%3CBR%20%2F%3EMore%20surprising%20is%20if%20I%20then%20downgrade%20the%20license%20back%20to%20cap%E2%80%A6.%20MeetingSignIn%20Continues.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20know%20one%20other%20org%20seems%20to%20be%20hitting%20the%20same%20issue%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2590975%22%20slang%3D%22en-US%22%3ERe%3A%20Common%20Area%20Phone%20License%20and%20Meeting%20Rooms%20%5C%20SignInMode%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2590975%22%20slang%3D%22en-US%22%3E%3CP%3EMy%20observed%20behaviour%20is%20as%20follows%3C%2FP%3E%3COL%3E%3CLI%3EAccount%20created%2C%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3Ecommon%20are%20phone%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Elicense%20allocated%20and%20TeamsIpPhonePolicy%2C%26nbsp%3BSignInMode%20set%20to%26nbsp%3BMeetingSignIn%3C%2FLI%3E%3COL%3E%3CLI%3E%3CSPAN%3EPhone%20signs%20in%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%3EThe%20phone%20switches%20to%20%22CommonAreaPhoneSignIn%22%20mode.%20This%20is%20also%20seen%20in%20the%20logs%20from%20the%20phone.%20ie%20MS%20are%20sending%20this%20parameter.%26nbsp%3B%20Key%20is%20the%20setting%20configured%20via%26nbsp%3Bgrant-CsTeamsIPPhonePolicy%20is%20not%20honoured.%3C%2FSPAN%3E%3C%2FLI%3E%3C%2FOL%3E%3CLI%3ELicense%20on%20the%20account%20is%20changed%20to%20%22%3CSTRONG%3EMicrosoft%20Teams%20Rooms%20Standard%3C%2FSTRONG%3E%22%20(Only%20change)%3C%2FLI%3E%3COL%3E%3CLI%3EThe%20phone%20switches%20to%20%22MeetingSignIn%22%20mode%26nbsp%3B%3C%2FLI%3E%3C%2FOL%3E%3CLI%3EChanging%20the%20license%20back%20to%26nbsp%3B%3CSTRONG%3Ecommon%20are%20phone%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3Blicense%3C%2FSPAN%3E%3C%2FLI%3E%3COL%3E%3CLI%3E%3CSPAN%3EAfter%2024%20hours%20the%20phone%20flips%20back%20to%20%22CommonAreaPhoneSignIn%22%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FSPAN%3E%3C%2FLI%3E%3C%2FOL%3E%3C%2FOL%3E%3CP%3E%3CSPAN%3EAll%20I%20can%20conclude%20is%20that%20there%20is%20a%20change%20in%20behaviour.%3CBR%20%2F%3EIf%20you%20are%20putting%20a%20conference%20phone%20in%20a%20meting%20room%20(Yealink%20CP960%2C%20Poly%20Trio%20c60%20etc)%20you%20have%20to%20assign%20a%20%22Microsoft%20Teams%20Rooms%20Standard%22.%3CBR%20%2F%3EUsing%20a%20CAP%20license%20MS%20is%20locking%20to%26nbsp%3B%22CommonAreaPhoneSignIn%22%20mode%3CBR%20%2F%3E%3CBR%20%2F%3EI%20would%20love%20to%20hear%20what%20other%20people%20experience%20_%20is%20this%20a%20fault%20or%20a%20license%20shift%20in%20position%20from%20MS.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2593803%22%20slang%3D%22en-US%22%3ERe%3A%20Common%20Area%20Phone%20License%20and%20Meeting%20Rooms%20%5C%20SignInMode%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2593803%22%20slang%3D%22en-US%22%3EI%20have%20and%20initial%20response%20is%20not%20encouraging%E2%80%A6%20along%20the%20lines%20of%20we%20are%20not%20trained%20to%20support%20phones..%20talk%20to%20the%20vendor%20etc.%3CBR%20%2F%3EI%20did%20point%20out%20if%20teams%20stops%20working%20on%20an%20iPhone%20do%20I%20talk%20to%20apple%3F%20etc..%3C%2FLINGO-BODY%3E
Contributor

Key questions
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

 

AlistairKeay_0-1627036960251.jpeg

 

AAD object created, and a CAP license assigned to the account

Ref https://docs.microsoft.com/en-us/microsoftteams/set-up-common-area-phones

“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

               

AlistairKeay_1-1627036960281.png

 

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

11 Replies
Are you assigning the TeamsIPPhonePolicy to the CAP account? I imagine you are, but just wanted to double check. Here is a really good blog article on this subject. May be worth working through and retracing your steps - https://seanmcavinue.net/2021/05/31/configure-microsoft-teams-common-area-phones/
Thanks Peter
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

  1. Account created, common are phone license allocated and TeamsIpPhonePolicy, SignInMode set to MeetingSignIn
    1. Phone signs in
    2. 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.
  2. License on the account is changed to "Microsoft Teams Rooms Standard" (Only change)
    1. The phone switches to "MeetingSignIn" mode 
  3. Changing the license back to common are phone license
    1. 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.

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..
best response confirmed by Alistair Keay (Contributor)
Solution

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
That's correct. For Audio Conference phones like Yealink CP960 and Trio C60 is better to use Teams Room license because you will need calendar features.
And of course some resource mailbox for it to book the meeting with.
CAP by default doesn't have it but still works on previous firmware, however it is not supported by Microsoft.

We use Teams Room Standard for Audio Conference phones as the most suitable one.
Please be aware as this license bundle also contains Intune license, But it's up to you to use intune or not.

Depends of what you need for reception. I mean what kind of interface (user or CAP or AC).
You can use some E3+Phone system addon or even F3 + Phone System for User interface.
Or you can try combination of CAP + Exchange Online P2 + user mailbox type (to enable Voicemail).
Also possible to use Teams Room Standard. But if you'll need voicemail >> you will need to add EXO Plan 2 + user mailbox type.

Basically there is quite a lot flexibility here so play in lab and get the most convenient way you like.
I've also heard from my MS contact that it will be possible to enable speed dials even for current CAP enforced interface.
Which should finally fix the current problem with CAP native interface.
Thanks.
The reception phone needs "UserSignIn" mode _ key is what you picked up.
The intent is a phone that will be left signed in as "Reception NY" for example. The person manning the phone can answer calls to reception and then transfer to typically an internal contact _ so it needs to show speed dials\contacts on the phone to allow simple\quick transferring. (No calendar\mail requirements)

MS told me to hold on while they investigate. Idea of E1 + Phone System flagged as "technically it works but this scenario is not compliant for device "

Also don't suppose you know _ is SideCar RTM or still classified as Beta?
When I lasted tested it worked perfectly but in production I hit "Due to a known issue the sidebar may trigger the bug of displaying "sign in your account" window on secondary interfaces. New Teams APP solved this issue will be released by Microsoft on TAC"

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 ...

In my testing
"Teams Room Standard" is working for me reliably and makes sense for meeting rooms. Reboots etc and the phone continues to work fine for me showing the calendar

Response from MS
"We’ve recently published documentation to provide more information. https://docs.microsoft.com/en-us/microsoftteams/devices/teams-android-devices-user-interface

Because of a recent change in enforcing licenses on phones, it might seem to the customer that they lost functionality. "

There will be further changes GA in September _ not quite sure what the outcome will be.

From my testing
1. CAP license will lock down the phone to a common area phone mode _ so "fair enough"
2. Meeting room phones\devices need at least "Teams Room Standard" to expose the calendar _ again "fair enough"

Still trying to get a clear answer on what license to use for a generic reception account where the "user sign in experience" is required. On the face of it a "E1 + Phone System question" seems logical but still checking on this to ensure compliant with licensing rules etc