NowSMS supports sending OTA (Over-the-Air) configuration information to mobile devices in order to configure some phone settings, such as internet browser, MMS, SyncML, and instant messaging settings.
The “Send WAP OTA Settings” option sends configuration settings in a format that is compatible with the Nokia/Ericsson OTA Specification (up to and including v7.1). This specification is mostly used by older devices, while most newer devices use the OMA (Open Mobile Alliance) OTA Provisioning Content, which is accessible via the Send OMA OTA Settings menu.
There are four different types of WAP OTA settings.
- Connection (and MMS Settings) – This sends configuration settings for the WAP/internet browser and/or MMS client.
- Bookmark – This sends a single bookmark for a web site to the mobile device (mostly supported only by older Nokia phones)
- SyncML Settings – This sends configuration settings for the SyncML client
- Wireless Village/IMPS Settings – This sends configuration settings for the Instant Messaging client.
Additional information regarding WAP OTA settings can be found in Sending WAP OTA Settings.
Note that beginning with NowSMS 2007, there is now a “View XML” button on all of the WAP and OMA OTA Settings forms. This button will display the XML document that NowSMS has generated for the current web form. This allows for easier customisation of settings to meet different requirements.
The OTA web forms supported by NowSMS are displayed on the following pages.
WAP OTA: Browser/MMS Client – GPRS/EDGE/Packet Data Settings
“Connection Type” specifies whether to use GPRS/EDGE/Packet Data, or GSM/CSD (Circuit-Switched Data). The web form is different depending on this selection, here we will describe the settings relevant for GPRS/EDGE/Packet Data.
“Phone Number to Receive Settings” is a comma delimited list of one or more phone numbers to receive the settings via SMS.
“GPRS Access Point Name” is the Access Point Name (APN) that should be used for these connection settings.
If “GPRS Login Parameters” is set to “Prompted”, then the browser will prompt for a user name and password every time a connection is attempt, and the “GPRS User Name” and “GPRS Password” settings will be ignored. If it is set to “Automatic”, the user will not be prompted for login information, and the “GPRS User Name” and “GPRS Password” fields will be used automatically. (Note that many access points do not require a user name and password to be specified.)
“GPRS Login Type” specifies the authentication protocol to be used for sending the user name and password for connecting to the access point. The standard choice is “PAP”, however “CHAP” and “MS-CHAP” can also be selected.
“WAP Gateway IP Address” specifies the IP address of a WAP gateway to be used for this connection profile.
If “WAP Gateway Login Parameters” is set to “Prompted”, then the browser will prompt for a user name and password every time a connection is attempt, and the “WAP Gateway User Name” and “WAP Gateway Password” settings will be ignored. If it is set to “Automatic”, the user will not be prompted for login information, and the “WAP Gateway User Name” and “WAP Gateway Password” fields will be used automatically. (Note that most gateways do not require a user name and password to be specified, and many phones also do not support sending a user name and password to the WAP Gateway.)
“WAP Gateway Connection Type” specifies which of the WAP protocols to use when connecting to the WAP Gateway. For most mobile operator gateways, you would use “Connection-oriented” for a standard non-secure connection (port 9201), or “Connection-oriented, Secure (WTLS)” for a secure connection (port 9203). The “Connection-less” protocols provide limited functionality. For a WAP2/HTTP Proxy, the port number is installation dependent. Frequently port 8080 is used, but it can be any port value.
“Settings Name” provides a descriptive name for the connection settings, which may be displayed on the mobile phone.
“Home Page URL” specifies the home page to be configured for the settings, if these settings are to be used to configure WAP/internet browser settings.
“MMS Message Server URL” specifies the URL for the MMSC server, if these settings are to be used to configure the MMS client.
Note that some phones support both the “Home Page URL” and “MMS Message Server URL” elements being present, and will configure both the WAP/internet browser and the MMS client. Other phones will only support one of these settings being present.
Use the “Submit” button to send the settings, or use the “View XML” button to view the XML settings that are generated by this web form.
Note: To define connection settings that do not use a proxy, leave the “WAP Gateway IP Address” field blank, and set the “WAP Gateway Connection Type” to port “80”.
WAP OTA – Browser/MMS Client: GSM/Circuit Switch Data Settings
“Connection Type” specifies whether to use GPRS/EDGE/Packet Data, or GSM/CSD (Circuit-Switched Data). The web form is different depending on this selection, here we will describe the settings relevant for GSM/CSD.
“Phone Number to Receive Settings” is a comma delimited list of one or more phone numbers to receive the settings via SMS.
“ISP Phone Number” is the phone number to be dialed to connect to the access server.
“ISP Call Type” specifies whether the connection type is “Analogue” or “ISDN”.
“ISP Call Speed” specifies the speed of the connection. Normally this would be set to “AUTO”, but it may be necessary to configure a specific speed in special situations.
If “ISP Login Parameters” is set to “Prompted”, then the browser will prompt for a user name and password every time a connection is attempt, and the “ISP User Name” and “ISP Password” settings will be ignored. If it is set to “Automatic”, the user will not be prompted for login information, and the “ISP User Name” and “ISP Password” fields will be used automatically.
“ISP Login Type” specifies the authentication protocol to be used for sending the user name and password for connecting to the access server. The standard choice is “PAP”, however “CHAP” and “MS-CHAP” can also be selected.
“WAP Gateway IP Address” specifies the IP address of a WAP gateway to be used for this connection profile.
If “WAP Gateway Login Parameters” is set to “Prompted”, then the browser will prompt for a user name and password every time a connection is attempt, and the “WAP Gateway User Name” and “WAP Gateway Password” settings will be ignored. If it is set to “Automatic”, the user will not be prompted for login information, and the “WAP Gateway User Name” and “WAP Gateway Password” fields will be used automatically. (Note that most gateways do not require a user name and password to be specified, and many phones also do not support sending a user name and password to the WAP Gateway.)
“WAP Gateway Connection Type” specifies which of the WAP protocols to use when connecting to the WAP Gateway. For most mobile operator gateways, you would use “Connection-oriented” for a standard non-secure connection (port 9201), or “Connection-oriented, Secure (WTLS)” for a secure connection (port 9203). The “Connection-less” protocols provide limited functionality. For a WAP2/HTTP Proxy, the port number is installation dependent. Frequently port 8080 is used, but it can be any port value.
“Settings Name” provides a descriptive name for the connection settings, which may be displayed on the mobile phone.
“Home Page URL” specifies the home page to be configured for the settings, if these settings are to be used to configure WAP/internet browser settings.
“MMS Message Server URL” specifies the URL for the MMSC server, if these settings are to be used to configure the MMS client.
Note that some phones support both the “Home Page URL” and “MMS Message Server URL” elements being present, and will configure both the WAP/internet browser and the MMS client. Other phones will only support one of these settings being present.
Use the “Submit” button to send the settings, or use the “View XML” button to view the XML settings that are generated by this web form.
Note: To define connection settings that do not use a proxy, leave the “WAP Gateway IP Address” field blank, and set the “WAP Gateway Connection Type” to port “80”.
“Phone Number” specifies a comma delimited list of one or more phone numbers to receive the bookmark.
“Text” specifies the descriptive name for the bookmark.
“WAP URL” specifies the HTTP URL for the bookmark.
Use the “Submit” button to send the settings, or use the “View XML” button to view the XML settings that are generated by this web form.
Please note that this functionality is not very widely supported, and is mostly supported only by older Nokia phones.
WAP OTA: SyncML Settings
“Phone Number to Receive Settings” is a comma delimited list of one or more phone numbers to receive the settings via SMS.
“Settings Name” is a descriptive name for the settings that may be displayed on the mobile phone.
“Sync URL” is the HTTP URL associated with the SyncML server.
“Sync Port” is the port number associated with the SyncML server. Normally this would be part of the “Sync URL”, but there is some ambiguity in this OTA specification.
User authentication in SyncML can be done on different levels. Therefore this OTA form contains many forms that allow a user name and password to be input. Normally, user authentication will only be performed by the SyncML Server, in which case it is only necessary to use the “Sync Server User Name”, “Sync Server Password” and “Sync Server Auth Scheme” settings for specifying a user name and password.
If HTTP Authentication is needed (Authorization: header), then the “Sync HTTP User Name”, “Sync HTTP Password” and “Sync HTTP Auth Scheme” settings can be used.
A “Database URI” is required for each SyncML database that is supported by the server. This is a relative URI, and not a complete URL specification. (It is common to see values such as “Calendar” or “./Calendar” for the “Calendar Database URI”, for example.)
The “Data Connection Profile” setting refers to an existing data connection profile that should exist on the device (e.g., the “Settings Name” associated with OTA settings for a browser connection settings message that was previously sent to the device). The “Data Connection Type” specifies whether the “Data Connection Profile” uses a “WAP Proxy” or an “HTTP Proxy” (although it is unclear why this might be necessary to know in the SyncML settings).
“OTA PIN” and “OTA PIN Type” are optional parameters supported for SyncML settings over WAP OTA, but that are commonly used in OMA OTA requests.
An “OTA PIN” can be associated with an OTA settings message to provide a layer of authentication to the message. Many devices will allow you to send OTA settings without a PIN, but some will require a PIN to be present before the settings will be accepted.
There are three different types of OTA PINs, depending on the “OTA PIN Type” setting.
- The simplest “OTA PIN Type” is “User PIN” (USERPIN). This setting indicates that a short PIN code (often 4 digits) is supplied as the “OTA PIN”. When the user receives the OTA settings message, they will need to supply this PIN code in order to be able to open the message and apply the settings.
- “Network PIN” (NETWPIN) indicates the PIN is a network PIN code. In the GSM environment, this is the IMSI number associated with the SIM card in the device. (Hint, if you want to experiment with determining the PIN card associated with a SIM, you can put the SIM into a GSM modem and the AT+CIMI command to return the IMSI. However, not all GSM modems support the AT+CIMI command.) When the device receives the settings, if the NETWPIN does not match the IMSI, the settings will be discarded.
- An additional type of PIN, known as “USERNETWPIN” also exists, which indicates a combination of the USERPIN and NETWPIN types. To use this OTA PIN type, select “Network PIN”, and define the OTA PIN as the IMSI number associated with the SIM card in the device, followed by a “:” character, followed by a USERPIN (e.g., 1234567889012345:1234). When the device receives the settings, the user will be prompted for a PIN. This user supplied PIN, and the SIM card IMSI, must match in order for the settings to be accepted.
Use the “Submit” button to send the settings, or use the “View XML” button to view the XML settings that are generated by this web form.
WAP OTA: Wireless Village/ IMPS Settings
“Phone Number to Receive Settings” is a comma delimited list of one or more phone numbers to receive the settings via SMS.
“Settings Name” is a descriptive name for the settings that may be displayed on the mobile phone.
“IMPS Server URL” is the HTTP URL associated with the Wireless Village/IMPS server.
“IMPS User Name” and “IMPS Password” define the user name and password for logging into the Wireless Village/IMPS Server.
Send WAP OTA Settings
The “Data Connection Profile” setting refers to an existing data connection profile that should exist on the device (e.g., the “Settings Name” associated with OTA settings for a browser connection settings message that was previously sent to the device).
“OTA PIN” and “OTA PIN Type” are optional parameters supported for IMPS settings over WAP OTA, but that are commonly used in OMA OTA requests.
An “OTA PIN” can be associated with an OTA settings message to provide a layer of authentication to the message. Many devices will allow you to send OTA settings without a PIN, but some will require a PIN to be present before the settings will be accepted.
There are three different types of OTA PINs, depending on the “OTA PIN Type” setting.
- The simplest “OTA PIN Type” is “User PIN” (USERPIN). This setting indicates that a short PIN code (often 4 digits) is supplied as the “OTA PIN”. When the user receives the OTA settings message, they will need to supply this PIN code in order to be able to open the message and apply the settings.
- “Network PIN” (NETWPIN) indicates the PIN is a network PIN code. In the GSM environment, this is the IMSI number associated with the SIM card in the device. (Hint, if you want to experiment with determining the PIN card associated with a SIM, you can put the SIM into a GSM modem and the AT+CIMI command to return the IMSI. However, not all GSM modems support the AT+CIMI command.) When the device receives the settings, if the NETWPIN does not match the IMSI, the settings will be discarded.
- An additional type of PIN, known as “USERNETWPIN” also exists, which indicates a combination of the USERPIN and NETWPIN types. To use this OTA PIN type, select “Network PIN”, and define the OTA PIN as the IMSI number associated with the SIM card in the device, followed by a “:” character, followed by a USERPIN (e.g., 1234567889012345:1234). When the device receives the settings, the user will be prompted for a PIN. This user supplied PIN, and the SIM card IMSI, must match in order for the settings to be accepted.
Use the “Submit” button to send the settings, or use the “View XML” button to view the XML settings that are generated by this web form.
.png)
No comments:
Post a Comment