Enabling Remote NAT Traversal C - Revision history

Allyntree at 16:49, 22 June 2024

2024-06-22T16:49:43Z

← Older revision		Revision as of 12:49, 22 June 2024
Line 7:		Line 7:
	\|-		\|-
	\|Tmedia		\|Tmedia
	\|2.9, 2~~.10~~, 3.0, 3.2		\|3.0, 3.2, 3.3
	\|-		\|-
	\|SBC		\|SBC
	\|3.0, 3.1		\|3.1, 3.3
	\|}		\|}

Allyntree at 18:32, 25 November 2020

2020-11-25T18:32:21Z

← Older revision		Revision as of 14:32, 25 November 2020
Line 1:		Line 1:
	~~=== '''''Applies to version: 2.9, 2.10, 3.0, 3.1, 3.2''''' ===~~
	{{DISPLAYTITLE:Enabling Remote NAT Traversal}}		{{DISPLAYTITLE:Enabling Remote NAT Traversal}}
			{\| class="wikitable"
			\|-
			\|rowspan="3"\|This article applies to:
			\|'''Product'''
			\|'''Version'''
			\|-
			\|Tmedia
			\|2.9, 2.10, 3.0, 3.2
			\|-
			\|SBC
			\|3.0, 3.1
			\|}

	~~<br>~~
	To enable Remote NAT Traversal:		To enable Remote NAT Traversal:

Allyntree at 17:27, 18 August 2020

2020-08-18T17:27:50Z

← Older revision		Revision as of 13:27, 18 August 2020
Line 1:		Line 1:
	=== '''''Applies to version: v2.9, v2.10, v3.0, v3.1''''' ===		=== '''''Applies to version: 2.9, 2.10, 3.0, 3.1, 3.2''''' ===
	{{DISPLAYTITLE:Enabling Remote NAT Traversal}}		{{DISPLAYTITLE:Enabling Remote NAT Traversal}}

Allyntree at 14:09, 1 May 2019

2019-05-01T14:09:28Z

← Older revision		Revision as of 10:09, 1 May 2019
Line 1:		Line 1:
	=== '''''Applies to version: v2.9, v2.10, v3.0''''' ===		=== '''''Applies to version: v2.9, v2.10, v3.0, v3.1''''' ===
	{{DISPLAYTITLE:Enabling Remote NAT Traversal}}		{{DISPLAYTITLE:Enabling Remote NAT Traversal}}

Allyntree at 19:43, 14 November 2017

2017-11-14T19:43:57Z

← Older revision		Revision as of 15:43, 14 November 2017
Line 1:		Line 1:
	=== '''''Applies to version: v2.9, v2.10''''' ===		=== '''''Applies to version: v2.9, v2.10, v3.0''''' ===
	{{DISPLAYTITLE:Enabling Remote NAT Traversal}}		{{DISPLAYTITLE:Enabling Remote NAT Traversal}}

Allyntree at 13:25, 27 October 2016

2016-10-27T13:25:08Z

← Older revision		Revision as of 09:25, 27 October 2016
Line 1:		Line 1:
	=== '''''Applies to version: v2.9.''''' ===		=== '''''Applies to version: v2.9, v2.10''''' ===
	{{DISPLAYTITLE:Enabling Remote NAT Traversal}}		{{DISPLAYTITLE:Enabling Remote NAT Traversal}}

Allyntree: Added northbound interface data

2016-01-01T15:27:10Z

Added northbound interface data

← Older revision		Revision as of 11:27, 1 January 2016
Line 43:		Line 43:
	'''Path'''		'''Path'''
	<pre>		<pre>
			/configurations/@[configuration_name]/naps/@[nap_name]/sip_cfg/network_address_translation
	</pre>		</pre>

	'''Parameters (text)'''		'''Parameters (text)'''
	<pre>		<pre>
			/configurations/@[configuration_name]/naps/@[nap_name]/sip_cfg/network_address_translation
			local_method = ""
			remote_method = "None"
	</pre>		</pre>

	'''Parameters (json)'''		'''Parameters (json)'''
	<pre>		<pre>
			{
			"network_address_translation" : {
			"local_method" : "",
			"remote_method" : "None"
			}
			}
			}
	</pre>		</pre>
	</div>		</div>

