Skip to content

Commit 68de7a5

Browse files
authored
Remove refs to AOCP
1 parent 9a70d3f commit 68de7a5

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

articles/communications-gateway/provisioning-platform.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ You can configure Azure Communications Gateway with the details of your customer
1616

1717
- Associate numbers with backend services.
1818
- Provision backend services with customer configuration (sometimes called _flow-through provisioning_).
19-
- Add custom header configuration (available for all communications services except Azure Operator Call Protection Preview and Teams Phone Mobile).
19+
- Add custom header configuration (available for all communications services except Teams Phone Mobile).
2020

2121
You can provision Azure Communications Gateway with the:
2222

@@ -31,7 +31,6 @@ The following table shows how you can provision Azure Communications Gateway for
3131
|Operator Connect | Automatically set up if you use the API for flow-through provisioning or you use the Number Management Portal | Recommended (with API) | Supported |
3232
|Teams Phone Mobile | Automatically set up if you use the API for flow-through provisioning or you use the Number Management Portal | Recommended (with API) | Not Supported |
3333
|Zoom Phone Cloud Peering | Required | Not supported | Supported |
34-
| Azure Operator Call Protection Preview | Required | Automatic | Not supported |
3534

3635
Flow-through provisioning of Operator Connect and Teams Phone Mobile with the Provisioning API interoperates with the Operator Connect APIs. It therefore allows you to meet the requirements for API-based provisioning from the Operator Connect and Teams Phone Mobile programs.
3736

@@ -40,7 +39,7 @@ Flow-through provisioning of Operator Connect and Teams Phone Mobile with the Pr
4039
4140
## Associating numbers with specific communications services
4241

43-
For Microsoft Teams Direct Routing, Zoom Phone Cloud Peering, and Azure Operator Call Protection, you must provision Azure Communications Gateway with the numbers that you want to assign to each of your customers and enable each number for the chosen communications service. This information allows Azure Communications Gateway to:
42+
For Microsoft Teams Direct Routing and Zoom Phone Cloud Peering, you must provision Azure Communications Gateway with the numbers that you want to assign to each of your customers and enable each number for the chosen communications service. This information allows Azure Communications Gateway to:
4443

4544
- Route calls to the correct communications service.
4645
- Update SIP messages for Microsoft Teams Direct Routing with the information that Microsoft Phone System requires to match calls to tenants. For more information, see [Identifying the customer tenant for Microsoft Phone System](interoperability-teams-direct-routing.md#identifying-the-customer-tenant-for-microsoft-phone-system).

0 commit comments

Comments
 (0)