Office 365 Hybrid Exchange 2013 with Cisco Unity Connection 9.1.2 Single Inbox
Hello,
I have a fully functional Hybrid setup between my on-premise Exchange 2013 and my Office 365 exchange Online tenant. I can migrate mailboxes without issue.
Single Inbox works for my on-premise mailboxes. If I take a mailbox that is on-premise, which has SIB functionality working, as soon as I migrate it, SIB no longer works. We do not use Viewmail, and we are not using Text to Speech.
I have followed the guidance here: Configuring Cisco Unity Connection 9.x and Microsoft Office 365 for Unified Messaging
and here: Cisco Unity Connection with Office 365 (Hybrid)
and here: O365 Integration with Unity Connection
I have tried contoso.onmicrosoft.com, contoso.mail.onmicrosoft.c
If I choose the search option, as the Cisco documentation recommends, all of them fail.
If I choose to specify the server, the only one that works is outlook.office365.com.
When I go to test an actual user that has been migrated, and was working prior to being migrated, and the messaging service has been updated on the user's inbox in Unity for O365, it fails, as though it is an invalid username or password. (401, I believe).
I am pulling my hair out - Unity Connection is the only thing standing in my way of finally migrating 1,000 mailboxes to O365.
Any advice would be very much appreciated.
Thanks,
Jonathan
I have a fully functional Hybrid setup between my on-premise Exchange 2013 and my Office 365 exchange Online tenant. I can migrate mailboxes without issue.
Single Inbox works for my on-premise mailboxes. If I take a mailbox that is on-premise, which has SIB functionality working, as soon as I migrate it, SIB no longer works. We do not use Viewmail, and we are not using Text to Speech.
I have followed the guidance here: Configuring Cisco Unity Connection 9.x and Microsoft Office 365 for Unified Messaging
and here: Cisco Unity Connection with Office 365 (Hybrid)
and here: O365 Integration with Unity Connection
I have tried contoso.onmicrosoft.com, contoso.mail.onmicrosoft.c
If I choose the search option, as the Cisco documentation recommends, all of them fail.
If I choose to specify the server, the only one that works is outlook.office365.com.
When I go to test an actual user that has been migrated, and was working prior to being migrated, and the messaging service has been updated on the user's inbox in Unity for O365, it fails, as though it is an invalid username or password. (401, I believe).
I am pulling my hair out - Unity Connection is the only thing standing in my way of finally migrating 1,000 mailboxes to O365.
Any advice would be very much appreciated.
Thanks,
Jonathan
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
So the issue might be with the DNS or with the logon credentials! I wonder in the case of migrated user do you setup Cisco unity to connect to the user's mailbox with the local AD or O365 credentials ? does Cisco unity uses Email and password to login or uses the UPN ?
Try testing your login credentials on testconnectivity.microsoft
Try testing your login credentials on testconnectivity.microsoft
ASKER
Thanks again.
You setup two services in Cisco Unity when you have a hybrid setup with Exhange on-premise and O365:
DNS works on Unity, as we can resolve outlook.office365.com, however we cannot resolve the other two, even though they are valid and were setup by Microsoft/O365....and are what is recommended to be used in the Cisco documentation.
The RCA (testconnectivity.microsof
In theory we should be using the UPN for login from Unity Connection, however the format I have to use in my Android to connect with ActiveSync is as follows:
contoso.com\username@conto
So I am wondering if we need to use that format in Unity Connection as well.
Nothing like good old Microsoft and Cisco to make things difficult.
Thanks,
Jonathan
You setup two services in Cisco Unity when you have a hybrid setup with Exhange on-premise and O365:
One for on-premise...along with an on-premise AD account that has the impersonate permission.
One for the O365 tenant......along with a tenant account that has the impersonate permission.
DNS works on Unity, as we can resolve outlook.office365.com, however we cannot resolve the other two, even though they are valid and were setup by Microsoft/O365....and are what is recommended to be used in the Cisco documentation.
The RCA (testconnectivity.microsof
In theory we should be using the UPN for login from Unity Connection, however the format I have to use in my Android to connect with ActiveSync is as follows:
contoso.com\username@conto
So I am wondering if we need to use that format in Unity Connection as well.
Nothing like good old Microsoft and Cisco to make things difficult.
Thanks,
Jonathan
Indeed. hope this goes well for you.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Figured it out on my own. points awarded for effort
ASKER
We are using the Windows Azure Active Directory Sync Tool, but I do not believe that has any bearing on this issue. Allow me to explain why.
We also do not have UM enabled on the Exchange/O365 side....but again, that has no bearing on this issue.
Unity Connection Single Inbox does not modify the AD/Exvhange user in any way.
The way Single Inbox works is that you create a user in AD (which I have - one in the on-premise environment, and one in the O365 tenant) and you assign it the impersonate permission. When a voicemail is left for a user, Unity Connection connects into the Exchange mailbox using the AD account specifically created for this purpose, and deposits the message in the form of an email with the actual voicemail being a wav attachment to the email. It is not sent via smtp, which is why people troubleshooting delivery get confused when message trace yields no results.
Voicemail delivery works just fine for on-premise, but Unity Connection can't seem to connect and/or authenticate to my O365 tenant even though I know the credentials for the tenant account are correct and the account has the proper permissions.
We don't need to check error logs on the Cisco side, because the error presents itself on the screen every time we test within the Unity Connection GUI.
Within Unity Connection, using the onmicrosoft.com domains, we get a DNS error when we configure the service and can't even test the user. With the office365.com domain, the service test passes, however we get a 401 login error when we test the user.
I think I know what the issue might be, but it is only a hunch - the way the username is formatted. Unfortunately I won't be able to test my theory until Monday when I can get one of my Unity admins back on the line.
In the mean time, please keep the ideas coming.
Thanks,
Jonathan