Does VM pro voicemail to email still work? 1

[headcase69]

IPO 9.1
VMPro 9.1.12

Does the VM pro still work with office 365 email servers? Our VM to email stopped working and we haven’t changed any settings?

Does office 365 need settings the VM pro doesn’t have?

 

[aarondyck]

There are a couple different ways to configure Office365. Can you show your configuration?

https://bovaird.ca/

 

[headcase69]

thanks for the reply....

mail domain: smtp.office365.com
mail server: smtp. office365.com
port: 587
sender: email address

check mark server requires authentication

user name: email account
password: email account PW

not sure if this is what your looking for?

thanks again for the reply...

 

[aarondyck]

That should do it.

The sender and username match?

Is your VMPro server Linux- or Windows-based? If it's Windows you can use dbgview to do some SMTP troubleshooting. Either way, turn on the debug logging to get individual SMTP sessions logged. From there you can see how the conversation is proceeding.

Voicemail to e-mail troubleshooting is never a good time. When it works it's great, but when it stops there is absolutely no support from anywhere!

https://bovaird.ca/

 

[headcase69]

not sure what these mean....

this is from the debug log after leaving a message in mailbox 350

AUTH LOGIN authentication was unsuccessful
an unexpected QUIT response was received
an unexpected AUTH response was received
already disconnected from SMTP server, doing nothing
send request failed for 350\MSG00085, error unspecified error (80004005)

 

[aarondyck]

Sounds like a username and password issue.

Since it's O365 you could try logging in with Webmail to validate the credentials.

Make sure the O365 user password is set to never expire.

https://bovaird.ca/

 

[headcase69]

the user and password are correct

I was able to login to the account online

password is set to never expire

the voicemail server is on a Windows 11 PC. not sure if this stared happing after updates were installed? I wasn't paying much attention to it as it has been working for a long time...

 

[aarondyck]

Windows 11 is not a supported platform for Voicemail Pro 9.1.

You probably nailed it with the Windows Update theory.

Migrate to an OS that is actually supported in documentation. If you aren't using MAPI just go with the Linux server. It works remarkably well.

Your settings look good to me.

https://bovaird.ca/

 

[Travis Harper]

The error code 80004005 suggests there is an issue with Office 356.

https://support.mozilla.org/en-US/questions/1288101

 

[headcase69]

so..... is anyone using office 365 for voicemail to email?

 

[Westi]

only on Linux machines so that the TLS 1.2 is actually used which is required by O365 and Avaya has not made adjustments on the Windows versions to actually use it.
Not like TLS 1.2 is not out for a decade

You need a relay server that takes it and sends it out for you using TLS 1.2 otherwise you are I am afraid set up for failure with Windows.

SMTP2go can relay your emails (no I do not get money from them)for a relatively small amount that is less than the headache you have and they still allow even unencrypted SMTP traffic if need be. You just have to make sure that you setup SMTP2go as verified relay for your domain otherwise some providers will reject the emails from there including probably O365
vm to email takes more time than anything else it seems

Joe
FHandw, ACSS, ACIS

"Dew knot truss yore Spell Cheque

 

[Travis Harper]

another option is to use the SMTP server provided by your ISP.

 

[headcase69]

@Westi

I'm getting SMTP2go setup... do you have any suggestions on how to set this up? what should the SMTP settings look like in the VM Pro client app? I'm sure it looks different for everyone, but i'm sure ill need a little guidance.

thanks again for the suggestion!

 

[headcase69]

@Westi

I got it to work!!!!!!!! thanks for the suggestion. I hate it had to come to this, but it works! hopefully Avaya will catch up with all this authentication mess...

thanks again!

 

[Westi]

Good to hear
just make sure you allow SMTP2Go to send for your domain and all should work.
Less headache than waiting for Avaya to discover TLS 1.2

Joe
FHandw, ACSS, ACIS

"Dew knot truss yore Spell Cheque

 

[dagwoodsystems]

Did you try smtp-legacy.office365.com, port 587 with STARTTLS?


Tim Alberstein

 

[IPGuru]

DO yourself a huge favour & migrate to application server!

Do things on the cheap & it will cost you dear

ACSS