Adhearsion, Vicidial and Screen-pops

[jsgoecke]

I have a user that would like to use Adhearsion to drive a database-driven IVR system and then transfers calls to a Vicidial agent. The hope here is to be able to have a simple call context with one line:

[ahn-context]
exten => _X.,1,AGI(agi://localhost)

That would hit an Adhearsion process running on another box to do its thing. Adhearsion would then add a custom channel variable to that call and issue a redirect over AMI to send it on its way to the appropriate Vicidial context to go through the queues and hit an agent.

What are the issues I would have to think about here? Is this a problem, is there a 'custom' extensions.conf like in FreePBX? Also, may Vicidial easily pick up a custom channel variable, say with account number, and pass that down to the agent as a 'screen-pop'?

[mflorell]

ViciDial currently doesn't use channel variables at all, but it would not be difficult to add something like that to the inbound call handling script.

As for the extensions.conf, vicidial does generate an extensions-vicidial.conf as of 2.0.5, and in SVN trunk we have database-generated call menus(IVRs) that go into that file as well.

[jsgoecke]

ViciDial currently doesn't use channel variables at all, but it would not be difficult to add something like that to the inbound call handling script.

As for the extensions.conf, vicidial does generate an extensions-vicidial.conf as of 2.0.5, and in SVN trunk we have database-generated call menus(IVRs) that go into that file as well.

Great on both counts. So I may have one custom context to do the IVR stuff and then modify it to pull of a channel variable. How does the IVR collect data now to be delivered as a screen-pop? Is there something to attach data to the proxy for that call object?

[mflorell]

The Call Menus are not really IVRs, they do not collect data at this point, although there are options for calls going into in-groups(our version of a queue) to collect data from the caller.

To get data from a channel variable shouldn't be a problem for calls going into the in-groups, it will just require a little simple modification of the ALL_inbound AGI script.