Symmetric NAT Traversal
From TBwiki
(Difference between revisions)
Candy Chan (Talk | contribs) |
Candy Chan (Talk | contribs) |
||
| Line 14: | Line 14: | ||
* Go to NAP -> Edit -> NAT traversal -> Check "Enable" | * Go to NAP -> Edit -> NAT traversal -> Check "Enable" | ||
* Save and activate your configuration | * Save and activate your configuration | ||
| + | <br> | ||
[[File:nat_traversal.jpg]] | [[File:nat_traversal.jpg]] | ||
| − | <br> | + | <br><br> |
| − | <br> | + | |
== External Sources == | == External Sources == | ||
* RFC 4961 Symmetric RTP / RTP Control Protocol (RTCP) | * RFC 4961 Symmetric RTP / RTP Control Protocol (RTCP) | ||
<br> | <br> | ||
Revision as of 23:17, 5 July 2012
Tmedia supports symmetric NAT Traversal which addresses the need of destination VoIP endpoints having private network addresses. This endpoint device is situated behind a NAT (Network Address Translation) device. e.g. Firewalls. TMG detect changes from the received RTP packet's source IP address and port. In response, TMG 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
How to enable 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)
