Hello,
May someone please explain the expected function of the parameter
confirmed-delivery (defined as part of the MM4 configuration under the
group = mmsproxy within the Mbuni MMSC configuration file) as this is
not clear enough from the description provided in the Mbuni User Guide?
Dear all,
We are currently testing MM4 between two Mbuni MMSCs by sending MMS from
the originator in one domain to the recipient in another domain.
We are using the fakesmsc simulator and are observing the following
trace corresponding to the Push Notification from the terminating Mbuni
Hello Deborah,
When a message is forwarded by Mbuni MMSC over MM4, we can ask the receiving
server to send back an Ack when the message is delivered to the final receiving
server. This is the purpose of this flag. In this case a DLR Ack is sent back
to us so that we do not retry sending the
The report might be different for all kinds of reasons. The report contains
information about the recipient, the message ID, etc. If any of those fields
changes, then the report will be different. What matters is that the sender is
able to match the report to what was sent.
On Jul 21, 2011, at
Hi,
I am not familiar with that modem, but in general if you can start a normal
PPP link with it, and can also send/receive MMS, then it'll work with Mbuni. I
would trawl the mailing list archives for a post by Nuno Freitas on how to get
that all setup.
Paul.
On Jul 20, 2011, at 20:21,
Hi Paul,
Thank you for your response. However, what is still not clear to us (as
also described in our earlier query) is that while normally only one SMS
is generated corresponding to the retrieval report, in the case of MMS
exchanged between users in different domains, two SMSs are instead
The SMS actually contains the DLR as an MMS. Size will vary depending on the
content of the DLR.
On Jul 21, 2011, at 06:16, Deborah Pisani wrote:
Hi Paul,
Thank you for your response. However, what is still not clear to us (as also
described in our earlier query) is that while normally
