Outbound Call Issue and FreeSwitch errors

Status
Not open for further replies.

devdewboy

New Member
Jan 17, 2023
3
0
1
56
California
Hello,
I have a FusionPBX Lab I am testing on before I upgrade production. Just patched OS(debian 11) and FusionPBX from 5.0.6 to 5.0.7.
I attempt to call my cell and:
  • I see the active call
  • My headset does not ring as ussual.
  • I can answer the call on my cell.
  • No Audio
I've rebooted the server, restarted freeswitch, restarted profiles etc. The Gateways appear to be up as well

Probably should have checked if outbound was working to begin with before patching. In any case digged around the logs and found this in the freeswitch.log:
Code:
2023-01-19 14:53:19.598312 97.63% [WARNING] sofia.c:6503 Ping failed 22245a48-552c-463a-a723-ce01ebbd69a2 with code 408 - count 1/0/1, state DOWN
2023-01-19 14:53:23.818309 98.47% [WARNING] sofia.c:6503 Ping failed 4864ac6e-9e50-4fff-8381-2c508f8912b5 with code 503 - count 1/0/1, state DOWN
2023-01-19 14:53:34.058319 98.30% [WARNING] sofia.c:6503 Ping failed ea361ca5-c815-4e33-be07-ec1ecdb9b12e with code 503 - count 1/0/1, state DOWN
2023-01-19 14:53:34.058319 98.30% [WARNING] sofia.c:6503 Ping failed b171ba70-06a5-4560-82be-596ed9d00041 with code 503 - count 1/0/1, state DOWN
2023-01-19 14:53:34.058319 98.30% [WARNING] sofia.c:6503 Ping failed 5553606b-e543-4427-bb63-ebed16001937 with code 503 - count 1/0/1, state DOWN
2023-01-19 14:53:34.058319 98.30% [WARNING] sofia.c:6503 Ping failed a66925c6-8057-4be8-8ee6-8d3a16ac851d with code 503 - count 1/0/1, state DOWN
2023-01-19 14:53:58.898311 98.13% [WARNING] sofia.c:6503 Ping failed 3c97878d-db57-4a5a-a587-32847886d53c with code 408 - count 1/0/1, state DOWN
2023-01-19 14:55:25.098335 96.50% [WARNING] sofia.c:6503 Ping failed 4864ac6e-9e50-4fff-8381-2c508f8912b5 with code 408 - count 1/0/1, state DOWN
2023-01-19 14:55:36.138329 96.30% [WARNING] sofia.c:6503 Ping failed a66925c6-8057-4be8-8ee6-8d3a16ac851d with code 408 - count 1/0/1, state DOWN
2023-01-19 14:55:36.138329 96.30% [WARNING] sofia.c:6503 Ping failed 5553606b-e543-4427-bb63-ebed16001937 with code 408 - count 1/0/1, state DOWN
2023-01-19 14:55:36.138329 96.30% [WARNING] sofia.c:6503 Ping failed b171ba70-06a5-4560-82be-596ed9d00041 with code 408 - count 1/0/1, state DOWN
2023-01-19 14:55:36.138329 96.30% [WARNING] sofia.c:6503 Ping failed ea361ca5-c815-4e33-be07-ec1ecdb9b12e with code 408 - count 1/0/1, state DOWN

Do not know how to debug the above. DNS is resolving correctly. A dig on sip.telnxy.com resolved to IP correctly. Any thought or suggestions?

Thanks,
Jason
 

hfoster

Active Member
Jan 28, 2019
684
81
28
34
That's essentialy saying the endpoint is rejecting your SIP Options pings, so Sofia won't choose to send calls to it.

If your gateways match the providers documentation, it might be a question for them. Maybe they have ACLs in place, I'm not sure.
 
Status
Not open for further replies.