RESOLVED: Origination CANCEL

[friendlysol]

Our carrier has given me a list of all calls that have been marked as "failed" since we are getting a high call failed count.

70% of the failed calls are with status "Origination CANCEL".

I verified that this means the call was hanged up by us before anyone answered the call. Any ideas why vicidial would "cancel" the call ? and if for a valid reason, is there a setting to increase the time before vicidial cancels the call ?

I check the lead history and I see the TSR to be VDAD and the hangup reason as "NONE"

Length of the call is 0.

[mflorell]

You are looking for the "Dial Timeout" campaign setting.

[friendlysol]

!@$%@#%!@$%!@#$ !

I decreased it to 40 sec from 60 and I was able to bring my dial level from 30 to 10 and everyone is on the phone !

WOW.

[williamconley]

that's funny. we cover that in training with every server we ship.

in addition to "available only tally = Y" unless you have more than 30 agents and are in Adapt mode, and drop seconds to 2 or 0 instead of 5.

And a few others.

But those are just opinions. Interesting how that worked out though.

[naveed6865]

Hi guys,

I am facing this issue of more number of CANCELS on inbound campaign in multi server setup. I have checked all settings of campaign and those are correct and in asterisk logs before CANCEL i see this line

[Aug 17 13:39:29] ERROR[32148]: utils.c:1446 ast_careful_fwrite: fwrite() returned error: Broken pipe

Please note that this is error not warning, so we cant ignore this like WARNING message, some thing really happening bad thats why asterisk is reporting error and due to which out dialing pace is slow now, Please advise what could be issue?

Regards

Naveed

[williamconley]

Hi guys,

I am facing this issue of more number of CANCELS on inbound campaign in multi server setup. I have checked all settings of campaign and those are correct and in asterisk logs before CANCEL i see this line

[Aug 17 13:39:29] ERROR[32148]: utils.c:1446 ast_careful_fwrite: fwrite() returned error: Broken pipe

Please note that this is error not warning, so we cant ignore this like WARNING message, some thing really happening bad thats why asterisk is reporting error and due to which out dialing pace is slow now, Please advise what could be issue?

Regards

Naveed

1) Welcome to the Party!

2) As you are obviously new here, I have some suggestions to help us all help you:

When you post, please post your entire configuration including (but not limited to) your installation method (7.X.X?) and vicidial version with build (VERSION: 2.X-XXXx ... BUILD: #####-####).

This IS a requirement for posting along with reading the stickies (at the top of each forum) and the manager's manual (available on EFLO.net, both free and paid versions)

You should also post: Asterisk version, telephony hardware (model number is helpful here), cluster information if you have one, and whether any other software is installed in the box. If your installation method is "manual/from scratch" you must post your operating system with version (and the .iso version from which you installed your original operating system) plus a link to the installation instructions you used. If your installation is "Hosted" list the site name of the host.

If this is a "Cloud" or "Virtual" server, please note the technology involved along with the version of that techology (ie: VMware Server Version 2.0.2). If it is not, merely stating the Motherboard model # and CPU would be helpful.

Similar to This:

Vicibox X.X from .iso | Vicidial X.X.X-XXX Build XXXXXX-XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation | Intel DG35EC | Core2Quad Q6600

3) That error message is misnamed. It shouldn't even be a notice. It is telling you that you opened a log file, and then didn't log anything. This is not just normal, it's expected, but the interaction of perl, agi, and the OpenSuSE OS combines to make the system lie. One day someone will recompile the system with that as a Notice and people will stop asking this question (which has been asked and answered hundreds of times).

4) You stated that your problem is with an inbound campaign. But your complaint regards outbound calls. This is a bit of a contradiction: I'll assume for the rest of this that your intent was to say that this is a Blended campaign with both inbound and outbound and you are experiencing problems with the outbound portion of the campaign.

5) Cancels are caused by the Vicidial system determining that the call has been in an active state for too long and terminating the call even though the carrier has not returned a termination reason or an answer status. There are many causes for this. You should test some of these calls which you believe should not have canceled (samples) and determine if the carrier is screwing up, or if your carrier or campaign settings are wrong. All are possible.

6) Happy Hunting!

[call0]

Hi Will. I just want to ask if what's wrong with this. The situation is that were having good time taking calls minutes ago then suddenly all the calls[100%] are canceled. CLI showed me this Warning.


[Nov 16 05:41:40] WARNING[1590]: chan_sip.c:4068 retrans_pkt: Retransmission timeout reached on transmission 1a54558357dba3382129926c7c5371fa@120.72.20.110:5060 for seqno 102 (Critical Request) -- See https://wiki.asterisk.org/wiki/display/ ... nsmissions
Packet timed out after 32000ms with no response
[Nov 16 05:41:40] WARNING[1590]: chan_sip.c:4092 retrans_pkt: Hanging up call 1a54558357dba3382129926c7c5371fa@120.72.20.110:5060 - no reply to our critical packet (see https://wiki.asterisk.org/wiki/display/ ... nsmissions).

Could this be at the Carrier side? Just wanna make sure.

Thanks in advance as always.

ISO: ViciBox_v8_1.x86_64-8.1.0
Vicibox v.8.1.0 180922
VERSION: 2.14-694a
BUILD: 181005-1738
ASTERISK: 13.21.1-vici
openSUSE Leap 42.3
Kernel 4.4.159-73 default (tty1)

no additional software installed | 8GB mem | intel core i5

[williamconley]

Firewall. Take it down to test. Put it back up immediately. Of course, it could also be that you lost internet or your carrier went down. Try another carrier. If you don't HAVE another carrier, Get One Now. Two carriers is a requirement even if only to test once in a while. Usually no monthly cost so it's silly not to have one.

[dspaan]

Maybe ports 10000-20000 are blocked for a specific host?

[call0]

Of course, it could also be that you lost internet or your carrier went down. Try another carrier. If you don't HAVE another carrier, Get One Now. Two carriers is a requirement even if only to test once in a while. Usually no monthly cost so it's silly not to have one.

Firewall and internet connection are good. And yes, we don't have any other carrier. We'll get another one. Thanks for the advice Will.