| MMS Problem |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through April 05, 2007 ⬆ |
◄ ► |
| Author | Message | ||||
| Anthony Sellers New member Username: Adsellers Post Number: 1 Registered: 11-2006 |
I have NowSMS 2006. The Serial Number is 2843 and the Ref Code is A197EDCF. The SMS portion of the product is working fine, but I am having problems with the MMS. I can not seem to send or receive MMS messages with the GSM handsets. At first I assumed there was a problem with the handset configuration, but now I do not beleive that is the problem. From my understanding MMS functionality can be checked by going to a browser and browsing to the address of the MMS server i.e. http://192.168.1.111/. If the MMS is working properly the server should reply with a blank page and no errors. When I attempt this I receive an error (404 not found). The MMSCDebug log shows the following: 08:01:43:578 [1] ThreadProcessConnection: C:\PROGRA~1\NowSMS\MMSCDATA\.INI 08:01:43:578 [1] ThreadProcessConnection: File not found 08:01:43:578 [1] ThreadProcessConnection: C:\PROGRA~1\NowSMS\MMSCDATA\ 08:01:43:578 [1] ThreadProcessConnection: HTTP/1.1 404 Not Found Content-Length: 0 Connection: Keep-Alive I do beleive the configuration is correct, but there may be a problem there. I have attached a copy of the MMS debug log. Please take a look and tell me what you think. Regards, Tony Sellers
| ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6840 Registered: 10-2002 |
Hi Tony, What you have detailed here is normal behaviour. It is not indicative of any problem. I'd like to see a debug log that shows you attempting to actually send a message (both SMSDEBUG.LOG and MMSCDEBUG.LOG ... and potentially also MMSWAPDEBUG.LOG if you are sending the MMS message via an operator MMSC using a GPRS modem). Also, tell me more about your configuration ... it sounds like you are trying to send using a GSM/GPRS modem? Are you configured to send the message via a GSM/GPRS modem in the "MMSC Routing" section? (See http://www.nowsms.com/howmmsworks.htm for background information.) The most common problems when sending MMS messages via an operator MMSC using a GPRS modem are: 1.) "MMSC Routing" definition for the GPRS modem connection not configured as the default route. 2.) "MMSC Users" account defined for the test message recipient. (This causes NowSMS to assume that the user should receive direct MMS delivery instead of via the GPRS modem ... unless a special INI file parameter is present.) 3.) "Default Sender Address" in the "MMSC Routing" definition should be blank, and "Allow Sender Address Override" should be UNchecked. Those are my best guesses, since I don't have much information on your setup. Again, the behaviour above is normal. -bn | ||||
| Anthony Sellers New member Username: Adsellers Post Number: 2 Registered: 11-2006 |
Bryce, Yes we are using GPRS to send and receive MMS messages. We have the NowSms server connected to our GSM network via an SMPP interface. The address of the SMPP interface is 192.168.1.150 and we are using port 2275 for this connection. The NowSMS server has an IP address of 192.168.1.111. We are able to send SMS messages from the the NowSMS server, but are unable to send MMS messages from the NowSMS server nor are we able to send or receive MMS messages from the handsets. The one thing that does work is when you send an MMS message from the NowSMS server the GSM handset will get a message saying that there is an MMS waiting and it will prompt the user to download the message. When the download is attempted the handsets tries to retrieve, but then fails. The MMSC is configured as follows: Http port = 80 SMTP port = 25 IP Address = 192.168.1.111 Local Host Name = 192.168.1.111 Enable SMTP Smart Mailer is checked Enable MMS Delivery Receipts is checked Enable Dynamic Image and Audio Conversion is checked MMSC User configuration is as follows 1st user Phone # +8601002 Alias = HP632 Password = TLC 2nd user Phone # +8601004 Alias = HP634 Password = TLC Handset MMS Settings are as follows 1st Handset Connect Via TLC Connections (GPRS) connect to Server (NowSMS) Server name = NowSMS Gateway = 192.168.1.150 Server address = http://192.168.1.111/HP632=tlc 2nd Handset Connect Via TLC Connections (GPRS) connect to Server (NowSMS) Server name = NowSMS Gateway = 192.168.1.150 Server address = http://192.168.1.111/HP634=tlc I know every handset is configured differently but this is the configuration offered by the HP 6315 that we are currently using. I know the GPRS connection is good because I can server the web and connect to other servers outside the GSM Network. What logs can I provide to you that may help resolve the current problem? Regards, Tony Sellers | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6843 Registered: 10-2002 |
Hi Tony, Ok. So you are trying to setup NowSMS as an MMSC. And you are getting MMS notifications to the handsets, but the handsets are not able to retrieve the MMS. It sounds like what you have is a connectivity issue between the handsets and the MMSC. There may be some configuration issues to deal with on the handsets as well. From the NowSMS side, the only configuration setting that may be an issue is the "Local Host Name or IP Address". More on that in a minute ... Let me ask you this. What happens when you try to send an MMS message using one of the phones? Do you see any activity in the MMSCDEBUG.LOG? If you do not, then the MMS settings configured in the phone are not sufficient for allowing the phone to connect to the MMSC. Now I understand why you were trying to connect to the HTTP port of the MMSC with a browser. In the past, I have suggested attempting to do this from a browser on the phone, with the browser on the phone using the same connectivity settings that you are trying to use for MMS. A "404 Not Found" error will be returned ... but you can look at the MMSCDEBUG.LOG to see if the phone's browser was able to make a connection to the MMSC at all. That's the value of that test ... testing IP connectivity from the device to the MMSC. The device that you are using might not let you configure a "gateway" for the browser settings. I don't think Windows Mobile devices allow this. So testing from the browser may not be the same as connecting from the MMS client, because you have configured the MMS client to connect through a gateway. I assume you're connecting via a private APN that gives you access to your private network, right? (The IP addresses that you have supplied above are all private.) You mention that you have an SMPP server at "192.168.1.150". But do you have a WAP gateway there as well? By setting this IP address as the "gateway" value, you are telling the MMS client to connect via a WAP gateway at the specified address. You could setup our NowWAP Proxy as the WAP gateway ... or the MMS client might let you leave this setting blank, meaning a direct connection to the MMSC without going through any type of gateway or proxy. (For your configuration, I don't think there is any value setting up a WAP gateway for this purpose ... unless the MMS client will only support connections via a WAP gateway/proxy.) -bn | ||||
| Anthony Sellers New member Username: Adsellers Post Number: 3 Registered: 11-2006 |
Bryce, I changed handsets and used some that have simpler MMS configuration parameters. I am now able to send an MMS from a Handset, but the MMS nevers gets sent from the Server. I have also tried to send an MMS directly from the Server, but it does not seem to go out. So at this point I am able to send an MMS successfully from a handset, but once it is sent to the MMSC it seems to get stuck there. I have attached the latest MMSC Debug which shows the inbound messages. Please let me know if there is another log that may help rectify this problem. Regards, Tony
| ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6852 Registered: 10-2002 |
Tony, I don't understand what you are doing. You seem to be sending MMS messages to e-mail addresses, instead of phone numbers. These e-mail addresses are theoretically the e-mail addresses on the MMSC that get routed back out to the phones. (The MMS message gets converted to e-mail format, and then back to MMS ... instead of just staying in MMS format.) But I don't understand why you are adding this extra layer of complexity. But it would all be much easier to follow if you were sending messages to the phone numbers, not the e-mail addresses. Try it that way, and reply back with both MMSCDEBUG.LOG and SMSDEBUG.LOG. -bn | ||||
| Anthony Sellers New member Username: Adsellers Post Number: 4 Registered: 11-2006 |
Bryce, Will use the phone number and get back to you in the A.M. Tony | ||||
| Anthony Sellers New member Username: Adsellers Post Number: 5 Registered: 11-2006 |
Bryce, I used the telephone numbers this morning and the MMS seems to be working like it is suppose to now. I guess the real challenge is going to be configuring different handsets. Each of them seem to be different when it comes to MMS configuration. Thanks for your help and sorry to bother you with simple mistakes. Regards, Tony Sellers | ||||
MMSC Debug Log
