Home

'Meeting Room' license vs 'Common Area Phone' license vs 'E1+Phone System' license

%3CLINGO-SUB%20id%3D%22lingo-sub-315033%22%20slang%3D%22en-US%22%3E'Meeting%20Room'%20license%20vs%20'Common%20Area%20Phone'%20license%20vs%20'E1%2BPhone%20System'%20license%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-315033%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%207%20meetings%20rooms%20(a%20mix%20of%20Polycom%20VVX%20and%20Logitech%20SmartDocks)%2C%20what%20is%20the%20best%20way%20to%20license%20them%3F%20I%20can%20see%20there%20is%20a%20thing%20called%20'Meeting%20Room'%20which%20is%20%2420.60%2C%20'Common%20Area%20Phone'%20which%20is%20%2411.00%20or%20'E1%2BPhone%20System'%20which%20is%20%2420.40.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20should%20I%20be%20using%3F%20and%20what%20is%20the%20difference%20between%20them%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%26nbsp%3B%3C%2FP%3E%3CP%3ETrent.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-315033%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ECloud%20PBX%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-352986%22%20slang%3D%22en-US%22%3ERe%3A%20'Meeting%20Room'%20license%20vs%20'Common%20Area%20Phone'%20license%20vs%20'E1%2BPhone%20System'%20license%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-352986%22%20slang%3D%22en-US%22%3E%3CP%3EHi%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20recently%20purchased%20the%20new%20Meeting%20Room%20SKU%20that%20was%20released%20on%20the%201st%20December%202018%20but%20there%20seems%20be%20very%20little%20information%20around.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20it%20possible%20by%20assigning%20the%20Meeting%20room%20licence%20to%20a%20device%2Fmeeting%20room%20resource%20for%20a%20licenced%20user%20under%20tenant%20to%20access%20there%20normal%20files%20and%20folders%2C%20even%20if%20it%20was%20by%20accessing%20there%20OneDrive%20account%3F%3C%2FP%3E%3CP%3EWe%20purchased%20the%20meeting%20room%20licence%20to%20try%20and%20avoid%20licensing%20each%20user%20with%20an%20audio%20conferencing%20licence%20but%20if%20users%20can't%20get%20access%20to%20there%20files%20we%20may%20have%20to%20re-think%20using%20the%20meeting%20room%20sku.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3CP%3EKris%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-325524%22%20slang%3D%22en-US%22%3ERe%3A%20'Meeting%20Room'%20license%20vs%20'Common%20Area%20Phone'%20license%20vs%20'E1%2BPhone%20System'%20license%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-325524%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20not%20sure%20what%20you%20mean%20with%20%22full%20audio%20conference%22%3F%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20need%20the%26nbsp%3B%3CSPAN%3EAudio%20Conferencing%20license%20to%20create%20dial-in%20conferences%20but%2C%20when%20you%20use%20the%20Meet%20now%20from%20the%20Trio%20you%20won't%20send%20out%20an%20mail%20invitation%2C%20you%20will%20invite%20users%20directly%20to%20the%20meeting.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EIf%20you%20wan't%20to%20create%20a%20conference%20with%20dial-in%20you%20should%20create%20it%20and%20invite%20the%20device%20to%20the%20meeting.%20You%20and%20the%20device%20will%20be%20able%20to%20join%20using%20Skype%20and%20other%20user%20will%20be%20able%20to%20join%20the%20meeting%20with%20dial-in.%20You%20have%20to%20have%20the%20audio%20conferencing%20license%20for%20your%20account%20(since%20you%20schedule%20and%20invite%20to%20the%20meeting)%2C%20not%20the%20device.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-325219%22%20slang%3D%22en-US%22%3ERe%3A%20'Meeting%20Room'%20license%20vs%20'Common%20Area%20Phone'%20license%20vs%20'E1%2BPhone%20System'%20license%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-325219%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20Team%3C%2FP%3E%3CP%3EThank%20you%20so%20much%20for%20this.%20I%20do%20have%20a%20dilemma%20though.%20I%20have%20a%20Polycom%20Trio%208800%20and%20it%20is%20assigned%20the%20Common%20Area%20license.%20The%20meet%20now%20is%20enabled%20on%20the%20phone%20and%20it%20does%20work%2C%20however%2C%20I%20was%20thinking%20with%20that%20we%20will%20be%20able%20to%20have%20a%20full%20audio%20conference%20on%20it%2C%20but%20does%20not%20seem%20to%20be%20the%20case.%20I%20am%20sure%20am%20missing%20something.%20Do%20I%20need%20to%20assign%20the%20Meeting%20Room%20license%20to%20the%20user%2C%20if%20yes%2C%20will%20that%20give%20it%20an%20audio%20conference%20number%20with%20PIN%20ext%20for%20users%20to%20dial%20into%3F%20Any%20recommendation%20and%20advise%20will%20be%20highly%20appreciated%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-316310%22%20slang%3D%22en-US%22%3ERe%3A%20'Meeting%20Room'%20license%20vs%20'Common%20Area%20Phone'%20license%20vs%20'E1%2BPhone%20System'%20license%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-316310%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3ECommon%20Area%20Phone%20will%20give%20you%20the%20Skype%20for%20Business%2FTeams%20capabilities%20and%20Phone%20System%20licenses%2C%20so%20this%20is%20for%20a%20basic%20phone%20like%20a%20Polycom%20VVX%20in%20a%20common%20area%20(like%20a%20conference%20room).%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EWith%20the%20Meeting%20Room%20license%20you%20get%20more%20stuff%3A%20Teams%2C%20Skype%20for%20Business%2C%20Phone%20System%2C%20Audio%20Conferencing%20and%20Intune.%20The%20mailbox%20you%20will%20setup%20as%20a%20room%20mailbox%20(no%20license).%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EWith%20the%20E1%2BPhone%20system%20you%20will%20get%20some%20stuff%20you%20won't%20need%20and%20you%20won't%20get%20the%20Intune%20and%20Audio%20Conferencing%20that%20you%20get%20with%20the%20Meeting%20Room%20license.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ESo%20Common%20Area%20Phone%20licenses%20for%20the%20VVX%20and%20Meeting%20Room%20license%20for%20the%20Logitechs.%20You%20might%20need%20to%20add%20Calling%20Plan%20license%20to%20these%20if%20you%20want%20to%20dial%20out%20from%20these%20devices%20but%20that%20depends%20on%20your%20Phone%20System%20setup.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-545926%22%20slang%3D%22en-US%22%3ERe%3A%20'Meeting%20Room'%20license%20vs%20'Common%20Area%20Phone'%20license%20vs%20'E1%2BPhone%20System'%20license%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-545926%22%20slang%3D%22en-US%22%3E%3CP%3EThere%20are%20two%20things%20worth%20nothing%20here.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E1.%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F9476%22%20target%3D%22_blank%22%3E%40Linus%20Cansby%3C%2FA%3E%26nbsp%3BWhile%20devices%20accounts%20are%20not%20used%20to%20send%20meeting%20invitations%2C%20the%20devices%20still%20need%20to%20be%20licensed%20with%20Audio%20Conferencing%20to%20cover%20one%20specific%20capability%3A%20inviting%20PSTN%20attendees%20ad-hoc%20to%20an%20active%20meeting%20from%20the%20device.%26nbsp%3B%20Meaning%20that%20if%20someone%20is%20in%20the%20room%2C%20connected%20to%20a%20Skype%20or%20Teams%20meeting%20and%20they%20use%20the%20device%20to%20'Add%20a%20Participant'%20and%20then%20select%20a%20PSTN%20phone%20number%20as%20the%20new%20attendee%2C%20the%20outbound%20PSTN%20call%20placed%20by%20the%20meeting%20MCU%20requires%20that%20the%20device%20is%20licensed%20with%20Audio%20Conferencing.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E2.%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F271549%22%20target%3D%22_blank%22%3E%40DEBEL77%3C%2FA%3E%26nbsp%3BThe%20main%20difference%20between%20Common%20Area%20Phone%20and%20Meeting%20Room%20licenses%20is%20that%20the%20CAP%20license%20does%20not%20support%20Exchange%2C%20while%20the%20Meeting%20Room%20licenses%20does.%26nbsp%3B%20Common%20Area%20Phones%20which%20simply%20are%20used%20to%20place%20audio%20calls%20are%20what%20the%20CAP%20license%20was%20designed%20for%2C%20and%20bookable%20rooms%20where%20users%20join%20meetings%20from%20a%20calendar%20are%20what%20the%20Meeting%20Room%20license%20was%20created%20for.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-545927%22%20slang%3D%22en-US%22%3ERe%3A%20'Meeting%20Room'%20license%20vs%20'Common%20Area%20Phone'%20license%20vs%20'E1%2BPhone%20System'%20license%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-545927%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F271549%22%20target%3D%22_blank%22%3E%40DEBEL77%3C%2FA%3E%26nbsp%3BThe%20main%20difference%20between%20Common%20Area%20Phone%20and%20Meeting%20Room%20licenses%20is%20that%20the%20CAP%20license%20does%20not%20support%20Exchange%2C%20while%20the%20Meeting%20Room%20licenses%20does.%26nbsp%3B%20Common%20Area%20Phones%20which%20simply%20are%20used%20to%20place%20audio%20calls%20are%20what%20the%20CAP%20license%20was%20designed%20for%2C%20and%20bookable%20rooms%20where%20users%20join%20meetings%20from%20a%20calendar%20are%20what%20the%20Meeting%20Room%20license%20was%20created%20for.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-834731%22%20slang%3D%22en-US%22%3ERe%3A%20'Meeting%20Room'%20license%20vs%20'Common%20Area%20Phone'%20license%20vs%20'E1%2BPhone%20System'%20license%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-834731%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F9476%22%20target%3D%22_blank%22%3E%40Linus%20Cansby%3C%2FA%3E%26nbsp%3BI%20have%20a%20similar%20question.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20Common%20Area%20Phone%20includes%20the%20Phone%20System%20(required%20for%20calling%20plan).%20If%20we%20assign%20the%20Common%20Area%20Phone%20to%20a%20User%20and%20then%20assign%20the%20Calling%20Plan%2C%20does%20this%20provide%20Microsoft%20Teams%20calling%20ability%20to%20Users.%26nbsp%3B%3C%2FP%3E%3CP%3ENote%3A%20This%20is%20not%20for%20a%20physical%20phone%20but%20for%20the%20User.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-835971%22%20slang%3D%22en-US%22%3ERe%3A%20'Meeting%20Room'%20license%20vs%20'Common%20Area%20Phone'%20license%20vs%20'E1%2BPhone%20System'%20license%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-835971%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F402680%22%20target%3D%22_blank%22%3E%40manoj_cse%3C%2FA%3E%26nbsp%3BWhat%20will%20you%20use%20that%20user%20for%3F%20Will%20they%20use%20the%20Teams%20client%20to%20sign%20in%20so%20that%20they%20already%20have%20a%20E1%2FE3%20license%3F%20Then%20I%20guess%20the%20Phone%20System%20Add-On%20is%20better.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-836757%22%20slang%3D%22en-US%22%3ERe%3A%20'Meeting%20Room'%20license%20vs%20'Common%20Area%20Phone'%20license%20vs%20'E1%2BPhone%20System'%20license%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-836757%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F9476%22%20target%3D%22_blank%22%3E%40Linus%20Cansby%3C%2FA%3E%26nbsp%3BThe%20User%20already%20has%20the%20Office%20365%20Business%20Premium%20License%20with%20Common%20Area%20Phone%20License.%20So%20if%20we%20now%20add%20the%20calling%20plan%20license%2C%20would%20he%20be%20able%20to%20make%20calls%2C%20considering%20the%20Common%20Area%20Phone%20comes%20with%20Phone%20System.%3C%2FP%3E%3CP%3EThe%20doubt%20is%20if%20the%20Common%20Area%20Phone%20license%20works%20for%20Users.%20Is%20it%20specifically%20and%20only%20used%20for%20physical%20phone%20licensing%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-867453%22%20slang%3D%22en-US%22%3ERe%3A%20'Meeting%20Room'%20license%20vs%20'Common%20Area%20Phone'%20license%20vs%20'E1%2BPhone%20System'%20license%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-867453%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F311774%22%20target%3D%22_blank%22%3E%40Jeff_Schertz%3C%2FA%3E%26nbsp%3B%22%3CSPAN%3Einviting%20PSTN%20attendees%20ad-hoc%20to%20an%20active%20meeting%20from%20the%20device.%3C%2FSPAN%3E%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eso%20if%20I%20just%20invite%20PSTN%20attendees%20from%20any%20other%20account%20that%20is%20joined%20to%20the%20conference%20ID%20then%20there%20is%20no%20need%20for%20this%20functionality%3F%26nbsp%3B%20they're%20charging%20effectively%20%244%2Fmo%20as%20part%20of%20this%20SKU%20so%20people%20don't%20have%20to%20reach%20into%20their%20pocket%20and%20make%20an%20outbound%20call%20from%20their%20E5%20licensed%20mobile%20client%20instead%20of%20the%20device%20on%20a%20table%3F%20that's%20a%20bad%20look.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-873516%22%20slang%3D%22en-US%22%3ERe%3A%20'Meeting%20Room'%20license%20vs%20'Common%20Area%20Phone'%20license%20vs%20'E1%2BPhone%20System'%20license%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-873516%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F311774%22%20target%3D%22_blank%22%3E%40Jeff_Schertz%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAre%20you%20sure%20regarding%20the%20CAP%20license%20not%20supporting%20an%20Exchange%20mailbox%3F%20I%20can't%20see%20a%20reason%20why%20you%20assign%20CAP%20to%20a%20room%20mailbox%20to%20facilitate%20meeting%20room%20booking.%20Your%20own%20article%20mentions%20this%20should%20be%20possible%20as%20well.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22There%20is%20no%20special%20account%20type%20like%20with%20the%20server%20platform%20as%20any%20standard%20online%20user%20account%20can%20be%20used%20with%20the%20new%20license%2C%20meaning%20that%20Exchange%20calendaring%20is%20available%20for%20phones%20registered%20using%20a%20CAP-enabled%20account%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CFONT%3E%3CA%20href%3D%22http%3A%2F%2Fblog.schertz.name%2F2018%2F05%2Fhot-desking-and-common-area-phones-in-skype-for-business%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fblog.schertz.name%2F2018%2F05%2Fhot-desking-and-common-area-phones-in-skype-for-business%2F%3C%2FA%3E%3C%2FFONT%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-897314%22%20slang%3D%22en-US%22%3ERe%3A%20'Meeting%20Room'%20license%20vs%20'Common%20Area%20Phone'%20license%20vs%20'E1%2BPhone%20System'%20license%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-897314%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F235429%22%20target%3D%22_blank%22%3E%40Steve%20Bedwell%3C%2FA%3E%26nbsp%3BThere%20has%20been%20some%20back%20and%20forth%20on%20this%20topic%20over%20time.%26nbsp%3B%20Originally%20Microsoft%20did%20not%20intend%20for%20the%20CAP%20account%20in%20Skype%20for%20Business%20to%20be%20mailbox%20enabled%20and%20mentioned%20that%20Exchange%20Online%20might%20be%20pulled%20from%20that%20license.%3CBR%20%2F%3E%3CBR%20%2F%3EBut%20now%20that%20the%20license%20will%20be%20used%20by%20Teams%20that%20is%20likely%20not%20going%20to%20happen.%20The%20behavior%20I%20do%20see%20currently%20is%20that%20if%20a%20Common%20Area%20Phone%20license%20(or%20a%20Meeting%20Room%20license)%20is%20added%20to%20a%20standard%20User%20mailbox%20account%2C%20its%20mailbox%20will%20vanish%20(but%20it%20will%20return%20if%20a%20regular%20license%20is%20reapplied).%26nbsp%3B%20But%20if%20those%20licenses%20are%20assigned%20to%20an%20account%20with%20a%20Room%20mailbox%20and%20enabled%20using%20the%20CsMeetingRoom%20cmdlets%20then%20the%20mailbox%20will%20be%20fine.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIt%20appears%20that%20using%20those%20device%20licenses%20on%20a%20user%20account%20causes%20the%20mailbox%20to%20be%20blocked%2C%20by%20design.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-911202%22%20slang%3D%22en-US%22%3ERe%3A%20'Meeting%20Room'%20license%20vs%20'Common%20Area%20Phone'%20license%20vs%20'E1%2BPhone%20System'%20license%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-911202%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F311774%22%20target%3D%22_blank%22%3E%40Jeff_Schertz%3C%2FA%3EMicrosoft%20needs%20to%20fix%20this%20license%20nightmare.%26nbsp%3B%20It%20is%20way%20too%20confusing%20to%20understand%20which%20license%20applies%20to%20which%20purpose%20and%20it%20keeps%20changing%20as%20seen%20by%20these%20threads.%26nbsp%3B%20I%20have%20confirmed%20that%20a%20meeting%20room%20license%20does%20not%20work%20for%20a%20Trio%20conference%20phone.%26nbsp%3B%20It%20will%20not%20accept%20a%20meeting%20invite.%26nbsp%3B%20I%20was%20also%20unsuccessful%20using%20a%20common%20area%20phone%20but%20it%20works%20with%20an%20E5%20license.%26nbsp%3B%20The%20E5%20of%20course%20is%20overkill%20but%20I%20was%20able%20to%20use%20a%20phone%20system%20-%20virtual%20user%20license%20to%20get%20it%20working%20instead.%26nbsp%3B%20Yet%20I%20am%20told%20by%20the%20support%20team%20that%20it%20should%20not%20work%20that%20way.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EWhy%20not%20provide%20exchange%2Fmailbox%20connectivity%20for%20all%20phone%20related%20licenses%20and%20include%20the%20audio%20conferencing%20within%20that%20license%20so%20we%20don't%20have%20to%20select%20multiple%20licenses%20for%20each%20purpose%3F%26nbsp%3B%20It's%20too%20granular.%26nbsp%3B%20Why%20have%20both%20a%20CAP%20and%20Meeting%20Room%20license%3F%26nbsp%3B%20Make%20those%20the%20same%20with%20mailbox%20enabled%20and%20audio%20conferencing%20included.%26nbsp%3B%20Even%20common%20area%20phones%20should%20have%20voicemail%20capabilities.%26nbsp%3B%20Why%20block%20these%20device%20licenses%20on%20a%20user%20account%3F%26nbsp%3B%20Does%20it%20matter%20whether%20it%20is%20a%20room%20account%20or%20user%20account%3F%26nbsp%3B%20Otherwise%2C%20don't%20allow%20the%20license%20to%20be%20assigned%20at%20all%20so%20there%20is%20no%20confusion.%20%26nbsp%3B%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-911550%22%20slang%3D%22en-US%22%3ERe%3A%20'Meeting%20Room'%20license%20vs%20'Common%20Area%20Phone'%20license%20vs%20'E1%2BPhone%20System'%20license%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-911550%22%20slang%3D%22en-US%22%3E%26gt%3B%20I%20have%20confirmed%20that%20a%20meeting%20room%20license%20does%20not%20work%20for%20a%20Trio%20conference%20phone.%20It%20will%20not%20accept%20a%20meeting%20invite.%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20meeting%20room%20license%20absolutely%20will%20work%20with%20a%20Trio%20phone.%20However%2C%20you%20have%20to%20ensure%20the%20account%20is%20created%20as%20a%20room%20mailbox%20and%20is%20configured%20correctly.%20See%20Jeff%E2%80%99s%20blog%20post%20for%20the%20configuration%20instructions%3A%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22http%3A%2F%2Fblog.schertz.name%2F2019%2F08%2Fexchange-resource-mailbox-configuration-for-meeting-rooms%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fblog.schertz.name%2F2019%2F08%2Fexchange-resource-mailbox-configuration-for-meeting-rooms%2F%3C%2FA%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-912794%22%20slang%3D%22en-US%22%3ERe%3A%20'Meeting%20Room'%20license%20vs%20'Common%20Area%20Phone'%20license%20vs%20'E1%2BPhone%20System'%20license%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-912794%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F80266%22%20target%3D%22_blank%22%3E%40Ryan%20Steele%3C%2FA%3EThis%20explains%20a%20lot.%26nbsp%3B%20The%20reason%20I%20never%20used%20a%20room%20mailbox%20is%20because%20of%20the%20DeleteComments%20parameter%20default%20as%20you%20explained.%26nbsp%3B%20So%20using%20the%20standard%20choice%20of%20a%20room%20mailbox%20didn't%20work%20with%20the%20Trio%20for%20meeting%20requests%20and%20using%20a%20regular%20account%20gets%20blocked%20so%20it%20cannot%20login.%26nbsp%3B%20Making%20it%20a%20room%20mailbox%20and%20changing%20the%20DeleteComments%20should%20fix%20that.%26nbsp%3B%20Thanks%20for%20the%20info.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20can%20see%20that%20this%20is%20all%20too%20confusing%20though.%26nbsp%3B%20The%20meeting%20room%20mailbox%20option%20didn't%20exist%20until%20over%20a%20year%20after%20the%20push%20by%20Microsoft%20to%20move%20from%20Skype%20to%20Teams.%26nbsp%3B%20The%20DeleteComment%20parameter%20is%20something%20most%20people%20wouldn't%20see%20until%20they%20dig%20into%20why%20they%20can't%20get%20a%20conference%20room%20to%20work.%26nbsp%3B%20Even%20the%20support%20tech%20that%20directed%20me%20to%20your%20posting%20didn't%20know%20about%20it%20either.%26nbsp%3B%20This%20is%20the%20stuff%20that%20drives%20implementation%20people%20crazy%20but%20thanks%20for%20the%20info.%26nbsp%3B%20My%20conference%20room%20is%20working%20now%20but%20I%20will%20try%20again%20with%20the%20meeting%20room%20license%20later.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1083358%22%20slang%3D%22en-US%22%3ERe%3A%20'Meeting%20Room'%20license%20vs%20'Common%20Area%20Phone'%20license%20vs%20'E1%2BPhone%20System'%20license%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1083358%22%20slang%3D%22en-US%22%3E%3CP%3EMeeting%20Rooms%20WITHOUT%26nbsp%3BAudio%20Conferencing%3A%20Is%20there%20much%20difference%20with%20this%20vs.%26nbsp%3BCommon%20Area%20Phone%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Trent Queen
Contributor

