ā07-24-2024 05:17 AM
I've been working all week to get unified messaging working again. We had is setup with our on-premise exchange server 2013. We migrated to Office365 and I created a new Unified Messaging service and followed the documentation to set it up. I created an application, created a new user in the cloud and gave that user application impersonation role and assigned that user to the application. Following the guide I applied appropriate API permissions. I can't see that I missed a step, but I'm still getting errors. I followed troubleshooting steps and can see SSL communication between Unity Connection and Microsoft. It ends with the Unity Connection server sending an Encrypted Alert (21). To the best of my research, that's just a simple error message that is of course encrypted. I have wiresharked and looked at logs and cannot determine the issue. Attached is a screenshot of the test and a snippet of the logs i've pulled.
I am really starting to think there is a bug in 12.5 (SU6) or maybe it just isn't supported.
14:38:38.356 |18255,,,CuESD,0,Thread=http-nio-81-exec-8 autodiscover testEmailAddress=false extsvcObjectId= clientid=7aa01437-xxxx-xxxx-xxxx-c00e7exxxx45
14:38:38.361 |18255,,,CsExMbxLocator,10,[CsExMbxLocator/CCsDbHelper.cpp:403]: Error access token is not found in database for uid: 7aa01437-xxxx-xxxx-xxxx-c00e7exxxx45
14:38:38.402 |18255,,,CsExMbxLocator,10,[CsExMbxLocator/CCsDNSResolver.cpp:190] failed to get dns results for _ldap._tcp.mygeatn.onmicrosoft.com._sites.dc._msdcs.outlook.office365.com question type 33
14:38:38.402 |18255,,,CsExMbxLocator,11,[CsExMbxLocator/CsExMbxLocator.cpp:458]: DNS query for: _ldap._tcp.mygeatn.onmicrosoft.com._sites.dc._msdcs.outlook.office365.com didn't return results
14:38:38.551 |18255,,,CsExMbxLocator,10,[CsExMbxLocator/CsExMbxLocator.cpp:1420]: HTTP request failed with error: 80004005, HTTP status code: 401, for Autodiscovery URL: https://outlook.office365.com/autodiscover/autodiscover.xml, verb: GET, query:
14:38:38.551 |18255,,,CsExMbxLocator,10,[CsExMbxLocator/CsExMbxLocator.cpp:1476]: HTTP request failed with error: Bad response from server, HTTP code returned: 401, HTTP status code: 401, for Autodiscovery URL: https://outlook.office365.com/autodiscover/autodiscover.xml, verb: GET, query:
14:38:38.577 |18255,,,CsExMbxLocator,10,[CsExMbxLocator/CsExMbxLocator.cpp:1420]: HTTP request failed with error: 80004005, HTTP status code: 0, for Autodiscovery URL: https://autodiscover.outlook.office365.com/autodiscover/autodiscover.xml, verb: GET, query:
14:38:38.577 |18255,,,CsExMbxLocator,10,[CsExMbxLocator/CsExMbxLocator.cpp:1476]: HTTP request failed with error: Couldn't resolve host name -- Could not resolve: autodiscover.outlook.office365.com (Domain name not found), HTTP status code: 0, for Autodiscovery URL: https://autodiscover.outlook.office365.com/autodiscover/autodiscover.xml, verb: GET, query:
14:38:38.752 |18255,,,CsExMbxLocator,10,[CsExMbxLocator/CsExMbxLocator.cpp:1420]: HTTP request failed with error: 80004005, HTTP status code: 401, for Autodiscovery URL: https://autodiscover-s.outlook.com/autodiscover/autodiscover.xml, verb: GET, query:
14:38:38.753 |18255,,,CsExMbxLocator,10,[CsExMbxLocator/CsExMbxLocator.cpp:1476]: HTTP request failed with error: Bad response from server, HTTP code returned: 401, HTTP status code: 401, for Autodiscovery URL: https://autodiscover-s.outlook.com/autodiscover/autodiscover.xml, verb: GET, query:
14:38:38.754 |18255,,,CsExMbxLocator,10,[CsExMbxLocator/CsExMbxLocator.cpp:1420]: HTTP request failed with error: 80004005, HTTP status code: 0, for Autodiscovery URL: http://autodiscover.outlook.office365.com/autodiscover/autodiscover.xml, verb: GET, query:
14:38:38.754 |18255,,,CsExMbxLocator,10,[CsExMbxLocator/CsExMbxLocator.cpp:1476]: HTTP request failed with error: Couldn't resolve host name -- Could not resolve: autodiscover.outlook.office365.com (Domain name not found), HTTP status code: 0, for Autodiscovery URL: http://autodiscover.outlook.office365.com/autodiscover/autodiscover.xml, verb: GET, query:
14:38:38.793 |18255,,,CsExMbxLocator,10,[CsExMbxLocator/CCsDNSResolver.cpp:190] failed to get dns results for _autodiscover._tcp.outlook.office365.com question type 33
14:38:38.793 |18255,,,CsExMbxLocator,11,[CsExMbxLocator/CsExMbxLocator.cpp:741]: DNS query for: _autodiscover._tcp.outlook.office365.com didn't return results
ā07-24-2024 01:15 PM
yes, one big difference is that your application is searching autodiscover.svc which actually returns a response when using my browsers. https://outlook.office365.com/autodiscover/autodiscover.svc
My application is pointing to https://outlook.office365.com/autodiscover/autodiscover.xml
This returns an error message in the browser. Which leads me back to my original concern that 15.5 SU6 may not be supported.
ā07-24-2024 11:18 PM
I think you meant 12.5 (SU6) as there are no 15.5 version.
ā07-25-2024 12:04 AM
According to the current documentation for how to setup a messaging service with O365 it should be supported. https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/12x/unified_messaging/b_12xcucumgx/b_12xcucumgx_chapter_01.html
That said I would recommend you to upgrade your CUC to either 14SU3 or later as that changes the integration with Exchange O365 to not rely on the old outdated EWS service and that the 12.5 version is soon to be EOL.
The changes in the integration are outlined in these documents.
ā07-25-2024 05:08 AM
Yes, I did mean 12.5 I my 5's were getting jumbled in my head. My actual version is 12.5(1)SU5 based on the version 12.5.1.15900 that is in the about section of unity.
Thank you for this documentation. I am working with my Cisco Partner on an upgrade path to 14....sooooo....many....projects!
ā07-25-2024 05:56 AM
Likely already known, but if not youāre needing to get to version 15 pretty soon as the underlying operating system in 14 and earlier versions is going EOS pretty soon. In the meantime you might want to consider upgrading to the latest SU release of 12.5, if Iām not wrong itās now SU8 or maybe even SU9. Given that the upgrade of CUC is pretty quick and straightforward it shouldnāt be too much effort, at least if youāre not using any additional locales. If you do the upgrade is a little more complex, but still on the easy side compared to other CVOS systems, like for example CUCM or CUPS.
ā07-25-2024 06:05 AM
Actually, I thought 14 got away from CentOS, i haven't researched it yet as I was trying to get through some other upgrade projects. That' explains why our Cisco Partner mentioned eventually getting to 15. I will be doing CUCM, CUC, UCCX, and CUPS (maybe). Not looking forward to it.
That document you mentioned is the guide I used. I know it doesn't specifically say 12.5(1) SU5 is not supported, but I wonder if changes in OAuth2 in Exchange have rendered older versions not usable. I am going to open a TAC case i believe, of course they'll likely ask me to upgrade.
ā07-25-2024 11:06 AM
My comment on that the document specifies that it should be supported was based out of that you wrote in the specific response that youāre using 12.5 SU6. It may be so that 12.5 SU5 isnāt supported anymore as you yourself suspect. As I mentioned before itās advisable that you get the system updated to the latest SU release instead of spending time on continue trying to get it to work with the SU5 release.
ā07-25-2024 04:05 PM
ā07-24-2024 08:33 AM
Not related to the name lookup, have you downloaded the certificates for O365 and uploaded them to the Tomcat trust store on your CUC system?
ā07-24-2024 10:07 AM
Yes, the link given in the documentation takes you to a login prompt and i was now able to get the root CA there. I ended up going to the outlook web application URL and downloaded the certificate and uploaded that as a Tomcat Trust cert to CUC. It was a digicert root CA. After doing so i can check the validate box and I don't get immediate RST from the server so i assume i have the right cert.
ā07-24-2024 01:03 PM
Since almost everything known has been checked and verified, could you please review the Tomcat logs from the interaction between the CUC and Office365/Azure? Kindly share the logs here or contact TAC for further assistance.
Regards
ā07-24-2024 01:37 PM
I've been constantly reviewing the Tomcat logs, in fact that's a snippet of what I posted originally. I was hesitant to post the whole thing because it has identifiers and this is a public forum. I may have to get with TAC. After seeing a successful test pointing to autodiscover.svc and mine is pointing to autodiscover.xml, i'm questioning if 15.5 SU5 is supported.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide