Enabling Remote NAT Traversal A: Difference between revisions

No edit summary
mNo edit summary
Line 1: Line 1:
=== '''''Applies to version: v2.7.''''' ===
{{DISPLAYTITLE:Enabling Remote NAT Traversal}}
{{DISPLAYTITLE:Enabling Remote NAT Traversal}}
{| class="wikitable"
|rowspan="2"|This article applies to:


Latest revision as of 09:08, 14 September 2022

This article applies to: Product Version
Tmedia 2.7

To enable Remote NAT Traversal:

1- Select NAPs from the navigation panel

Sip C 0.png

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

  • Click Edit

SipParams 0 1 A.png

3- In the Network Address Translation section:

  • Choose the proper Remote Method.

Nat remote select.png

  • Click Save

The 3 Remote NAT Traversal Methods are described as follows:


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

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