Skip to content

Commit db655de

Browse files
committed
Fold setting custom header into general number configuration
1 parent 896cc26 commit db655de

File tree

3 files changed

+14
-41
lines changed

3 files changed

+14
-41
lines changed

articles/communications-gateway/includes/communications-gateway-custom-header-configuration-portal.md

Lines changed: 0 additions & 12 deletions
This file was deleted.

articles/communications-gateway/manage-enterprise-operator-connect.md

Lines changed: 4 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -19,9 +19,8 @@ Azure Communications Gateway's Number Management Portal (preview) enables you to
1919
You can:
2020

2121
* Manage your agreement with an enterprise customer.
22-
* Manage numbers for the enterprise.
22+
* Manage numbers for the enterprise, including (for Operator Connect) optionally configuring a custom header.
2323
* View civic addresses for an enterprise.
24-
* Configure a custom header for a number (not available for Teams Phone Mobile).
2524

2625
## Prerequisites
2726

@@ -146,10 +145,9 @@ Uploading numbers for an enterprise allows IT administrators at the enterprise t
146145

147146
---
148147

149-
1. To remove numbers from an enterprise:
150-
1. Select the numbers.
151-
1. Select **Delete numbers**.
152-
1. Wait 30 seconds, then select **Refresh** to confirm that the numbers have been removed.
148+
1. To change or remove existing numbers:
149+
1. Select the checkbox next to the number you want to change or remove.
150+
1. Select **Edit number** or **Delete numbers** as appropriate.
153151

154152
## View civic addresses for an enterprise
155153

@@ -160,12 +158,6 @@ You can view civic addresses for an enterprise. The enterprise configures the de
160158
1. You can see the address, the company name, the description, and whether the address was validated when the enterprise configured the address.
161159
1. Optionally, select an individual address to view additional information provided by the enterprise, for example the Emergency Location Identification Number (ELIN).
162160

163-
## Configure a custom header for a number
164-
165-
You can specify a custom SIP header value for an enterprise telephone number. This value applies to all SIP messages sent and received by that number. This feature is available for all communications services except Azure Operator Call Protection Preview and Teams Phone Mobile.
166-
167-
[!INCLUDE [instructions for configuring custom headers in the portal](includes/communications-gateway-custom-header-configuration-portal.md)]
168-
169161
## Next steps
170162

171163
Learn more about [the metrics you can use to monitor calls](monitoring-azure-communications-gateway-data-reference.md).

articles/communications-gateway/manage-enterprise-teams-direct-routing.md

Lines changed: 10 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -15,8 +15,7 @@ ms.date: 03/31/2024
1515
Providing Microsoft Teams Direct Routing service with Azure Communications Gateway requires configuration on Azure Communications Gateway and in customer tenants. This article provides guidance on how to set up Direct Routing for a customer, including:
1616

1717
* Setting up a new customer.
18-
* Managing numbers for a customer.
19-
* Configuring a custom header for a number.
18+
* Managing numbers for a customer, including optionally configuring a custom header.
2019

2120
> [!TIP]
2221
> You typically need to ask your customers to change their tenants configuration, because your organization won't have permission.
@@ -139,8 +138,16 @@ When you [set up Direct Routing a the customer](#set-up-direct-routing-for-a-cus
139138
140139
# [Number Management Portal (preview)](#tab/number-management-portal)
141140
141+
To add new numbers:
142+
142143
[!INCLUDE [instructions for configuring Direct Routing numbers in the portal](includes/communications-gateway-direct-routing-configure-numbers-portal.md)]
143144
145+
To change or remove existing numbers:
146+
147+
1. From the overview page for your Communications Gateway resource, find the **Number Management** section in the sidebar. Select **Accounts**.
148+
1. Select the checkbox next to the customer's **Account name** and select **View numbers**.
149+
1. Select the checkbox next to the number you want to change or remove and select **Edit number** or **Delete numbers**.
150+
144151
# [Provisioning API (preview)](#tab/api)
145152
146153
Use Azure Communications Gateway's Provisioning API to provision the details of the numbers you allocated to this customer under the account. Enable each number for Teams Direct Routing. For example API requests, see [Add one number to the account](/rest/api/voiceservices/#add-one-number-to-the-account) or [Add or update multiple numbers at once](/rest/api/voiceservices/#add-or-update-multiple-numbers-at-once) in the _API Reference_ for the Provisioning API.
@@ -149,25 +156,11 @@ Use Azure Communications Gateway's Provisioning API to provision the details of
149156
150157
### Ask the customer to configure users in their tenant
151158
152-
Your customer can now set up users for Microsoft Teams Direct Routing. They must:
159+
Your customer can now set up users for Microsoft Teams Direct Routing. To add new numbers, they must:
153160
154161
1. Enable users for Microsoft Teams Direct Routing, by following [Enable users for Direct Routing](/microsoftteams/direct-routing-enable-users).
155162
2. Configure these users with the voice route for Azure Communications Gateway that [they configured earlier](#ask-the-customer-to-configure-call-routing-that-uses-azure-communications-gateway). For instructions, see the steps for assigning voice routing policies in [Configure call routing for Direct Routing](/microsoftteams/direct-routing-voice-routing).
156163
157-
## Configure a custom header for a number
158-
159-
You can specify a custom SIP header value for an enterprise telephone number. This value applies to all SIP messages sent and received by that number.
160-
161-
# [Number Management Portal (preview)](#tab/number-management-portal)
162-
163-
[!INCLUDE [instructions for configuring custom headers in the portal](includes/communications-gateway-custom-header-configuration-portal.md)]
164-
165-
# [Provisioning API (preview)](#tab/api)
166-
167-
Update the configuration for each number to include the custom SIP header value. For more information on Number resources in the Provisioning API, see the [API Reference](/rest/api/voiceservices) for the Provisioning API.
168-
169-
---
170-
171164
## Next steps
172165
173166
Learn more about [the metrics you can use to monitor calls](monitoring-azure-communications-gateway-data-reference.md).

0 commit comments

Comments
 (0)