837366 - Roaming message is null and sender number corrupt

Status: RESOLVED DUPLICATE of bug 860730

(Firefox OS Graveyard :: Gaia::SMS, defect)

Description

[Dave Hunt [:davehunt] [he/him] ⌚BST]

Attachment: Screenshot of messages application showing bad message

Traveling from UK to Belgium for FOSDEM I recieved a message, presumably to notify my of roaming charges. The message content is null and the sender number is not identifiable. This is shown in notifications and the messages app. See attached screenshot.

Comment 1

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Exactly the same happened to me when I entered Belgium. I got the message from my provider which has been shown a similar garbled phone number. But compared to Dave I was able to see the content of the message.

Comment 2

[Andrew Overholt [:overholt]]

Vicamo, do you know what could cause this?  Could this be some sort of carrier message class that we're displaying incorrectly?

Comment 3

[Alex Keybl [:akeybl]]

Also ni? on Daniel, to see if this is a blocker from the tef perspective (may not be affected).

Comment 4

[Daniel Coloma:dcoloma]

I think this is related to class 2 SMSs, David, is this critical?

Comment 5

[Vicamo Yang [:vicamo][:vyang]]

(In reply to Andrew Overholt [:overholt] from comment #2)
> Vicamo, do you know what could cause this? Could this be some
> sort of carrier message class that we're displaying incorrectly?

We got a text body here, so the message encoding must be either 7bit or ucs2, and the string "2;778#;967" is intended.  That's possible because when DCS reads zero, that means 7bit encoding.  We got null sender because the address length is zero.  Looks like that's for some special purpose only, not a normal SMS message. Could be a CLASS 1/2/3 SMS as Daniel said.

Comment 6

[David Palomino [:dpalomino]]

Hi, 

Has it been detected when roaming in any other country apart from Belgium? All SMS that I've personally seen are alway standard class 1 SMS. 

As Vicamo has stated, it seems a quite particular carrier-specific message. From my understanding, this would be not blocking... 

Thks!
David

Comment 8

[Alex Keybl [:akeybl]]

Sounds like this doesn't block TEF. May block another of our partners though?

Comment 9

[Alex Keybl [:akeybl]]

Andreas - can you verify whether or not you're impacted?

Comment 10

[Alex Keybl [:akeybl]]

Given current testing, this is not a blocker for any of our partners. Please re-nom if/when that changes.