Search results

SOLUTION: ------------------------------- The root cause turned out to be FusionPBX failing to regenerate the cached configuration file for extension 208 after a password change. Manually deleting the stale file resolves the issue: /var/cache/fusionpbx/pbx-vm.directory.208@192.168.0.212...

I also checked the FusionPBX PostgreSQL database and could not find anything unusual about extension 208 — all entries appear identical to those of other extensions. I also created a new extension, 308, with a simple password and tested it with a softphone (MicroSIP) — everything worked...

I did it many times, as stated in the first post...

Yes - I tried different devices and a softphones: 403 Forbidden....

The system is not yet in production, but the extensions numbers should match those on the existing analog system. I have tried restarting the service, flushing the cache, and even updating the FreeSWITCH to the latest version, but nothing has resolved the issue.

I'm running out of ideas at this point. Can anyone point me in the right direction?

More logs, just before "403 FORBIDDEN" tport.c:3055 tport_deliver() tport_deliver(0x7ff5d4008f90): msg 0x7ff5d408ae80 (837 bytes) from tcp/192.168.0.23:11799/sip next=(nil) nta.c:2968 agent_recv_request() nta: received REGISTER sip:192.168.0.212:5060 SIP/2.0 (CSeq 2) (load: 1 rps) nta.c:3175...

Anyone please ? I tried everything I was able to find in net.

There are two sets of logs attached. The first was captured when the device was assigned to extension 210, which registers successfully. The second was captured when the same device was assigned to extension 208, which fails to register. In both cases, the initial response to the REGISTER...

Hi All, I have a new FusionPBX installation running in a VM on Debian 13. There are around 20 extensions configured, along with the same number of devices (Yealink SIP-T74U phones). Everything is working correctly except for one extension: 208. This extension will not register any device. The...