Topics | Functions | Macros | Structs, Records, Enums | Types

Provides functions to send, read, delete, cancel the SMS messages.


An application can use vm_gsm_sms_send() to send a SMS message, or use the use vm_gsm_sms_cancel_send() to cancel a pending message to be sent. It can also reads a SMS message by calling vm_gsm_sms_read_message(), and delete a message with vm_gsm_sms_delete_message(). It can delete all messages from a specific message inbox by calling vm_gsm_sms_delete_message_list(). 

An application can get the SMS Center Address through the vm_gsm_sms_get_center_address() asynchronously via a callback, or through the vm_gsm_sms_get_center_address_sync() synchronously.



Saves a new message to SMS Storage. If the caller specifies those parameters (Status, Address, Content, SIM Card, Storage Type, Profile element), they will be used. Otherwise, it will use the default values (If the parameters are in the SMS setting, it will use them as default). The Callback Action Data Struct is vm_gsm_sms_save_message_callback_t
Cancels sending SMS. The function can be used only after vm_gsm_sms_send() has been invoked and it returns TRUE, and before the corresponding callback is invoked. Otherwise, calling this function is invalid. 
Clears the interrupt handler for the specified event type. 
Deletes an existing message as specified by message ID. The Callback Action Data Structure is vm_gsm_sms_delete_message_callback_t
Deletes all the existing messages in the specified message box, e.g. Inbox, Outbox, etc. The Callback Action Data Structure is vm_gsm_sms_delete_message_list_callback_t
Gets number of the messages in a box list 
Asynchronously gets center address of the SIM for SMS, which is a phone number. 
Synchronously gets center address of the SIM for SMS, which is a phone number. 
Gets the message ID of the message in the box, as specified by message_index. 
Gets the message ID list of the messages on the device through the query. The query attributes are specified in query_data. The message ID list is obtained through the callback, vm_gsm_sms_callback(), which takes vm_gsm_sms_callback_t with vm_gsm_sms_query_message_callback_t as action_data that contains the result of the query. 
Checks if the SMS message is ready. 
Reads message data, including message status, number, content and other attributes (Storage Type, SIM Card, Profile element, etc.) specified by the flag. The buffer to save the content should be provided by the caller. The Callback Action Data Structure is vm_gsm_sms_read_message_data_callback_t
Sends SMS 
Sets the interrupt handler for the specified event type. 
The maximum length of SMS message address. 
The maximum length of SMS message content. 
Structs, Records, Enums
Struct, Record, Enum 
SMS Action Type. 
Add Message Data Structure. 
SMS Box type. 
SMS Operation Callback Data Structure. 
SMS Cause. 
Message Class Type. 
SMS DCS(Data Coding Scheme). 
Delete Message - Callback Data Structure. 
Delete Message List - Callback Data Structure. 
SMS new message event type. 
Message New SMS Interrupt Event - Callback Data Structure. 
SMS ready message struct 
SMS Event Structure. 
Message Folder type. 
Gets SMS center number - Callback Data Structure 
Message Type Indication. 
Network type. 
New Message Data Structure. 
SMS Sorting Order. 
SMS Parameter Flag. 
Protocol Identifier 
Query Message - Callback Data Structure. 
Query Data Structure. 
Read Message - Callback Data Structure. 
Message Data Structure. 
SMS request results. 
Add Message - Callback Data Structure. 
The results of SMS send
SIM Card Type 
SMS Sort Type. 
Message Status. 
Message Storage Type 
Validity period. 
SMS operation callback function. 
SMS event callback function. 
Created with a commercial version of Doc-O-Matic. In order to make this message disappear you need to register this software. If you have problems registering this software please contact us at