×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

Single Inbox on Unity Connection 8.5 and Exchange 2003 SP2

Answered Question
May 25th, 2012
User Badges:

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

Correct Answer by Michael Gross about 5 years 2 months ago

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

TTS uses IMAP.


Mike

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (3 ratings)
Loading.
Aaron Harrison Fri, 05/25/2012 - 04:46
User Badges:
  • Super Bronze, 10000 points or more
  • Community Spotlight Award,

    Member's Choice, May 2015

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

Rob Huffman Fri, 05/25/2012 - 06:02
User Badges:
  • Super Red, 40000 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 IP Telephony, Unified Communications

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

ryabutler Tue, 05/29/2012 - 04:50
User Badges:

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

mgower Tue, 05/29/2012 - 06:01
User Badges:

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

Correct Answer
Michael Gross Tue, 05/29/2012 - 12:35
User Badges:

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

TTS uses IMAP.


Mike

ryabutler Tue, 05/29/2012 - 16:15
User Badges:

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


Thank you!


-rya

Imthiyas Khan K I Wed, 01/23/2013 - 20:22
User Badges:
  • Bronze, 100 points or more

Try


web-Based Authentication Mode     : NTLM

web-Based Protocol                       : HTTP


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

Actions

This Discussion

Related Content