Ozeki NG SMS Gateway logo OZEKI NG SMS Gateway
"The World's most reliable SMS gateway software!"
info@ozekisms.com
Tel.: +36 1 371 0150
SMS Gateway to send SMS via GSM modem or IP SMS connection Overview SMS Gateway to send SMS via GSM modem or IP SMS connection SMS Gateway to send SMS via GSM modem or IP SMS connection Quick start SMS Gateway to send SMS via GSM modem or IP SMS connection SMS Gateway to send SMS via GSM modem or IP SMS connection Download SMS Gateway to send SMS via GSM modem or IP SMS connection SMS Gateway to send SMS via GSM modem or IP SMS connection Manual SMS Gateway to send SMS via GSM modem or IP SMS connection SMS Gateway to send SMS via GSM modem or IP SMS connection How to buy SMS Gateway to send SMS via GSM modem or IP SMS connection SMS Gateway to send SMS via GSM modem or IP SMS connection FAQ SMS Gateway to send SMS via GSM modem or IP SMS connection SMS Gateway to send SMS via GSM modem or IP SMS connection Contact Us SMS Gateway to send SMS via GSM modem or IP SMS connection
OZEKI NG SMS Gateway - Product Guide

SyncML settings Contents | SearchUSSD

Home > Product Manual > Appendix > C - Message types > OMA OTA Settings

SMS Gateway SMS Gateway Home

  Product Manual
  Introduction
  SMS technology
  Installation Guide
  User Guide
  Developers Guide
  Examples and Solutions
  Appendix
  A - Terms and definitions
  B - References
  C - Message types
  Introduction
  OTA bitmap
  Operator logo I.
  Operator logo II.
  Ringtone
  Wappush
  Binary XML
  VCard
  VCalendar
  Special SMS Message Indication
  Bookmark
  MMS:XML
  WAP Browser Settings
  SyncML settings
  OMA OTA Settings
  USSD
  WAP Push SL
  Picture message
  D - Database connection strings
  E - SMS alphabet
  F - GSM error codes
  G - SMSC settings
  H - MMSC settings
  I - GSM operators
  J - SMPP providers
  K - GSM modems, phones
  L - Error codes
  M - Country codes
  O - SMPP Error codes
  W - Wireshark Capture
  FAQ
  Feature list
  Commercial Information
  Search
  Cookie policy
 


Automated phone calls?
Ozeki Phone System XE VoIP PBX software is an advanced PBX built for automated voice calls and 2 way SMS messaging. It has outstanding APIs for software developers. It can be used for:

Phone calls from SQL
Phone calls from HTTP
Voice and SMS applications

Callcenter developers
If you are working on telephone solutions, please check out the Ozeki VoIP SIP SDK.
It can be used to create VoIP client and server software.

Contact Us!
If you wish to get further information, do not hesitate to contact us!

E-mail: info@ozekisms.com

If you have a technical question, please submit a support request on-line.

Mobile message type specification - OMA OTA settings SMS
(SMS message type, SMS message format)

Introduction

OMA OTA settings refer to the setting up of new services, such as GPRS, MMS and Instant Messaging for an existing subscriber of a mobile phone network, and any gateways for standard Internet chat or mail services. Network operators typically send these settings to the subscriber's handset using SMS or WAP as mobile operating systems accept.

Why it is convenient

If you do not want to set the browser of every phone manually to enable it to connect to the network or to specify the e-mail settings, this message type can be used to send the required settings. This way, the necessary parameters can be set by just pressing one or two buttons.

Message type

SMS:WAPPUSH:OMAOTASETTINGS:GPRS    for GPRS connection
SMS:WAPPUSH:OMAOTASETTINGS:GSMCSD  for GSM/CSD connection

The format of the message data is:

You can modify this structure according to the OMA WAP Provisioning description.

