<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>24 maj 2013 kl. 23:39 skrev Kevin Harwell <<a href="mailto:reviewboard@asterisk.org">reviewboard@asterisk.org</a>>:</div><br class="Apple-interchange-newline"><blockquote type="cite"><pre style="font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255); margin: 0px; padding: 0px; white-space: pre-wrap; word-wrap: break-word; ">Adds support for 'alwaysauthreject' to the new SIP channel driver. When the 'alwaysauthreject' option is set to 'yes' (default) and no matching endpoint is found for the incoming request, after challenging, Asterisk will respond with a 401 Unauthorized regardless of the reason it rejects the request.
</pre><br class="Apple-interchange-newline"></blockquote></div>Alwaysauthreject was a fix for a bug that existed in asterisk. We had to keep the old behaviour being afraid of breaking stuff out there.<div><br></div><div>Why are we replicating the bug and the fix in a *new* channel driver? It doesn't make much sense. We have no old versions of this channel driver that's broken in production anywhere.</div><div><br></div><div>Are there any use cases for discovery of sip accounts by getting a 404 for non-existing accounts?</div><div><br></div><div><br></div><div>/O</div></body></html>