Quantcast
Channel: Exchange Server 2013 - Mobility and ActiveSync forum
Viewing all articles
Browse latest Browse all 1206

.wav file will not play on iOS / active sync (opens as MIME type)

$
0
0

iOS 7 not playing .wav file from email

Asked by:MitchS47

our landlord phone system sends voice mails to email via a wav file attachment.  we were able to listen to the wav file in all places, i.e. Outlook, OWA, and iPhone/iPad before moving email from SBS 2008 (exchange 2007) to Office 365.

other change at about same time iOS 7 upgrade.

the current chain goes like this Phone system send to the landlord Exchange 2010 server > the exchange 2010 sends to our Office 365 (exchange 2013) > emails to devices.

Now, we can listen to the wav file on Outlook, OWA, and Android (galaxy 2) but cannot listen on the iPhone/iPad.  it shows as a MIME attachment.

the strange thing is that if your forward the email from Outlook to yourself the wav file will play on the iPhone/iPad.

any searches regarding the MIME attachment generally says that you do not have an app for the file type but of course there is one and works when forwarded to yourself.

I am thinking it lies with Exchange or office 365 but have been through both the exchange 2010 and O365 and can't find anything actionable.

any help would be greatly appreciated.

Asked On

2013-10-11 at 07:04:57ID28264632

Top of Form

Delete QuestionRequest Attention

Bottom of Form

Your Comment

by:MitchS47Posted on 2013-10-11 at 07:42:02ID: 39565778

Exchange 2010 phone system setup clarification.
the phone system, copier/scanner, etc., owned by landlord, send Voicemail and scanned docs to the Contact of the tenant on the Exchange server 2010 server.  The Contact is configured with the external email of the tenant.

NOTE:  this worked before the move to Office 365 and iOS7 and still does on Outlook clients and OWA and Andriod.  


Mitch


Viewing all articles
Browse latest Browse all 1206

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>