cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3609
Views
10
Helpful
10
Replies

Single Inbox on Unity Connection 8.5 and Exchange 2003 SP2

ryabutler
Level 1
Level 1

Hi,

We have Unity Connection 8.5 (with SU2) and Exchange 2003 SP2

We want to setup the Single Inbox feature that works well with Exchange 2007 and 2010, but my customer is running Exchange 2003 SP2.

We met all of the requirements outlined in: http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/requirements/8xcucsysreqs.html#wp459928

I configure a new "Unified Messaging Services" profile for Exchange using Exchange 2003 and enabled for Single Inbox.  When I run "Test" it displays the following errors (other validation is successfully)

The service port for IMAP is not functioning.      

The system failed to connect to the server with a socket connection through port beatles.clubone.com:993. The error is error:0200206F:system library:connect:Connection refused. Refer to the tomcat log file for more details. If you are using secure connection, confirm that SSL is enabled on the server.

Why is it trying to connect using IMAP, that wasn't the case when I used for Exchange 2007 or 2010 when IMAP was not enabled.

Is there something else I'm missing for configuration with Unity Connection to support Single Inbox with Exchange 2003 SP2?

Thank you!

-rya

1 Accepted Solution

Accepted Solutions

Michael Gross
Level 1
Level 1

Try unchecking the box next to "Access Exchange Email by Using Text To Speech (TTS)"

TTS uses IMAP.

Mike

View solution in original post

10 Replies 10

Aaron Harrison
VIP Alumni
VIP Alumni

Hi Rya

From the 8.6.2a SU1 release notes:

 

 Exchange 2007 and Exchange 2003 Are Supported with Single Inbox
Revised February 16, 2011
When Connection and Microsoft Exchange mailbox synchronization (single inbox) was introduced in
the 8.5(1) release, only Exchange Server 2010 was supported. With Connection 8.6(2a) Service
Update 1, you can also use Exchange Server 2007 and Exchange Server 2003.

Regards

Aaron

Aaron Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!

Rob Huffman
Hall of Fame
Hall of Fame

Hi Rya,

I just wanted to add my +5 vote for this great catch by Aaron (nice work "A")

If you are going to upgrade to Unity Connection 8.6

Check out this great doc from Saurabh for the refresh upgrade notes to 8.6.

https://supportforums.cisco.com/community/netpro/collaboration-voice-video/unified-comm-application/blog/2011/08/11/checklist-before-upgrading-to-unity-connection-86

Cheers!

Rob

"Show a little faith, there's magic in the night" - Springsteen

But, here is what's listed as of April 30, 2102 if using Unity Connection 8.5

reference: http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/requirements/8xcucsysreqs.html#wp459928

So it never mentioned anything about requiring 8.6(2c) until this is referenced somewhere else.

Thank you!

-rya

Hi

Ah yes.. there's a similar note in the 8.5 release notes : http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/release/notes/851cucrn.html#wp1006460

Aaron

Aaron Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!

But, is it IMAP that deals with Single Inbox synchronization between Unity Connection and Exchange 2003 SP2 even for Exchange 2007/2010?

That's the error I see and I don't think that should be checking for IMAP because I never needed that for 2007/2010 in the past.

Thank you!

-rya

For Exchange 2003 CUC uses WebDav to perform message synchronization.  With Exchange 2007/2010 it uses Exchange Web Services.  I'm not sure what is causing your errors; I remember that I had some issues with my Web Based Auth Mode settings, so you may want to play around with those.

-Mel

Thanks for the good explanation.

-rya

Michael Gross
Level 1
Level 1

Try unchecking the box next to "Access Exchange Email by Using Text To Speech (TTS)"

TTS uses IMAP.

Mike

That did this to get those IMAP errors to go away.

Thank you!

-rya

Try

web-Based Authentication Mode     : NTLM

web-Based Protocol                       : HTTP

now you can select all the options under "Service Capabilities"