thewraith2008
Member
- Joined
- Nov 22, 2016
- Messages
- 1,867
OK here is another thing I've recently noticed on a CAP+ network I found that seems to mainly send DATA.
I'm seeing unconfirmed rate 1/2 data blocks with a second proprietary header included where the CRC32 is not checking correctly after all blocks received. While I don't really expect to be able to decode this type of DATA (yet?), I'm wondering if this is using a RAS style of CRC check. (Voice that is rarely seen does not use RAS). At first, I though the CRC code I was using was not right but this seems OK with other networks I've seen with DATA been sent.
I've tested the DATA with the bad CRC in another CRC generator and it is giving the same bad CRC which make me thing the code is OK and something else is afoot.
Anyone else seen this?
I'm seeing unconfirmed rate 1/2 data blocks with a second proprietary header included where the CRC32 is not checking correctly after all blocks received. While I don't really expect to be able to decode this type of DATA (yet?), I'm wondering if this is using a RAS style of CRC check. (Voice that is rarely seen does not use RAS). At first, I though the CRC code I was using was not right but this seems OK with other networks I've seen with DATA been sent.
I've tested the DATA with the bad CRC in another CRC generator and it is giving the same bad CRC which make me thing the code is OK and something else is afoot.
Anyone else seen this?