Symmetric NAT Traversal

From TBwiki
(Difference between revisions)
Jump to: navigation, search
(TelcoBridges and NAT Traversal)
Line 1: Line 1:
Tmedia supports symmetric NAT Traversal that addresses the need of peer VoIP endpoint having a private network address. This endpoint device is situated behind a NAT (Network Address Translation) device, e.g. Firewall, while the Tmedia VoIP port has a public IP address. For this "passive NAT 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.  
+
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 (Network Address Translation) 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.  
 
<br><br>
 
<br><br>
  
== TelcoBridges and NAT Traversal ==
+
== TelcoBridges and Passive NAT Traversal ==
 
Tmedia supports passive NAT Traversal starting from Tmedia release 2.6.31. Please refer to [http://docs.telcobridges.com/mediawiki/index.php/TMG-CONTROL_Version_2.6 TMG-CONTROL version 2.6]
 
Tmedia supports passive NAT Traversal starting from Tmedia release 2.6.31. Please refer to [http://docs.telcobridges.com/mediawiki/index.php/TMG-CONTROL_Version_2.6 TMG-CONTROL version 2.6]
 
<br><br>
 
<br><br>
Line 8: Line 8:
 
== Important Reminders ==
 
== Important Reminders ==
 
* All devices in the path must support symmetric RTP/RTCP: RFC 4961
 
* All devices in the path must support symmetric RTP/RTCP: RFC 4961
* Currently, TMedia does not support advertising itself behind a NAT
+
* Currently, TMedia does not support advertising itself behind a NAT (Active NAT Traversal)
 
<br>
 
<br>
  

Revision as of 17:20, 20 August 2012

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 (Network Address Translation) 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.

Contents

TelcoBridges and Passive NAT Traversal

Tmedia supports passive NAT Traversal starting from Tmedia release 2.6.31. Please refer to TMG-CONTROL version 2.6

Important Reminders

  • All devices in the path must support symmetric RTP/RTCP: RFC 4961
  • Currently, TMedia does not support advertising itself behind a NAT (Active NAT Traversal)


How to enable passive NAT Traversal

  • This feature is to be enabled per SIP NAP
  • Go to NAP -> Edit -> NAT traversal -> Check "Enable"
  • Save and activate your configuration


Nat traversal.jpg

External Sources

  • RFC 4961 Symmetric RTP / RTP Control Protocol (RTCP)


Personal tools