Page 1 of 1

new called

PostPosted: Fri Mar 03, 2017 1:28 pm
by davide.filippi
Hi all,
what can you say me about "new called" leads?

Re: new called

PostPosted: Fri Mar 03, 2017 2:01 pm
by williamconley
likely bad dialplan in admin->carriers OR you have phone numbers with the wrong number of digits. if the numbers don't match the dialplan pattern, they get 'lost'. you can put an "s" extension in to catch the bad numbers and terminate them. just put in an s entry like this into ONE of your live carriers:
Code: Select all
exten=> s,1,AGI(agi://127.0.0.1:4577/call_log)
exten=> s,n,NoOp(No Dial Pattern Matches This Extension)
exten=> s,n,Hangup

Re: new called

PostPosted: Fri Mar 03, 2017 2:54 pm
by davide.filippi
This is how actually look my dialplan and the numbers have the correct number of digits.
Also, if i call a number "new called" with my phone, it ringing

exten => _49639[03]Z.,1,Dial(sip/${EXTEN:3}@__serverip__,60,Tto)
exten => _49639[03]Z.,n,Hangup()

exten => _47739[03]Z.,1,Dial(sip/${EXTEN:3}@__serverip__,60,Tto)
exten => _47739[03]Z.,n,Goto(s-${DIALSTATUS},1)
exten => s-FAILED,1,Playback(failed)
exten => s-CANCEL,1,Playback(failed)
exten => s-BUSY,1,Playback(busy)
exten => s-CHANUNAVAIL,1,Playback(failed)
exten => s-CONGESTION,1,Playback(failed)
exten => _47739[03]Z.,n,Hangup()

Re: new called

PostPosted: Fri Mar 03, 2017 3:18 pm
by williamconley
Then your entire dialplan entry is wrong. Delete it and start over. Did you read the Vicidial Manager's Manual regarding dialplan entries?

Since you've never had a functional autodialing Vicidial system, you should start at the first page of the Vicidial Manager's Manual (Free version available on EFLO.net). Don't skip any pages.

Every carrier entry must have three lines: one has an agi script. Then comes the "dial" line. Then the hangup line. Trying to do this without the manual is a huge waste of time. Educational, to be sure, but do you have a few months to re-invent Vicidial? lol

Re: new called

PostPosted: Sat Mar 04, 2017 4:31 am
by davide.filippi
This dialplan was used before i start work there.
The "new called" problem is not for all numbers.

You mean that my dialplan have to look like

exten => _49639[03]Z.,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _49639[03]Z.,n,Dial(sip/${EXTEN:3}@__serverip__,60,Tto)
exten => _49639[03]Z.,n,Hangup()

exten => _47739[03]Z.,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _47739[03]Z.,n,Dial(sip/${EXTEN:3}@__serverip__,60,Tto)
exten => _47739[03]Z.,n,Goto(s-${DIALSTATUS},1)
exten => s-FAILED,1,Playback(failed)
exten => s-CANCEL,1,Playback(failed)
exten => s-BUSY,1,Playback(busy)
exten => s-CHANUNAVAIL,1,Playback(failed)
exten => s-CONGESTION,1,Playback(failed)
exten => _47739[03]Z.,n,Hangup()

where exten _496 is used for predictive call and _477 for manual call.

Re: new called

PostPosted: Sat Mar 04, 2017 4:46 am
by williamconley
You have a pathway (manually dialed calls) that could end without a "hangup" line. Note that the hangup line invokes the hangup script which tells the agi (attached in the first line) that the call has ended and activates all the logging routines and call handling information scripts in Vicidial.

There must ALWAYS be a hangup line. On all pathways.

Plus: What about "s" without a fail status? the Catch-all that accepts and kills malformed numbers (too many digits? impossible dials?). This is useful to avoid "losing" those that do not match a dialplan. Without it, the Vicidial agi is never attached, and Vicidial simply assumes that the all is going to happen ... some day. And it waits. Patiently. While your system stops dialing, of course, because it's waiting. 8-)

Re: new called

PostPosted: Sat Mar 04, 2017 5:29 am
by davide.filippi
First of all thank you for explain me that.

What about the predictive path? It is correct?

for the _477 exten you mean this?

exten => _47739[03]Z.,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _47739[03]Z.,n,Dial(sip/${EXTEN:3}@__serverip__,60,Tto)
exten => _47739[03]Z.,n,Goto(s-${DIALSTATUS},1)
exten => s-FAILED,1,Playback(failed)
exten => s-FAILED,n,Hangup()
exten => s-CANCEL,1,Playback(failed)
exten => s-CANCEL,n,Hangup()
exten => s-BUSY,1,Playback(busy)
exten => s-BUSY,n,Hangup()
exten => s-CHANUNAVAIL,1,Playback(failed)
exten => s-CHANUNAVAIL,n,Hangup()
exten => s-CONGESTION,1,Playback(failed)
exten => s-CONGESTION,n,Hangup()
exten => _47739[03]Z.,n,Hangup()

You suggest me to create a carrier for exten _496 only and a carrier for exten _477 only?

Re: new called

PostPosted: Tue Mar 07, 2017 5:31 am
by davide.filippi
...wrong number of digits...

Is there a minimum/maximum number of digits?

Re: new called

PostPosted: Thu Mar 09, 2017 6:11 am
by davide.filippi
When i make call with the new extensions

exten => _49639[03]Z.,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _49639[03]Z.,n,Dial(sip/${EXTEN:3}@__serverip__,60,Tto)
exten => _49639[03]Z.,n,Hangup()

exten => _47739[03]Z.,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _47739[03]Z.,n,Dial(sip/${EXTEN:3}@80.90.90.254,,Tto)
exten => _47739[03]Z.,n,Goto(s-${DIALSTATUS},1)
exten => s-FAILED,1,Playback(failed)
exten => s-FAILED,n,Hangup()
exten => s-CANCEL,1,Playback(failed)
exten => s-CANCEL,n,Hangup()
exten => s-BUSY,1,Playback(busy)
exten => s-BUSY,n,Hangup()
exten => s-CHANUNAVAIL,1,Playback(failed)
exten => s-CHANUNAVAIL,n,Hangup()
exten => s-CONGESTION,1,Playback(failed)
exten => s-CONGESTION,n,Hangup()
exten => _47739[03]Z.,n,Hangup()

sometimes appear a popup that say
DIAL ALERT:
Call Rejected: BUSY
Cause: 17 - User busy

Is there a way to not show this?

Re: new called

PostPosted: Sun Mar 19, 2017 3:10 pm
by williamconley
davide.filippi wrote:When i make call with the new extensions

exten => _49639[03]Z.,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _49639[03]Z.,n,Dial(sip/${EXTEN:3}@__serverip__,60,Tto)
exten => _49639[03]Z.,n,Hangup()

exten => _47739[03]Z.,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _47739[03]Z.,n,Dial(sip/${EXTEN:3}@80.90.90.254,,Tto)
exten => _47739[03]Z.,n,Goto(s-${DIALSTATUS},1)
exten => s-FAILED,1,Playback(failed)
exten => s-FAILED,n,Hangup()
exten => s-CANCEL,1,Playback(failed)
exten => s-CANCEL,n,Hangup()
exten => s-BUSY,1,Playback(busy)
exten => s-BUSY,n,Hangup()
exten => s-CHANUNAVAIL,1,Playback(failed)
exten => s-CHANUNAVAIL,n,Hangup()
exten => s-CONGESTION,1,Playback(failed)
exten => s-CONGESTION,n,Hangup()
exten => _47739[03]Z.,n,Hangup()

sometimes appear a popup that say
DIAL ALERT:
Call Rejected: BUSY
Cause: 17 - User busy

Is there a way to not show this?

Sure. Autodial instead of Manual Dial. But when an agent manually dials, they must be given some sort of response when the call fails since there's often no audible response.

Failing that, of course, you can alter the code on the page ... but honestly you're likely so far into micro-managing at this point instead of making money I'm not sure there's any way to bring you back from the brink. lol.

Autodial, dude. Seriously.

davide.filippi wrote:
...wrong number of digits...

Is there a minimum/maximum number of digits?

I didn't say "too many" nor "too few". I said wrong number. It has to match.