Merge pull request #173504 from boris-bazilevskiy/dr-provisioning

SBC list edition, MP regions updated, PSTN&SMS data note

Author: v-andreaco

articles/communication-services/concepts/privacy.md

@@ -19,6 +19,9 @@ Azure Communication Services is committed to helping our customers meet their pr
 
 When creating an Communication Services resource, you specify a **geography** (not an Azure data center). All chat messages, and resource data stored by Communication Services at rest will be retained in that geography, in a data center selected internally by Communication Services. Data may transit or be processed in other geographies. These global endpoints are necessary to provide a high-performance, low-latency experience to end-users no matter their location.
 
+> [!NOTE]
+> For PSTN & SMS, call and message data records required for the operation and billing of the service, may be stored in the United States.
+
 ## Data collection
 
 Azure Communication Services only collects diagnostic data required to deliver the service. 

articles/communication-services/concepts/telephony-sms/certified-session-border-controllers.md

@@ -37,8 +37,8 @@ If you have any questions about the SBC certification program for Communication
 |[AudioCodes](https://www.audiocodes.com/media/lbjfezwn/mediant-sbc-with-microsoft-azure-communication-services.pdf)|Mediant SBC|7.40A
 |Metaswitch|Perimeta SBC|4.9|
 |[Oracle](https://www.oracle.com/technical-resources/documentation/acme-packet.html)|Oracle Acme Packet SBC|8.4|
-|Ribbon Communications|SBC SWe|9.02|
-||SBC SWe Lite|9.0
+|Ribbon Communications|SBC SWe / SBC 5400 / SBC 7000|9.02|
+||SBC SWe Lite / SBC 1000 / SBC 2000|9.0
 
 Note the certification granted to a major version. That means that firmware with any number in the SBC firmware following the major version is supported.
 

articles/communication-services/concepts/telephony-sms/direct-routing-infrastructure.md

@@ -153,18 +153,15 @@ The port range of the Media Processors is shown in the following table:
 
 ## Media traffic: Media processors geography
 
-The media traffic flows via components called media processors. Media processors are placed in the same datacenters as SIP proxies. Also, there are additional media processors to optimize media flow. For example, we do not have a SIP proxy component now in Australia (SIP flows via Singapore or Hong Kong SAR) but we do have the media processor locally in Australia. The need for the media processors locally is dictated by the latency which we experience by sending traffic long-distance, for example from Australia to Singapore or Hong Kong SAR. While latency in the example of traffic flowing from Australia to Hong Kong SAR or Singapore is acceptable to preserve good call quality for SIP traffic, for real-time media traffic it is not.
-
-Locations where both SIP proxy and media processor components deployed:
+The media traffic flows via components called media processors. Media processors are placed in the same datacenters as SIP proxies:
 - US (two in US West and US East datacenters)
 - Europe (Amsterdam and Dublin datacenters)
 - Asia (Singapore and Hong Kong SAR datacenters)
 - Australia (AU East and Southeast datacenters)
-
-Locations where only media processors are deployed (SIP flows via the closest datacenter listed above):
 - Japan (JP East and West datacenters)
 
 
+
 ## Media traffic: Codecs
 
 ### Leg between SBC and Cloud Media Processor or Microsoft Teams client.