Summary:	ASTERISK-16385: Ignoring SIPS requests
Reporter:	Olle Johansson (oej)	Labels:
Date Opened:	2010-07-16 07:50:37	Date Closed:
Priority:	Minor	Regression?	No
Status:	Open/New	Components:	Channels/chan_sip/TCP-TLS
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
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.
Comments:	By: Olle Johansson (oej) 2013-04-24 11:27:34.038-0500 Wow. Three years without any attention. By: Sean Bright (seanbright) 2017-12-13 08:12:54.766-0600 That is incorrect. It has been -7.5- 9 years.