You need to look into the resolver-library parameter of the MMSC setup. This provides a way to map each MM1 transaction to the MSISDN. Keep in mind that because MMS transactions are over HTTP (over TCP/IP), there needs to be a way to figure out who the sender is. In some setups the WAP Gateway inserts a special header into the HTTP traffic to identify the sender MSISDN, in others you have to find a way to figure it out yourself (e.g. give each sending phone a personalised MMSC URL that can later be used to identify the sender). P.
On 10/9/07, Theis Borg <[EMAIL PROTECTED]> wrote: > > Hi all > > I have just completed my first test with mbuni: a simple connection with a > phone sending a message to a phone through the mbuni mmsc. Everything works > fine, so the phone, SMSC and MMSC is working fine. > > Now for test2: sending an MMS to an application. > > I have setup a VASP and can send from the MMSC to the VASP and forward the > MMS to a java application. But the problem is that the MSISDN is only passed > on to the MMSC and not to the VASP. Right now I get the ip address of the > MMSC in the sender field: > > <mm7:Sender><mm7:RFC2822Address>194.182.251.15/TYPE=IPv4 > </mm7:RFC2822Address> > </mm7:Sender> > So my question is: how do I add the MSISDN to the sender field in the > MMSC? > > BR > > q:o) Theis > > _______________________________________________ > Users mailing list > [email protected] > http://lists.mbuni.org/mailman<http://lists.mbuni.org/mailman/listinfo/users> > /listinfo/users <http://lists.mbuni.org/mailman/listinfo/users> > >
_______________________________________________ Users mailing list [email protected] http://lists.mbuni.org/mailman/listinfo/users
