Inbound calls not connecting - Incompatible Destination

[firmfoit]

Hi all, just had this occurring on one tenant. Inbound calls are not connecting - just coming up as call ended. Nothing in call detail records but getting the following in the logs:

04cfbf18-3f1c-42fa-aaaf-7f714eeffb69 2023-07-18 06:17:13.742659 96.53% [NOTICE] switch_channel.c:1123 New Channel sofia/internal/0123456789@sip1.trunkprovider.com [04cfbf18-3f1c-42fa-aaaf-7f714eeffb69]
04cfbf18-3f1c-42fa-aaaf-7f714eeffb69 2023-07-18 06:17:13.742659 96.53% [DEBUG] switch_core_state_machine.c:581 (sofia/internal/0123456789@sip1.trunkprovider.com) Running State Change CS_NEW (Cur 1 Tot 1)
04cfbf18-3f1c-42fa-aaaf-7f714eeffb69 2023-07-18 06:17:13.742659 96.53% [INFO] sofia.c:10462 sofia/internal/0123456789@sip1.trunkprovider.com receiving invite from 203.160.8.75:5060 version: 1.10.7 -release-19-883d2cb662 64bit call-id: 7827-1302-6172023201713-BN02-BCPD-1-125.213.174.81~1o
2023-07-18 06:17:13.742659 96.53% [DEBUG] sofia.c:10556 verifying acl "domains" for ip/port 203.160.8.75:0.
2023-07-18 06:17:13.742659 96.53% [DEBUG] sofia.c:10585 IP 203.160.8.75 Approved by acl "domains[]". Access Granted.
04cfbf18-3f1c-42fa-aaaf-7f714eeffb69 2023-07-18 06:17:13.742659 96.53% [DEBUG] sofia.c:7499 Channel sofia/internal/0123456789@sip1.trunkprovider.com entering state [received][100]
04cfbf18-3f1c-42fa-aaaf-7f714eeffb69 2023-07-18 06:17:13.742659 96.53% [DEBUG] sofia.c:7509 Remote SDP:
04cfbf18-3f1c-42fa-aaaf-7f714eeffb69 v=0
04cfbf18-3f1c-42fa-aaaf-7f714eeffb69 o=PortaSIP 1169812648721763344 1 IN IP4 203.160.8.106
04cfbf18-3f1c-42fa-aaaf-7f714eeffb69 s=ENSResip
04cfbf18-3f1c-42fa-aaaf-7f714eeffb69 t=0 0
04cfbf18-3f1c-42fa-aaaf-7f714eeffb69 m=audio 63744 RTP/AVP 8 0 101
04cfbf18-3f1c-42fa-aaaf-7f714eeffb69 c=IN IP4 203.160.8.106
04cfbf18-3f1c-42fa-aaaf-7f714eeffb69 a=rtpmap:8 PCMA/8000
04cfbf18-3f1c-42fa-aaaf-7f714eeffb69 a=rtpmap:0 PCMU/8000
04cfbf18-3f1c-42fa-aaaf-7f714eeffb69 a=rtpmap:101 telephone-event/8000
04cfbf18-3f1c-42fa-aaaf-7f714eeffb69 a=fmtp:101 0-15
04cfbf18-3f1c-42fa-aaaf-7f714eeffb69 a=silenceSupp:off - - - -
04cfbf18-3f1c-42fa-aaaf-7f714eeffb69
04cfbf18-3f1c-42fa-aaaf-7f714eeffb69 2023-07-18 06:17:13.742659 96.53% [DEBUG] switch_core_media.c:5650 Audio Codec Compare [PCMA:8:8000:20:64000:1]/[G722:9:8000:20:64000:1]
04cfbf18-3f1c-42fa-aaaf-7f714eeffb69 2023-07-18 06:17:13.742659 96.53% [DEBUG] switch_core_media.c:5650 Audio Codec Compare [PCMU:0:8000:20:64000:1]/[G722:9:8000:20:64000:1]
04cfbf18-3f1c-42fa-aaaf-7f714eeffb69 2023-07-18 06:17:13.742659 96.53% [DEBUG] switch_core_media.c:5566 Set telephone-event payload to 101@8000
04cfbf18-3f1c-42fa-aaaf-7f714eeffb69 2023-07-18 06:17:13.742659 96.53% [DEBUG] switch_core_media.c:5973 sofia/internal/0123456789@sip1.trunkprovider.com Set 2833 dtmf send payload to 101 recv payload to 101
04cfbf18-3f1c-42fa-aaaf-7f714eeffb69 2023-07-18 06:17:13.742659 96.53% [NOTICE] sofia.c:7991 Hangup sofia/internal/0123456789@sip1.trunkprovider.com [CS_NEW] [INCOMPATIBLE_DESTINATION]
04cfbf18-3f1c-42fa-aaaf-7f714eeffb69 2023-07-18 06:17:13.742659 96.53% [DEBUG] sofia.c:1527 Channel is already hungup.
04cfbf18-3f1c-42fa-aaaf-7f714eeffb69 2023-07-18 06:17:13.742659 96.53% [DEBUG] switch_core_state_machine.c:600 (sofia/internal/0123456789@sip1.trunkprovider.com) State NEW
04cfbf18-3f1c-42fa-aaaf-7f714eeffb69 2023-07-18 06:17:13.742659 96.53% [DEBUG] switch_core_state_machine.c:581 (sofia/internal/0123456789@sip1.trunkprovider.com) Running State Change CS_HANGUP (Cur 1 Tot 1)
04cfbf18-3f1c-42fa-aaaf-7f714eeffb69 2023-07-18 06:17:13.742659 96.53% [DEBUG] switch_core_state_machine.c:844 (sofia/internal/0123456789@sip1.trunkprovider.com) Callstate Change DOWN -> HANGUP
04cfbf18-3f1c-42fa-aaaf-7f714eeffb69 2023-07-18 06:17:13.742659 96.53% [DEBUG] switch_core_state_machine.c:846 (sofia/internal/0123456789@sip1.trunkprovider.com) State HANGUP
04cfbf18-3f1c-42fa-aaaf-7f714eeffb69 2023-07-18 06:17:13.742659 96.53% [DEBUG] mod_sofia.c:468 Channel sofia/internal/0123456789@sip1.trunkprovider.com hanging up, cause: INCOMPATIBLE_DESTINATION
04cfbf18-3f1c-42fa-aaaf-7f714eeffb69 2023-07-18 06:17:13.742659 96.53% [DEBUG] mod_sofia.c:613 Responding to INVITE with: 488
04cfbf18-3f1c-42fa-aaaf-7f714eeffb69 2023-07-18 06:17:13.742659 96.53% [DEBUG] switch_core_state_machine.c:59 sofia/internal/0123456789@sip1.trunkprovider.com Standard HANGUP, cause: INCOMPATIBLE_DESTINATION
04cfbf18-3f1c-42fa-aaaf-7f714eeffb69 2023-07-18 06:17:13.742659 96.53% [DEBUG] switch_core_state_machine.c:846 (sofia/internal/0123456789@sip1.trunkprovider.com) State HANGUP going to sleep
04cfbf18-3f1c-42fa-aaaf-7f714eeffb69 2023-07-18 06:17:13.742659 96.53% [DEBUG] switch_core_state_machine.c:616 (sofia/internal/0123456789@sip1.trunkprovider.com) State Change CS_HANGUP -> CS_REPORTING
04cfbf18-3f1c-42fa-aaaf-7f714eeffb69 2023-07-18 06:17:13.742659 96.53% [DEBUG] switch_core_state_machine.c:581 (sofia/internal/0123456789@sip1.trunkprovider.com) Running State Change CS_REPORTING (Cur 1 Tot 1)
04cfbf18-3f1c-42fa-aaaf-7f714eeffb69 2023-07-18 06:17:13.742659 96.53% [DEBUG] switch_core_state_machine.c:932 (sofia/internal/0123456789@sip1.trunkprovider.com) State REPORTING

