New-CsExUmContact -displaynumber +613456789 –sipaddress -registrarpool -ou “OU=IT,OU=UCSorted,DC=com” The Organization Name is also the * Default Domain as defined in the Admin Center in the Company Profile page Don’t use the same Tennant name as the on premise SIP domain as that will resolve to on premise and, of course, for voicemail it needs to resolve to O365 TIP: To find the Organization name login to O365 Admin Portal. New-CsHostedVoicemailPolicy -identity CloudUMPolicy -Destination exap.um. -Description “Office 365 Voicemail” -Organization “ ” NOTE “CloudUM” in my case is the name I gave the on premise UM Policy The policy is added with the following cmdlet: We now need to add the Hosted Voicemail policy, The Office 365 Tenant Name is required for this. Make sure these changes have been replicated (don’t continue until it has!)Ĭonfirm with Replication Successfully completed:Ĥ. New-CsHostingProvider -Identity “Exchange Online” -Enabled $True -EnabledSharedAddressSpace $True -HostsOCSUsers $False -ProxyFqdn “exap.um.” -IsLocal $False -VerificationLevel UseSourceVerificationģ. ![]() NOTE Partner discovery may be either enabled or disabled.Ģ. Set-CsAccessEdgeConfiguration -enablepartnerdiscovery $true -UseDnsSrvRouting -AllowFederatedUsers 1 Ensure that Federation is enabled for the Edge Configuration (Federation needs to be enabled in the Topology). Also Federation needs to be enabled (and working) First we will configure the Skype for Business Front End Poolġ. So it goes without saying that a working Edge infrastructure is required. NOTE: UM connectivity, in this case is done via Federation to Office 365. ![]() On premise users synchronised back to Office 365 via DirSync On premise Skype for Business 2015 deployment Of course no task should be undocumented, so here goes. Configuring Skype for Business and Office 365 Unified Messaging for Voicemail is a fairly simple task.
0 Comments
Leave a Reply. |