Symmetric NAT Traversal
From TBwiki
(Difference between revisions)
Clod Patry (Talk | contribs) (remove the limitation of not being active) |
Clod Patry (Talk | contribs) (added monenclature.) |
||
| Line 4: | Line 4: | ||
== TelcoBridges and Passive NAT Traversal == | == TelcoBridges and Passive NAT Traversal == | ||
Tmedia supports passive NAT Traversal starting from Tmedia release 2.6.31. | Tmedia supports passive NAT Traversal starting from Tmedia release 2.6.31. | ||
| + | |||
| + | Passive NAT traversal means the remote endpoint is behind a NAT. | ||
| + | This is also called Remote NAT traversal or far-end NAT traversal. | ||
<br><br> | <br><br> | ||
Revision as of 14:15, 3 May 2013
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.
Passive NAT traversal means the remote endpoint is behind a NAT.
This is also called Remote NAT traversal or far-end NAT traversal.
TelcoBridges and Active NAT Traversal
Tmedia supports active NAT Traversal starting from Tmedia release 2.7.
Typical Use Case
Important Reminders
- All devices in the path must support symmetric RTP/RTCP: RFC 4961
Configuration
External Sources
- RFC 4961 Symmetric RTP / RTP Control Protocol (RTCP)
