Incoming SMS with special sender numbers are discarded (e.g. SMS from Skype)

Bug #1238939 reported by Michael Zanetti
54
This bug affects 8 people
Affects Status Importance Assigned to Milestone
telephony-service
Fix Released
High
Tiago Salem Herrmann
telepathy-ofono (Ubuntu)
Fix Released
High
Tiago Salem Herrmann
telephony-service (Ubuntu)
Fix Released
High
Tiago Salem Herrmann

Bug Description

Incoming SMS with special sender strings are silently ignored. The screen wakes up but nothing else happens. Those SMS can be recieved from services like Skype or other non phone sources.

* .cache/upstart/dbus.log just prints this single message when the message comes in

Error creating channel for incoming message

* dbus-monitor --system

signal sender=:1.19 -> dest=(null destination) serial=972 path=/ril_0; interface=org.ofono.MessageManager; member=IncomingMessage
   string "test4"
   array [
      dict entry(
         string "LocalSentTime"
         variant string "2013-10-11T18:36:16+0000"
      )
      dict entry(
         string "SentTime"
         variant string "2013-10-11T20:36:16+0200"
      )
      dict entry(
         string "Sender"
         variant string "dreadhead12"
      )
   ]

Related branches

Revision history for this message
Pat McGowan (pat-mcgowan) wrote :

@Michael
This is working for me from Skype, is there more to how you send the SMS or how your account is configured?

Changed in telephony-service:
status: New → Incomplete
Revision history for this message
Michael Zanetti (mzanetti) wrote :

@Pat

Not really, no. It's my (very old) standard skype account. I have some money on it to be able to send SMS and do Phone calls. When sending a SMS it seems to put my skype nickname in the sender's field. I could immagine US mobile providers not allowing that and hence making it work for you. What's the sender's number when you send a SMS from skype?

Revision history for this message
Max (samuray-bo) wrote :

i have same problem for hidden numbers.

google 2 factor auth sms:

* .cache/upstart/dbus.log just prints this single message when the message comes in

Error creating channel for incoming message

dbus-monitor --system

interface=org.freedesktop.UPower; member=DeviceChanged
   string "/org/freedesktop/UPower/devices/battery_battery"
=org.ofono.MessageManager; member=IncomingMessage
   string "[deleted google message]"
   array [
      dict entry(
         string "LocalSentTime"
         variant string "2013-10-16T19:29:57+0300"
      )
      dict entry(
         string "SentTime"
         variant string "2013-10-16T19:29:57+0300"
      )
      dict entry(
         string "Sender"
         variant string "Google"
      )
   ]

Revision history for this message
Solstag (solstag) wrote :

I've been having this issue as well.

My phone operator sends messages with sender "teligou" when somebody calls me and my phone is out of reach.

Ubuntu Touch silently ignores these messages. Not a single one of those arrive.

If I move my SIM card back to a different phone they arrive normally.

It would seem that any sender that is not numeric is being ignored.

I also remember this used to work, meaning I got those messages, with very early versions of Ubuntu Touch, like in the quantal releases.

Ni!

Revision history for this message
Tiago Salem Herrmann (tiagosh) wrote :

