From 39be2603ae1829a1865ca293b6be3dfeb6c1aeef Mon Sep 17 00:00:00 2001 From: lmadsen Date: Tue, 8 Jun 2010 15:23:49 +0000 Subject: 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: http://svn.digium.com/svn/asterisk/branches/1.6.2@268990 f38db490-d61c-443f-a65b-d21fe96a405b --- configs/sip.conf.sample | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/configs/sip.conf.sample b/configs/sip.conf.sample index 291f86e8d..0b099a496 100644 --- 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. -- cgit v1.2.3