vicidial.org

Just making an initial manual call. I believe I have all my extensions setup correctly, as well as the configurations.

I see this in the console:

-- Executing MeetMe("Local/8600051@default-bf03,2", "8600051") in new stack
> Channel Local/8600051@default-bf03,1 was answered.
-- Executing AGI("Local/8600051@default-bf03,1", "agi://127.0.0.1:4577/call_log") in new stack
-- AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
-- Executing Dial("Local/8600051@default-bf03,1", "Zap/g2/12067356735||tTo") in new stack
Aug 12 16:00:51 NOTICE[4323]: app_dial.c:1076 dial_exec_full: Unable to create channel of type 'Zap' (cause 34 - Circuit/channel congestion)
== Everyone is busy/congested at this time (1:0/1/0)
-- Executing Hangup("Local/8600051@default-bf03,1", "") in new stack
== Spawn extension (default, 912067356735, 3) exited non-zero on 'Local/8600051@default-bf03,1'
-- Executing DeadAGI("Local/8600051@default-bf03,1", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----34-----CONGESTION----------)") in new stack
-- AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... ----------) completed, returning 0
== Spawn extension (default, 8600051, 1) exited non-zero on 'Local/8600051@default-bf03,2'
-- Executing DeadAGI("Local/8600051@default-bf03,2", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0---------------)") in new stack
-- AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... ----------) completed, returning 0

Looking closer at the error, is a 9 being dialed before the 1?
Ideas?

Thank you in advance.

Yes, it will place a 9 before the 1 in the dialplan. Did you alter the dialplan to accept this string?

mflorell wrote:Yes, it will place a 9 before the 1 in the dialplan. Did you alter the dialplan to accept this string?

I did, but it still times out after 50 seconds of waiting for ring. I was playing around with the CSU vs DSX settings yesterday on the Channel bank. I'm going to revert back to the default CSU mode today.