Merge pull request #310692 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: PhilKang0704

articles/expressroute/using-expressroute-for-microsoft-pstn.md

@@ -1,10 +1,10 @@
 ---
 title: 'Using ExpressRoute for Microsoft PSTN Services'
-description:  ExpressRoute circuits can be used for Microsoft PSTN services, including Operator Connect, Azure Communications Gateway, and Azure Communication Services Direct Routing.
+description:  ExpressRoute circuits can be used for Microsoft PSTN service, Operator Connect.
 author: tracsman
 ms.service: azure-expressroute
 ms.topic: concept-article
-ms.date: 09/06/2023
+ms.date: 08/07/2025
 ms.author: jonor
 manager: tracsman
 # Customer intent: "As a network administrator, I want to configure ExpressRoute Microsoft Peering for PSTN services, so that I can ensure reliable and high-quality voice connectivity for my organization’s communication needs."
@@ -19,28 +19,22 @@ An ExpressRoute circuit provides private connectivity to the Microsoft backbone
 
 For more information about ExpressRoute, see the [Introduction to ExpressRoute][ExR-Intro] article.
 
-You can use ExpressRoute Microsoft Peering to connect to the following Microsoft PSTN services:
+You can use ExpressRoute Microsoft Peering to offer the following Microsoft PSTN services:
 
 * Operator Connect (including Calling, Conferencing and Teams Phone Mobile offers)
-* Azure Communications Gateway
-* Azure Communication Services Direct Routing
 
 > [!IMPORTANT]
-> Operator Connect SIP Trunks do not support encryption when using ExpressRoute Microsoft Peering connectivity. 
+> Encryption support is pending delivery for Express Route PSTN connectivity. 
 
 In this article, you'll learn about why you might consider using ExpressRoute to connect to these Microsoft PSTN services.
 
 ## When to use ExpressRoute Microsoft Peering for Microsoft PSTN services
 
 In certain scenarios, using ExpressRoute Microsoft Peering provides better quality for voice calling than using the internet for your traffic. Microsoft owns one of the largest global networks, and the Microsoft network is optimized to achieve the core objective of offering the best network performance. The Microsoft network uses "cold potato" routing, meaning traffic enters and exits as close as possible to client devices/customer networks to reduce network hops and provide optimal quality of service for voice traffic. The Microsoft network is designed with redundancy and is highly available. For more information about architecture optimization, see [How Microsoft builds its fast and reliable global network][MGN].
 
-### For enterprises managing your own PSTN connectivity
-
-If your PSTN traffic is concentrated in multiple global locations and each location has its own ExpressRoute connection, ExpressRoute Microsoft Peering could be suited to you. This architecture is common for users of Direct Routing who have deployed their own SBCs in sites with ExpressRoute connectivity.
-
 ### For Communications Services Providers
 
-We recommend that Communications Services Providers use Peering Service Voice interconnect (sometimes also called MAPSV or MAPS Voice) to connect their networks to the Microsoft network. To configure Peering Service Voice interconnection, follow [Internet peering for Peering Service Voice walkthrough](../internet-peering/walkthrough-communications-services-partner.md).
+We recommend Communications Services Providers use Microsoft Azure Peering Service Voice interconnect (also known as MAPSV or MAPS Voice) to connect their networks to the Microsoft network. To configure Peering Service Voice interconnection, follow [Internet peering for Peering Service Voice walkthrough](../internet-peering/walkthrough-communications-services-partner.md).
 
 In some cases, using ExpressRoute Microsoft Peering might be preferable as it allows you to:
 
@@ -53,7 +47,7 @@ Operator Connect providers must ensure the architecture used for network connect
 
 ## Configuring Microsoft Peering for use with Microsoft PSTN services
 
-Multiple Microsoft services (including Microsoft PSTN services, Microsoft 365 services and some Azure PaaS offerings) can be connected via Microsoft Peering. With the use of a *Route Filter*, you can select which service prefixes you want Microsoft to advertise over Microsoft Peering to your on-premises network. To configure a suitable Route Filter for Microsoft PSTN services, follow [Configure route filters for Microsoft Peering][ExRRF], setting *Azure SIP Trunking* as an allowed service community.
+Multiple Microsoft services (including Microsoft PSTN services, Microsoft 365 services and some Azure PaaS offerings) can be connected via Microsoft Peering. With the use of a *Route Filter*, you can select which service prefixes you want Microsoft to advertise over Microsoft Peering to your on-premises network. To configure a suitable Route Filter for Microsoft PSTN services, follow [Configure route filters for Microsoft Peering][ExRRF], setting *Azure SIP Trunking* as an allowed service community. The community reference is Microsoft PSTN services 12076:5250.
 
 All Microsoft PSTN services supported for Microsoft Peering use the 52.120.0.0/15 subnet. The Azure SIP Trunking service community refers to this subnet.