I am unable to provision a SIP device, the noam.ipp.sdg.teams.microsoft.com site is showing that all services arent available right now.

Dear @Chubeck, Eric,

Thank you for your update. I truly sorry for late response.

If the issue persists after verifying your setup and trying the suggested workarounds, the best course of action is to contact Microsoft Support by creating support ticket via Admin Center. They have access to backend diagnostic tools and can confirm whether this is part of a regional outage or a deeper SIP Gateway service problem.

Here’s what you should include when opening the ticket:

• Affected URL: http://noam.ipp.sdg.teams.microsoft.com/mac.ini
• Error message: “Our services aren’t available right now”
• Device details: AudioCodes MP112, firmware 6.60A.367.005
• Steps taken: Verified network (no firewall/proxy), confirmed other devices fail, attempted alternate URLs
• Impact: Unable to provision SIP devices for Teams

Here's the Microsoft Official Support Site: https://support.microsoft.com/en-us/contactus

For more information and instruction: Get support for Microsoft 365 for business

I truly apologize that as forum moderators; our primary goal is to provide helpful guidance and support through general troubleshooting steps. While we don’t have access to internal systems or administrative tools required to resolve account-specific or backend issues, we truly appreciate your understanding of these limitations. We genuinely hope the information we share helps guide you in the right direction, and we're always here to assist as much as we can within our scope.

Once your support ticket is created, could you kindly share the ticket number with me in a private message? This will allow us to check whether the case is currently being handled by an agent and ensure you’re receiving the assistance you need.

Thank you for your patience and your understanding. If you have any questions, please feel free to reach out.

I'm looking forward for your reply.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".   

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

This is an AudioCodes MP112. It has firmware version 6.60A.367.005.

This is the first time provisioning this particular device, but we have provisioned many of the same device previously.

The device is not behind a firewall or proxy.

I believe the issue is with the regional URL failing. When trying to access that site for the mac.ini on any device, on any network, a page pops up that the service is down.

Dear @Chubeck, Eric,

Thank you for posting your question in the Microsoft Q&A forum.

Before giving you the best solution, could you please confirm these questions below to help me diagnose the issue more effectively: 

• What SIP device model and firmware version are you using?
• Has the device been successfully provisioned before, or is this the first attempt?
• Is the device behind a firewall or proxy?

SIP Gateway enables your organization to use any compatible SIP device together with Microsoft Teams. This article lists some common issues that might occur when you use a compatible SIP device to make and receive calls through Teams, and provides steps to help you troubleshoot these issues, visit: Common issues when you use SIP devices with Teams. Therefore, here are some steps I recommend you try while waiting for further investigating:

Option 1:

• Verify that you're using a compatible SIP device.
• Make sure that you reset the device to the factory default settings.
• Verify that the SIP Gateway provisioning server's URL begins in "HTTP", not "HTTPS". For example, use http://noam.ipp.sdg.teams.microsoft.com, not https://noam.ipp.sdg.teams.microsoft.com.
• Check whether the device can connect to SIP Gateway. Verify that the connection isn't blocked by your firewall or proxy server, and that the required HTTPS endpoints and TCP/UDP ports are open.
• For more information, see the list of items that follows "Before you can configure SIP Gateway" in Configure SIP Gateway.

Option 2:

• Make sure that you're using the correct credentials. Sign in to the Teams app by using the same credentials to check whether the credentials are correct.
• If your organization uses Conditional Access, make sure that the IP address of SIP Gateway is excluded. For more information, see Configure conditional access.

Option 3:

• Check whether the requirements to use SIP Gateway are met. To use SIP Gateway, Teams users must have a phone number that has PSTN calling enabled.
• Check whether SIP Gateway policy is set correctly. For more information, see Enable SIP Gateway for the users in your organization.
• Check whether another user from a different tenant signed in to the device, but didn't sign out gracefully. If they didn't, have that user sign in and sign out again.
• Check whether the device can connect to SIP Gateway. Verify that the connection isn't blocked by your firewall or proxy server, and that the required HTTPS endpoints and TCP/UDP ports are open. For more information, see the list of items that follows "Before you can configure SIP Gateway" in Configure SIP Gateway.SIP Gateway enables your organization to use any compatible SIP device together with Microsoft Teams. This article lists some common issues that might occur when you use a compatible SIP device to make and receive calls through Teams, and provides steps to help you troubleshoot these issues.

Alternative approach if urgent

Some admins have temporarily pointed devices to http://sip.pstnhub.microsoft.com for manual provisioning when regional URLs fail. This is not officially documented as a permanent solution but might work in some cases.

I hope this information is helpful. Please follow these steps and let me know if it works for you. If not, we can work together to resolve this.

Please understand that our initial response does not always resolve the issue immediately. However, with your help and more detailed information, we can work together to find a solution.

Thank you for your patience and your understanding. If you have any questions, please feel free to reach out.

I'm looking forward for your reply.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".   

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.