From: Leif Madsen Date: Fri, 26 Mar 2010 19:17:42 +0000 (+0000) Subject: Merged revisions 255021 via svnmerge from X-Git-Tag: 1.6.1.19-rc1~13 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=ef9708211b6025e869a9d488cd1d84527b996818;p=thirdparty%2Fasterisk.git Merged revisions 255021 via svnmerge from https://origsvn.digium.com/svn/asterisk/trunk ........ r255021 | lmadsen | 2010-03-26 14:07:38 -0500 (Fri, 26 Mar 2010) | 8 lines 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/branches/1.6.1@255026 65c4cc65-6c06-0410-ace0-fbb531ad65f3 --- diff --git a/configs/sip.conf.sample b/configs/sip.conf.sample index c8359e8c57..3d5e995ca1 100644 --- a/configs/sip.conf.sample +++ b/configs/sip.conf.sample @@ -116,8 +116,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 IP address must match the common name (hostname) in the - ; certificate, 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 ;tlscertfile=asterisk.pem ; Certificate file (*.pem only) to use for TLS connections ; default is to look for "asterisk.pem" in current directory