Changes between Version 1 and Version 2 of get-around-nat-blocked-traffic-filtering

Timestamp:

Feb 10, 2011 12:41:28 PM (14 years ago)

Author:

bennylp

Comment:

--

get-around-nat-blocked-traffic-filtering

@@ -14 +14 @@
 [[BR]]
 
-== Settings ==
-
-=== Use TCP/TLS for SIP Traffic ===
+== Use TCP/TLS for SIP Traffic ==
 
 '''Problems to solve'''
@@ -32 +30 @@
  You will need to configure your proxy to record route so that the proxy is always reachable via TCP (otherwise if the UAS sends a Contact URI without {{{";transport=tcp"}}} parameter, we will send subsequent requests within the dialog via UDP).
 
-=== Disable STUN ===
+== Disable STUN ==
 
 '''Problems to solve'''
@@ -42 +40 @@
 
 '''Solution'''
- For the problems above, you may consider disabling STUN altogether! This may sound like a silly approach but it does work especially if NEITM actively mangles SIP messages to assist NAT traversal (I assume it's because then it will be easier for it to spot the private IP addresses which should be replaced in a SIP message). 
+ For the problems above, you may consider disabling STUN altogether! This may sound like a silly approach but it does work especially if NEITM actively mangles SIP messages to assist NAT traversal (I assume it's because then it will be easier for it to spot the private IP addresses which need mangling in a SIP message). 
 
  In the case where NEITM doesn't assist NAT traversal, your server (in public Internet) must terminate RTP traffic, because RTP traffic won't be able to go end to end between clients. 
 
 
-=== Relay RTP via TURN/TCP ===
+== Relay RTP via TURN/TCP ==
 
 '''Problems to solve'''
@@ -58 +56 @@
 
 
-=== Use Non-standard Ports for VoIP Services ===
+== Use Non-standard Ports for VoIP Services ==
 
 '''Problems to solve'''