[svn-commits] mmichelson: trunk r209674 - /trunk/configs/sip.conf.sample

[SVN commits to the Digium repositories]

Author: mmichelson
Date: Fri Jul 31 12:57:00 2009
New Revision: 209674

URL: http://svn.asterisk.org/svn-view/asterisk?view=rev&rev=209674
Log:
Add configuration sample code for previous commit.


Modified:
    trunk/configs/sip.conf.sample

Modified: trunk/configs/sip.conf.sample
URL: http://svn.asterisk.org/svn-view/asterisk/trunk/configs/sip.conf.sample?view=diff&rev=209674&r1=209673&r2=209674
==============================================================================
--- trunk/configs/sip.conf.sample (original)
+++ trunk/configs/sip.conf.sample Fri Jul 31 12:57:00 2009
@@ -100,6 +100,27 @@
                                 ; Set this to your host name or domain name
 udpbindaddr=0.0.0.0             ; IP address to bind UDP listen socket to (0.0.0.0 binds to all)
                                 ; Optionally add a port number, 192.168.1.1:5062 (default is port 5060)
+
+; When a dialog is started with another SIP endpoint, the other endpoint
+; should include an Allow header telling us what SIP methods the endpoint
+; implements. However, some endpoints either do not include an Allow header
+; or lie about what methods they implement. In the former case, Asterisk
+; makes the assumption that the endpoint supports all known SIP methods.
+; If you know that your SIP endpoint does not provide support for a specific
+; method, then you may provide a comma-separated list of methods that your
+; endpoint does not implement in the disallowed_methods option. Note that 
+; if your endpoint is truthful with its Allow header, then there is no need 
+; to set this option. This option may be set in the general section or may
+; be set per endpoint. If this option is set both in the general section and
+; in a peer section, then the peer setting completely overrides the general
+; setting (i.e. the result is *not* the union of the two options).
+;
+; Note also that while Asterisk currently will parse an Allow header to learn
+; what methods an endpoint supports, the only actual use for this currently
+; is for determining if Asterisk may send connected line UPDATE requests. Its
+; use may be expanded in the future.
+;
+; disallowed_methods = UPDATE
 
 ;
 ; Note that the TCP and TLS support for chan_sip is currently considered