Skip to content

Commit 59ee83b

Browse files
committed
Fix note formatting and use Oxford command and 'because'
1 parent da1917a commit 59ee83b

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/communications-gateway/deploy.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -168,10 +168,10 @@ When your resource has been provisioned, you can connect Azure Communications Ga
168168
1. Azure Communications Gateway is preconfigured to support the DigiCert Global Root G2 certificate and the Baltimore CyberTrust Root certificate as root certificate authority (CA) certificates. If the certificate that your network presents to Azure Communications Gateway uses a different root CA certificate, provide your onboarding team with this root CA certificate.
169169
1. The root CA certificate for Azure Communications Gateway's certificate is the DigiCert Global Root G2 certificate. If your network doesn't have this root certificate, download it from https://www.digicert.com/kb/digicert-root-certificates.htm and install it in your network.
170170
1. Configure your infrastructure to meet the call routing requirements described in [Reliability in Azure Communications Gateway](reliability-communications-gateway.md).
171-
* Depending on your network, you might need to configure SBCs, softswitches and access control lists (ACLs).
171+
* Depending on your network, you might need to configure SBCs, softswitches, and access control lists (ACLs).
172172

173-
> [!IMPORTANT]
174-
> When configuring SBCs, firewalls and ACLs ensure that your network can receive traffic from both of the /28 IP ranges provided to you by your onboarding team as the IP addresses used by Azure Communications Gateway can change as a result of maintenance, scaling or in disaster scenarios.
173+
> [!IMPORTANT]
174+
> When configuring SBCs, firewalls and ACLs ensure that your network can receive traffic from both of the /28 IP ranges provided to you by your onboarding team because the IP addresses used by Azure Communications Gateway can change as a result of maintenance, scaling or disaster scenarios.
175175
176176
* Your network needs to send SIP traffic to per-region FQDNs for Azure Communications Gateway. To find these FQDNs:
177177
1. Sign in to the [Azure portal](https://azure.microsoft.com/).

0 commit comments

Comments
 (0)