Home

Common Area Phones

%3CLINGO-SUB%20id%3D%22lingo-sub-41820%22%20slang%3D%22en-US%22%3ECommon%20Area%20Phones%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-41820%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWas%20wonder%20if%20and%20when%20common%20area%20phones%20will%20be%20supported%20with%20Skype%20Online%20and%20what%20people%20are%20doing%20in%20the%20interirm.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAre%20you%20assigning%20generic%20ID's%20and%20logging%20into%20them%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3CP%3ELT%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-41820%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EVoice%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-338523%22%20slang%3D%22en-US%22%3ERe%3A%20Common%20Area%20Phones%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-338523%22%20slang%3D%22en-US%22%3E%3CP%3EHas%20anyone%20been%20successful%20getting%20the%20provisioning%20to%20work%20on%20a%20Polycom%20VVX%20phone%3F%20I%20have%20tried%20several%20different%20times%20and%20not%20had%20a%20successful%20provisioning.%20I%20have%20a%20ticket%20open%20with%20Microsoft%20but%20they%20seem%20to%20be%20slow%20playing%20the%20problem.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-236780%22%20slang%3D%22en-US%22%3ERe%3A%20Common%20Area%20Phones%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-236780%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20creating%20the%20account%20in%20AD%20and%20having%20it%20sync%20to%20O365.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20far%20as%20the%20phone%20working%20with%20the%20CAP%20SKU%20licensing%20all%20is%20good.%20Just%20can%20not%20get%20the%20provisioning%20working%20as%20others%20have%20mentioned%20it%20appears%20to%20fail%20whilst%20trying%20to%20change%20the%20password.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20currently%20login%20in%20as%20the%20CAP%20account%20by%20going%20to%20the%20polycom%20web%20gui%20and%20logging%20in%20as%20the%20user.%20Would%20be%20nice%20if%20the%20provisioning%20worked%20as%20designed.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20any%20update%20on%20this%20functionality%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELarry%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-218455%22%20slang%3D%22en-US%22%3ERe%3A%20Common%20Area%20Phones%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-218455%22%20slang%3D%22en-US%22%3E%3CP%3ETo%20folks%20that%20are%20on%20Hybrid%20setups%2C%20are%20you'll%20creating%20the%20CAP%20account%20in%20AD%20and%20syncing%20it%20to%20O365%2C%20or%20creating%20an%20O365-only%20account%20for%20these%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20case%20of%20the%20latter%2C%20how%20are%20you%20telling%20Skype%20On-Prem%20to%20send%20the%20calls%20to%20the%20Online%20user%3F%20There%20has%20to%20be%20some%20pointer%20to%20forward%20the%20calls%20to%20Skype%20Online%2C%20right%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-193745%22%20slang%3D%22en-US%22%3ERe%3A%20Common%20Area%20Phones%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-193745%22%20slang%3D%22en-US%22%3E%3CP%3EI%20can%20confirm%20the%20Firmware%20issue%20still%20exists%20on%20Polycom%20-%20we%20also%20saw%20the%20same%20%22An%20error%20occured%22%20using%20skypecap%20provisioning%2C%20used%20workaround%20aka%2Fms%2Fsphone.%3C%2FP%3E%3CP%3EAnybody%20else%20heard%20anything%20from%20support%20%3F%3C%2FP%3E%3CP%3EI%20will%20create%20a%20support%20ticket%20raising%20this%20issue%20again.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-179389%22%20slang%3D%22en-US%22%3ERe%3A%20Common%20Area%20Phones%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-179389%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F126329%22%20target%3D%22_blank%22%3E%40Alexander%20Grinman%3C%2FA%3E%3C%2FP%3E%0A%3CP%3EYup%2C%20getting%20the%20same%20thing%20here.%20Works%20fine%20for%20full%20Cloud%20accounts%20but%20doesn't%20work%20for%20hybrid%20accounts%20we%20get%20the%20same%20error%20your%20seeing.%26nbsp%3B%20I'm%20guessing%20its%20due%20to%20resetting%20the%20password%20when%20the%20phone%20is%20provisioned.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EStill%20not%20had%20MS%20support%20come%20back%20to%20say%20it's%20resolved%2C%20so%20will%20raise%20the%20question%20with%20them%20when%20they%20do.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-178652%22%20slang%3D%22en-US%22%3ERe%3A%20Common%20Area%20Phones%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-178652%22%20slang%3D%22en-US%22%3E%3CP%3EWell%2C%20I%20finally%20got%20around%20to%20doing%20some%20testing%20of%20my%20own%20today%2C%20using%20a%20Polycom%20VVX%20600%2C%20on%20software%20version%26nbsp%3B%3CSPAN%3E5.7.1.2205.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EAt%20this%20time%2C%20I%20was%20able%20to%20successfully%20provision%20the%20phone%20using%20an%20%22In%20Cloud%22%20account%20created%20directly%20in%20our%20Office%20365%20tenant.%20However%2C%20as%20we%20operate%20in%20a%20hybrid%20configuration%20with%20Skype%20for%20Business%20Server%202015%20in%20our%20environment%2C%20I%20was%20hoping%20this%20would%20also%20work%20for%20an%20account%20synced%20from%20our%20Active%20Directory%20and%20enabled%20with%20the%20required%20%22Common%20Area%20Phone%22%20license.%20This%20did%20not%20work%2C%20unfortunately%2C%20and%20produced%20the%20same%20error%20as%20before%2C%20seen%20below.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20331px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F31403iE8157D996869C55D%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22SfBOnline_CAP_Provisioning_OnPrem_Error_2.png%22%20title%3D%22SfBOnline_CAP_Provisioning_OnPrem_Error_2.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EI%20was%20hoping%20for%20a%20complete%20success%2C%20but%20will%20take%20progress%20where%20I%20can%20get%20it.%20Hopefully%20Microsoft%20will%20allow%20this%20to%20work%20with%20synced%20accounts%20just%20as%20well%20as%20%22In%20Cloud%22%20accounts.%3CBR%20%2F%3E%3CBR%20%2F%3EHas%20anybody%20had%20any%20luck%20in%20getting%20this%20to%20provision%20successfully%20with%20an%20account%20synced%20from%20your%20Active%20Directory%20and%20assigned%20the%20%22Common%20Area%20Phone%22%20license%3F%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F121650%22%20target%3D%22_blank%22%3E%40Kevin%20Prudhoe%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EAs%20you%20had%20experienced%20this%20exactly%20the%20same%20as%20I%20did%20in%20our%20own%20environment%2C%20I%20as%20wondering%20if%20you%20had%20done%20any%20additional%20testing%20since%20these%20past%20few%20updates.%20Really%20curious%20to%20hear%20if%20you%20have%20the%20same%20results%20of%20success%20with%20an%20%22In%20Cloud%22%20account%20and%20still%20no%20luck%2Fsame%20results%2Ferror%20as%20previously%20seen%20with%20a%20synced%20account.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-177821%22%20slang%3D%22en-US%22%3ERe%3A%20Common%20Area%20Phones%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-177821%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F27877%22%20target%3D%22_blank%22%3E%40Steve%20Whitcher%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F72755%22%20target%3D%22_blank%22%3E%40Wayne%20Stuebing%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ELooks%20like%20Microsoft%20is%20pushing%20the%205.6.x%20firmware%20to%20the%20phone%20when%20connected%20to%20Skype%20for%20Business%20Online.%20Check%20out%20Martin%20Boam's%20experience%20with%20CAP%20Provisioning%20on%20his%20blog%2C%20where%20he%20mentions%20how%20to%20configure%20the%20IP%20Phone%20policy%20to%20prevent%20getting%20the%20older%20firmware%20pushed%20to%20the%20phone%3A%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fucmart.uk%2F2018%2F03%2F23%2Fsfb-online-common-area-phone-my-experience-so-far%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fucmart.uk%2F2018%2F03%2F23%2Fsfb-online-common-area-phone-my-experience-so-far%2F%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20short%2C%20you'll%20want%20to%20run%26nbsp%3B%3CSTRONG%3E%3CSPAN%3ESet-CsIPPhonePolicy%20-EnableDeviceUpdate%3C%2FSPAN%3E%3C%2FSTRONG%3E%20%3CSTRONG%3E%24false%3C%2FSTRONG%3E%20in%20order%20to%20stop%20the%20lower%20firmware%20from%20getting%20installed%20on%20the%20phone%20after%20900%20seconds%20of%20inactivity.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAlso%2C%20there%20is%20some%20good%20news.%20Polycom%20literally%20just%20yesterday%20released%20the%20newer%205.7.1%20firmware%20for%20the%20various%20VVX%20models%2C%20so%20may%20be%20worth%20trying%20that%20out.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-177817%22%20slang%3D%22en-US%22%3ERe%3A%20Common%20Area%20Phones%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-177817%22%20slang%3D%22en-US%22%3E%3CP%3EI%20saw%20the%20same%20behavior%20here.%26nbsp%3B%20I%20only%20have%20one%20polycom%20phone%20currently%2C%20for%20evaluation%2Fproof%20of%20concept%20purposes.%26nbsp%3B%20I%20manually%20updated%20it%20to%20the%20latest%20firmware%20available%20from%20polycom%2C%20v5.7.0%2C%20only%20to%20find%20that%20the%20next%20day%20it%20had%20rolled%20back%20to%20v5.6.0.%26nbsp%3B%20I%20haven't%20gotten%20to%20trying%20the%20Common%20Area%20Phone%20licensing%20yet%2C%20so%20it%20wasn't%20a%20big%20deal%20at%20the%20time.%26nbsp%3B%20I%20assumed%20that%20the%20firmware%20was%20just%20so%20new%20it%20hadn't%20been%20updated%20on%20the%20skype%20servers%20yet%2C%20but%20it's%20been%20almost%20a%20month%20and%20nothing%20has%20changed.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-177801%22%20slang%3D%22en-US%22%3ERe%3A%20Common%20Area%20Phones%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-177801%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20is%20working%20now%20but%20there%20is%20still%20a%20an%20issue%20for%20Polycom%20devices.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIt%20looks%20like%20that%20the%20firmware%20that%20is%20hosted%20via%20cloud%20PBX%20is%20incompatible%20it%20lacks%20the%20CAP%20options.%20When%20you%20provision%20a%20device%20it%20signs%20in%20that%20does%20an%20firmware%20downgrade%20and%20removes%20CAP.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-177764%22%20slang%3D%22en-US%22%3ERe%3A%20Common%20Area%20Phones%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-177764%22%20slang%3D%22en-US%22%3EI%20just%20tested%2C%20and%20can%20confirm%20it's%20working%20great%20now!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-175925%22%20slang%3D%22en-US%22%3ERe%3A%20Common%20Area%20Phones%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-175925%22%20slang%3D%22en-US%22%3E%3CP%3EO365%20support%20have%20confirmed%20that%20this%20is%20a%20known%20issue%20on%20their%20backend%20infrastructure%2C%20and%20a%20fix%20is%20expected%20W%2FC%3A%202nd%20April%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-174587%22%20slang%3D%22en-US%22%3ERe%3A%20Common%20Area%20Phones%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-174587%22%20slang%3D%22en-US%22%3EIf%20you%20do%20please%20let%20me%20know%2C%20so%20we%20can%20collaborate%20to%20solve%20this%20issue.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-174580%22%20slang%3D%22en-US%22%3ERe%3A%20Common%20Area%20Phones%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-174580%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F129760%22%20target%3D%22_blank%22%3E%40Joseph%20Kuehner%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20suppose%20from%20the%20perspective%20of%20the%20physical%20phone%20handset%20itself%2C%20this%20workaround%20would%20be%20acceptable%2C%20since%20the%20phone%20is%20in%20CAP%20mode%20and%20does%20ultimately%20work.%20Hopefully%20this%20will%20not%20need%20to%20be%20used%20by%20everyone%2C%20as%20it%20is%20not%20especially%20convenient%20to%20have%20to%20enter%20a%20user%20name%20and%20password%20to%20sign%20the%20phone%20in%2C%20when%20this%20is%20the%20very%20thing%20which%20CAP%20Provisioning%20was%20meant%20to%20simplify.%20I%20sure%20hope%20Microsoft%20can%20figure%20out%20what%20is%20going%20wrong%20on%20the%20backend.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F34020%22%20target%3D%22_blank%22%3E%40Erwin%20Bierens%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20have%20not%20actually%20opened%20a%20ticket%20with%20Microsoft%20just%20yet%2C%20though%20likely%20will%20if%20no%20progress%20on%20this%20is%20made%20this%20week.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-174544%22%20slang%3D%22en-US%22%3ERe%3A%20Common%20Area%20Phones%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-174544%22%20slang%3D%22en-US%22%3E%3CP%3EI%20was%20able%20to%20figure%20out%20a%20workaround.%20Instead%20of%20using%20the%20CAP%20provisioning%20I%20was%20able%20to%20sign%20the%20phone%20in%20using%20the%20aka.ms%2Fsphone%20instead%20of%20aka.ms%2Fskypecap.%20CAP%20mode%20on%20the%20Polycom%20still%20works%20on%20the%20phone.%20I%20can%20make%2Freceive%20PSTN%20and%20regular%20Skype%20calls%20with%20no%20issue.%20I%20will%20probably%20need%20to%20move%20forward%20with%20this%20method%20as%20I%20am%20deploying%20about%2040%20conference%20room%20phones%20next%20week.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-174531%22%20slang%3D%22en-US%22%3ERe%3A%20Common%20Area%20Phones%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-174531%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F126329%22%20target%3D%22_blank%22%3E%40Alexander%20Grinman%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F121650%22%20target%3D%22_blank%22%3E%40Kevin%20Prudhoe%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F129760%22%20target%3D%22_blank%22%3E%40Joseph%20Kuehner%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F27883%22%20target%3D%22_blank%22%3E%40Wayne%20Stuebing%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHi%20All%2C%26nbsp%3B%3C%2FP%3E%0A%3CP%3ECan%20you%20provide%20me%20your%20ticket%20numbers%20in%20a%20direct%20message%3F%20I%20also%20have%20a%20open%20ticket%20and%20trying%20to%20consolidate%20this%20issue%20because%20it%20looks%20like%20something%20is%20going%20wrong%20in%20the%20backend%20of%20Skype%20for%20Business%20Online.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ECheers%2C%3C%2FP%3E%0A%3CP%3E-Erwin%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CDIV%20class%3D%22user-login%22%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-174126%22%20slang%3D%22en-US%22%3ERe%3A%20Common%20Area%20Phones%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-174126%22%20slang%3D%22en-US%22%3E%3CP%3EGot%20the%20same%20thing%20as%20well%20when%20trying%20to%20use%20the%20web%20portal.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAlso%20looks%20like%20there%20is%20nothing%20in%20the%20docs%20on%20using%20powershell%20to%20due%20this%20yet.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-173427%22%20slang%3D%22en-US%22%3ERe%3A%20Common%20Area%20Phones%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-173427%22%20slang%3D%22en-US%22%3E%3CP%3EI%20worked%20with%20MS%20today%20on%20this%20same%20issue.%20The%20guy%20I%20talked%20to%20was%20stumped%20and%20had%20to%20talk%20to%20engineering.%20I%20am%20waiting%20on%20him%20to%20get%20back%20to%20me.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-173238%22%20slang%3D%22en-US%22%3ERe%3A%20Common%20Area%20Phones%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-173238%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20SKU%20is%20now%20available%20to%20purchase%20-it's%20basically%20Skype%20Online%20Plan%202%20plus%20Cloud%20System%20at%20a%20reduced%20cost.%20You%20still%20need%20to%20by%20a%20Calling%20Plan%20as%20an%20add-on%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-172308%22%20slang%3D%22en-US%22%3ERe%3A%20Common%20Area%20Phones%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-172308%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F121650%22%20target%3D%22_blank%22%3E%40Kevin%20Prudhoe%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYou%20are%20experiencing%20exactly%20the%20same%20issues%20which%20are%20observed%20in%20our%20own%20environment.%20Same%20exact%20errors%20as%20you%20as%20well.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EReally%20curious%20to%20hear%20what%20Microsoft%20says%20about%20this.%20I%20think%20this%20may%20shed%20some%20light%20for%20a%20lot%20of%20people%20confused%20and%20frustrated%20by%20this%20new%20license%20who%20were%20excited%20about%20its%20launch.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-172091%22%20slang%3D%22en-US%22%3ERe%3A%20Common%20Area%20Phones%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-172091%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20tried%20to%20provision%20a%20phone%20through%20the%20CAP%20portal%20and%20haven't%26nbsp%3Bbeen%20successful%2C%20likewise%20we're%20in%20a%20hybrid%20scenario.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ETrying%20a%20pure%20online%20account%20I%20get%20an%20error%3A%26nbsp%3BProvision%20failed%2C%20Correlation%20ID......%3C%2FP%3E%0A%3CP%3ETrying%20a%20synced%20AD%20user%20I%20get%20%22Error%2C%20we%20ran%20into%20a%20problem%22%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ELogged%20with%20MS%20support%2C%20so%20shall%20see%20what%20they%20say.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-170863%22%20slang%3D%22en-US%22%3ERe%3A%20Common%20Area%20Phones%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-170863%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20there%20anybody%20who%20has%20tried%20to%20provision%20any%20phones%20using%20this%20new%20license%20and%20manner%20of%20provisioning%3F%20We%20have%20activated%20a%20trial%20for%2025%20licenses%20of%20%22Common%20Area%20Phone%22%20in%20my%20organization%2C%20and%20have%20assigned%20the%20license%20and%20calling%20plan%2C%20as%20required.%20However%2C%20the%20actual%20provisioning%20seems%20to%20fail%20every%20time.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EDefinitely%20nothing%20wrong%20with%20the%20account%20itself%2C%20as%20no%20errors%20when%20checking%20the%20account%20in%20Skype%20for%20Business%20Online%20PowerShell.%20I%20thought%20it%20might%20be%20due%20to%20hybrid%20configuration%2C%20so%20tried%20with%20a%20pure%20%22In%20Cloud%22%20account%2C%20which%20isn't%20synced%20from%20our%20Active%20Directory%2C%20and%20that%20made%20no%20difference.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-167341%22%20slang%3D%22en-US%22%3ERe%3A%20Common%20Area%20Phones%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-167341%22%20slang%3D%22en-US%22%3E%3CP%3EActually%2C%20I%20was%20able%20to%20piece%20together%20some%20information%20about%20this%20from%20various%20sources.%26nbsp%3B%20I%20put%20together%20what%20I%20have%20in%20a%20short%20blog%20post%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22http%3A%2F%2Fwww.neighborgeek.net%2F2018%2F03%2Fcommon-area-phone-license-available-for.html%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fwww.neighborgeek.net%2F2018%2F03%2Fcommon-area-phone-license-available-for.html%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-167206%22%20slang%3D%22en-US%22%3ERe%3A%20Common%20Area%20Phones%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-167206%22%20slang%3D%22en-US%22%3E%3CP%3EAlejandro%20--%20Are%20you%20able%20to%20share%20any%20additional%20information%20about%20this%20new%20SKU%20yet%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESteve%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-151366%22%20slang%3D%22en-US%22%3ERe%3A%20Common%20Area%20Phones%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-151366%22%20slang%3D%22en-US%22%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F27877%22%20target%3D%22_blank%22%3E%40Steve%20Whitcher%3C%2FA%3E%20wrote%3A%3CBR%20%2F%3E%3CP%3EAlejandro%20-%20To%20be%20clear%2C%20when%20you%20say%20'this%20SKU'%2C%20do%20you%20mean%20a%20license%20specifically%20for%20common%20area%20phones%3F%26nbsp%3B%20If%20so%2C%20that's%20great%20news!%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E--%26gt%3B%20Correct%2C%20it's%20a%20license%20what%20is%20coming%20soon%20(expect%20it%20to%20be%20available%20in%20about%20a%20month%20or%20so).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20introduction%20of%20this%20SKU%20is%20intended%20to%20provide%20Microsoft%20customers%20the%20flexibility%20needed%20to%20license%20all%20calling%20devices%20in%20their%20Enterprise%20appropriately%20and%20compliantly%20%3CSTRONG%3Ewithout%20over%20licensing%3C%2FSTRONG%3E.%3C%2FP%3E%0A%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-151363%22%20slang%3D%22en-US%22%3ERe%3A%20Common%20Area%20Phones%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-151363%22%20slang%3D%22en-US%22%3E%3CP%3EJeff%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAfter%20upgrading%20to%20the%20December%20CU%20in%20Skype%20for%20Business%20On-Prem%20I%20have%20found%20out%20that%20my%20CX600%20and%20CX3000%20common%20area%20phones%20no%20longer%20support%20PIN%20Authentication.%20They%20all%20logged%20out%20after%20the%20update%20and%20were%20unable%20to%20log%20back%20in.%20Running%20the%20latest%20firmware%204531%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-151241%22%20slang%3D%22en-US%22%3ERe%3A%20Common%20Area%20Phones%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-151241%22%20slang%3D%22en-US%22%3E%3CP%3EAlejandro%20-%20To%20be%20clear%2C%20when%20you%20say%20'this%20SKU'%2C%20do%20you%20mean%20a%20license%20specifically%20for%20common%20area%20phones%3F%26nbsp%3B%20If%20so%2C%20that's%20great%20news!%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20have%20many%20phones%20not%20dedicated%20to%20a%20specific%20user%2C%20but%20to%20a%20position%20or%20department%2C%20and%20may%20people%20use%20those.%26nbsp%3B%20It%20seemed%20silly%20that%20to%20accomplish%20this%20with%20MS%20Phone%20System%20I%20would%20have%20to%20give%20each%20phone%20an%20E5%2BPSTN%20calling%20license*%2C%20when%20the%20ONLY%20thing%20it%20needs%20is%20the%20ability%20to%20make%20and%20receive%20phone%20calls.%26nbsp%3B%20(And%2C%20most%20of%20those%20don't%20even%20need%20to%20receive%20external%20calls%2C%20but%20should%20at%20least%20be%20capable%20of%20dialing%20out)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E*Or%20(E1%20or%20Skype4b%20plan%202)%2BCloudPBX%2BPSTN%20Calling%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-143471%22%20slang%3D%22en-US%22%3ERe%3A%20Common%20Area%20Phones%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-143471%22%20slang%3D%22en-US%22%3EHi%20Larry%2C%20March%201st%202018%20is%20the%20date%20that%20we%20can%20now%20share%20for%20this%20SKU%20to%20be%20available.%20Stay%20tuned%2C%20more%20details%20will%20come%20soon%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-42274%22%20slang%3D%22en-US%22%3ERe%3A%20Common%20Area%20Phones%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-42274%22%20slang%3D%22en-US%22%3EThanks.%20this%20is%20what%20I%20was%20implying%20-%20that%20you%20need%20to%20use%20a%20fully%20featured%20user%20account%20and%20phone%20that%20supports%20this%20to%20%22impersonate%22%20a%20common%20area%20phone.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-42141%22%20slang%3D%22en-US%22%3ERe%3A%20Common%20Area%20Phones%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-42141%22%20slang%3D%22en-US%22%3E%3CP%3EActually%20some%20devices%20labeled%20as%20'Common%20Area%20Phones'%20like%20the%20Polycom%20CX500%20are%20NOT%20supported%20witrh%20Skype%20for%20Business%20Online.%20%26nbsp%3BThese%20devices%20do%20not%20include%20a%20USB%20port%20and%20thus%20cannot%20be%26nbsp%3Bauthenticated.%20%26nbsp%3BSfB%20Online%20does%20not%20support%20PIN%20Authentication%20which%20is%20the%20only%20way%20to%20the%20traditional%20Common%20Area%20Phone%20account%20can%20authenticate.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20article%20covers%20user%20account%2Flicense%20requirements%20for%20phones%20used%20online%3A%26nbsp%3B%3CA%20href%3D%22http%3A%2F%2Fblog.schertz.name%2F2017%2F01%2Fskype-for-business-online-meeting-room-accounts%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fblog.schertz.name%2F2017%2F01%2Fskype-for-business-online-meeting-room-accounts%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUsing%20other%203PIP%20devices%20can%20emulate%20this%20approach%20buy%20using%20a%20regular%20user%20or%20meeting%20room%20account%20online%20(not%20CAP%20accounts).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-41918%22%20slang%3D%22en-US%22%3ERe%3A%20Common%20Area%20Phones%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-41918%22%20slang%3D%22en-US%22%3ESkype%20for%20Business%20Online%20does%20support%20common%20area%20phones%20but%20not%20in%20the%20same%20way%20as%20on-prem.%3CBR%20%2F%3EIt's%20a%20more%20simplistic%20approach%20in%20that%20the%20phone%20needs%20to%20have%20a%20user%20license%20and%20be%20set%20up%20like%20any%20normal%20user%20%26amp%3B%20handset.%3CBR%20%2F%3ESo%20yes%20-%20we%20have%20customers%20setting%20up%20generic%20accounts%20and%20logging%20into%20those.%3C%2FLINGO-BODY%3E
Highlighted
Larry Thomas
Occasional Contributor

