Symmetric NAT Traversal - Revision history

Luc Morissette: Updated title

2020-02-27T22:13:17Z

Updated title

Allyntree: Needs revising edit

2018-04-24T19:21:24Z

Needs revising edit

Cbilodeau: convert link list to table

2018-04-10T17:18:21Z

convert link list to table

Cbilodeau: change configuration link to 3.0

2018-04-09T18:23:11Z

change configuration link to 3.0

Mohamad Badreddine at 16:23, 9 April 2018

2018-04-09T16:23:19Z

Mohamad Badreddine at 15:58, 9 April 2018

2018-04-09T15:58:42Z

Mohamad Badreddine at 15:38, 9 April 2018

2018-04-09T15:38:05Z

Mohamad Badreddine at 15:27, 9 April 2018

2018-04-09T15:27:45Z

Mohamad Badreddine at 17:41, 5 April 2018

2018-04-05T17:41:22Z

Mohamad Badreddine at 17:37, 5 April 2018

2018-04-05T17:37:09Z

@@ Line 1: / Line 1: @@
 === '''''Applies to version(s): v3.0''''' ===
 SBC/Tmedia supports NAT (Network Address Translation) Traversal.
 <br><br>
 == Symmetric NAT Traversal==
-A Network Address Translation (NAT) has many functions such as: firewall, and hiding the client IP. Usually, a NAT limits the number of "opened" IPs/Ports that are allowed to communicate with the internal network and ignores all messages sent to the "closed" IPs/Ports. A correct configuration of TSB/Tmedia allows the messages to reach a client behind a NAT, also known as ''NAT Traversal''. There are two cases of NAT traversal: "Active NAT Traversal" where TSB/Tmedia is behind a NAT and "Passive NAT Traversal" where the client is behind a NAT. A ''Symmetric NAT Traversal'' is the process that sends the replied message back to the same '''public IP/Port''' where the message came from.
+A Network Address Translation (NAT) has many functions such as: firewall, and hiding the client IP. Usually, a NAT limits the number of "opened" IPs/Ports that are allowed to communicate with the internal network and ignores all messages sent to the "closed" IPs/Ports. A correct configuration of TSB/Tmedia allows the messages to reach a client behind a NAT, also known as ''NAT Traversal''. There are two cases of NAT traversal: "Active NAT Traversal" where TSB/Tmedia is behind a NAT and "Passive NAT Traversal" where the client is behind a NAT.
 === TelcoBridges and Active NAT Traversal ===

@@ Line 4: / Line 4: @@
 == Symmetric NAT Traversal==
-A Network Address Translation (NAT) has many functions such as: firewall, hiding the client IP. Usually, a NAT limits the number of "opened" IPs/Ports allowed to communicate with the internal network and ignores all messages sent to the "closed" IPs/Ports. Thus, a right configuration of TSB/Tmedia allows the messages to reach a client behind a NAT, also known as ''NAT Traversal''. There are two cases of NAT traversal: "Active NAT Traversal" where TSB/Tmedia is behind a NAT and "Passive NAT Traversal" where the client is behind a NAT. A ''Symmetric NAT Traversal'' is the process that sends the replied message back to the same '''public IP/Port''' where the message came from.
+A Network Address Translation (NAT) has many functions such as: firewall, and hiding the client IP. Usually, a NAT limits the number of "opened" IPs/Ports that are allowed to communicate with the internal network and ignores all messages sent to the "closed" IPs/Ports. A correct configuration of TSB/Tmedia allows the messages to reach a client behind a NAT, also known as ''NAT Traversal''. There are two cases of NAT traversal: "Active NAT Traversal" where TSB/Tmedia is behind a NAT and "Passive NAT Traversal" where the client is behind a NAT. A ''Symmetric NAT Traversal'' is the process that sends the replied message back to the same '''public IP/Port''' where the message came from.
 === TelcoBridges and Active NAT Traversal ===
@@ Line 13: / Line 13: @@
 === TelcoBridges and Passive NAT Traversal ===
