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
To: Deborah Pisani
Cc: users@mbuni.org
Subject: Re: [Users] Retrieval Report for MMS sent over MM4
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
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,
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?
if the
recipient does not retrieve the message within that period of time.
Best Regards,
Deborah and Andrew
From: kitand...@gmail.com [mailto:kitand...@gmail.com] On Behalf Of Paul
Bagyenda
Sent: 26 May 2011 13:48
To: Deborah Pisani
Cc: users@mbuni.org
Subject: Re: [Users] Push Notification DLRs
Hello,
We are currently testing Mbuni as a MMSC and would appreciate whether
someone may help to clarify the following regarding the above subject.
In our setup, Mbuni MMSC makes use of Kannel both as a WAP GW (wapbox)
for MMS origination and as a Push Proxy GW (smsbox) for the SMS-based
