03-13-2014 01:08 PM - edited 03-19-2019 08:00 AM
Hi everyone,
I am integrating Cisco Unity 8.6 with Microsoft Office 365 and I am getting a strange IPv6 issue that is preventing the system from accessing the mailbox in the could.
All the instructions were followed, and the hosted exchange server was configured as "outlook.office365.com"
When I go to test a user with UM setup for this integration, the Unity server tries to connect to the hosted exchange server using it's IPv6 address: 2a01:111:f400:840::2:
Here's the test result:
Some possible reasons for 503: Server busy. Service offline. Attempting access using HTTPS when HTTP is required.
HTTP status=[503 Service Unavailable] Diagnostic=[Couldn't connect to server -- Failed to connect to 2a01:111:f400:840::2: Network is unreachable]
I looked it up and 2a01:111:f400:840::2: is indeed outlook.office365.com.
My Unity server is NOT setup for IPv6. When I test from CLI, IPv4 DNS resolution is working:
admin:utils network ping outlook.office365.com
PING outlook-namnortheast.office365.com (132.245.4.130) 56(84) bytes of data.
Any ideas on how to stop it from getting an IPv6 address?
03-13-2014 01:51 PM
Known issue...
please see:
https://supportforums.cisco.com/discussion/11901446/cuc-upgrade-862es4422900-44-86224092-1-failing
Microsoft dns is replying with ipv6 first..
either use ip addresses or upgrade to 9.x unity connection.
03-13-2014 01:58 PM
Thank you for your reply. When I do a lookup, I see the IPv6 addresses first:
> outlook.office365.com
Server: [10.7.7.240]
Address: 10.7.7.240
Non-authoritative answer:
Name: outlook-namnortheast.office365.com
Addresses: 2a01:111:f400:854::9
2a01:111:f400:854::12
2a01:111:f400:878::6
2a01:111:f400:878::9
2a01:111:f400:88c::9
2a01:111:f400:16::2
2a01:111:f400:16::12
2a01:111:f400:2a::9
2a01:111:f400:840::2
2a01:111:f400:840::9
132.245.8.9
132.245.8.12
132.245.8.166
132.245.8.169
132.245.9.233
132.245.13.217
132.245.3.210
132.245.3.220
132.245.4.130
132.245.4.137
Aliases: outlook.office365.com
outlook.office365.com.glbdns.microsoft.com
If I set the server as one of the IPs listed above, I get the following error from CUC test:
Diagnostic=[SSL connect error -- Unknown SSL protocol error in connection to 132.245.8.9:443 ] Verb=[POST] url=[https://132.245.8.9/EWS/Exchange.ASMX]
09-15-2014 07:06 PM
Were you able to resolve the issue? I am setting up a connection to a hosted Exchange environment and I am getting:
"Diagnostic=[SSL connect error -- Unknown SSL protocol error in connection to x.x.x.x:443"
I have verified the URL and login.
thanks
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: