" /> Dynamic Calling List , Outbound - Genesys CTI User Forum
« previous next »
Pages: [1]   Go Down

Author Topic: Dynamic Calling List , Outbound  (Read 4260 times)

This topic contains a post which is marked as Best Answer. Press here if you would like to see it.

Charly_uk

  • Guest
Dynamic Calling List , Outbound
« on: January 01, 1970, 12:00:00 AM »
Advertisement
Hello, we are in the process of setting up Outbound for Genesys 6.x

Our Problem now is , that our Calling List is dynamic. The data is coming as
an Snapshot from the Mainframe every 10 Minutes and then the Calling List has to be
updated.

Is their another way to update the calling list instead of the “Userdata Method” and have somebody
an example please how to do that with the attached Data.

Thanks in Advance

Logged

Mark Newcomb

  • Guest
Dynamic Calling List , Outbound
« Reply #1 on: January 01, 1970, 12:00:00 AM »
You could just insert directly into the list using sql. However be warned if you update the list direct that you need to play with the caching parameters in the configuration........
Logged

Vic

  • Guest
Dynamic Calling List , Outbound
« Reply #2 on: January 01, 1970, 12:00:00 AM »
Can you do it for a calling list in an active campaign???
Logged

Charly_uk

  • Guest
Dynamic Calling List , Outbound
« Reply #3 on: January 01, 1970, 12:00:00 AM »
I don’t think it will work, to many “Not Null” Fields in the Calling Table.
Logged
Marked as best answer by on Today at 10:15:39 PM

Mark Newcomb

  • Guest
Dynamic Calling List , Outbound
« Reply #4 on: January 01, 1970, 12:00:00 AM »
  • Undo Best Answer
    • Hi Vic,

    yes you can, we do it all the time with an abandoned call monitoring solution we designed. The only issue you have is that list manager / OCS caches records when a campaign is running in any of the dialling modes. The only way around it is to set the min_record_buf_size and opt_record_buf_size both to 0. Unfortunately this setting is global in Outbound 5.1 this will mean that ALL running campaigns will no longer cache and the database will be hit every single time genesys decides to make a dial. However in 6.5 [I have been informed by Genesys] this is now a setting you can relate to a campaign group and hence restrict it to just the calling lists you want to.

    Hope this helps!
    Mark
    Logged
    Pages: [1]   Go Up
    « previous next »