Unity Connection 10.5.2.13900-12 and Exchange 2016 VM to Outlook Not Working

[Cisco54]

Hi all-

I have recently (nearly) completed an on-prem migration from Exchange 2013 to 2016.  All is working as expected EXCEPT when it comes to my Unity Connection server and the voicemail to Outlook/inbox feature.  This is not working.  All SMTP settings have been updated to point to the new 2016 server on Unity, autodiscover settings are correct, receive connector on Exchange is working, etc.  I've created a new management role with ApplicationImpersonation as noted in documentation.  When I shut down my 2013 Exchange server, Unity voicemail to Outlook stops working.  When I fire it back up, that process begins working again.

At this point, I'm thinking it's related to the SU level I am on.  We are running Unity Connection 10.5.2.13900-12.  I believe this is SU3, please correct me if I'm wrong.  Do I have to get this to a specific SU level for the voicemail to Outlook feature to work with Exchange 2016?

Thanks guys!

[Cisco54]

Still hoping for some feedback regarding this issue...  Thanks all.

[Ratheesh Kumar]

Hi there

Yes, 10.5.2.13900-12 is SU3. Can you check this ? and also  try removing the Application Impersonation permission from the previous account, and re-add.

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/10x/requirements/10xcucsysreqs.html#pgfId-579146

Unified Messaging Requirements: Synchronizing Unity Connection and Exchange Mailboxes (Single Inbox)

Revised March, 2018

• Cisco Unity Connection integrated with a supported version of Microsoft Exchange Server

– Exchange Server 2016 with Cumulative Update 8 and earlier

– Exchange Server 2013 with Cumulative Update 19 and earlier

 

Hope this helps!

Cheers
Rath!

***Please rate helpful posts***

[Cisco54]

Thank you for the replies.  I have already reset the application impersonation with no improvement.

I am currently on Exchange 2016 CU9 (not CU8 or earlier as your post explained).  Is CU9 not supported?

[Cisco54]

I've narrowed it down to what I believe to be an issue with Exchange 2016 in some way.  If my 2013 server is shut down, I get a "503:Server Busy" error when testing through the unity interface.  Changing the Unified Messaging Service Web-Based Protocol to HTTP just gets me a similar error saying it requires HTTPS instead?!  When my 2013 server is up, all tests are successful within Unity and voicemail to inbox flows as it should.  Users test successfully as expected.  Only when my 2013 box is offline do all these issues start.

Here's an excerpt of the error I'm seeing within Unity when testing an individual user (I've altered some names for privacy):

Failed accessing user@mydomain.com on autodiscover.mydomain.com 

Some possible reasons for 503: Server busy. Service offline. Attempting access using HTTPS when HTTP is required.     

HTTP status=[503 Service Unavailable] Diagnostic=[Bad response from server, HTTP code returned: 503] Verb=[POST] url=[https://autodiscover.mydomain.com/EWS/Exchange.ASMX] request=[<?xml version="1.0" encoding="utf-8"?> <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types"> <soap:Header> <t:RequestServerVersion Version="Exchange2007_SP1"/> <t:ExchangeImpersonation> <t:ConnectingSID> <t:PrimarySmtpAddress>user@mydomain.com</t:PrimarySmtpAddress> </t:ConnectingSID> </t:ExchangeImpersonation> </soap:Header> <soap:Body> <GetFolder xmlns="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types"> <FolderShape> <t:BaseShape>Default</t:BaseShape> </FolderShape> <FolderIds> <t:DistinguishedFolderId Id="deleteditems"> <t:Mailbox> <t:EmailAddress>user@mydomain.com</t:EmailAddress> </t:Mailbox> </t:DistinguishedFolderId> </FolderIds> </GetFolder> </soap:Body> </soap:Envelope> ] response=[]

I have the same 3rd party SSL certificate on my 2016 server as on the 2013 server.  The only difference is I have selected SMTP service on the 2016 certificate, whereas, on my 2013 that service is not selected.

[Cisco54 · Accepted solution]

It was the SSL certificate on Exchange 2016.  I removed it, re-imported it, but didn't select the SMTP service.  Everything works correctly now.  Old server down, voicemail to inbox works.

[gudakeshsharma525]

Hey there,

I am facing the same issue please help

HTTP status=[500 Internal Server Error] Diagnostic=[Bad response from server, HTTP code returned: 500] Verb=[POST] url=[https://webmail.company.com/EWS/Exchange.ASMX] request=[<?xml version="1.0" encoding="utf-8"?> <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types"> <soap:Header> <t:RequestServerVersion Version="Exchange2007_SP1"/> <t:ExchangeImpersonation> <t:ConnectingSID> <t:PrimarySmtpAddress>user@company.com</t:PrimarySmtpAddress> </t:ConnectingSID> </t:ExchangeImpersonation> </soap:Header> <soap:Body> <GetFolder xmlns="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types"> <FolderShape> <t:BaseShape>Default</t:BaseShape> </FolderShape> <FolderIds> <t:DistinguishedFolderId Id="deleteditems"> <t:Mailbox> <t:EmailAddress>user@company.com</t:EmailAddress> </t:Mailbox> </t:DistinguishedFolderId> </FolderIds> </GetFolder> </soap:Body> </soap:Envelope> ] response=[<?xml version="1.0" encoding="utf-8"?><s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><s:Body><s:Fault><faultcode xmlns:a="http://schemas.microsoft.com/exchange/services/2006/types">a:ErrorNoRespondingCASInDestinationSite</faultcode><faultstring xml:lang="en-GB">Exchange Web Services are not currently available for this request because none of the Client Access Servers in the destination site could process the request.</faultstring><detail><e:ResponseCode xmlns:e="http://schemas.microsoft.com/exchange/services/2006/errors">ErrorNoRespondingCASInDestinationSite</e:ResponseCode><e:Message xmlns:e="http://schemas.microsoft.com/exchange/services/2006/errors">Exchange Web Services are not currently available for this request because none of the Client Access Servers in the destination site could process the request.</e:Message></detail></s:Fault></s:Body></s:Envelop

There are many certificates on the 2016 server .. one with all the SAN names has IMAP, POP, SMTP assigned to it, other than this cert there are 2 other certs for server.company.local (one with SMTP and other NONE)

I do not want to break anything , kindly suggest.

Thanks in advance.

[DavidNolan1]

We encountered this exact error message while doing our Exchange 2013 to 2019 migration. We had to mail-enable the user on one of the Exchange 2019 mailbox databases, and that seems to have resolved the issue. There is a small footnote in the instructions that indicate this:

Do not create a mailbox for the domain user account. If you create a mailbox for the account, unified messaging does not function properly.

Caution

Some newer Exchange versions need mailbox for domain user account.You need to create a mailbox for domain user account if you face any issue while testing Unified Messaging Service/Account.

[srfndoc]

We had a similar situation where we had migrated all users off of a 2013 DAG to a 2019 DAG and when we retired the 2013 DAG unity stopped working with mostly 503 errors.  Turns out the fix was to add a mailbox to the unity service account as its required when using Exchange 2019 but not documented.  Hopefully this saves someone else from hours of troubleshooting.

[nadeem1nadeem]

Hello,

Have you fixed your issue. I am also facing the same problem.