Asterisk 18.20.2 is suddenly stopped responding

General Help
1

Today same problem happened twice on 2 diff PBXs.
both are using Freepbx and Asterisk 18.20.2

Problem: Asterisk is suddenly stopped responding

Suddenly today Asterisk stopped responding to our PJSIP devices. At that time, PBX box itself was connected with the internet network. However PJSIP devices are unable to connect with the Asterisk and unable to register also.

Once I restart our Asterisk, everything works fine again.

I don’t understand where and what the problem is.
no logs in CLI about errors
but on both servers it started with

2024-09-19 07:40:20] VERBOSE[47741] asterisk.c: Remote UNIX connection disconnected
[2024-09-19 07:40:47] VERBOSE[46366][C-0000d4bc] res_musiconhold.c: Stopped music on hold on Local/138@from-queue-000083cd;2
[2024-09-19 07:40:49] WARNING[46407][C-0000d4bc] channel.c: Exceptionally long voice queue length queuing to Local/138@from-queue-000083cd;2
[2024-09-19 07:40:50] WARNING[46407][C-0000d4bc] channel.c: Exceptionally long voice queue length queuing to Local/138@from-queue-000083cd;2
[2024-09-19 07:40:51] WARNING[46407][C-0000d4bc] channel.c: Exceptionally long voice queue length queuing to Local/138@from-queue-000083cd;2
[2024-09-19 07:40:53] WARNING[46407][C-0000d4bc] channel.c: Exceptionally long voice queue length queuing to Local/138@from-queue-000083cd;2
[2024-09-19 07:40:54] WARNING[46407][C-0000d4bc] channel.c: Exceptionally long voice queue length queuing to Local/138@from-queue-000083cd;2
[2024-09-19 07:40:55] WARNING[46407][C-0000d4bc] channel.c: Exceptionally long voice queue length queuing to Local/138@from-queue-000083cd;2
[2024-09-19 07:40:57] WARNING[46407][C-0000d4bc] channel.c: Exceptionally long voice queue length queuing to Local/138@from-queue-000083cd;2
[2024-09-19 07:40:58] WARNING[46407][C-0000d4bc] channel.c: Exceptionally long voice queue length queuing to Local/138@from-queue-000083cd;2
[2024-09-19 07:40:59] WARNING[46407][C-0000d4bc] channel.c: Exceptionally long voice queue length queuing to Local/138@from-queue-000083cd;2

Strange but before “long voice queue” I can see a reload of asterisk
like someone edits something and applies changes.
I assume it starts after that

On both servers, we are using PJSIP with TCP for extensions - if it matters
[2024-09-19 07:47:56] NOTICE[33116] res_pjsip/pjsip_transport_management.c: Shutting down transport 'TCP to 174.68.146.XX:5062' since no request was received in 32 seconds

Any hints or help would be appreciated.

Thank you.

2

The bits that immediately preceded the “reload” are pertinent, did Asterisk crash first ?

3

Multiposted at Asterisk 18.20.2 is suddenly stopped responding - Asterisk Support - Asterisk Community

4

hi there was no crash
it just stops responding to SIP messages I assume
because nobody can register and asterisk does not respond on invites

5

there was reload just before (new extension was added)

6

What version FreePBX?

7

FreePBX 15.0.37.8
FreePBX 15.0.37.4
both

8

Did you check that you are not running out memory or storage?

9

This error means that audio frames are being queued up and the thread that is supposed to read them isn’t doing it fast enough or at all. This will most likely require a backtrace to debug it.

Providing Great Debug - Support Services - Sangoma Documentation (atlassian.net)

10

Are these bare metal or virtual?

If bare metal what is the ram/cpu/storage space like on the FPBX servers?

You would probably save yourself a LOT of trouble trying to figure this out if you merely found a couple of more or less decent computers, Core i5, generation 7 or 6, 500GB hard disk, and just loaded FreePBX 16 on them, selecting Asterisk 18, then did the backup and restore from your old FPBX systems.

Gen7/6 is not usable for windows 11 so anything running windows 10 on that hardware is going to have to be replaced in a year anyway - and even off-lease gen8 gear is under $200 used.