Skip to content

Commit aa3fd6b

Browse files
authored
Update detailed-call-flows.md
1 parent e6ccba7 commit aa3fd6b

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/communication-services/concepts/detailed-call-flows.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -79,7 +79,7 @@ The direction of the arrows in the preceding diagram reflects the direction of t
7979
#### Flow descriptions
8080

8181
* Flow 2 – Represents a flow initiated by a user on the customer network to the internet as a part of the user's Azure Communication Services experience. Examples of these flows include DNS and peer-to-peer media transmission.
82-
* Flow 2 – Represents a flow initiated by a remote mobile Azure Communication Services user with VPN to the customer network.
82+
* Flow 2` – Represents a flow initiated by a remote mobile Azure Communication Services user with VPN to the customer network.
8383
* Flow 3 – Represents a flow initiated by a remote mobile Azure Communication Services user to Azure Communication Services endpoints.
8484
* Flow 4 – Represents a flow initiated by a user on the customer network to Azure Communication Services.
8585
* Flow 5 – Represents a peer-to-peer media flow between one Azure Communication Services user and another within the customer network.
@@ -145,21 +145,21 @@ This media transmission is bidirectional. The direction of Flow 2 to the remote
145145

146146
:::image type="content" source="./media/call-flows/vpn-to-internal-via-relay.png" alt-text="Diagram that shows a one-to-one call flow between an internal user and a VPN user via Azure transport relay.":::
147147

148-
Signaling between the VPN to the customer network uses Flow 2. Signaling between the customer network and Azure uses Flow 4. However, media bypasses the VPN and is routed by using Flows 3 and 4 through Azure Media Relay.
148+
Signaling between the VPN to the customer network uses Flow 2`. Signaling between the customer network and Azure uses Flow 4. However, media bypasses the VPN and is routed by using Flows 3 and 4 through Azure Media Relay.
149149

150150
### VPN user to internal user (direct media)
151151

152152
:::image type="content" source="./media/call-flows/vpn-to-internal-direct-media.png" alt-text="Diagram that shows a one-to-one call flow between an internal user and a VPN user with direct media":::
153153

154-
Signaling between the VPN to the customer network uses Flow 2. Signaling between the customer network and Azure uses Flow 4. However, media bypasses the VPN and is routed by using Flow 2 from the customer network to the internet.
154+
Signaling between the VPN to the customer network uses Flow 2`. Signaling between the customer network and Azure uses Flow 4. However, media bypasses the VPN and is routed by using Flow 2 from the customer network to the internet.
155155

156156
This media transmission is bidirectional. The direction of Flow 2 to the remote mobile user indicates that one side initiates the communication from a connectivity perspective.
157157

158158
### VPN user to external user (direct media)
159159

160160
:::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.":::
161161

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.
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.
163163

164164
This media transmission is bidirectional. The direction of Flow 6 to the remote mobile user indicates that one side initiates the communication from a connectivity perspective.
165165

0 commit comments

Comments
 (0)