I am using mbuni as MMS gateway which uses Kannel GWLIB & WAP libraries. I am facing some problem. When MMS gateway send MMS message with SMIL attachment to MMSC in the SOAP submit request it sends following content type
Content-Type: multipart/related; type=application/smil; start="<presentation>"; boundary=_boundary_551921173_1162288522_B_x_bd316408487
From mbuni mailing lists I confirmed that this is being done by using Kannel. As per my understanding from RFC standards the application/smil should be in qouted strings. For example;
Content-Type: multipart/related; type="application/smil"; start="<presentation>"; boundary=_boundary_551921173_1162288522_B_x_bd316408487
Please take a look into the rfc 2045 section 5 . (
http://www.ietf.org/rfc/rfc2045.txt)
Content-Type Header Field. If I understand
correctly the parameter value must be quoted in cases the parameter is having tspecials characters.
content := "Content-Type" ":" type "/" subtype
*(";" parameter); Matching of media type and subtype
; is ALWAYS case-insensitive.
type := discrete-type / composite-type
discrete-type := "text" / "image" / "audio" / "video" /
"application" / extension-token
composite-type := "message" / "multipart" / extension-token
extension-token := ietf-token / x-token
ietf-token := <An extension token defined by a
standards-track RFC and registered with IANA.>
x-token := <The two characters "X-" or "x-" followed, with no intervening white space, by any token>
subtype := extension-token / iana-token
iana-token := <A publicly-defined extension token. Tokens
of this form must be registered with IANA as specified in RFC 2048.>
parameter := attribute "=" value
attribute := token ; Matching of attributes
; is ALWAYS case-insensitive.
value := token / quoted-string
token := 1*<any (US-ASCII) CHAR except SPACE, CTLs, or tspecials>
tspecials := "(" / ")" / "<" / ">" / "@" /
"," / ";" / ":" / "\" / <">
"/" / "[" / "]" / "?" / "="
; Must be in quoted-string, ; to use within parameter values
Note that the definition of "tspecials" is the same as the RFC 822 definition of "specials" with the addition of the three characters
"/", "?", and "=", and the removal of ".".
So in case the value is having tspecials characters it must be in quoted-string.
So Kannel should add qouted strings. Please correct me if my understanding is wrong. If the above mentioned information is correct than modify it in current CVS. I would highly appreciate it.
Hope to listen form someone soon. Thanks in advance
