I picked up a pile of used P325 endpoints, and they’ve been far less straightfoward to provision than I’d expect.
I am running a new, up-to-date FreePBX 17 system on a Vultr-hosted Debian 12.14 VM. I have been unable to get any of the P325 units to do other than boot and give a “Communication Error: Timed out contacting proxy.” I have performed many Factory Resets as I’ve been making changes and finding issues, but I’m getting to my wits’ end.
The phone is configured in the Sangoma Portal, and is connected to the correct deployment. The poll count never increments (it shows N/A for all my test phones).
I have DPMA set up. I have mDNS disabled, because the PBX is not on my local network.
I have verified that servers are listening on the correct IP address (or 0.0.0.0).
Endpoint Manager is configured, and the extension’s configured Model/MAC are set correctly.
I can confirm that I can connect to the HTTPS provisioning port on the PBX from a workstation on the same ethernet switch. I have tried switching from my Unifi UDM Pro to a factory-default GL-Inet Slate router with no luck. I even went so far as to attempt a connection with my Cox Business cable modem directly connected to the phone, and it still would not connect.
I can connect to the phone’s web interface
I will say, none of the Tech Support diagnostic tools (Ping, NSLookup, Traceroute, etc) work. All fail with a “This feature is not implemented.” error. I am also not having any luck with “Start the phone without a configuration” - it just shows the Communications Error.
I did update the firmware from 4_18_3 to 4_25_1, but it made no difference.
What am I missing? Is there some configuration item in the endpoint I’ve missed, that Factory Default doesn’t clear?
