Calls not disconnected over AMI

Asterisk
1

Hi,
I am using asterisk 11.9 for conferencing, and I have an application server which controls the conferences over AMI.
The application server ends the conference and sends AMI hangup requests, but sometimes some of the participants are not disconnected.
The application server’s log is filled with lines like this one:

[INFO] 04 Aug 11:44:30 AM AJ DaemonPool-1.1 [] org.asteriskjava.manager.event.HangupRequestEvent[dateReceived=‘Thu Aug 04 11:44:30 IDT 2016’,privilege=‘call,all’,cause=‘111’,sequencenumber=null,channelstate=null,calleridname=null,timestamp=null,systemname=null,priority=null,exten=null,accountcode=null,connectedlinenum=null,calleridnum=null,channelstatedesc=null,connectedlinename=null,callerid=null,linkedid=null,uniqueid=‘1470216874.87’,context=null,server=null,language=null,channel=‘SIP/omnisip-incoming-0000004f’,systemHashcode=1355223354]

and asterisk’s log is filled with lines like this:

[Aug 3 06:48:38] WARNING[20549] chan_sip.c: Autodestruct on dialog ‘7c1ea63f33a10e3128bbab276168c768@94.188.133.70’ with owner SIP/omnisip-outgoing-0000001a in place (Method: BYE). Rescheduling destruction for 10000 ms

Any clues on how to solve this?

Thanks.

2

If you’re seeing this error message:

[Aug 3 06:48:38] WARNING[20549] chan_sip.c: Autodestruct on dialog '7c1ea63f33a10e3128bbab276168c768@94.188.133.70' with owner SIP/omnisip-outgoing-0000001a in place (Method: BYE). Rescheduling destruction for 10000 ms

Then you most likely have a ‘stuck’ channel in Asterisk. That typically occurs when the channel should be destroyed, but something is still referencing the channel. This is usually sign of a bug in some off nominal condition.

As it is, Asterisk 11.9.x is pretty old - over two years now - and bugs involving stuck channels have certainly been fixed within that time frame. I’d recommend upgrading to the latest in the 11.x series to see if that resolves the issue.

1 Like