Server not receiving data in actual port

Hello,

I am trying to configure a device. It uses AVL102 protocol for message transfer and format and this protocol seems to have been already implemented in traccar in port 5007 with protocol named totem. But if the device is configured to send messages in port 5007, server doesn't receive any data. However server can receive data, if I configured device to send messages in port 5001 but obviously cannot decode the message. I have already confirmed that port 5007 is open. Its kind of weird and cannot think of why a device is not sending messages to one open port while it was able to send to another open port.

Thanks.

Can I see some HEX data samples?

Here's the HEX sample, I got when device is configured with port 5001.

2016-11-20 13:37:13 DEBUG: [A3AB1ACA: 5001 < 223.186.42.175] HEX: 242442343836373936353032303730383736307c4141244750524d432c3035353635312e30302c412c313332352e35393632332c4e2c30373530302e31333236362c452c302e3030302c2c3230313131362c2c2c412a37437c312e39357c312e30347c312e36367c3030303030303030303030307c32303136313132303035353635337c31343135313235317c30303030303030307c32464339413737387c303030307c302e303030307c303238387c463344300d0a
2016-11-20 13:37:15 DEBUG: [A3AB1ACA: 5001 < 223.186.42.175] HEX: 242442343836373936353032303730383736307c4141244750524d432c3035353635352e30302c412c313332352e35393632332c4e2c30373530302e31333236362c452c302e3030302c2c3230313131362c2c2c412a37367c312e39357c312e30347c312e36357c3030303030303030303030307c32303136313132303035353635357c31343135313235317c30303030303030307c32464339413737387c303030307c302e303030307c303238397c374635450d0a

You are right that it's Totem protocol, so port 5007 should work. If you don't see any HEX data on port 5007, it probably means that you are doing something wrong. Is it possible that your device uses UDP protocol and not TCP?

Sorry for delayed response. I just confirmed that the device is using TCP whereas the device has an option to choose UDP or TCP.

Now GPS has started sending feed. It took an hour to send feeds after changing to TCP protocol. So please just ignore my above message. And thank you very much for your support.

Good to know that it has both options. We might need to add UDP support for Totem protocol.