BulkVS and FusionPBX

lamabean

New Member
Jan 15, 2025
7
0
1
24
I have outbound calling with BulkVS working fine however inbound calling fails without even ringing. Here are logs, where 10123456789 is the sanitized (not the actual number) number I'm calling in from, and 162.249.171.198 is BulkVS's IP address. Any idea what I should look into?

I'm using IP authentication, and have the BulkVS ips whitelisted in access control. It looks like their traffic is hitting 5060 internal instead of the 5080 external. however they will not send traffic to anything other than port 5060. And besides I read elsewhere on the forum that if their IPs are whitelisted in the access control, that the port mismatch isn't supposed to be an issue? I'm a FusionPBX beginner coming from FreePBX so forgive me if this is a very elementary mistake.


Code:
28ad6f56-53d8-47bc-8293-2f595270b609 2025-01-17 16:49:30.403868 97.63% [DEBUG] switch_core_state_machine.c:745 (sofia/internal/10123456789@162.249.171.198:5060) State DESTROY going to sleep
28ad6f56-53d8-47bc-8293-2f595270b609 2025-01-17 16:49:30.403868 97.63% [DEBUG] switch_core_state_machine.c:175 sofia/internal/10123456789@162.249.171.198:5060 Standard DESTROY
28ad6f56-53d8-47bc-8293-2f595270b609 2025-01-17 16:49:30.403868 97.63% [DEBUG] mod_sofia.c:380 sofia/internal/10123456789@162.249.171.198:5060 SOFIA DESTROY
28ad6f56-53d8-47bc-8293-2f595270b609 2025-01-17 16:49:30.403868 97.63% [DEBUG] switch_core_state_machine.c:745 (sofia/internal/10123456789@162.249.171.198:5060) State DESTROY
28ad6f56-53d8-47bc-8293-2f595270b609 2025-01-17 16:49:30.403868 97.63% [DEBUG] switch_core_state_machine.c:735 (sofia/internal/10123456789@162.249.171.198:5060) Running State Change CS_DESTROY (Cur 0 Tot 1)
28ad6f56-53d8-47bc-8293-2f595270b609 2025-01-17 16:49:30.403868 97.63% [NOTICE] switch_core_session.c:1770 Close Channel sofia/internal/10123456789@162.249.171.198:5060 [CS_DESTROY]
28ad6f56-53d8-47bc-8293-2f595270b609 2025-01-17 16:49:30.403868 97.63% [NOTICE] switch_core_session.c:1766 Session 1 (sofia/internal/10123456789@162.249.171.198:5060) Ended
28ad6f56-53d8-47bc-8293-2f595270b609 2025-01-17 16:49:30.403868 97.63% [DEBUG] switch_core_session.c:1748 Session 1 (sofia/internal/10123456789@162.249.171.198:5060) Locked, Waiting on external entities
28ad6f56-53d8-47bc-8293-2f595270b609 2025-01-17 16:49:30.403868 97.63% [DEBUG] switch_core_state_machine.c:607 (sofia/internal/10123456789@162.249.171.198:5060) State Change CS_REPORTING -> CS_DESTROY
28ad6f56-53d8-47bc-8293-2f595270b609 2025-01-17 16:49:30.403868 97.63% [DEBUG] switch_core_state_machine.c:932 (sofia/internal/10123456789@162.249.171.198:5060) State REPORTING going to sleep
28ad6f56-53d8-47bc-8293-2f595270b609 2025-01-17 16:49:30.403868 97.63% [DEBUG] switch_core_state_machine.c:168 sofia/internal/10123456789@162.249.171.198:5060 Standard REPORTING, cause: WRONG_CALL_STATE
28ad6f56-53d8-47bc-8293-2f595270b609 2025-01-17 16:49:30.403868 97.63% [DEBUG] switch_core_state_machine.c:932 (sofia/internal/10123456789@162.249.171.198:5060) State REPORTING
28ad6f56-53d8-47bc-8293-2f595270b609 2025-01-17 16:49:30.403868 97.63% [DEBUG] switch_core_state_machine.c:581 (sofia/internal/10123456789@162.249.171.198:5060) Running State Change CS_REPORTING (Cur 1 Tot 1)
28ad6f56-53d8-47bc-8293-2f595270b609 2025-01-17 16:49:30.403868 97.63% [DEBUG] switch_core_state_machine.c:616 (sofia/internal/10123456789@162.249.171.198:5060) State Change CS_HANGUP -> CS_REPORTING
28ad6f56-53d8-47bc-8293-2f595270b609 2025-01-17 16:49:30.403868 97.63% [DEBUG] switch_core_state_machine.c:846 (sofia/internal/10123456789@162.249.171.198:5060) State HANGUP going to sleep
28ad6f56-53d8-47bc-8293-2f595270b609 2025-01-17 16:49:30.403868 97.63% [DEBUG] switch_core_state_machine.c:59 sofia/internal/10123456789@162.249.171.198:5060 Standard HANGUP, cause: WRONG_CALL_STATE
28ad6f56-53d8-47bc-8293-2f595270b609 2025-01-17 16:49:30.403868 97.63% [DEBUG] mod_sofia.c:469 Channel sofia/internal/10123456789@162.249.171.198:5060 hanging up, cause: WRONG_CALL_STATE
28ad6f56-53d8-47bc-8293-2f595270b609 2025-01-17 16:49:30.403868 97.63% [DEBUG] switch_core_state_machine.c:846 (sofia/internal/10123456789@162.249.171.198:5060) State HANGUP
28ad6f56-53d8-47bc-8293-2f595270b609 2025-01-17 16:49:30.403868 97.63% [DEBUG] switch_core_state_machine.c:844 (sofia/internal/10123456789@162.249.171.198:5060) Callstate Change DOWN -> HANGUP
28ad6f56-53d8-47bc-8293-2f595270b609 2025-01-17 16:49:30.403868 97.63% [DEBUG] switch_core_state_machine.c:581 (sofia/internal/10123456789@162.249.171.198:5060) Running State Change CS_HANGUP (Cur 1 Tot 1)
28ad6f56-53d8-47bc-8293-2f595270b609 2025-01-17 16:49:30.403868 97.63% [NOTICE] switch_core_state_machine.c:687 Hangup sofia/internal/10123456789@162.249.171.198:5060 [CS_NEW] [WRONG_CALL_STATE]
28ad6f56-53d8-47bc-8293-2f595270b609 2025-01-17 16:49:30.403868 97.63% [WARNING] switch_core_state_machine.c:684 28ad6f56-53d8-47bc-8293-2f595270b609 sofia/internal/10123456789@162.249.171.198:5060 Abandoned
28ad6f56-53d8-47bc-8293-2f595270b609 2025-01-17 16:49:20.363606 97.30% [DEBUG] switch_core_state_machine.c:600 (sofia/internal/10123456789@162.249.171.198:5060) State NEW
2025-01-17 16:49:20.363606 97.30% [DEBUG] sofia.c:2419 detaching session 28ad6f56-53d8-47bc-8293-2f595270b609
2025-01-17 16:49:20.363606 97.30% [DEBUG] sofia.c:10554 verifying acl "providers" for ip/port 162.249.171.198:0.
28ad6f56-53d8-47bc-8293-2f595270b609 2025-01-17 16:49:20.363606 97.30% [INFO] sofia.c:10460 sofia/internal/10123456789@162.249.171.198:5060 receiving invite from 162.249.171.198:5060 version: 1.10.12-release git d8481a9 2025-01-13 17:41:43Z 64bit call-id: 335862418_131033260@x.x.x.x
28ad6f56-53d8-47bc-8293-2f595270b609 2025-01-17 16:49:20.363606 97.30% [DEBUG] switch_core_state_machine.c:581 (sofia/internal/10123456789@162.249.171.198:5060) Running State Change CS_NEW (Cur 1 Tot 1)
28ad6f56-53d8-47bc-8293-2f595270b609 2025-01-17 16:49:20.363606 97.30% [NOTICE] switch_channel.c:1142 New Channel sofia/internal/10123456789@162.249.171.198:5060 [28ad6f56-53d8-47bc-8293-2f595270b609]
SQL [Enabled]
 
Last edited:

lamabean

New Member
Jan 15, 2025
7
0
1
24
This has been SOLVED. My problem was that I was not putting the SIP ip addresses in the "providers" section of access control. Once I did that, inbound calls worked fine. Simple beginner mistake. :)