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.
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
Bear in mind that there are two methodologies to populate the mysql(like ) asteriskcdrdb database tables, for many years the now deprecated “cdr-mysql” (as per “make menuselect” while building Asterisk) and the newer cleaner “cdr_adaptive_odbc” (also in make menuselet, but lower down ) , with some irony, if you have them both working then the asteriskcdrdb cdr table will have duplicates, so if you have migrated an older system , the who knows, if for 10 years he used cdr-mysql. but now mariadb or something “deprecated to termination” then he will have to move singularly to the odbc thingy. Basically , either way needs configuring appropriately the connection to asteriskcdrdb, either by direct mysql or through odbc.
We are talking of the FreePBX distro though so if it was ever using the older way of accessing the database tables it should have been properly migrated to the current way a while ago…
I am really looking forward to @waldrondigital posting his findings when he attempts upgrading again to see if the package is there to start with and somehow not being properly updated on his box…
By the way, you did post in at least one thread where his problems with the distro upgrader were mentioned and he provided input about them so I thought you knew he was having problems with the distro upgrader “script”…
Now it’s not impossible he could have been talking about another system which is not running the FreePBX distro but I have not seen any mention of people having problem with the upgrader module, only about the distro upgrader “script”. I also noticed, from reading past messages of his, that he seems to be normally using the FreePBX distro so it was easy to assume he is talking about a FreePBX distro system…
You are right, I did make a small assumption and I know what happens when you assume…
Then is it just possible that the “Distro” upgrade needs to be fixed so the cdr records still work ?, I don’t personally have that problem, but I also don’t use “The Distro”, everything in cdr land works hunky-dory for me
Yes, that is what the devs are currently doing, fixing all reported problems with the distro upgrader “script”…
There is, at least, two known problems after the distro upgrade…
The existing /etc/odbc.ini is renamed to /etc/odbc.ini.rpmsave but nothing is put in its place. I logged that problem in FREEPBX-15491 the 8th of August. I believe the problem was fixed but there’s probably more than one reason this happens because some people still have this problem…
The asterisk*-odbc package is needed but not installed… That’s a new one…
Actually if they do it will be of their own making because it is something they will have setted up incorrectly…
That being said unless the upgrader module does way more than I think it does when it comes to upgrading to FreePBX 14 only the distro upgrader “script” users will possibly have that problem…
I see your post as a series of non-sequitors please clarify what you expect the upgrader module to do, and if you use the Distro , then does upgrading it then break the odbc cdr’s ? . Please one thing at a time.
@waldrondigital, if it turns out that when you attempt to upgrade your system again you have that problem and that this ticket has not been resolved could you please upload your logs in it? There must be a clue in them as to why this happened.
@waldrondigital, same question if you end up with the same problem if you retry this again…
As the problem did not happen on my own system (I mentioned it in the ticket but Bryan must be so busy he must have forgotten) I cannot provide any logs to have this problem fixed…
(I am also hoping he will revisit my original ticket because I found something else which is broken since my upgrade and I don’t think it is specific to my box…)
@Marbled I have looked at recent tickets and all the recent tickets I’ve looked at, look correct with regards to asterisk13-odbc, which is why we would need to see the logs in this particular case.
I know, which is why I am asking at least one of the person who had this problem, @jpaquin…
My guess is that @waldrondigital had the same problem but had to reinstall before it could be investigated further…
The reason I think this is this:
which suggests it was his problem as well…
I know @waldrondigital had DAHDI cards in at least some of his tests (and I know there is still a problem with this, this is what is causing my extremely slow boot, see my original ticket) and I believe was using VMs, maybe it plays a part like it did initially…
@jpaquin, do you have DAHDI cards or are you using VMs?
For what it’s worth - had the same problem on a machine (before I found this thread…) and screwed around with it for about an hour - the quick (and fairly easy) fix I finally found was to do an asterisk-version-switch to Asterisk 14 and then back down to Asterisk 13 - I have done it three times this way and it has fixed it every time.