When Chorus finds an invalid IMEI, it attempts to decode it (from hex to binary) to see if they are valid once decoded – this is in order to handle some of the formats seen in RDHI data.
However, we have been recently made aware of instances in Three data where the target IMEI has a “F” on the end (thus making it an invalid IMEI). These IMEIs can be decoded by removing the “F”, as Three have confirmed it means nothing. We will incorporate this decoding into our rules to ensure this scenario is decoded correctly in future. This fix will be included in the next release of Chorus.
In the interim, please bear in mind if you have data where the target IMEI has a “F” on the end then Chorus may not be processing correctly – we advise checking your data carefully.
If you have any queries regarding this or require any further information then please contact our support team at [email protected] or call 020 3597 7350.
