Hi, all: We are using ofono to send sms with validity period and message class in our project. but by checking source code, it seems ofono doesn't support these requirements. Current implemntation is the dbus interface "SendMessage" contains "To" and "Text" only. Does oFono plan to support these extra fields when sending sms?

-----Original Message----- From: Rajesh.Nagaiah(a)elektrobit.com [mailto:Rajesh.Nagaiah@elektrobit.com] Sent: 2010?10?29? 18:09 To: ofono(a)ofono.org Subject: RE: oFono SMS Validity Period and Message Class support Hi, > Hi, all: > > We are using ofono to send sms with validity period and message class > in our project. > but by checking source code, it seems ofono doesn't support > these requirements. > > Current implemntation is the dbus interface "SendMessage" > contains "To" and "Text" only. > > Does oFono plan to support these extra fields when sending sms? > Right now oFono uses hardcoded Relative validity period of value 167 (24hrs: 12hrs +(167-143)x30mins)for SUBMIT message. If later supported then the Validity period should be part of the SMS app settings and the setting changes will trigger the property change in the org.ofono.MessageManager interface. But currently Validity Period property is missing in org.ofono.MessageManager interface. So it doesnt need to be part of the SendMessage dbus interface ? Regarding the message class, none of the UE usually gives the a user setting for message class for outgoing SMS. So oFono uses unspecified message class and it sets only the encoding type (GSM 7bit or UCS2) in the DCS byte for the SUBMIT message. For the SMS DELIVER it decodes the Message class and handles it accordingly (Note: Class 2 messages are not supported in oFono) BR, Rajesh