151
151
status reports are received, the UI is notified either via DBus or history
154
- Source / Destination port addressing scheme from 3GPP 23.040. A special
155
header is used to indicate the source / destination port of the application
156
this SMS message belongs to. oFono provides a handler registration
157
framework where plugins can handle the reception of such messages. The
158
handler can be registered to receive messages which contain a specific
159
source and destination port, or a wildcard. When such messages are received,
160
they are matched against the registered handlers and dispatched appropriately.
162
oFono takes care of de-fragmentation of such SMS messages, so the handler
163
is informed only once the entire message has been received, and the data
164
payload has been extracted.
166
- Smart Messaging Service - vCard support. oFono provides the ability to send
167
and receive vCard objects through the SmartMessaging interface. vCards can
168
be sent using the SendBusinessCard method and received using the
169
SmartMessagingAgent framework.
171
- Smart Messaging Service - vCalendar support. oFono provides the ability to
172
send and receive vCalendar objects through the SmartMessaging interface.
173
vCalendars can be sent using the SendAppointment method and received using
174
the SmartMessagingAgent framework.
176
- WAP PUSH notification support. oFono allows the reception of WAP PUSH
177
messages via SMS through the use of the PushNotification interface and the
178
PushNotificationAgent framework.