| No save option on nokia 3650s from wapPush |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through March 23, 2004 ⬆ |
◄ ► |
| Author | Message | ||||
| billComer Unregistered guest |
Hi there, When I wapPush to a nokia 7210 all is fine. When I wapPush to a nokia 3650 I do not get an option to save the content. Any clues? The url I am using to post to the NowSMS is of the form: http://nowsms.me.com:8800/?PhoneNumber=0766666666662&WAPURL=http%3A%2F%2Fmediast ore. huey%2FMediaCollector%3Fid%3D3843024732990622720 I am not pushing the content onto the nowSMS box. This is a link to a servlet that performs a one-shot grab of the content. One thought is 'should I be using Multimedia WAP message' instead ? | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1672 Registered: 10-2002 |
Hi Bill, I tried the "Send Multimedia WAP Message" option sending to a Nokia 3650, and it does give me an option to save the image. When the image is displayed, "Save" is the first menu option on the "Options" menu. I see that if I send a push that links directly to an image, the 3650 will not allow it to be saved, so that is probably what you are encountering. -bn | ||||
| Bill Comer New member Username: Billcomer Post Number: 1 Registered: 01-2004 |
Thx, When I go through the "Send Multimedia WAP Message" I also get a save option. However when I post to the URL as above I do not. I am struggling to find the documantation referring to the API for Multimedia WAP. I have found this http://www.nowsms.com/documentation/ProductDocumentation/sending_messages/url_pa rameters_for_sending_messages.htm And I have found reference in the forums to the parameter 'MMSWapPush=YES' but I am unclear what other parameters I need to make my WapPush an MMSWapPush. Please help. I am also unclear what the difference is between a WapPush and an MMSWapPush. Please also help. | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1688 Registered: 10-2002 |
Hi Bill, Sorry, this is a bit confusing. I need to do a write-up on how to submit messages using the multimedia WAP push function. Basically, the way that it works is that you are actually posting the content to the gateway. The push that gets sent out to the device is then a URL that resides on the gateway, instead of on your existing web server. Submitting one of these multimedia WAP pushes to NowSMS is basically the same as submitting an MMS message. Any of the APIs that can be used for submitting an MMS, can also be used for submitting a multimedia WAP push. http://www.nowsms.com/documentation/ProductDocumentation/mms_notifications_and_content/Submitting_MMS_Messages.htm However, there is a flag in each one of these settings that tells NowSMS to send it as a push instead of as an MMS. I'll go ahead and explain this in relation to each of the APIs. Sorry if this is a bit overwhelming, but I think it is important that we have this documented somewhere, even if it is just in this discussion board posting for now. For the proprietary URL approach: http://www.nowsms.com/documentation/ProductDocumentation/mms_notifications_and_content/Submitting_MMS_Messages_URL.htm You would need to add another section to the multipart, which would define the MMSWAPPush variable. For example, insert this after the MMSSubject section of the multipart: ----boundary-border-- Content-Disposition: form-data; name="MMSWAPPush" Yes For the MM7 approach: http://www.nowsms.com/documentation/ProductDocumentation/mms_notifications_and_content/Submitting_MMS_Messages_MM7.htm Add /TYPE=WAPP after the phone number of a recipient. This will tell NowSMS to send the message out as a multimedia WAP push instead of an MMS. (Note: There is a bug, and this approach does not work properly in the current v5.0 or v5.01 versions. If you have a need to use this approach, we can supply an update to fix this problem.) For the MM4/SMTP approach: http://www.nowsms.com/documentation/ProductDocumentation/mms_notifications_and_content/Submitting_MMS_Messages_MM4.htm To send via multimedia WAP push instead of MMS, change the address in the RCPT TO: to be <phonenumber.wappush@mms.domain.name> or <phonenumber/TYPE=WAPP@mms.domain.name>. For the MM1 or EAIF approach: http://www.nowsms.com/documentation/ProductDocumentation/mms_notifications_and_content/Submitting_MMS_Messages_MM1.htm http://www.nowsms.com/documentation/ProductDocumentation/mms_notifications_and_content/Submitting_MMS_Messages_EAIF.htm Specify the recipient address in the format phonenumber/TYPE=WAPP (instead of phonenumber/TYPE=PLMN which is what would be used for sending an MMS). Finally, a PHP example: I've also modified the sendmms.php example that is found at the following link: http://support.nowsms.com/discus/messages/1/1113.html So that it can be used to send a multimedia WAP push message instead. The PHP script is attached.
-bn | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1690 Registered: 10-2002 |
Bill, Further to all this, I should also clarify my earlier comment about why you don't see the save option in your push, but you do in our Multimedia WAP Push. In your push, you are sending a push that links directly to the image. Some devices don't like that. (In this case, the Nokia 3650 will display it but won't let you save it.) By contrast our Multimedia WAP Push is sending a link to a WML page that then links to the image. This approach, of linking to a WML page first seems to work better with more browsers than pushing a direct link to an image. While I'm babbling (it's been a long day), I should also mention that the Multimedia WAP Push function now has an option to delete content after it has been downloaded. See the http://www.nowsms.com/whatsnew.htm, but the short is: MMS/Multimedia WAP Push: Add configuration parameter to delete dynamically generated links (such as those used when sending MMS or Multimedia WAP Push) after they are accessed. To enable this feature, edit MMSC.INI, and under the [MMSC] section header, add ExpireDynamicLinks=##, where ## is the number of minutes after the link is first accessed before it should be automatically deleted. | ||||
| Bill Comer New member Username: Billcomer Post Number: 2 Registered: 01-2004 |
Bryce, Thx for all the info. I am now back on the case after a short interlude. I find I can post an MMS WAPPush successfully to a phone and get the save option if the URL is to an existing image. EG: http://nowsms.lammtara.com:8800/?PhoneNumber=07123456789&MMSWAPPush=Yes&MMSFrom= sender2@domain&MMSSubject=Message+Subject&MMSText=An+optional+text+part+of+the+message& MMSFile=http://www.nowsms.com/media/logo.gif However if I repeat the above but instead of specifying a file I specify a URL which points to a servlet that will return the image EG http://nowsms.lammtara.com:8800/?PhoneNumber=071234567789&MMSWAPPush=Yes&MMSFrom =bill@nowhere.com&MMSSubject=your+pic&MMSText=here+is+your+pic&MMSFile=http://mediastore.com/MediaCollector?id=6670310738862954496 ...then I get the following text 'Sorry, Download failed' instead of the image. This servlet sets the mime-type and returns the data and works fine through a browser. I guess this might be because the link referred to in MMSFILE does not have an extension. I know I could get around the problem by temporarilly storing the file and uploading that and then deleting it after, but I would rather not due to performance implications. Have you any suggestions please? | ||||
| Bill Comer New member Username: Billcomer Post Number: 3 Registered: 01-2004 |
Here I am again...still with no luck. Following an idea from http://support.nowsms.com/discus/messages/132/2636.html I have changed the Servlet mapping in my web.xml to map to /sevletName* Now if I retreieve in the browser http://mediastore.com/MediaCollector/fakeName.jpg?id=6670310738862954496 I can save the file as fakeName.jpg. However NowSMS still can not retrieve this. It has a zero length file in the MMSCDATA directory. Any ideas anyone ? | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 2108 Registered: 10-2002 |
Bill, Apologies for not replying back to you on this, I must have missed the message. I can confirm that when you use the "MMSFILE" parameter to point to a URL, NowSMS has a problem if the URL includes a "?" character. NowSMS expects the last part of the URL to point to be a valid filename, and it gets confused by the "?" character. I've got an update that fixes this problem. If you are still interested after all this time, please send an e-mail to nowsms@now.co.uk, and I will send this to you. (This fix is not included in the current v5.50 beta, but will be included in the v5.50 release version.) -bn | ||||
SendMMWapPush.php
