Asterisk/Vicidial not hanging up channles

[Rudolfmdlt]

Hello All,

ViciBox Redux v.6.0.2-140825 single server install. Used the preload ISO. The server has an amfeltec card. Desktop setup with intel Core i7.

The server dials out over a SIP trunk and call quality is perfect but as the day proceeds, asterisk does not hang up calls and channels.

When I do an asterisk -rx 'core show channels' the active calls and channels reaches into the 10 000's after a couple of hours an inadvertently causes issues. On the asterisk console, I start getting hundreds of these messages:

Code: Select all

Oct  7 17:14:39] WARNING[25594]: chan_sip.c:4214 __sip_autodestruct: Autodestruct on dialog '5d0f4fb1561dc3e96d4d61c521a23272@172.17.146.11:5060' with owner SIP/Peer-Dialer1-000001e0 in place (Method: BYE). Rescheduling destruction for 10000 ms
[Oct  7 17:14:39] WARNING[25594]: chan_sip.c:4214 __sip_autodestruct: Autodestruct on dialog '229b0b48544b045f6a2c44750784d8b3@192.168.1.5:5060' with owner SIP/500-00000173 in place (Method: BYE). Rescheduling destruction for 10000 ms
[Oct  7 17:14:40] WARNING[25594]: chan_sip.c:4214 __sip_autodestruct: Autodestruct on dialog '0bfc7b5d0a34e37e11ed495c6cbb9a9d@192.168.1.5:5060' with owner SIP/500-000001b3 in place (Method: BYE). Rescheduling destruction for 10000 ms

Has anybody seen this behaviour on Vicidial before?

Regards,

Rudolf

[boybawang]

did you try another sip carrier? also is your server behind nAT?

[geoff3dmg]

What does your carrier dialplan look like? Did you forget to put the Hangup() as the last entry?

[bondkmf]

I am now getting this error as well.

WARNING[2940]: chan_sip.c:4214 __sip_autodestruct: Autodestruct on dialog '5925e955189577c860ced004479cb6f9@198.178.122.5:5060' with owner SIP/iplinkOUT65-00002adf in place (Method: BYE). Rescheduling destruction for 10000 ms

This is causing calls to not complete and place agents on hold for 3+ minutes. Also when a call finally does connect it does not register as a LIVE CALL.

VERSION: 2.12-497a
BUILD: 150717-1333

This is my carrier dial plan and we have switched carriers and that didn't help either.

exten => _91XXXXXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _91XXXXXXXXXX,2,Dial(${SIPTRUNK}/${EXTEN:1},,To)
exten => _91XXXXXXXXXX,3,Hangup

exten => _1XXXXXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _1XXXXXXXXXX,2,Dial(${SIPTRUNK}/${EXTEN},,To)
exten => _1XXXXXXXXXX,3,Hangup

exten => _XXXXXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _XXXXXXXXXX,2,Dial(${SIPTRUNK}/1${EXTEN},,To)
exten => _XXXXXXXXXX,3,Hangup



Please advise as we are pretty much 100% out of business at this point because of this error. I restarted the servers and it worked fine for about 30 minutes then boom same issue.

[bondkmf]

It's not just every now and then either, it's a constant stream of:

[Nov 9 16:22:49] WARNING[6367]: res_agi.c:1500 launch_netscript: FastAGI connection to 'agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0-----CANCEL----------' timed out after MAX_AGI_CONNECT (2000) milliseconds.
[Nov 9 16:22:49] WARNING[6369]: res_agi.c:1500 launch_netscript: FastAGI connection to 'agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0-----CANCEL----------' timed out after MAX_AGI_CONNECT (2000) milliseconds.
[Nov 9 16:22:49] WARNING[6375]: res_agi.c:1500 launch_netscript: FastAGI connection to 'agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0-----CANCEL----------' timed out after MAX_AGI_CONNECT (2000) milliseconds.
[Nov 9 16:22:49] WARNING[6379]: res_agi.c:1500 launch_netscript: FastAGI connection to 'agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0-----CANCEL----------' timed out after MAX_AGI_CONNECT (2000) milliseconds.
[Nov 9 16:22:49] WARNING[6385]: res_agi.c:1500 launch_netscript: FastAGI connection to 'agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0-----CANCEL----------' timed out after MAX_AGI_CONNECT (2000) milliseconds.
[Nov 9 16:22:49] WARNING[6388]: res_agi.c:1500 launch_netscript: FastAGI connection to 'agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0-----CANCEL----------' timed out after MAX_AGI_CONNECT (2000) milliseconds.
[Nov 9 16:22:49] WARNING[6392]: res_agi.c:1500 launch_netscript: FastAGI connection to 'agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0-----CANCEL----------' timed out after MAX_AGI_CONNECT (2000) milliseconds.
[Nov 9 16:22:49] WARNING[6394]: res_agi.c:1500 launch_netscript: FastAGI connection to 'agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0-----CANCEL----------' timed out after MAX_AGI_CONNECT (2000) milliseconds.
[Nov 9 16:22:49] WARNING[6396]: res_agi.c:1500 launch_netscript: FastAGI connection to 'agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0-----CANCEL----------' timed out after MAX_AGI_CONNECT (2000) milliseconds.
[Nov 9 16:22:49] WARNING[6405]: res_agi.c:1500 launch_netscript: FastAGI connection to 'agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0-----CANCEL----------' timed out after MAX_AGI_CONNECT (2000) milliseconds.
[Nov 9 16:22:49] WARNING[6407]: res_agi.c:1500 launch_netscript: FastAGI connection to 'agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0-----CANCEL----------' timed out after MAX_AGI_CONNECT (2000) milliseconds.
[Nov 9 16:22:49] WARNING[6413]: res_agi.c:1500 launch_netscript: FastAGI connection to 'agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0-----CANCEL----------' timed out after MAX_AGI_CONNECT (2000) milliseconds.
[Nov 9 16:22:49] WARNING[6417]: res_agi.c:1500 launch_netscript: FastAGI connection to 'agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0-----CANCEL----------' timed out after MAX_AGI_CONNECT (2000) milliseconds.