You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/communication-services/concepts/detailed-call-flows.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -72,7 +72,7 @@ For more information about media paths, see [call flows conceptual documentation
72
72
73
73
This call flow topology example depicts customers that use Azure Communication Services from the cloud without any on-premises deployment, such as Azure direct routing. In this topology, traffic to and from Azure Communication Services flows over the internet.
74
74
75
-
:::image type="content" source="./media/call-flows/detailed-flow-general.png" alt-text="Diagram that shows Azure Communication Services call flow topology initiated by a cloudbased user over the internet.":::
75
+
:::image type="content" source="./media/call-flows/detailed-flow-general.png" alt-text="Diagram that shows the Azure Communication Services call flow topology initiated by a cloud-based user over the internet.":::
76
76
77
77
The direction of the arrows in the preceding diagram reflects the direction of the initial communication that affects connectivity at the enterprise perimeters. For UDP media, the first packets might flow in the reverse direction, but these packets might be blocked until packets are flowing in the other direction.
78
78
@@ -133,7 +133,7 @@ This media transmission is bidirectional. The direction indicates which side ini
133
133
134
134
### Customer network to external user (direct media)
135
135
136
-
:::image type="content" source="./media/call-flows/one-to-one-with-extenal.png" alt-text="Diagram that shows a one-to-one call flow between an external user with direct media.":::
136
+
:::image type="content" source="./media/call-flows/one-to-one-with-extenal.png" alt-text="Diagram that shows a one-to-one call flow with an external user with direct media.":::
137
137
138
138
In step 7, Flow 2 (from the customer network to the client's peer over the internet) is selected.
139
139
@@ -157,7 +157,7 @@ This media transmission is bidirectional. The direction of Flow 2 to the remote
157
157
158
158
### VPN user to external user (direct media)
159
159
160
-
:::image type="content" source="./media/call-flows/vpn-user-to-external-user.png" alt-text="Diagram that shows a one-to-one call flow for and external user calling a VPN user with direct media.":::
160
+
:::image type="content" source="./media/call-flows/vpn-user-to-external-user.png" alt-text="Diagram that shows a one-to-one call flow for an external user calling a VPN user with direct media.":::
161
161
162
162
Signaling between the VPN user to the customer network uses Flow 2* and Flow 4 to Azure. However, media bypasses the VPN and is routed by using Flow 6.
0 commit comments