Outbound Dialer Issue

[adignan]

I’ve noticed an issue with an Outbound Dialer/Blended Agent install. If the OutboundControl variable is set PREDICTIVE_(ONLY or BLENDED) or PROGRESSIVE_(ONLY or BLENDED) the call never actually rings through to the “customer” side. The dialer picks up the record and dials. The call gets delivered to the agent, the call is placed on hold at this time, however there appears to be no attempt to reach the “customer”. I have noticed the ECC variables(such as customer name and Contact #) are not coming through to the CISCO Outbound Option Agent Softphone. The softphone does shows the Mode correctly as “Predictive Outbound”, for example.

If the dialer is placed in PREVIEW or PREVIEW_DIRECT modes, then the outbound option functions as expected. The agent receives reservation call and upon acceptance the dialer actually dials the “customer” number and the call connects through. The ECC variables such as customer name and account number also appear as expected.

[b.hsu]

Try the following:

Change the dialer rotary-group configuration under the physical interface to match the already-configured dialer interface.

Configure a new dialer interface corresponding to the dialer rotary-group.

[adignan]

Turned out to be that there was only 1 agent in the outbound skill group and in the Campaign setup, overflow agents was set to 1 (default is zero). It wouldn't dialout in progressive or predictive cuz there were no overflow agents. Setting this back to zero fixed the issue.

[ciscogini]

When you use the outboundDialer for IVR Campaign with CVP, How do I pass the Customer Data to IVR to play.

Which ECC varibales

Thank you,

[geoff]

BAAccountNumber is the only way to tie the two together. I have this working and it's fine.

If you have your customer data in an external database, when you create the import file for the dialer to munge on, ensure you include the AccountNumber. When it calls the customer and they answer and it transfers the call to CVP, pass the BAAccountNumber from ICM down to your Audium application in the normal way (ToExtVXML array).

In your Audium application, pick up the BAAccountNumber and query your external database using the BAAccountNumber as the key and retrieve all the customer data required. This works very nicely.

Regards,

Geoff

[ciscogini]

Thnak you Geoff

[ciscogini]

Geoff,

Did you do a Translation Route to CVP when transferign the call to IVR or you used the RUN External Script Node.

I am trying to send the Customer Accoutn Number and I am sending the calls to CVP using RUN External Script, but I do not see any data ( BAAccount) information come accross.

[geoff]

With CVP 3.x, you need the trans route.

With CVP 4.x and ICM 7.1 you use the Type 10 Network VRU and only require the "Send To VRU" node.

Regards,

Geoff

[k.chemodanov]

Hello.

I have the like problem.

And how i have to configure trans route ?

WBR, Konstantin.

[ciscogini]

I have not yet done it. Probably Geff can answer your questions.

[telecomteam]

we are facing the issue with ICM Dialer as Side A is completely down, we have PCCE 12.5 Below is the error in the logs.

08:26:42:747 lb-CampaignManager Trace: Unable to read files from dir \\SBWPDCISAP001\OOHARepl\*.repl, error code 53
08:27:09:467 lb-CampaignManager Trace: (CM_PCB) No personal callback records available.
08:27:09:467 lb-CampaignManager Trace: (CM_PCB) RecordsRequest(): Before send records time: [0].
08:27:14:600 lb-CampaignManager Trace: (CM_DNC) DNC table keys 0 0 0 0
08:27:14:600 lb-CampaignManager Trace: (CM_DNC) keys are same, no changes
08:27:18:381 lb-CampaignManager The outbound HA replication failed. Possible reasons include incorrect logger hostname in setup, invalid user account/security group or partner logger not started.
08:27:18:381 lb-CampaignManager Trace: HA local Pending replication files: 42669 (total size: 161588 KB)
08:27:18:381 lb-CampaignManager Trace: Replication status: REPLICATION_STATUS_ERROR

[bill.king1]

You may want to create a fresh, new post with this, as the original one is almost 20 years old. Also, if you can provide more details such as if this is a new install, if it ever worked vs. if it stopped working after something happened, etc., for people to try and offer you suggestions. A larger snippet of the log (especially if it worked and then stopped) might be good too. Good luck.