Skip to main content

Unable to leave Voice Mail for Skype for Business users.

Unable to leave Voice Mail for Skype for Business users.

ms-diagnostics: 15014;reason=”Hosted Voicemail Policy assigned to the user is not fully configured. Destination or Organization might be null”;source=””;appName=”ExumRouting”

Recently I came across issue, were users are unable to leave VoiceMail. Their exchange mailbox migrated recently to Exchange On-Premise.  All affected users Skype for Business SIP account and Exchange mailbox both are homed on On-Premise Skype for Business (SFB) /Lync Server and Exchange server respectively.

When I capture UCCAPILOG and Monitoring log for Voicemail failures, ms-diagnostics says Hosted Voicemail Policy assigned to the user is not fully configured. Destination or Organization might be null

But in my case user’s mailbox and SIP address are homed on-premise server not on Exchange UM Online, when checked user (Get-CsUser -Identity “Balu Ilah”), result shows ‘HostedVoiceMail’ shows True.

Why Voicemail routes to hosted exchange UM online?

Remember ‘HostedVoiceMail” value attribute tells that user enabled for Hosted Voicemail, and Hosted VoiceMail policy determine how to route Voicemail to Hosted Exchange UM. A hosted voice mail policy provides information to the Skype for Business/ Lync Server ExUM Routing application about where to route calls for users whose mailboxes are located on a hosted Exchange services.

In my case users SfB account and Exchange mailbox homed on On-Premise Server but ‘HostedVoiceMail’ attribute shows ‘True’, means my account enabled for SFB/Lync Server to use an Exchange UM hosted voicemail service. hosted VoiceMail policy determines how to route unanswered calls to the user to a hosted Exchange UM service (Exchange Online).

However, all users including me who are unable to leave voicemail are homed on SFB/Lync Server and Exchange Server on-premise. So, it should not route voicemail to Hosted Exchange UM service (Online) but it is routing and failing.

Let’s troubleshoot this behavior:  

To resolve this, I have tried to manually set “HostedVoiceMail” attribute value as False/Null in SFB/Lync Server, but is automatically getting changed from False/Null to True, as soon as DirSync runs (by default every 30 mins). That’s how server learns that to send Voicemail to hosted Exchange UM service, however both SFB/Lync and mailbox are on-premise so obviously, voicemail fails as expected.

What might have had happen, When User mailbox moved back to On-Premise from Exchange Online, for Exchange online msExchUCVoiceMailSettings attribute did not change to $Null.

What is msExchUCVoiceMailSettings, attribute and why we need this? This is an attribute which get created when Active Directory schema prepared for SFB/Lync Server. Also, this attribute holds voicemail setting shared by SFB/Lync Server and Exchange UM Service (online). The hosted Exchange online may in some cases set the value of the msExchUCVoiceMailSettings attribute in the process of enabling Exchange UM, or during the process of transferring mailboxes to a hosted Exchange (Online).

Basically, the HostedVoicemail in SFB/Lync Server is a reflection of the msExchUCVoiceMailSettings attribute in Exchange (On-prem or Online).

Now question comes how can we resolve this issue?

