| Send MMS |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through September 15, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| Anonymous |
Good day. I have acquired a copy of your free trial nowsms.exe and installed it on a windows xp environment. I can now send sms using nowsms. My question is this: how can I retrieve the mms file that I created for example the file "3EF55180a.mms" facts are sa follows: 1.) I have uploade the file to a webserver "http://abs-axxxxxx.com/3EF55180a.mms" so that I can retrieve the 3EF55180a.mms in me GSM phone via GPRS. The site http://xxx-xxxxxx.com/3EF55180a.mms can even be access thru a browser in a PC. 2.) When I tried to send a mms notification message to Phone Number :+639173213506 and MMS URL : http://xxx-xxxxxx.com/3EF55180a.mms I get a error message :"Error: Invalid Content Type for URL: application/octet-stream " 3.) I tried to send the site address via WAP Push message and was successfully received by my GSM Phone but when I tried to retrieve the file I get a "conncection time-out" did i miss something? or is it me telco is having a firewall to block me from retrieving the file? BTW, I can surf thru my GSM phone via gprs. Thanks for the support and waiting for your reply. | |||
| Bryce Norwood - NowSMS Support |
Hi, Let me explain "the facts" ... 1.) Self-explanatory. 2.) If you want to serve up the MMS content from an external web server, you must configure the web server to present the correct MIME content type. The notification is going to tell the mobile phone to fetch this URL as MMS message content, and therefore we validate that the MIME type is correct before sending out the message, so that the recipient mobile phone will understand it. The MIME type must be "application/vnd.wap.mms-message". 3.) That is to be expected. The WAP browser and MMS client are logically separate entities, and most WAP browsers cannot receive MMS content. Even if the WAP browser could retrieve MMS content, or pass the MMS content to the MMS client automatically ... it is a little more complicated. The MMS client expects to receive a notification first, and then it expects to fetch the content URL referenced in that notification. Without receiving the notification first, the MMS client would not know what to do with the content URL. Bottom line, what you are seeing is normal. -bn | |||
| manish |
hello | |||
| Anonymous |
 } testtttttttttt.... | |||
| avism |
Hi, I have experienced some strange problem while sending MMS messages to a Nokia 7650 cell phone. I am trying to evaluate the NOW.SMS, last week I have successfully sent and received MMS messages on my phone but for the last couple of days I just receive the "retrieve message" notification and then a notification sound that a new message received but no message exist. Just to clarify: 1.I am sending the same MMS message as before, or even just plain test. 2.I am sure and rechecked that NOWsms ip + port is open to the internet. 3.I do receive MMS message sent from my cell phone to my self. 4.The log file MMSC-20030831.LOG do prints the following line(2003-08-31 09:46:41,MMSRETRIEVE,192.116.86.209,,,20030831/09/3F51A68Aa.MMS,OK,1519) which means the cell phone did retrieved the mms message. Any idea what could be the problem? Thanks Avi. | |||
| khalid |
| |||
| Bryce Norwood - NowSMS Support |
Avi, If you're sending a message through the web menu interface, there is an extra "MMSRETRIEVE" entry that is generated in the MMSC-yyyymmdd.LOG file which can be misleading. I suspect that 192.116.86.209 is the IP address of the PC that is submitting the message. What happens is that when the web interface is used to submit an MMS message ... internally we build the MMS message, store it on the MMSC, and then fetch it back to verify that things are configured correctly. Unfortunately, this results in an extra bogus line MMSRETRIEVE entry in the log file. So I suspect the phone is not able to connect to the MMSC via the GPRS APN and WAP gateway that are configured for the MMS settings. You might want to try to create a simple WML file, and store it in the MMSCDATA subdirectory (be sure to use a .WML file extension, let's say it is named test.wml for this example). Then configure the WAP browser in the phone to use the same access point settings as the MMS client ... and verify that you can connect to the MMSC with the WAP browser to fetch the WML file (you can reference a file named test.wml in the MMSCDATA directory, by connecting to host.name:port/test.wml). -bn | |||
| avism |
Hi Bryce, Thanks, I would just like to clarify that Wap push and send Wap multimedia messages do work correctly, so probably my Wap configuration are OK. Could the problem be with my operator? could be that he filters MMS mime type response from servers other then its own one. Just to remind again, "I receive the "retrieve message" notification and then a notification sound that a new message received but no message exist." did you ever experienced this. Thanks Avi. | |||
| Bryce Norwood - NowSMS Support |
Avi, The filtering has nothing to do with MIME types, and its not really filtering per se. What the issue usually is ... is that the WAP browser and the MMS client have separate connectivity settings. Each has a GPRS APN and WAP Gateway IP address associated with it. Many operators establish a separate GPRS APN and WAP gateway for MMS ... they then establish IP restrictions so that the WAP gateway that is used in the MMS settings can only connect to the operator MMSC. Check the GPRS APN and WAP Gateway IP that are configured in the "access points" that are defined in the 7650. To determine the access point settings used by the WAP browser, go into Services, select Options/Settings. Then select Options/Change, Options/Edit to find the details about the GPRS APN and Gateway IP address. To get to the MMS settings, go into Messaging. Select Options, Settings, Multimedia Message. Then you can go into Options/Change, Options/Edit to find out the details of the settings. -bn | |||
