provided by Star2Billing S.L.

Hey all!

I've just finished installing A2Billing on my Asterisk server, I go to my
login page .../A2Billing_UI and use the default user/password to login. It
logs me in sucessfully but when I go to use any of the tools (Add
Administrators, Callback, Trunks) it says "Access Denied" can you please
give me more information on how to edit these permissions via SQL?

System Specs:
CentOS 4
MySQL 5
PHP 5
Asterisk2Billing - Version 1.3.3 (Doudou08)

Regards,
Andrew
Multi3VoIP

Hi

What do your apache and PHP logs say?

On centos 5 with recent yum updates, this problem has reared its head:-

http://www.freepbx.org/trac/ticket/2472

Joe

Well according to that post you gave me all I need to do is chown asterisk /var/lib/php/session/ and this may well fix it as I'm also getting a PHP Error "/var/lib/php/session/BUNCHOFRANDOMLETTERS" Permission Denied. Once the SIP server is back up I will try this.

EDIT:
Worked a treat! If anyone else has this issue simply run; chown asterisk /var/lib/php/session/

Thanks!
Andrew

This might have worked, but it is not the right thing to do unless you Apache is running as user:group 'asterisk:....'. And that is not always the case in Linux. In my case, Apache has always been running as user:group "apache:apache".

If you run applications other than asterisk that need to create PHP sessions and that run as a user other than asterisk, it will not work.

Asiby is right.

I was having the same problem and was wondering why the permissions wasn't working in MySql. The owner was already asterisk. So after reading Asiby's post and looking at another machine I updated yesterday, I changed the user to root and the group to apache for "/var/lib/php/session."

It now works fine. (user=root, group=apache)

This is PIAF 1.2, CentOs 5.2.

I hope this will help someone.

RobinA.

There is another thing among many that people should be aware of. Usually, out of the box, Asterisk runs as root. And it is mostly dangerous to run any application as root, specially daemons that interact with the outside world. The real problem starts when a malicious surfer breaks through your security. He or she will instantly have root access and will have the potential to do some damage. For each application, it is always a good idea to create a user that has no login access (using /bin/false or /sbin/nologin shell) and use that user account and group for only for running that application.

In our case, we have Asterisk, MySQL, Apache and A2B. Usually, Apache and MySQL are well configured. I personally don't like the fact that Apache would run with a user called Asterisk. It may be confusing. Parts of A2B will run as asterisk (the AGI) and other parts will run as apache (the GUI). Asterisk can run as asterisk.

Oh, I almost forgot. You may notice sometimes that the asterisk files may have been chowned to asterisk:asterisk. That does not mean that asterisk itself is running as asterisk:asterisk.

Cheers

Thanks for you very informative input. I'll personally take not of that and make the necessary changes the best that I can. I hope other newbees are taking note.

RobinA.

Hi Robin

If you, or anyone else are using PiaF as a base, then update-scripts, followed by update-fixes should fix the problem for you. The problem was caused during a yum update.

Joe