SOLVED Problem configuring routes. Not working.

[AverageGuy]

I am upgrading FusionPBX and decided to do a complete install. All seemed to be going OK. I created a few extensions which worked fine. I added my gateway (Telasip) and it registered OK. I then generated an inbound destination and it seemed to not have a problem with that. I then took a look at the inbound route that it created. The xml looks fine:

<extension name="7707190239" continue="false" uuid="8ee1ce5f-55e9-4da1-ba33-bbfa8f7c69ac">
<condition field="destination_number" expression="^(7707190239)$">
<action application="export" data="call_direction=inbound" inline="true"/>
<action application="set" data="domain_uuid=dfc61fd9-c1af-442c-9829-6b8851eeb807" inline="true"/>
<action application="set" data="domain_name=192.168.2.25" inline="true"/>
<action application="transfer" data="1003 XML 192.168.2.25"/>
</condition>
</extension>

I included screen dumps of the associated panels. To test I placed a call from another phone. As soon as it connected, it tossed me into my sip provider's voicemail. I looked in the FS log and here's what it says:

b9879b22-3ba2-41a8-a0b9-ad3f8769148a 2025-06-21 09:07:57.343566 99.53% [NOTICE] switch_channel.c:1142 New Channel sofia/external/+17702827403@23.105.171.76 [b9879b22-3ba2-41a8-a0b9-ad3f8769148a]
b9879b22-3ba2-41a8-a0b9-ad3f8769148a 2025-06-21 09:07:57.343566 99.53% [DEBUG] switch_core_state_machine.c:581 (sofia/external/+17702827403@23.105.171.76) Running State Change CS_NEW (Cur 1 Tot 4)
b9879b22-3ba2-41a8-a0b9-ad3f8769148a 2025-06-21 09:07:57.343566 99.53% [INFO] sofia.c:10460 sofia/external/+17702827403@23.105.171.76 receiving invite from 18.215.9.144:5060 version: 1.10.12-release git d8481a9 2025-01-13 17:41:43Z 64bit call-id: Rsp6w-hKdOPglmpRVtsCbwGPLxm8AxZI
2025-06-21 09:07:57.343566 99.53% [DEBUG] sofia.c:10554 verifying acl "providers" for ip/port 18.215.9.144:0.
b9879b22-3ba2-41a8-a0b9-ad3f8769148a 2025-06-21 09:07:57.343566 99.53% [DEBUG] switch_core_state_machine.c:600 (sofia/external/+17702827403@23.105.171.76) State NEW
2025-06-21 09:07:57.343566 99.53% [DEBUG] sofia.c:2419 detaching session b9879b22-3ba2-41a8-a0b9-ad3f8769148a
b9879b22-3ba2-41a8-a0b9-ad3f8769148a 2025-06-21 09:08:07.363565 99.07% [WARNING] switch_core_state_machine.c:684 b9879b22-3ba2-41a8-a0b9-ad3f8769148a sofia/external/+17702827403@23.105.171.76 Abandoned
b9879b22-3ba2-41a8-a0b9-ad3f8769148a 2025-06-21 09:08:07.363565 99.07% [NOTICE] switch_core_state_machine.c:687 Hangup sofia/external/+17702827403@23.105.171.76 [CS_NEW] [WRONG_CALL_STATE]
b9879b22-3ba2-41a8-a0b9-ad3f8769148a 2025-06-21 09:08:07.363565 99.07% [DEBUG] switch_core_state_machine.c:581 (sofia/external/+17702827403@23.105.171.76) Running State Change CS_HANGUP (Cur 1 Tot 4)
b9879b22-3ba2-41a8-a0b9-ad3f8769148a 2025-06-21 09:08:07.363565 99.07% [DEBUG] switch_core_state_machine.c:844 (sofia/external/+17702827403@23.105.171.76) Callstate Change DOWN -> HANGUP
b9879b22-3ba2-41a8-a0b9-ad3f8769148a 2025-06-21 09:08:07.363565 99.07% [DEBUG] switch_core_state_machine.c:846 (sofia/external/+17702827403@23.105.171.76) State HANGUP
b9879b22-3ba2-41a8-a0b9-ad3f8769148a 2025-06-21 09:08:07.363565 99.07% [DEBUG] mod_sofia.c:469 Channel sofia/external/+17702827403@23.105.171.76 hanging up, cause: WRONG_CALL_STATE
b9879b22-3ba2-41a8-a0b9-ad3f8769148a 2025-06-21 09:08:07.363565 99.07% [DEBUG] switch_core_state_machine.c:59 sofia/external/+17702827403@23.105.171.76 Standard HANGUP, cause: WRONG_CALL_STATE
b9879b22-3ba2-41a8-a0b9-ad3f8769148a 2025-06-21 09:08:07.363565 99.07% [DEBUG] switch_core_state_machine.c:846 (sofia/external/+17702827403@23.105.171.76) State HANGUP going to sleep
b9879b22-3ba2-41a8-a0b9-ad3f8769148a 2025-06-21 09:08:07.363565 99.07% [DEBUG] switch_core_state_machine.c:616 (sofia/external/+17702827403@23.105.171.76) State Change CS_HANGUP -> CS_REPORTING
b9879b22-3ba2-41a8-a0b9-ad3f8769148a 2025-06-21 09:08:07.363565 99.07% [DEBUG] switch_core_state_machine.c:581 (sofia/external/+17702827403@23.105.171.76) Running State Change CS_REPORTING (Cur 1 Tot 4)

It looks like FS isn/t seeing the dialplan. Is there something new that I have to do? I've configured FusionPBX a half dozen times in the past and did ever have problems this early.

Any help would be appreciated.
Jim

 

[pbxgeek]

Did you add your provider to ACL list? Also, flash cache, reload XML?

 

[AverageGuy]

The ACL list was the key. I compared the old system to the new one and found they differed. Fixed, thank you.