Update confusing documentation for tlsbindaddr.
Update some confusing documentation for the tlsbindaddr option in sip.conf.sample. Point at a link instead which has better documentation. (closes issue #17054) Reported by: klaus3000 git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@255021 65c4cc65-6c06-0410-ace0-fbb531ad65f3
This commit is contained in:
parent
a165ccc10f
commit
aae9d51510
|
@ -157,10 +157,8 @@ tcpbindaddr=0.0.0.0 ; IP address for TCP server to bind to (0.0.0.0
|
|||
;tlsenable=no ; Enable server for incoming TLS (secure) connections (default is no)
|
||||
;tlsbindaddr=0.0.0.0 ; IP address for TLS server to bind to (0.0.0.0) binds to all interfaces)
|
||||
; Optionally add a port number, 192.168.1.1:5063 (default is port 5061)
|
||||
; Remember that the DNS entry for the common name (server name) in the
|
||||
; certificate must point to the IP address you bind to,
|
||||
; so you don't want to bind a TLS socket to multiple IP addresses.
|
||||
|
||||
; For details how to construct a certificate for SIP see
|
||||
; http://tools.ietf.org/html/draft-ietf-sip-domain-certs
|
||||
|
||||
srvlookup=yes ; Enable DNS SRV lookups on outbound calls
|
||||
; Note: Asterisk only uses the first host
|
||||
|
|
Loading…
Reference in New Issue