search

alkali147 / fbilling

Accounting and billing Application for FreePBX
BSD 2-Clause "Simplified" License
15 stars 22 forks source link

fbilling not logging #25

Open wasbak opened 8 years ago

wasbak commented 8 years ago

System info:

Centos 5 freepbx 2.11.0.25 Asterisk 11.10

Installed fbiller as per instructions. Veriffy script shows all components as ok but also gives notice:

Checking FBilling configuration file... [OK] Possible missing configuration in /etc/asterisk/fbilling.conf

fbilling configuration looks correct the log file exists and permissions on log files are correct yet no logging occurs either in console or log file. (password and host ip changed for security reasons):

[general] ; specify where fbilling will log its activities ; 0 - no logging, 1 - log to only console, ; 2 - log to only log file, 4 - log both to console and log file log_level = 2 ; you can specify any location, just make sure file and parent directories are accessible and writebale ; by user asterisk and group asterisk log_location = /var/log/asterisk/fbilling.log

[database] ; database settings that AGI script will use for connecting to mysql database username = fbiller password = xxxxxxxx database = fbiller host = 12.34.56.78 port = 3306

fbilling doesn't pass calls on to the trunk but we currently have no way of seeing what the problem is.

alkali147 commented 8 years ago

Can you post Asterisk Console output around call initiation? once fbilling AGI script is executed it should log to asterisk console similar output:

Launched AGI Script /var/lib/asterisk/agi-bin/fbilling.agi
fbilling.agi,: ==================================================================
fbilling.agi,: ==================================================================
fbilling.agi,: FBILLING version 0.9.1, executing with debug level 2
fbilling.agi,: Only logging to /var/log/asterisk/fbilling.log
    -- AGI Script Executing Application: (Dial) Options: (SIP/XXXXXXXX)

If not the same output, at least it should say that script failed to execute... Also I noticed, in fbilling.conf file, for comments you use ";" rather then "#" - which is weird and if so, might cause the issue.