silox
New Member
- Joined
- Jun 14, 2016
- Messages
- 20
- Reaction score
- 16
Hello all,
I was recently affected by the Google Voice 'jabber TLS' issue on my OpenWRT Asterisk install which inspired me to build a new PBX. I decided to fit an SSD inside of one of my old Pogoplug Pros, install Debian on it with Linux kernel 4.1 and Incredible PBX 12 w/ Asterisk 13. I followed the instructions created by 'LeggoMyEggo' AKA 'Jay Deal' to install Incredible PBX on the Pogoplug Pro and they worked great. I also added the GV oauth2 patch and G729 without any problems as well. Things are up and running, I've successfully made plenty of incoming and outgoing calls. VERY IMPRESSIVE BTW!!!
I enabled incoming and outoing recording on my extension and I can see the recorded files on the Pogoplug Pro filesystem however nothing shows up under CDR reports. I've also installed/updated the UCP and User Management modules. After installing the modules, I created a user and associated my extension with it as well as added all of the appropriate CDR permissions. When I log into the UCP with that login I created which is associated with my extension, it doesn't show any entries either. I tried creating new entries by making some calls and still nothing in UCP nor CDR reports.
I've verified that the appropriate DB info is set in the asterisk config files (tested manually with 'mysql -u asteriskuser -p' as well as 'isql MySQL-asteriskcdrdb -v'). I also verified that the 'asteriskcdrdb' database exists, the 'asteriskuser' user has permissions to use it and it contains both the 'cdr' and 'cel' tables. Both tables are empty.
I do know that CDR records are being recorded as I've found a CSV file that contains all of the records I expect to see in the CDR reports and UCP area.
Any ideas? I've run odbc-gen.sh and tried using those generated files along with what was created at install time as well as manually modifying files (/etc/odbc.ini, /etc/odbcinst.ini, /etc/asterisk/cdr*.conf) with no luck. Below is status info from the Asterisk console:
pogopro01*CLI> cdr show status
Call Detail Record (CDR) settings
----------------------------------
Logging: Enabled
Mode: Simple
Log unanswered calls: No
Log congestion: No
* Registered Backends
-------------------
ODBC
csv
Adaptive ODBC
cdr-custom
cdr_manager (suspended)
pogopro01*CLI> odbc show all
ODBC DSN Settings
-----------------
Name: MySQL-TravMan4
DSN: MySQL-TravMan4
Last connection attempt: 1969-12-31 18:00:00
Name: MySQL-asteridex
DSN: MySQL-asteridex
Last connection attempt: 1969-12-31 18:00:00
Name: MySQL-asterisk
DSN: MySQL-asterisk
Last connection attempt: 1969-12-31 18:00:00
Name: MySQL-asteriskcdrdb
DSN: MySQL-asteriskcdrdb
Last connection attempt: 1969-12-31 18:00:00
Name: MySQL-avantfax
DSN: MySQL-avantfax
Last connection attempt: 1969-12-31 18:00:00
Name: MySQL-mysql
DSN: MySQL-mysql
Last connection attempt: 1969-12-31 18:00:00
Name: MySQL-performance_schema
DSN: MySQL-performance_schema
Last connection attempt: 1969-12-31 18:00:00
Name: MySQL-test
DSN: MySQL-test
Last connection attempt: 1969-12-31 18:00:00
Name: MySQL-timeclock
DSN: MySQL-timeclock
Last connection attempt: 1969-12-31 18:00:00
Name: MySQL-zipcodes
DSN: MySQL-zipcodes
Last connection attempt: 1969-12-31 18:00:00
If you need any additional info from me, please let me know and I'll be happy to oblige.
I was recently affected by the Google Voice 'jabber TLS' issue on my OpenWRT Asterisk install which inspired me to build a new PBX. I decided to fit an SSD inside of one of my old Pogoplug Pros, install Debian on it with Linux kernel 4.1 and Incredible PBX 12 w/ Asterisk 13. I followed the instructions created by 'LeggoMyEggo' AKA 'Jay Deal' to install Incredible PBX on the Pogoplug Pro and they worked great. I also added the GV oauth2 patch and G729 without any problems as well. Things are up and running, I've successfully made plenty of incoming and outgoing calls. VERY IMPRESSIVE BTW!!!
I enabled incoming and outoing recording on my extension and I can see the recorded files on the Pogoplug Pro filesystem however nothing shows up under CDR reports. I've also installed/updated the UCP and User Management modules. After installing the modules, I created a user and associated my extension with it as well as added all of the appropriate CDR permissions. When I log into the UCP with that login I created which is associated with my extension, it doesn't show any entries either. I tried creating new entries by making some calls and still nothing in UCP nor CDR reports.
I've verified that the appropriate DB info is set in the asterisk config files (tested manually with 'mysql -u asteriskuser -p' as well as 'isql MySQL-asteriskcdrdb -v'). I also verified that the 'asteriskcdrdb' database exists, the 'asteriskuser' user has permissions to use it and it contains both the 'cdr' and 'cel' tables. Both tables are empty.
I do know that CDR records are being recorded as I've found a CSV file that contains all of the records I expect to see in the CDR reports and UCP area.
Any ideas? I've run odbc-gen.sh and tried using those generated files along with what was created at install time as well as manually modifying files (/etc/odbc.ini, /etc/odbcinst.ini, /etc/asterisk/cdr*.conf) with no luck. Below is status info from the Asterisk console:
pogopro01*CLI> cdr show status
Call Detail Record (CDR) settings
----------------------------------
Logging: Enabled
Mode: Simple
Log unanswered calls: No
Log congestion: No
* Registered Backends
-------------------
ODBC
csv
Adaptive ODBC
cdr-custom
cdr_manager (suspended)
pogopro01*CLI> odbc show all
ODBC DSN Settings
-----------------
Name: MySQL-TravMan4
DSN: MySQL-TravMan4
Last connection attempt: 1969-12-31 18:00:00
Name: MySQL-asteridex
DSN: MySQL-asteridex
Last connection attempt: 1969-12-31 18:00:00
Name: MySQL-asterisk
DSN: MySQL-asterisk
Last connection attempt: 1969-12-31 18:00:00
Name: MySQL-asteriskcdrdb
DSN: MySQL-asteriskcdrdb
Last connection attempt: 1969-12-31 18:00:00
Name: MySQL-avantfax
DSN: MySQL-avantfax
Last connection attempt: 1969-12-31 18:00:00
Name: MySQL-mysql
DSN: MySQL-mysql
Last connection attempt: 1969-12-31 18:00:00
Name: MySQL-performance_schema
DSN: MySQL-performance_schema
Last connection attempt: 1969-12-31 18:00:00
Name: MySQL-test
DSN: MySQL-test
Last connection attempt: 1969-12-31 18:00:00
Name: MySQL-timeclock
DSN: MySQL-timeclock
Last connection attempt: 1969-12-31 18:00:00
Name: MySQL-zipcodes
DSN: MySQL-zipcodes
Last connection attempt: 1969-12-31 18:00:00
If you need any additional info from me, please let me know and I'll be happy to oblige.