-SBC/Tmedia supports passive NAT Traversal that addresses the need of peer VoIP endpoint having a private network address. This endpoint device is situated behind a NAT device, e.g. Firewall, while the SBC/Tmedia VoIP port has a public IP address. For the passive mode, SBC/Tmedia detects the received RTP packet's source IP address and port. In response, SBC/Tmedia uses this source IP address and port as the packet destination for RTP.
+SBC/Tmedia supports passive NAT Traversal, which addresses the need of peer VoIP endpoint having a private network address. This endpoint device is situated behind a NAT device, e.g. Firewall, while the SBC/Tmedia VoIP port has a public IP address. For the passive mode, SBC/Tmedia detects the received RTP packet's source IP address and port. In response, SBC/Tmedia uses this source IP address and port as the packet destination for RTP.
 This is also called Remote NAT traversal or far-end NAT traversal.
@@ Line 25: / Line 25: @@
 # When a client (Bob) calls someone (Alice) located outside of the internal network, the messages need to get through the NAT which sends the messages to SBC/Tmedia.
 # After their reception, SBC/Tmedia processes and forwards the messages to Alice.
-# When SBC/Tmedia gets a reply from the Alice, it sends the answer back to the NAT.
+# When SBC/Tmedia gets a reply from Alice, it sends the answer back to the NAT.
 # The NAT checks if the received messages from SBC/Tmedia are allowed to be forwarded to Bob.
 <br />
-Bob's IP can only be used in the internal network. When SBC/Tmedia needs to send the Alice's messages to Bob, the message cannot be dispatched directly to the internal IP of Bob or any other IP closed by the NAT. Usually, a replied message is transmitted to the same IP/Port of the NAT where the previous message came from. In this case, SBC/Tmedia sends Alice's messages to the public IP of the NAT. Then, the NAT maps back the message to Bob's internal IP. This is called a ''symmetric response''.
+Bob's IP can only be used in the internal network. When SBC/Tmedia needs to send the Alice's messages to Bob, the message cannot be dispatched directly to the internal IP of Bob or any other IP closed by the NAT. Usually, a replied message is transmitted to the same IP/Port of the NAT from where the previous message originated. In this case, SBC/Tmedia sends Alice's messages to the public IP of the NAT and the NAT maps back the message to Bob's internal IP. This is called a ''symmetric response''.
 <br />
 <br />
@@ Line 40: / Line 40: @@
 A call always begins and ends with a SIP traversal (before and after the media transmission). The media is transmitted through RTP.<br />
-In a User Datagram Protocol (UDP), a SIP traversal through the NAT can be resumed as follows:<br />
+In a User Datagram Protocol (UDP), a SIP traversal through the NAT is shown as follows:<br />
 [[File:Passive_Nat_Traversal_Sip_Sequence_Call.jpg|600px|Figure 2: SIP Traversal Through NAT over UDP]]
 <br />
@@ Line 109: / Line 109: @@
 * RFC 4961 Symmetric RTP / RTP Control Protocol (RTCP)
 <br>

@@ Line 88: / Line 88: @@
 == Configuration ==
