remove mention of later TLS versions

boris-bazilevskiy · boris-bazilevskiy · commit 7b888ccec31b · 2024-04-30T17:25:39.000+02:00
diff --git a/articles/communication-services/concepts/telephony/direct-routing-infrastructure.md b/articles/communication-services/concepts/telephony/direct-routing-infrastructure.md
@@ -58,7 +58,7 @@ Learn more:
 [Included CA Certificate List](https://ccadb-public.secure.force.com/microsoft/IncludedCACertificateReportForMSFT)
 
 >[!IMPORTANT]
->Azure Communication Services direct routing supports only TLS 1.2 (or a later version). To avoid any service impact, ensure that your SBCs are configured to support TLS1.2 and can connect using one of the following cipher suites for SIP signaling: 
+>Azure Communication Services direct routing supports only TLS 1.2. To avoid any service impact, ensure that your SBCs are configured to support TLS1.2 and can connect using one of the following cipher suites for SIP signaling: 
 >
 >TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 i.e. ECDHE-RSA-AES256-GCM-SHA384 
 >TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 i.e. ECDHE-RSA-AES128-GCM-SHA256 

Original file line number	Diff line number	Diff line change
`@@ -58,7 +58,7 @@ Learn more:`
`58`	`58`	`[Included CA Certificate List](https://ccadb-public.secure.force.com/microsoft/IncludedCACertificateReportForMSFT)`
`59`	`59`
`60`	`60`	`>[!IMPORTANT]`
`61`		`->Azure Communication Services direct routing supports only TLS 1.2 (or a later version). To avoid any service impact, ensure that your SBCs are configured to support TLS1.2 and can connect using one of the following cipher suites for SIP signaling:`
	`61`	`+>Azure Communication Services direct routing supports only TLS 1.2. To avoid any service impact, ensure that your SBCs are configured to support TLS1.2 and can connect using one of the following cipher suites for SIP signaling:`
`62`	`62`	`>`
`63`	`63`	`>TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 i.e. ECDHE-RSA-AES256-GCM-SHA384`
`64`	`64`	`>TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 i.e. ECDHE-RSA-AES128-GCM-SHA256`