I assumed that there must have been a change to the codec used by the trunk provider, but they assure me there is not - and other FusionPBX instances that I use the same provider are not having trouble.

The only thing that has happened to any of the instances of late is that I deleted two of the 6 gateways that were on the system as we're no longer using them. I can't say for sure that the issues started at the same time, but I can't think of anything else that has changed. Any suggestions for further debugging?

Thanks

 

[Adrian Fretwell]

488 is "Not Acceptable Here". This can often be caused when the two endpoints could not agree on a common codec. I see from the log that one end is offering PCMA and PCMU, but it looks like the other end is only offering G722. This could be your problem.

 

[bdmonsey]

try sngrep -c and call in the number and see whats the reason it's being blocked, sometimes it can be that the ip wasnt added in the ACL, sometimes it can be that the carrier sends 11 digits and you entered 10 digits.

 

[firmfoit]

488 is "Not Acceptable Here". This can often be caused when the two endpoints could not agree on a common codec. I see from the log that one end is offering PCMA and PCMU, but it looks like the other end is only offering G722. This could be your problem.

Yes that's how I was reading it too. I can't understand why it's only offering that though, the SIP profile is using the global_codec_prefs variable, and that variable is set as PCMA,PCMU,G729,G722

 

[Adrian Fretwell]

There will be a reason! Check what you have inbound-codec-negotiation set to. I tend to use "generous".
It may be worth getting a packet capture to find out exactly what is going on.

 

[firmfoit]

There will be a reason! Check what you have inbound-codec-negotiation set to. I tend to use "generous".
It may be worth getting a packet capture to find out exactly what is going on.

Yes codec negotiation is set to generous. I can't understand why my setup is only offering G722. Will keep digging...

 

[firmfoit]

OK, working now. Not entirely sure what was the root cause, but it seems like something quirky in the database. Specifying the codecs in the sip profile allowed calls to connect, but were going immediately to 'busy', not to the ring group. Checked the ring group, the destinations weren't working properly - no ability to select timeout and all marked as disabled.

Ran upgrade including reset app defaults, enabled the extensions in the ring group again, and everything is now fine, including setting the codec selection back to the global variable.

 

[Adrian Fretwell]

Glad you have got it working. Just curious, what version of Fusion are you running?

 

[firmfoit]

5.1.0 after updates today.