| OMA OTA setting for Nokai N96, N85, Nokia 5800 XpressMusic... |  Search
|
|
NowSMS Support Forums ⬆ WAP Technical Discussions (unsupported) ⬆ |
◄ ► |
| Author | Message | |||
| chaoraksa New member Username: Chaoraksa Post Number: 1 Registered: 11-2008 |
Hi all!!! Please help! do you have any xml OMA OTA setting for this phone (Nokai N96, N85, Nokia 5800 XpressMusic)? Thanks in advanced. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7699 Registered: 10-2002 |
What have you tried that didn't work? Have you ever OTA'd any other phones, or are these the first ones you are attempting. Most Nokia devices require OTA settings to be signed with the USERPIN method. | |||
| chaoraksa New member Username: Chaoraksa Post Number: 3 Registered: 11-2008 |
I have used to send OTA setting with USERPIN (1234) to that phone model but don't work. After receiving that OTA setting, it can save but this setting store in the unrecognized folder in ( Setting -> connection -> Destination ). Below it the xml OTA setting that i send: <wap-provisioningdoc> <characteristic type="BOOTSTRAP"> <parm name="NAME" value="GPRS" /> </characteristic> <characteristic type="NAPDEF"> <parm name="NAME" value="GPRS" /> <parm name="NAPID" value="GPRS_NAPID" /> <parm name="BEARER" value="GSM-GPRS" /> <parm name="NAP-ADDRESS" value="internet" /> <parm name="NAP-ADDRTYPE" value="APN" /> <parm name="INTERNET" /> </characteristic> <characteristic type="APPLICATION"> <parm name="APPID" value="w2" /> <parm name="NAME" value="GPRS" /> <parm name="TO-NAPID" value="GPRS_NAPID" /> <characteristic type="RESOURCE"> <parm name="NAME" value="GPRS" /> <parm name="URI" value="www.telecom.com" /> <parm name="STARTPAGE" /> </characteristic> </characteristic> </wap-provisioningdoc> | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7701 Registered: 10-2002 |
That does look like something that should work. In cases like this, I usually try some trial and error. What if you take out the BOOTSTRAP characteristic section? What if you take out the APPLICATION characteristic section? Granted, you may want to ultimately find a way to add these settings back, but for testing it is important to figure out exactly what attribute or setting is causing a problem. -bn | |||
| Oclv New member Username: Oclv Post Number: 1 Registered: 09-2009 |
Has anyone come up with a solution to the OMA settings being sent to the unrecognised folder? I have been successfully sending various settings for a couple of years now, but with all of the latest Nokia devices the settings are now appearing in the unrecognised folder. The settings do still work on the new Nokia devices. Is there a change to the parms they expect? Is this a new feature of the firmware to discourage people other than the manufacturer/network sending settings? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1276 Registered: 08-2008 |
Is it related to this issue? http://support.nowsms.com/discus/messages/485/5910.html -- Des NowSMS Support | |||
| Oclv New member Username: Oclv Post Number: 2 Registered: 09-2009 |
Unfortunately that is not the case with my issue. It appears that newish S60 Nokia devices (at least the N97, 6800, 5730, E75, 6710, E52) have started breaking down the Access Points into several categories including Internet, Multimedia, WAP, and Uncategorised. Under this new orginisational structure all of our OMA settings are getting put in the Uncategorised folder (which can be manually moved to another folder). Our settings appear from the correct sender, get installed, defaulted, and work. They simply get put in the Uncategorised folder, which looks unprofessional. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1278 Registered: 08-2008 |
Which type of settings are you sending? I assume it's multiple settings in the same message? If you only send one type of setting, does it get categorised correctly? I can't say that I've experimented much with any of those phones, but with OTA issues, I usually like to start simple and then step-by-step add to the XML to figure out where the issue is. So, if you only send one type of setting in the XML, does it get categorised correctly? -- Des NowSMS Support | |||
| Oclv New member Username: Oclv Post Number: 3 Registered: 09-2009 |
Thanks for the reply. As a slight update to my previous posts, the folder that the settings are going into is "Uncategorised" not "Unrecoginsed". sorry for the confusion. For now I am only sending wap, mms, and isp. During testing of a new device, I send the settings seperately as some devices have issues with the number of parts a combined message will generate. But, your question did jog my memory that I was using a string table to compress the number of parts. Unfortunately even with that removed it is still classed as uncategorised. here is a sample of the ISP settings: <wap-provisioningdoc> <characteristic type="BOOTSTRAP"> <parm name="NAME" value="Vodafone Internet"/> <parm name="PROXY-ID" value="0.0.0.0"/> </characteristic> <characteristic type="NAPDEF"> <parm name="NAME" value="Vodafone Internet"/> <parm name="NAPID" value="N1"/> <parm name="BEARER" value="GSM-GPRS"/> <parm name="NAP-ADDRESS" value="internet"/> <parm name="NAP-ADDRTYPE" value="APN"/> <parm name="INTERNET"/> <characteristic type="NAPAUTHINFO"> <parm name="AUTHTYPE" value="PAP"/> <parm name="AUTHNAME" value="web"/> <parm name="AUTHSECRET" value="web"/> </characteristic> </characteristic> <characteristic type="APPLICATION"> <parm name="APPID" value="w2"/> <parm name="TO-NAPID" value="N1"/> <parm name="NAME" value="Vodafone Internet"/> <characteristic type="RESOURCE"> <parm name="URI" value="http://wap.google.com"/> <parm name="NAME" value="Google"/> <parm name="STARTPAGE"/> </characteristic> </characteristic> </wap-provisioningdoc> | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1287 Registered: 08-2008 |
Have you tried removing the "PROXY-ID" setting from the BOOTSTRAP section? I'm not sure what it is trying to accomplish, but if present it should reference a proxy defined in the settings, and there is no matching proxy. | |||
| Oclv New member Username: Oclv Post Number: 4 Registered: 09-2009 |
I have now tried it without the proxy-id as well as without the whole bootstrap section and I get the same results. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1299 Registered: 08-2008 |
I've got one more idea. Nokia phones like to have a "PROVURL" parameter in the BOOTSTRAP section. The presence of this parameter allows a future settings message to replace/update previous settings with the same "PROVURL". Modify your BOOTSTRAP section to include PROVURL: <characteristic type="BOOTSTRAP"> <parm name="NAME" value="Vodafone Internet"/> <parm name="PROVURL" value="http://mydomain/VodafoneInternet"/> </characteristic> The URL that you specify doesn't have to be a valid web URL. -- Des NowSMS Support | |||
| Oclv New member Username: Oclv Post Number: 5 Registered: 09-2009 |
I seem to have missed the PROVURL in my reading. It sounds like a very usefull parameter. Unfortunately it didn't resolve my current issue. Thanks for all your time and help. If I come across a solution or a reason why it is occuring, I will definately post back. | |||
| Masum Naqvi New member Username: Masum Post Number: 1 Registered: 11-2009 |
I am having the same issue. This is happening with all newer nokia devices running symbian 5th edition such as n97. 5800, 5530... The XML is correct and based on OMA specs but there seems to be something additional that Nokia requires to mark and identify access points to correct destinations. I have moved around and experimented with XML blocks (similar to the one listed above for ISP) to no avail. Any thoughts??? | |||
| Oclv New member Username: Oclv Post Number: 6 Registered: 09-2009 |
w904C improves the situation slightly if I add something like: <characteristic type="APPLICATION"> <parm name="APPID" value="w904C" /> <parm name="NAME" value="Internet" /> … <parm name="TO-NAPID" value="_ip" /> </characteristic> The settings will be put in a category that matches the NAME parameter. However, if the category name already exists, S60 5th edition will create a new category suffixed by a number so in the example above we will get the category "Internet (1)" So while not a perfect solution, with some clever category names and combined settings OTA/s it is possible to have a better user experience. One additional thing that I have noticed is that while uncategorized internet settings can be defaulted for the browser, it is not possible to default them for all applications. | |||
