| CONFUSING MMS and WapPush |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through October 19, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| alya New member Username: Alya Post Number: 14 Registered: 12-2003 |
Hi Bryce... Not Understand..Understand...not understand...that's i feel. It's look like same in nowsms..just different parameter : WAPUrl or MMSUrl. Could you explain to me about mms and wappush in nowsms terminology and technic (or in the world)  | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6257 Registered: 10-2002 |
The WAPURL parameter is used by the "Send WAP Push Message" page in the web interface. Basically, this is used when you want to send a WAP push message to the phone. The UI varies from phone-to-phone, but generally the recipient will see the text that you include in the message, and have an option to launch the URL that you included in the push. This URL would be loaded by the browser, so it would normally be a WML or basic XHTML page. (The URL could also point directly to an image, or some other content type supported by the phone. But phones generally expect the URL to be a page that can be displayed by the browser, and some phones can get confused if the link points directly to some other content ... for example, on some Nokia phones, if you link directly to an image, the image will be displayed but no option will be available to allow the recipient to save the image.) Some phones refer to a WAP Push message as a "Service Message" (Nokia seems to use this terminology) or a "Browser message" (Motorola seems to use this terminology). The "MMSURL" parameter is used by the "Send MMS Notification" page in the web interface. This parameter can only point to a compiled MMS message file residing on another web server. Note that more than half of the mobile operators out there don't allow MMS messages to be fetched from an external source like this, so it may fail. (See http://www.nowsms.com/howmmsworks.htm for more background on how MMS works.) -bn | |||
| alya New member Username: Alya Post Number: 15 Registered: 12-2003 |
Ok...it's much helpful for me, i confuse because on this forum some sample write (can) : mmsurl=http://ip:port/path/image1.gif or sometime mmsurl=http://ip:port/path/mymms1.mms. So I Think, if in mmsurl you can put direct to object (not only *.mms), it's no different with wapurl. thanks :alya | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6281 Registered: 10-2002 |
Hi Alya, No, you cannot point "MMSURL=" to a ".gif" ... only a ".mms". You might be confusing the "MMSFILE=" parameter. "MMSFILE=" can point to a ".gif" file. "MMSFILE=" tells NowSMS to build an MMS message and send it ... via whatever outbound MMS delivery settings are configured in NowSMS (might be as a direct delivery MMSC, might be over a GPRS modem). "MMSURL=" sends out a raw MMS notification message telling the receiving client to try to fetch an MMS message from the specified URL. | |||
| Sarah Gindin New member Username: Sarahgindin Post Number: 1 Registered: 04-2007 |
[spam deleted] | |||
