Signals
| IMSIChanged | (s: IMSI) |
Properties
| MessageValidityPeriod | u | Read/Write | ||
| OverrideMessageServiceCentre | b | Read/Write | ||
| MessageServiceCentre | s | Read/Write | ||
| IMSI | s | Read only | ||
| MessageReducedCharacterSet | b | Read/Write | ||
| MessageNationalCharacterSet | s | Read/Write |
Description
This interface is for various cellular things (GSM and/or CDMA) that aren't really applicable to other protocols.
Signals
IMSIChanged (s: IMSI)
Parameters
- IMSI — s
Properties
MessageValidityPeriod — u
Note: Connections implementing this property SHOULD provide a corresponding parameter named org.freedesktop.Telepathy.Connection.Interface.Cellular.MessageValidityPeriod with the DBus_Property flag. Clients SHOULD update this property by calling UpdateParameters on the relevant Account rather than setting the property directly; change notification is via AccountPropertyChanged.
Define how long should the service centre try message delivery before giving up, failing delivery and deleting the message. A value of 0 means to use the service centre's default period.
The value specified is in seconds. Note that various protocols or implementations may round the value up (eg. to a minute or hour precision). The maximum validity period may vary depending on protocol or provider.
OverrideMessageServiceCentre — b
Note: Connections implementing this property SHOULD provide a corresponding parameter named org.freedesktop.Telepathy.Connection.Interface.Cellular.OverrideMessageServiceCentre with the DBus_Property flag. Clients SHOULD update this property by calling UpdateParameters on the relevant Account rather than setting the property directly; change notification is via AccountPropertyChanged.
If True, SMSes will be sent via the service centre
specified by MessageServiceCentre. If
False, the SIM's default SMSC will be used, ignoring the
value of MessageServiceCentre.
Rationale:
It could be desirable for a configuration interface to remember the user's previous choice of custom SMSC, even if it's not in use. This boolean allows that choice to be saved as an account parameter by Mission Control, rather than the UI needing to save it elsewhere to be restored if the user wants to reactivate it.
MessageServiceCentre — s
True.Note: Connections implementing this property SHOULD provide a corresponding parameter named org.freedesktop.Telepathy.Connection.Interface.Cellular.MessageServiceCentre with the DBus_Property flag. Clients SHOULD update this property by calling UpdateParameters on the relevant Account rather than setting the property directly; change notification is via AccountPropertyChanged.
Address for the messaging service centre. Typically (as is the case
for GSM's SMSC), it's the ISDN / telephony address (ie. a phone
number). If
OverrideMessageServiceCentre is
False, this property's value should be ignored by the CM
in favour of the SIM's default SMSC.
IMSI — s
The International Mobile Subscriber Identifier, if it exists. This would originate from a SIM card. If the IMSI is unknown, this will contain an empty string ("").
MessageReducedCharacterSet — b
Note: Connections implementing this property SHOULD provide a corresponding parameter named org.freedesktop.Telepathy.Connection.Interface.Cellular.MessageReducedCharacterSet with the DBus_Property flag. Clients SHOULD update this property by calling UpdateParameters on the relevant Account rather than setting the property directly; change notification is via AccountPropertyChanged.
Determines how to encode SMSes containing characters that do not
fit into a non-Unicode character set.
If False (which SHOULD be the default), messages will
be encoded as UCS-2 and sent with no loss of fidelity (at the
potential financial cost of using twice as many SMSes); if
True, the message will be recoded in an
implementation‐specific way to fit into a GSM reduced character
set.
MessageNationalCharacterSet — s
Note: Connections implementing this property SHOULD provide a corresponding parameter named org.freedesktop.Telepathy.Connection.Interface.Cellular.MessageNationalCharacterSet with the DBus_Property flag. Clients SHOULD update this property by calling UpdateParameters on the relevant Account rather than setting the property directly; change notification is via AccountPropertyChanged.
Hint for the connection manager for the GSM character set that
should be used to send SMSes. The connection manager SHOULD follow
this hint unless it has other ways to determine a better encoding.
If the value is "gsm" (which SHOULD be the default),
SMSes will be encoded in the normal 7-bit GSM character set,
eventually falling back to UCS-2; see the
MessageReducedCharacterSet property
for details.
Other valid character sets are specified in the
GSM standard and are, for instance, "turkey",
"spain" or "portugal".
If the SMS cannot be encoded using the requested character set the
behaviour is implementation-specific, but it is RECOMMENDED that
the connection manager should behave as if this property was set
to "gsm".