All looks fine for now, except for one thing: You are providing a POST parameter *value* but no field name. You should do something like http-post-parameters = elements[]=%zOn May 29, 2006, at 10:43, kartikay malhotra wrote:Thanks again. I'm using 2 conf. files. The first is for mmsc (mmsc1.conf)-group=core ..group=mbuni .. group = mms-vasp vasp-id = newscorptype = eaif short-code = 111 vasp-username = newscorpvasp-password = news123 vasp-url = "" href="http://107.108.89.158:23535/">http://107.108.89.158:23535/ mmsc-username = user mmsc-password = secretThe second is for VASP (mmsc2.conf)- group=core .. group=mbuni ..group = mmsc id = testonemmsc-url = "" href="http://107.108.89.158:1982/mm7?username=newscorp=news123">http://107.108.89.158:1982/mm7?username=newscorppassword=news123 incoming-username = newscorp incoming-password = news123incoming-port = 10002 type = eaifgroup = mms-service name = fullmessagepost-url = ""http://107.108.89.158/mms/2.php"> http://107.108.89.158/mms/2.php"http-post-parameters = %z catch-all = trueaccept-x-mbuni-headers = true keyword = wwwI now run mmsrelay, mmsproxy with the 1st conf file and mmsbox with the secondFinally I fire - mmssend -f 100/TYPE=PLMN -t 111/TYPE=PLMN -m abc.mms mmsc2.confwhich yields:Queued: y-qf1148907236.1.x806.509, mmbox=2006-05-29 12:53:56 [6806] [0] DEBUG: Immutable octet strings: 701.I get in mmsrelay:2006-05-29 12:56:42 [6638] [7] INFO: Sent to VASP[newscorp], code=[200] 2006-05-29 12:56:42 [6638] [7] INFO: Sent Global Queue MMS Send: From 100/TYPE=PLMN, to 111/TYPE=PLMN, msgsize=18465: err=(null)I want to send this mms (abc.mms) to a PHP script running on a HTTP server provided the keyword in text part of MMS is "www". I think I'm doing something wrong with http-post-parameters. Please advise. GratefulKMP.S. I sent you two (Paul) JPEG files (showing Mbuni architecture) based on my understanding. Could you please validate those.On 5/17/06, Paul Bagyenda [EMAIL PROTECTED] wrote: Ok I may not be able to offer a config for now (bit busy), but will provide some guidelines, and you can start with the sample config and modify to suit your needs.First you want a sort of 'fake mmsc'. For this, just use the sample config. It defines a VASP called "newscorp", who is on short code 111. This is the one you will connect to. Run the mmsc thus: mmsrelay conf_file mmsproxy conf_file This will start the Mbuni MMSC. Now make a slightly different config file, this time to run Mbuni as VAS GW, connecting to the MMSC just started. Things to do:- Define the core config (should be largely as before) - Define an MMC group and put in the mmsc group with the mmsc url as http://localhost:1982/mm7?username=newscorppassword=news123 -- i.e. you are telling your VASP setup to connect to the local MMSC on port 1982, to use user/pass newscorp/news123.- Define an mms-service (the one that will call the url when it receives a messages from mmsbox). You should probably set the catch-all flag to true Now start mmsbox as mmsbox conf_fileFinally, call the mmssend command of the MMSC to send an mms into the MMSC. Do this: mmssend -f 100/TYPE=PLMN -t 111/TYPE=PLMN -m file.mms conf_fileThis will: - Send the mms file to the local MMSC - When the MMSC receives the file it will send it to mmsbox since mmsbox is listed as handling all incoming messages to short code 111 - mmsbox on receiving the message will call the mms-service you will have defined.That should do the trick.Let me know if you need more help. On May 17, 2006, at 08:39, kartikay malhotra wrote:Forgot to add:I am not bothered about sending mms. I only with to receive it. Also, while faking mms, do I submit a .mms file to Mbuni, or a SMIL file? ThanksKM-- Forwarded message -- From: kartikay malhotra [EMAIL PROTECTED]Date: May 17, 2006 5:07 AMSubject: Re: [Users] mbuni.conf + fake mms ? MMS fileTo: Paul Bagyenda [EMAIL PROTECTED]Hi Paul, Thanks. Things are more clear now. However, there is still some confusion. So I'll explain my immediate needs. I wish to send a sample (fake) mms to Mbuni. I want Mbuni gateway to forward it to a HTTP (apache) server. On the server I run a PHP script to receive the MMS and dump it in a MySQL database. This is exactly what I did for SMS (using Kannel). Since this is proof of concept, I do not bother about any authenticationlocal-prefixes, allowed or denied IP addresses, etc. For kannel my conf file was: group = core admin-port = 13000 smsbox-port = 13001 admin-password = bar # SMSC CONNECTIONS group = smsc smsc = fake smsc-id = FAKE port = 1 # SMSBOX SETUP group = smsbox bearerbox-host = localhost sendsms-port = 13013 global-sender = 13013 access-log = "/tmp/access.log" # SEND-SMS USERS group = sendsms-user username = tester password = foobar # SERVICES group=sms-service keyword=www get-url=""http://107.108.89.158/script.php?sms=%25a" target="_blank" > http://107.108.89.158/script.php?sms=%a" And after running bearerbox and smsbox in
