| WAP3GX & NOWSMS?????? |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through December 09, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| Digs Unregistered guest |
Hi There, Wondering if you can help, several questions here! 1)WAP3GX Gateway - I have downloaded and installed this gateway and can connect to it on our internal network no problem using a simulator. For example, the gateway is installed on machine 192.168.1.6 and the simulator on another machine 192.168.1.4 and it can connect to the wap gateway, use it and so on no problem. Both machines are connected to a firewall and have access to the internet. The machine that is hosting the WAP3GX gateway CAN also be accessed through our firewall as all ports are open and redirecting port requests to that machine(192.168.1.6) with TCP & UDP forwarding enabled. The problem is connecting to the wap gateway through the firewall - does not work with the simulator and I cannot connect to it with a phone either and I cannot figure out whats wrong? 2)HOW to add the WAP gateway settings to a phone to be certain so I can test correctly? We have several phones with a handful of operators in our region all gprs enabled. Each phone has a DATA account setup with the operator and then the wap profile settings. Can I simply add in the WAP3GX wap profile settings and use any of the data accounts in order to connect and test connectivity? Once I solve question 1 of course. 3)NOWSMS - This is why I am tesing with WAP3GX. How to send a WAP push message AND WAP-OTA/OMA settings to a handset in one go via URL? We have NOWSMS have up and running now and it's looking good, this is also on the same machine as the WAP3GX gateway connected to one of the gsm modems. We are testing WAP push and sms and it's working. Problem is with local operators WAP restrictions(file size) so I want to be able to send users handset's alternative WAP gateway settings and WAP push message so they can download the content without issue? 4) TO OTA or OMA? I don't know where to start on this one? Any help much appreciated, thanks, Digs | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1050 Registered: 10-2002 |
Hi Digs, 1.) The WAP protocol listens on UDP ports 9200 and 9201 (plus 9202 and 9203 if WTLS is used). I guess the question would be whether the problem is with the requests making it through the firewall, or the requests making their way back. I'm not a real expert in this area, but I'd suggest enabling the debug log on the WAP3GX side by manually editing WAPGW.INI, and adding Debug=Yes under the [WAPGW] section header. Then restart the gateway service. Attempt your connection again. In the WAPDEBUG.LOG, you should see information about a received packet if the request makes it as far as the gateway. If it doesn't make it there, then the firewall isn't routing it. If it makes it there, but the reply isn't received by the device (you'd probably see a lot of retry information in the log), then there's a problem routing the replies back through the firewall. 2.) In order to connect to your own WAP gateway, you need to configure the phone to use a GPRS APN that allows open internet access. Many operators have multiple GPRS APNs ... one for WAP (which can only talk to the operator WAP gateway), one for internet (usually used for PCs and PDAs, but that can interface to external WAP gateways), and sometimes another for MMS. Some smaller operators don't bother with all of the different APNs. But basically, you'd need to determine which APN to use for your operator for "internet" access. Then you configure the IP address of the WAP gateway in the profile in the phone. 3.) Unfortunately you can't send a WAP push and settings in a single message. It would make sense if that was possible, but it's not. 4.) The original OTA settings format was based upon a specification jointly published by Nokia and Ericsson. Generally speaking, it will only work on Nokia and (Sony)Ericsson phones. The OMA OTA settings were more recently defined by the work of the Open Mobile Alliance (OMA). We'll start to see more phones supporting these settings, but right now very few phones support this format (Nokia 6220, Nokia 6600 are a couple of released phones that support it ... we'll see more phones in the next 6 months). | |||
| Digs Unregistered guest |
Hi Bryce, Thanks for the reply, much appreciated, I see your blitzing the board! Well done! A few more questions for you. Any knowledge of how the latest Motorola & Siemens phones work with the OTA specification if at all? Any idea on how one could help these users stuck with operators crappy WAP gateway service? Unable to send WAP OTA & WAP Push at the same time? So in order to deliver content to a user's phone on a network with size limitations for example, I would send them the WAP PUSH OTA settings first, wait for the user to save the settings and activate that profile and then send them the second WAP CONTENT PUSH so they can download the content? I am trying to find a way of making this seamless and automatic for the end user so they can just get the content without any hiccups? Any idea's as to how this is done? When sending WAP OTA settings to Nokia/SE phones is it saved and ready for use automaticaly? I got your many OTA settings examples, I will try this and report back. Thanks again, Digs. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1081 Registered: 10-2002 |
Hi Digs, So far I haven't heard of any Motorola or Siemens phones supporting either OTA approach yet. (Siemens does have a proprietary OTA specification, because I have seen some operator sites that implement it ... but we have not had any luck getting access to the specification.) Crappy WAP gateways are a problem in some parts of the world. If possible, let the operators know about the problems, as they might not be aware. Unfortunately, there aren't any real good answers to all of this, because even on the Nokia/SE phones, when you save the settings, they are usually not automatically activated. -bn | |||
| Digs Unregistered guest |
Hi Bryce, OK, got the WAP gateway working ok, thanks for the debug tip. Turns out the 2nd machine I was testing from with the simulator was passing it's ip address over(192.168....) and not that of the firewall, so the two were unable to talk correctly. I tested from another machine outside the firewall and it works. I then tested from a SE-T310 using one of my crappy WAP gateway's APN that allow connections and it works great - very fast! Sending WAP OTA settings is the problem. I used the online web form from nowsms to send WAP OTA settings, got no errors but the settings never made it to the phone. Am yet to test with an OTA file. Note, the NOWSMS gateway that I am testing with is working fine as far as I can tell. It can send sms and wap push to other devices no problem so I assumed it would send the WAP OTA settings without issue. I am testing NOWSMS4.2 Thanks, Digs | |||
| Digs Unregistered guest |
Hi Bryce, OK, I have tried numerous times to send WAP OTA, WAP BOOKMARK & WAP VCARD settings via the web interface to two different handsets with two different operators....nothing came through, not even a beep? However, from the same web interface I CAN send SMS, WAP PUSH & WAP MULTIMEDIA messages no problem to the same handsets etc. So then I tried with an OTA document and placed it in the OTA sub directory FILENAME.OTA and submitted it that way....still nothing came through, not even a beep? Below is my sample structure OTA document file that I got from you from a previous post, the one on my test nowsms server is filled out. I am going to try and find the debug flag in NOWSMS and see whats going on. This is suppose to work right? Can both operators have this blocked somehow? Many thanks, Digs <CHARACTERISTIC-LIST> <CHARACTERISTIC TYPE="ADDRESS"> <PARM NAME="BEARER" VALUE="GPRS"/> <PARM NAME="PROXY" VALUE="1.2.3.4"/> <PARM NAME="PORT" VALUE="9201"/> <PARM NAME="GPRS_ACCESSPOINTNAME" VALUE="apn.name"/> <PARM NAME="PPP_AUTHTYPE" VALUE="PAP"/> <PARM NAME="PPP_AUTHNAME" VALUE="user"/> <PARM NAME="PPP_AUTHSECRET" VALUE="password"/> <PARM NAME="ISP_NAME" VALUE="Settings Name"/> </CHARACTERISTIC> <CHARACTERISTIC TYPE="MMSURL" VALUE="http://mms.server.url/"/> <CHARACTERISTIC TYPE="NAME"> <PARM NAME="NAME" VALUE="Settings Name"/> </CHARACTERISTIC> <CHARACTERISTIC TYPE="URL" VALUE="http://home.page.url"/> <CHARACTERISTIC TYPE="BOOKMARK"> <PARM NAME="NAME" VALUE="Settings Name"/> <PARM NAME="URL" VALUE="http://home.page.url"/> </CHARACTERISTIC> </CHARACTERISTIC-LIST> | |||
| Digs Unregistered guest |
Hi There, I checked the logs in debug mode. The requests are getting through to the gateway no probs and are being executed from what I can tell. I can see the ThreadProcessModem in & out strings and every entry finishes with an OK entry? So I guess thats fine, must be the operators or the handsets. I am testing here with a SE T310 and a SE-T300. Yawn! | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1109 Registered: 10-2002 |
Hi Digs, There is a problem with the v4.20 release and OTA to SonyEricsson phones We changed the order of some header bytes used for SMS concatenation, and although perfectly legal format, it confused the SonyEricsson phones. Update to the v5.0 release, or it looks like the v4.20a update is still available at the following link: http://www.nowsms.com/download/nowsms420a.exe -bn | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1110 Registered: 10-2002 |
P.S. - I tried your settings example to a T68i, and they were recognised as such. The format should be fine. | |||