We have 7 meetings rooms (a mix of Polycom VVX and Logitech SmartDocks), what is the best way to license them? I can see there is a thing called 'Meeting Room' which is $20.60, 'Common Area Phone' which is $11.00 or 'E1+Phone System' which is $20.40.

 

What should I be using? and what is the difference between them?

 

Thanks 

Trent.

16 Replies

Common Area Phone will give you the Skype for Business/Teams capabilities and Phone System licenses, so this is for a basic phone like a Polycom VVX in a common area (like a conference room).

 

With the Meeting Room license you get more stuff: Teams, Skype for Business, Phone System, Audio Conferencing and Intune. The mailbox you will setup as a room mailbox (no license).

 

With the E1+Phone system you will get some stuff you won't need and you won't get the Intune and Audio Conferencing that you get with the Meeting Room license.

 

So Common Area Phone licenses for the VVX and Meeting Room license for the Logitechs. You might need to add Calling Plan license to these if you want to dial out from these devices but that depends on your Phone System setup.

Hello Team

Thank you so much for this. I do have a dilemma though. I have a Polycom Trio 8800 and it is assigned the Common Area license. The meet now is enabled on the phone and it does work, however, I was thinking with that we will be able to have a full audio conference on it, but does not seem to be the case. I am sure am missing something. Do I need to assign the Meeting Room license to the user, if yes, will that give it an audio conference number with PIN ext for users to dial into? Any recommendation and advise will be highly appreciated

