Trying to access the call log on Sangoma P-Series phones is returning a curl_error(-1). Have tried the few solutions I see on the forums and no luck so far. I did also try support and thought we had a solution but it has not been consistent. I have phones on the same templates both working as they should (getting call log fine)and not working(getting curl error when accessing call log). Some have always done it other have started spontaneously. If anyone has and advice it would be greatly appreciated! Sample from access.log if it helps (ip x’d out) XXX.XXX.XXX.XXX - - [07/May/2026:16:29:49 -0300] “GET /rtapi/socket.io/?EIO=3&transport=websocket&t=1778182190 HTTP/1.1” 404 214 “-” “WebSocket++/0.8.2”
I had a similar issue. Was there a user created when the extension was created? Was it added to the all users group?
There was not a user created when the extension was created. We are using AD to sync most of our extensions and this one is more of generic extension so there was no user account attached. Is that something that ended up resolving things for you?
We (Sangoma phones dev team) have only seen the “curl error(-1)” error when attempting to retrieve call logs, but it was not a phone error – it was related to DPMA connection/PBX failures. Perhaps you are seeing something similar.
This error can happen when the PBX is temporarily unavailable, or has failed over to the `host_alternate`. The Call Log config doesn’t provide a backup option.
The websocket connection failure in the access log suggests network connectivity issues between the phones and FreePBX server rather than phone configuration problems. Since some phones work fine on identical templates, it’s likely intermittent network or DPMA service issues. The missing user account for extensions could definitely cause authentication problems with call log access - worth creating users even for generic extensions if they need full phone features.