[asterisk-bugs] [Asterisk 0017664]: Ignoring SIPS requests

Asterisk Bug Tracker noreply at bugs.digium.com
Fri Jul 16 10:52:10 CDT 2010


The following issue has been UPDATED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17664 
====================================================================== 
Reported By:                oej
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17664
Category:                   Channels/chan_sip/TCP-TLS
Reproducibility:            have not tried
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
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-07-16 07:50 CDT
Last Modified:              2010-07-16 10:52 CDT
====================================================================== 
Summary:                    Ignoring SIPS requests
Description: 
We have many cases in the SIP channel where SIP and SIPS requests are
handled in the same way. One good example is in the REFER handling:

14147                 if (!strncasecmp(referred_by_uri, "sip:", 4)) {
14148                         referred_by_uri += 4;           /* Skip sip:
*/
14149                 } else if (!strncasecmp(referred_by_uri, "sips:",
5)) {
14150                         referred_by_uri += 5;           /* Skip
sips: */
14151                 } else {

In this case, if the header is SIPS: this needs to get back into the
dialplan, since we have a request for a secure channel regardless of
technology. How the admin handles this is of course up to his/hers
configuration, but just stripping the information should be regarded as a
BUG.
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-07-16 10:52 lmadsen        Description Updated                          
======================================================================




More information about the asterisk-bugs mailing list