CISCO CDR records - Failure to read a corrupt record

[annam]

TNG stops importing records as soon as it has to interpret a corrupt record or incorrect format that cannot be interpreted by the plugin. We solve this by guessing the error record, removing it from the file and restarting TNG.

Would it not be better to place the faulty record into "Rejected" folder?

[Belinda Frick]

The plugin has checks to see if it is a valid call data string. It however cannot cater for every possible variation, especially with a comma delimited file (no fixed values to check).

If you can provide various samples of the call data caused the failure, I can log it with development.