| Can't receive mms notification pls help |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through February 20, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| Anonymous |
I sent a MMS notification to retrieve the message from http://www.nowsms.com/download/btmms.mms but I dun received anything on my phone and I had test send & receive mms from my phone to other phones. Below is the message from the log. I can send wap push. I also got a "invalid content type text/plain" sending the same btmms.mms from my own webserver why is that so? pls help! 2004-02-08 12:22:37,4025B86E.req,202.156.109.9,91083021,OK -- Nokia 6100 (Cable),Binary=1;DCS=F5;UDH=0605040B8423F0;Data=6B06226170706C69636174696F6E2F76 6E642E7761702E6D6D732D6D65737361676500AF848C82983430323542383644008D909642542049 676E697465204D4D53008A808E02513C88058103093A8083687474703A2F2F7777772E6E6F77736D 732E636F6D2F646F776E6C6F61642F62746D6D732E6D6D7300 | |||
| Anonymous |
Below is my mmscdebug file on sending another mms notification 12:21:14:015 [0] main: Now MMSC Web server started on port number 80 12:21:16:031 [2] ThreadListenSMTPIn: Now MMSC SMTP server started on port number 26 12:52:20:031 [6] ThreadProcessConnection: Processing connection from 202.156.109.9... 12:52:20:031 [6] ThreadProcessConnection: Packet Length is 131 bytes 12:52:20:031 [6] ThreadProcessConnection: 47 45 54 20 2F 62 74 6D 6D 73 2E 6D 6D 73 20 48 GET /btmms.mms H 12:52:20:031 [6] ThreadProcessConnection: 54 54 50 2F 31 2E 30 0D 0A 55 73 65 72 2D 41 67 TTP/1.0 User-Ag 12:52:20:031 [6] ThreadProcessConnection: 65 6E 74 3A 20 4E 6F 77 20 53 4D 53 2F 4D 4D 53 ent: Now SMS/MMS 12:52:20:031 [6] ThreadProcessConnection: 20 47 61 74 65 77 61 79 20 76 35 2E 30 31 20 28 Gateway v5.01 ( 12:52:20:031 [6] ThreadProcessConnection: 62 32 30 30 33 31 32 33 30 29 0D 0A 41 63 63 65 b20031230) Acce 12:52:20:031 [6] ThreadProcessConnection: 70 74 3A 20 2A 2F 2A 0D 0A 43 6F 6E 6E 65 63 74 pt: */* Connect 12:52:20:031 [6] ThreadProcessConnection: 69 6F 6E 3A 20 43 6C 6F 73 65 0D 0A 48 6F 73 74 ion: Close Host 12:52:20:031 [6] ThreadProcessConnection: 3A 20 65 72 63 2E 6D 79 66 74 70 2E 6F 72 67 0D : erc.myftp.org 12:52:20:031 [6] ThreadProcessConnection: 0A 0D 0A 12:52:20:046 [6] ThreadProcessConnection: Sending C:\PROGRA~1\NowSMS\MMSCDATA\btmms.mms 12:52:20:046 [6] ThreadProcessConnection: Processing Complete | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1849 Registered: 10-2002 |
If you can send a WAP push to your phone ok, but you cannot send a notification for that file with the URL pointing to our web site, then this most likely indicates that your mobile operator has closed their network to external MMSCs. This means that the only way that you can use NowSMS to send MMS messages are: 1.) If you change the settings on recipient mobile phones to a different GPRS APN and WAP gateway IP address (usually just copy the GPRS APN and WAP Gateway IP config that is used for your WAP browser settings). 2.) Configure NowSMS to send MMS messages through the operator MMSC over GPRS, instead of performing direct delivery. 3.) Use Multimedia WAP Push and deliver the multimedia content to the WAP browser instead of the MMS client. Here are some links that explain how MMS works, and will better explain the "closed" issue that I mentioned above. They will also explain the two approaches that can be used for sending MMS (which approach you use depends on whether or not your mobile operator has blocked access to external MMSCs). http://support.nowsms.com/discus/messages/1/589.html http://support.nowsms.com/discus/messages/485/1958.html Regarding your other questions:
Because the MIME content type for the MMS message file is not configured on your web server. See this thread for a more complete discussion: http://support.nowsms.com/discus/messages/485/1350.html Regarding the mmscdebug.log, that appears normal. Before NowSMS sends a notification for a URL, it verifies that the URL is valid, and has the correct MIME content type, and has valid content. In this case, it is NowSMS that is fetching the URL from the MMSC to validate this fact ... before it sends out the notification. -bn | |||
