Voicemail pro vm to email 4

[qthephoneman]

I am having issues with a voicemail pro 8.0, manager is at 8.0, and customer installed windows 7. They are getting voip phones and dont want to upgrade anything so i am trying to make it work with what they have. Everything was working until a semiannual update moved them to windows 10 and vmpro stopped working. She ordered 7 and installed it without backing anything up so i had to rebuild everything. Vm to email will not work. In vmpro, email sender> all domain, username, and password is correct with authentication checked and those fields filled in with user and pswd. Email receiver has the domain inserted in the domain field. What am i missing? I'm not good with reading sys monitor.

 

[Westi]

You can install VmPro ( and Manager really) of R 9.1 and it will work better with Win10 than the old R8.0

You can even install the R11.x admin suite if you like but VmPro you have to stick with 9.1.x (use the latest)

Also make sure to install it with Administrator rights otherwise it may act up a bit.

Joe
FHandw, ACSS, ACIS

"Dew knot truss yore Spell Cheque

 

[chadphoneguy]

Westi, QthePhoneman is asking for solutions to fix the issue with what they have now. It did work before on this release.
This is a tech that works for me that created this post. He stated in the original post, the customer is not willing to upgrade at this time.
Their corporate office is replacing the system within the next 6 to 8 months supposedly with an IP cloud system they are migrating all of their locations to.
Plus they have 2 local office locations with Avaya IPO networked together, so to upgrade it would be upgrading both locations from 8.0 to 11.1 to even attempt to fix this now.
ANY SOLUTIONS THAT HELP US FIX THE ISSUE WITH VM TO EMAIL ON 8.0 WITH THE WINDOWS 7 THEY CURRENTLY HAVE?
As QthePhoneman stated, VM to email worked, then an update happened that upgraded the windows 7 VM server to Windows 10 (BTW, all automatic updates were turned off, but somehow the Windows 7 still updated to Windows 10). So after my tech got everything to work again after that update, except for the VM to email, since it's not compatible with Windows 10, the customer bought a Windows 7 copy. The customer then installed it themselves without contacting us or without backing anything up. And then my tech had to go recreate everything again. But the VM to email still is not working even after going back to Windows 7.
Any suggestions besides the obvious "upgrade the phone system licensing and VM server" is greatly appreciated.
We just need to get the VM to email working again until their corporate actually goes through with the upgrade, they really use this feature alot.

 

[chiden]

I'm having similar issue with 9.1 VM Pro's but not 11.0.
These are ones using Microsoft.
Looks like not able to do handshake. Assuming a TLS issue.

27/10/2021 14:37:06.997 - Attempting to connect to host smtp.office365.com on port 587, local bound address is (null)
27/10/2021 14:37:07.088 - Successfully connected to host smtp.office365.com on port 587
27/10/2021 14:37:07.139 - < 220 CH0PR03CA0357.outlook.office365.com Microsoft ESMTP MAIL Service ready at Wed, 27 Oct 2021 19:37:07 +0000
27/10/2021 14:37:07.189 - ######## START OF CHUNK ######
27/10/2021 14:37:07.241 - > EHLO FAKE-VMPRO
27/10/2021 14:37:07.317 - ######## END OF CHUNK ######
27/10/2021 14:37:07.399 - < 250-CH0PR03CA0357.outlook.office365.com Hello [12.231.201.3]
27/10/2021 14:37:07.399 - 250-SIZE 157286400
27/10/2021 14:37:07.399 - 250-PIPELINING
27/10/2021 14:37:07.399 - 250-DSN
27/10/2021 14:37:07.399 - 250-ENHANCEDSTATUSCODES
27/10/2021 14:37:07.399 - 250-STARTTLS
27/10/2021 14:37:07.399 - 250-8BITMIME
27/10/2021 14:37:07.399 - 250-BINARYMIME
27/10/2021 14:37:07.399 - 250-CHUNKING
27/10/2021 14:37:07.399 - 250 SMTPUTF8
27/10/2021 14:37:07.471 - ######## START OF CHUNK ######
27/10/2021 14:37:07.533 - > STARTTLS
27/10/2021 14:37:07.596 - ######## END OF CHUNK ######
27/10/2021 14:37:07.633 - < 220 2.0.0 SMTP server ready
27/10/2021 14:37:07.712 - ######## START OF CHUNK ######
27/10/2021 14:37:07.750 - > EHLO FAKE-VMPRO
27/10/2021 14:37:07.813 - CSMTPConnection::SendChunk: Failed to send data chunk error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure
27/10/2021 14:37:07.875 - CSMTPConnection::ConnectESMTP: An unexpected error occurred while sending the EHLO command. error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure
27/10/2021 14:37:07.912 - ######## START OF CHUNK ######
27/10/2021 14:37:07.950 - > HELO FAKE-VMPRO
27/10/2021 14:37:08.012 - CSMTPConnection::SendChunk: Failed to send data chunk error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure
27/10/2021 14:37:08.076 - CSMTPConnection::ConnectSMTP: An unexpected error occurred while sending the HELO command error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure
27/10/2021 14:37:08.113 - ######## START OF CHUNK ######
27/10/2021 14:37:08.176 - > QUIT
27/10/2021 14:37:08.212 - CSMTPConnection::SendChunk: Failed to send data chunk error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure
27/10/2021 14:37:08.276 - CSMTPConnection:isconnect: Failed in call to send QUIT command error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure
27/10/2021 14:37:08.313 - <
27/10/2021 14:37:08.375 - CSMTPConnection:isconnect: An unexpected QUIT response was received
27/10/2021 14:37:08.437 - CSMTPConnection::Connect: An unexpected HELO/EHLO response was received
27/10/2021 14:37:08.525 - CSMTPConnection:isconnect: Already disconnected from SMTP server, doing nothing

 

