Recent content by Rasreby

Order is now set to 90. See logs below. 8dc97725-2f15-4165-a4c5-be1b60813615 2024-12-21 06:27:41.231989 99.50% [DEBUG] switch_core_state_machine.c:281 (sofia/internal/401@192.168.2.245:5090) State Change CS_ROUTING -> CS_EXECUTE 8dc97725-2f15-4165-a4c5-be1b60813615 2024-12-21 06:27:41.231989...

Gateway is properly setup and registered. Sending 10 digits CLID Outbound route is set with Dialplan expression set for North America. I think my issues are around limit which is set at 120 and order which is set for 100.

Still no success with the changes recommended. On the CDR, Destination says limit_exceeded and on Hang Up Cause it says Exchange routing error. Also I just notice inbound calls are not coming in. This must have been broken while playing around with the configs.

Yes, outbound route is created. Order is 100 and limits was first blank. I put it to 10 and it seem to for a while but it stopped working all together now.

Extension to extension call works fine, inbound also works fine but fast busy on all outbound calls. See logs below. a1316f56-7bda-48f9-b689-b4f45351f609 2024-12-17 18:58:27.182495 99.77% [DEBUG] switch_core_state_machine.c:281 (sofia/internal/401@192.168.2.241) State Change CS_ROUTING ->...

After instillation was complete I ran the command # cd /usr/src/fusionpbx-install.sh/debian/resources/ then # ./letsencrypt.sh. The output fail as you will see below and now I can't login to IP or domain. ERROR: Challenge is invalid! (returned: invalid) (result: ["type"] "http-01" ["url"]...

Running Fusion PBX ver 5.3 on Debian 12. Gateway is registered, outbound calls are fine and extension to extension is fine. However my DID cannot ring into the extension or Ring Group. I get a busy signal. My carrier is VoIPMS. See below for logfile output...

VoIP trunk registration is good, outbound calls are fine but no incoming calls. Fusion PBX 5.3 and below is what I see in the Log file. I have gone ahead and create a new domain and user name as requested by the log file but still no luck. See below for log file entry. 2024-11-27...