I'm not sure what you mean with "full audio conference"? 

You need the Audio Conferencing license to create dial-in conferences but, when you use the Meet now from the Trio you won't send out an mail invitation, you will invite users directly to the meeting.

 

If you wan't to create a conference with dial-in you should create it and invite the device to the meeting. You and the device will be able to join using Skype and other user will be able to join the meeting with dial-in. You have to have the audio conferencing license for your account (since you schedule and invite to the meeting), not the device.

Hi

 

We have recently purchased the new Meeting Room SKU that was released on the 1st December 2018 but there seems be very little information around.

 

Is it possible by assigning the Meeting room licence to a device/meeting room resource for a licenced user under tenant to access there normal files and folders, even if it was by accessing there OneDrive account?

We purchased the meeting room licence to try and avoid licensing each user with an audio conferencing licence but if users can't get access to there files we may have to re-think using the meeting room sku.

 

Thanks

Kris

@Linus Cansby While devices accounts are not used to send meeting invitations, the devices still need to be licensed with Audio Conferencing to cover one specific capability: inviting PSTN attendees ad-hoc to an active meeting from the device.  Meaning that if someone is in the room, connected to a Skype or Teams meeting and they use the device to 'Add a Participant' and then select a PSTN phone number as the new attendee, the outbound PSTN call placed by the meeting MCU requires that the device is licensed with Audio Conferencing.

 

