Asterisk Channel Stucks

Asterisk Asterisk Support
1

I am facing issue on Asterisk 1.8.26.0 & 11.17.1.

It mostly happens when the system stays idle for more than 1 hour.

I am also logging MySQL CDRs via cdr_mysql module.

Below are the logs for reference:

[Mar  7 14:56:04] WARNING[25048] chan_sip.c: Autodestruct on dialog '370b69df0ccf5612464d6ce229110529@10.20.80.2' with owner SIP/4238104302-000034da in place (Method: BYE). Rescheduling destruction for 10000 ms
[Mar  7 14:56:08] WARNING[25048] chan_sip.c: Autodestruct on dialog '159ddd3120ae0efa2d7af3271a9bc31d@192.168.170.108:5060' with owner SIP/4571-000034dd in place (Method: BYE). Rescheduling destruction for 10000 ms
[Mar  7 14:56:10] WARNING[25048] chan_sip.c: Autodestruct on dialog '370b69df0ccf5612464d6ce229110529@10.20.80.2' with owner SIP/4238104302-000034da in place (Method: BYE). Rescheduling destruction for 10000 ms
[Mar  7 14:56:17] WARNING[25048] chan_sip.c: Autodestruct on dialog '370b69df0ccf5612464d6ce229110529@10.20.80.2' with owner SIP/4238104302-000034da in place (Method: BYE). Rescheduling destruction for 10000 ms
[Mar  7 14:56:19] WARNING[25048] chan_sip.c: Autodestruct on dialog '159ddd3120ae0efa2d7af3271a9bc31d@192.168.170.108:5060' with owner SIP/4571-000034dd in place (Method: BYE). Rescheduling destruction for 10000 ms
[Mar  7 14:56:23] WARNING[25048] chan_sip.c: Autodestruct on dialog '370b69df0ccf5612464d6ce229110529@10.20.80.2' with owner SIP/4238104302-000034da in place (Method: BYE). Rescheduling destruction for 10000 ms
[Mar  7 14:56:29] WARNING[25048] chan_sip.c: Autodestruct on dialog '159ddd3120ae0efa2d7af3271a9bc31d@192.168.170.108:5060' with owner SIP/4571-000034dd in place (Method: BYE). Rescheduling destruction for 10000 ms
[Mar  7 14:56:29] WARNING[25048] chan_sip.c: Autodestruct on dialog '370b69df0ccf5612464d6ce229110529@10.20.80.2' with owner SIP/4238104302-000034da in place (Method: BYE). Rescheduling destruction for 10000 ms
[Mar  7 14:56:34] ERROR[32277] cdr_mysql.c: Server has gone away. Attempting to reconnect.
2

We are not using connection pooling. But it happens when after MySQL connection disconnects(after
being idle for more than 1 hour) and it takes approximately 15-16 minutes for the connection to be established. Once the MySQL connection established, Autodestruct error vanishes

3

I have added a crontab where I made test calls with call files to keep the mysql conection alive.