-*[[Toolpack:Tsbc_IP_Network_Settings_3.0#NAT|Configure NAT Traversal for version 3.0]]
-*[[Create_NAT_Traversal_B|Configure NAT Traversal for version 2.10]]
-*[[Create_NAT_Traversal_B|Configure NAT Traversal for version 2.9]]
-*[[Create_NAT_Traversal_A|Configure NAT Traversal for version 2.8]]
+{| cellpadding="5" border="1" class="wikitable"
 *[[Web_Portal_Tutorial_Guide_v2.7#SIP Advanced Features|Toolpack v2.7: SIP Advance Features]]
 *[[Web_Portal_Tutorial_Guide_v2.6#SIP Advanced Features|Toolpack v2.6: SIP Advance Features]]
+|}
 == External Sources ==
 * RFC 4961 Symmetric RTP / RTP Control Protocol (RTCP)

@@ Line 88: / Line 88: @@
 == Configuration ==
-*[[Create_NAT_Traversal_C|Configure NAT Traversal for version 3.0]]
+*[[Toolpack:Tsbc_IP_Network_Settings_3.0#NAT|Configure NAT Traversal for version 3.0]]
 *[[Create_NAT_Traversal_B|Configure NAT Traversal for version 2.10]]
 *[[Create_NAT_Traversal_B|Configure NAT Traversal for version 2.9]]

@@ Line 81: / Line 81: @@
     Content-Length: ...
   [Session Description Protocol not shown]
 <br />

@@ Line 2: / Line 2: @@
 SBC/Tmedia supports NAT (Network Address Translation) Traversal.
 <br><br>
-== Typical Use-Case ==
-A Network Address Translation (NAT) has many functions such as: firewall, hiding the client IP. Usually, a NAT limits the number of "opened" IPs/Ports allowed to communicate with the internal network and ignores all messages sent to the "closed" IPs/Ports. A typical call can be described as follow:
+== Network Address Translation Traversal==
 <br>
 [[File:passive_nat_traversal_use_case.jpg|Figure 1: NAT Traversal typical Use-case]]
@@ Line 15: / Line 31: @@
 <br />
 <br />
-== SIP Call Flow Over UDP ==
+==== SIP Call Flow Over UDP ====
 A typical call is made of a flow of messages and is composed of two parts: Session Initiation Protocol (SIP) and Real-Time Transport Protocol (RTP). The SIP part allows:
 * the different connection points (Bob's device, NAT, SBC/Tmedia, Alice's device) to identify themselves;

@@ Line 1: / Line 1: @@
 === '''''Applies to version(s): v3.0''''' ===
-Tmedia supports NAT (Network Address Translation) Traversal.
+SBC/Tmedia supports NAT (Network Address Translation) Traversal.
 <br><br>
 == Typical Use-Case ==
@@ Line 16: / Line 16: @@
 <br />
 == TelcoBridges and Passive NAT Traversal ==
-Tmedia supports passive NAT Traversal that addresses the need of peer VoIP endpoint having a private network address. This endpoint device is situated behind a NAT device, e.g. Firewall, while the Tmedia VoIP port has a public IP address. For the passive mode, TMG detects the received RTP packet's source IP address and port. In response, Tmedia uses this source IP address and port as the packet destination for RTP.
+SBC/Tmedia supports passive NAT Traversal that addresses the need of peer VoIP endpoint having a private network address. This endpoint device is situated behind a NAT device, e.g. Firewall, while the SBC/Tmedia VoIP port has a public IP address. For the passive mode, SBC/Tmedia detects the received RTP packet's source IP address and port. In response, SBC/Tmedia uses this source IP address and port as the packet destination for RTP.
 This is also called Remote NAT traversal or far-end NAT traversal.
@@ Line 22: / Line 22: @@
 == TelcoBridges and Active NAT Traversal ==
-Active NAT traversal means the TMG endpoint is behind a NAT.  The Tmedia unit can advertise a public IP so that the remote device will know where to send the RTP traffic. It can also send the 'a=direction:active' in SIP SDP attribute so that the remote device puts itself in passive mode.
+Active NAT traversal means the SBC/Tmedia endpoint is behind a NAT.  The SBC/Tmedia unit can advertise a public IP so that the remote device will know where to send the RTP traffic. It can also send the 'a=direction:active' in SIP SDP attribute so that the remote device puts itself in passive mode.
 This is also called Local NAT traversal or near-end NAT traversal.
@@ Line 78: / Line 78: @@
 <br />
 == Automatic Detection ==
-Tmedia is able to automatically detect if the client is behind a NAT. To ensure a correct SIP traversal, the automatic detection feature can be activated in the NAP configuration as follows:<br /><br />
+SBC/Tmedia is able to automatically detect if the client is behind a NAT. To ensure a correct SIP traversal, the automatic detection feature can be activated in the NAP configuration as follows:<br /><br />
 [[File:Symetric_NAT_Traversal_SIP_Menu_Automatic.jpg]]

← Older revision		Revision as of 17:37, 5 April 2018
Line 1:		Line 1:
		+	=== '''''Applies to version(s): v3.0''''' ===
	Tmedia supports NAT (Network Address Translation) Traversal.		Tmedia supports NAT (Network Address Translation) Traversal.
	<br><br>		<br><br>