CVS has been updated as requested below. The key changes are:
Each VASP (from the MMSC point of view) has two extra flags: mms-to-
email-handler if set causes all mms2email to be routed via the VASP
account (using MM7 SOAP or EAIF) instead of via SMTP. mms-to-local-
copy-handler if set causes Mbuni to send a copy of each incoming
local messages to the VASP, before sending out a notification to the
user.
Carefully used, these changes should provide what you need.
cheers
P.
On Oct 19, 2005, at 19:00, Nicolas Zielinski wrote:
It looks to me like you have Mbuni MMSC and Mbuni VAS GW both
running.
Indeed ;)
There is a problem, you are right, but a different kind of problem:
The MMSC currently sends all messages destined to email addresses
directly to the SMTP server. Should it have an option to re-direct
this to a VAS? It is easy to do, I just need to understand if we
should be doing it...
For instance, a MVNO which holds several mobile brands and who
wants to use
one MMSC for all brands. Then, when a user sends a MMS2Email, it
would be
cool to customize the e-mail in function of the sender (for example in
adding the brand logo in the message).
But maybe it doesn't exactly fit with the VASP concept...
BTW, I've found a little bug, mmsproxy doesn't close anymore when I
use
start-stop-daemon, I have to use kill -9 pid instead.
NZ.
On Oct 19, 2005, at 16:08, Nicolas Zielinski wrote:
Mmsbox is running but I didn't test if it can receive messages...
The log doesn't say anything special, the MMS arrives to mbuni, and
then a
SMS or a mail is sent, but the mms-service is not called...
By the way I'm not clear with the expected message routing, could
you tell
me if I'm wrong :
MMS - Mbuni - MMS-Service - VASP - SendMMS - SMS/Mail ?
And currently I think it's doing this :
MMS - Mbuni - SMS/mail
-Message d'origine-
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la
part de
Paul Bagyenda
Envoye : mercredi 19 octobre 2005 12:26
A : Mbuni MMS Gateway Developers
Objet : Re: [Devel] Mbuni as VAS GW (documentation updated)
And mmsbox is running and receiving messages via MM7? What does the
log say?
Keep in mind that mmsbox is not part of the MMSC. It is a separate
app even though it shares code.
P.
On Oct 19, 2005, at 12:29, Nicolas Zielinski wrote:
Hi Paul,
Not at the moment. But you could certainly implement your own VASP
URL that receives the MMS and does the necessary re-formatting
before
sending out to email. This is the beauty of the new additions.
I tried to do that, in using a mms-service with the catch-all
option, but it
seems that it's never called.
I just added this to my conf file, maybe I forgot something :
--
group = send-mms-user
username = pass
password = pass
group = mmsc
id = vas_gw
mmsc-url = http://localhost:1981/
# mmsc-url = http://localhost:8080/vasp/servlet/messagerouter
incoming-username = pass
incoming-password = pass
incoming-port = 10002
type = soap
group = mms-service
name = main
catch-all = true
post-url = http://localhost/mms/vasp.php
http-post-parameters =
images[]=%itext[]=%tsmil[]=%sbinary[]=%bparts[]=%z
accept-x-mbuni-headers = true
keyword = all
assume-plain-text = true
-Message d'origine-
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la
part de
Paul Bagyenda
Envoye : mardi 18 octobre 2005 17:14
A : Mbuni MMS Gateway Developers
Objet : Re: [Devel] Mbuni as VAS GW (documentation updated)
Hi Nicolas, some answers below
On Oct 18, 2005, at 16:15, Nicolas Zielinski wrote:
Hey, these changes seem to be great :)
receive MMS and based on the text in the MMS
decide which URL to call, script to execute, or file to load to
get
the content to send back.
Is it possible to use this function with the MMS2Email feature ?
Not at the moment. But you could certainly implement your own VASP
URL that receives the MMS and does the necessary re-formatting
before
sending out to email. This is the beauty of the new additions.
For instance, I would like to adapt the content of a MMS2Mail
before sending
it (depending on the recipient address for example). Is it possible
to do
this ?
Another question about MM7 : what is the structure of the SOAP
message that
a VASP should send to mbuni ?
As documented, the VASP sends Mbuni either a SMIL file or some
content (e.g. image, audio). If you send Mbuni a SMIL, it examines
it, fetches all the referenced content (relative to the query URL if
need be) and packs the result together as an MM. If you send Mbuni
some other type of content, it packs it as-is into a message (this
means you can also send Mbuni a binary message).
Thanks.
Nicolas.
-Message d'origine-
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la
part de
Paul Bagyenda
Envoye : lundi 17 octobre 2005 19:22
A : Mbuni MMS Gateway Developers
Objet : [Devel] Mbuni as VAS GW (documentation updated)
Hello All,
If you've been watching CVS you've
