Merged revisions 268988 via svnmerge from

https://origsvn.digium.com/svn/asterisk/trunk

........
  r268988 | lmadsen | 2010-06-08 10:23:20 -0500 (Tue, 08 Jun 2010) | 8 lines

  Update note in sip.conf.sample.
  Update note in sip.conf.sample about externip and externhost with STUN.

  (closes issue #16323)
  Reported by: klaus3000
  Patches:
        sip.conf.sample-patch.txt uploaded by klaus3000 (license 65)
........

git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/1.6.2@268990 65c4cc65-6c06-0410-ace0-fbb531ad65f3

diff --git a/configs/sip.conf.sample b/configs/sip.conf.sample
index 291f86e8dbe1644b48541b323aaccea66119d02c..0b099a496eaed5bb6cb975ab0b5cab333cd02068 100644 (file)
--- a/configs/sip.conf.sample
+++ b/configs/sip.conf.sample
@@ -632,10 +632,9 @@ srvlookup=yes                   ; Enable DNS SRV lookups on outbound calls
 ; really need to use STUN.
 ;
 ; NOTE 2: when using "externip" or "externhost", the address part is
-; also used as the external address for media sessions.
-; If you use "stunaddr", STUN queries will be sent to the same server
-; also from media sockets, and this should permit a correct mapping of
-; the port numbers as well.
+; also used as the external address for media sessions. Even if you 
+; use "stunaddr", STUN queries will be sent only from the SIP port,
+; not from media sockets. Thus, the port information in the SDP may be wrong!
 ;
 ; In addition to the above, Asterisk has an additional "nat" parameter to
 ; address NAT-related issues in incoming SIP or media sessions.