Authenticate() bad password processing strategies

Is there a way to catch a failed authentication besides using the “j” and n+101 method?

I don’t have priorityjumping enabled in extensions.conf and I would like to avoid doing that, if possible.

Perhaps there is an undocumented status variable passed by the Authenticate() funtion?

Running asterisk


There are only 161 lines of code in app_authenticate.c (excluding the documentation, but including other comments and blank lines). None of them manipulates channel variables.

Hi wouldnt take much to use Read() and the Astdb to make a authentication system that will set variables and report wrong passwords, We use this method for accessing conference rooms.

Definitely going the route of Read() and db entries.

Just for laughs, I typed

and there wasn’t even a ‘j’ option listed.