3CX v15.5 Log Viewer Missing Data

[[email protected]]

I'm finding that when I open the .bldef and .blrec files from the support info that I'm missing data. I can go into the Call Logs and find the call I'm looking for but when I use the log viewer the detailed data I'm looking for isn't in there at all. I know for a fact that I've used this log viewer to view detailed call information in the past (on 3cx v14) but now there's no details on calls. It seems to be mostly errors in there. I've made sure that everything is checked including the radio button for all levels under the log viewer preferences.

Can someone tell me how to get the log viewer to show me the detailed records of a call? I want to see all details of the route it took in, the transfer from the attendant to the queue, the extension that picked it up, and the disconnect of the call. As of this writing all of that information is gone from the log.

I found someone online saying to just use pgadmin to pull the call records that I want. I'm going to play around with that later but I would prefer to get the 3CX log viewer to show me the data I need.

 

[[email protected]]

I noticed that on my system a few weeks ago. Just now getting around to looking it up.
I found an article saying there was a Hotfix shortly after 15.5 SP3 to fix this ... obviously it didn't!
My Call Logs screen is completely blank.

What version are you running?

Dashboard shows: 15.5.15502.6
Parameters shows:15.5.12227.5

3CX Phone System v15.5, Update 6, Build 15.5.15502.6

 

[[email protected]]

What browser are you using ... I just installed Firefox 66.0 and I can see stuff!

 

[[email protected]]

I'm running version 15.5.15502.6.

The viewer I'm looking at isn't part of the web interface. The 3cx information on it can be found at https://www.3cx.com/docs/3cx-log-viewer/. I'm pulling the support logs that should include some detailed information about the calls in 3cx.

If I use the Call Logs menu in the web interface I can see a single entry for the call I'm looking for and it has some basic info like to,from, and call duration. I was hoping to find more detailed records about the call as it travels from my PRI, to 3CX, to the queue, to the extension that picked it up, and then the hangup.

 

[YiannisH_3CX]

If services were restarted at some point after the call was made then you will not find the information in the bin log viewer as logs get reset when services are restarted. Also .bldef files are correlated with specific .blrec files. So if you have a high volume PBX and new .blrec files are files are created all the time to keep up with the logs your .bldef file might not be able to read the specific .blrec file that the call you want is located at. For maximum details you may want to enable Verbose logging but it is not recommended to keep it enabled all the time as it is CPU intensive.

 

[[email protected]]

The call I'm looking for happened after the last reboot for Windows Update. The log file contains data for the time frame I'm looking for. As an example. I know that yesterday a call with one way audio came in at 1:42PM yesterday. I can find the call in the gui call log. But when I search the time frame in the support call log this is all I see:

27/03/2019 13:41:14:442 | 8 | [CM503003]: Call(C:22057): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 10.73.0.200:5062
27/03/2019 13:42:08:366 | 8 | Call to T:Extn:1849@[Dev:sip:[email protected]:5062] from L:22065.1[Extn:1800] failed, cause: Cause: 302 Moved Temporarily/INVITE from 10.73.84.189:5062
27/03/2019 13:42:08:367 | 8 | [CM503003]: Call(C:22065): Call to <sip:[email protected]:5060> has failed; Cause: 302 Moved Temporarily/INVITE from 10.73.84.189:5062
27/03/2019 13:42:33:711 | 8 | [CM503003]: Call(C:22072): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 10.73.47.165:63251
27/03/2019 13:42:33:727 | 8 | [CM503003]: Call(C:22072): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 10.73.47.184:5062
27/03/2019 13:42:33:731 | 8 | [CM503003]: Call(C:22072): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 10.73.47.190:5062
27/03/2019 13:42:33:735 | 8 | [CM503003]: Call(C:22072): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 10.73.47.189:5062
27/03/2019 13:42:33:747 | 8 | [CM503003]: Call(C:22072): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 10.73.47.182:5062
27/03/2019 13:42:33:759 | 8 | [CM503003]: Call(C:22072): Call to "Loc47 Ring/Page" <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 10.73.47.180:2204
27/03/2019 13:42:33:803 | 8 | [CM503003]: Call(C:22072): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 10.73.47.183:5062
27/03/2019 13:42:33:835 | 8 | [CM503003]: Call(C:22072): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 10.73.47.185:5062
27/03/2019 13:42:33:937 | 8 | [CM503003]: Call(C:22072): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 10.73.47.188:5062
27/03/2019 13:43:36:428 | 8 | [CM503003]: Call(C:22083): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 10.73.0.245:5062
27/03/2019 13:43:57:419 | 8 | [CM503003]: Call(C:22087): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 10.73.0.207:5062
27/03/2019 13:44:26:450 | 8 | [CM503003]: Call(C:22089): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Cancelled/INVITE from 10.73.1.99:5060
27/03/2019 13:44:32:070 | 8 | [CM503003]: Call(C:22096): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 10.73.0.197:61356
27/03/2019 13:44:32:279 | 8 | [CM503003]: Call(C:22094): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 10.73.1.171:49466
27/03/2019 13:44:32:289 | 8 | [CM503003]: Call(C:22094): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 10.73.1.62:5062
27/03/2019 13:44:32:312 | 8 | [CM503003]: Call(C:22097): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 10.73.1.199:5062
27/03/2019 13:44:32:314 | 8 | [CM503003]: Call(C:22100): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 10.73.1.181:5062
27/03/2019 13:44:32:317 | 8 | [CM503003]: Call(C:22098): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 10.73.0.206:5062
27/03/2019 13:44:32:317 | 8 | [CM503003]: Call(C:22099): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 10.73.1.211:5062
27/03/2019 13:44:32:320 | 8 | [CM503003]: Call(C:22095): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 10.73.0.215:5062
27/03/2019 13:44:32:330 | 8 | [CM503003]: Call(C:22101): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 10.73.1.215:5062
27/03/2019 13:44:37:653 | 8 | [CM503003]: Call(C:22104): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 10.73.0.207:5062
27/03/2019 13:44:54:954 | 8 | [CM503003]: Call(C:22109): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 10.73.1.105:5062

In the past when I searched I would get a lot more information from the log than that.

I'll look into verbose logging. I don't believe I've ever had to turn on verbose logging before. It's possible my predecessor had it enabled and when I upgraded the server to 15.5 from 14 in October that may have reset it.

 

[[email protected]]

After reviewing everything I believe that my predecessor had enabled verbose logging and the difference I see now is because we upgraded from v14 to v15.5. The instructions on enabling verbose logging are here: https://www.3cx.com/docs/collecting-logs-for-3cx-support/