| Summary: | ASTERISK-21223: Asterisk no longer responds to SIP REGISTER's that don't contain an Authorization | ||
| Reporter: | Sverre G (sverre) | Labels: | |
| Date Opened: | 2013-03-07 23:50:39.000-0600 | Date Closed: | 2013-03-07 23:59:01.000-0600 |
| Priority: | Minor | Regression? | |
| Status: | Closed/Complete | Components: | Channels/chan_sip/Registration |
| Versions: | 11.2.1 | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | CentOS 6.3 | Attachments: | ( 0) Screen_Shot_2013-03-08_at_4.34.05_PM.png |
| Description: | On previous versions of Asterisk, e.g. 1.4.22, SIP clients (in particular some versions of firmware on the Cisco 7960) would attempt to register without any authorization header, causing Asterisk to reply with 401 Unauthorized, causing the SIP client to attempt to register again (but this time with an authorization header).
In the current version of Asterisk (11.2.1), Asterisk silently ignores clients that do not provide an authorization header, essentially not allowing these clients to register as they never receive the nonce that they need to continue. See screenshots for side-by-side comparison of packets against Asterisk 1.4.22 versus Asterisk 11.2.1. | ||
| Comments: | By: Sverre G (sverre) 2013-03-07 23:53:14.227-0600 Asterisk 1.4.22 on the left showing sucessful registration, asterisk 11.2.1 showing ignored registration attempts. By: Sverre G (sverre) 2013-03-07 23:59:01.444-0600 While documenting I found a REGISTER without an Authorization that Asterisk did reply to, so it's something else that's causing it. | ||