Allyntree at 19:08, 30 November 2015

2015-11-30T19:08:27Z

← Older revision		Revision as of 15:08, 30 November 2015
Line 38:		Line 38:
	The TMG will look in the SDP to find an attribute direction:active. If it finds this attribute, the TMG will act exactly as the “Force Passive Mode” method. In fact, this a dynamic way to enable the “Force Passive Mode”.		The TMG will look in the SDP to find an attribute direction:active. If it finds this attribute, the TMG will act exactly as the “Force Passive Mode” method. In fact, this a dynamic way to enable the “Force Passive Mode”.

	~~== Related actions ==~~
	~~[[Symmetric_NAT_Traversal\|Symmetric NAT traversal]]~~

	<div class="mw-collapsible mw-collapsed" data-collapsetext="Northbound Interface" data-expandtext="Northbound Interface" style="width: 400px;">		<div class="mw-collapsible mw-collapsed" data-collapsetext="Northbound Interface" data-expandtext="Northbound Interface" style="width: 400px;">
Line 55:		Line 53:
	</pre>		</pre>
	</div>		</div>


			== Related actions ==
			[[Symmetric_NAT_Traversal\|Symmetric NAT traversal]]

Allyntree: Created page with "=== '''''Applies to version: v2.9.''''' === {{DISPLAYTITLE:Enabling Remote NAT Traversal}}
To enable Remote NAT Traversal: 1- Select '''NAPs''' from the navigation pane..."

2015-11-30T19:07:40Z

Created page with "=== '''''Applies to version: v2.9.''''' === {{DISPLAYTITLE:Enabling Remote NAT Traversal}} <br> To enable Remote NAT Traversal: 1- Select '''NAPs''' from the navigation pane..."

New page

=== '''''Applies to version: v2.9.''''' ===
{{DISPLAYTITLE:Enabling Remote NAT Traversal}}

<br>
To enable Remote NAT Traversal:

1- Select '''NAPs''' from the navigation panel

[[Image:EnableRemoteNatTraversal_0 .png]]

2- Select a SIP NAP from the '''Network Access Point List'''

[[Image:EnableRemoteNatTraversal_1.png]]

3- In the '''Network Address Translation''' section:
* Choose the desired "remote method".
* Click '''Save'''

[[Image:EnableRemoteNatTraversal_2.png]]

The 3 Remote NAT Traversal Methods are described as follows:

'''No NAT'''

The local endpoint is NOT behind a NAT. This means, your local endpoint has a Public IP address, which is globally routable on the Internet. For further information, refer to http://en.wikipedia.org/wiki/Private_network.

'''Force Passive Mode'''

The TMG will NOT send any RTP packets and will wait for the first RTP packet. The remote endpoint will send the first RTP packet. It will ignore the IP address/port sent in the SDP (in the SIP '200 OK' message)and use the IP address/port from where it received the RTP packet.

Note: If the remote endpoint is also set as passive, this method will not work because both sides will wait for the first incoming RTP packet.

'''Parse Direction Attribute'''

The TMG will look in the SDP to find an attribute direction:active. If it finds this attribute, the TMG will act exactly as the “Force Passive Mode” method. In fact, this a dynamic way to enable the “Force Passive Mode”.

== Related actions ==
[[Symmetric_NAT_Traversal|Symmetric NAT traversal]]

<div class="mw-collapsible mw-collapsed" data-collapsetext="Northbound Interface" data-expandtext="Northbound Interface" style="width: 400px;">

'''Path'''
<pre>
</pre>

'''Parameters (text)'''
<pre>
</pre>

'''Parameters (json)'''
<pre>
</pre>
</div>