Jovan,
Answers in line.
On Apr 21, 2008, at 02:11, Jovan Kostovski wrote:
Hi Paul,
I have some post-url related questions:
1. When post-url is used to save MMS contents or generate the response
MMS and suppress-reply = false (or it's not
present) Mbuni does not check the validity of the MMS contents. I've
tested with Sony Ericsson and Nokia phones. If
the post-url does not return anything (any contents of the MMS) on SE
I get empty response MMS with an attached file which is
empty and the Nokia phones show error message that the contents of the
MMS are invalid. If the url defined in post url exits with
an error the debug information is sent as an attached text file (see
mms_22.log) . This is a god feature for debugging, but it's not good
for the end user ;)
If the post-url doesn't return any contents and supress-reply = true
everything's fine.
What happens if I want to return MMS which contains for example, text,
image and audio and is defined by the smil returned by the post-url
and some of the data files can not be fetched? Will Mbuni send only
the correctly fetched data files or will send all fetched data
which will end as a bad formatted MMS?
The best way to do this is to return a SMIL file (content type must of
course be set to application/smil) that references the parts you want
to add. Mbuni will automatically build the MMS out of the SMIL and the
referenced content.
2. In the MMS Service Configuration exampleexample in the
documentation there is a
parameter fx=true in the post-url: http-post-parameters =
fx=true&images[]=%i&text[]=%t
What's the use of it? It's static and it always has the value. Extra
parameter that will
be send to the MMSC when sending the MMS or extra parameter sent to
the post-url?
If its for the post-url I don't see any use of it except in case where
there is one same post-url
handler for more than one mms service.
That extra fx=true was only for illustrative purposes and has no use
really in this case.
3. I tried to get the sender, receiver and the subject of the MMS.
I've checked the X-MBUNI headers
and the only one that I could get are: HTTP_X_MBUNI_MESSAGE_ID,
HTTP_X_MBUNI_MMSC_ID,
HTTP_X_MBUNI_FROM, HTTP_X_MBUNI_SUBJECT, HTTP_X_MBUNI_TRANSACTIONID
and
HTTP_X_MBUNI_TO.
I've checked the logs and I found no other X-MBUNI headers. I guess
the headers whose values have not been set are not sent, right?
No data for the other parameters is sent from the MMSC or Mbuni
doesn't process the data?
Correct
What's casing the warning:
2008-04-17 13:54:06 [23803] [0] WARNING: mms_queueread: Mal-formed
address [+xxxxxxxxxxxxxxxx] in file
/home/storage/mbuni/mmsbox_incoming/qf3244.1.x803.92! Attempting
fixup.
line 80 in receive-mmsgw.log
This means that the sender/receiver number does not have a correct
format. Usually Mbuni is able to correct it.
I have another major problem:
I can not send MMS via Mbuni cgi interface ( Mbuni -> MMSC)
I compiled mbuni CVS with kannel CVS without applying extra pathes.
The receiving of the MMS works fine (MMSC->Mbuni) but when I try to
send
MMS (Mbuni -> MMSC) via the cgi interface I'm getting a reply with
HTTP error code 400 from the MMSC (see the log send-mmsgw.log).
The MMSC is Nokia.
The MMSC does not have a CGI interface for sending mms. Use the
command line mmssend tool instead.
I've contacted my service provider (the mobile operator) to see whats
going wrong
on the MMSC and they gave me the following log lines:
Content-Type: application/vnd.wap.multipart.related;
Type="application/smil"; Start="<presentation>"
Missing mandatory header(s) in message type: m-send-req
HTTPServerHandler->SendResponse()
HTTP-> HTTP/1.1 400 Message Validation Failed
The thing that confuses me is that when Mbuni receives a MMS
(MMSC->Mbuni) and then sends a response message
(Mbuni->MMSC) the response message is sent correctly...
I found a forum discussion [1] in which you say that you've posted a
patch in the CVS but I couldn't find any patch.
Is the CVS code patched with the mentioned patch? If not, where can I
find this patch?
[1] http://www.mail-archive.com/[email protected]/msg00614.html
Yes the fix is on CVS, try that and advise. We will shortly put out a
new release that should fix these issues.
BR, Jovan
<mmsbox.conf><keyword_bouncer.php><mms_22.log><receive-
mmsgw.log><send-mmsgw.log>
_______________________________________________
Users mailing list
[email protected]
http://lists.mbuni.org/mailman/listinfo/users