The problem is that telepathy-ofono checks if the Sender (for sms's) or the LineIdentification (for calls) properties coming from ofono are actually phone numbers, otherwise they will be ignored.
It's probably possible to change this behavior in telepathy-ofono, and I assume no big changes to the upper layers are required.

Changed in telephony-service:
status: Incomplete → New
Revision history for this message
Roman S. Pavlov (romangoward) wrote :

Hi fellas,
I've same trouble with receiving of SMS from online banking service. It contains the next field, entirely of letters:
         string "Sender"
         variant string "Alfa-Bank"

./phoneutils.h:
...
300 bool isPhoneNumber(const QString &identifier) {
301 // remove all non diable digits
302 QString finalNumber = QString(identifier).replace(QRegExp("[p+*#()-]"),"");
303 finalNumber = finalNumber.replace(QRegExp("(\\s+)"), "");
304 // if empty, the number is invalid
305 if (finalNumber.isEmpty())
306 return false;
307
308 finalNumber = finalNumber.replace(QRegExp("(\\d+)"), "");
309 return finalNumber.isEmpty();
310 }
311
312 QString normalizePhoneNumber(const QString &identifier) {
313 QRegExp regexp = QRegExp("(\\s+)");
314 QString finalNumber = QString(identifier).replace(regexp,"");
315 finalNumber = finalNumber.replace(QRegExp("[()-]"),"");
316 return finalNumber;
317 }

Do we really needs this check? Could we delete isPhoneNumber() function at all? I suppose, normalizePhomeNumber() will be enough for correct work.
./connection.cpp contains only four test-cases with isPhoneNumber() and it looks easy to clean.

Any thoughts?

Revision history for this message
Oliver Grawert (ogra) wrote :

same for all google notification as well as confirmation SMS (see duplicated bug #1246630)

Revision history for this message
Taras Perebeynosov (taras-perebeynosov) wrote :

I have the same issue with Google Auth and Raiffaisen Connect:

signal sender=:1.33 -> dest=(null destination) serial=2582 path=/ril_0; interface=org.ofono.MessageManager; member=IncomingMessage
   string "Konfidencialno. Kod podtverzhdenija ***** R-Connect Oplata Volga branch ******* summa 500.00 RUR. Po voprosam zvonite 88007000072 Raiffeisenbank"
   array [
      dict entry(
         string "LocalSentTime"
         variant string "2013-11-03T14:24:14+0400"
      )
      dict entry(
         string "SentTime"
         variant string "2013-11-03T14:24:14+0400"
      )
      dict entry(
         string "Sender"
         variant string "Raiffeisen"
      )
   ]

Tony Espy (awe)
Changed in telephony-service:
status: New → Confirmed
Revision history for this message
Sam Bull (dreamsorcerer) wrote :

I no longer receive messages when my university sends me text messages because a lecture is cancelled.
I also don't receive messages from my mobile provider with roaming charges when connecting in a foreign country (which I believe is actually required by law).

Particularly considering the legal requirements of the last point, this should be a high priority bug.

Bill Filler (bfiller)
Changed in telephony-service:
status: Confirmed → Fix Committed
Changed in telepathy-ofono (Ubuntu):
status: New → Fix Committed
Changed in telephony-service:
importance: Undecided → High
Changed in telepathy-ofono (Ubuntu):
importance: Undecided → High
Changed in telephony-service:
assignee: nobody → Tiago Salem Herrmann (tiagosh)
Changed in telepathy-ofono (Ubuntu):
assignee: nobody → Tiago Salem Herrmann (tiagosh)
Changed in telephony-service (Ubuntu):
status: New → Fix Committed
importance: Undecided → High
assignee: nobody → Tiago Salem Herrmann (tiagosh)
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Trying to confirm the fix in order to release to distro; however I now no longer get messages shown in the Messaging app history, either for special numbers (which I however do receive a notification for), or from text messages I send to myself.

In fact, I no longer get any text messages received listing in messaging-app -- given that this package update causes a regression, I'm marking it as blocked until we can discuss this further.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package telepathy-ofono - 0.2+14.04.20131205.1-0ubuntu1

---------------
telepathy-ofono (0.2+14.04.20131205.1-0ubuntu1) trusty; urgency=low

  [ Tiago Salem Herrmann ]
  * Accept non numeric id's. (LP: #1238939)

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 52
 -- Ubuntu daily release <email address hidden> Thu, 05 Dec 2013 02:02:57 +0000

Changed in telepathy-ofono (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Sam Bull (dreamsorcerer) wrote :

Seems to be working now.

Changed in telephony-service (Ubuntu):
status: Fix Committed → Fix Released
Changed in telephony-service:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.