We have over 40,000 devices using Quectel MC25 modules. They worked fine until our GSM operator started enforcing A5/3 ciphering.
After upgrading to firmware MC25MBR01A24, devices still fail to register. Some report as “powered off,” others say “call not possible.” We suspect MC25 may not support A5/3.
Does MC25 support A5/3 ciphering at all? Is there any way to enable it (special firmware, AT commands)?
We can’t replace hardware at this scale, so any workaround or help is appreciated.
A5/3 is a GSM encryption algorithm based on the Kasumi block cipher. It’s more secure than A5/1 and A5/2, and many network operators are now enforcing it due to regulatory or security reasons.
In our case, the mobile operator has started enforcing A5/3-only ciphering on their 2G/GSM network — meaning that any device that does not support or cannot negotiate A5/3 cannot register on the network anymore.
Before this change, our MC25 modules worked fine. But now, even after updating to firmware MC25MBR01A24, they can’t register anymore. We suspect the module either doesn’t support A5/3, or the feature is not enabled.
So to clarify:
Does the MC25 module support A5/3 encryption for GSM ciphering?
If yes, is there a way to enable or confirm that capability via firmware or AT commands?
Hello everyone. I have the same problem. Many of our products are based on QUECTEL MC25MB module and all of them failed right after our operators implemented GSM A5/3 encryption mode. Since the GSM/GPRS baseband SoC inside MC25 module is RDA8955L, I need to know if this chip has hardware encryption engine for A5/3? Also I need to know which GPRS encryption modes (GEA1, GEA2 and GEA3) are supported by this chip? The RDA8955L chip information and reference manual documents are confidential and not available to the public. This problem is very important and I expect QUECTEL to respond. Thanks.
Does MC25 support A5/3 ciphering at all?