Symmetric NAT Traversal
From TBwiki
(Difference between revisions)
(link to configuration section to web portal tutorial guide) |
(change link to 'sip advanced features' instead of 'sip') |
||
| Line 15: | Line 15: | ||
== Configuration == | == Configuration == | ||
| − | [[Web_Portal_Tutorial_Guide_v2.6#SIP|Toolpack v2.6: SIP Advance Features]] | + | [[Web_Portal_Tutorial_Guide_v2.6#SIP Advanced Features|Toolpack v2.6: SIP Advance Features]] |
== 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 10:25, 14 December 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
Typical Use Case
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)
Configuration
Toolpack v2.6: SIP Advance Features
External Sources
- RFC 4961 Symmetric RTP / RTP Control Protocol (RTCP)
