| MMS Gateway question |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through June 02, 2011 ⬆ |
◄ ► |
| Author | Message | |||||||
| Jens Jensen New member Username: Dunkeldane Post Number: 1 Registered: 01-2011 |
Hi, I have a situation where a MMS camera (with a SIM-card) sends MMS pictures to a users mobile phone when camera detects any movement. It has been working perfectly for many years, but now the operator has closed their old wap1.1 MMS gateway. So now you have to use another port (8080) instead of port 9201. But the camera can only use port 9201 and as I understand it then they don't use the MMS gateway for wap 2.0. This is a serius problem, since we have many hundred cameras out there. Is the a another way to fix this problem e.g. running our own MMS gateway or ? Regards, Dunkeldane | |||||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2855 Registered: 08-2008 |
Hi Dunkeldane, That is unfortunate. There is not an easy solution for this because you would require a WAP gateway and some sort of MMS gateway. You could use NowWAP and NowSMS for this purpose, but it may be a little complicated to work into your existing configuration. I'll try to explain. The WAP gateway is a special type of proxy. This part is relatively easy to setup, just install NowWAP and open up UDP port 9201 on a public IP address so that the device can connect to it. Unfortunately, the WAP gateway can't just relay the MMS message to the existing operator MMSC due to firewall and authentication issues. However, you could also change the MMS server URL to have the MMS message posted to NowSMS. There are two ways to do this. 1.) NowSMS is an MMSC. Because you are not fully integrated into an operator environment, you need to manually provision an "MMSC User" account for each device. Then, each device uses a unique URL to authenticate to the NowSMS MMSC (http://server:port/user=password). There may be a challenge here, however, depending on what the destination address is for your MMS message. If the destination address is an e-mail, that will be easy, as each device becomes phonenumber@mmsdomain. However, if your destination address is a phone number, you may lose the sender device address depending on how your outbound MMSC connectivity is configured. 2.) The less intuitive option is to use the MMSC VASP interface, which gives some more message routing control. In this case, you create an account for each device under in the "MMSC VASP" list. The MMS Server URL on each device is http://server:port/mm1/account=password. That's an overview, let me know if you need any more clarification. -- Des NowSMS Support | |||||||
| Jens Jensen New member Username: Dunkeldane Post Number: 2 Registered: 01-2011 |
Hi Des, Thanks for your answer. It seems that both solutions looks very complicated and I think that the operators don't really care about their customers. People change their mobile phones frequently so they don't see the problem, but our customers don't just invest in new cameras. Since I'm a novice in this field and haven'th planned to run a operator gateway, then I'm a little bit confused on what to do. Also could you explain this to me: The operator say they are closing the gateway and port 9201, but tell us that we can use port 8080 and the rest of the parameters are the same, APN, IP, MMSC address. How can this be that all the parameters are the same except the port and if we try to use port 8080 then it don't work. There surely must be something else that differs ? What if the operator that have closed their gateway could open for an external MMSC server, would that work ? Thanks for helping out. Regards, Dunkeldane | |||||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2861 Registered: 08-2008 |
Hi Dunkeldane, It is complicated. The port 9201 access uses a different protocol called WSP. This is a UDP (connection less IP) based protocol. We normally refer to this as WAP/WSP. The other proxy on port 8080 is using wireless profiled HTTP over TCP. We usually refer to this as WAP2/HTTP. So you can't simply change the port and have it work, unless the device also supports WAP2/HTTP and knows to use it instead of WAP/WSP. Where it gets more confusing is that an actual MMSC uses HTTP. An MMS client talks to a WAP gateway using either WAP/WSP or WAP2/HTTP. In either case, the WAP gateway always forwards the request to the MMSC using normal HTTP. (The WAP gateway handles things like authenticating the subscriber IP address and telling other network components, such as the MMSC what the phone number of the transmitting device is.) Opening up their gateway for an external MMSC is not a solution, because your devices cannot communicate with their gateway. Allowing an external gateway to forward requests to their MMSC is not an answer because an external gateway cannot perform the necessary user authentication/identification that their MMSC will require. The only solutions that I see are ... a.) new cameras or updated firmware b.) install a WAP gateway and MMSC (NowWAP and NowSMS) and reconfigure the cameras to send through these devices. c.) the operator installs a WAP gateway to handle legacy devices and continue supporting their customers. I do think the option for you to install your own WAP gateway and MMSC is quite complicated, especially considering that you would have to migrate existing customers. Workable, but complicated. If you have an open dialog with the operator, you may want to suggest that they look at our NowWAP product for supporting legacy devices, and to avoid requiring customers to reconfigure their MMS settings. It would seem to be not very well thought out that they are expecting customers to change MMS settings, not to mention its impact on customers like you who cannot change settings. We are seeing quite a few situations where operators are swapping out their WAP gateways because companies that offer older WAP gateway solutions are charging too much money for maintenance. So NowWAP may actually be a good solution for them (http://www.nowsms.com/productinfo/now-wap-gateway) ... definitely much easier for them to implement than for you to implement. But if you don't have another option, I'm happy to assist you in getting NowWAP and NowSMS setup on your end. The important tips for that are in my previous reply. -- Des NowSMS Support | |||||||
| Jens Jensen New member Username: Dunkeldane Post Number: 3 Registered: 01-2011 |
Hi Des, Many thanks for your comments. I can understand the this is very difficult and it's not possible to upgrade the cameras and asking the operator to install the wap gateway is not an option either. They don't even want to discuss it and because they are one of the largest operators in Scandinavia then they don't care about our customers. This is really not a good situation and I don't know what to do when customers find out that they can't use their camera. I'm trying to get the camera factory to upgrade the cameras but they say it's not possible. What I don't understand is that the cameras are using the Benq M22 gsm module and I have tested a modem with this GSM module with your NowSMS light and it's no problem sending MMS'es from the Pc with the same server info (APN, IP, port 8080). So the module should be able to use the WAP2/HTTP. If we should install the Wap Gateway and MMSC, what hardware do we need. Do you have a drawing on this setup ? But if we run it then we have to change the MMSC setup in the cameras which is not a problem. But do the customers mobile phones also have to have their MMSC setup changed or will they still point at the operators MMSC, since they are using different operators then the cameras ? If you could give me a simple outline of the setup, then maybe we can decide if this is the way to go ? Could you estimate the price for the NowSMS software we need ? Many thanks and regards, Dunkeldane | |||||||
| Jens Jensen New member Username: Dunkeldane Post Number: 4 Registered: 01-2011 |
Hi Des, I have tried to setup the NowSMS to send and receive MMS with a external modem connected to the Pc, but with no luck. SMS works fine and the SIM-card works fine in a mobile phone. The SIM-card operator are only using WAP2/HTTP and I'm using the same parameters as in the mobile phone. Do you have any good idears ? My goal is to use the NowSMS as a private MMSC, because I have a lot of boxes that sends SMS and MMS over GPRS but can only use WAP/WSP. I then want the boxes to send their MMS'es to the NowSMS and then use the NowSMS to send the MMS to the users mobile phones. They are only using WAP2/HTTP and have different operators. But first I wanted to be able to send and receive MMS first. Hope you can help out. Regards, Dunkeldane | |||||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3113 Registered: 08-2008 |
Hi Dunkeldane, Sorry for the delay in response. Have you configured the MMSC Routing definition to send outbound messages over the modem via the operator MMSC? The Direct Delivery MMSC configuration is blocked by most operators. You will most likely need to send via the operator MMSC. More info here: http://www.nowsms.com/doc/mmsc-messaging-server/connecting-to-an-operator-mmsc/s ending-mms-messages/mm1-gprs-modem And a bit more of an overview here: http://www.nowsms.com/faq/how-mms-works -- Des NowSMS Support | |||||||
| Jens Jensen New member Username: Dunkeldane Post Number: 5 Registered: 01-2011 |
Hi Des, Thank's for your response. Yes I have configured a route using the modem, but it won't send any MMS'es. In the outbound route I'm using the MM1, and the MMS version is 1.0 to 1.3, but the operator is not supporting WAP1. So do I need to use another setup ? As I wrote then the end solution is to act as a relay between the boxes using WAP1 and a operator only using WAP2. Is that possible ? Regards, Dunkeldane | |||||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3119 Registered: 08-2008 |
OK...let's try to get this resolved... Can you show me the settings on the "MMSC Routing" definition? (For WAP2/HTTP settings, use http://ip:port format in the Gateway Address field.) Also verify this route is set as the "Default Route". Enable all the debug logs on the serial # page...try sending again. Then send me the SMSDEBUG.LOG, MMSCDEBUG.LOG and MMSWAPDEBUG.LOG so I can understand your system. Either post them as an attachment here, or email to nowsms@nowsms.com with Attention: Des on the subject line. -- Des NowSMS Support | |||||||
| Jens Jensen New member Username: Dunkeldane Post Number: 6 Registered: 01-2011 |
Hi Des, I'm using the http:// for wap2 and also the settings as default route. See attached files. I have swapped phone numbers with XXXXXXXX in the logs. Regards, Dunkeldane
| |||||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3124 Registered: 08-2008 |
Hi Dunkeldane, I've never seen this error before. The MMSC is returning an error indicating that the list of recipients (in your case a single recipient) is corrupt. I've reviewed this extensively and compared NowSMS MMS packet formats to those of a variety of different clients, and I don't see how there can be any type of corruption in the recipient format. I'm guessing that the MMSC is detecting some other type of problem, and returning a misleading error description. The problem is determining what else the problem could be. I've discussed this with my colleagues, and here are the possibilities that we have determined. 1.) MMS access is not provisioned for the SIM card in your modem. Try moving the SIM card to a phone and verify that you can actually send MMS with the SIM in a phone. 2.) The APN setting is incorrect. Many operators have separate APNs for MMS and general internet access. I see some references that indicate that the internet APN can be used for sending/receiving MMS on Telenor DK. However, I also see others that reference different APN names. Try using an APN of Telenor to see if that makes a difference. 3.) I notice that you have the MMS version configured for 1.2. That should be fine, but try 1.0 for maximum compatibility. 4.) Maybe the MMSC doesn't like NowSMS because it is not identifying the MMS client software. Edit MMSC.INI, and add the following settings under the [MMSC] header to make the MMSC think you are using an iPhone: HeaderProfile=http://www.apple.com/mms/uaprof.rdf HeaderUserAgent=iPhoneOS/4.2.1 (8C148) Hopefully one of these ideas points to a resolution. -- Des NowSMS Support | |||||||
| Jens Jensen New member Username: Dunkeldane Post Number: 7 Registered: 01-2011 |
Hi Des, After sending the message to you I have tried to see what could be wrong, and I think I found the problem. From the operator I got: WAP GPRS APN: internet MMS APN: telenor I have used the "internet" in the route setup, because it said "GPRS APN", but if I change it to "telenor" then it sends MMS with no problem. I have seen from other operator's that they also writ "GPRS APN" and "MMS APN", so it's a bit confusing. But using the "MMS APM" in the route setup did the trick. Now I just have to find out how to rout the WAP1 boxes MMS to the users mobile phones using our NowSMS. Do you have some king of info on how to setup this ? Thanks for all your until now. Regards. Dunkeldane | |||||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3126 Registered: 08-2008 |
Hi Dunkeldane, We should probably adjust our terminology to avoid confusion, but that said, I found numerous Internet sites that claim the Internet APN is to be used for MMS on that operator. Here's what I'd do for the setup. Create an MMSC User account for each device (well, one to start with). Assign an alias and password for each account, as they will be used to construct a unique URL to be configured for each device. (In this configuration, there is no way to automatically identify the device phone number.) Install NowWAP, and make sure any firewall is allowing UDP traffic on ports 9200 and 9201 (probably only 9201 will actually be used). There is nothing to configure in NowWAP. On the device, point the WAP Gateway IP to the NowWAP IP. The MMS Server URL becomes http://NowSMS.server.address:port/alias=password Note that port is the HTTP port number configured on the MMSC setup page, which is different from the port that you use to access the web interface for sending messages. The NowSMS server doesn't necessarily need to have a public IP. It may be preferable for you to have it on a private IP accessible only via the WAP gateway. -- Des NowSMS Support | |||||||
| Jens Jensen New member Username: Dunkeldane Post Number: 8 Registered: 01-2011 |
Hi Des, Thanks I will try this. I assume that the device operator has to allow to use an external MMSC ? Do I use of that operator's parameters, like their wap apn ? The port used in the MMS Server URL is that e.g. 8800 if I don't change anything in the NowSMS, or is it 9201 ? I have installed the NowWAP earlier and removed it again. But after installing it again, there is no days left. How can I exten that so I can test it again ? Do I keep using the default route I made or can I use the internally MMSC ? Regards, Dunkeldane | |||||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3128 Registered: 08-2008 |
Hi Dunkeldane, The devices should use an Internet APN, because the devices will be communicating with NowSMS as their MMSC, not the operator MMSC. The port number in the MMS server URL is not 8800. It is whatever port number is configured on the "MMSC" page of the NowSMS configuration. This port number must be different from the one used for the NowSMS web interface. The 9201 port (UDP) is used by the device to communicate with the WAP gateway. Keep the default route configured, for now at least. Further testing would be required to determine if you can use the direct delivery setting on networks in your country. Let's save that test for later, as chances are that this might work with an operator or two, but probably will not work with all in your country. (The issue is one of which mobile operator the message receivers are using, not the one your devices are using.) For the NowWAP extension, please send an email to nowsms@nowsms.com with Attention: Des in the subject line, and I'll sort the extension for you via email. -- Des NowSMS Support | |||||||
MMSCDEBUG
NowSMS Setup1
