CDR not working after FreePBX 13 to 14 upgrade

Hi!

Hi!

Assuming you have Asterisk 13 it should be in /usr/lib64/asterisk/modules/res_odbc.so and it is provided by the asterisk13-odbc-13.17.0-3.sng7.x86_64 package.

Is the file present and is that package (or the one appropriate for your Asterisk version) installed?

Good luck and have a nice day!

Nick

Hi!

Have you tried yum update?

There were new packages published recently…

Do make sure you have the odbc one in the bunch…

Good luck and have a nice day!

Nick

I have exactly this same problem. Same results from cdr show status and from odbc show.

Other than call reporting, everything seems to be working fine.

And according to yum everything is updated.

Bonjour!/Hi!

Is the file /usr/lib64/asterisk/modules/res_odbc.so present on your disk and is the appropriate package installed?

What is the output of rpm -q -a | grep odbc ?

Good luck and have a nice day!

Nick

Have had same issue for a while, have tried reverting back to FreePBX 13 no change and then back again to 14. Yum update done, system works Ok in all other respects just no CDR records visible in reports since full upgrade on 10th August. Query output for this system is:

rpm -q -a | grep odbc
asterisk14-odbc-14.6.1-2.sng7.x86_64
mysql-connector-odbc-5.2.5-6.el7.x86_64
php56w-odbc-5.6.31-2.sng7.x86_64

Hi!

Have you checked for/tried this:

UCP data stopped after upgrade to FreepBX 14 - #3 by Marbled ?

Good luck and have a nice day!

Nick

You are running Asterisk 14, who else in this thread is?

Good luck and have a nice day!

Nick

No Nick, I hadn’t tried the fix suggested, erring on the cautious side to see if others found a non invasive therapy . This morning however, boldly stepping out, I found etc/odbc.ini.rpmsave and renamed it as odbc.ini, ‘presto’ CDR records are being accumulated once again. There remains the record gap between snag and solution, c’est la vie!

Hi!

FYI, If the file was no longer present it is a non invasive therapy…

In essence, part of the configuration needed to access the database was no longer present on your system…

For some of us the file we had was moved out of the way (into the .rpmsave) and not replaced by a new one…

If I am not mistake a .rpmsave is made if the file we had is not the original one published with the RPM, in my case I believe I had to add the character set (charset) which was not initially present in the file…

You essentially had one of the problems I documented in my ticket about a month ago. Somehow, in some situations, this problem happens again after many releases of the upgrade “script”…

Yep, that’s life… :wink:

(French is actually my mother tongue so saying it in French in a sentence which is mostly in English would not sound as nice as an English speaking person using a French expression…)

Have a nice day!

Nicolas

et à toi aussi une belle journée

Richard

Interesting. My odbc.ini looked the same as odbc.ini.rpmsave. I have since reverted my VM back to FreePBX 13.

If you figure out a fix, please share!

LOL, merci!

Nicolas

Hi!

I believe it is two different problems… The end result appears to be the same but the cause apparently different…

Hopefully we can figure out what is missing.

Was the file /usr/lib64/asterisk/modules/res_odbc.so actually present on your disk?

Mike, when you retry this and especially if it is on the system that has a Sangoma A200, please let me know.

Once booted my system works but I am experiencing very slow boot and it seems to be directly related to my DAHDI hardware… I am wondering if you have the same problem as well…

As for your system I am sure that if we compare a system where CDR works to your non-working one I am sure we can figure out what is missing.

The first thing I would check if if the file is there, it looks like it is not… That would suggest the asterisk*-odbc package didn’t get installed somehow…

Good luck and have a nice day!

Nick

In my case /usr/lib64/asterisk/modules/res_odbc.so is not present.
odbc.ini matches odbci.ini.rpmsave

But the output from the rpm query gives:

rpm -q -a | grep odbc
php56w-odbc-5.6.31-2.sng7.x86_64
mysql-connector-odbc-5.2.5-6.el7.x86_64

So it looks like I have no odbc…

Bonjour Jacques!
(Hi Jacques!)

Now things are starting to make sense…

Can you do

yum install asterisk13-odbc

(if you are running Asterisk 13)

or

yum install asterisk14-odbc

(if you are running Asterisk 14)

and post the results back?

Do you get any error message, warnings about missing depencies, etc…?

If it installs properly, can you retry reloading the module (it might require a reboot but I don’t think so, at least to try to load it).

Good luck and have a nice day!

Nick

Bonjour!
(while I have a French name… I alas speak no French other than 4 years in high school that was a long time ago. I would love to be able to spend enough time in Montreal to rectify that situation:)

yum install asterisk13-odbc
Loaded plugins: fastestmirror, versionlock
Loading mirror speeds from cached hostfile
Resolving Dependencies
--> Running transaction check
---> Package asterisk13-odbc.x86_64 0:13.17.1-2.sng7 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

