Avaya Voicemail to Email Stopped Working

[mjp1201]

Hello,

We are running Avaya IP Office 500 and we noticed recently that our users stopped receiving voicemail emails. I can connect to the voicemail settings using the voicemail pro application and I checked the settings and they look correct. We did go through a on prem exchange decommission and we now have the voicemail settings pointed at our MX record in office 365 but we tested it and voicemail emails were working after we made the change. I have rebooted they system but emails still do not get sent. I have logging turned on for the voicemail pro application and all it says is "unexpected program error: start_lock - calling thread does not own OS_Critical_Section." We aren't sure why it stopped working but any help would be appreciated.

Thanks

 

[icet500]

I think that office 356 does not support TLS lower then v1.2

But you can see that in the smtp logs. The one you posted is not the smtp.

 

[mjp1201]

That's a good theory, i've seen that happen on a bunch of our other servers but it was working at one point. We also have mimecast and i tried pointing it to the mimecast servers and that's not working either. I enabled syslog since i can't get smtp logs working and i'm seeing an error "-04:00 2021 667 1 .ipovmpro | 0 VMP-ALARM|SMTP - Non-Secure Connection to Host "us-smtp-outbound-1.mimecast.com" on port {25} has failed, will not try again for another 900000 ms.|

 

[Nortel4Ever]

mjp1201
You haven't said what software level your IP500 (V2 I hope) and VM Pro are at. icet500 is correct in that older versions of VM Pro do not support TLS that O365 requires. In that case you need to upgrade both your IPO and VM Pro. When connecting to O365 for VM to Email I have had the best success if an O365 account is created specifically for the VM Pro (voicemail@companyname.com) then use port 587 that O365 requires for TLS.
A quick Google search will tell you what settings are required for third-party email senders with O365.