| Store, ringtones, OTA settings, MMS, etc. |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through September 15, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| petter |
Hi How can I store different typs of OTA settings? Petter | |||
| Bryce Norwood - NowSMS Support |
Petter, I'm not sure that I understand the question ... so please feel free to ask me for clarification on this response, as I might have misunderstood. There are basically two different ways of handling OTA in NowSMS. The easiest way to handle OTA is to generate a URL request to the NowSMS server which has the different "OTA_xxx" parameters set to the values that you desire. When you use the web menu interface to send an OTA ... basically you can look at the source for the form to see how each of the fields in the form has a particular variable name associated with it. In this case, the form instructs the web browser how to build a URL request that is sent to the NowSMS gateway to send out the OTA configuration message. So let's take an example. Let's say that we wanted to send out an OTA message with the standard WAP GPRS settings for Vodafone in the UK. If we were to fill out the web menu interface form, we'd fill in the following values: Connection type: GPRS GPRS Access Point Name: wap.vodafone.co.uk GPRS Login Parameters: Automatic GPRS User Name: user@vodafone.net GPRS Password: user GPRS Login Type: Standard (PAP) WAP Gateway IP Address: 212.183.137.12 WAP Gateway Login Parameters: Automatic WAP Gateway user name: (blank) WAP Gateway password: (blank) WAP Gateway Connection Type: Connection-oriented Settings Name: VodaUK Home Page URL: http://i.dont.remember.the.default/home.wml If you look at the source for the form, you'd see that the form is causing the following URL request to be submitted: /Send%20WAP%20GPRS%20Settings.htm? OTA_BEARER=GPRS& PhoneNumber=phone-number& OTA_GPRS_ACCESSPOINTNAME=wap.vodafone.co.uk& OTA_PPP_LOGINTYPE=AUTOMATIC& OTA_PPP_AUTHNAME=user@vodafone.net& OTA_PPP_AUTHSECRET=user& OTA_PPP_AUTHTYPE=PAP& OTA_PROXY=212.183.137.12& OTA_PROXY_LOGINTYPE=AUTOMATIC& OTA_PROXY_AUTHNAME=& OTA_PROXY_AUTHSECRET=& OTA_PORT=9201& OTA_NAME=VodaUK& OTA_URL=http%3A%2F%2Fi.dont.remember.the.default%2Fhome.wml Note: The "&" in the above is a field separator. When you submit multiple variables in a URL request, the "&" character is used to separate variables. Based upon the settings that we selected on the form, all of the variables are pretty obvious except for OTA_PORT=9201. Basically this maps to connection type = connection-oriented, and you'll want to always include this setting unless you are using WTLS encryption, in which case you would specify 9203 instead. If you wanted to save these settings, the easiest thing is to create a form on a separate web server which sets these variables as hidden fields in the form, with maybe just the ability to set a phone number. The other way of doing settings is to create an OTA document. You place the OTA document in a subdirectory of the gateway named "OTA". And you can use a simple HTTP request to cause that OTA document to be sent to a particular user. Unless you have very specialised needs, however, you're best off using the URL variable approach. -bn | |||
