Delivery report

[GoogleCodeExporter]

It would be great to be able to retrieve delivery report, since for example 
FishText provides this functionality, so it could be integrated into this 
application.

Original issue reported on code.google.com by jambo...@gmail.com on 7 Jul 2010 at 7:44

[GoogleCodeExporter]

Original comment by felix.bechstein on 13 Jul 2010 at 5:03

• Added labels: Component-Logic, Priority-Low, Product-WebSMS, Type-Enhancement
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

innosend and smstrade also provide that feature! It would be very very very 
great if you would do implement that!

Original comment by de.hub...@googlemail.com on 15 Jul 2010 at 7:03

[GoogleCodeExporter]

I saw that no app offers that function. I also think if you would offer that, a 
lot of users would change from chomp to websms...

Original comment by de.hub...@googlemail.com on 16 Jul 2010 at 2:39

[GoogleCodeExporter]

yes, it' s very need for smspilot connertor!
this is an API for simple delivery check of recent sms:

https://smspilot.ru/api.php?check=recent&apikey=XYZ

where XYZ is your 64 simbol apikey

returns status of all sent sms for 24 hours, for ex.
4566,79087964782,1,-1
4567,79131231212,1,2

transcription:[SMS ID-not interesting for simple checking],[Recipient's 
number],[zone of recipient-not interesting value],[STATUS of delivery]

status VALUES:
-2 - server doesn't receive this message (ID not found) 
-1 - message not delivered (phone is switched off or operator is not supported)
0 - new message
1 - awaiting of delivery
2 - message is delivered successfully

Original comment by ximonline@gmail.com on 31 Oct 2010 at 1:07

[GoogleCodeExporter]

Es wäre toll, wenn man Sendeberichte für SMS über GSM einstellen könnte.
Diese sollten dann auch in SMSdroid lesbar bzw, durch ein Icon angezeigt werden 
- ähnlich wie in der stock sms appliaktion.

LG

Original comment by kingmalk...@gmail.com on 18 Nov 2010 at 12:38

[GoogleCodeExporter]

Issue 487 has been merged into this issue.

Original comment by f...@ub0r.de on 5 Apr 2011 at 4:38

[GoogleCodeExporter]

Issue 500 has been merged into this issue.

Original comment by f...@ub0r.de on 22 Apr 2011 at 9:01

[GoogleCodeExporter]

Issue 572 has been merged into this issue.

Original comment by f...@ub0r.de on 1 Sep 2011 at 7:59

[GoogleCodeExporter]

does anyone know if o2.de has delivery reports for web sms?
i recall having seen it, but right now, i only discovered a simple send 
confirmation next to the message in the communication center.

Original comment by m...@mitjaveil.com on 9 Oct 2011 at 2:15

[GoogleCodeExporter]

Hi, me and 3 students have done a class named Parsing with a method who takes 2 
parameters (date & the receiver's number). This method returns an integer (1 or 
2 or 3, it depends on the status of the message [sent, received, or waiting]). 
We created this method with JSoup and the connector is fishtext. 
And we would like to know how to integrate it in WebSMS, 
Thanks for cooperating.

Original comment by patrick....@gmail.com on 27 Dec 2011 at 11:56

[GoogleCodeExporter]

there are a few things to do, before this can be merged:

1) we need to change the app to trigger the delivery report
2) we need to extend the api to let the app push this command to the connector
3) we need to extend the connector to handle the command and push back the 
information
4) we need to change the app to show the information handed back from the 
connector

2+3) this is quite easy
1+4) i don't how to change the ui to get this into the app. what should be 
displayed? the status of the last message? where to put the information? when 
should the information be fetched?

do you have any idea?
feel free to implement something and ask me to pull it into the master.

technically it's easy quite easy to merge your code.
fork fintanf's git repository [1] and integrate your code, ask him to pull your 
changes into the master.

[1] https://github.com/fintanf/websms-connector-fishtext

Original comment by f...@ub0r.de on 29 Dec 2011 at 2:54

• Changed state: Started

[GoogleCodeExporter]

Thank you for your really helpful answer.

Our first thought was to modify websms to create messages with a status like 
"unknown" and with a background task, to update this status with the connector, 
based on the function I described in my first post here. 
The background task will be running while the message's status are not on 
"message delivered", and will stop when all the messages will be received. 
The objective of the background task will be to update the status of a message 
every x seconds until the status is "message delivered".
Do you think it is possible to do something like that ?

Our project has a deadline on the 11th of january, so it isn't our priority to 
show the status directly on the app, because some others apps like handcent sms 
which handle the status already exists and could probably show the status of 
messages sent by websms.

After that we will be pleased to do it on the app itself :)

Again, thank you very much for your help !

Original comment by patrick....@gmail.com on 30 Dec 2011 at 1:57

[GoogleCodeExporter]

ok, having a table inside websms having all "not yet sent" messages holding 
android's message id with the id of the connector should do this.
websms itself could then trigger the connector's "update message status" 
command.
the connector itself should retrieve and update the message status via 
ContentResolver.

