Problem with URL from MMWAPURLOnly=Yes (annoying!)

Problem with URL from MMWAPURLOnly=Yes (annoying!) SearchSearch
Author Message
Lars Nielsen, MobileNation ApS - Denmark
Frequent Contributor
Username: Larsmservice

Post Number: 291
Registered: 10-2003
Posted on Tuesday, July 29, 2008 - 01:24 pm:   

I have a problem. It's really annoying.

I am sending a multimedia wap push with the param: MMWAPURLOnly=Yes

Nowsms returns a text/plain with the text:
URL=http://xxx.xxx.com:8080/20080729/12/009E56C7.wml?id=1234

My plan is to read that .wml page and change it myself so it supports xhtml. Basically read the content and build a new file from that.

But...
Nowmss is killing me! If i use a browser or any phone to enter the generated URL, mmscdebug.log says this:


14:02:34:328 [7] ThreadProcessConnection: C:\NowSMS\MMSCDATA\20080729/14/6D365FB1.INI
14:02:34:328 [7] ThreadProcessConnection: MSISDN does not match message recipient
14:02:39:328 [7] ThreadProcessConnection: HTTP/1.1 404 Not Found
Content-Length: 0
Connection: Keep-Alive

WHY?

If i send a wappush as normal the phone can enter fine. But not like above.

It is irritating me and i've spent all day on this.

Can you tell me what i am doing wrong here ???


;)Lars
Lars Nielsen, MobileNation ApS - Denmark
Frequent Contributor
Username: Larsmservice

Post Number: 292
Registered: 10-2003
Posted on Wednesday, July 30, 2008 - 02:54 pm:   

My second day on this problem. Still i got no idea...

Lars Nielsen, MobileNation ApS - Denmark
Frequent Contributor
Username: Larsmservice

Post Number: 293
Registered: 10-2003
Posted on Thursday, July 31, 2008 - 03:10 pm:   

Could somebody @nowsms support team please have a look at this ???
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 19
Registered: 08-2008
Posted on Tuesday, August 19, 2008 - 08:35 pm:   

Are you including the "?id=1234" parameter?

It's basically a check to help reduce trolling for files. The number after "?id=" must match a recipient of the original message.

--
Des
NowSMS Support
Lars Nielsen, MobileNation ApS - Denmark
Frequent Contributor
Username: Larsmservice

Post Number: 294
Registered: 10-2003
Posted on Tuesday, August 19, 2008 - 11:54 pm:   

Yes i have includede the GET param.
The problem (or bug perhaps) is when i send it to nowsms with MMWAPURLOnly=Yes, i cannot access it.

If i send it normally everything works perfectly...
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 36
Registered: 08-2008
Posted on Wednesday, August 20, 2008 - 08:41 pm:   

Lars,

Perhaps this is a stupid question as I'm not familiar with this feature until this week.

But did this ever work?

Here are a few things that I found out in my testing ...

1.) The URL works if you have the MMSC bound to a specific IP address, and you make a request to retrieve it that originates from that same IP address.

2.) If you edit MMSC.INI, and under the [MMSC] header, add MSISDNMatchRequiredForReceive=No, then this particular check will be disabled.


From what I can see, that .INI file that is referenced in the MMSCDEBUG.LOG normally would contain the MSISDN of the intended recipient. But it does not get recorded if you use the MMWAPURLOnly=Yes parameter.

So my question is ... did this work at one time in an older version, but it doesn't work any more. Or could #1 explain what you might have experienced before?


--
Des
NowSMS Support
Lars Nielsen, MobileNation ApS - Denmark
Frequent Contributor
Username: Larsmservice

Post Number: 295
Registered: 10-2003
Posted on Wednesday, September 03, 2008 - 08:35 am:   

IT WORKED!
This worked: "MSISDNMatchRequiredForReceive=No".

That's all i needed to know ;-)
Thankyou.

I will now be able to deliver MMS-WP to Iphones.

;)Lars