Symmetric NAT Traversal
From TBwiki
(Difference between revisions)
Candy Chan (Talk | contribs) (Created page with "Toolpack supports symmetric NAT Traversal which addresses the need of destination VoIP endpoints having private network addresses. This endpoint device is situated behind a NA...") |
Candy Chan (Talk | contribs) |
||
| Line 1: | Line 1: | ||
Toolpack 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. | Toolpack 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. | ||
| + | <br> | ||
== TelcoBridges and NAT Traversal == | == TelcoBridges and NAT Traversal == | ||
Toolpack supports NAT Traversal starting from Toolpack release 2.6.31. Please refer to the TMG-CONTROL version history. | Toolpack supports NAT Traversal starting from Toolpack release 2.6.31. Please refer to the TMG-CONTROL version history. | ||
[http://docs.telcobridges.com/mediawiki/index.php/TMG-CONTROL_Version_2.6 TMG-CONTROL version 2.6] | [http://docs.telcobridges.com/mediawiki/index.php/TMG-CONTROL_Version_2.6 TMG-CONTROL version 2.6] | ||
| + | <br> | ||
== Important Reminders == | == Important Reminders == | ||
* All devices in the path must support symmetric RTP/RTCP | * All devices in the path must support symmetric RTP/RTCP | ||
* RFC 4961 Symmetric RTP / RTP Control Protocol (RTCP) | * RFC 4961 Symmetric RTP / RTP Control Protocol (RTCP) | ||
| + | <br> | ||
== How to enable NAT Traversal == | == How to enable NAT Traversal == | ||
| Line 13: | Line 16: | ||
* 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]] | ||
Revision as of 04:43, 5 July 2012
Toolpack 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.
TelcoBridges and NAT Traversal
Toolpack supports NAT Traversal starting from Toolpack release 2.6.31. Please refer to the TMG-CONTROL version history.
TMG-CONTROL version 2.6
Important Reminders
- All devices in the path must support symmetric RTP/RTCP
- RFC 4961 Symmetric RTP / RTP Control Protocol (RTCP)
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
