vicidial.org

Hi Everybody,

DB Schema Version: 1315
DB Schema Update Date: 2012-03-20 03:33:24
VERSION: 2.4-362a
BUILD: 120316-1203
Hardware Specs:
quad core 3.2 8 GIG
8gig mem
Asterisk 1.4.39.2-vici

I am new to VICIDIAL. I work as a system/dialer operator and technical support. I was monitoring some of the calls in our US campaign. Our agent is now experiencing a lot of call hang-ups (but some of it are successful calls). By the moment our agent receives the call, after 5 seconds the system will prompt call hangup.

This US Camp is BLENDED with 2 more camps. One is NZ and HK. Our agent receives random calls from either. But these call hang-ups only happen with our US Campaign.

below is one of the call logs we saw during these calls:

ERROR[32298]: utils.c:967 ast_carefulwrite: write() returned error: Broken pipe
[Jul 2 09:14:23] -- AGI Script agi-VDAD_ALL_inbound.agi completed, returning 0
[Jul 2 09:14:23] -- Executing [010*000*000*042*8600051default:1] Goto("SIP/eastwest-000000fe", "default|8600051|1") in new stack
[Jul 2 09:14:23] -- Goto (default,8600051,1)
[Jul 2 09:14:23] -- Executing [8600051@default:1] MeetMe("SIP/eastwest-000000fe", "8600051|F") in new stack
[Jul 2 09:14:23] == Manager 'sendcron' logged off from 127.0.0.1
[Jul 2 09:14:24] == Spawn extension (default, 8600052, 1) exited non-zero on 'SIP/motiontelecomau-000000fa'
[Jul 2 09:14:24] -- Executing [h@default:1] DeadAGI("SIP/******-000000fa", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0---------------") in new stack
[Jul 2 09:14:24] -- AGI Script agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0--------------- completed, returning 0
[Jul 2 09:14:24] == Manager 'sendcron' logged off from 127.0.0.1
[Jul 2 09:14:32] == Spawn extension (default, 8600051, 1) exited non-zero on 'SIP/eastwest-000000fe'
[Jul 2 09:14:32] -- Executing [h@default:1] DeadAGI("SIP/eastwest-000000fe", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0---------------") in new stack


What is the meaning of the call log? I just like to know what could be the cause of these hang-ups.

Thank you so much and more power to VICIDIAL

Best Regards,
Joel

broken pipe is a misnamed notice which results when the log file is opened but nothing is written into it and then it is closed. the warning should not occur, but nobody is fixing it because most other applications only open the log if they have something to write ...

calls generally hang up at the "drop call seconds" setting for the campaign. Have you read the manual yet? And are you in compliance with the FCC regulations regarding drop calls?

Hi William,

Good day Sir! how can i get a manual? they (IT Staff) just taught me this vicidial when i entered here few months ago. they didn't give me a manual. Regarding the FCC regulations regarding drop calls. i see less than 3% of the total drop calls when i generate reports.

Thanks for your continued support,
Joel

Actually the error is caused because between asterisk 1.4.21.2 and asterisk 1.4.23 (with all the Dahdi changes), Digium made it so that if you connect into the manager interface or the AGI interface and issue a commend, but not stick around for a result it will throw that error. This does not cause any actual problems though. I fixed the manager events early on as it was easy to correlate then the ERROR message arrived and what was running at the time. It was much harder to figure out just what was causing the ERROR in the AGI scripts. While doing the Asterisk 1.8 work I was able to track these down. Once that has been submitted into the main code branch these errors will go away. In my 1.8 testing I have not had a single Broken Pipe ERROR since fixing that.

Now that's cool. Cuz that error is annoying. LOL