Please note that as of October 24, 2014, the Nokia Developer Wiki will no longer be accepting user contributions, including new entries, edits and comments, as we begin transitioning to our new home, in the Windows Phone Development Wiki. We plan to move over the majority of the existing entries over the next few weeks. Thanks for all your past and future contributions.

Archived:Creating multiple access points using OMA DM

From Wiki
Jump to: navigation, search

Archived.pngArchived: This article is archived because it is not considered relevant for third-party developers creating commercial solutions today. If you think this article is still relevant, let us know by adding the template {{ReviewForRemovalFromArchive|user=~~~~|write your reason here}}.

Article Metadata
Created: User:Technical writer 1 (12 May 2009)
Last edited: hamishwillee (15 Jun 2012)


When creating multiple access points using OMA DM commands on devices, certain rules have to be followed.


Adding access points on Symbian using device management describes how to add a single access point. If this approach is used to create multiple access points in a sequence, the OMA DM server might be configured to create a runtime node named APIdxxx every time and the results would be unexpected because this value was already added in previous ADD command. In this case the OMA server encounters error "-418" indicating that the access point already exists.

The correct approach would be to first get the list of the top level runtime nodes of the access point tree using the command GET ./AP which would obtain the current list of runtime nodes as follows: "APId001/APId002/APId003....".

From this list, the OMA DM server should be able to generate a unique runtime node name. If the last current node is APId007, the server should be able to predict a unique value, such as APId008 or if not, it should be able to generate unique values that do not clash with the existing set of runtime nodes.

Once the server is ready with a unique runtime node name, such as APId010, it can follow the approach described in Adding access points on Symbian using device management with slight changes:

 Add ./AP/<APId010>    
Add ./AP/<APId010>/NAPDef/<NAPId001>
Add ./AP/<APId010>/NAPDef/<NAPId001>/Name NewAPName
Add ./AP/<APId010>/NAPDef/<NAPId001>/Bearer/<BId001>
Add ./AP/<APId010>/NAPDef/<NAPId001>/Bearer/<BId001>/BearerL GSM-GPRS
Add ./AP/<APId010>/NAPDef/<NAPId001>/Bearer/<BId001>/Direction Outgoing

where the inner runtime node names, such as "NAPId001" are locally unique within an access point.

Once this command succeeds, the next get command on AP runtimes nodes lists this node.

Note that user-entered runtime node names will be present on the AP tree even for the subsequent OMA DM sessions.

This page was last modified on 15 June 2012, at 00:48.
29 page views in the last 30 days.

Was this page helpful?

Your feedback about this content is important. Let us know what you think.


Thank you!

We appreciate your feedback.