“Cloud computing is like sex in High School. Everybody is
talking about it, only few did it, and they– didn’t know what they are doing.”
Found somewhere in Internet
I have been thinking recently of one hypothetical scenario –
let’s say my company has domain “lynclog.com” and we host Exchange and Lync on
prem. We acquire small company B with domain “myuc.us”. The management decides
to decommission Exchange Server in Company B and move all users to Office 365
Exchange services. However, because "lynclog.com" already utilizes Lync
Enterprise Voice, we also want to decommission Company B’s PBX and provide EV to”
myuc.us” users. The main question is - how to resolve the problem with Unified
Messaging for Company B?
Let’s see if this is possible.
First, of course, I must sign up for Office 365 service. I
created tenant “forblog.onmicrosoft.com”, added “myuc.us” and verified it as
outlined on the online documentation.
For the purpose of this post, I created user “Myuc User” with
ID mu1@myuc.us. This represents all users from
Company B and the assumption here is the migration to Exchange Online has been
competed, mailboxes migrated etc.
Next step is to prepare the Cloud service for Unified
Messaging. I will create UM Dial Plan:
…and we can see, a default policy was automatically created.
I might modify it later.
***I have not created Auto Attendant at this point – I am
more interested if this concept will work to begin with…
This concludes my Cloud based user configuration. now let's prepare hosted Lync for Cloud Integration.
Run the following command from Lync Management Shell:
New-CsHostingProvider -Identity "Hosted UM"
-Enabled $True -enabledSharedAddressspace $True -HostsOCSUsers $false
-ProxyFqdn "exap.um.outlook.com" -IsLocal $False -VerificationLevel
UseSourceVerification
Get-CsHostingProvider -Identity "Hosted UM" cmdlet should return the following:
***I hit a bump at this point. Took me for a while to figure that the routing must be done toward the authoritative cloud domain. To see which domain is authoritative for my setup, I had to use Remote Power Shell:
$cred = Get-Credential
$s = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell -Credential $cred -Authentication Basic -AllowRedirection
$importresults = Import-PSSession $s
...and verify if our session is OK
Get-Mailbox
When i ran: Get-AcceptedDomain , the output showed that only "forblog.onmicrosoft.com" is Authoritative and I will use it in my Lync configuration.
Next, create new Hosted Voice Mail Policy:
***Note that I am using "forblog.onmicrosoft.com" as Organization, because this is the only Authoritative domain returned.
Get-CsHostedVoicemailPolicy -Identity "MYUC Domain" should return
***Yesterday I already added "myuc.us" as "Additional Supported Sip Domain" in my Lync topology, made the necessary changes in the public DNS, reissued the public certificate to include the new domain, you know the drill..Also, mu1@myus.us was added to Lync and provisioned for Enterprise Voice.
Now I will set HostedVoiceMailPolicy for this user to True. This way, when voicemail is to be deposited, my Lync on prem will route the call to the Cloud.
Set-CsUser -Identity lynclog\mu1 -HostedVoiceMail $True
...and grant the policy I created earlier:
Grant-CsHostedVoicemailPolicy -Identity lynclog\mu1 -PolicyName "MYUC Domain"
Let's examine our user' properties now:
Set-CsUser -Identity lynclog\mu1 -HostedVoiceMail $True
...and grant the policy I created earlier:
Grant-CsHostedVoicemailPolicy -Identity lynclog\mu1 -PolicyName "MYUC Domain"
Let's examine our user' properties now:
Time to test our setup.
The call was connected and I left new Voice Mail.
***One last note - in this test,on my Edge Server, I used Public Certificate issued form StartSSL.org. Office 365 did now have any problem with it...
