SMS delivery report

SMS delivery report

[Miettinen Pasi]

[-- Attachment #1: Type: text/plain, Size: 876 bytes --]

Hi all,

My name is Pasi Miettinen. I have been working with SMS delivery report item
based on the TODO list. The work covers requesting of SMS report in the 
DBus interface via SendMessage method by adding third parameter. If 
parameter is TRUE status report is asked. Incoming status report is reported
also via DBus by sending signla called IncomingStatusreport. Status reports
of the concatenated messages are also supported. Internal oFono SMS
history is updated according status report results. This patch utilizes old style
msg_id (not hash). Concatenated messages have one internal msg_id that
relates to multiple TP-MR. If one MR-number is resulted to "delivery-failed",
the whole concatenated message is considered as failed and history is
updated using internal msg_id.

An initial set of patches follow for review.

Best regards,
Pasi Miettinen 

Re: SMS delivery report

[Denis Kenzior]

[-- Attachment #1: Type: text/plain, Size: 1177 bytes --]

Hi Pasi,

> Hi all,
> 
> My name is Pasi Miettinen. I have been working with SMS delivery report
>  item based on the TODO list. The work covers requesting of SMS report in
>  the DBus interface via SendMessage method by adding third parameter. If
>  parameter is TRUE status report is asked. Incoming status report is
>  reported also via DBus by sending signla called IncomingStatusreport.
>  Status reports of the concatenated messages are also supported. Internal
>  oFono SMS history is updated according status report results. This patch
>  utilizes old style msg_id (not hash). Concatenated messages have one
>  internal msg_id that relates to multiple TP-MR. If one MR-number is
>  resulted to "delivery-failed", the whole concatenated message is
>  considered as failed and history is updated using internal msg_id.
> 
> An initial set of patches follow for review.

First of all, welcome aboard :)

Since you're making good progress on the Status Report tasks, can you submit a 
patch against the TODO file indicating that you're the Owner of this task?
Simple  'Owner: Author' (same as commit info) annotation will suffice.

Thanks,
-Denis