Ronnie,
The size of the contact list is a little concerning. Yes they can index the outbound contact list (and in this case they definitely should).
Breaking the contact list up so that there is one per campaign does make sense, but there are multiple reasons why a customer would want to keep them in one table. For example, if they are automatically populating the contact list from a data source (not through Administrator/ICBM), they most likely use the single table as that is the easiest to program. Custom reporting could also be affected by using multiple contact list tables.
If you can give some examples of issues they're having we may be able to help in proposing solutions.
For your second question, I haven't seen any size limitations for the Dialer_Config.xml file, however the larger that it is, the longer it will take to load the information into the Dialer container. If possible, I would try to back up the file regularly to prevent any issues should something fail to load, or become corrupted.
Phil
------------------------------
Phil Chapman
Sr. Solution Engineer
Altivon
------------------------------
Original Message:
Sent: 11-27-2018 17:41
From: Ronnedith Padron
Subject: Contact list tables and Dialer Campaigns
Hello guys,
I'm working with a customer who is on 2016 R1, places about 3 millions calls per month, and has about 300 Campaigns pointing to the same contact lists (2) that have 1.8 millions records and the other one 1.5 millions records. My research, findings, experience and common sense says that they should have a single table/Contact list per Campaign in order to improve performance and resolve many of the issues they are experiencing but I wanted to get your input on this.
I also have the following questions.
1. Can the Outbound Contact list be indexed?
2. Is there a maximum recommended size for the Dialer_Config.xml file ?
Thank you.
#Outbound
------------------------------
Ronnie Padron
Sr. Genesys/ININ Consultant
ronnedith@yahoo.com
312-428-8613
------------------------------