Receiving SMS

I am having an issue receiving SMS messages. Sending works fine. I have a Verizon GX440

From ATT: No messages received
From Sprint: No messages received
From Google Voice: Works great
From Verizon: Works great

Anyone had similar issues?

***Edit

System logs seem to confirm texts from these carriers cannot decode, triggering “User data encoding is not 7BITAscii”.

iPhone from Verizon works, iPhone from Sprint does not. Carrier level problem? Anyone?

-Tim

Hi,

How exactly you are monitoring the sent and received SMS.

Can you please send the complete system logs in case of success and failure in receiving SMS.

Thanks.

I am using the sample sms.lua application.

I noticed some messages were not triggering the call back. Upon viewing the logs, I saw:

Logs for an SMS message from AT&T say:

Nov  7 17:24:43 info ALEOS_WAN_RadioTask: SMS Storage Type is: 1
Nov  7 17:24:43 info ALEOS_WAN_RadioTask: *** Message Index is: 0
Nov  7 17:24:43 info ALEOS_WAN_RadioTask: SLQS Get SMS  ret code  0  Tag 1  Format 0 Size 45 
Nov  7 17:24:43 info ALEOS_WAN_RadioTask: Processing Incoming SMS PDU
Nov  7 17:24:43 info ALEOS_WAN_RadioTask:  -- Top Level Parsing --
Nov  7 17:24:43 info ALEOS_WAN_RadioTask: Identifier 0 TELESERVICE len 2
Nov  7 17:24:43 info ALEOS_WAN_RadioTask: Identifier 2 From Phone num len 7
Nov  7 17:24:43 info ALEOS_WAN_RadioTask: Identifier 8 BEARER_DATA len 29
Nov  7 17:24:43 info ALEOS_WAN_RadioTask: --
Nov  7 17:24:43 info ALEOS_WAN_RadioTask: Decoding phone number
Nov  7 17:24:43 info ALEOS_WAN_RadioTask: Phone <<my phone number>> -len 10
Nov  7 17:24:43 info ALEOS_WAN_RadioTask:  -- Parsing Bearer Data --
Nov  7 17:24:43 info ALEOS_WAN_RadioTask: ID 0 - Msg Sub Id
Nov  7 17:24:43 info ALEOS_WAN_RadioTask: ID 1 - User Data  len 14
Nov  7 17:24:43 info ALEOS_WAN_RadioTask: ID 3 - Timestamp  len 6
Nov  7 17:24:43 info ALEOS_WAN_RadioTask: Decoding User Data
Nov  7 17:24:43 err ALEOS_WAN_RadioTask: User data encoding is not 7BITAscii
Nov  7 17:24:43 err ALEOS_WAN_RadioTask: Decode Error, Ret = 1
Nov  7 17:24:43 info ALEOS_WAN_RadioTask: PDU Parse Return code 1 
Nov  7 17:24:43 info ALEOS_WAN_RadioTask: --
Nov  7 17:24:43 info ALEOS_WAN_RadioTask: Error processing PDU Return code1
Nov  7 17:24:43 info ALEOS_WAN_RadioTask: SMS Delete successful ************

Working SMS message from Google Voice

Nov  7 00:03:52 info ALEOS_WAN_RadioTask: SMS Storage Type is: 1
Nov  7 00:03:52 info ALEOS_WAN_RadioTask: *** Message Index is: 1
Nov  7 00:03:53 info ALEOS_WAN_RadioTask: SLQS Get SMS  ret code  0  Tag 1  Format 0 Size 52 
Nov  7 00:03:53 info ALEOS_WAN_RadioTask: Processing Incoming SMS PDU
Nov  7 00:03:53 info ALEOS_WAN_RadioTask:  -- Top Level Parsing --
Nov  7 00:03:53 info ALEOS_WAN_RadioTask: Identifier 0 TELESERVICE len 2
Nov  7 00:03:53 info ALEOS_WAN_RadioTask: Identifier 2 From Phone num len 7
Nov  7 00:03:53 info ALEOS_WAN_RadioTask: Identifier 8 BEARER_DATA len 36
Nov  7 00:03:53 info ALEOS_WAN_RadioTask: --
Nov  7 00:03:53 info ALEOS_WAN_RadioTask: Decoding phone number
Nov  7 00:03:53 info ALEOS_WAN_RadioTask: Phone <<my gvoice number>> -len 10
Nov  7 00:03:53 info ALEOS_WAN_RadioTask:  -- Parsing Bearer Data --
Nov  7 00:03:53 info ALEOS_WAN_RadioTask: ID 0 - Msg Sub Id
Nov  7 00:03:53 info ALEOS_WAN_RadioTask: ID 1 - User Data  len 21
Nov  7 00:03:53 info ALEOS_WAN_RadioTask: ID 3 - Timestamp  len 6
Nov  7 00:03:53 info ALEOS_WAN_RadioTask: Decoding User Data
Nov  7 00:03:53 info ALEOS_WAN_RadioTask: len 22:  68 65 79 6f 20 66 72 6f 6d 20 
Nov  7 00:03:53 info ALEOS_WAN_RadioTask: len 22:  heyo from google voice
Nov  7 00:03:53 info ALEOS_WAN_RadioTask: PDU Parse Return code 0 
Nov  7 00:03:53 info ALEOS_WAN_RadioTask: --
Nov  7 00:03:53 info ALEOS_WAN_RadioTask: --- Returned Data ---
Nov  7 00:03:53 info ALEOS_WAN_RadioTask: Msg ID : 61090
Nov  7 00:03:53 info ALEOS_WAN_RadioTask: Sender : <<my gvoice number>> Len 10
Nov  7 00:03:53 info ALEOS_WAN_RadioTask: Msg    : heyo from google voice  Len 22
Nov  7 00:03:53 info ALEOS_WAN_RadioTask: Pri    : 255
Nov  7 00:03:53 info ALEOS_WAN_RadioTask: SMS Delete successful ************

Chalk it up as a known firmware issue. The messages fails before any of the aleos (application framework or acemanager) callback is called.