Merged revisions 282269 via svnmerge from

https://origsvn.digium.com/svn/asterisk/branches/1.8

........
  r282269 | dvossel | 2010-08-13 15:03:56 -0500 (Fri, 13 Aug 2010) | 4 lines
  
  res_stun_monitor for monitoring network changes behind a NAT device
  
  Review: https://reviewboard.asterisk.org/r/854
........


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

3 files changed, 41 insertions, 0 deletions

diff --git a/configs/iax.conf.sample b/configs/iax.conf.sample
index b516d4b85..73ae78afb 100644
--- a/configs/iax.conf.sample
+++ b/configs/iax.conf.sample
@@ -244,6 +244,15 @@ forcejitterbuffer=no
 ;
 ;register => FWDNumber:passwd@iax.fwdnet.net
 ;
+; Through the use of the res_stun_monitor module, Asterisk has the ability to detect when the
+; perceived external network address has changed.  When the stun_monitor is installed and
+; configured, chan_iax will renew all outbound registrations when the monitor detects any sort
+; of network change has occurred. By default this option is enabled, but only takes effect once
+; res_stun_monitor is configured.  If res_stun_monitor is enabled and you wish to not
+; generate all outbound registrations on a network change, use the option below to disable
+; this feature.
+;
+; subscribe_network_change_event = yes ; on by default
 ;
 ; You can disable authentication debugging to reduce the amount of
 ; debugging traffic.
diff --git a/configs/res_stun_monitor.conf.sample b/configs/res_stun_monitor.conf.sample
new file mode 100644
index 000000000..9237799c5
--- /dev/null
+++ b/configs/res_stun_monitor.conf.sample
@@ -0,0 +1,22 @@
+;
+; Configuration file for the res_stun_monitor module
+;
+; The res_stun_monitor module sends STUN requests to a configured STUN server
+; periodically.  If the monitor detects a change in the external ip or port
+; provided by the STUN server an event is sent out internally within Asterisk
+; to alert all listeners to that event of the change.
+
+; The current default listeners for the netork change event include chan_sip
+; and chan_iax.  Both of these channel drivers by default react to this event
+; by renewing all outbound registrations.  This allows the endpoints Asterisk
+; is registering with to become aware of the address change and know the new
+; location.
+;
+[general]
+;
+; ---- STUN Server configuration ---
+;  Setting the 'stunaddr' option to a valid address enables the stun monitor.
+;
+; stunaddr = mystunserver.com ; address of the stun server to query.
+; stunrefresh = 30     ; number of seconds between stun refreshes. default is 30
+;
diff --git a/configs/sip.conf.sample b/configs/sip.conf.sample
index 44ef9aa1a..244e22b6c 100644
--- a/configs/sip.conf.sample
+++ b/configs/sip.conf.sample
@@ -783,6 +783,16 @@ srvlookup=yes                   ; Enable DNS SRV lookups on outbound calls
 ; can not be set per-user or per-peer.
 ;
 ; media_address = 172.16.42.1
+;
+; Through the use of the res_stun_monitor module, Asterisk has the ability to detect when the
+; perceived external network address has changed.  When the stun_monitor is installed and
+; configured, chan_sip will renew all outbound registrations when the monitor detects any sort
+; of network change has occurred. By default this option is enabled, but only takes effect once
+; res_stun_monitor is configured.  If res_stun_monitor is enabled and you wish to not
+; generate all outbound registrations on a network change, use the option below to disable
+; this feature.
+;
+; subscribe_network_change_event = yes ; on by default
 
 ;----------------------------------- MEDIA HANDLING --------------------------------
 ; By default, Asterisk tries to re-invite media streams to an optimal path. If there's