SMS replies for some commands

  • 1
  • Problem
  • Updated 2 years ago

Using this device http://www.amazon.com/Floureon-OBD-GPS-Positioning-Diagnostic/dp/B017R6NT34?ie=UTF8&psc=1&re...

With a Tracfone SIM card it all works and responds with correct messages.

With an Aeris SIM card, only some of the SMS commands work. Basically the shorter responses.

I am stuck and do not know how to proceed. The messages all get delivered to terminal but I do not get a response back. How can I debug this further?

Does support have a way of testing an SMS send receive?

Thank you,

Dave

Photo of Dave Anderson

Dave Anderson

  • 11 Posts
  • 0 Reply Likes

Posted 2 years ago

  • 1
Photo of Bob Heckmann

Bob Heckmann, Official Rep

  • 349 Posts
  • 12 Reply Likes
Hi Dave,

To be sure we understand your issue correctly can you please detail the steps you're taking and the result you're expecting?

Regards,
Bob
Photo of Dave Anderson

Dave Anderson

  • 11 Posts
  • 0 Reply Likes

Thanks for responding Bob.

This device uses SMS only to receive commands and send responses. No GPRS involved.

If I use a Tracfone SIM card in the device I can send two commands and get responses (I am keeping this focused, there are of course more commands).

1. If I send LANG,0# I get back a response of SET LANG OK.EN

2. If I send STATUS# I get back a response of BATTERY:100%, GSM Signal:HIGH, and 5 additional status items.

If I use an Aeris SIM card and the Aeris API

1. If I send LANG,0# I get back a response of SET LANG OK.EN no problems at all with this one.

2. If I send STATUS# I do not get back a response at all via longpoll.aerframe.aeris.com

The SMS message looks like it got delivered ok. The Json reponse includes: "deliveryStatus":"DeliveredToTerminal"


The first call to longpoll.aerframe.aeris.com returns:

{"deliveryInfoNotification":[{"callbackData":"testApp1-mt-delivery","deliveryInfo":[{"address":"IMSI","deliveryStatus":"DeliveredToTerminal","link":[{"rel":"MTMessageRequest ResourceUrl","href":"https://api.aerframe.aeris.com/smsmessaging/v2/accountId/outbound/AITC/requests/requestID"},{&q... ResourceUrl","href":"https://api.aerframe.aeris.com/smsmessaging/v2/accountId/outbound/AITC/subscriptions/subscriptionID&...}

The second call to longpoll.aerframe.aeris.com returns:

{"deliveryInfoNotification":[],"inboundSMSMessageNotification":[]}

At first I thought it was because I was requesting a response to early (the device takes about 20 seconds to send a response to STATUS# via Tracfone SIM card). So I waited longer, but I still cannot get a response.

How can I debug this?

Thank you,

Dave

(Edited)
Photo of Dave Anderson

Dave Anderson

  • 11 Posts
  • 0 Reply Likes

Do you need more information from me on this issue? My client is getting jumpy and I would like to get this resolved so I can move forward with testing.

Thanks

Photo of Bob Heckmann

Bob Heckmann, Official Rep

  • 349 Posts
  • 12 Reply Likes
Hi Dave,

For the most recent SMS-MT the logs indicate successful delivery but we don't see a corresponding SMS-MO. It would be very helpful if you could send SMS-MT to the device again (and provide us the time stamp) so we can observe what if any response we receive from the device.

Regards,
Bob
Photo of Bill Gadek

Bill Gadek

  • 4 Posts
  • 0 Reply Likes
im having the same issue with my tracker as well cant get any sms responce need help too
Photo of Dave Anderson

Dave Anderson

  • 11 Posts
  • 0 Reply Likes

Hi Bob,

Today 30-APR-2016 starting at 19:25 UTC you should see 7 MTs and 3 MOs. So 4 of the MTs did not result in an MO being received by the AERIS API.

I tested the device again with a Tracfone SIM and all 7 MTs resulted in 7 MOs so I believe that the device is working correctly and generating the MOs correctly.

The key thing here is that the 3 suceeding MOs using the Aeris SIM are all short messages i.e. 15 characters or less.
The failed MOs are all longer message i.e. 80 characters or more in length. These include URLs (e.g. http://maps.google.com/maps?maps?q=N22.540885,E113.96265). I am wondering if a wierd non printable character might be upsetting the AERIS receiver?

Are you able to see if the device responded with an MO and it was somehow rejected by the AERIS receiving software? I really hope this is resolvable.

Thank you,

Dave

Photo of Dave Anderson

Dave Anderson

  • 11 Posts
  • 0 Reply Likes

Hi Bob,

Any update?

Thanks,

Dave

Photo of Bob Heckmann

Bob Heckmann, Official Rep

  • 349 Posts
  • 12 Reply Likes
Hi Dave,

Unfortunately, we don't see any initiate records in our database for the SMS-MO that you're missing, which means there is nothing for us to trace. It's as though the device hasn't sent anything in those cases. The character limit for SMS is 140 so your payload is fine.

Has all this testing been with a single device or have you tried more than one? If you haven't tried more than one we recommend you do that and let us know the time stamps so we can check the logs.

Regards,
Bob

This conversation is no longer open for comments or replies.