Hi 

 

Was wonder if and when common area phones will be supported with Skype Online and what people are doing in the interirm. 

 

Are you assigning generic ID's and logging into them?

 

Thanks

LT

30 Replies
Skype for Business Online does support common area phones but not in the same way as on-prem.
It's a more simplistic approach in that the phone needs to have a user license and be set up like any normal user & handset.
So yes - we have customers setting up generic accounts and logging into those.

Actually some devices labeled as 'Common Area Phones' like the Polycom CX500 are NOT supported witrh Skype for Business Online.  These devices do not include a USB port and thus cannot be authenticated.  SfB Online does not support PIN Authentication which is the only way to the traditional Common Area Phone account can authenticate.

 

This article covers user account/license requirements for phones used online: http://blog.schertz.name/2017/01/skype-for-business-online-meeting-room-accounts/

 

Using other 3PIP devices can emulate this approach buy using a regular user or meeting room account online (not CAP accounts).

Thanks. this is what I was implying - that you need to use a fully featured user account and phone that supports this to "impersonate" a common area phone.
Hi Larry, March 1st 2018 is the date that we can now share for this SKU to be available. Stay tuned, more details will come soon

Alejandro - To be clear, when you say 'this SKU', do you mean a license specifically for common area phones?  If so, that's great news! 

 

