| OTA File vs. Send XML Document |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through February 02, 2006 ⬆ |
◄ ► |
| Author | Message | |||
| Oded Cohen New member Username: Macman Post Number: 1 Registered: 01-2006 |
Hi Bryce, I've created 2 .OTA files which are used for Sony Ericsson provisioning. However, the strange thing is that it gives me the following error: "Error: Invalid Format for OTA File" when using the URL submission (using OMAOTA=xxx.ota), while the EXACT content, if pasted to the "Send XML Document" is working successfully and the OTA settings are submitted... Can you please check into this issue ASAP as this is something we MUST have working in order to purchase the product... We are currently working on the trial and planning to purchase the product ASAP. Thanks, Oded | |||
| Oded Cohen New member Username: Macman Post Number: 2 Registered: 01-2006 |
I have found that you seems to have a bug in the OMAOTA which does not accepe SE WV, and "OTA=xxx.ota" does work with those SE .ota files... Are you planning to fix it? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5400 Registered: 10-2002 |
Hi Oded, I'm not sure that the issues in your two messages are related. But I'd really need to see examples of what you are submitting to fully understand the question. I would suggest always using "OTA=" instead of "OMAOTA=". When you use the "OTA=" parameter, NowSMS will automatically detect the type of settings that are present by scanning the settings. When you use the "OMAOTA=" parameter, it assumes that they are in the OMA Provisioining Content, and bypasses the automatic check. (And if the automatic check can't determine the settings type, it is unlikely that the encoder would actually encode them correctly.) So the "OMAOTA=" parameter is something of a "legacy" parameter. I would not recommend using it, and you are better off using the "OTA=" parameter which will accept any of the supported settings formats. Now that I think about it, I suppose this would explain the first issue as well. If you specified "OMAOTA=" to reference a settings file, but the settings file was actually a "CHARACTERISTIC-LIST" or "SyncSettings" or "WVSettings" document, then it would not be encoded properly, because we would try to process it as "OMA Provisioning Content". Therefore the "Invalid Format for OTA File" error would be returned. Bottom line, use the "OTA=" parameter for the automatic settings type check. (The "OMAOTA=" parameter can only be used if it is an OMA Provisioning Content, e.g., "wap-provisioningdoc" format document. And even then, to avoid confusion, it is best to specify "OTA=" so that NowSMS automatically figures out the format.) -bn | |||
| Oded Cohen New member Username: Macman Post Number: 3 Registered: 01-2006 |
Hi Bryce, I indeed checked and the OTA also supports both formats... I will use it instead of the OTAOMA=xxx Can you provide me some examples you are using for WV/IMPS provisioning for using with Sony Ericsson devices? I have the Nokia working (from the NowIMP documentation + some experience), but the Sony Ericsson format (WVSettings) fails to be received on the phone as expected... As far as I read and understand it should be a 2 parts XML, one for the GPRS and the second for WV settings... Thanks, Oded | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5403 Registered: 10-2002 |
Hi Oded, With newer SonyEricsson devices, like the W800, I've had luck sending the OMA OTA format for this provisioning. But I can't say that I've tried OMA OTA for WV/IMPS provisioning on the earlier SE phones (K700/S700 would be the earliest SE phones to support WV/IMPS). So let me give you an example of the old SE format, and then I'll also give an OMA OTA example. <WVSettings> <WVOTAVersion>1.0</WVOTAVersion> <WVCommon> <WVSettingsName>WV</WVSettingsName> <WVRefName>Profile</WVRefName> <WVSupportedVersion>1.0</WVSupportedVersion> <WVSupportedVersion>1.1</WVSupportedVersion> <WVUserID>username</WVUserID> <WVPassword>password</WVPassword> <WVPreferredProtocol/> </WVCommon> <WVHTTP> <WVSAPURI>http://server/path</WVSAPURI> <WVSAPFourWaySupported>T</WVSAPFourWaySupported> </WVHTTP> </WVSettings> The "WVRefName" value (Profile) refers to an existing internet connection profile. Note that you can only provision "WAP" proxy internet connection (not "HTTP") via the old style of OTA. Here's a simple example: <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="gprsapn" /> <PARM NAME="PPP_AUTHTYPE" VALUE="PAP" /> <PARM NAME="PPP_AUTHNAME" VALUE="gprsusername" /> <PARM NAME="PPP_AUTHSECRET" VALUE="gprspassword" /> <PARM NAME="ISP_NAME" VALUE="Profile" /> </CHARACTERISTIC> <CHARACTERISTIC TYPE="URL" VALUE="http://home/page" /> <CHARACTERISTIC TYPE="NAME"> <PARM NAME="NAME" VALUE="Profile" /> </CHARACTERISTIC> </CHARACTERISTIC-LIST> Now let's try the OMA OTA example: <wap-provisioningdoc> <characteristic type="BOOTSTRAP"> <parm name="NAME" value="WVIMPS" /> <parm name="PROXY-ID" value="WVIMPS_Proxy" /> </characteristic> <characteristic type="NAPDEF"> <parm name="NAME" value="WVIMPS" /> <parm name="NAPID" value="WVIMPS_NAPID" /> <parm name="BEARER" value="GSM-GPRS" /> <parm name="NAP-ADDRESS" value="gprsapn" /> <parm name="NAP-ADDRTYPE" value="APN" /> </characteristic> <characteristic type="PXLOGICAL"> <parm name="NAME" value="WVIMPS" /> <parm name="PROXY-ID" value="WVIMPS_Proxy" /> <characteristic type="PXPHYSICAL"> <parm name="PHYSICAL-PROXY-ID" value="WVIMPS_PhProxy" /> <parm name="PXADDR" value="1.2.3.4" /> <parm name="PXADDRTYPE" value="IPV4" /> <parm name="TO-NAPID" value="WVIMPS_NAPID" /> <characteristic type="PORT"> <parm name="PORTNBR" value="9201" /> <parm name="SERVICE" value="CO-WSP" /> </characteristic> </characteristic> </characteristic> <characteristic type="APPLICATION"> <parm name="APPID" value="wA" /> <parm name="TO-PROXY" value="WVIMPS_Proxy" /> <parm name="NAME" value="WVIMPS" /> <parm name="ADDR" value="http://server/path" /> <characteristic type="APPAUTH"> <parm name="AAUTHLEVEL" value="APPSRV" /> <parm name="AAUTHNAME" value="username" /> <parm name="AAUTHSECRET" value="password" /> </characteristic> </characteristic> </wap-provisioningdoc> -bn | |||
