called_count to 65535

[Gregorio]

Greetings,

I'm wondering what conditions would cause the "called_count" field in the "vicidial_list" table to bump to 65535.

For us, it bumps to 65535 in a relatively short amount of time-- seemingly immediately after the lead is imported into the dialing list. These leads haven't even been called yet either.

(In case you're curious: Leads are being imported via generated export files, that get placed into the "LEADS_IN" directory)

OS: CentOS

Vicidial info:
VERSION: 2.0.5-164
BUILD: 90210-1042

Thanks

[mflorell]

This happens when you improperly format lead files.

Usually when you have too many fields and a large number is attempted to be entered into the call_count field, since 65500 is the largest value in MySQL for that field that is what it is set to.

[Gregorio]

Thanks. I believe we have fixed it.

There was a stray pipe, "|", getting thrown in with each lead.

Now, even before, the leads and all of their data seemed to get imported properly. And, placed into the proper fields.

It was only the "called_count" maxing out to 65535 that alerted us that there might be a problem. A message stating there was a malformed lead, or, too many fields would be nice.

Thanks again. I appreciate it.

[mflorell]

Well, having a number in that field is valid. If you would like to submit a patch to the lead loader please do so on the issue tracker.

[Gregorio]

Thank you