Trunk call reject

[Vahram]

Hello

Please help understand why my incoming calls are rejecting by acl domains

2018-01-12 10:32:53.613974 [NOTICE] switch_channel.c:1104 New Channel sofia/internal/177@10.10.10.25 [6b7acb6a-f762-11e7-a94a-2fa59df0ae7b]
2018-01-12 10:32:53.613974 [DEBUG] switch_core_state_machine.c:584 (sofia/internal/177@10.10.10.25) Running State Change CS_NEW (Cur 1 Tot 2)
2018-01-12 10:32:53.613974 [DEBUG] sofia.c:9873 sofia/internal/177@10.10.10.25 receiving invite from 10.10.10.25:5060 version: 1.6.19 64bit
2018-01-12 10:32:53.613974 [DEBUG] sofia.c:10044 IP 10.10.10.25 Rejected by acl "domains". Falling back to Digest auth.
2018-01-12 10:32:53.613974 [WARNING] sofia_reg.c:1792 SIP auth challenge (INVITE) on sofia profile 'internal' for [118833@10.10.10.29] from ip 10.10.10.25
2018-01-12 10:32:53.613974 [DEBUG] switch_core_state_machine.c:603 (sofia/internal/177@10.10.10.25) State NEW
2018-01-12 10:32:53.613974 [DEBUG] sofia.c:2334 detaching session 6b7acb6a-f762-11e7-a94a-2fa59df0ae7b
2018-01-12 10:33:03.633971 [WARNING] switch_core_state_machine.c:687 6b7acb6a-f762-11e7-a94a-2fa59df0ae7b sofia/internal/177@10.10.10.25 Abandoned
2018-01-12 10:33:03.633971 [NOTICE] switch_core_state_machine.c:690 Hangup sofia/internal/177@10.10.10.25 [CS_NEW] [WRONG_CALL_STATE]
2018-01-12 10:33:03.633971 [DEBUG] switch_core_state_machine.c:584 (sofia/internal/177@10.10.10.25) Running State Change CS_HANGUP (Cur 1 Tot 2)
2018-01-12 10:33:03.633971 [DEBUG] switch_core_state_machine.c:850 (sofia/internal/177@10.10.10.25) Callstate Change DOWN -> HANGUP
2018-01-12 10:33:03.633971 [DEBUG] switch_core_state_machine.c:852 (sofia/internal/177@10.10.10.25) State HANGUP
2018-01-12 10:33:03.633971 [DEBUG] mod_sofia.c:438 Channel sofia/internal/177@10.10.10.25 hanging up, cause: WRONG_CALL_STATE
2018-01-12 10:33:03.653962 [DEBUG] switch_core_state_machine.c:60 sofia/internal/177@10.10.10.25 Standard HANGUP, cause: WRONG_CALL_STATE
2018-01-12 10:33:03.653962 [DEBUG] switch_core_state_machine.c:852 (sofia/internal/177@10.10.10.25) State HANGUP going to sleep
2018-01-12 10:33:03.653962 [DEBUG] switch_core_state_machine.c:619 (sofia/internal/177@10.10.10.25) State Change CS_HANGUP -> CS_REPORTING
2018-01-12 10:33:03.653962 [DEBUG] switch_core_state_machine.c:584 (sofia/internal/177@10.10.10.25) Running State Change CS_REPORTING (Cur 1 Tot 2)
2018-01-12 10:33:03.653962 [DEBUG] switch_core_state_machine.c:938 (sofia/internal/177@10.10.10.25) State REPORTING
2018-01-12 10:33:03.653962 [DEBUG] switch_core_state_machine.c:174 sofia/internal/177@10.10.10.25 Standard REPORTING, cause: WRONG_CALL_STATE
2018-01-12 10:33:03.653962 [DEBUG] switch_core_state_machine.c:938 (sofia/internal/177@10.10.10.25) State REPORTING going to sleep
2018-01-12 10:33:03.653962 [DEBUG] switch_core_state_machine.c:610 (sofia/internal/177@10.10.10.25) State Change CS_REPORTING -> CS_DESTROY
2018-01-12 10:33:03.653962 [DEBUG] switch_core_session.c:1665 Session 2 (sofia/internal/177@10.10.10.25) Locked, Waiting on external entities
2018-01-12 10:33:03.653962 [NOTICE] switch_core_session.c:1683 Session 2 (sofia/internal/177@10.10.10.25) Ended
2018-01-12 10:33:03.653962 [NOTICE] switch_core_session.c:1687 Close Channel sofia/internal/177@10.10.10.25 [CS_DESTROY]
2018-01-12 10:33:03.653962 [DEBUG] switch_core_state_machine.c:741 (sofia/internal/177@10.10.10.25) Running State Change CS_DESTROY (Cur 0 Tot 2)
2018-01-12 10:33:03.653962 [DEBUG] switch_core_state_machine.c:751 (sofia/internal/177@10.10.10.25) State DESTROY
2018-01-12 10:33:03.653962 [DEBUG] mod_sofia.c:343 sofia/internal/177@10.10.10.25 SOFIA DESTROY
2018-01-12 10:33:03.653962 [DEBUG] switch_core_state_machine.c:181 sofia/internal/177@10.10.10.25 Standard DESTROY
2018-01-12 10:33:03.653962 [DEBUG] switch_core_state_machine.c:751 (sofia/internal/177@10.10.10.25) State DESTROY going to sleep

 

[Uday]

From which IP you are getting incoming calls? Is that IP allowed in ACL?

 

[Vahram]

Thanks for your answer

Problem solved by adding IP in acl

 

[hailthemelody]

As an aside, some trunks have multiple IPs that they originate calls from. I had this happen with Twilio, where sometimes calls would come in (after adding the trunks IP to the ACL) and sometimes be blocked. Ensure that you add the range of IPs, if applicable.