I am trying to set up IP Office 8.1.65 with embedded voicemail to utilize Office 365 Outlook as the mail client for voicemail to email notifications. In the IP office under SMTP I have set an IP address tyhat the company IT person says it the Outlook SMTP address. I have tried ports 587 and 25 with and without user authentication. Is there something I am missing or is this not supported with embedded voicemail.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
voicemail to email
- Thread starter Dweidmann
- Start date
Eric121508
Programmer
Office 365 requires TLS encryption for SMTP. This isn't supported with IPO until RLS 9.1, where they add a "Starttls" check box, and TLS support in security settings.
You will either need them to setup a relay connector to forward the traffic to office 365 via relay, or use some type of public email relay server such as However these do occasionally get blacklisted so you may have to create a new account for it once in a while if you go with the free version.
What my company did was build our own public relay server with SMTP2Go.com. You pay for the service, and then you can eithert use password authentication, or you can add their puplic IP address to the allowed senders list. It works fantastic, and its super easy to setup, and it supports standard and TLS on port 25, 80, 587, 2525, or you can use SSL on 443, 465, 8465. They do all the port mapping, and the nice thing is when you use a public relay, the customers are not limited to only using the work domain email account, and email address can be put in the users vm tab to receive voicemail emails.
You will either need them to setup a relay connector to forward the traffic to office 365 via relay, or use some type of public email relay server such as However these do occasionally get blacklisted so you may have to create a new account for it once in a while if you go with the free version.
What my company did was build our own public relay server with SMTP2Go.com. You pay for the service, and then you can eithert use password authentication, or you can add their puplic IP address to the allowed senders list. It works fantastic, and its super easy to setup, and it supports standard and TLS on port 25, 80, 587, 2525, or you can use SSL on 443, 465, 8465. They do all the port mapping, and the nice thing is when you use a public relay, the customers are not limited to only using the work domain email account, and email address can be put in the users vm tab to receive voicemail emails.
amriddle01
Programmer
You can configure Office 365 to work with unencrypted connections, we have a solicitors running 3 sites using 365 and they're on 9.0.
Their IT sorted that side out but the SMTP server is customername-co-uk.mail.protection.outlook.com if that points you in the right direction
Their IT sorted that side out but the SMTP server is customername-co-uk.mail.protection.outlook.com if that points you in the right direction
- Status