On a couple systems I manage, the call logs are not showing outbound calls. They only show inbound and missed calls. I’m not sure when this changed. The Call History and Call Events widgets in the UCP are working fine and showing the called numbers. What can I look into, or why wouldn’t they be showing on the desk phone? Sangoma P330 and P325 phones on v4.28.1.
I’m going on these assumption (correct me where I’m wrong) :
- this is affecting all Sangoma phones – not just a select few.
- this is a new issue (you said “I’m not sure when this changed”), possibly introduced along with a phone firmware update or a FreePBX update
- Call logs are maintained on the server
A 4.28.1 regression was reported recently, but in a Switchvox environment, only in a small cohort of phone configurations, and presents itself as a binary: either calls are logged, or they’re not. It’s not a hybrid case of missing only outbound calls.
A PTSR to examine would be extremely helpful.
If you can enable remote logging for an affected phone, you might find helpful clues there. Indications of call log requests and responses/requests are there.
Your assumptions are correct. I did do a remote syslog while trying and i’ll paste some of the sanitized lines below. I did try firmware versions 4.28.3, 4.28.1, 4.26.1, and 4.25.1 all with the same result.
[ 813]I/middleman: Sending cURL request to https://******.********.com:3443/dphoneApi.php/json with body {"request":{"method":"switchvox.users.callLogs.getList","parameters":{"account_id":"1","sort_field":"start_time","sort_order":"DESC","max_entries":"50"}}} and id call_log50
DEBUG USER 8/27/2026 12:00:46 PM lisa: [ 813]D/middleman: getFilecURL - sslInfo=Normal
DEBUG USER 8/27/2026 12:00:46 PM lisa: [ 529]D/dphonecored: KeyHandlerSangoma Key code:0x0028 value:0x0000
NOTICE USER 8/27/2026 12:00:47 PM xyz: [2026-08-27 12:00:47] [connect] Successful connection
NOTICE USER 8/27/2026 12:00:47 PM xyz: [2026-08-27 12:00:47] [error] Server handshake response error: websocketpp.processor:20 (Invalid HTTP status.)
DEBUG USER 8/27/2026 12:00:56 PM lisa: [ 813]D/middleman: cURL status code https://*******.*********.com:3443/dphoneApi.php/json 200
DEBUG USER 8/27/2026 12:00:56 PM lisa: [ 531]D/GeneralRequests: dispatch/remove request-id 'call_log50'
>>>>repeated 12 times INFO USER 8/27/2026 12:00:56 PM lisa: [ 531]I/dpcore: DPCall::DPCall() slot 0.0 callType(0) ringType(normal) remoteInfo()
INFO USER 8/27/2026 12:00:56 PM lisa: [ 531]I/core_ipc: Tx[0]: {"jsonrpc":"2.0","id":"516-49","result":[{"slot":"0","subslot":"0","callHandle":"1785792695.81","lastStatus":"487","lastStatusText":"","state":"DISCONNECTED","extraData":"","remoteInfo":"","remoteContact":"","mediaStatus":"none","role":"callee","localInfo":"","localContact":"","connectDuration":"0","creationTime":"2026-08-03 21:31:35Z","answerTime":"","codec":"","callIdHeader":"","xEventHeader":"","parsedName":"COGENT","parsedNumber":"+15717771150","dialedNumber":"","callPhotoPath":"","completedElsewhere":"0"},{"slot":"0","subslot":"0","callHandle":"1785850168.94","lastStatus":"487","lastStatusText":"","state":"DISCONNECTED","extraData":"","remoteInfo":"","remoteContact":"","mediaStatus":"none","role":"callee","localInfo":"","localContact":"","connectDuration":"0","creationTime":"2026-08-04 13:29:28Z","answerTime":"","codec":"","callIdHeader":"","xEventHeader":"","parsedName":"[V]######","parsedNumber":"+1***********","dialedNumber":"","callPhotoPath":
Looking through the DPMA apps log, it’s not sending any of the outbound calls. Below is the first request received. Sorry, but what’s a PTSR?
[2026-08-27 14:22:34] [dpmaapps.DEBUG]: dpmaapps: Received Request={“format”:“json”,“method”:“switchvox.users.callLogs.getList”,“parameters”:{“account_id”:“1”,“sort_field”:“start_time”,“sort_order”:“DESC”,“max_entries”:“50”},“contentType”:“application/json; charset=utf-8”}
For reference:
- “lisa” is the phone application (phone core and GUI combined) for P310-P330 phones. It’s “marge” on the P370.
- the “xyz” log lines refer to a different library that is not relevant in this use case (the associated error can be ignored here)
- the lisa/core_ipc line is the call log data being sent from the phone core up to the GUI.
You seem to be confirming this is an issue with FreePBX as you are pointing out:
it’s not sending any of the outbound calls
I cannot provide any insight into how to further debug the problem from the fpbx side.
A PTSR (“Phone Technical Support Report”) is an encrypted package that can be retrieved from a phone containing all the logs, configuration, etc. that we can use for diagnostics. It is obtained via HTTP request: http://<phone_ip>/cgi-bin/ptsr . At this point, I don’t believe it will reveal anything not already known here.
I did some more testing and reverting the restapps package back to 17.0.6.7 completely fixes the issue. Going back to 17.0.6.8 breaks it again.
Noted and internal ticket opened, thank you.
Any ticket number I could reference to test when an update is released? Would you be able to post in here when a patch is out and I can test it?
I am also experiencing this issue with my shop system. Any update on what’s going on?
What versions of Asterisk and the phone configuration module are y’all using ?
$ sudo -u asterisk /usr/sbin/asterisk -rx "core show version"
$ dpkg -l | grep digium
There’s been some certificate handling improvements across the ecosystem – please be on the lookout for any SSL negotiation errors if you are (hopefully) grabbing pcaps.
Asterisk 22.10.1 built by jenkins @ 63d217089c0c on a x86_64 running Linux on 2026-06-30 05:20:19 UTC
ii asterisk22-res-digium-phone 3.6.12-1.sng12 amd64 Provides a number of enhanced provisioning and application capabilities for Digium SIP phones
workaround until bug is fixed:
fwconsole ma downloadinstall restapps --tag=17.0.6.6