The global settings that are applied to SMS MTM are known as the SMS service settings. Each SMS message entry has its own individual group of settings known as SMS message settings.
An SMS service entry contains the following two types of settings that are handled through member functions of CSmsSettings:
General settings for sending and retrieving SMS messages.
Default settings applied to new outgoing messages.
Clients must use the set of CSmsSettings member functions. SMS settings can hold a configuration for one or more SMS service centres. The SMS service centre details are encapsulated in CSmsServiceCenter objects, and the functions access these objects. An SMS service is stored as a message entry with the characteristics that are be set by the MTM for an SMS service.
Settings such as reply options, alert on delivery, language indicator and so on are set on a new message from the defaults for message settings specified in the SMS service.
| Setting | Description |
|---|---|
Add or remove service centre to the list of service centres |
The SMS service settings maintain a list of service centres. The default service centre used to send SMS messages to be set from this list. |
Set default service centre |
The set the default service centre to which SMS messages are sent is from the list of service centres. |
Delivery scheduling |
The SMS plug-in supports sending an SMS message at a scheduled time, upon request or when other SMS messages are being sent. |
Quoted reply |
A reply message to a received SMS message may contain the body of the original message. |
Status report handling |
Received status reports may be stored as an invisible or visible message in the global inbox or they may be discarded altogether. Along with each of these storage options status reports may be optionally matched to the message that they refer to. The message is updated to reflect the delivery status. The SMS plug-in may also be configured to not receive the status reports at all from the SMS Stack. |
Special message handling |
Received special messages may be stored as an invisible or visible message in the global inbox, or they may be discarded altogether. The SMS plug-in may also be configured to not receive these messages at all from the SMS Stack. |
Store service centre information in the Comms database. |
This option allows the default service centre and the validity period to be stored in the Comms database when the SMS service settings are stored in the Message Store. |
Store bearer information in the Comms database. |
This option allows the current bearer information to be stored in the Comms database when the SMS service settings are stored in the Message Store. |
Bearer setting |
The bearer setting allows the selection of the underlying data layer. A packet or circuit switch data layer may be either mandated or preferred. |
Class 2 folder |
The location of the class 2 folder is configurable. It may set to be the global inbox. |
Each SMS message has a Message Store index entry that can be accessed through TMsvEntry. The index entry allows an application quick access to important properties of a message. See TMsvEntry for detailed information on the functions and member variables of that can be set by the SMS MTM.
| Setting | Description |
|---|---|
Validity period |
The message validity period indicates how long a sent message may remain in the service centre pending deliver to the recipient. |
Duplicate handling |
Duplicate messages that are received may be rejected. |
Delivery report |
A delivery report may be requested when sending a message. |
Reply path |
Specifies if SMS messages must be sent with the reply path set. The reply path is the service centre to which replies to the sent SMS message can be sent to. |
Message conversion |
Defines the conversion set which the message must be encoded as when sent over the air. The conversion sets are not defined by the SMS plug-in. |
Concatenation |
This setting indicates whether the message can be concatenated into more than one SMS PDU. |
Character set |
The character set of the SMS message can be configured. The supported char sets are not defined by the SMS plug-in. |
Copyright ©2010 Nokia Corporation and/or its subsidiary(-ies).
All rights
reserved. Unless otherwise stated, these materials are provided under the terms of the Eclipse Public License
v1.0.