There are couple of ways to resolve Voicemail issues.

  1. Option1: Move the all affected On-prem user mailbox back Exchange online (Hosted UM), then disable UM while mailbox online and then finally move back user mailbox to Exchange on-premise.

  1. Then, run below command to turn off Hosted Voicemail value and policy,
    Set-CsUser -Identity "Balu Ilag" -HostedVoiceMail $Null
    Grant-CsHostedVoicemailPolicy -Identity “Balu Ilag” -PolicyName $Null
  2. Above command let should change hostedvoicemail and policy to Null and voicemail issue must get resolves.
  3. But moving user mailbox to Exchange online and then back to Exchange On-prem is not good option because moving several GB mailboxes to Exchange Online takes long time. So, moving mailbox back and forth are not good option especially when you are dealing with large size mailboxes.

  1. Option2: You can open ticket with Microsoft, and their UM Operations team can manually edit Exchange online msExchUCVoiceMailSettings attribute to False/Null, for users on your tenant that experience VoiceMail failure. And later this attribute will sync to on-premise Exchange attribute. Then finally you can run below command to change HostedVoiceMail value to False/Null.
    Set-CsUser -Identity "Balu Ilag" -HostedVoiceMail $Null
    This will resolve your voicemail failure issue.
    Sometime what happens is even though Exchange online UM attribute (msExchUCVoiceMailSettings) set $Null in Azure AD but HostedVoiceMail attribute in SFB/Lync Server automatically getting changed from False/Null to True, as soon as DirSync runs.
    This exactly was happening in customer environment. In SFB/Lync Server manually setting HostedVoiceMail values is automatically getting changed from False/Null to True, as soon as DirSync runs.
    You resolve this by following below steps:
    The attribute msExchUCVoiceMailSettings in Exchange Online (where the mailboxes had previously been) was set to Null and Dirsync is writing that back to On-Premise. But still HostedVoiceMail value get reset to True, so looks like there is some corrupted meta information on our local Azure AD Connector server.
    You can simply cleare connector space on dirsync server and performed a new initial sync.
    Perform below steps in order to clear connector space:

  1. First disable the sync cycle temporarily.  Login to DirSync server > you must have ADSyncAdmin local group permission > open Windows PowerShell and run below command:
    Set-ADSyncScheduler -SyncCycleEnabled $false
  2. Open “miisclient.exe” tool and go to the Connectors tab > Right click on each Connector and choose “Delete…” > On the pop up window, ensure we have selected “Delete connector space only”.  Do this for all Connectors. (This process takes while).
  3. Once this is done, initial a full/initial sync by running below command:
    Start-ADSyncSyncCycle -PolicyType initial
    Note: Initial sync cycle takes log time because it will sync each object.
  4. When the initial sync has completed, you must re-enable the sync cycle schedule:
    Set-ADSyncScheduler -SyncCycleEnabled $true
  5. Now time to set HostedVoiceMail attribute value to $Null for all affected users account by running below command.
    Set-CsUser -Identity "Balu Ilag" -HostedVoiceMail $Null

This resolve voicemail issue and HostedVoiceMail attribute value did not change even after dirsync runs.

Important points:

  1. Disable Voicemail, before migrating user mailbox from On-premise exchange to Exchange Online.
  2. Disable Voicemail before migrating user mailbox from Exchange Online to exchange on-premise.
    Thank you.


Popular posts from this blog

Outlook Add-in for Skype meeting getting disable after restarting Outlook.

Issue: Outlook Add-in for Lync meeting getting disable after restarting Outlook.
Problem Statement: Outlook Add-ins gets install automatically when Office 2013 installs (Lync and Skype for Business clients are part of Office package). Add-ins name is Lync Meeting Scheduling Outlook Addin or Skype meeting Add-in for Microsoft Office 2013. Sometime if other add-ins conflict with Outlook add-ins then outlook add-in keep getting disabled. And user has to enable it manually after Outlook restarts. 
Resolution: By default Lync Meeting Scheduling Outlook Addin or Skype Meeting Add-in for Microsoft Office 2013 installs wit load behavior "Load at Startup". However due to some conflict users Lync or Skype add-ins load behavior get changed to loaded instead of "Load at Startup" had to re-enable Lync Meeting Add-In in each time Outlook 2013 was started as it was not set to "Load at Startup". Look at the below screenshot. Now question is how we can change load behavior …

Unable to share desktop in Skype for Business?

Unable to share desktop in Skype for Business?
You can show your entire desktop or just a program to everyone in a Skype for Business Meeting, call, or instant messaging (IM) conversation. However sometime this feature does not work and give different errors.  Error message: ·Cannot start Desktop/Application Sharing due to network issues. ·An error occurred during the screen presentation. Resolution: There are multiple thing which may affect application/desktop sharing. 1.Make sure application / desktop sharing enabled on Skype for Business / Lync Server. SfB /Lync Control Panel > Conferencing > Conferencing policy > select Global or create new policy and set enable ‘Enable application and desktop sharing’. Refer below image. 2.Make sure your Skype for Business (Lync) client is updated with latest cumulative updates. Download latest update Skype (Lync) client. 3.Update your Video and Display drivers. a.Go to Start > Control panel. b.Search for Device Manager, and then open it. c.Find V…

Unable to login to Skype for Business client?

Unable to login to Skype for Business client? In order to sign-in on Skype (Lync) you must have login credential provided to you from your organization. ·Sign-in address: ·User name: orgname\bilag ·Password: ************
Note: is my SIP domain name. Here are the most common mistake people make while sign-in on Skype for Business (Lync).
1.If you have login credential however still unable to sign-in then make sure you are putting proper login credential. Below error shows when you are wrong entering your sign-in address:
2.If you are writing correct Sign-in address however getting DNS error then contact administrator/ Support team there may be a DNS resolution or configuration issue. Administrator need to verify the SfB (Lync) AutoDiscover DNS records. 3.Sometime users password may expired/ lockout: Make sure that you password is not expire and lockout. If yes then call to helpdesk and reset your password / unlock. 4.Make user to have updated Skype for Business cli…