Thirdlane.com logo

You don't have permission to access this page

Posted by rokio on Tue, 07/26/2011
Forums
Thirdlane platform General Questions

We have this problem for months but it seems impossible to fix for support or forum readers..., are we the only one? did I miss something? we use PBX Manager 6.1.1.10

We have a ongoing problem that our users cannot listen to the recorded calls via web (root admin, tenant admin, and enduser). we can off course email the wav files, but listening from the web gives a "You don't have permission to access this page".

-The records are generated by extensions that are forwarded in the end user interface by "call forwarding" "/ find me follow me" to an external number.

-on the server, all files have the same file rights. 644 asterisk asterisk

-the only thing that is different is that i CAN ALWAYS listen to the Anonymous calls
but NEVER to calls with a number

the call with a CallerID do NEVER work (You don't have permission to access this page)

https://sipserverIP:10000/asterisk/get_file.cgi?path=/var/spool/asteris…

But the Anonymous DO ALWAYS work:

https://sipserverIP:10000/asterisk/get_file.cgi?path=/var/spool/asteris…

the only difference I can see is that we can listen to Anonymous calls. I tried with firefox, safari, chrome, all same result.

anyone?

Rob

Submitted by eeman on Tue, 07/26/2011 Permalink

I think it has something to do with the perl script and the file name of the wav recording. At some point we decided that the ":" in the filenames for time was creating a lot of problems with other scripts and shell commands, its a special character that the command interpreter tries to parse on. I happen to have a couple recordings before we made this switch and those will play but the the ones with the harmless dashes gives this error. Try taking the file that wont play and rename it but .. try just removing the '+' to see if it plays then. If so then the likely cause is not enough error handling in the filename string.

Submitted by rokio on Tue, 07/26/2011 Permalink

you are right! when I renamed the file (remove the +) it worked perfectly.

I just reconfigured our incoming trunks to send the callerid in 00.... instead of +.... format, and it all works

thanks,

rob

Submitted by rsa on Thu, 11/10/2011 Permalink

Is there any update on this bug. We have a lot of recorded calls with the + in them and i could change them all with a script and change the incoming trunk. Only i would prefer to be able to use the +