<wap-provisioningdoc version="...">
    <characteristic type="BOOTSTRAP">
        <parm name="NAME" value="..."/>
    </characteristic>
    <characteristic type="NAPDEF">
        <parm name="NAPID" value="..."/>
        <parm name="NAME" value="..."/>
        <parm name="BEARER" value="..."/>
        <parm name="NAP-ADDRESS" value="..."/>
        <parm name="NAP-ADDRTYPE" value="..."/>
        <characteristic type="NAPAUTHINFO">
            <parm name="AUTHTYPE" value="..."/>
            <parm name="AUTHNAME" value="..."/>
            <parm name="AUTHSECRET" value="..."/>
        </characteristic>
    </characteristic>
    <characteristic type="PXLOGICAL">
        <parm name="PROXY-ID" value="..."/>
        <parm name="NAME" value="..."/>
        <parm name="STARTPAGE" value="..."/>
        <characteristic type="PXAUTHINFO">
            <parm name="PXAUTH-TYPE" value="..."/>
            <parm name="PXAUTH-ID" value="..."/>
            <parm name="PXAUTH-PW" value="..."/>
        </characteristic>
        <characteristic type="PXPHYSICAL">
            <parm name="PHYSICAL-PROXY-ID" value="..."/>
            <parm name="PXADDR" value="..."/>
            <parm name="PXADDRTYPE" value="..."/>
            <parm name="TO-NAPID" value="..."/>
            <characteristic type="PORT">
                <parm name="PORTNBR" value="..."/>
                <parm name="SERVICE" value="..."/>
            </characteristic>
        </characteristic>
    </characteristic>
    <characteristic type="APPLICATION">
        <parm name="APPID" value="..."/>
        <parm name="NAME" value="..."/>
        <parm name="TO-PROXY" value="..."/>
        <characteristic type="RESOURCE">
            <parm name="URI" value="..."/>
            <parm name="NAME" value="..."/>
            <parm name="STARTPAGE"/>
        </characteristic>
    </characteristic>
    <characteristic type="APPLICATION">
        <parm name="APPID" value="..."/>
        <parm name="NAME" value="..."/>
        <parm name="TO-PROXY" value="..."/>
        <parm name="ADDR" value="..."/>
    </characteristic>
    <characteristic type="APPLICATION">
        <parm name="APPID" value="..."/>
        <parm name="NAME" value="..."/>
        <parm name="TO-PROXY" value="..."/>
        <parm name="ADDR" value="..."/>
        <characteristic type="APPAUTH">
            <parm name="AAUTHLEVEL" value="..."/>
            <parm name="AAUTHNAME" value="..."/>
            <parm name="AAUTHSECRET" value="..."/>
        </characteristic>
    </characteristic>
    <characteristic type="APPLICATION">
        <parm name="APPID" value="..."/>
        <parm name="NAME" value="..."/>
        <parm name="TO-NAPID" value="..."/>
        <parm name="ADDR" value="..."/>
        <characteristic type="APPAUTH">
            <parm name="AAUTHNAME" value="..."/>
            <parm name="AAUTHSECRET" value="..."/>
        </characteristic>
        <characteristic type="RESOURCE">
            <parm name="URI" value="..."/>
            <parm name="NAME" value="..."/>
            <parm name="AACCEPT" value="..."/>
        </characteristic>
    </characteristic>
    <characteristic type="APPLICATION">
        <parm name="APPID" value="..."/>
        <parm name="PROVIDER-ID" value="..."/>
        <parm name="TO-NAPID" value="..."/>
        <parm name="FROM" value="..."/>
        <characteristic type="APPADDR">
            <parm name="ADDR" value="..."/>
            <characteristic type="PORT">
                <parm name="PORTNBR" value="..."/>
            </characteristic>
        </characteristic>
        <characteristic type="APPAUTH">
            <parm name="AAUTHNAME" value="..."/>
            <parm name="AAUTHSECRET" value="..."/>
        </characteristic>
    </characteristic>
    <characteristic type="APPLICATION">
        <parm name="APPID" value="..."/>
        <parm name="PROVIDER-ID" value="..."/>
        <parm name="TO-NAPID" value="..."/>
        <characteristic type="APPADDR">
            <parm name="ADDR" value="..."/>
            <characteristic type="PORT">
                <parm name="PORTNBR" value="..."/>
            </characteristic>
        </characteristic>
        <characteristic type="APPAUTH">
            <parm name="AAUTHNAME" value="..."/>
            <parm name="AAUTHSECRET" value="..."/>
        </characteristic>
    </characteristic>
    <ozSecurityInfo>
        <OTAPIN>...</OTAPIN>
        <SecParam>...</SecParam>
    </ozSecurityInfo>
</wap-provisioningdoc>


The dark green section can be left out.
The <ozSecurityInfo> element is not included in the OMA WAP Provisioning
standard.
It is used to inform the SMS encoding program that you want to use security
settings.

Look at an example:

The following example will show you how to send a SyncML DS Settings to a phone
with security settings. The connection is GPRS.

