Overview
The customer is experiencing an issue with incorrect CELL ID values in some Call Detail Records (CDRs), causing these records to be rejected at the Financial Management System (FMS) end. The problem lies in the field specific to Cell ID (Example: General32), where certain CELL ID values are not being converted from hexadecimal format to decimal format, but instead are being transferred as is.
Solution
The issue with incorrect CELL ID values in some Call Detail Records (CDRs) is due to the CELL ID not being converted from hexadecimal format to decimal format. The solution to this problem involves verifying the format of the 16-digit CELL ID with the upstream system. Validate the CELL ID field in the LLD/HLD solution documents. Here is an example specification for CELL ID:
- User location information in raw format
- Sample ASN correct format: 0104654888e83ec3
- MCC-MNC + LAC + CellID
- Cell ID Logic: Swap-nibble (MCCMNC) + hex2Dec (LAC) + hex2Dec (Cell ID)
The incorrect format being received is: 1832f451301f32f4. The upstream system needs to be checked for this incorrect format and corrected if necessary.
Summary
In conclusion, the issue with incorrect CELL ID values in Call Detail Records (CDRs) is due to the CELL ID not being converted from hexadecimal format to decimal format. The solution involves verifying the format of the 16-digit CELL ID with the upstream system and correcting it if necessary.
FAQ
- What is the cause of the incorrect CELL ID values in some Call Detail Records (CDRs)?
The issue is due to the CELL ID not being converted from hexadecimal format to decimal format. - What is the solution to this problem?
The solution involves verifying the format of the 16-digit CELL ID with the upstream system and correcting it if necessary. - What is the correct format for the CELL ID?
This is usually specified in the LLD/HLD solution documents shared with the customer. The correct format is: Swap-nibble (MCCMNC) + hex2Dec (LAC) + hex2Dec (Cell ID).
Comments
0 comments
Article is closed for comments.