Troubleshooting Incorrect 'Start Date' in Parsed Call Detail Records (CDRs) For VMIPL

Overview

The issue pertains to the parsing of Call Detail Records (CDRs), specifically the 'Start Date' column. In some instances, the parsed CDRs do not match the raw CDRs from the switch, with the date being replaced by a '4' value. This inconsistency suggests a problem with the upstream data source. The date format in the raw CDRs should match the expected format specified in the Parsing Service configuration to avoid such discrepancies.

Recording: Explaining the issue

Ticket: 4116397

Solution

1. Check with the upstream data source to confirm the discrepancy in the 'Start Date' column.
2. 
3. The customer need to verify the source from the upstream team
4. Ensure that the date format in the switch raw CDRs is consistent and matches the expected format specified in the Parsing Service configuration.
5. If there is a mismatch in the date format, correct it to avoid discrepancies in the 'Start Date' column.

Summary

The issue with the 'Start Date' column in the parsed CDRs not matching the raw CDRs from the switch was identified to be originating from the upstream data source. The customer was advised to check with the upstream data source and ensure the date format in the raw CDRs matches the expected format in the Parsing Service configuration.

FAQ

1. What could cause the 'Start Date' in the parsed CDRs to not match the raw CDRs from the switch?
   This could be due to a discrepancy in the upstream data source or a mismatch in the date format between the raw CDRs and the expected format in the Parsing Service configuration.
2. What should I do if the 'Start Date' in the parsed CDRs does not match the raw CDRs from the switch?
   You should check with the upstream data source and ensure the date format in the raw CDRs matches the expected format in the Parsing Service configuration.
3. What happens if the date format in the raw CDRs does not match the expected format in the Parsing Service configuration?
   If there is a mismatch in the date format, it could cause discrepancies in the 'Start Date' column of the parsed CDRs.