How To Change Voicemail On Mitel 5312 Ip Phone

Home
Cloud
Microsoft Office 365

We had a local exchange and the voicemail to email worked fine, now the voicemail is no longer forwarding to email. Our Mitel (Conexus) tech said the .wav file might be blocked on the office 365 side, but I have no clue where to find it, I am new to this system, and I have admin credentials, and I am the lone person working on this project. Can someone help me resolve the vmail to emali ???

thank you all in advance...

13 Replies

lahimakonem

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

Jun 9, 2017 at 21:10 UTC

I hope this helps - We use a Mitel 5000 system, but I think the admin is the same:

In the Session Manager, navigate to the System>E-Mail Gateway

Now set the proper settings for your email setup.

Ensure you firewall has a port open for your email from the Mitel system IP - Make sure your port and smtp settings are correct.

Make sure that the System>IPSettings is also set coreectly for your new network.

Once set, you will need to reboot the Mitel system and all should work fine.

From pchiodo on this thread

https://community.spiceworks.com/topic/245337-mitel-system-with-forward-as-email-issues

Did you change the smtp settings or just hoped it worked?
Have to go into the db programming and change smtp settings. Might have to play with ports 25, 587, and 465. 365 will require authentication to relay mail.
Can't just set an ip in exchange to allow relay.

Update... Let me start by saying thanks... Our Vmail to email is still not working.. the relay server is setup correctly, the IP has been updated in our MiVoice Business (Mitel), of course the IP address was the first think updated. Here is the message that I am receiving in the log CSMTPClientMsg::ProcessResult - Failed sending Voice Mail to Email: From Vpim: phonenumber@mailserverIP To Mailbox: extension To Domain:Name@company.edu

CSMTPClientMsg::ProcessResult - Look into SOCKET error number <786434> <0> bytes transferred

The IIS relay is set to connect with 365 using a username and password and not just open relaying to the smart host by name? Kinda looks like a rights issue.

I think an answer was found by configuring IMAP for office 365.. I will let you know my outcome.

It is not a rights issue, but thanks for the input.

We are having our Linux guy look into our SMTP relay.. it may be as simple as that... (fingers crossed)

Did this ever get resolved?

No it didn't get resolved t8rl33t ... We have decided to leave the company that we are currently using for our phone system, if we are paying for support, and they are not supporting our needs, we are moving on...

I don't know how to close this out

I was having the same issue with our 3300 using embedded voicemail, just as long as you have the public IP office 365 sees the relay request coming from specified in the exchange connector use the IP from your O365 relay server not the FQDN for your email server under system properties>system options>email server on your 3300. Worked like a charm for me, I tried using the FQDN of our o365 relay servers and other names of servers in that email server field on the 3300 but they all failed, when I put the IP in works like intended. Hope this helps...

You're doing your employer and yourself a disservice. Check these guys out https://www.dialpad.com/integrations/office-365

This topic has been locked by an administrator and is no longer open for commenting.

To continue this discussion, please ask a new question.