FreePBX | Register | Issues | Wiki | Portal | Support

UCP data stopped after upgrade to FreepBX 14

freepbx
bug
Tags: #<Tag:0x00007fb9057867f0> #<Tag:0x00007fb905786548>

(Jared Busch) #1

I upgraded my FreePBX 13 instance to FreePBX 14 on Friday night. I have a weird issue with TLS registration not working well, but otherwise everything seemed to be working.

Today I finally setup my UCP because I will be working from the back porch for a while and I use the UCP to start calls (I wear a DECT Headset).

Well the UCP works and I setup the widgets I want, but the data is all from prior to the upgrade.

This is a small system and I can easily blow it up and install clean, but I wanted to test the upgrade process.

I also no longer see a way to dial from the UCP. So I will have to use FOP2 for that.


(Andrew Nagy) #2

The data comes from asteriskcdrdb I would look there first in the cdr table.


(Marbled) #3

Hi!

Does CDR and CEL work at all from the Dashboard?

(edit: by at all I mean do you see anything added to it or is it just stale data from before the upgrade?)

After the upgrade that no longer worked for me, see

https://issues.freepbx.org/browse/FREEPBX-15491?focusedCommentId=108408&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-108408

(and the next 2 messages that follow it).

I had to recopy odbc.ini (in /etc I believe), as it was no longer present. I had to recopy the backup that was done when the RPM was updated (odbc.ini.rpmsave) to odbc.ini…

Are you having the same problem?

Good luck and have a nice day!

Nick


FreePBX 14 - Can't send FAX through FAXPro anymore
Video call does not have video
CDR not working after FreePBX 13 to 14 upgrade
CDR not working after FreePBX 13 to 14 upgrade
How to Upgrade FreePBX Distro 13 to 14
CDR Reports not working after update
(Jared Busch) #4

Yes, they worked perfectly. See the above screenshots. just the data was old.

I too, had the odbc.ini.rpmsave file with no odbc.ini. I copied the file and rebooted and still had no new data.

I made another phone call and it showed perfectly.

So I lost all my CDR and CEL data in the UCP since Friday. What other stuff is affected by this file?


(Jared Busch) #5

I opened a new issue, because I was not experiencing the same things you were and my 13 to 14 upgrade did not fail.

https://issues.freepbx.org/browse/FREEPBX-15597


(Andrew Nagy) #6

Just CDR and CEL


(Marbled) #7

Hi Jared!

Sorry, this is what I meant… I could see the old data but nothing new was getting added to it…

I recognized your issue as, apparently, being the same as mine because of this but I was somewhat pressed for time when I wrote my post and did not full explain what I meant… By at all I actually meant is there anything new added to it globally without any possible filtering done in UCP…

Sorry if being low on caffeine :tired_face: and pressed for time :worried: made my post unclear… I am glad that you checked if the file was present and fixed it anyway…

Actually, you were, sorry for that… As you so eloquently said, there is a definitely a difference between us though, yours was a successful upgrade, mine was not…

For me it was just one more thing that got broken…

Good luck and have a nice day!

Nick


(Jared Busch) #8

@Marbled looks like my follow me is broke too. So not perfect, but I do have a working system.


(Andrew Nagy) #9

Follow me was fixed last night.


(Jared Busch) #10

Was it this? I was just testing it and found this in my log.

[2017-08-17 14:50:14] WARNING[13331][C-00000012]: pbx_functions.c:460 func_args: Can't find trailing parenthesis for function 'IF(1?103-314NXXXXXX#:314NXXXXXX#'?

Edit: ah, it looks like that was it. Because farther down the log is this.

[2017-08-17 14:50:24] VERBOSE[13331][C-00000012] res_agi.c: dialparties.agi: Starting New Dialparties.agi
[2017-08-17 14:50:24] VERBOSE[13331][C-00000012] res_agi.c: dialparties.agi: Caller ID name is 'Lake' number is '5195'
[2017-08-17 14:50:24] VERBOSE[13331][C-00000012] res_agi.c: dialparties.agi: CW Ignore is: 
[2017-08-17 14:50:24] VERBOSE[13331][C-00000012] res_agi.c: dialparties.agi: CF Ignore is: 
[2017-08-17 14:50:24] VERBOSE[13331][C-00000012] res_agi.c: dialparties.agi: CW IN_USE/BUSY is: 1
[2017-08-17 14:50:24] VERBOSE[13331][C-00000012] res_agi.c: dialparties.agi: Methodology of ring is  'ringall'
[2017-08-17 14:50:24] VERBOSE[13331][C-00000012] res_agi.c: dialparties.agi: Added extension 103 to extension map
[2017-08-17 14:50:24] VERBOSE[13331][C-00000012] res_agi.c: dialparties.agi: Added extension 3145NXXXXXX#) to extension map

It has appended the missing ) to my number.


