"From" field seems not to inserted

"From" field seems not to inserted SearchSearch
Author Message
Jean-Michel
Posted on Friday, January 17, 2003 - 11:08 am:   

Hi,

We looked at the MMS message headers sent with a Nokia 7650 and an Ericsson T68i. It appears the phone does not include the "from" header parameter in the message headers. At the same time, when we fetch the MMS, the phone indicates that the message was by "from" ...
- Does your MMSC insert the from field in the message fetched ? Is it based on the alias/passwd configuration ?
- Do you know if some MMS phones inserts it ?

Or am I wrong ...?

Thanks again,
Bryce Norwood - NowSMS Support (Bryce)
Posted on Friday, January 17, 2003 - 03:36 pm:   

Hi,

Yes, our MMSC inserts the From, and it is based on the login information (alias or phone number and password) in the message server URL.

No, I haven't seen any MMS phones that insert this information themselves.

-bn
Jerome
Posted on Friday, January 17, 2003 - 05:20 pm:   

What are doing mobile-operators ?
Do they insert the MSISDN in the from field on the MMSC (by interrogating a database linked to the GGSN) or do they insert an HTTP header containing the MSISDN at WAP Gateway level and then the MMSC is using this header to fill the from field ?

Jerome
Bryce Norwood - NowSMS Support (Bryce)
Posted on Friday, January 17, 2003 - 07:15 pm:   

I believe that they are getting an HTTP header from the WAP gateway (at least that is the way that we recommend doing it).

Keep in mind that in order for the WAP gateway to get the MSISDN, it needs to be getting information from the GGSN. (With our WAP gateway, we'll take a Radius accounting feed from the GGSN.)

-bn
Jerome
Posted on Friday, January 17, 2003 - 08:11 pm:   

So you have a way to read the msisdn from the http header. It is not mentionned in the doc or support messages, can you precise the way to do it ? (I imagine that this a setting to put in the MMSC.INI file). Thanks for your high-quality support.

Regards,
Jerome
Bryce Norwood - NowSMS Support (Bryce)
Posted on Tuesday, January 21, 2003 - 04:24 pm:   

Hi Jerome,

I want to follow-up with you directly via e-mail to make sure that I understand your configuration.

The support for this functionality can be a little tricky, as it requires specific understanding of the host environment.

I'm sending an e-mail to your address posted here. If for some reason that address is not correct, feel free to contact me at nowsms@now.co.uk.

-bn
Feras
Posted on Sunday, June 08, 2003 - 07:58 am:   

hello
i need some information on how to configure getting MSISDN from the mms. can u tell me how can i do it both ways : the raduis way and getting it from the url way in case the operator does not have raduis cabapility?
thanx alot
Bryce Norwood - NowSMS Support
Posted on Wednesday, June 11, 2003 - 10:24 pm:   

Feras,

There are only two ways to get the MSISDN of a device that is submitting an MMS message.

1.) It is supplied by the device. With the Now MMSC, we allow you to manually define MMS users in the configuration dialog, and when users configure the MMSC URL in their phone, they include a username and password in the URL which is used to identify them to the MMSC.

2.) The MSISDN is validated and supplied by a proxy server on the network. In today's environments, most commercial MMS compatible devices uses a WAP gateway proxy and a limited few can use an HTTP proxy.

By the time the request makes it to the MMSC, the MMSC only sees an HTTP request coming in from the IP address of the proxy, with no other identifying information.

Where Radius comes into play is that there is no built-in mechanisms for the device to identify itself to the proxy. So the normal way of supporting this functionality is for the proxy to rely on a Radius accounting feed. So it is actually the WAP gateway (proxy) that is interfacing with Radius. The WAP gateway uses information supplied through Radius protocols to get the MSISDN of a connected device.

The WAP gateway then must be configured to pass the MSISDN to the MMSC when it proxies a request to the MMSC.

We've got a document that describes this latter approach at the following link: http://www.nowsms.com/tb/TB-NOWSMS-002.htm

There are also some notes in the read me for the current release that talk about configuration parameters for the MMSC to receive the MSISDN from other WAP gateways. (Of course, the WAP gateway must be configured to pass the MSISDN along to the MMSC ... for privacy reasons, most operator WAP gateways will not forward MSISDN to external content servers.)

-bn