vicidial.org

Using GoAutoDial CE 2.0 RC2.

Everything is working properly and setup.

Now I need to modify the dial plan to allow for dynamic callerid's on outbound calls and transfers. Here is my dial plan.

exten => _101NXXNXXXXXX,1,AGI(bt-caller-id.php,L1,C2,${EXTEN:3})
exten => _101NXXNXXXXXX,n,Set(__BTCID=${RETURNID})
exten => _101NXXNXXXXXX,n,Set(__LINE1=${EXTEN:3})
exten => _101NXXNXXXXXX,n,Goto(${EXTEN:3},3)

exten => _102NXXNXXXXXX,1,AGI(bt-caller-id.php,L1,C1,${EXTEN:3})
exten => _102NXXNXXXXXX,n,Set(__BTCID=${RETURNID})
exten => _102NXXNXXXXXX,n,Set(__LINE1=${EXTEN:3})
exten => _102NXXNXXXXXX,n,Goto(${EXTEN:3},3)

exten => _NXXNXXXXXX,1,AGI(bt-caller-id.php,L2,,${EXTEN},${LINE1})
exten => _NXXNXXXXXX,2,Set(__BTCID=${RETURNID})
exten => _NXXNXXXXXX,3,Set(CALLERID(all)=${BTCID})
exten => _NXXNXXXXXX,n,AGI(agi://127.0.0.1:4577/call_log,${EXTEN})
exten => _NXXNXXXXXX,n,Dial(SIP/+1${EXTEN}@PROVIDER-SIP-A,,tTor)
exten => _NXXNXXXXXX,n,Hangup


As soon as the call is answered or shows answered status the DeadAGI runs as if the call was hung up, the agent doesn't receive a call, and it's never brought into the conference.

My assumption is this has something to do with call_log and the EXTEN being passed to it? However, when I move it into the different levels 101,102 it still has the same behavior.

Is there a link with more detailed information on how call_log functions or how to build more complex dial plans similar to what is being done here?

The reason I'm using 101 and 102 is this is how I will distinguish between C1 or C2 (campaign1 or 2) to determine which cid is being looked up from the agi.

Thanks!

This should be fun:

it's not a "call_log" function. It's an agi script listening on port 4577 (127.0.0.1:4577) on the localhost (which is of course the 127.0.0.1 portion of it). The /call_log, portion is merely a switch to log the call in addition to whatever else it may be doing.

so ... which script is listening on port 4577?

There are several scripts "running" in screens that are initiated at startup and "kept alive" which watch the system at all times and basically run the system. These are in your crontab entries and also available via

Code: Select all

screen -list

you'll need to check out what they do, find the one on 4577 and you will determine (most likely) that you have altered a variable and annoyed vicidial.

Our dynamic outbound callerid script just checks the asteriskdb table (internal, not sql) for a true/false value and changes the callerid NUMBER accordingly (callerid NAME is OFF-LIMITS as altering it will break vicidial ... in a fashion similar to what you are experiencing). ours is a single line in the dialplan that runs after the port 4577 call which initiates vicidial.

William,

Thanks for the reply. This fixed it by changing

CALLERID(all)

to

CALLERID(num)

That preserved the CID-NAME as to not break vicidial.

I'm still seeing DeadAGI going on after the conference is connected, but none of the calls drop and it seems to work....so not sure why those are getting triggered.

Thanks again for the insights,

CallCrazy

try the agi logs in /var/log/astguiclient and/or agi debug in asterisk.

also, for the future:

when you post, please post your entire configuration including (but not limited to) your installation method and OS with kernel or version, vicidial version and build, 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.

Similar to This:
Vicibox X.X from .iso | Vicidial X.X.X Build XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation

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)

GoAutoDial CE 2.0 RC2 | Vicidial 2.2.1-237 Build 100510-2015 | Asterisk 1.4.27.1-1 | Single Server | Sangoma A104D (not used configured) | phpmyadmin installed after installation.