Symmetric NAT Traversal
From TBwiki
(Difference between revisions)
Candy Chan (Talk | contribs) (→Important Reminders) |
Candy Chan (Talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | Tmedia supports symmetric NAT Traversal that addresses the need of | + | 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. |
<br><br> | <br><br> | ||
Revision as of 03:26, 10 July 2012
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.
Contents |
TelcoBridges and NAT Traversal
Tmedia supports 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
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
External Sources
- RFC 4961 Symmetric RTP / RTP Control Protocol (RTCP)
