Tuesday, February 23, 2016

Cisco Unity Connection and Office 365 Unified Messaging Integration

Helped a cohort out troubleshooting a new Unity Connection 11 and Office 365 Unified Messaging integration today.  A couple quick notes to help you out:
  • It's recommended to use Search for Hosted Exchange Servers.   
  • The Active Directory DNS Domain Name has been outlook .office365.com at the last few sites I've dealt with or deployed.
  • The username to access Exchange must be in the username@domain.com format.
  • As usual, Unity Connection errors can be misleading.  Here we were being returned a "Searching the network Failed to locate a Domain Controller via DNS." error.  Despite looking to be a network access or name resolution problem, it's actually a symptom of a bad password on the Exchange access account. 
Good job, Cisco.


8 comments:

  1. Thank you so much for this, I spent an hour messing with DNS and restarting services. What an awful error message

    ReplyDelete
  2. Thank you, you saved me a lot of troubleshooting and support calls.

    ReplyDelete
  3. Helped me as well - Thanks!

    ReplyDelete
  4. Thanks! This post was a HUGE HELP and now I'm going to take a deep breath and have some more coffee :-)

    ReplyDelete
  5. This comment has been removed by a blog administrator.

    ReplyDelete
  6. Hey Guys, after re-imputing the password, and running the test, did you still get the error message?

    ReplyDelete
  7. Web Maxtor: Cisco Unity Connection And Office 365 Unified Messaging Integration >>>>> Download Now

    >>>>> Download Full

    Web Maxtor: Cisco Unity Connection And Office 365 Unified Messaging Integration >>>>> Download LINK

    >>>>> Download Now

    Web Maxtor: Cisco Unity Connection And Office 365 Unified Messaging Integration >>>>> Download Full

    >>>>> Download LINK

    ReplyDelete