Identifying protocol

Wichogg3 years ago

Hello all!!!!

I have checkd my tracker-server.log an got a response on port 5055 very similar to this thread:
https://www.traccar.org/forums/topic/help-identifying-protocol/

Did try with port 5023 and all other ports on this guide with no luck:
https://www.traccar.org/clones/

Out of this message, how can I figure out what port is my gps tracker using:

2021-02-26 10:52:00  INFO: [3F7620C3] connected
2021-02-26 10:52:00 DEBUG: [3F7620C3: 5055 < 190.106.212.32] HEX: 78780d010357857045068485000566830d0a
2021-02-26 10:52:00  WARN: [3F7620C3] error - empty text - IllegalArgumentException (...)
2021-02-26 10:52:00  INFO: [3F7620C3] disconnected

Thanks in advance for your time.

Anton Tananaev3 years ago

Port 5023 might be the right one.

Wichogg3 years ago

Thank you for your response.

I did try that port on my server and the log does not store any comunication; also try the same thing on demo server and it does not appear online.

the only port that saves some data is 5055, I notice a new warning message on my log:

2021-02-26 11:18:16  INFO: [5E3C7FD8] connected
2021-02-26 11:18:16 DEBUG: [5E3C7FD8: 5055 < 190.106.194.219] HEX: 78780a134006640001000b332f0d0a
2021-02-26 11:18:16  WARN: [5E3C7FD8] error - empty text - IllegalArgumentException (...)
2021-02-26 11:18:16  INFO: [5E3C7FD8] disconnected
2021-02-26 11:18:16  WARN: [5E3C7FD8] error - empty text - IllegalArgumentException (... < MainEventHandler:115 < *:104 < ... < GeocoderHandler:52 < ... < ExtendedObjectDecoder:52 < ...)
2021-02-26 11:18:31  INFO: [22ADB10F] connected
2021-02-26 11:18:31 DEBUG: [22ADB10F: 5055 < 190.106.212.112] HEX: 78780d010357857045068485000cfb420d0a
2021-02-26 11:18:31  WARN: [22ADB10F] error - empty text - IllegalArgumentException (...)
2021-02-26 11:18:31  INFO: [22ADB10F] disconnected
2021-02-26 11:18:48  INFO: [51736F3B] connected
2021-02-26 11:18:48 DEBUG: [51736F3B: 5055 < 181.174.88.15] HEX: 78780d010357857045068485000cfb420d0a
2021-02-26 11:18:48  WARN: [51736F3B] error - empty text - IllegalArgumentException (...)
2021-02-26 11:18:48  INFO: [51736F3B] disconnected
2021-02-26 11:19:03  INFO: [4724376E] connected
2021-02-26 11:19:03 DEBUG: [4724376E: 5055 < 181.174.68.224] HEX: 78780d010357857045068485000cfb420d0a
2021-02-26 11:19:03  WARN: [4724376E] error - empty text - IllegalArgumentException (...)
2021-02-26 11:19:03  INFO: [4724376E] disconnected
2021-02-26 11:19:20  INFO: [6D24B0B9] connected
2021-02-26 11:19:20 DEBUG: [6D24B0B9: 5055 < 190.106.213.70] HEX: 78780d010357857045068485000cfb420d0a
2021-02-26 11:19:20  WARN: [6D24B0B9] error - empty text - IllegalArgumentException (...)
2021-02-26 11:19:20  INFO: [6D24B0B9] disconnected
2021-02-26 11:19:35  INFO: [441F262E] connected
2021-02-26 11:19:35 DEBUG: [441F262E: 5055 < 181.174.68.9] HEX: 78780d010357857045068485000cfb420d0a
2021-02-26 11:19:35  WARN: [441F262E] error - empty text - IllegalArgumentException (...)
2021-02-26 11:19:35  INFO: [441F262E] disconnected
2021-02-26 11:19:52  INFO: [1EA7AD3C] connected
2021-02-26 11:19:52 DEBUG: [1EA7AD3C: 5055 < 190.106.195.18] HEX: 78780d010357857045068485000cfb420d0a
2021-02-26 11:19:52  WARN: [1EA7AD3C] error - empty text - IllegalArgumentException (...)
2021-02-26 11:19:52  INFO: [1EA7AD3C] disconnected

Is there a way to know if this unit is malfunctioning?
when I call the unit by voice it does return a SMS with current location.

Anton Tananaev3 years ago

Looks like you have an issue with geocoder. Disable that first.

Anton Tananaev3 years ago

Also, wrong port again. You have to use 5023.

Wichogg3 years ago

No luck with port 5023

Can you help me out if I point the device to demoserver IP 46.101.24.212 and port 5023?

