White Paper K310
34 February 2006
The user can insert multimedia elements into
multimedia messages from:
• File Manager
•Camera
• Contacts
•Calendar
• Web browser
• Java™ applications
Possibility for sent messages to be
memorized into a folder in the phone
memory
Yes
Actions that the user can perform after
message notification:
•Auto Download
•Always Ask
• Ask in roaming
• Not in roaming
•Off
Actions that the user can perform after
message retrieval:
• reply to the sender of the message SMS/MMS/Voice
message
• reply to the sender and to Cc people MMS/Voice mes-
sage
• reply to the sender and to Bcc people MMS/Voice mes-
sage
• forward the message MMS
• delete the message
• save message in the phone memory
• call the sender of a message
• view details
• save items
• mark as unread
Multimedia codecs/formats supported for
audio
AMR, MP3, 3GP and WAV.
Multimedia codecs/formats supported for
video
3GPP™, SDP
Multimedia codecs/formats supported for
image
JPEG, GIF87, GIF89A, WBMP, BMP and PNG
Supported formats for message
presentation:
• message body + attachments (email presentation)
• SMIL version as described in OMA MMS IOP docu-
ment version 1.2
Maximum message size that can be handled
by the phone for message
Content Class and Creation mode are applied. Also
maximum size is possible to customize.
MMS User Agent will report problems to user
in case of:
• message not sent causes no user subscription to serv-
ice, if included in ResponseText (please see WAP209).
• message not sent causes required functionality not
supported by MMS Relay/Server, if included in
ResponseText (please see WAP209).
• message not sent causes insufficient credit (in case of
prepaid charging), if included in ResponseText (please
see WAP209).
Feature Support