Voicemail to Email Issue

[UnknownKing]

Hello Everyone,

   I am having a bit of an issue with the voicemail to email flowing. A quick backstory. We recently as of 2 months ago switched from Exchange 2010 to Office 365. The settings in our Mitel 5000 did not change as the voicemail was still flowing over to email just fine with the old settings. As of last weekend our independent contractor removed some of his equipment and now out voicemail isn't going to email. I can set it back to directly to the phone but not email. I have tried with the old settings as well as changing the SMTP settings to Office 365 but I am still have no luck at all. I have tried the steps in many of the post that are here and none of them has worked for me yet. Any assistant at all would be greatly appreciated.

[Tech Electronics]

UnknowningKing,

Try port 587 instead of port 25.

Thanks,

TE

[UnknownKing]

Thank you for the reply.

I have previously tried port 587 and didn't have much luck with it so I was testing port 25 which didn't work either.

[Tech Electronics]

UnknownKing,

With port 25 you will need to go to the root MX as the smtp.office365.com usually doesn't work well with it. I know there are several instances where I explained how to determine your root MX for Office 365 so you just need to do a search for it.

Thanks,

TE

[PhoneSlayer]

A few months ago I had a slew of customers with the same problem. I was able to find a solution that fixed the issue for all of them. See below:

When setting up email integration with Office 365 there are a few considerations:

1) - Mitel recommends Mitel 5000 release 6.2 or later software for integration with O365.

2) - server address must be entered in the following format - <domain>.mail.protection.outlook.com. So if the company's domain is xyzinc.com, the address would be xyzinc-com.mail.protection.outlook.com. Take note that the domain uses a hyphen in place of the dot.

3) - port should be set to 25

4) - username and password seem to be required by the Mitel server. Despite what the server admin may assert regarding authentication it is best to enter an account and password. Ask the server admin to provide account/password. Rel 6.2 and higher will generate INVALID APPLICATION alarm A028 when account info is missing from the email gateway form.

5) - a connector is required in the O365 environment to enable mail relay. The following article seems to describe the setup process quite well  https://technet.microsoft.com/en-us/library/dn751020(v=exchg.150).aspx

[acejavelin]

4) - username and password seem to be required by the Mitel server. Despite what the server admin may assert regarding authentication it is best to enter an account and password. Ask the server admin to provide account/password. Rel 6.2 and higher will generate INVALID APPLICATION alarm A028 when account info is missing from the email gateway form.

Really? We have several 250's with 6.2 and SMTP email to servers that require no authentication, and the only think in the Email Gateway form is IP address and email address, no account name or password, and it works fine with no alarms or issues. (Not related to the OP's Office365 issue, that is covered quite well already... for the record, I hate dealing wotj O365 email integration issues when it doesn't "just work")

[Tech Electronics]

PhoneSlayer,

Don't take this the wrong way, but where are you getting your information from?

With the solution you provided point 1 wouldn't whether it was for O365 or any other server as it is just basic SMTP. This solution has worked in the MiVO-250 for many versions. If you are referring to Enhanced Integration with O365 then it is always best to try and get on the latest version.

Steps 2 & 3 are basically the same thing I already posted which is solid information for anyone having these sorts of issues with O365.

Step 4 however I have never heard of as an issue. Where did you run into this at?

Step 5 Nice information to have.

Thanks,

TE

[jzs_phone]

We recently ran into the same issue when we upgraded to V6.2 but only after we also upgraded our Exchange to 2016.  The issue was resolved by adding Administrator Email Address;Email Real Name; Email Username (domain\username); Gateway Password. All of those fields were from the same email/user.

[Tech Electronics]

jzs_phone,

Are you stating that it was working with nothing in those fields? Was it setup for Enhanced Integration or just SMTP?

Thanks,

TE