On 06/07/2012 04:43 AM, Marcel Holtmann wrote:
> doc/storage.txt | 30 ++++++++++++++++++++++++++++++
> 1 files changed, 30 insertions(+), 0 deletions(-)
> diff --git a/doc/storage.txt b/doc/storage.txt
> index 8e76382..0aa6d9d 100644
> --- a/doc/storage.txt
> +++ b/doc/storage.txt
> @@ -18,6 +18,7 @@ Meta file Example
I would just shortcut this to "id". Or is the a reason to keep
"message_id" for this?
Let's go for "id"
> Meta file Keys/Values details
> @@ -31,3 +32,32 @@ state: The message local state, possible values can be:
> - "received": m-Retrieve.Conf PDU downloaded and successfully
> - "draft": m-Send.Req PDU ready for sending.
> - "sent": m-Send.Req PDU successfully sent.
> +message_id: this is the value provided in the M-Send.conf PDU (assigned by MMSC
> +in response to a M-Send.req message), this entry will only be created upon
> +M-Send.conf message reception if the delivery report was requested.
> +For sent messages, a group [delivery_status] could take place in addition to
> +[info] if delivery report is requested.
> +In this group, every recipient has a MMS Delivery status value which can be one
> +of the following:
> + - "none": no report has been received yet.
> + - "expired": recipient did not retrieve the MMS before expiration.
> + - "retrieved": MMS successfully retrieved by the recipient.
> + - "rejected": recipient rejected the MMS.
> + - "deferred": recipient decided to retrieve the MMS at a later time.
> + - "indeterminate": cannot determine if the MMS reached its
> + - "forwarded": recipient forwarded the MMS without retrieving it
> + - "unreachable": recipient is not reachable.
> +Example of a sent_message meta file with delivery report requested
How is this suppose to work. I am kinda failing to see what this tries
If the delivery-report is requested, a delivery_status group will be
created in the message meta file. This group will be used to manage the
received delivery_report sent by each recipients. This group will have
an entry per recipient, the associated value will be set to "none"
(which means no report has been received yet) and updated upon report
reception. The stored "id" (provided by the MMSC in the Send.conf msg)
must match the received "id" in the delivery.ind push msg sent by each
This intents to handle and store delivery reports received status. Next
step will be to define how to let the upper layer knows about the
delivery reporting status.