@DEBEL77 The main difference between Common Area Phone and Meeting Room licenses is that the CAP license does not support Exchange, while the Meeting Room licenses does.  Common Area Phones which simply are used to place audio calls are what the CAP license was designed for, and bookable rooms where users join meetings from a calendar are what the Meeting Room license was created for.

@Linus Cansby I have a similar question.

 

The Common Area Phone includes the Phone System (required for calling plan). If we assign the Common Area Phone to a User and then assign the Calling Plan, does this provide Microsoft Teams calling ability to Users. 

Note: This is not for a physical phone but for the User.

@manoj_cse What will you use that user for? Will they use the Teams client to sign in so that they already have a E1/E3 license? Then I guess the Phone System Add-On is better.

@Linus Cansby The User already has the Office 365 Business Premium License with Common Area Phone License. So if we now add the calling plan license, would he be able to make calls, considering the Common Area Phone comes with Phone System.

The doubt is if the Common Area Phone license works for Users. Is it specifically and only used for physical phone licensing?

@Jeff_Schertz "inviting PSTN attendees ad-hoc to an active meeting from the device."

 

so if I just invite PSTN attendees from any other account that is joined to the conference ID then there is no need for this functionality?  they're charging effectively $4/mo as part of this SKU so people don't have to reach into their pocket and make an outbound call from their E5 licensed mobile client instead of the device on a table? that's a bad look.