We have many phones not dedicated to a specific user, but to a position or department, and may people use those.  It seemed silly that to accomplish this with MS Phone System I would have to give each phone an E5+PSTN calling license*, when the ONLY thing it needs is the ability to make and receive phone calls.  (And, most of those don't even need to receive external calls, but should at least be capable of dialing out)

 

*Or (E1 or Skype4b plan 2)+CloudPBX+PSTN Calling

Jeff,

 

After upgrading to the December CU in Skype for Business On-Prem I have found out that my CX600 and CX3000 common area phones no longer support PIN Authentication. They all logged out after the update and were unable to log back in. Running the latest firmware 4531


@Steve Whitcher wrote:

Alejandro - To be clear, when you say 'this SKU', do you mean a license specifically for common area phones?  If so, that's great news! 

 

--> Correct, it's a license what is coming soon (expect it to be available in about a month or so).

 

The introduction of this SKU is intended to provide Microsoft customers the flexibility needed to license all calling devices in their Enterprise appropriately and compliantly without over licensing.


 

Alejandro -- Are you able to share any additional information about this new SKU yet?

 

Steve

Actually, I was able to piece together some information about this from various sources.  I put together what I have in a short blog post:

 

http://www.neighborgeek.net/2018/03/common-area-phone-license-available-for.html

 

Is there anybody who has tried to provision any phones using this new license and manner of provisioning? We have activated a trial for 25 licenses of "Common Area Phone" in my organization, and have assigned the license and calling plan, as required. However, the actual provisioning seems to fail every time.

 

Definitely nothing wrong with the account itself, as no errors when checking the account in Skype for Business Online PowerShell. I thought it might be due to hybrid configuration, so tried with a pure "In Cloud" account, which isn't synced from our Active Directory, and that made no difference.

I've tried to provision a phone through the CAP portal and haven't been successful, likewise we're in a hybrid scenario.

 

Trying a pure online account I get an error: Provision failed, Correlation ID......

Trying a synced AD user I get "Error, we ran into a problem"

 

Logged with MS support, so shall see what they say.

 

@Kevin Prudhoe

 

You are experiencing exactly the same issues which are observed in our own environment. Same exact errors as you as well.

 

Really curious to hear what Microsoft says about this. I think this may shed some light for a lot of people confused and frustrated by this new license who were excited about its launch.

This SKU is now available to purchase -it's basically Skype Online Plan 2 plus Cloud System at a reduced cost. You still need to by a Calling Plan as an add-on

I worked with MS today on this same issue. The guy I talked to was stumped and had to talk to engineering. I am waiting on him to get back to me. 

Got the same thing as well when trying to use the web portal.

 

Also looks like there is nothing in the docs on using powershell to due this yet.

@Alexander Grinman

@Kevin Prudhoe

@Joseph Kuehner

@Wayne Stuebing

 

Hi All, 

Can you provide me your ticket numbers in a direct message? I also have a open ticket and trying to consolidate this issue because it looks like something is going wrong in the backend of Skype for Business Online.

 

Cheers,

-Erwin

 

I was able to figure out a workaround. Instead of using the CAP provisioning I was able to sign the phone in using the aka.ms/sphone instead of aka.ms/skypecap. CAP mode on the Polycom still works on the phone. I can make/receive PSTN and regular Skype calls with no issue. I will probably need to move forward with this method as I am deploying about 40 conference room phones next week. 

@Joseph Kuehner

 

I suppose from the perspective of the physical phone handset itself, this workaround would be acceptable, since the phone is in CAP mode and does ultimately work. Hopefully this will not need to be used by everyone, as it is not especially convenient to have to enter a user name and password to sign the phone in, when this is the very thing which CAP Provisioning was meant to simplify. I sure hope Microsoft can figure out what is going wrong on the backend.

 

@Erwin Bierens

 

We have not actually opened a ticket with Microsoft just yet, though likely will if no progress on this is made this week.

If you do please let me know, so we can collaborate to solve this issue.

O365 support have confirmed that this is a known issue on their backend infrastructure, and a fix is expected W/C: 2nd April

I just tested, and can confirm it's working great now!

It is working now but there is still a an issue for Polycom devices. 

 

It looks like that the firmware that is hosted via cloud PBX is incompatible it lacks the CAP options. When you provision a device it signs in that does an firmware downgrade and removes CAP. 

I saw the same behavior here.  I only have one polycom phone currently, for evaluation/proof of concept purposes.  I manually updated it to the latest firmware available from polycom, v5.7.0, only to find that the next day it had rolled back to v5.6.0.  I haven't gotten to trying the Common Area Phone licensing yet, so it wasn't a big deal at the time.  I assumed that the firmware was just so new it hadn't been updated on the skype servers yet, but it's been almost a month and nothing has changed.

@Steve Whitcher

@Wayne Stuebing

 

Looks like Microsoft is pushing the 5.6.x firmware to the phone when connected to Skype for Business Online. Check out Martin Boam's experience with CAP Provisioning on his blog, where he mentions how to configure the IP Phone policy to prevent getting the older firmware pushed to the phone:

https://ucmart.uk/2018/03/23/sfb-online-common-area-phone-my-experience-so-far/

 

In short, you'll want to run Set-CsIPPhonePolicy -EnableDeviceUpdate $false in order to stop the lower firmware from getting installed on the phone after 900 seconds of inactivity.

 

Also, there is some good news. Polycom literally just yesterday released the newer 5.7.1 firmware for the various VVX models, so may be worth trying that out.

Well, I finally got around to doing some testing of my own today, using a Polycom VVX 600, on software version 5.7.1.2205.

 

At this time, I was able to successfully provision the phone using an "In Cloud" account created directly in our Office 365 tenant. However, as we operate in a hybrid configuration with Skype for Business Server 2015 in our environment, I was hoping this would also work for an account synced from our Active Directory and enabled with the required "Common Area Phone" license. This did not work, unfortunately, and produced the same error as before, seen below.

 

SfBOnline_CAP_Provisioning_OnPrem_Error_2.png

 

 

I was hoping for a complete success, but will take progress where I can get it. Hopefully Microsoft will allow this to work with synced accounts just as well as "In Cloud" accounts.

Has anybody had any luck in getting this to provision successfully with an account synced from your Active Directory and assigned the "Common Area Phone" license?

 

@Kevin Prudhoe

As you had experienced this exactly the same as I did in our own environment, I as wondering if you had done any additional testing since these past few updates. Really curious to hear if you have the same results of success with an "In Cloud" account and still no luck/same results/error as previously seen with a synced account.

@Alexander Grinman

Yup, getting the same thing here. Works fine for full Cloud accounts but doesn't work for hybrid accounts we get the same error your seeing.  I'm guessing its due to resetting the password when the phone is provisioned.

 

Still not had MS support come back to say it's resolved, so will raise the question with them when they do.

 

 

I can confirm the Firmware issue still exists on Polycom - we also saw the same "An error occured" using skypecap provisioning, used workaround aka/ms/sphone.

Anybody else heard anything from support ?

I will create a support ticket raising this issue again.

To folks that are on Hybrid setups, are you'll creating the CAP account in AD and syncing it to O365, or creating an O365-only account for these?

 

In case of the latter, how are you telling Skype On-Prem to send the calls to the Online user? There has to be some pointer to forward the calls to Skype Online, right?

We are creating the account in AD and having it sync to O365.

 

As far as the phone working with the CAP SKU licensing all is good. Just can not get the provisioning working as others have mentioned it appears to fail whilst trying to change the password.

 

We currently login in as the CAP account by going to the polycom web gui and logging in as the user. Would be nice if the provisioning worked as designed.

 

Is there any update on this functionality?

 

Larry

Has anyone been successful getting the provisioning to work on a Polycom VVX phone? I have tried several different times and not had a successful provisioning. I have a ticket open with Microsoft but they seem to be slow playing the problem.

Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
46 Replies
Extentions Synchronization
Deleted in Discussions on
3 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
29 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
13 Replies