Voicemail to email weird issue 8

[rval80]

I received an email from a customer who is having a strange problem with his voicemail to email. Obviously, his voicemails are usually delivered as a wav attachment, however, two time in the last two days, he doesn't get the attachment. What he gets is what appears to be the wav file opened using notepad. Anyone ever experience this?

 

[Okkie26]

Check his windows settings. I think he changed the .wav settings to always open with notepad.

Try to forward the email to another user, then try to open it.

 

[rval80]

One thing I did notice is that in the email, it's saying that it's being sent in MIME format. What does that mean? Is it an issue with email or the Avaya?

 

[Okkie26]

I don't know. Sorry...

 

[rval80]

Here's what he gets in the first part of email before all the garbage starts:

This is a multi-part message in MIME format.

--{f30906a0-9dd6-1049-b6bf-8a1f9f16ad14}
Content-Type: text/plain;
charset=o-8859-1
Content-Transfer-Encoding: quoted-printable

IP Office Voicemail redirected message

--{f30906a0-9dd6-1049-b6bf-8a1f9f16ad14}
Content-Type: audio/wav;
name=SG00104.WAV"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename=SG00104.WAV"

 

[Okkie26]

Maybe the WAV file is to large to email?

 

[dwone555]

We have had multiple customers report the same issue. They all have been experienced the MIME error. At this point I can only assume a Windows Update has caused the issue due to the timing of the error. If I am able to find a resolution quickly I will update this post as well.

 

[jsanbor1]

we are also experiencing this same issue. It started yesterday.

 

[Zandolee]

This sounds like a Microsoft issue, you can try saving the file and changing the extension back to .wav. This should make it playable again.

 

[pmcook]

MIME is how non-ASCII files are sent via email.

 

[pmund]

This problem also started for us this week. It's random... some voicemail to email work properly, some show up as garbled text. There is no attachment when the problem happens (the garble shows in the message body).
No Windows updates on the voicemail server in almost a month. The message doesn't display correctly in webmail either (not a end-user computer issue). We have server 2008 R2, Voicemail Pro 9.0.0.0 build 311. Email is Exchange Online (O365). Ideas?

 

[jsanbor1]

Yep - no attachment. It seems to be random here as well..

Server 2003 R2- also Exchange O365.

Version 9.0.0.0 build 829

 

[CarGoSki]

I think my affected customer has office 365. Does everyone who has this issue have vmpro sent email to O365?
Doesnt seem to be a specific firmware release or server type. Mine is server edition 9.0.8 and has the issue.

 

[CarGoSki]

voicemail traces show that the file name sent is MSGXXXXX.wav but what is received as the filename is SGXXXXX.wav.

I have a case open.

 

[CarGoSki]

Could be?

https://community.office365.com/en-us/f/158/t/413700

 

[djs01]

We are also having the same issue and yes it is related to office 365. Please keep us updated on the ticket progress. Perhaps we should also open up a ticket with Microsoft?

 

[CarGoSki]

confirmed. Microsoft issue. They are working on a patch and deployment.

 

[CarGoSki]

Avaya will make an immediate solution note. I suppose immediate is in the eye of the beholder.

 

[ThePhoneMn]

I have been working on this for two days, I am so relieved to see this thread. I am on 9.1.4 SE using O365.

You guys are the best, thank you.


Been there, done that

 

[TouchToneTommy]

In the meantime, I downloaded UUDeview from here -

http://www.fpx.de/fp/Software/UUDeview/

Save the email with the inline attachment as an .eml file, drag it to the Decode These window (or use the Add dialogue), and press Go to generate the wav file.