@Jeff_Schertz 

 

Are you sure regarding the CAP license not supporting an Exchange mailbox? I can't see a reason why you assign CAP to a room mailbox to facilitate meeting room booking. Your own article mentions this should be possible as well.

 

"There is no special account type like with the server platform as any standard online user account can be used with the new license, meaning that Exchange calendaring is available for phones registered using a CAP-enabled account"

 

http://blog.schertz.name/2018/05/hot-desking-and-common-area-phones-in-skype-for-business/

@Steve Bedwell There has been some back and forth on this topic over time.  Originally Microsoft did not intend for the CAP account in Skype for Business to be mailbox enabled and mentioned that Exchange Online might be pulled from that license.

But now that the license will be used by Teams that is likely not going to happen. The behavior I do see currently is that if a Common Area Phone license (or a Meeting Room license) is added to a standard User mailbox account, its mailbox will vanish (but it will return if a regular license is reapplied).  But if those licenses are assigned to an account with a Room mailbox and enabled using the CsMeetingRoom cmdlets then the mailbox will be fine.

 

It appears that using those device licenses on a user account causes the mailbox to be blocked, by design.

 

@Jeff_SchertzMicrosoft needs to fix this license nightmare.  It is way too confusing to understand which license applies to which purpose and it keeps changing as seen by these threads.  I have confirmed that a meeting room license does not work for a Trio conference phone.  It will not accept a meeting invite.  I was also unsuccessful using a common area phone but it works with an E5 license.  The E5 of course is overkill but I was able to use a phone system - virtual user license to get it working instead.  Yet I am told by the support team that it should not work that way. 

