touch-packages team mailing list archive

[Matthias Apitz <guru@xxxxxxxxxxx>]

comparing the database timestamps and the provider times (from the
screenshots) we see:

database            provider
19:31:58.664   21:32:05 ... 21:32:45
11:31:17.015   13:31:21 ... 13:31:32

i.e. (ignoring the 2 hour diff due to TZ) it seems that the database
timestamp is made when the SMS is "queued" for delivery and not from the
last send attempt;

are there other log files (the question goes to Canonical) about the
send attempts?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1480554

Title:
  High costs due to SMS being sent multiple times when having a bad
  network connection

Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  When having a bad network connection, Ubuntu tries to send SMS
  multiple times but fails to recognize which messages have already been
  sent, resulting in very high costs due to the same message actually
  being sent several times.

  I found this when looking through my provider's monthly reports and I
  remember being on train journeys with very bad network connections on
  these days. See the attached screenshots.

  ==========

  This happened on a Nexus 4 running on the stable channel (with up-to-
  date images at the given times).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+subscriptions