| 6230i OMA-OTA settings |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through October 19, 2005 ⬆ |
◄ ► |
| Author | Message | |||
| Anonymous |
hi every body i sent ota settings to nokia 6230i but i note that in the mobile's Menu sync->sync server->sync settings->Config.Settings it is showing "Unnamed".and i didn't find the server ip and the port . and when i make sync with the server it say the sync faild. the server is sync4j my ota is <?xml version="1.0"?> <!DOCTYPE wap-provisioningdoc PUBLIC "-//WAPFORUM//DTD PROV 1.0//EN" "http://www.wapforum.org/DTD/prov.dtd"> <wap-provisioningdoc> <characteristic type="APPLICATION"> <parm name="APPID" value="w5"/> <parm name="NAME" value="new Sync Server"/> <parm name="TO-NAPID" value="INTERNET"/> <characteristic type="APPADDR"> <parm name="ADDR" value="http://serevr ip/sync4j/sync"/> <characteristic type="PORT"> <parm name="PORTNBR" value="8080"/> </characteristic> </characteristic> <characteristic type="RESOURCE"> <parm name="URI" value="./contact"/> <parm name="NAME" value="contacts"/> <parm name="AACCEPT" value="text/x-vcard,text/vcard"/> </characteristic> <characteristic type="APPAUTH"> <parm name="AAUTHNAME" value="test"/> <parm name="AAUTHSECRET" value="test"/> </characteristic> </characteristic> </wap-provisioningdoc> please help me thanks alot | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5150 Registered: 10-2002 |
Hi, Nokia Series 40 phones expect a "BOOTSTRAP" section to be present, with a name for the settings. That is why your settings are showing up unnamed. Also, there seems to be some debate and confusion for SyncML settings whether you should use "ADDR" directly in the characteristic "APPLICATION" section, or whether it should be under an "APPADDR" section with "ADDR" and "PORT" separated. Since SyncML is HTTP based, the application address is an HTTP URI. According to OMA Provisioning Content v1.1 specifications, "ADDR" in the characteristic "APPLICATION" section can have a value that is either a URI (e.g., http://), an IPv4 address, or an internet host name. If you use the characteristic "APPADDR" section, then the "ADDR" value can be either an IPv6 address, an E164 phone number, or a generic alphanumeric address. Although you could consider an HTTP URI to be within the specifications of a generic alphanumeric address, since HTTP URI is explicitly listed as an allowed value type for parm "ADDR" in the characteristic "APPLICATION" section, but NOT for parm "ADDR" in the characteristic "APPADDR" section, I would lean toward interpreting this to mean that if the address is an HTTP URI (such as for a SyncML server setting), then it should be specified as a parm "ADDR" value in the characteristic "APPLICATION" section. The example below reflects these two changes: <wap-provisioningdoc> <characteristic type="BOOTSTRAP"> <parm name="NAME" value="SyncML Settings"/> </characteristic> <characteristic type="APPLICATION"> <parm name="APPID" value="w5" /> <parm name="TO-NAPID" value="INTERNET" /> <parm name="NAME" value="SyncML Settings" /> <parm name="ADDR" value="http://server:port/syncml" /> <characteristic type="RESOURCE"> <parm name="URI" value="./contacts" /> <parm name="NAME" value="Contacts DB" /> <parm name="AACCEPT" value="text/x-vcard" /> </characteristic> <characteristic type="RESOURCE"> <parm name="URI" value="./calendar" /> <parm name="NAME" value="Calendar DB" /> <parm name="AACCEPT" value="text/x-vcalendar" /> </characteristic> <characteristic type="RESOURCE"> <parm name="URI" value="./notes" /> <parm name="NAME" value="Notes DB" /> <parm name="AACCEPT" value="text/plain" /> </characteristic> <characteristic type="APPAUTH"> <parm name="AAUTHNAME" value="testuser" /> <parm name="AAUTHSECRET" value="testpass" /> </characteristic> </characteristic> </wap-provisioningdoc> Just remove the characteristic "RESOURCE" sections that are not applicable for your configuration. -bn | |||