Why not provide exchange/mailbox connectivity for all phone related licenses and include the audio conferencing within that license so we don't have to select multiple licenses for each purpose?  It's too granular.  Why have both a CAP and Meeting Room license?  Make those the same with mailbox enabled and audio conferencing included.  Even common area phones should have voicemail capabilities.  Why block these device licenses on a user account?  Does it matter whether it is a room account or user account?  Otherwise, don't allow the license to be assigned at all so there is no confusion.   

> I have confirmed that a meeting room license does not work for a Trio conference phone. It will not accept a meeting invite.

The meeting room license absolutely will work with a Trio phone. However, you have to ensure the account is created as a room mailbox and is configured correctly. See Jeff’s blog post for the configuration instructions:

http://blog.schertz.name/2019/08/exchange-resource-mailbox-configuration-for-meeting-rooms/

@Ryan SteeleThis explains a lot.  The reason I never used a room mailbox is because of the DeleteComments parameter default as you explained.  So using the standard choice of a room mailbox didn't work with the Trio for meeting requests and using a regular account gets blocked so it cannot login.  Making it a room mailbox and changing the DeleteComments should fix that.  Thanks for the info.

 

You can see that this is all too confusing though.  The meeting room mailbox option didn't exist until over a year after the push by Microsoft to move from Skype to Teams.  The DeleteComment parameter is something most people wouldn't see until they dig into why they can't get a conference room to work.  Even the support tech that directed me to your posting didn't know about it either.  This is the stuff that drives implementation people crazy but thanks for the info.  My conference room is working now but I will try again with the meeting room license later.

Meeting Rooms WITHOUT Audio Conferencing: Is there much difference with this vs. Common Area Phone?