12:02 a.m.
These patches concern mmsd and update documentation to describe new
functionalities to add to mmsd.
Ronald Tessier (2):
doc: Describe delivered group in storage doc
doc: Add new D-Bus methods to service interface
doc/service-api.txt | 20 ++++++++++++++++++++
doc/storage.txt | 36 ++++++++++++++++++++++++++++++++++++
2 files changed, 56 insertions(+), 0 deletions(-)
--
1.7.4.1
12:02 a.m.
New subject: [PATCHv2 1/2] doc: Describe delivered group in storage doc
---
doc/storage.txt | 36 ++++++++++++++++++++++++++++++++++++
1 files changed, 36 insertions(+), 0 deletions(-)
diff --git a/doc/storage.txt b/doc/storage.txt
index 8e76382..de74a77 100644
--- a/doc/storage.txt
+++ b/doc/storage.txt
@@ -18,6 +18,7 @@ Meta file Example
[info]
read=false
state=notification
+id=0123456789ABCDEF
Meta file Keys/Values details
@@ -31,3 +32,38 @@ state: The message local state, possible values can be:
- "received": m-Retrieve.Conf PDU downloaded and successfully
acknowledged.
- "draft": m-Send.Req PDU ready for sending.
- "sent": m-Send.Req PDU successfully sent.
+
+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. It 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 recipients.
+
+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 destination.
+ - "forwarded": recipient forwarded the MMS without retrieving it first.
+ - "unreachable": recipient is not reachable.
+
+
+Example of a sent_message meta file with delivery report requested
+==================================================================
+
+[info]
+state=sent
+id=0123456789ABCDEF
+
+[delivery_status]
++33612345678=retrieved
++4915187654321=none
--
1.7.4.1
12:02 a.m.
New subject: [PATCHv2 2/2] doc: Add new D-Bus methods to service interface
---
doc/service-api.txt | 20 ++++++++++++++++++++
1 files changed, 20 insertions(+), 0 deletions(-)
diff --git a/doc/service-api.txt b/doc/service-api.txt
index 36e1161..02396ff 100644
--- a/doc/service-api.txt
+++ b/doc/service-api.txt
@@ -63,6 +63,26 @@ Methods array{object,dict} GetMessages()
[service].Error.PermanentContentNotAccepted
[service].Error.PermanentLackOfPrepaid
+ void DeleteMessages(array{object})
+
+ Delete an array of message objects that represents
+ the currently stored messages to delete.
+
+ Possible Errors: [service].Error.InvalidArguments
+
+ void DeleteConversation(string number)
+
+ Delete the messages that belongs to the conversation
+ defined by the given number.
+
+ The number parameter contains digits to look for
+ (i.e.: n last digits of the phone number), only messages
+ with a recipient which ends with the given number will
+ be member of the conversation and thus will be deleted.
+
+ Possible Errors: [service].Error.InvalidArguments
+
+
Signals MessageAdded(object path, dict properties)
Signal that is sent when a new message is added. It
--
1.7.4.1
3737
days inactive
3750
days old
3 comments
2 participants
participants (2)
-
Marcel Holtmann -
Ronald Tessier