Anton Tananaev3 years ago

What do you mean no luck? Have you done troubleshooting? If not, please do that before asking for further help.

Wichogg3 years ago

I have done troubleshooting, also I have two devices working corrrectly. the problem is this unit with seems to be a chinese one

Probably is a malfunctioning one...

Anton Tananaev3 years ago

Please post the results of the troubleshooting. Please details for each step.

SamS3 years ago

Hey Anton,
Greetings of the day. Kindly accept my sincerest apologies for bugging unrelated question.
I am looking for your kind attention towards my problem and couldn't find a way to connect with you.

https://www.traccar.org/forums/topic/position-fluctuations-constitute-towards-distance-in-summary/

Thanks in advance , will always be happy to oblige you.

Wichogg3 years ago

Step 1

Logs are stored but only devices using port 5055 are working and showing

2021-02-26 12:15:50  INFO: [02C53DEA] connected
2021-02-26 12:15:50 DEBUG: [02C53DEA: 5055 < 190.104.119.100] HEX: 504f5354202f3f69643d3530313031322674696d657374616d703d31363134333633333434266c61743d31342e383535343236266c6f6e3d2d39312e3534333234312673706565643d302662656172696e673d3026616c7469747564653d323339332e3039393332343934313633352661636375726163793d363526626174743d313720485454502f312e310d0a486f73743a203139302e3130362e3230332e3235303a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313230362044617277696e2f32302e312e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2021-02-26 12:15:50 DEBUG: [02C53DEA: 5055 > 190.104.119.100] HEX: 485454502f312e3120323030204f4b0d0a436f6e74656e742d4c656e6774683a20300d0a0d0a
2021-02-26 12:15:52  WARN: Geocoding failed - Empty address - GeocoderException (JsonGeocoder:74 < ...)
2021-02-26 12:15:52  INFO: [02C53DEA] id: 501012, time: 2021-02-26 12:15:44, lat: 14.85543, lon: -91.54324, speed: 0.0, course: 0.0
2021-02-26 12:16:04  INFO: [CC090284] connected
2021-02-26 12:16:04 DEBUG: [CC090284: 5055 < 181.174.87.139] HEX: 78780d010357857045068485000cfb420d0a
2021-02-26 12:16:04  WARN: [CC090284] error - empty text - IllegalArgumentException (...)
2021-02-26 12:16:04  INFO: [CC090284] disconnected
2021-02-26 12:16:18  INFO: [99C8D105] connected
2021-02-26 12:16:18 DEBUG: [99C8D105: 5055 < 181.174.69.243] HEX: 78780d010357857045068485000cfb420d0a
2021-02-26 12:16:18  WARN: [99C8D105] error - empty text - IllegalArgumentException (...)
2021-02-26 12:16:18  INFO: [99C8D105] disconnected
2021-02-26 12:16:21  INFO: [02C53DEA] disconnected

Step 2

There's no unknown device and HEX for wrong device is

2021-02-26 12:16:18 DEBUG: [99C8D105: 5055 < 181.174.69.243] HEX: 78780d010357857045068485000cfb420d0a
2021-02-26 12:16:18  WARN: [99C8D105] error - empty text - IllegalArgumentException (...)

This is why it seems be port 5023:
https://www.traccar.org/forums/topic/help-identifying-protocol/

Step 3

If I call the device it does return a SMS with location.

Step 4

Iam behind a firewall with proper security so online port tools will not show anything open, but I have opened ports:
5055
5001
5002
5006
5013
5015
5023
5036
5093
Other devices works fine with traccar

Step 5

I have try all of these ports and I this device only reply trough port 5055
I did send the fix command with unlimited number of replies.

Step 6

Pretty much similar as step #4

Anton Tananaev3 years ago

I don't really understand your comment on step 4. You tried port 5023 and you don't get any HEX for it, so this is clearly the issue here.

Wichogg3 years ago

Appreciate your help.

The port is open, I redirect an Apache web server and it works.

Will keep doing some tests and get back to this post.

Wichogg3 years ago

Hello Anton.

Again, appreciate all of your help with my problem.

I decided to format my entire server and updated to last version of traccar and now it works, gt06 protocol in port 5023

There are some errors on the log, the web server display the unit in online status and sometimes it gets offline, but the unit has some configuration regarding movment disconnection. 