<wap-provisioningdoc version="1.1">
    <characteristic type="BOOTSTRAP">
        <parm name="NAME" value="GPRSSetting"/>
    </characteristic>
    <characteristic type="NAPDEF">
        <parm name="NAPID" value="GPRSSetting_NAP"/>
        <parm name="NAME" value="GPRSSettingGPRS"/>
        <parm name="BEARER" value="GSM-GPRS"/>
        <parm name="NAP-ADDRESS" value="WAP"/>
        <parm name="NAP-ADDRTYPE" value="APN"/>
    </characteristic>
    <characteristic type="PXLOGICAL">
        <parm name="PROXY-ID" value="GPRSSetting_PRX"/>
        <parm name="NAME" value="GPRSSetting_Proxy"/>
        <characteristic type="PXPHYSICAL">
            <parm name="PHYSICAL-PROXY-ID" value="GPRSSetting_PHPX"/>
            <parm name="PXADDR" value="100.100.100.110"/>
            <parm name="PXADDRTYPE" value="IPV4"/>
            <parm name="TO-NAPID" value="GPRSSetting_NAP"/>
            <characteristic type="PORT">
                <parm name="PORTNBR" value="9200"/>
                <parm name="SERVICE" value="CL-WSP"/>
            </characteristic>
        </characteristic>
    </characteristic>
    <characteristic type="APPLICATION">
        <parm name="APPID" value="w5"/>
        <parm name="NAME" value="GPRSSetting"/>
        <parm name="TO-NAPID" value="GPRSSetting_NAP"/>
        <parm name="ADDR" value="http://syncserver.com"/>
        <characteristic type="APPAUTH">
            <parm name="AAUTHNAME" value="SyncMLUser"/>
            <parm name="AAUTHSECRET" value="SyncMLPassw"/>
        </characteristic>
        <characteristic type="RESOURCE">
            <parm name="URI" value="./contacts"/>
            <parm name="NAME" value="Contacts DB"/>
            <parm name="AACCEPT" value="text/x-vcard"/>
        </characteristic>
    </characteristic>
        <ozSecurityInfo>
        <OTAPIN>1234</OTAPIN>
        <SecParam>1</SecParam>
    </ozSecurityInfo>
</wap-provisioningdoc>

SQL example:

If you use the Database user to send and receive SMS messages with Ozeki NG - SMS Gateway, you can use the following SQL statement to send an OMA OTA Settings message:
insert into ozekimessageout (receiver,msgtype,msg,status) values (’+36205222245’,
    ’SMS:WAPPUSH:OMAOTASETTINGS:GPRS’,’<wap-provisioningdoc version="1.1">
                                     <characteristic type="BOOTSTRAP">
                                     <parm name="NAME" value="GPRSSetting"/>
                                     </characteristic>
                                     <characteristic type="NAPDEF">
                                     <parm name="NAPID" value="GPRSSetting_NAP"/>
                                     <parm name="NAME" value="GPRSSettingGPRS"/>
                                     <parm name="BEARER" value="GSM-GPRS"/>
                                     <parm name="NAP-ADDRESS" value="WAP"/>
                                     <parm name="NAP-ADDRTYPE" value="APN"/>
                                     </characteristic>
                                     <characteristic type="PXLOGICAL">
                                     <parm name="PROXY-ID" value="GPRSSetting_PRX"/>
                                     <parm name="NAME" value="GPRSSetting_Proxy"/>
                                     <characteristic type="PXPHYSICAL">
                                     <parm name="PHYSICAL-PROXY-ID" value="GPRSSetting_PHPX"/>
                                     <parm name="PXADDR" value="100.100.100.110"/>
                                     <parm name="PXADDRTYPE" value="IPV4"/>
                                     <parm name="TO-NAPID" value="GPRSSetting_NAP"/>
                                     <characteristic type="PORT">
                                     <parm name="PORTNBR" value="9200"/>
                                     <parm name="SERVICE" value="CL-WSP"/>
                                     </characteristic></characteristic>
                                     </characteristic>
                                     <characteristic type="APPLICATION">
                                     <parm name="APPID" value="w5"/>
                                     <parm name="NAME" value="GPRSSetting"/>
                                     <parm name="TO-NAPID" value="GPRSSetting_NAP"/>
                                     <parm name="ADDR" value="http://syncserver.com"/>
                                     <characteristic type="APPAUTH">
                                     <parm name="AAUTHNAME" value="SyncMLUser"/>
                                     <parm name="AAUTHSECRET" value="SyncMLPassw"/>
                                     </characteristic>
                                     <characteristic type="RESOURCE">
                                     <parm name="URI" value="./contacts"/>
                                     <parm name="NAME" value="Contacts DB"/>
                                     <parm name="AACCEPT" value="text/x-vcard"/>
                                     </characteristic></characteristic>
                                     <ozSecurityInfo><OTAPIN>1234</OTAPIN>
                                     <SecParam>1</SecParam></ozSecurityInfo>
                                     </wap-provisioningdoc>’,’send’);




Next page: USSD
Copyright © 2000 - 2017 Ozeki Informatics Ltd.
All rights reserved

Software PBX for Windows | VoIP SDK   |   Legal information   |   Privacy policy   |   Terms of use
Please, address your inquiries to info@ozekisms.com