How to configure Office 365 Unified Messaging with Skype for Business


Configuring Skype for Business and Office 365 Unified Messaging for Voicemail is a fairly simple task. Of course no task should be undocumented, so here goes.

Environment

On premise Skype for Business 2015 deployment
Mail delivered via Office 365
On premise users synchronised back to Office 365 via DirSync

NOTE: UM connectivity, in this case is done via Federation to Office 365. So it goes without saying that a working Edge infrastructure is required. Also Federation needs to be enabled (and working)

First we will configure the Skype for Business Front End Pool

From the Skype Front End Server
1. Ensure that Federation is enabled for the Edge Configuration (Federation needs to be enabled in the Topology). Confirm by the following cmdlet:-

Get-CsAccessEdgeConfiguration

RoutingMethod

To change AccessEdgeConfiguration:-

Set-CsAccessEdgeConfiguration -enablepartnerdiscovery $true -UseDnsSrvRouting -AllowFederatedUsers 1

NOTE Partner discovery may be either enabled or disabled.

2. Adding O365 as a hosting provider for UM

New-CsHostingProvider -Identity “Exchange Online” -Enabled $True -EnabledSharedAddressSpace $True -HostsOCSUsers $False -ProxyFqdn “exap.um.outlook.com” -IsLocal $False -VerificationLevel UseSourceVerification

exap.um.outlook.com

3. Make sure these changes have been replicated (don’t continue until it has!)

Force Replication with:

Invoke-CsManagementStoreReplication

Confirm with Replication Successfully completed:

Get-CsManagementStoreReplicationStatus

check replication

4. We now need to add the Hosted Voicemail policy, The Office 365 Tenant Name is required for this. The policy is added with the following cmdlet:

NOTE “CloudUM” in my case is the name I gave the on premise UM Policy

New-CsHostedVoicemailPolicy -identity CloudUM -Destination exap.um.outlook.com -Description “Office 365 Voicemail” -Organization “tenantname.onmicrosoft.com

CloudUM

TIP: To find the Organization name login to O365 Admin Portal. 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

The Organization Name is also the *Default Domain as defined in the Admin Center in the Company Profile page

Skype for Business Office 365 Unified Messaging

Skype for Business Office 365 Unified Messaging

Next, we need to configure Office 365