2021-02-27 00:25:57  INFO: [638c94a7: gt06 < 181.174.68.30] HEX: 78781f1215021a0f3217ca0198053d09d24f42003c0002c002235e0012170003d7a40d0a
2021-02-27 00:25:57  INFO: [638c94a7: gt06 > 181.174.68.30] HEX: 787805120003903f0d0a
2021-02-27 00:25:57  INFO: [638c94a7] id: 357857045068485, time: 2021-02-26 15:50:23, lat: 14.85557, lon: -91.54322, course: 0.0
2021-02-27 00:25:57  WARN: [638c94a7] error - Connection reset by peer - IOException (...)
2021-02-27 00:25:57  INFO: [638c94a7] disconnected
2021-02-27 00:26:01  INFO: [f6f804a5] connected
2021-02-27 00:26:01  INFO: [f6f804a5: gt06 < 181.174.72.217] HEX: 78780d010357857045068485000654180d0a
2021-02-27 00:26:01  INFO: [f6f804a5: gt06 > 181.174.72.217] HEX: 787805010006ad630d0a
2021-02-27 00:26:02  INFO: [f6f804a5: gt06 < 181.174.72.217] HEX: 78781f1215021a0f3421c90198053d09d24f42003c0002c002235e0012170004c3d80d0a
2021-02-27 00:26:02  INFO: [f6f804a5: gt06 > 181.174.72.217] HEX: 787805120004e4800d0a
2021-02-27 00:26:02  INFO: [f6f804a5] id: 357857045068485, time: 2021-02-26 15:52:33, lat: 14.85557, lon: -91.54322, course: 0.0
2021-02-27 00:26:07  INFO: [f6f804a5: gt06 < 181.174.72.217] HEX: 78781f1215021a0f3921ca0198053d09d24f42003c0002c002235e0012170005d5e00d0a
2021-02-27 00:26:07  INFO: [f6f804a5: gt06 > 181.174.72.217] HEX: 787805120005f5090d0a
2021-02-27 00:26:07  INFO: [f6f804a5] id: 357857045068485, time: 2021-02-26 15:57:33, lat: 14.85557, lon: -91.54322, course: 0.0
2021-02-27 00:26:12  INFO: [f6f804a5: gt06 < 181.174.72.217] HEX: 78781f1215021a100035c90198053d09d24f42003c0002c002235e0012170006bbf20d0a
2021-02-27 00:26:12  INFO: [f6f804a5: gt06 > 181.174.72.217] HEX: 787805120006c7920d0a
2021-02-27 00:26:12  INFO: [f6f804a5] id: 357857045068485, time: 2021-02-26 16:00:53, lat: 14.85557, lon: -91.54322, course: 0.0
2021-02-27 00:26:17  INFO: [f6f804a5: gt06 < 181.174.72.217] HEX: 78781f1215021a100114c70198053d09d24f42003c0002c002235e001217000120a10d0a
2021-02-27 00:26:17  INFO: [f6f804a5: gt06 > 181.174.72.217] HEX: 787805120001b32d0d0a
2021-02-27 00:26:17  INFO: [f6f804a5] id: 357857045068485, time: 2021-02-26 16:01:20, lat: 14.85557, lon: -91.54322, course: 0.0
2021-02-27 00:26:22  INFO: [f6f804a5: gt06 < 181.174.72.217] HEX: 78781f1215021a10012dc80198053d09d24f42003c0002c002235e0012170002bddb0d0a
2021-02-27 00:26:22  INFO: [f6f804a5: gt06 > 181.174.72.217] HEX: 78780512000281b60d0a
2021-02-27 00:26:22  INFO: [f6f804a5] id: 357857045068485, time: 2021-02-26 16:01:45, lat: 14.85557, lon: -91.54322, course: 0.0
2021-02-27 00:26:27  INFO: [f6f804a5: gt06 < 181.174.72.217] HEX: 78781f1215021a100400cb0198053d09d24f42003c0002c002235e001217000301030d0a
2021-02-27 00:26:27  INFO: [f6f804a5: gt06 > 181.174.72.217] HEX: 787805120003903f0d0a
2021-02-27 00:26:27  INFO: [f6f804a5] id: 357857045068485, time: 2021-02-26 16:04:00, lat: 14.85557, lon: -91.54322, course: 0.0
2021-02-27 00:26:32  INFO: [f6f804a5: gt06 < 181.174.72.217] HEX: 78781f1215021a100432ca0198053d09d24f42003c0002c002235e0012170004ab5b0d0a
2021-02-27 00:26:32  INFO: [f6f804a5: gt06 > 181.174.72.217] HEX: 787805120004e4800d0a
2021-02-27 00:26:32  INFO: [f6f804a5] id: 357857045068485, time: 2021-02-26 16:04:50, lat: 14.85557, lon: -91.54322, course: 0.0
2021-02-27 00:26:33  WARN: [f6f804a5] error - Connection reset by peer - IOException (...)
2021-02-27 00:26:33  INFO: [f6f804a5] disconnected