OTA Settings on Sony Ericsson K500, K700, S700 etc.

OTA Settings on Sony Ericsson K500, K700, S700 etc. SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through October 19, 2005 » OTA Settings on Sony Ericsson K500, K700, S700 etc. « Previous || Next »
Author Message
Anonymous
 
Posted on Wednesday, September 21, 2005 - 08:47 pm:   

Sony Ericsson Handsets like K500, K700, S700 etc. has an option under Internet Profiles "Internet Mode" which is either WAP or HTTP.

When we sent an OTA Setting either WAPOTA or OMA I cannot set the Internet Mode to HTTP, its by default set itself to WAP Mode. My query is how can we set it to HTTP Mode.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 5001
Registered: 10-2002
Posted on Thursday, September 22, 2005 - 06:04 pm:   

Hi,

This is a bit of a frustrating issue, because it is an incompatibility between Nokia and SonyEricsson in OTA handling.

Here's typical XML for NowSMS to generate from its web form for creating an HTTP profile:

<wap-provisioningdoc>
<characteristic type="BOOTSTRAP">
<parm name="NAME" value="GPRS Settings" />
</characteristic>
<characteristic type="NAPDEF">
<parm name="NAME" value="GPRS Settings" />
<parm name="NAPID" value="GPRS_Settings_NAPID" />
<parm name="BEARER" value="GSM-GPRS" />
<parm name="NAP-ADDRESS" value="wap.operator.com" />
<parm name="NAP-ADDRTYPE" value="APN" />
<characteristic type="NAPAUTHINFO">
<parm name="AUTHTYPE" value="PAP" />
</characteristic>
</characteristic>
<characteristic type="PXLOGICAL">
<parm name="NAME" value="GPRS Settings" />
<parm name="PROXY-ID" value="GPRS Settings_Proxy" />
<parm name="STARTPAGE" value="http://portal.operator.com/" />
<characteristic type="PXPHYSICAL">
<parm name="PHYSICAL-PROXY-ID" value="GPRS Settings_PhProxy" />
<parm name="PXADDR" value="1.2.3.4" />
<parm name="PXADDRTYPE" value="IPV4" />
<parm name="TO-NAPID" value="GPRS_Settings_NAPID" />
<characteristic type="PORT">
<parm name="PORTNBR" value="8080" />
<parm name="SERVICE" value="CO-WSP" />
</characteristic>
</characteristic>
</characteristic>
<characteristic type="APPLICATION">
<parm name="APPID" value="w2" />
<parm name="NAME" value="GPRS Settings" />
<parm name="TO-PROXY" value="GPRS Settings_Proxy" />
<characteristic type="RESOURCE">
<parm name="NAME" value="GPRS Settings" />
<parm name="URI" value="http://portal.operator.com/" />
<parm name="STARTPAGE" />
</characteristic>
</characteristic>
</wap-provisioningdoc>

While this works properly on Nokia phones, on SonyEricsson phones, it will always create a WAP profile instead of an HTTP profile.

The reason for this is the following line in the above XML:

<parm name="SERVICE" value="CO-WSP" />

If you take that out, then you'll get the HTTP profile you expect on a SonyEricsson phone.

Since this parameter actually means to use WAP/WSP as the protocol, I can understand why SonyEricsson is creating a WAP/WSP profile.

So why do we include this parameter???

Well, if you specify any port other than a well known port (9200, 9201, 9202, and 9203 are well known WAP ports, while 80 and 8080 are considered well known HTTP ports), Nokia won't properly a profile. There is no "SERVICE" value for "HTTP" ... so Nokia wants "CO-WSP" to be used, even though the profile will be HTTP.

We had the "OMA OTA" web form in NowSMS add this setting automatically to avoid problems on Nokia phones.

But in light of this behaviour of SonyEricsson phones, and the fact that specifying this setting doesn't make logical sense ... we're going to change the default behaviour of the NowSMS OMA OTA web form.

If the connection type is "Other", we're going to omit this setting.

If we do this, SonyEricsson phones will work properly (and I suspect this will effect some other phones as well) ... and Nokia phones will work properly as long as the port used is "80" or "8080". If you need to send OTA for a different HTTP proxy port, then you will need to manually create your own XML.

This change is going to be reflected in the v5.51i patch, that is going to be uploaded later today (I will make a note in this thread when it is uploaded). But you can also just create your own XML, and omit this line.

If you want to use NowSMS default XML as a base for making your own settings, see the following thread for instructions on how to intercept the XML generated by the NowSMS web form: http://support.nowsms.com/discus/messages/485/4555.html

-bn
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 5016
Registered: 10-2002
Posted on Thursday, September 22, 2005 - 06:51 pm:   

An update for NowSMS v5.51 (any subversion) has been uploaded to address the issue discussed in this thread.

The update patch is available at http://www.nowsms.com/download/latestpatch.zip.

To install this update, unzip the attached files into the NowSMS program directory, and use them to replace the existing files of the same name.

This update is for the v5.51 release of the Now SMS/MMS Gateway product only. Applying these updates to other versions may cause unpredictable results.

Remember to stop the NowSMS services before attempting to install these updates.

Specific details regarding the issue discussed in this thread:


* OMA OTA Provisioning: No longer include <parm name="SERVICE" value="CO-WSP"/> when generating settings from the web page where the connection type is "other". When this setting is present, many phones assume that the settings are to use WAP/WSP instead of WAP2/HTTP. NowSMS was including these settings because otherwise Nokia phones will not accept the settings properly unless the port being used is 9200, 9201, 9202, 9203, 80, or 8080. Therefore, if you need to send proxy settings to a Nokia phone using a port other than one of these listed ports, it is necessary to manually generate an XML settings document, and include this line in the "PORT" characteristic section.

Login Login / Register Logout Logout Search Last 30 Days Topics Topics