Re-posted here at the suggestion of a moderator in the Exchange Server 2013 - Outlook, OWA, POP, and IMAP Clients forum.
I've recently upgraded an Exchange environment from 2007 to 2013 SP1. A lingering issue has been that the play on phone functionality doesn't work from Outlook 2010 or 2013 clients. When attempting to use this function, a message indicating "The
Microsoft Exchange Unified Messaging service cannot be contacted to play messages on your phone. Try again later. If this problem continues, contact your Exchange administrator or support organization" is displayed. Additionally, the"Manage Voice Mail" button does not appear under the File menu in either of these two clients. Using Play on Phone from OWA, however, works fine, as does managing voice mail from within OWA.
I've tried manipulating the authentication methods used by the EWS, ECP and OWA virtual directories as well as resetting/recreating them and trying different combinations. I've confirmed the Microsort Exchange Add-in for Outlook is enabled. I tried
manipulating the authentication methods used by the MAPI virtual directory. All this to no avail. I scoured the web trying to figure out how
Play on Phone works. Late last night (rather early this morning), after reading the linked article for the 10th or 20th time (in spite of the fact that I couldn't find any of the attributes referenced in ADSIEdit), I latched onto the phrase "When
the User clicks the Play on Phone Icon on his Voicemail
form
Outlook a RPC over HTTPS request is
send to the Exchange CAS" and decided to see what the effect of forcing a RPC over HTTPS connection between client and server would be. Lo and behold, a registry key at HKEY_CURRENT_USER\Software\Microsoft\Exchange\"MapiHttpDisabled"=dword:00000001 and
a (forced) autodiscover later and Play on Phone is functional.
This is on Exchange 2013 SP1 CU10, with Outlook 2010 SP2 (14.0.7153.5000) and Outlook 2013 SP1 (Outlook.exe version
15.0.4753.1002).
So - is it possible to use Mapi over HTTP and retain the Play on Phone functionality in Outlook 2010 or 2013? I hope so, because it looks like forcing RPC over HTTP isn't going to be an option in Outlook 2016.
Thanks,
Stan
Exchange Server 2013 - Outlook, OWA, POP, and IMAP Clients
Exchange Server 2013 - Outlook, OWA, POP, and IMAP Clients
Exchange Server 2013 - Outlook, OWA, POP, and IMAP Clients
Exchange Server 2013 - Outlook, OWA, POP, and IMAP Clients
Exchange Server 2013 - Outlook, OWA, POP, and IMAP Clients