Hi, > Here in Denmark, the law dictates that the mobile operators must allow > the mobile subscribers to move between operators, but take their MSISDN > with them. In other words, we can't use prefixes to determine whether or > not the user is local, and if not, to which other MMSC to send the > message. For this reason, I've devised a patch that implements a > technique similar to the billing plugin system.
Well, the issue is the same in the whole EU countries and even more globally. > I've added a directive to the configuration file for defining an > external resolver module. This module is responsible for resolving an > MSISDN to a hostname to which the MMS should be sent. If this hostname > matches our own hostname, the user is considered local. This is a nice job and it partly solves problem. I've recently looked to the 3GPP TS 23410-680 Annexes G and H and at least G was new for me. So I think that we could try to follow this kind of routing here, although I have doubts it actually works worldwide. What is more, I think that this resolver module could fetch (if possible) more info (from the operator) about a particular MSISDN. For example, having an IMSI number we could follow a routing defined in the Annex H. Another case for this is related with content adaptation. For example, if this module could fetch info about MSISDN user agent, and if user agent is not MMS capable, MMS mobile sender could send a SMS with an URL to MMS preview instead of MM.notification.ind. However, IMO this issue should be investigated deeper, as some of the resolving procedures involves MM5 (communication with HLR) for which Mbuni has no plans to implement. -- Dziugas _______________________________________________ Devel mailing list Devel@mbuni.org http://mbuni.org/mailman/listinfo/devel_mbuni.org
