Hi all

I'm running a 1.8.32.3 instance of Asterisk on Centos 7.

About 80 SIP phones connected.

I'm getting tens of thousands of error messages in the CLI, and callers are
having extreme difficulty dialing, they can dial once and then if they try
to dial again their extension is shown as busy.

The server has been running for a year and a half, until this Wedenesday.
When I encountered this problem I then replaced the server with a new
physical machine with the same version of Asterisk that has been working for
the past year.

E. g. the hardware on the server is completely new, still having the exact
same problem as with the older server.

This is what is appearing in the CLI:

[Oct 30 11:02:16] WARNING[16831]: chan_sip.c:4057 __sip_autodestruct:
Autodestruct on dialog '[email protected]:5060'
with owner SIP/centra-out-00000140 in place (Method: BYE). Rescheduling
destruction for 10000 ms
[Oct 30 11:02:24] WARNING[16831]: chan_sip.c:4057 __sip_autodestruct:
Autodestruct on dialog '[email protected]:5060'
with owner SIP/3088-000001b0 in place (Method: BYE). Rescheduling
destruction for 10000 ms
[Oct 30 11:02:37] WARNING[16831]: chan_sip.c:4057 __sip_autodestruct:
Autodestruct on dialog '[email protected]:5060'
with owner SIP/3055-00000137 in place (Method: BYE). Rescheduling
destruction for 10000 ms
[Oct 30 11:02:39] WARNING[16831]: chan_sip.c:4057 __sip_autodestruct:
Autodestruct on dialog '[email protected]:5060'
with owner SIP/centra-out-000001b1 in place (Method: BYE). Rescheduling
destruction for 10000 ms
[Oct 30 11:02:40] WARNING[16831]: chan_sip.c:4057 __sip_autodestruct:
Autodestruct on dialog '[email protected]:5060'
with owner SIP/centra-out-000000cb in place (Method: BYE). Rescheduling
destruction for 10000 ms
[Oct 30 11:02:40] WARNING[16831]: chan_sip.c:4057 __sip_autodestruct:
Autodestruct on dialog '[email protected]:5060'
with owner SIP/3065-000000ca in place (Method: BYE). Rescheduling
destruction for 10000 ms
[Oct 30 11:02:43] WARNING[16831]: chan_sip.c:4057 __sip_autodestruct:
Autodestruct on dialog '[email protected]:5060'
with owner SIP/centra-out-00000138 in place (Method: BYE). Rescheduling
destruction for 10000 ms
[Oct 30 11:02:46] WARNING[16831]: chan_sip.c:4057 __sip_autodestruct:
Autodestruct on dialog '[email protected]:5060'
with owner SIP/3054-0000013f in place (Method: BYE). Rescheduling
destruction for 10000 ms
[Oct 30 11:02:48] WARNING[16831]: chan_sip.c:4057 __sip_autodestruct:
Autodestruct on dialog '[email protected]:5060'
with owner SIP/centra-out-00000140 in place (Method: BYE). Rescheduling
destruction for 10000 ms
[Oct 30 11:02:56] WARNING[16831]: chan_sip.c:4057 __sip_autodestruct:
Autodestruct on dialog '[email protected]:5060'
with owner SIP/3088-000001b0 in place (Method: BYE). Rescheduling
destruction for 10000 ms
[Oct 30 11:02:59] WARNING[16831]: chan_sip.c:4057 __sip_autodestruct:
Autodestruct on dialog '[email protected]:5060'
with owner SIP/3008-000001d2 in place (Method: BYE). Rescheduling
destruction for 10000 ms
[Oct 30 11:03:00] WARNING[16831]: chan_sip.c:4057 __sip_autodestruct:
Autodestruct on dialog '[email protected]:5060'
with owner SIP/3014-000001d7 in place (Method: BYE). Rescheduling
destruction for 10000 ms
[Oct 30 11:03:03] WARNING[16831]: chan_sip.c:4057 __sip_autodestruct:
Autodestruct on dialog '[email protected]:5060'
with owner SIP/3061-000001d5 in place (Method: BYE). Rescheduling
destruction for 10000 ms
[Oct 30 11:03:09] WARNING[16831]: chan_sip.c:4057 __sip_autodestruct:
Autodestruct on dialog '[email protected]:5060'
with owner SIP/3055-00000137 in place (Method: BYE). Rescheduling
destruction for 10000 ms
[Oct 30 11:03:11] WARNING[16831]: chan_sip.c:4057 __sip_autodestruct:
Autodestruct on dialog '[email protected]:5060'
with owner SIP/centra-out-000001b1 in place (Method: BYE). Rescheduling
destruction for 10000 ms
[Oct 30 11:03:12] WARNING[16831]: chan_sip.c:4057 __sip_autodestruct:
Autodestruct on dialog '[email protected]:5060'
with owner SIP/centra-out-000000cb in place (Method: BYE). Rescheduling
destruction for 10000 ms

If I do

asterisk*CLI>module show like timing 

I get

module show like timing
Module                         Description                              Use
Count
res_timing_dahdi.so            DAHDI Timing Interface                   0
asterisk*CLI>

My modules.conf specifies that only dahdi timing.

I have never seen any of my other 17 Asterisk servers at other sites showing
NO use of ANY timing interface...

What does these __sip_autodestruct messages mean? How can I fix this
problem?

Calls in progress are also randomly cut-off with no other CLI indications.

As I said, the server has been running completely stable for more than a
year before this started, and replacing the server physically has not
helped, same version of Asterisk loaded.

Any ideas?

Thanks!

Stefan


-- 
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
               http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Reply via email to