Don't receive originator's phone number on MO MMS

Author

Message

Dirk Müller
New member
Username: Pflapf

Post Number: 1
Registered: 06-2009

Posted on Monday, June 15, 2009 - 04:00 pm:

Hi,

we have a setup for 2-way MMS with NowSMS delivering the MMS directly to the phone. Phone's APN is changed, VASP and users are created, routing MO MMS to a Java servlet via MM7 works and it looks really fine, only one problem remains. On the phone we have a generic user/pw set in the URL, i.e. http://..../generic=generic. Whenever the servlet receives an MM7 request the sender's number is posted as "generic" like the authenticated user name.
How can we get the originator's number instead?

Thanks a lot,
Dirk

Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 7782
Registered: 10-2002

Posted on Tuesday, June 16, 2009 - 02:09 pm:

Hi Dirk,

In the "MMSC Routing" definition for your MM7 application, make sure to check "Allow Sender Address Override".

-bn

Dirk Müller
New member
Username: Pflapf

Post Number: 2
Registered: 06-2009

Posted on Tuesday, June 16, 2009 - 02:57 pm:

Hi Bryce,

this checkbox is already enabled.

Regards,
Dirk

Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 7785
Registered: 10-2002

Posted on Tuesday, June 16, 2009 - 03:14 pm:

Enable the SMSDEBUG.LOG and MMSCDEBUG.log and let us see a message being received and processed.

Also there was a recent issue...try downloading http://www.nowsms.com/download/nowsms2009rc.zip

Dirk Müller
New member
Username: Pflapf

Post Number: 3
Registered: 06-2009

Posted on Tuesday, June 16, 2009 - 04:47 pm:

Hi Bryce,

I attached the content of a message of the mmsc debug log.
Please note the following: the authentication username and password is +49173230975. The msisdn that sends the MMS is +491732309756.
As you can see the MM7 post to my linux notebook contains the authenticated user name instead of the originator's msisdn.

I hope that helps.

Thanks,
Dirk

extract from mmsc debug log
mmscdebuglog.txt (14.4 k)

Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 7788
Registered: 10-2002

Posted on Wednesday, June 17, 2009 - 11:31 pm:

Hi Dirk,

The issue here is that we have no way of knowing the originator's actual MSISDN.

When a phone submits a message to an MMSC, the phone doesn't send anything to identify itself. The actual from field usually contains a token that is asking the MMSC to insert the device's address as the sender.

How the MMSC identifies the device is actually outside of the scope of the MMS protocol. In a real world mobile operator environment, we do this by receiving information from the WAP gateway, which in turn receives the information via RADIUS (this process is described in the following document: http://www.nowsms.com/support/bulletins/tb-nowsms-002.htm)

Without access to that type of information, the only alternative is to have URLs that embed the device identification ... which is where we are getting that other phone number from.

-bn

Dirk Müller
New member
Username: Pflapf

Post Number: 4
Registered: 06-2009

Posted on Thursday, June 18, 2009 - 05:52 am:

Hi Bryce,

thanks for this info! I was not aware that the MSISDN isn't part of the mms request from the phone.
Is there a way to provision MMSC users automatically, i.e. via webservices or something similar?

Thanks,
Dirk

Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 7792
Registered: 10-2002

Posted on Monday, June 22, 2009 - 02:30 pm:

Hi Dirk,

Sorry for the delay in response.

Here is a link that explains an HTTP interface for account provisioning:

http://support.nowsms.com/discus/messages/485/5907.html

-bn

Dirk Müller
New member
Username: Pflapf

Post Number: 5
Registered: 06-2009

Posted on Tuesday, June 23, 2009 - 07:09 am:

Hi Bryce,

thanks for your support, I'll check the docs.

Dirk

Dirk Müller
New member
Username: Pflapf

Post Number: 6
Registered: 06-2009

Posted on Thursday, June 25, 2009 - 12:24 pm:

Hi Bryce!

We changed the mmsc.ini and added the following parts to [MMSC]:
MSISDNHeader=X-MSISDN
MSISDNHeaderGateways=*
MSISDNHeaderAutoProvision=Yes

Also we now have an X-MSISDN header in the request, it's something like

POST /+4917323097512=+4917323097512 HTTP/1.1
X-MSISDN: +4917323097512
... and some more headers + content

In the MMSC log I see the following line:
2009-06-25 12:14:46,MMSIN,10.223.202.58,+4917323097512,,User Not Defined,FAILED

Is there anything else that I need to do to enable auto-provisioning or use it correctly?

Thanks,
Dirk

Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 7814
Registered: 10-2002

Posted on Thursday, June 25, 2009 - 11:51 pm:

Hi Dirk,

I don't have access to verify this at the minute, but I think you need to specify *.*.*.* for the gateway wildcard setting.

-bn

Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 951
Registered: 08-2008

Posted on Friday, June 26, 2009 - 05:56 pm:

Hi Dirk,

Just following up. Bryce is correct, it needs to be MSISDNHeaderGateways=*.*.*.* if you want the header to be accepted from any source address.

--
Des
NowSMS Support

Dirk Müller
New member
Username: Pflapf

Post Number: 7
Registered: 06-2009

Posted on Monday, June 29, 2009 - 07:51 am:

Hi Bryce, hi Des,

thanks for your support, works now. :-)

Dirk

charlier yohann
New member
Username: Zucko

Post Number: 1
Registered: 06-2009

Posted on Thursday, July 16, 2009 - 03:06 pm:

Hello,

At first sorry for my english....

It makes a long time that i try to configure my nowsms but i have some problems:
At first, i didn't succeed in receipting MMS via Nowsms but i have no problem to send MMS.
In a second time, when i test a mobile i can't send a MMS with it but i have no problem of MMS reception.

I use this configuration for my mobile : "APN: testbouygtel1; mmsc url : http://xxx.bttiv.org:8080; No Proxy".

I send with my post all the capture that can help you in order to see all my problems.

Thank you for your fast help.....

}