diff options
| author | mmichelson <mmichelson@f38db490-d61c-443f-a65b-d21fe96a405b> | 2009-07-31 17:57:00 +0000 |
|---|---|---|
| committer | mmichelson <mmichelson@f38db490-d61c-443f-a65b-d21fe96a405b> | 2009-07-31 17:57:00 +0000 |
| commit | f5274e741bbd7a5b0fdcb20aec17e22071026af2 (patch) | |
| tree | c256a4d6d484c0ed435207feda8ebdea4118757e /configs/sip.conf.sample | |
| parent | 9366a4f77431c1f5e1ebc9843a0e136412302ca1 (diff) | |
Add configuration sample code for previous commit.
git-svn-id: http://svn.digium.com/svn/asterisk/trunk@209674 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'configs/sip.conf.sample')
| -rw-r--r-- | configs/sip.conf.sample | 21 |
1 files changed, 21 insertions, 0 deletions
diff --git a/configs/sip.conf.sample b/configs/sip.conf.sample index 3aadc633d..fef5ef8f4 100644 --- a/configs/sip.conf.sample +++ b/configs/sip.conf.sample @@ -101,6 +101,27 @@ allowoverlap=no ; Disable overlap dialing support. (Default is y 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 ; experimental. Since it is new, all of the related configuration options are |