Prepare for live traffic with Microsoft Teams Direct Routing and Azure Communications Gateway
Before you can launch your Microsoft Teams Direct Routing service, you and your onboarding team must:
- Test your service.
- Prepare for launch.
In this article, you learn about the steps that you and your Azure Communications Gateway onboarding team must take.
Important
Some steps can require days or weeks to complete. We recommend that you read through these steps in advance to work out a timeline.
Prerequisites
You must have completed the following procedures.
- Prepare to deploy Azure Communications Gateway
- Deploy Azure Communications Gateway
- Integrate with Azure Communications Gateway's Provisioning API
- Connect Azure Communications Gateway to Microsoft Teams Direct Routing
- Configure a test customer for Microsoft Teams Direct Routing
- Configure test numbers for Microsoft Teams Direct Routing
Carry out integration testing and request changes
Network integration includes identifying SIP interoperability requirements and configuring devices to meet these requirements. For example, this process often includes interworking header formats and/or the signaling and media flows used for call hold and session refresh.
You must test typical call flows for your network. Your onboarding team will provide an example test plan that we recommend you follow. Your test plan should include call flow, failover, and connectivity testing.
- If you decide that you need changes to Azure Communications Gateway, ask your onboarding team. Microsoft must make the changes for you.
- If you need changes to the configuration of devices in your core network, you must make those changes.
Test raising a ticket
You must test that you can raise tickets in the Azure portal to report problems with Azure Communications Gateway. See Get support or request changes for Azure Communications Gateway.
Learn about monitoring and maintenance
Your operations team can use a selection of key metrics to monitor Azure Communications Gateway. These metrics are available to anyone with the Reader role on the subscription for Azure Communications Gateway. See Monitoring Azure Communications Gateway.
Your operations team must have Azure Monitor alerts for:
- Azure Service Health notifications to stay informed about upcoming upgrades and scheduled maintenance activities.
- Azure resource health notifications to stay informed about changes in the health of Azure Communications Gateway.
Next steps
- Learn about getting support and requesting changes for Azure Communications Gateway.
- Learn about monitoring Azure Communications Gateway.
- Learn about maintenance notifications.
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for