[chadphoneguy]

Anybody with any suggestions on what to do for this?
VM to email not working on 8.0 Avaya IP Office with VM Pro and a new version of Windows 7 installed.
Used to work on the old Windows 7 version.
But had to recreate everything when it was deleted when the customer installed the windows 7 version.
I know repeating myself here, but hadn't received any valid suggestions, besides upgrade, which isn't an option for the customer at this time.
Thank you in advance for any help or suggestions you may have.

 

[sizbut]

AFTER YOUR ATTACK AGAINST THE FIRST PERSON WHO TRIED TO HELP WITH A PERFECTLY VALID OPTION, I'M KEEPING QUIET.

You could have just said that unfortunately upgrading wasn't an option and so would welcome any alternate ideas. B

Stuck in a never ending cycle of file copying.

 

[CarGoSki]

Chad, you could try O365 direct send relay which has never failed for me. BTW Westi and Sizbut are at the top of the the IPO Tech ladder in IPO land and are well respected here. And you instead have failed to even provide an smtp trace of the failure for review and went ALL CAPS in your frustration. It is always best to nice to those who do know what they are doing.


Microsoft Office 365 Direct Send Relay:

https://docs.microsoft.com/en-us/ex...nter-or-application-to-office-365-direct-send

VMPro SMTP settings to connect to Office 365 Direct Send Relay:
Domain: domain.com
Server: domain.com.mail.protection.outlook.com
Port: 25
Identifier(Sender): vmpro@domain.com
Authentication: <none>

One last note about domain.com.mail.protection.outlook.com
Microsoft O365 seems to have a common server name as mail.protection.outlook.com and the domain.com will be provided from Microsoft.
It is usually the company name you setup so I suspect yours could be exasperated.com and when combined gives..
Server: exasperated.com.mail.protection.outlook.com

 

[IPGuru]

Linux application serve is available for this release & illiminates all Windows compatibility issues


Do things on the cheap & it will cost you dear

Avaya Remote Support Engineer (A.R.S.E)

 

[chadphoneguy]

Woah ummm, I didn't attack anybody. Sorry if it came off that way.
I appreciate the options, it's just he said in the beginning that upgrading wasn't an option, is all I was saying.
Sorry if it somehow sounded like an attack, definitely didn't mean it to.
And CarGoSki, I appreciate the option you gave us here, we can try that.
Thanks for the suggestions and we'll try a few things this week and see where we are at with it.
thanks and have a good start to November week everyone.

 

[critchey]

Not only did you write in all caps (dont do that here it wont fly) you didn't bother reading what he actually wrote.

You can install VmPro ( and Manager really) of R 9.1 and it will work better with Win10 than the old R8.0

He said you could download R9.1 VMPro and run it on the that computer already running VMPro. HE SAID NOTHING ABOUT UPGRADING TO R11(see how it turns into an attack when I do this?). You can keep your systems on R8 and just run VMPro on R9.1 on the PC(I believe R9.1 VMPro would run on Win7 or Win10 but Win7 really shouldn't be used).

Keep in mind that everyone on this forum is helping you and others for absolutely nothing. If the posted solution isn't doable, it is fine, but when you start posting in all caps and clearly don't even read the solution you will run into attitude.



The truth is just an excuse for lack of imagination.

 

[Westi]

Wow, was not looking for a few days and a fight breaks out.

I was not offended btw. just busy - It is hard to offend me really

I might not have expressed that installing a higher release of VmPro doesn't require an upgrade of the system.

I however find that CarGoSki's info is great and I will hang on to that one.

So all good


Joe
FHandw, ACSS, ACIS

"Dew knot truss yore Spell Cheque

 

[Ekster]

Chad, you could try O365 direct send relay which has never failed for me. BTW Westi and Sizbut are at the top of the the IPO Tech ladder in IPO land and are well respected here. And you instead have failed to even provide an smtp trace of the failure for review and went ALL CAPS in your frustration. It is always best to nice to those who do know what they are doing.


Microsoft Office 365 Direct Send Relay:

https://docs.microsoft.com/en-us/exchange/mail-flo...

VMPro SMTP settings to connect to Office 365 Direct Send Relay:
Domain: domain.com
Server: domain.com.mail.protection.outlook.com
Port: 25
Identifier(Sender): vmpro@domain.com
Authentication: <none>

One last note about domain.com.mail.protection.outlook.com
Microsoft O365 seems to have a common server name as mail.protection.outlook.com and the domain.com will be provided from Microsoft.
It is usually the company name you setup so I suspect yours could be exasperated.com and when combined gives..
Server: exasperated.com.mail.protection.outlook.com

This is the way we go with all Office 365 instances of voicemail to email, assuming the customer is happy with it. The beauty of it is, you don't need an Office 365 licence to connect this way!

“Some humans would do anything to see if it was possible to do it.
If you put a large switch in some cave somewhere, with a sign on it saying 'End-of-the-World Switch. PLEASE DO NOT TOUCH'.
The paint wouldn't even have time to dry.”

Terry Pratchet