This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 87%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EFB%3C/text%3E%3C/svg%3E)
i have followed the guidance to setting up Hybrid mode to allow access to Cloud Voicemail for my Skype for Business on-premises users. When trying to call a users voicemail I am getting a fast busy.
Logs are showing:
ms-diagnostics: 1008;reason="Unable to resolve DNS SRV record";source="FE1@mydomain.com";dialplan="Hosted__exap.um.outlook.com__mydomain.onmicrosoft.com";umserver="exap.um.outlook.com";responsecode="504";msexchdomain="mydomain.com";msexchdns-srv-result="NegativeResult";msexchdns-source="InternalCache";msexchsource="sip.mydomain.com";appName="ExumRouting"
Server: ExumRouting/7.0.0.0
What am I missing? I can find no documentation for configuration on the M365 side. Everything i have read says the Skype for Business users are setup automatically for mailbox use.
Anyone out there setup this configuration? Exchange 2016 / Skype for Business 2019
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(169.60000000000002, 28.999999999999996%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKF%3C/text%3E%3C/svg%3E)
It's been a couple of years since I've been involved in a Skype to Teams migration, not to mention a Skype to Cloud Voicemail integration. I've got the exact same "NegativeResult". I'm waiting to hear back from the client, I'm hoping that it's just that the CsOnlineVoicemailUserSettings for the user is that their VoicemailEnabled is set to False for some unknown reason, but easily fixed.
Did you find a resolution or get an answer from MS Support? I have a customer just now moving from Exchange 2016 to Exchange Online, and have the same 1008 error.