| NowSMS as MMSC gateway... |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through July 28, 2006 ⬆ |
◄ ► |
| Author | Message | |||
| Pancho New member Username: Pancho Post Number: 9 Registered: 09-2005 |
Hi, Does anybody here have done this? Can Now SMS become an MMSC server? If so, please help me how did you guys did this... Thanks in advance. Regards, Pancho | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5238 Registered: 10-2002 |
Hi Pancho, Can you please clarify your question? I don't really understand what you are asking. For more information on how MMS works, and issues of NowSMS being either an "MMSC" or an "MMS Gateway connecting to an operator MMSC", please see http://www.nowsms.com/howmmsworks.htm. -bn | |||
| Pancho New member Username: Pancho Post Number: 11 Registered: 09-2005 |
Hi Bryce, Is it possible that NowSMS will become an independent MMSC? For instance, I can still send and receive MMS without connecting NowSMS to an operator's MMSC. Thanks, Pancho | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5261 Registered: 10-2002 |
Hi Pancho, NowSMS is an MMSC. There are even mobile operators who use it as their MMSC. However, there are practical considerations for whether or not it can be used as an MMSC for specific environments, because of restrictions imposed by various mobile operators. The thread that I referenced above explains those considerations. (http://www.nowsms.com/howmmsworks.htm) Note that in order to send MMS, you do need to have SMSC connectivity from NowSMS. The following guide covers the basics of setting up NowSMS as an MMSC: http://www.nowsms.com/documentation/quickstartguide/ -bn | |||
| Pancho New member Username: Pancho Post Number: 12 Registered: 09-2005 |
Hi Bryce, Thanks for your assistance. Will look into it. I hope the procedures are not too complicated  Regards, Pancho | |||
| Pancho New member Username: Pancho Post Number: 15 Registered: 09-2005 |
Hi Bryce, Thanks for the instruction on how to setup NowSMS as an MMSC. I have successfully dedicate an external IP address where NowSMS resides. I tested sending MMS using the Web Interface it says message submitted however, the MMS didn't arrive in my mobile phone... I'm curious is it possible to send MMS using Nokia 7250 as my GSM modem? Please confirm... Thank you. Regards, Pancho | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5265 Registered: 10-2002 |
Hi Pancho, Yes, it is possible using that device as a modem, but you can have situations where the mobile operator blocks MMS delivery from external MMSCs (as described in the "howmmsworks" link referenced above). My advice for troubleshooting is this ... 1.) Send a simple text SMS message and verify that it works. 2.) Send a simple WAP Push message (use any URL, http://wap.oa.yahoo.com is one I usually use for testing), and verify that it can be received. 3.) Send a multimedia WAP Push message. This works like the WAP Push message in the previous step, except that it builds a dynamic URL on the NowSMS MMSC (so that you can verify that you have connectivity back to the HTTP port of the MMSC). 4.) Assuming all of the above works, then try your MMS test. It may be helpful to have a phone other than a Nokia phone on the receiving end. Most other phones will give you an indication that they have received an "MMS Notification", even if they cannot access the URL that contains the MMS message ... but Nokia phones generally don't give you any indication (some show a spinning envelope in one of the corners, but that's it). ... So if you get through 1 thru 3 ok, and 4 is not working, then it is likely that your mobile operator does not allow messages from external MMSCs. In this case, the alternatives are: a.) Change the settings on the mobile phone to an access point and gateway/proxy which are open to external sites. (This is generally only feasible for testing environments or closed user group implementations, and is not recommended for general purpose environments.) b.) A connection to the operator MMSC using an MMS related protocol (I know you've had issues with your mobile operator because they say they support MM7 but are using some strange LogicaCMG PAP interface.) c.) Submit messages via your operator MMSC using a GSM/GPRS modem. There is a link from "howmmsworks" that explains this in more detail. But basically, in NowSMS, you define an "MMSC Routing" that uses the MM1 protocol over a GPRS modem. You then need to configure the MMSC settings that are specific to that mobile operator. d.) Use an alternative such as multimedia WAP Push. -bn | |||
| Pancho New member Username: Pancho Post Number: 16 Registered: 09-2005 |
Hi Bryce, I followed your instruction above and I can now send MMS using the Web Interface. Is it possible to send MMS without using the Web Interface? Thanks, Pancho | |||
| Pancho New member Username: Pancho Post Number: 17 Registered: 09-2005 |
Hi Bryce, I found the answer to my problem... http://support.nowsms.com/discus/messages/1/1113.ht ml Thanks again. Pancho | |||
| Pancho New member Username: Pancho Post Number: 18 Registered: 09-2005 |
Hi Bryce, I was able to send MMS message (text) using the Web Interface however, when I tried sending an image file... My recepient received an MMS message containing the text message with a download button in it. But, when we tried pressing the download, we didn't get the image file that I have attached. Any idea? Thanks, Pancho | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5362 Registered: 10-2002 |
Hi Pancho, If there was a download link in the message, it sounds like you sent a multimedia WAP push. Did you send an MMS or a multimedia WAP Push? If you sent an MMS, there's no way that there would be a download link. However, some phones are a little funny if you don't include a SMIL file in your MMS message, and they display any objects in the message as attachments. (What is a SMIL file? See http://support.nowsms.com/discus/messages/1/828.html) Another issue could be the file extension in the file name of the image. Make sure to use an appropriate file extension, such as .gif or .jpg, because NowSMS figures out the appropriate MIME type based upon the file extension. If you are using multimedia WAP Push, then it is also possible that it is a MIME type issue. Or, if the image is very large, it could be a size limitation on the operator WAP gateway. I'd be curious to see the MMSC-yyyymmdd.LOG file, just to make sure I understand whether we're talking about MMS or Multimedia WAP Push. -bn | |||
| Pancho New member Username: Pancho Post Number: 20 Registered: 09-2005 |
Hi Bryce, I tried sending an MMS using the Web Interface (Send MMS Message). This time I attached a PNG file with sample text message(Test) and sent it to XDA IIs. The results are still the same, download button appeared in the MMS message and the body (text) was there but, not the image file. I also checked the MMSCDATA Folder and there was a .MMS so, I don't know what could be the problem. Here's what I got from the MMSC-20060110 Log File. 2006-01-10 10:35:10,MMSRETRIEVE,192.168.2.150,,,20060110/10/43C31D60a.MMS,OK,587 In my MMSC settings I didn't put any configuration like Local Host Name or IP address and etc. because, I only need the functionality where I can send MMS through NowSMS. Please help. Thanks, Pancho | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5426 Registered: 10-2002 |
Pancho, I'm sorry, but I'm confused. I think I just don't have a full picture of what is going on. Can you enable the SMSDEBUG.LOG and MMSCDEBUG.LOG files ... and repeat sending your message. Then I'd like to look at the SMSDEBUG.LOG and MMSCDEBUG.LOG ... and perhaps that will give me a better idea of how your system is configured. -bn | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5427 Registered: 10-2002 |
P.S. - Maybe you just need to include a SMIL file in the MMS message? (See http://support.nowsms.com/discus/messages/485/5962.html) | |||
| Pancho New member Username: Pancho Post Number: 21 Registered: 09-2005 |
Hi Bryce, Pardon my ignorance where should I include the smil file again? Do I have to type it in the body text? Thanks, Pancho | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5483 Registered: 10-2002 |
Hi Pancho, The SMIL file gets included in as one of the attachments of the message. (If you are using the web interface of NowSMS to submit the message, also put your text into a file attachment instead of putting it in the text box, then have the SMIL reference that text file name as well as any images.) But maybe we should backup a minute ... Try sending the following file as an MMS message on your system and see if you get a presentation: http://www.nowsms.com/download/btmms.mms (This is a real old file, but it's the only simple MMS message that I had sitting around for a test.) -bn | |||
| Pancho New member Username: Pancho Post Number: 22 Registered: 09-2005 |
Hi Bryce, I downloaded the .mms file from the link above and tried sending it using the interface. When the message arrived in my XDA IIs unit. Its still the same, it shows the MMS information with the download button but, when I pressed the button, the .mms content doesn't appear. I tried sending the same message twice and its still the same. In case, I have to do the SMIL file, can you give me an actual file for my reference? Also, I'm attaching the MMSC DEBUG message below for your perusal: Thank you. Regards, Pancho --------------- MMSCDEBUG ----------------------- 12:00:04:125 [0] main: preferred sender = 09173974901,admin 12:00:06:203 [0] main: Now MMSC v5.51b (b20050428) service started. Using web port 80. 12:00:06:250 [2] ThreadListenSMTPIn: Now MMSC SMTP server started on port number 25 12:02:03:031 [8] ThreadProcessConnection: Processing connection from 192.168.2.150... 12:02:03:031 [8] ThreadProcessConnection: Packet Length is 135 bytes 12:02:03:031 [8] ThreadProcessConnection: 47 45 54 20 2F 32 30 30 36 30 32 30 33 2F 31 32 GET /20060203/12 12:02:03:031 [8] ThreadProcessConnection: 2F 34 33 45 32 44 35 42 42 61 2E 4D 4D 53 20 48 /43E2D5BBa.MMS H 12:02:03:031 [8] ThreadProcessConnection: 54 54 50 2F 31 2E 31 0D 0A 55 73 65 72 2D 41 67 TTP/1.1 User-Ag 12:02:03:031 [8] ThreadProcessConnection: 65 6E 74 3A 20 4E 6F 77 20 53 4D 53 2F 4D 4D 53 ent: Now SMS/MMS 12:02:03:031 [8] ThreadProcessConnection: 20 47 61 74 65 77 61 79 20 76 35 2E 35 31 62 20 Gateway v5.51b 12:02:03:031 [8] ThreadProcessConnection: 28 62 32 30 30 35 30 34 32 38 29 0D 0A 41 63 63 (b20050428) Acc 12:02:03:031 [8] ThreadProcessConnection: 65 70 74 3A 20 2A 2F 2A 0D 0A 43 6F 6E 6E 65 63 ept: */* Connec 12:02:03:031 [8] ThreadProcessConnection: 74 69 6F 6E 3A 20 43 6C 6F 73 65 0D 0A 48 6F 73 tion: Close Hos 12:02:03:031 [8] ThreadProcessConnection: 74 3A 20 0D 0A 0D 0A t: 12:02:03:140 [8] ThreadProcessConnection: Sending C:\PROGRA~1\NowSMS\MMSCDATA\20060203/12/43E2D5BBa.MMS 12:02:03:140 [8] ThreadProcessConnection: HTTP/1.0 200 OK 12:02:03:140 [8] ThreadProcessConnection: Content-Length: 20819 12:02:03:140 [8] ThreadProcessConnection: Content-Type: application/vnd.wap.mms-message 12:02:03:140 [8] ThreadProcessConnection: Connection: close 12:02:03:187 [8] ThreadProcessConnection: Processing Complete 12:05:39:671 [8] ThreadProcessConnection: Processing connection from 192.168.2.150... 12:05:39:671 [8] ThreadProcessConnection: Packet Length is 135 bytes 12:05:39:671 [8] ThreadProcessConnection: 47 45 54 20 2F 32 30 30 36 30 32 30 33 2F 31 32 GET /20060203/12 12:05:39:671 [8] ThreadProcessConnection: 2F 34 33 45 32 44 35 42 46 61 2E 4D 4D 53 20 48 /43E2D5BFa.MMS H 12:05:39:671 [8] ThreadProcessConnection: 54 54 50 2F 31 2E 31 0D 0A 55 73 65 72 2D 41 67 TTP/1.1 User-Ag 12:05:39:687 [8] ThreadProcessConnection: 65 6E 74 3A 20 4E 6F 77 20 53 4D 53 2F 4D 4D 53 ent: Now SMS/MMS 12:05:39:687 [8] ThreadProcessConnection: 20 47 61 74 65 77 61 79 20 76 35 2E 35 31 62 20 Gateway v5.51b 12:05:39:687 [8] ThreadProcessConnection: 28 62 32 30 30 35 30 34 32 38 29 0D 0A 41 63 63 (b20050428) Acc 12:05:39:687 [8] ThreadProcessConnection: 65 70 74 3A 20 2A 2F 2A 0D 0A 43 6F 6E 6E 65 63 ept: */* Connec 12:05:39:687 [8] ThreadProcessConnection: 74 69 6F 6E 3A 20 43 6C 6F 73 65 0D 0A 48 6F 73 tion: Close Hos 12:05:39:687 [8] ThreadProcessConnection: 74 3A 20 0D 0A 0D 0A t: 12:05:39:687 [8] ThreadProcessConnection: Sending C:\PROGRA~1\NowSMS\MMSCDATA\20060203/12/43E2D5BFa.MMS 12:05:39:687 [8] ThreadProcessConnection: HTTP/1.0 200 OK 12:05:39:687 [8] ThreadProcessConnection: Content-Length: 20819 12:05:39:687 [8] ThreadProcessConnection: Content-Type: application/vnd.wap.mms-message 12:05:39:687 [8] ThreadProcessConnection: Connection: close 12:05:39:687 [8] ThreadProcessConnection: Processing Complete | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5543 Registered: 10-2002 |
Pancho, See my November 30th post. Basically, the phone is not connecting to the MMSC to retrieve the message. This is most likely due to connectivity settings on the phone. Follow the suggestions in that post for troubleshooting. | |||
