chan_sip.c:4214 __sip_autodestruct

[Nefariousparity]

Getting a lot of these errors while running a survey. Eventually I end up having to restart the server or Asterisk.

chan_sip.c:4214 __sip_autodestruct: Autodestruct on dialog '59b24c763ffc984c2bf6c6e611bfc6d5@*.*.*.*.:5060' with owner SIP/baretelecom-00007de8 in place (Method: BYE). Rescheduling destruction for 10000 ms

srv01-Tel0 srv01-Tel01 *.*.*.* Y 624 - 22% 3312 6%

EDIT: I have updated my signature:

|| DB Schema Version: 1405 || 1.8.29.0-vici || BUILD: 150302-0951 ||VERSION: VERSION: 2.12-477a|1xTelephony|1x Telephony|1x Database\WEB|

[williamconley]

Nice that you updated your signature, but where's the installer version?

[Nefariousparity]

Here you go. I did some research and it seems to be some bug in asterisk. One thing I notice that made it go away was when I moved Telephony servers to SSD Hard drives.

[ZibiX]

Hi Nefariousparity.

I was experiencing the same issue as you are. I believe this was happening when server was overloaded.

For me, the problem was solved when i switch to SSD (same as you).

[Kumba]

Most asterisk related issues come from uptime (lack of nightly reboots) and overloading the server. This is why we recommend 125-150 channels per telephony server at the most. Asterisk does not scale with hardware.

[nandotech]

chan_sip.c:4214 __sip_autodestruct: Autodestruct on dialog '59b24c763ffc984c2bf6c6e611bfc6d5@*.*.*.*.:5060' with owner SIP/baretelecom-00007de8 in place (Method: BYE). Rescheduling destruction for 10000 ms

Looks curiously like an error I used to get from one of my carriers when my inbound settings were screwy if it is not definitely performance based issues, as suggested above.

[Nefariousparity]

I have six servers now, and I limit to 96 Trunks each 3cps. Fixed our transfer problem as well.

[rrb555]

Nice post back. I had the same problem. did the same thing but I am thinking the nightly reboot do the job.

Does anyone had the same problem which had more than 96 trunks? I have now 95 for my main (all-in-one) and 96 for my 2nd telephony server.

This is a nightmare I hope I dont experience this