vicidial.org

Hello,

Maybe this issue has been posted already, but i didn't find, so I'm sorry if it's a duplicate.

If you are calling a registerd personally callback by selecting the callback and clicking the "DIAL LEAD" Link the callback is dialed and if the called lead picks up the line the call is established and working fine.

But on the top the status message "STATUS: Calling: (xxx)xxx-xxxx UID: M0812130719000112627 Waiting for Ring... 45 seconds" is displayed any longer and counting the ringing seconds until 45 sec, and then you get a popup-message "Dial timed out..", but the call is active.

So it seems to be that the system is not recognizing, that the called lead has picked up the phone.

astguiclient version: 2.0.4.1RC3

I have replaced following files from the 2.0.4.1RC3 zip archive with the files from /svn/agc_2-X/branches/agc_2.0.4/www
vicidial.php, vdc_db_query.php, (at svn vicidial.php line 3218 is commented out).
Before replacing that files, the callback feature caused a firefox crash with popup flooding...

sounds like I need to release 2.0.4.1rc4 soon.

Are you still having issues?

Yes, the Callback issue (waiting for Ring...) is not solved by replacing the files from svn, the replacment only solved the firefox popup flooding issue.

can you post some Asterisk CLI of the Manual Callback call being placed?

that's the CLI output beginning with manually dial the callback, pick up the call, until the timout message appears

-- Executing AGI("Local/8600051@default-21b1,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-21b1,1", "IAX2/userid:password@111.222.111.222/00123456789|55|o") in new stack
-- Called userid:password@111.222.111.222/00123456789
-- Call accepted by 111.222.111.222 (format ulaw)
-- Format for call is ulaw
== Manager 'sendcron' logged off from 127.0.0.1
-- IAX2/userid-7 is ringing
== Parsing '/etc/asterisk/manager.conf': Found
== Manager 'sendcron' logged on from 127.0.0.1
== Manager 'sendcron' logged off from 127.0.0.1
-- IAX2/userid-7 stopped sounds
-- IAX2/userid-7 answered Local/8600051@default-21b1,1

Asterisk version?

1.2.24

Are these calls showing up in the call_log table of the MySQL database?

The calls are shown in the call_log.
The record appears also before the customer picks up the phone.

I've noticed another thing:
If everyone is logged out of the campaigns the vicidial_auto_calls table should be empty or not?
In our case the table is not emtpy it seems that also some calls with status XFER remains in the table. (Just to be sure I empty the table before monitoring that)

How many different contexts do you have in your dialplan?

I would recommend following a single call through the /screenlog.0 log file and posting every event that takes place on that call and channel.

W're using just one context in the dialplan the default one.

I'll turn the logging on and will post the results.

May VICIDIAL conflict with the installed asterisk-addons 1.2.9 (using for mysql realtime & cdr logging)?

I have not used asterisk-addons in a long time. I wouldn't think it would conflict, but that could be a possibility.

Problems like yours are usually caused by the call logging not working properly in some way, whether it is because of a callerID override somewhere or some kind of error.

With callerID override did you mean something like that?

exten => _00[1-7]X.,1,Set(CDR(accountcode)=${CALLERID(num)})
exten => _00[1-7]X.,2,Set(CALLERID(num)=0123456789)
exten => _00[1-7]X.,3,Set(CALLERID(name)=unknown)
exten => _00[1-7]X.,4,AGI(agi://127.0.0.1:4577/call_log)
exten => _00[1-7]X.,5,Dial(${TRUNKIAX}/${EXTEN:0},55,o)
exten => _00[1-7]X.,n,Hangup

orig CallerID in the Campaign ist set to a string (for billing purposes), becaus e vicidial can only use one context (as I know), and if its necessary to bill different campaigns to different users, we tried this do do in that way. Maybe there is not such a dirty billing solution possible?
to work with the carrier we have to set the callerid a number and char as shown above.

Well, there's the problem. remove the section where the name is changed and see if that fixes things. VICIDIAL depends on the callerIDname to track calls.

Well, you are right. Uncommenting the line with callerIDname solved both issues.
Thank you very much for your patience and your helpfulness.

No problem, glad you got it working. Let us know how your system is going after you've been up and running for a while.

It's actually possible to have VICIDIAL work with A2Billing. This way, you can have a billing solution for different clients using different campaigns.