- Code: Select all
[Apr 4 23:35:16] -- Executing [2261234567@trunkinbound:1] AGI("SIP/vitel-inbound-0000000c", "agi-DID_route.agi") in new stack
[Apr 4 23:35:16] -- Launched AGI Script /var/lib/asterisk/agi-bin/agi-DID_route.agi
[Apr 4 23:35:16] -- AGI Script agi-DID_route.agi completed, returning 0
[Apr 4 23:35:16] -- Executing [99909*3*@default:1] Answer("SIP/vitel-inbound-0000000c", "") in new stack
[Apr 4 23:35:16] -- Executing [99909*3*@default:2] AGI("SIP/vitel-inbound-0000000c", "agi-VDAD_ALL_inbound.agi") in new stack
[Apr 4 23:35:16] -- Launched AGI Script /var/lib/asterisk/agi-bin/agi-VDAD_ALL_inbound.agi
[Apr 4 23:35:16] -- Playing 'sip-silence' (escape_digits=) (sample_offset 0)
[Apr 4 23:35:16] -- Playing 'sip-silence' (escape_digits=) (sample_offset 0)
[Apr 4 23:35:16] -- AGI Script agi-VDAD_ALL_inbound.agi completed, returning 0
[Apr 4 23:35:16] -- Executing [99909*3*@default:3] Hangup("SIP/vitel-inbound-0000000c", "") in new stack
[Apr 4 23:35:16] == Spawn extension (default, 99909*3*, 3) exited non-zero on 'SIP/vitel-inbound-0000000c'
[Apr 4 23:35:16] -- Executing [h@default:1] DeadAGI("SIP/vitel-inbound-0000000c", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16---------------") in new stack
[Apr 4 23:35:16] -- AGI Script agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16--------------- completed, returning 0
go*CLI>
When I go into the DID set-up screen and set it up to go to an agent that works fine. This seems to only occur when I try to send the call to an inbound queue. Any ideas on what might be the issue and how I might be able to fix it?
P.S.
OS Version: CentOS release 5.5 (Final)
Vicidial Version: 2.2.1-237
Asterisk Version: 1.4.27.1-1