Page 1 of 1
Breaking NO ANSWER AUTO DIAL
Posted:
Wed Jul 25, 2007 5:07 pm
by binbash
We are having a lot of NO ANSWER AUTODIAL. I want to know if that's normal ?
The DIAL TIMEOUT is 28 seconds ... installed AMD on it and adjusted the amd.conf according to recommended amd standards.
IS THERE a way that we can BREAK the NO ANSWER AUTODIAL in order to identify, which percentage belongs to BUSY,RING NO ANSWER, and the rest.
For REPORT Purposes and to better understand the leads if they are good
or not.
THanks
Posted:
Thu Jul 26, 2007 8:50 am
by mflorell
This depends on your carrier and what codes they send you.
No answer auto dial are simply the calls that do not send an Answer signal and time out. (Invalid/Disconnect/Ring-no-answer).
Posted:
Thu Jul 26, 2007 11:29 am
by aster1
I think its fine to have lot of No ANSWER AUTO DIAL since you have very short dial timeout .. Most of calls after this timeout goes to answering machine anyway .. You can try increasing dial timeout and you will have few no answer auto dial's but lot of answering machines
Posted:
Thu Jul 26, 2007 4:45 pm
by enjay
Also keep in mind the quality of your list can be to blame.
Posted:
Thu Jul 26, 2007 8:30 pm
by binbash
So we can do some programming on it in order that calls don't just go to NO ANSWER AUTODIAL ?
We can add codes on it so that if the carrier gave INVALID .. then i can setup a report that goes to INVALID ?
But is that hardwork , .. i mean .... since you made vicidial.
Posted:
Fri Jul 27, 2007 12:27 am
by aster1
I dont see where is it vicidial's or asterisk's fault if your leads are not good and carrier is sending back INVALID or so . Btw what is the problem with NO ANSWER AUTO DIAL ... set your dial timeout to 60 then i am sure you will get very few no answer auto dial ..
Posted:
Fri Jul 27, 2007 9:26 am
by mflorell
The problem is that some carriers do not send out proper codes, and it also depends on if you are using SIP/IAX/T1 as your outgoing lines. Some carriers do not send the proper termination codes when a call ends because it was an invalid number, ditto for Disconnected. Some carriers play a ringing sound for 5 rings before telling you that the number is dicsonnected, some play the SIT tone, some do not. It's all very inconsistent and there is no way to guarantee accuracy in today's USA telephone system.
Posted:
Fri Jul 27, 2007 11:48 am
by binbash
Aster1 ...
If you recommend that a dial time out be 60, .. what would be your recommended settings for AMD.conf currently ... i've set it to default. and have followed the settings on the MANAGER MANUaL.
But seems like a lot of answering machine calls pass the detection and to the agents side.
Thanks
Posted:
Fri Jul 27, 2007 2:16 pm
by aster1
Dont take me wrong i am not recommending dial timeout to be 60
I am just suggesting that you will have lot of "no answer auto dial" if you have dial timeout of 28 seconds . This infact might be a good thing since asterisk disconnects the call if no one picks up in 28 seconds or else in most cases calls will go to customer's answering machines anyway ( and to AMD() in asterisk which may or may not detect it as answering machine
)
Posted:
Sat Jul 28, 2007 1:20 pm
by Vigi
See if your csv column that contains phone numbers is formatted as text... it happened to me it took me 2 days to figur it out.... i had 16 calls simoultanoeusly and no freakin answer ... it was formatted as text and the numbers had a "space" in front of each digit.
Check this i hope it helps
Posted:
Mon Jul 30, 2007 10:50 am
by binbash
Thanks VIGI, .. i'll go check that out, ... could be a reason.
that's a nice tip.
But question though ,... i was checking out the columnproperty but it's a varchar .. regardless if it was a text, should it matter ???