[asterisk-bugs] [Asterisk 0017054]: strange documentation of tlsbindaddr in sip.conf

[Asterisk Bug Tracker]

The following issue has been SUBMITTED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17054 
====================================================================== 
Reported By:                klaus3000
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17054
Category:                   Documentation
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-03-18 09:20 CDT
Last Modified:              2010-03-18 09:20 CDT
====================================================================== 
Summary:                    strange documentation of tlsbindaddr in sip.conf
Description: 
sipc.conf.sample cotains:

;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.

The part starting with "Remember that the DNS ..." is not correct
(multiple IP addresses serving the same domain (e.g. mutliple A records)
work well) and IMO it is very confusing. IMO a better text would be: "For
details how to construct a certificate for SIP see
http://tools.ietf.org/html/draft-ietf-sip-domain-certs"
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-03-18 09:20 klaus3000      New Issue                                    
2010-03-18 09:20 klaus3000      Asterisk Version          => SVN             
2010-03-18 09:20 klaus3000      Regression                => No              
2010-03-18 09:20 klaus3000      SVN Branch (only for SVN checkouts, not tarball
releases) => N/A             
======================================================================