Before you start on this, do you have an agent-based campaign working?
Make it progressive with no over-dialing and ensure that you have the scripting (routing and admin) worked out. Make sure you have correctly configured the campaign, the import and query rules etc, dialing times and all that junk completely sorted out and understood. Learn how the dumprt in the campaign manager works and make sure you understand all the colums in the trace that pops out of baDialer every 5 seconds. Make the font smaller and set the window wide so you see all of this. Use procmon to up the trace on the baDialer so you see the CTISVR and dialing events.
You should have a simple import file with one line, copying that to where import is watching and have it rename the file as .bak. Get a feel for how long it takes the dialer to call after dropping the import file in place. You will build on the dialer and must be working faultlessly.
Now to change the campaign to an IVR campaign, just edit that type, set it to have AMD, and then edit the skill group page. Make sure your agent is now logged out.
Set the number of ports you want to use (say 5) and add the route point.
If you look at the Dialer trace now, you will now see that it thinks 5 agents belong to this campaign and are ready to go. Those are your ports.
The route point must be owned by the JTAPI ICM PG user. When the dialer calls a customer and they answer, the other end is transferred to your route point and this should run a script. So you need to configure dialed numebr, call type, routing script.
The first thing you need to do is get the call over to the IVR with a trans route. I'm hoping you can whip out those trans routes in your sleep.
If your IVR is CVP, there is a lot more to do with the very tricky "Send to VRU" node - but I'm guessing you are using IPIVR. Correct?
So once it's been trans routed over to IP IVR, you can run your .aef application.
I tried with agent based campaign and I am having issues with it. The system just calls the agent and hangs up after two seconds. Even it is not calling the outside number, it just calls the agent and then hangs up.
not sure whats going on.
I will look the steps you mentined and try to check everythign again.
The system should be calling the customer, not the agent.
One thing I always like to do to start off is shutdown the Dialer and use dialogictest to call from the SCCP ports on the Dialer. Run this tool and let it see all your ports (channels). Make a call from each channel in turn to an outside number (the customer) to ensure that this part is configured correctly.
Then ensure all ports are associated with the ICM JTAPI user.
The Dialer is a bit tricky if all you've done is inbound. There are a few odd things in the setup to make it work that were borrowed from an inbound system.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.