| How to receive or view MMS messages ? |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through October 19, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| Rob Ristroph New member Username: Robristroph Post Number: 1 Registered: 05-2007 |
Hi, I have NowSMS gateway set up with a MultiTech Edge modem. I can send SMS messages. When I receive SMS messages I see a file appear in C:\Program Files\NowSMS\SMS-IN which has the incoming message in it, so that appears to be working OK. This doesn't seem to be working with MMS messages, however. Nothing ever appears in C:\Program Files\NowSMS\MMS-IN. If I send an mms message to myself (from the cellular modem to the cellular modem via the web interface) a reasonable looking .MMS file appears in C:\Program Files\NowSMS\MMSCDATA\20070517\14 , but if I send an MMS message to the modem from a cell phone, nothing appears there, although a file in C:\Program Files\NowSMS\MMSINQ\COM1-\ seems to have a link to the MMS content, not the content embedded. I attempted to configure NowSMS to forward all MMS messages via email, but that seems not to have worked. I have two questions: 1) how can I make sure that the MMS messages I receive arrive with the content embedded, not with a URL to a place to fetch the content ? 2) so I can debug the above, what is the simplest way I can see all the MMS messages arriving at the modem ? I would like to list them on a web page, put them in a local directory, or forward them via email, anything simple to set up. I searched the manual on these issues and also this forum, but didn't find anything quickly . . . I will be reading the manual in the mean time. Thanks in advance. | |||
| Parvez Alam New member Username: Parvez_alam Post Number: 1 Registered: 06-2007 |
i am facing the same issue. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7159 Registered: 10-2002 |
Hi, If everything is configured correctly, received MMS messages will be decoded and stored in the MMS-IN directory. There will be a ".HDR" file with text versions of the MMS headers, and this file will include special "X-NowMMS-Content-Location:" headers that point to the file names of the different file parts of the MMS message (for example, text parts, images, SMIL presentation markup). These file parts are stored in a subdirectory that matches the name of the ".HDR" file without the ".HDR" extension. In the next major release of NowSMS (due within the next couple of weeks), we've added a "View" button to the "2-way" page which displays a list of received SMS and MMS messages. But for now, these received MMS messages would appear as files in the "MMS-IN" directory. But ... you're not getting that far ... as it sounds like there are configuration issues. So, let's work through those. First, I'd encourage you to take a look at the write up for "How MMS Works" at http://www.nowsms.com/howmmsworks.htm. This will help explain some of the basics of MMS technology, which may help in an overall understanding. You mentioned the MMSCDATA and MMSINQ directories ... which is good detective work on your part. Let me explain when and why you would see MMS related files in these directories, as this will help in sorting through the configuration issues. The MMSCDATA directory contains sent MMS messages, when your system is configured for "direct delivery" as an MMSC. NowSMS stores the MMS message content in a dynamically created directory beneath the MMSCDATA directory, and it then sends an MMS notification over SMS to tell the client to retrieve the message from NowSMS as the MMSC. (If you refer back to the "How MMS Works" link, however, you'll see that many mobile operator MMS configurations do not allow MMS message delivery from external MMSCs like this.) Normally, when you are sending MMS messages via a modem, you wouldn't do "direct delivery" as an MMSC, you would configure NowSMS to route the messages to the operator MMSC over the modem. This type of configuration is described here: http://www.nowsms.com/documentation/ProductDocumentation/mms_notifications_and_content/Connecting_to_operator_MMSC.htm#UsingGPRS Basically, you need to define an "MMSC Routing" to send the MMS messages out via the modem, and make that the "Default Route". The NowSMS software has been updated since the link that I referenced above was written, and it's a little easier to configure now as we have operator settings available to select from a list for most of the major operators. So, if you see an MMS message file in the "MMSCDATA" directory when you send an MMS message, this means that you are using NowSMS as an MMSC for "Direct Delivery". In most real world configurations, this won't work ... see the "How MMS Works" link that I referenced above for more explanation why. When you send an MMS message that is going to be routed to an external MMSC connection, such as over a modem connection, you will find that after the MMS message is submitted to NowSMS, it is temporarily queued in the VASPQ directory while it is being processed. The MMSINQ Directory is used for processing MMS notifications that have been received via SMS. If you refer back to the "How MMS Works" explanation, you'll see that the MMS delivery process is triggered first by an MMS notification message that is delivered to the handset over SMS. The handset must then retrieve the URL referenced in the MMS notification in order to receive the content of the MMS message. When NowSMS receives an MMS notification over SMS, it decodes the notification (and the URL referenced by the notification), and creates a temporary file in the MMSINQ directory. NowSMS then periodically tries to retrieve the MMS message content for the message. The fact that the file is remaining in the MMSINQ directory suggests that NowSMS is having difficulty retrieving the message content. Such a problem would occur most likely if there was a configuration problem. You see, the URL for the MMS message is not retrievable over the internet. NowSMS has to fetch the message content over the modem. And it needs to use configuration settings for the modem which are operator specific. If you highlight the modem in the "SMSC" list and press "Properties", you need to press "MMS Settings" to configure the operator specific settings for the modem. It gets a little bit more confusing here if you have configured NowSMS to talk to the modem via a direct COM port reference (in the original posting I see you are using "COM1:") In order to send/receive MMS messages via a modem, NowSMS needs you to have a Windows modem driver installed for the modem, and when defining the modem to NowSMS, you should use the named Windows modem driver instead of the direct COM port reference. (Stop the NowSMS service, remove the "COMx:" modem definition from the SMSC list, and then re-add the modem using the named modem driver instead.) If your modem does not have a Windows modem driver, just go into the Windows Control Panel and manually add a modem driver to associate with the proper COM port. Use the "Standard 33600 bps Modem" driver. (Don't be concerned about the speed, this driver does not limit you to 33600 bps.) Under the "MMS Settings" for the modem in NowSMS, select the settings for your mobile operator. For "Network Connection:", select the "Modem:" entry that matches the modem driver (NowSMS should pre-select this as the default). Press the "Test Connection" button to verify that NowSMS can make the connection. Completing that part of the configuration puzzle should be the last piece of what you need to get things working. When an MMS notification is received, a file will be temporarily created in the MMSINQ directory while the notification is processed. However, the end result should be the contents of the MMS message in the MMS-IN directory. (Unless you configure NowSMS to do something different with the received message.) -bn | |||
| Rob Ristroph New member Username: Robristroph Post Number: 3 Registered: 05-2007 |
Thanks for the detailed and informative reply. I am looking over more of the documentation. I was not able to add the modem as you described, in the step where you associate the "Standard 33600 bps Modem drive" with COM1, I am not able to select which port to use with that driver. This might be a problem with my windows that is not related to Now.SMS. I will look into this. I am very interested in the new version of now.sms you describe as having the web interface for receiving MMS messages. I presume the issue with configuration would still have to be fixed in the same way, though. I will post again to this thread tomorrow when I have figured more out. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7165 Registered: 10-2002 |
Hi Rob, If you're using Windows XP or Windows 2003, you should be able to go into the Windows Control Panel, select "Phone and Modem Options", select "Modems" ... select "Add" ... select "Don't detect my modem; I will select from a list" ... select "Next" ... select "Standard 33600 bps Modem" and "Next" ... then on the next screen it will prompt for the port to install it on. Ah ... I just noticed something here, it looks like Windows tries to open the ports before displaying the ones that you can select. If NowSMS is running and has the port open, then it might not appear on the list. -bn | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7179 Registered: 10-2002 |
P.S. - There is a pre-release version of the new release available for download at http://www.nowsms.com/download/nowsms2007.zip. | |||
| Rob Ristroph New member Username: Robristroph Post Number: 4 Registered: 05-2007 |
is someone here that can help me send an MMS message from now.sms? I can send/receive sms text messages, but I must have someting config'd wrong or something not done right - I cannot send nor receive MMS. It looks like it is queing up the MMS I'm trying to send - but the modem lights show a simple "polling" action. The MMS send is NOT causing the modem to send the MMS messages I tried to send. I'm using t-mobile chip, if that makes any difference. Please help me! Thanks! | |||
| Rob Ristroph New member Username: Robristroph Post Number: 5 Registered: 05-2007 |
Here's the error I keep getting over and over: [ErrorDetail] RetryCount=15 LastRetryTime=20070627223215 LastErrorInfo=ERROR - Modem Response (2): +CMS ERROR: 535 -- Standard 33600 bps Mode What would CMS ERROR 535 mean? Thanks! | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7300 Registered: 10-2002 |
CMS ERROR 535 is a manufacturer specific error code. For the Multitech EDGE and other modems based upon Siemens chipsets, it means "Protocol Stack Busy". The question is ... what does that really mean? Based upon the way you are seeing this error code displayed, it sounds like NowSMS is configured for direct delivery as an MMSC, and not for sending the MMS message to the operator MMSC over the modem. (Yes, NowSMS is still using the modem, but it is using the modem to send SMS messages for what is known as the "MMS Notification".) Normally, when you are sending MMS messages via a modem, you wouldn't do "direct delivery" as an MMSC, you would configure NowSMS to route the messages to the operator MMSC over the modem. This type of configuration is described here: http://www.nowsms.com/documentation/ProductDocumentation/mms_notifications_and_c ontent/Connecting_to_operator_MMSC.htm#UsingGPRS Basically, you need to define an "MMSC Routing" to send the MMS messages out via the modem, and make that the "Default Route". The NowSMS software has been updated since the link that I referenced above was written, and it's a little easier to configure now as we have operator settings available to select from a list for most of the major operators. I still don't see why text messages would be sent and received ok, and the MMS notifications would fail with a CMS ERROR 535. But if you change the configuration like I describe, then MMS messages will be sent in a different way. To avoid confusion, I'll walk you through the configuration steps ... Go to the "MMSC Routing" page. Select "Add". "Account Name" is an identifier that is used internally by NowSMS only, you can put whatever you want here, but for simplicity, put in "T-Mobile". "Account Description" can be left blank. "Default Sender Address" should be left blank ... and "Allow Sender Address Override" should NOT be checked. "Route messages to this ..." can be left blank. "Route messages to VASP via" should be set to "MM1". Click on "Lookup Operator Settings". Select "USA - T-Mobile" ... this should load the settings for your operator. Make sure that "Use specific network connection (GPRS modem)" is checked. "Network Connection" should be set to "Modem: modem driver name" (e.g., "Modem: Standard 33600 bps Modem"). "Modem Used" should be set to the same named modem. And this should be the same modem that is in your "SMSC" list in NowSMS. Press "Test Connection" to test out the settings. Press "OK" to return back to the previous page, and change the "Default Route" to match the name of the routing that you just defined ("T-Mobile"). Press "Apply". Restart the service ... try sending another MMS message. | |||
| Alejandro Calero New member Username: Streamingmx Post Number: 1 Registered: 07-2007 |
I want to use NowSMS to receive MMS messages from the Operator’s MMSC. I believe the MMSC tab and MMSC VASP tab are all configured correctly, but I fail to see any inbound messages in the MMSINQ folder. The Operator is TELCEL, largest Operator in Mexico. They run Comverse’s MMSC. Because for the time being I do not need to send any messages back to the users’ mobile phones, I did not create any SMSC connections, nor MMSC Routing. Both the SMS Gateway Service and MMSC Service are active. Telcel is pointing its MMSC to my NowSMS address: http:// 200.67.98.161:88/mm7 Telcel’s MMSC is behind a firewall that I fear may be blocking the HTTP messages out to the internet and into my NowSMS. I don’t see events in the log. Assuming we solve this connectivity issue, I still need to clarify…. • Are there any compatibility issues between Comverse and NowSMS? • Is the MMS connection dependant on an existing SMS connection? i.e, Is it possible that I don’t get inbound MMS messages for lack of full SMS configuration? • I gather the folder names have changed a bit from the time some of these posts were written to the time NowSMS v7 was released. I’d like to re-confirm that the MMS-IN folder is in fact MMSINQ. | |||
| Alejandro Calero New member Username: Streamingmx Post Number: 3 Registered: 07-2007 |
Never mind my questions #2 and #3. I have confirmed that the MMS service runs in spite of the server complaining about not having the SMSC portion active. Also I learned that the MMS-IN folder is not present until after the first message arrives. I still would like to hear about any known compatibility issues between the Comverse MSMC and NowSMS. Any opinions about the Comverse performance would be much appreciated. | |||
| SMSCOMM New member Username: Smstext Post Number: 4 Registered: 07-2007 |
I updated to NOWSMS 2007. but is has become very very slow in sending messages. Why is this?? | |||
| Hamdy Mahmoud New member Username: King5858 Post Number: 1 Registered: 08-2007 |
Hi, I'm new to this service and it happen that I have received a message on my mobile from someone I trust telling me that I have a MMS and stated a passcode to access this meesage. Actually I have tried to do so, but I couldn't. I need your support. Thanks | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7416 Registered: 10-2002 |
Regarding the Comverse MMSC, I believe that their MM7 implementation only supports a very old version of MM7. If memory serves me correctly, you need to set the "MM7 Schema" to "REL-5-MM7-1-0". The XML schema for MM7 varies somewhat by version, and while most MMSCs try to be flexible and ignore newer elements that they do not understand, some are very strict about only supporting specific versions. Of course, this is just based upon past experience of users connecting to Comverse MMSCs. It is very possible that newer versions of the Comverse MMSC support newer versions of the MM7 XML schema. If you experience problems, enable the MMSCDEBUG.LOG, and we can analyse this for clues as to what version the MMSC expects.
This can be caused by an activation code problem. If you have an actual purchased license, you should contact us directly (http://www.nowsms.com/contact.htm) to verify the activation code details.
This is the support forum for the Now SMS/MMS Gateway software product. That message is coming from your mobile operator (or the mobile operator to which your friend is subscribed). We don't have any involvment with that service. If you need help, you need to contact your mobile operator. Sorry. | |||
| chris harpe New member Username: Harpefearless Post Number: 1 Registered: 08-2007 |
i used to receive mms mesgs now it says "message reciept falied" what do i do???????? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7418 Registered: 10-2002 |
Where does it say this? This is the technical support forum for the Now SMS/MMS Gateway software product. If you are using NowSMS as a direct delivery MMSC, please see the information at http://www.nowsms.com/howmmsworks.htm. If you are not using NowSMS ... and are just an end user with a mobile phone, then I would suggest contacting technical support at your mobile operator. | |||
| alex chan New member Username: Alex_chan9 Post Number: 1 Registered: 09-2007 |
I have NowSMS gateway set up with a Nokia N70 or 6800 mobile phone. I can sent MMS without any problem, but I am not sure how to set the NowSMS to received MMS. Is it possible to receive MMS by the NowSMS not by the mobile? | |||
| alex chan New member Username: Alex_chan9 Post Number: 2 Registered: 09-2007 |
Now I use the Fargo GSM/GPRS modem for my NowSMS gateway setup. I can sent and received MMS from NowSMS to and from Mobile. However, it is not working when I try to sent a MMS from NowSMS to NowSMS itself with same GSM/GRPS modem. Is there some setting I should set for sent MMS to itself in NowSMS. I am thinking it may be the problem when setting the local host name in the MMSC setting. I try to put the "localhost" or "127.0.0.1" or the real ip address (from run ipconfig in commands prompt) but still not work. Would someone have some suggestion for me about this problem. Thanks a lot Alex | |||
| alex chan New member Username: Alex_chan9 Post Number: 3 Registered: 09-2007 |
I fixed the problem above by removed all the MMSC Users that I created before. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7487 Registered: 10-2002 |
Lots of different unrelated issues on this thread. It should probably be closed to prevent more issues from being posted, as it is getting a bit confusing. But to address the last few issues: I am not aware of any mobile phones that can be used as a modem for receiving MMS messages. The problems is that the MMS notification message is always routed to the MMS client in the mobile phone, and it is not routed to NowSMS over the GSM modem interface. A dedicated GSM/GPRS modem device (instead of a mobile phone acting as a modem) is the only solution. Regarding the 2 messages above this ... that is correct ... for any phone numbers listed in the "MMSC Users" list, NowSMS will always attempt to send MMS messages to those phone numbers using direct delivery as an MMSC. If you need to have these phone numbers in the "MMSC Users" list for another reason (such as being able to accept e-mail to MMS or SMS for these phone numbers) ... but you do not want the MMSC to perform direct MMS delivery for these phone numbers, it is possible to add the following setting under the [MMSC] header of MMSC.INI: DisableMMSDirectDelivery=Yes -bn | |||
