You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/communications-gateway/prepare-for-live-traffic-operator-connect.md
+14-14Lines changed: 14 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,7 +51,7 @@ In this article, you learn about the steps that you and your onboarding team mus
51
51
52
52
## Methods
53
53
54
-
In some parts of this article, the steps you must take depend on whether you're using the Number Management Portal (preview), the Provisioning API (preview), or the Operator Connect portal. This article provides instructions for each option. Choose the appropriate instructions.
54
+
In some parts of this article, the steps you must take depend on whether you're using the Provisioning API (preview), the Number Management Portal (preview), or the Operator Connect portal and APIs. This article provides instructions for each option. Choose the appropriate instructions.
55
55
56
56
## Ask your onboarding team to register your test enterprise tenant
57
57
@@ -79,7 +79,15 @@ Integration testing requires setting up your test tenant for Operator Connect or
79
79
1. Select your company in the list of operators, fill in the form and select **Add as my operator**.
80
80
1. In your test tenant, create some test users (if you don't already have suitable users). License the users for Teams Phone System and place them in Teams Only mode.
81
81
1. Configure emergency locations in your test tenant.
82
-
1. Upload numbers in the Number Management Portal (preview), over the Provisioning API (preview), or using the Operator Connect Operator Portal. Use the Calling Profile that you obtained from your onboarding team.
82
+
1. Upload numbers for integration testing over the Provisioning API (preview), in the Number Management Portal (preview), or using the Operator Connect Operator Portal.
83
+
84
+
# [Provisioning API (preview)](#tab/provisioning-api)
85
+
86
+
The following steps summarize the requests you must make to the Provisioning API. For full details of the relevant API resources, see the [API Reference](/rest/api/voiceservices).
87
+
88
+
1. Find the _RFI_ (Request for information) resource for your test tenant and update the `status` property of its child _Customer Relationship_ resource to indicate the agreement has been signed.
89
+
1. Create an _Account_ resource that represents the customer.
90
+
1. Create a _Number_ resource as a child of the Account resource for each test number.
@@ -92,14 +100,6 @@ Integration testing requires setting up your test tenant for Operator Connect or
92
100
1. Select **View numbers** and select **Upload numbers**.
93
101
1. Fill in the fields as required, and then select **Review and upload** and **Upload**.
94
102
95
-
# [Provisioning API (preview)](#tab/provisioning-api)
96
-
97
-
The following steps summarize the requests you must make to the Provisioning API. For full details of the relevant API resources, see the [API Reference](/rest/api/voiceservices).
98
-
99
-
1. Find the _RFI_ (Request for information) resource for your test tenant and update the `status` property of its child _Customer Relationship_ resource to indicate the agreement has been signed.
100
-
1. Create an _Account_ resource that represents the customer.
101
-
1. Create a _Number_ resource as a child of the Account resource for each test number.
102
-
103
103
# [Operator Portal](#tab/no-flow-through)
104
104
105
105
1. Ask your onboarding team for the name of the Calling Profile that you must use for these test numbers. The name typically has the suffix `CommsGw`. We created this Calling Profile for you during the Azure Communications Gateway deployment process.
@@ -183,6 +183,10 @@ Your staff can use a selection of key metrics to monitor Azure Communications Ga
183
183
184
184
Your onboarding team must provide Microsoft with proof that you have integrated with the Microsoft Teams Operator Connect APIs for provisioning. Choose the appropriate instructions for your deployment.
185
185
186
+
# [Provisioning API (preview)](#tab/provisioning-api)
187
+
188
+
Your onboarding team can obtain proof automatically. You don't need to do anything.
You can't use the Number Management Portal after you launch, because the Operator Connect and Teams Phone Mobile programs require full API integration. You can integrate with Azure Communications Gateway's [Provisioning API](provisioning-platform.md) or directly with the Operator Connect API.
@@ -196,10 +200,6 @@ If you integrate with the Operator Connect API, provide your onboarding team wit
196
200
- Unassign TN
197
201
- Release TN
198
202
199
-
# [Provisioning API (preview)](#tab/provisioning-api)
200
-
201
-
Your onboarding team can obtain proof automatically. You don't need to do anything.
202
-
203
203
# [Operator Connect APIs](#tab/no-flow-through)
204
204
205
205
Provide your onboarding team with proof of successful API calls for:
0 commit comments