but the last problem is: who to display this information in the gui?

Original comment by f...@ub0r.de on 2 Jan 2012 at 6:03

• Added labels: Priority-High
• Removed labels: Priority-Low

[GoogleCodeExporter]

Hmm, we would like to implement message status exactly like they are 
implemented by the original android app to send message, this way, any apps 
could display the status of a message send by websms : messages, smsdroid, 
handcent sms, etc... if the user want it or not.

Did you ask "how to display this information in the gui?" because it is not 
possible like we said ? :S or because you think it's a bad idea ?

We appreciate your help very much, we are new to the android developpment, it 
is our first project and we learn by ourselves so any help is welcomed. We are 
very motivated, but we don't know where to begin because of our lack of 
experience.

Again thank you for your answer

Original comment by patrick....@gmail.com on 2 Jan 2012 at 7:16

[GoogleCodeExporter]

it's even better if the status can be handled in android's database.
but i was not sure, the "sent but not received" status is represent-able there.

smsdroid could be changed easily to show that status.
but how should it be shown in websms itself? did i missed something in your 
comments?

in the end: i'd like to have websms triggering the background task by pushing a 
ConnectorCommand to the connectors, because saving the message to the database 
is handled by websms on itself.
the status can be written by the connector directly though.

Original comment by f...@ub0r.de on 2 Jan 2012 at 8:38

[GoogleCodeExporter]

Hello, I'm working with Patrick on this project, thank you for your answers !

We also don't know how to display it on websms, that's why we thought : websms 
should only create messages with a "delivery report" (or status) attribute, 
which will be update by our background task, the display will be handle 
elsewhere. 

Then, this status attribute will be show like other delivery report on android, 
when not using websms but ordinary sms (by clicking on one specific message on 
the native application, or by icons next to the corresponding message on other 
apps like those we talked before, or, if we have time, by a new feature on 
smsdroid).

Do you think we have to display it directly on websms or this should do it ?

I hope you'll see what we want to do here, but if you think we are taking the 
wrong way, please tell us :)

Again, thank you for your time.

Original comment by egits...@gmail.com on 2 Jan 2012 at 9:26

[GoogleCodeExporter]

well, adding "delivery report" functionality to websms without the possibility 
to view the status is kind of strange fro most users. but showing a "please use 
smsdroid" hint to users might work for the start.

one thing i missed yesterday: using the android's own message database is not 
enough for internal purpose: there is no way to save the used connector on the 
internal database. but i guess this information needs to be tracked to trigger 
the connectors "get status" command.

Original comment by f...@ub0r.de on 3 Jan 2012 at 6:08

[GoogleCodeExporter]

Hello,

We are currently coding the following things : 
In the API : 
two functions : -"connectorAllowDeliveryReport" which will return a boolean 
saying if the connector specified can provide delivery report or not, default 
is false
-deliveryReportStatus : which will return the status of the sms, default is 
'unknown', or an int (other values are : message sent or message delivered but 
will be return only by the connector)

In the connector : we override those functions, connectorAllowDeliveryReport 
will then return true and deliveryReportStatus will take the 2 parameters we 
talked before : the number of the receiver and the exact time of sending, and 
will return the status (this is basically the function we have already wrote 
using jsoup).

Then, in websms, when the connector allow delivery report, we put the id of the 
message sent in a table with the connector id, the message will be in the table 
as long as the delivery report associate is not "message delivered", until 
then, we will launch deliveryReportStatus in background every x seconds.

Thanks to our teacher, we have manage to find the following information that 
may be usefull : 
http://androidforums.com/application-development/158592-querying-sms-content-pro
vider.html#post2168101
we think the column we need is "report_date" but we haven't test it yet.

With this, we will use the value returned by deliveryReportStatus to update 
this column in the sms database, then, delete the sms/connector_ids of the 
table in websms.

By doing that I think that the sms status will be seen by any sms app which 
handle delivery report.

I think that all of this will do it, and I think I didn't forgot anything you 
said before, if it's not the case or if you see a problem or other things to 
do, please tell us !

Thank you very much for your help.

Original comment by egits...@gmail.com on 5 Jan 2012 at 10:26

[GoogleCodeExporter]

By the way, you will be able to see those changes (or at least a part of it) by 
the end of the day on my github profile at https://github.com/romaindesjours
Thanks !

Original comment by egits...@gmail.com on 5 Jan 2012 at 10:32

[GoogleCodeExporter]

Just to point out that it's my fork of the websms-connector-fishtext that you 
actually want to fork, modify, and send pull requests to (you've currently 
forked from Felix's account). I took over maintaining the fishtext connector 
from Felix last year.

It's at:
https://github.com/fintanf/websms-connector-fishtext

Original comment by fint...@gmail.com on 5 Jan 2012 at 10:57

[GoogleCodeExporter]

Indeed x) we have forked your version and will modify this one instead, thanks 
:)

Original comment by egits...@gmail.com on 5 Jan 2012 at 11:15