Changes between Version 1 and Version 2 of sound-problems/Getting_Around_Nat

Timestamp:

Jul 13, 2015 6:54:15 AM (9 years ago)

Author:

ming

Comment:

--

sound-problems/Getting_Around_Nat

@@ -3 +3 @@
 If [wiki:audio-check-rx-rtp no RTP packet is received] (or [wiki:audio-problem-local-no-audio you can't any hear audio]), perhaps it's because of the NAT device is blocking the incoming RTP packets. 
 
-== Use STUN ==
+== Use STUN and/or TURN and/or ICE ==
 One of the obvious reason why no incoming packet is received is because the application sends private IP address as its RTP address. This can be verified by looking at the SDP {{{c=}}} line that is sent by the application. 
 
-If the SDP {{{c=}}} line contains private address, then probably you need to use STUN. You can enable STUN support in ''pjsua'' by using '''{{{--stun-srv}}}''' option from the command line. For example:
+If the SDP {{{c=}}} line contains private address, then probably you need to use STUN or TURN. You can enable STUN support in ''pjsua'' by using '''{{{--stun-srv}}}''' option from the command line. For example:
 {{{
- $ ./pjsua --use-stun stun.pjsip.org
+ $ ./pjsua --stun-srv stun.pjsip.org
 }}}
 
-
+Another example to use TURN and ICE:
+{{{
+ $ ./pjsua --use-ice --use-turn --turn-srv turn.pjsip.org --turn-user [username] --turn-passwd ***
+}}}
 
 == Disabling VAD ==