A couple of cents worth: Intuitively your suggestion makes sense.
There is a potential problem that the MMSC would have to remember
every single message it has handled and where it came from, so that
it can route the corresponding DLRs. That could put a lot of pressure
on the MMSC in terms of storage requirements.
In addition, consider that the DLR really is a message in its own
right. It should be routed as a normal message. What if between
receipt of message and receipt of DLR routing for the relevant
destination has changed? Must we note take that into account when
sending back the report?
P.
On Sep 02, 2005, at 13:20, Dziugas Baltrunas wrote:
Hi list,
I'd like to figure out, what should be the logic for sending delivery
reports to VASPs via MM7.
I believe, that VASP should get DLR back to the every message it has
submitted via MM7 SubmitReq. What is more, SubmitReq allows to specify
any sender address (if this is not forbidden by MMSC, in this case
mbuni). However, mbuni (and some others MMSC) outbound MM routing does
on the basis of recipient address. This illustrates a snip from
mmsc/mmsglobalsender.c sendMsg() function:
---
} else /* Search VASP list, see what you can find... */
for (j = 0, m = list_len(settings->vasp_list);
j < m; j++)
if ((vasp = list_get(settings->vasp_list, j))
!= NULL &&
_x_octstr_int_compare(vasp->short_code,
phonenum) == 0) {
res = mms_sendtovasp(vasp, e->from,
to->rcpt,
e->msgId,
msg, &err);
sent = 1;
break;
}
---
I agree that this is the only possible case for routing a multimedia
message, but for DLRs I see the approach written above. It means that
DLR routing should be based on MM transaction IDs and when DLR arrives
from recipient (via MM1 for example), MMSC should look up it's
received MMs (submitted via MM7 SubmitReq by VASPS) table in order to
match MM transaction id with the VASP which submitted the original
message.
I'd be interesting to know, what do others think about this approach.
I'm not sure if it's mentioned somewhere in 3GPP or OMA standards.
--
Dziugas
_______________________________________________
Devel mailing list
Devel@mbuni.org
http://mbuni.org/mailman/listinfo/devel_mbuni.org
_______________________________________________
Devel mailing list
Devel@mbuni.org
http://mbuni.org/mailman/listinfo/devel_mbuni.org
