SIP NAT

From Yate Documentation
(Difference between revisions)
Jump to: navigation, search
 
(11 intermediate revisions by 2 users not shown)
Line 1: Line 1:
  
What's going in the picture is the fact that YATE uses the RTP stream IP+Port instead of the RTP IP+Port declared in SDP in 200 OK. This small hack allows most of the SIP CLIENTS when Yate is the SERVER to pass the voice over NAT.  
+
In order to solve the common problems with lossing voice when passing through NAT, YATE uses the RTP stream's IP+Port instead of the RTP IP+Port declared in SDP in the ''200 OK'' response.  
  
 +
This small hack allows most of the SIP CLIENTS when Yate is the SERVER to pass the voice over NAT.
 +
 +
A better explanation can be found at: http://freshmeat.net/articles/view/2079/
  
 
[[File:SIP_NAT.png]]
 
[[File:SIP_NAT.png]]
  
  
A better explanation can be found at: http://freshmeat.net/articles/view/2079/
+
'''See also'''
 +
 
 +
* [http://freshmeat.net/articles/view/2079/ NAT traversal for the SIP protocol]
 +
* [[SIP_in_Yate#SIP_with_NAT_in_Yate|SIP with NAT in Yate]]
 +
* [[Telephony]]
 +
 
 +
[[Category:SIP]] [[Category:NAT]] [[Category:Server]]

Latest revision as of 12:04, 4 November 2013

In order to solve the common problems with lossing voice when passing through NAT, YATE uses the RTP stream's IP+Port instead of the RTP IP+Port declared in SDP in the 200 OK response.

This small hack allows most of the SIP CLIENTS when Yate is the SERVER to pass the voice over NAT.

A better explanation can be found at: http://freshmeat.net/articles/view/2079/

SIP NAT.png


See also

Personal tools
Namespaces

Variants
Actions
Preface
Configuration
Administrators
Developers