Author Topic: NuPoint UM Standard working with Office 365 in the Cloud  (Read 6120 times)

Offline Tech Electronics

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2983
  • Country: us
  • Karma: +89/-1
    • View Profile
NuPoint UM Standard working with Office 365 in the Cloud
« on: December 19, 2013, 12:13:19 PM »
I am currently having an issue with getting the Office 365 server [outlook.office365.com or smtp.office365.com] accepting connections.

Has anyone been successful setting up UM Standard or Advanced with Office 365.

Thanks,

TE


Offline Tech Electronics

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2983
  • Country: us
  • Karma: +89/-1
    • View Profile
Re: NuPoint UM Standard working with Office 365 in the Cloud
« Reply #1 on: January 02, 2014, 10:54:56 PM »
Everyone,

I finally got a solution to this problem that may help others in the future.

1. Office 365 in the Cloud is not compatible with NuPoint Advanced UM, but hopefully in the future it will now that I turned over all my findings to Mitel Engineering.
2. Office 365 in the Cloud is compatible with NuPoint Standard UM and can be two ways.

Standard UM can be set up utilizing either port 25 with No Authentication or 587/TLS with Authentication.

Port 25 No Authentication Setup. This setup allows all emails to go through with no problems, but it takes longer to set up due to the Office 365 portion.

1. Get an administrator email login to the Office 365 portal
2. Select the Admin drop down and click on Office 365
3. Select Domains from the left side menu
4. Select the radio button for the primary domain
5. Click on View DNS Settings link
6. Click on the View DNS Records link under DNS Records paragraph
7. Copy the MX Records Points of Address URL
8. Click Return to Domains List
9. Select Exchange from the Admin drop down menu
10. Select Mail Flow from the left side menu
11. Select Connectors from the top menu on the right
12. Select the + symbol to create a new Inbound Connector
13. Under the General Menu settings: Create a Name for the Connector, Check Inbound Connector, Select On-Premises for the Connector Type and provide a comment for what it is used for.
14. Under the Security settings: Set Connection Security to Opportunistic TLS and Under Domain Restrictions set it to None
15. Under the Scope Menu settings: Click the + symbol under *Domains and add a *, Under *IP Addresses add the outside IP address of the MAS Server.
Note: You can find the outside IP address used by the MAS under the Configuration menu under Review Configuration and find the Internet Visible IP Address (to AMC).

MAS Portion
1. Under Configuration > Email Settings use the MX record retrieved from step 7 above
2. Use Port 25 and do not put anything in the authentication section

NuPoint Web Console Portion
1. Unified Messaging > Smarthost Configuration verify that the radio button is set to let the NuPoint determine the from address.
2. Set up the FCOS for Standard UM and make sure to have bits 262, 263, and 264 turned on in order to send Caller ID information out in the email.
Note: Feature bit 280 is not needed even though Feature bit 264 says that it is; go figure.


Port 587/TLS with Authentication. This works fine, but it does not allow the Welcome E-mail to be delivered since the email address, donotreply@mas.{domainname.com} doesn't have permission to send email.

Office 365 Portion
1. Have an Office 365 administrator set up a mailbox on their server.
2. Set the new mailbox to be an administrator. <- This step is crucial or emails will be denied for no reason in some cases.
3. Log in to the new mailbox and verify that you can send and receive emails.

MAS Portion
1. Under Configuration > Email Settings use smtp.office365.com
2. Use Port 587/TLS if available
3. Set the Login and Password credentials for the new administrator mailbox.

NuPoint Web Console Portion
1. Unified Messaging > Smarthost Configuration verify that the radio button is set to let the MAS server to use the Email credentials provided in step 3 above.
2. Set up the FCOS for Standard UM and make sure to have bits 262, 263, and 264 turned on in order to send Caller ID information out in the email.
Note: Feature bit 280 is not needed even though Feature bit 264 says that it is; go figure.

Either one of those scenarios should work with no problems as long Office 365 doesn't change how they do stuff; again.

You can watch the emails being sent out through the View Logs and then select qmail\current.

Thanks,

Te



 

Sitemap 1 2 3 4 5 6 7 8 9 10