[asterisk-commits] oej: trunk r168711 - /trunk/configs/sip.conf.sample

[SVN commits to the Asterisk project]

Author: oej
Date: Thu Jan 15 11:55:53 2009
New Revision: 168711

URL: http://svn.digium.com/svn-view/asterisk?view=rev&rev=168711
Log:
Clarify some misunderstandings and make it even more clear that you can refer to a peer
in the register= line.


Modified:
    trunk/configs/sip.conf.sample

Modified: trunk/configs/sip.conf.sample
URL: http://svn.digium.com/svn-view/asterisk/trunk/configs/sip.conf.sample?view=diff&rev=168711&r1=168710&r2=168711
==============================================================================
--- trunk/configs/sip.conf.sample (original)
+++ trunk/configs/sip.conf.sample Thu Jan 15 11:55:53 2009
@@ -413,16 +413,20 @@
 ;----------------------------------------- OUTBOUND SIP REGISTRATIONS  ------------------------
 ; Asterisk can register as a SIP user agent to a SIP proxy (provider)
 ; Format for the register statement is:
-;       register => [transport://]user[:secret[:authuser]]@host[:port][/extension][~expiry]
+;       register => [transport://]user[:secret[:authuser]]@domain[:port][/extension][~expiry]
 ;
 ; 
+;
+; domain is either 
+;	- domain in DNS
+; 	- host name in DNS
+;	- the name of a peer defined below or in realtime
+; The domain is where you register your username, so your SIP uri you are registering to 
+; is username at domain
 ;
 ; If no extension is given, the 's' extension is used. The extension needs to
 ; be defined in extensions.conf to be able to accept calls from this SIP proxy
 ; (provider).
-;
-; host is either a host name defined in DNS or the name of a section defined
-; below.
 ;
 ; A similar effect can be achieved by adding a "callbackextension" option in a peer section.
 ; this is equivalent to having the following line in the general section: