| MMSC Setup problems |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through September 15, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| Tillmann |
Hi, I've set-up NowSMS, using a Nokia 8310 as a temp GSM modem to send out messages. The connection works fine and I can send out SMS messages to phones using the web interface that get delivered properly. Trying to send MMS messages though fails. I tried nowSMS's dummy MMS that was mentioned in another thread, and also to send just an MMS notification message that points to an .mms file that is sitting on a webserver. For comparison, I tried WAP push as well. Here is what happens in all instances: - the target phone receives a normal SMS, with some garbled characters (from binary data) and the MMS-retrieval URL in plain text. The target phone (P800) had received MMS messages and WAP push earlier via the telco networks without any problems. What am I doing wrong? Any help is appreciated. Thanks, Tillmann -------------------------- SMSOUT.log ... 2003-05-20 12:34:21,SAR-93854344-17-2-1.req,192.168.168.5,93854344,OK 2003-05-20 12:34:29,SAR-93854344-17-2-2.req,192.168.168.5,93854344,OK 2003-05-20 12:35:52,3EC9AF18.req,192.168.168.5,93854344,OK 2003-05-20 12:46:07,3EC9AF1C.req,192.168.168.5,93854344,OK 2003-05-20 12:48:55,3EC9AF1D.req,192.168.168.5,93854344,OK 2003-05-20 12:49:16,3EC9AF21.req,192.168.168.5,93854344,OK 2003-05-20 12:52:42,3EC9AF22.req,192.168.168.5,93854344,OK SMSWEB.log ... 2003-05-20 12:34:02,192.168.168.5,nxspace,SAR-93854344-17-2-2.req,SendMMS 2003-05-20 12:35:41,192.168.168.5,nxspace,3EC9AF18.req,WAPPush 2003-05-20 12:45:52,192.168.168.5,nxspace,3EC9AF1C.req,SendMMS 2003-05-20 12:48:38,192.168.168.5,nxspace,3EC9AF1D.req,Text 2003-05-20 12:48:56,192.168.168.5,nxspace,3EC9AF21.req,SendMMS 2003-05-20 12:52:28,192.168.168.5,nxspace,3EC9AF22.req,WAPPush MMSCDEBUG.log ... 12:45:52:376 [5] ThreadProcessConnection: Sending C:\PROGRA~2\NowSMS\MMSCDATA\20030520/12/3EC9AF1Aa.MMS 12:48:56:290 [5] ThreadProcessConnection: Processing connection from 192.168.168.5... 12:48:56:290 [5] ThreadProcessConnection: Input Buffer Length is 140 bytes 12:48:56:290 [5] ThreadProcessConnection: 47 45 54 20 2F 32 30 30 33 30 35 32 30 2F 31 32 GET /20030520/12 12:48:56:290 [5] ThreadProcessConnection: 2F 33 45 43 39 41 46 31 46 61 2E 4D 4D 53 20 48 /3EC9AF1Fa.MMS H 12:48:56:290 [5] ThreadProcessConnection: 54 54 50 2F 31 2E 30 0D 0A 55 73 65 72 2D 41 67 TTP/1.0 User-Ag 12:48:56:290 [5] ThreadProcessConnection: 65 6E 74 3A 20 4E 6F 77 20 53 4D 53 2F 4D 4D 53 ent: Now SMS/MMS 12:48:56:301 [5] ThreadProcessConnection: 20 47 61 74 65 77 61 79 20 76 34 2E 31 30 0D 0A Gateway v4.10 12:48:56:301 [5] ThreadProcessConnection: 41 63 63 65 70 74 3A 20 2A 2F 2A 0D 0A 43 6F 6E Accept: */* Con 12:48:56:301 [5] ThreadProcessConnection: 6E 65 63 74 69 6F 6E 3A 20 43 6C 6F 73 65 0D 0A nection: Close 12:48:56:301 [5] ThreadProcessConnection: 48 6F 73 74 3A 20 31 39 32 2E 31 36 38 2E 31 36 Host: 192.168.16 12:48:56:301 [5] ThreadProcessConnection: 38 2E 35 3A 38 30 30 38 0D 0A 0D 0A 8.5:8008 12:48:56:301 [5] ThreadProcessConnection: Sending C:\PROGRA~2\NowSMS\MMSCDATA\20030520/12/3EC9AF1Fa.MMS | |||
| Bryce Norwood - NowSMS Support (Bryce) |
Tillman, It looks like I responded first on e-mail again ... for the interest of others, here's how I replied. === Hi Tillman, I need to get back out to the discussion forum. We've got two people on vacation this week, and it is creating quite a backlog in support queries. I don't have any experience with the Nokia 8310 as a GSM modem, but it sounds to me like the device is not sending out the binary messages properly. I had a support incident with someone who was using an Ericsson R520 as a GSM modem, and they had a similar problem. What was odd was that I also have an R520 and I did not have any problems. After several weeks of testing and trying different operator combinations, I got them to try a different phone, and everything worked properly. What we found was that by sending a message from the phone to its own number, and having NowSMS receive the message ... was that the UDHI (user data header indicator) flag was being lost. This is an important flag when sending almost every type of binary SMS message ... as without that flag set, the recipient device does not parse the user data header, which tells the device how to interpret the binary message content. You might want to try a test of NowSMS sending a WAP push message to itself. And send me the SMSDEBUG.LOG, and I can determine if it is the same problem. In that particular case that I am thinking of, there was some odd difference in the behavior between 2 different versions of firmware for the R520, and the version that the customer had was not setting the UDHI flag when sending out binary messages for some reason. Another thing to try ... manually edit SMSGW.INI, and under the [SMSGW] section header, add BinaryDCS=4, and then restart the gateway ... and see if that makes a difference. We had a provider in the USA where this setting made a difference going cross-operator. Speaking of cross operator, that brings up another thought. It's been almost 2 years since I was last in Singapore, but last time I was there, I investigated a problem that someone was having where they could not send WAP push messages between operators using a GSM modem. I forget whether we were using a StarHub or M1 SIM sending to the other ... but binary messages were being corrupted when they went cross operator. I haven't seen that issue anywhere else (apart from the USA where things are weird because of the different mobile phone protocols that are being used), but that is also something to look at. In that case, you might need to try an SMS provider if cross operator binary SMS is still a problem. -bn | |||
| Tillmann |
Bryce, great support! Here is what I found out: My original configuration was a 8310 with a SingTel SIM, sending to a P800 on StarHub. This scenario caused the binary headers not to be sent properly. I finally got hold of another SingTel SIM in a 3650 and suddenly it works. I am able to send WAP Push Messages and also MMS Notification Messages from the 8310 to the 3650. Full MMS I can't test yet due to the lack of a webserver to store the messages on. I tried using a standard webserver to store the .mms file but get a "Error: Invalid Content Type for URL: text/plain" message from the web front-end. Do I need to configure the MIME type on the webserver for .mms manually? Cheers, Tillmann | |||
| Bryce Norwood - NowSMS Support (Bryce) |
Hi Tillmann, Yes, you need to get the MIME type on the web server configured for ".mms" manually as "application/vnd.wap.mms-message" (unless the MMSC itself is the server, in which case the content type is pre-defined). The issue is that when you send out the MMS notification, the gateway is just building the MMS headers, and telling the phone to fetch the specified URL. If the content type isn't correct, the phone wouldn't accept the URL as an MMS message, so we try to catch this up front to save from troubleshooting problems later. -bn | |||
| Jimmy |
Hi Bryce, I have the exact same problem as Tillmann stated, but i'm using a SonyEricsson t68i. As i have only one sim card. I had to put the sim card in my gsm modem connected to my pc to compose a mms message using the nowsms web interface, after i have finished composing and send, i had to remove the sim card from the gsm modem and put it into my t68i to check for the mms. I didnt receive the MMS sent, but infact got an SMS showing the weird characters with the url of the MMS message. what could be the cause of this problem? I posted a thread in the technical discussion, but could not find my post. My post can only be found using the search. Sorry to ask the same question here. Jimmy | |||
| Bryce Norwood - NowSMS Support (Bryce) |
Hi Jimmy, I'd be lost without the "Search" function out here. Here's a link to the thread, and a response. http://support.nowsms.com/discus/messages/12/330.html In short, after giving it a lot of thought, I think your problem is related to the SIM swapping. The other thread will explain that in some more detail. Cheers! -bn | |||
