OMA client provisioing to nokia 6600 | Search |
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through October 19, 2005 ⬆ |
◄ ► |
Author | Message | |||
Anonymous |
I tried to send syncml settings using OMA client provisioing to nokia 6600 and I am using nowsms and my xml file 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"> <characteristic type="APPADDR"> <parm name="ADDR" value="http://sync.pt98.com/sync"/> <characteristic type="PORT"> <parm name="PORTNBR" value="8080"/> </characteristic> </characteristic> <characteristic type="RESOURCE"> <parm name="URI" value="./ycontact"/> <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> the message is sent to the mobile(6600)only once, and when i sent it again it send any thing to the mobile please please help me Please advise if I did anything wrong please give me an explaination ,or give me any hent to continue my working. Thanks a lot, | |||
Anonymous |
please please give me an explaination ,or give me any hent to continue my working. please reply to me | |||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4871 Registered: 10-2002 |
Hi, Here are 2 example templates that we use for provisioning SyncML settings using OMA Provisioning. The first example includes the proxy definition, so that the SyncML settings are bound to a specific proxy. <wap-provisioningdoc> <characteristic type="BOOTSTRAP"> <parm name="NAME" value="SyncML" /> </characteristic> <characteristic type="NAPDEF"> <parm name="NAME" value="SyncML" /> <parm name="NAPID" value="SyncML_NAPID" /> <parm name="BEARER" value="GSM-GPRS" /> <parm name="NAP-ADDRESS" value="gprs.apn" /> <parm name="NAP-ADDRTYPE" value="APN" /> <characteristic type="NAPAUTHINFO"> <parm name="AUTHTYPE" value="PAP" /> </characteristic> </characteristic> <characteristic type="PXLOGICAL"> <parm name="NAME" value="SyncML" /> <parm name="PROXY-ID" value="SyncML_Proxy" /> <characteristic type="PXPHYSICAL"> <parm name="PHYSICAL-PROXY-ID" value="SyncML_PhProxy" /> <parm name="PXADDR" value="1.2.3.4" /> <parm name="PXADDRTYPE" value="IPV4" /> <parm name="TO-NAPID" value="SyncML_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="w5" /> <parm name="TO-PROXY" value="SyncML_Proxy" /> <parm name="NAME" value="SyncML" /> <parm name="ADDR" value="http://syncserver:port/path" /> <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="syncusername" /> <parm name="AAUTHSECRET" value="syncpassword" /> </characteristic> </characteristic> </wap-provisioningdoc> The second example includes only the SyncML settings, which will use an existing "internet" connection profile, if one is defined: <wap-provisioningdoc> <characteristic type="APPLICATION"> <parm name="APPID" value="w5" /> <parm name="TO-NAPID" value="INTERNET" /> <parm name="NAME" value="SyncML" /> <parm name="ADDR" value="http://syncserver:port/path" /> <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="syncusername" /> <parm name="AAUTHSECRET" value="syncpassword" /> </characteristic> </characteristic> </wap-provisioningdoc> Here is another example for sending a GPRS access point definition which should be used as the default profile on the phone for internet accessability: <wap-provisioningdoc> <characteristic type="BOOTSTRAP"> <parm name="NAME" value="Internet" /> </characteristic> <characteristic type="NAPDEF"> <parm name="NAME" value="Internet" /> <parm name="NAPID" value="Internet_NAPID" /> <parm name="BEARER" value="GSM-GPRS" /> <parm name="NAP-ADDRESS" value="gprs.apn" /> <parm name="NAP-ADDRTYPE" value="APN" /> <parm name="INTERNET" /> <characteristic type="NAPAUTHINFO"> <parm name="AUTHTYPE" value="PAP" /> </characteristic> </characteristic> </wap-provisioningdoc> Good luck! -bn |