[asterisk-bugs] [Asterisk 0012350]: the Authenticate app does not authenticate my second call

noreply at bugs.digium.com noreply at bugs.digium.com
Mon Apr 7 12:18:55 CDT 2008


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12350 
====================================================================== 
Reported By:                elandivar
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12350
Category:                   Applications/app_authenticate
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.17 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             04-01-2008 19:35 CDT
Last Modified:              04-07-2008 12:18 CDT
====================================================================== 
Summary:                    the Authenticate app does not authenticate my second
call
Description: 
Hello Folks,

I have a very weird issue here when I try to authenticate my calls with a
pinset. This is the scenario:

I place a call from an extension to an outside number, the system asks for
a pin, i dial the pin, the call is authenticated succesfuly and everything
ok.

If I put this call on hold and call another outside number, the system ask
for a pin, i dial the right pin but the system says that the password is
incorrect.

I'm entering the password correctly. To verify this i modified some lines
of the app_authenticate.c file to print the password i'm entering.

This is the block of code I modified:

        /* Start asking for password */
        prompt = "agent-pass";
        for (retries = 0; retries < 3; retries++) {
                res = ast_app_getdata(chan, prompt, passwd, maxdigits,
0);
                if (res < 0)
                        break;
                res = 0;
                /* here is my line to print the password */
                ast_log(LOG_WARNING, "XXXXXXXXXXXXXXXXX: The password is
%s\n", passwd);

The first time i can see my password in the asterisk log file but the
second time the password is empty. I have tried dozens of times.

I'm using freePBX (which comes with Elastix). So, the dialplan logic to
handle the authentication is very simple:

[macro-pinsets]
include => macro-pinsets-custom
exten => s,1,GotoIf(${ARG2} = 1?cdr,1)
exten => s,n,Authenticate(/etc/asterisk/pinset_${ARG1},)
exten => cdr,1,Authenticate(/etc/asterisk/pinset_${ARG1},a)

Thanks a lot for any help. 
====================================================================== 

---------------------------------------------------------------------- 
 elandivar - 04-07-08 12:18  
---------------------------------------------------------------------- 
Hello Folks,

I finally could access the customer equipment and notice that the
technology is SIP instead of IAX, configured with rfc2833. I also tested
with "inbound" but it does not solve the problem.

Also, we tested with an IAX extension to be sure and the problem was not
present. So, maybe it is related to the SIP technology. I hope this helps.

I'm attaching CLI output and the full log excerpts for two scenarios:

1) The IAX extension (the test was succesful)
      - authenticate.cli.success.txt
      - authenticate.var.log.asterisk.full.success.txt
2) The SIP extension (the test failed)
      - authenticate.cli.failed.txt
      - authenticate.var.log.asterisk.full.failed.txt 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
04-07-08 12:18  elandivar      Note Added: 0085085                          
======================================================================




More information about the asterisk-bugs mailing list