On Sun, Feb 6, 2011 at 5:22 PM, Simon J Mudd
<sjmudd@pobox.com> wrote:
I've been looking at trying to configure tighter controls for extensions that register.
Doing so made me trigger this error message (adjusted slightly):
2011-02-07 00:07:51.343303 [WARNING] sofia_reg.c:1247 SIP auth challenge (REGISTER) on sofia profile 'internal' for [1000@sip.example.com] from ip 192.168.4.99
2011-02-07 00:07:51.343303 [WARNING] sofia_reg.c:1247 SIP auth challenge (REGISTER) on sofia profile 'internal' for [1000@sip.example.com] from ip 192.168.4.99
Looking at the message it is not clear if the SIP authentication has succeeded or failed.
Judging by the code it seems this is meant to represent a SIP auth failure. If so should
the code not be patched as shown?
No. This is just saying that there was a challenge, not that there was a failure. There is already a failure detection routine. To test it, setup a SIP client with an incorrect password. You'll see two log lines like this:
2011-02-07 12:23:28.490029 [WARNING] sofia_reg.c:1247 SIP auth challenge (REGISTER) on sofia profile 'internal' for [1002@10.10.16.161] from ip 10.10.16.161
2011-02-07 12:23:29.035950 [WARNING] sofia_reg.c:1247 SIP auth challenge (REGISTER) on sofia profile 'internal' for [1002@10.10.16.161] from ip 10.10.16.161
2011-02-07 12:23:29.240695 [WARNING] sofia_reg.c:1205 SIP auth failure (REGISTER) on sofia profile 'internal' for [1002@10.10.16.161] from ip 10.10.16.161
This allows you to differentiate between the mere fact that an auth challenge was sent to the SIP client vs. the SIP client failing to auth. (Someone asked for that differentiation a while back - I don't know who or why...)
-MC