Mbuni generally does not care about the file types, except in a few
cases:
- As MMSC, before sending the MMS to the phone, provided content
adaptation is turned on, Mbuni attempts to transform certain content
types to more acceptable types for the phone, based on its advertised
profile (UAProf). This is only done for common image and audio types,
and is also done for different character sets.
- For The VAS Gateway, no transcoding is done. You can however install
a custom filter module (see mt-filter parameters) that transforms/
filters messages prior to their being sent out. This is precisely how
the DRM module is implemented.
On Jul 03, 2008, at 06:47, Willis Vandevanter wrote:
I have a few questions regarding file type restrictions with Mbuni.
- Can I configure Mbuni to only allow specific file types within
MMs? Do they have to be specified in 3GPP 26.14 or can I configure
Mbuni for any file type?.
- Does Mbuni verify the file matches it's declared MIME type? Can I
configure it do so?
- What happens if a user sends a file type that Mbuni is not
configured for? The Documentation mentions defaulting to application/
octet-stream.
- What if the SMIL code includes references to an both supported
and unsupported file type in the same MM?
- Does Mbuni attempt to perform terminal capability negotiation
with the receiving terminal if the file is not listed as a supported
file type or does it forward it directly to the receiver?
Thank you for your help.
- Willis
_______________________________________________
Users mailing list
[email protected]
http://lists.mbuni.org/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.mbuni.org/mailman/listinfo/users
