No Customer Data

[ctc_olsen]

Hi. We just upgraded from GoAutodial CE 2.0 to 2.1 today. Everthing went fine just that in Campaign A, when doing an outbound call, the call goes through but there is no customer data on the agent screen. This is an old list from CE2.0.

I tried Campaign B, still with the old data before the upgrade, but the customer data loads fine here. I cannot find any relevant information at asterisk CLI. Help please?

[williamconley]

You failed to mention whether data does load when you use new data (I don't like to infer, I prefer to be certain). Also: when this occurred, was the server handling more than one call? (VMware and load = instability ...).

And (just to be funny), could you describe the steps taken to upgrade your database?

Also seriously consider using phpMyAdmin to compare data for a Newly uploaded lead vs an Old lead if the new ones are working properly.

And just to be funny: Consider upgrading to the latest SVN (which will kill your pretty goautodial styled screens, but give you many more tools you do not have at present ...).

Happy Hunting

[ctc_olsen]

You failed to mention whether data does load when you use new data (I don't like to infer, I prefer to be certain). Also: when this occurred, was the server handling more than one call? (VMware and load = instability ...).

Hi William. Thanks for replying. I just ran the test like 5 mins ago. I logged in as the only agent in this server. I create a new list, with new leads in Campaign A(the one with issues), the customer data pops up.

While in Campaign B, even with the old list/leads, the data pops up with no problems at all. I'm lost on where to look next.

And (just to be funny), could you describe the steps taken to upgrade your database?

I followed the steps here:
http://goautodial.org/projects/goautodi ... autodial21

[ctc_olsen]

I just found out that this only applies if the dial method is adapt average. I we choose manual, and the pop up loads fine even with the old lists. Something must be missing here.

[ctc_olsen]

A simple reboot resolved this. Whewwwww! Thanks.