=================================================================================================================================================================================
 Package                                       Arch                                 Version                                         Repository                              Size
=================================================================================================================================================================================
Installing:
 asterisk13-odbc                               x86_64                               13.17.1-2.sng7                                  sng-pkgs                                62 k

Transaction Summary
=================================================================================================================================================================================
Install  1 Package

Total download size: 62 k
Installed size: 208 k
Is this ok [y/d/N]: y
Downloading packages:
asterisk13-odbc-13.17.1-2.sng7.x86_64.rpm                                                                                                                 |  62 kB  00:00:00     
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
  Installing : asterisk13-odbc-13.17.1-2.sng7.x86_64                                                                                                                         1/1 
  Verifying  : asterisk13-odbc-13.17.1-2.sng7.x86_64                                                                                                                         1/1 

Installed:
  asterisk13-odbc.x86_64 0:13.17.1-2.sng7                                                                                                                                        

Complete!
[root@vps1486485000 /]# rpm -q -a | grep odbc
php56w-odbc-5.6.31-2.sng7.x86_64
asterisk13-odbc-13.17.1-2.sng7.x86_64
mysql-connector-odbc-5.2.5-6.el7.x86_64

And checking the CDR report now shows that call detailed reporting is now working.

Merci!

Bonjour Jacques!
(Hi Jacques!)

:blush:

Both your first and last name is so very much French sounding that I had absolutely no doubt you spoke it…

If you want to be sure you have almost no choice but to speak in French, don’t go to Montréal… :wink:

While there are people who only speak French there (they learned it in school and forgot) it is quite easy to find someone who speaks English…

Yay!!! :smile:

I wonder why it didn’t get installed initially…

I was somewhat expecting to see a conflict or something similar but it got installed without problems…

@waldrondigital, @GameGamer43, installing the appropriate asterisk*-obbc was the fix this time… It somehow never got installed during the upgrade…

De rien!
(You are welcome!)

Have a nice day!

Nicolas

On a upgrade we only yum update so it would seem he did not have odbc installed before hence why a yum update does not pick it up.

Hi Tony!

Unlikely since he would likely have noticed the problem earlier but you are right, it’s one of the possibilities…

@waldrondigital, since you seem to have the same problem could you make a list of all the (asterisk, at least) modules you have before attempting the upgrade again and let us know if you do end up with the same problem @jpaquin had…

I wonder if it is the only package missing or the only one we noticed was missing…

The system I can compare with is itself a result of an in-place upgrade but this is what I have

asterisk13-13.17.1-2.sng7.x86_64
asterisk13-addons-13.17.1-2.sng7.x86_64
asterisk13-addons-bluetooth-13.17.1-2.sng7.x86_64
asterisk13-addons-core-13.17.1-2.sng7.x86_64
asterisk13-addons-mysql-13.17.1-2.sng7.x86_64
asterisk13-addons-ooh323-13.17.1-2.sng7.x86_64
asterisk13-core-13.17.1-2.sng7.x86_64
asterisk13-curl-13.17.1-2.sng7.x86_64
asterisk13-dahdi-13.17.1-2.sng7.x86_64
asterisk13-doc-13.17.1-2.sng7.x86_64
asterisk13-flite-2.2.1.3-3_3118e6a.sng7.x86_64
asterisk13-odbc-13.17.1-2.sng7.x86_64
asterisk13-ogg-13.17.1-2.sng7.x86_64
asterisk13-resample-13.17.1-2.sng7.x86_64
asterisk13-voicemail-13.17.1-2.sng7.x86_64

with Asterisk 13

and

asterisk14-addons-bluetooth.x86_64 0:14.6.1-2.sng7
asterisk14-addons-core.x86_64 0:14.6.1-2.sng7
asterisk14-addons-mysql.x86_64 0:14.6.1-2.sng7
asterisk14-addons-ooh323.x86_64 0:14.6.1-2.sng7
asterisk14-addons.x86_64 0:14.6.1-2.sng7
asterisk14-core.x86_64 0:14.6.1-2.sng7
asterisk14-curl.x86_64 0:14.6.1-2.sng7
asterisk14-dahdi.x86_64 0:14.6.1-2.sng7
asterisk14-doc.x86_64 0:14.6.1-2.sng7
asterisk14-flite.x86_64 0:2.3.1.3-4_c5b9348.sng7
asterisk14-odbc.x86_64 0:14.6.1-2.sng7
asterisk14-ogg.x86_64 0:14.6.1-2.sng7
asterisk14-resample.x86_64 0:14.6.1-2.sng7
asterisk14-voicemail.x86_64 0:14.6.1-2.sng7
asterisk14.x86_64 0:14.6.1-2.sng7

with Asterisk 14.

These are only the modules which have the Asterisk version in them.

@jpaquin, do you have all these packages now?

Have a nice day!

Nick