From Forum Nokia Wiki

ID	TSS001363	Creation date	May 12, 2009
Platform	S60 3rd Edition	Devices
Category	Symbian C++	Subcategory	Networking, Device Management

Keywords (APIs, classes, methods, functions):

Overview

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

Description

TSS000699 - Adding access points via 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 TSS000699 - Adding access points via 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.