From the Office 365 Portal

  1. Navigate to Unified Messaging (Office 365 Admin Center – Exchange – Unified Messaging
exchange

2. Add a new UM Dial Plan by clicking on the +

UM Dial Plan

3. Complete the New UM Dial Plan Page as per your requirements and click Save

Office 365 Dial Plan
 4. To assign the Subscriber access number, edit the UM Dial Plan you just created.
UM Edit
5. Click on configure
Subscriber access configure
6. Select Outlook Voice Access and add the DDI\DID assigned to the ExUmContact on premise as DisplayNumber (see next step)
OVA DDI

Next we head back to Skype for Business

  1. Create the UM Contact

New-CsExUmContact -displaynumber +613456789 –sipaddress SIP:EX_UM_365_SA@ucsorted.com -registrarpool pool01.ucsorted.com -ou “OU=IT,OU=UCSorted,DC=com”

TIP: I often come across a request to change Subscriber Access number, use Set-ExUmContact to change it if you need too.

NOTE: By specifying the “DisplayNumber” the LineUri is also set (I know its odd)

New-CsExUmContact

2. Assign the Hosted Voicemail Policy to the EX UM Contact

Grant-cshostedvoicemailpolicy –identity “CN={f169db8b-….DC=au” –policyname CloudUM

TIP: I am not very fond of copying the identity in this manner. Since I have added only the 1 exumcontact I just do the following:-

Get-CsExUmContact | Grant-CsHostedVoicemailPolicy -PolicyName CloudUM

Then we switch to Exchange Online PowerShell

TIP: Use the following script to connect to EOL:

$UserCredential = Get-Credential
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection

Import-PSSession $Session

Exchange Online

Next,

Set-UMmailboxpolicy -identity “Office 365 UM Default Policy” -SourceForestPolicy “CloudUM”

ummailboxpolicy

TIP: The identity is that of the Office 365 UM Mailbox Policy (not the UM Dial Plan)

The following step only appies if UM is already deployed on premise and this UM deployment is part of migrating UM to O365. This is done from the on premise exchange environment.

Set-UMmailboxpolicy -identity “On Premise UM Policy” -SourceForestPolicy “CloudUM”

Finally, time to configure users

IMPORTANT

You cannot have a spilt setup where UM is in O365 and the user mailbox is on premise or vice versa.

2 steps are required for enabling users for UM in O365:-

  1. From SkypefB – Grant the user the Hosted Voicemail Policy and enable the user for Hosted Voicemail
  2. From O365 – Enable the user for UM

Within Skype for Business 2015 PowerShell

Grant-cshostedvoicemailpolicy –identity “paulb” –policyname CloudUM

get-csuser –identity “paulb”

Set-csuser –identity “paulb” –hostedvoicemail $true

Within O365 Exchange Admin Center

Navigate to Recipients (Office 365 Admin Centre – Exchange – Recipients)

Find the user you would like to enable for UM and click Enable

O365 Recipients

Browse for the O365 UM Mailbox Policy and click next

UM Mailbox Policy

Provide the required extension number and PIN settings, click Finish to complete.

UM Extension

Of course synchronization by way of DirSync is required to ensure that the account is enabled for unified messaging.

Advertisements

About Paul B

My name is Paul Bloem and I am employed at Lexel Systems in New Zealand as a Principal Consultant for Unified Communications. I have been working on enterprise voice solutions for over 20 years. My first 10 years were spent working for a Telco in South Africa (Telcom SA). This is where all the groundwork happened as I was exposed to just about every aspect of telecommunication you could imagine. I develop an interest in PBX technologies and eventually became the go-to guy. Next, I had a 10 year run at Siemens South Africa, most of my time there was as a Technical Trainer. During this time VoIP hit the world stage, I had the privilege of introducing VoIP both as H.323 and later SIP across the Siemens HiPath 4000 solution stack. In 2008 I immigrated to New Zealand with my newly attained MCSE, I was ready to go where no PBX Techie had gone before. I was employed to explore OCS 2007 and that was pretty much the beginning of the end for me. I have been working on OCS and Lync ever since. My current role focuses exclusively on Lync and associated technologies.. That includes pre-sales, consulting, architecture and design, training and support. I even get to play in the development space from time to time - focus on play ;-) I was nominated as a Microsoft VTSP for Lync early in 2013 and also awarded Microsoft's MVP award for Lync in 2014.
This entry was posted in Office 365, Unified Messaging, voicemail and tagged . Bookmark the permalink.

10 Responses to How to configure Office 365 Unified Messaging with Skype for Business

  1. Pingback: How to configure Office 365 Unified Messaging with Skype for Business | The Organized Assistant

  2. Hendrik du Plessis says:

    Hi Paul.

    Thank you for the great article. Have you ever tested O365 UM compatibility with 3PIP phones like the Snom UC Edition?

    Regards

    Like

    • Paul B says:

      Hi Hendrik, I sure have. I have a SNOM 710 on my desk doing the job well. Occasionally there is a delay before the message button indicates a message is waiting. I believe that may be to latency from me to O365.

      Like

  3. jamesitpro says:

    Hi Paul, thanks for the post. I followed the steps and enabled my user for unified messaging. When I call my DDI the line goes dead after a few rings and doesn’t redirect to Voicemail. Do you know where to start with troubleshooting this issue?

    Like

    • Paul B says:

      Hi James, I have added a few screen shots on adding the Subscriber Access number to the post. Basically you need to add the DDI in O365 to the Subscriber Access config and also make sure that its the same DDI you assigned on premise to the ExUmContact.
      Let me know how you get on.

      Like

      • jamesitpro says:

        Thanks Paul. My colleague had a look this morning. He changed a couple of settings in the Dialing rules & authorization on Office 365 and it started working. Thanks again.

        Like

  4. Pingback: Shared Address Space Routing is Disabled | greiginsydney.com

  5. Dewalt says:

    HI Paul, I have configured the policies as per your steps, but I am not able to get PSTN calls to reach the AA or SA numbers. I am able to call the services from a Skype client. I get the below message in clslogger.

    ms-diagnostics: 1008;reason=”Unable to resolve DNS SRV record”;domain=”domain.global”;dns-srv-result=”NegativeResult”;dns-source=”InternalCache”;source=”acedge01.domain.global”
    ms-edge-proxy-message-trust: ms-source-type=EdgeProxyGenerated;ms-ep-fqdn=acedge01.domain.global;ms-source-verified-user=verified

    The edge server can resolve external DNS fine and the hybrid connection is working as expected. I read in another post that they had to change the default SIP domain to resolve the issue, but we have another client with the same configuration and they are working fine so I do not want just go and change the default SIP domain.

    Any advise is appreciated.

    Like

    • Paul B says:

      Hi Dewalt, firstly, I will assume that your domain “domain.global” is valid externally. Next validation, does federation work as expected? The error you have posted looks very much like what is seen when the edge server is unable to resolve the _sipfederation._tls record so I’d check that too (when this record is not resolvable it generally affects federation). Cheers, Paul

      Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s