Issue getting FollowMe to work to external
(Marbled) #11

Hi Jared!

That’s not something I played with on that system so it’s quite possible I have the same problem…

There is at least one more problem I know about on my system, there is something that complains twice at boot and I have to try to get a better picture of to help track this down…

Unfortunately those error messages don’t end up in any of the logs (I know about) so it’s not a simple matter of cut and pasting it into the ticket and I can’t seem to get a good enough picture of the whole screen…

Good luck and have a nice day!

Nick


(Jared Busch) #12

Updated Core to 14.0.1.5 and it is fixed. Issue 15588 was referenced.
https://issues.freepbx.org/browse/FREEPBX-15588


(Andrew Nagy) #13

So is it fixed or not? I am not sure. Another person has commented on said ticket saying it doesnt work.


(Jared Busch) #14

Fixed. Sorry, I buried that statement in my sentence.

No issue with Follow Me now.


(Jared Busch) #15

Here is what my follow up test call looked like.

[2017-08-17 15:15:41] VERBOSE[17236][C-00000014] res_agi.c: dialparties.agi: Starting New Dialparties.agi
[2017-08-17 15:15:41] VERBOSE[17236][C-00000014] res_agi.c: dialparties.agi: Caller ID name is 'Lake' number is '5195'
[2017-08-17 15:15:41] VERBOSE[17236][C-00000014] res_agi.c: dialparties.agi: CW Ignore is:
[2017-08-17 15:15:41] VERBOSE[17236][C-00000014] res_agi.c: dialparties.agi: CF Ignore is:
[2017-08-17 15:15:41] VERBOSE[17236][C-00000014] res_agi.c: dialparties.agi: CW IN_USE/BUSY is: 1
[2017-08-17 15:15:41] VERBOSE[17236][C-00000014] res_agi.c: dialparties.agi: Methodology of ring is  'ringallv2'
[2017-08-17 15:15:41] VERBOSE[17236][C-00000014] res_agi.c: dialparties.agi: Added extension 103 to extension map
[2017-08-17 15:15:41] VERBOSE[17236][C-00000014] res_agi.c: dialparties.agi: Added extension 314NXXXXXX# to extension map

The trailing ) is gone. No warning and the call went out over the trunk as normal.


(Jared Busch) #16

I tested a FreePBX 13 system and posted on the issue thread.


(Russell Manning) #17

I’m still having this problem and my core version is 14.0.1.9.


Call Detail Record (CDR) settings

Logging: Enabled
Mode: Simple
Log unanswered calls: No
Log congestion: No

  • Registered Backends

    Adaptive ODBC

Module Description Use Count Status Support Level
cdr_adaptive_odbc.so Adaptive ODBC CDR backend 0 Running core
cdr_odbc.so ODBC CDR Backend 0 Not Running extended
cel_odbc.so ODBC CEL backend 0 Running core
func_odbc.so ODBC lookups 0 Not Running core
res_config_odbc.so Realtime ODBC configuration 0 Running core
res_odbc.so ODBC resource 0 Running core
res_odbc_transaction.so ODBC transaction resource 0 Running core
7 modules loaded


(Russell Manning) #18


(Marbled) #19

Hi!

Which problem? There were more than one here…

If CDR is not working (I think this is what this is about), please take a look at this:

(an earlier post in this thread)

and this

(My guess with what you posted is that THIS is your problem…)

and for more information this:

If you have the missing asterisk*-odbc package problem, we would need your help to provide the upgrade logs you have on your system…

Good luck and have a nice day!

Nick


After 14 upgrade, fax and call logging not working
SensuSangomaCheckService CRITICAL: rsyslogd DOWN
(Russell Manning) #20

Thanks the rename worked. Now if I can just get video working in 14.