Share via

Adding a GSM-CSD Network Access Point (WAP Technique) Example

  • Article

4/8/2010

This example adds a NAPDEF (NAP1) by using WAP techniques.

Code Example

<characteristic type="NAPDEF">
  <parm name="NAPID" value="NAP1"/>
  <parm name="BEARER" value="GSM-CSD"/>
  <parm name="NAME" value="ANY NAME 3"/>
  <parm name="NAP-ADDRESS" value="+XXXXXXXXXXX"/>
  <parm name="NAP-ADDRTYPE" value="E164"/>
  <characteristic type="NAPAUTHINFO">
    <parm name="AUTHTYPE" value="PAP"/>
    <parm name="AUTHNAME" value="myuser"/>
    <parm name="AUTHSECRET" value="mysecret"/>
  </characteristic>
</characteristic>

Remarks

One provisioning XML file typically contains configuration information for multiple Configuration Service Providers. To use this example, you must replace the values as appropriate, and add the node as a child of the OMA Client Provisioning file. For information about the syntax of this file, see OMA Client Provisioning Files. For examples, see OMA Client Provisioning XML File Examples.

If you are using standard OMA Client Provisioning ("WAP Technique") format to add a network access point then your provisioning XML document must be placed in a mxipcold_<package name>_<version>.provxml file (for example mxipcold_myprovfile_<version>.provxml).

See Also

Tasks

NAPDEF Configuration Service Provider Examples for OMA Client Provisioning