subscribe to our Youtube


4167 questions

4739 answers


0 members

We are migrating to our new platform at Moving forward, you can continue discussions on this new platform. This current platform will be temporarily maintained for reference purposes.
0 votes
in Vehicle tracking by anonymous

I am implementing a server which implements TCP/TLS communication. According to Codec 8 specification the preamble is composed by a short (two bytes) indicationg the length of the IMEI, followed by the IMEI itself.

I noted the swap of first two bytes containing the IMEI length in case of encryption enabled/disabled. The following pictures report the received buffer in the two situations.

Encryption NOT enabled

Encryption enabled

Is this a known issue? Is this related to endianess of the short indicating the IMEI length?

1 Answer

0 votes
by anonymous

We would like to analyze your case, therefore please open ticket in VIP Helpdesk and provide all needed information: device IMEI, firmware version, configuration file. If you don't have VIP Helpdesk login. please contact with your Sales Manager. If you don't have any contacts with our Sale managers, please contact with them on our official website and click on the "Contact Us" button. When you will click, please fill the form and submit it. Note: as a topic, please choose "Vehicle telematics".
Or you can send an e-mail with description of your situation to

Best Regards