Re: [Users] Help with Mbuni VASGW administration Interfaces
Hi, That measure is for PDUs sent, which includes delivery reports and such. The interface does not (yet) make a distinction between the different types of PDUs On Feb 09, 2009, at 16:11, hafez ahmad wrote: Dears, When I use the admin http interface and I get the following groupmmc1/group throughput0./throughput re-routefalse/re-route reroute-mmscN/A/reroute-mmsc stats uptime47 days 18 hrs 39 mins 34 secs/uptime last-pdu02/09/09 15:06:07/last-pdu mtpdus6754/pduserrors838/errors/mt mopdus0/pduserrors0/errors/mo /stats is that mean that I have 6754 queued MMS or sent 6754 MMS or ? Regards, Hafez On Mon, Dec 22, 2008 at 3:22 PM, Paul Bagyenda bagye...@dsmagic.com wrote: Use: http://localhost:8100/status?password=mypass The command is the URI On Dec 22, 2008, at 12:36, hafez ahmad wrote: this one :) curl http://localhost:8100/?password=mypasscommand=status; regards, Hafez On Mon, Dec 22, 2008 at 11:28 AM, Paul Bagyenda bagye...@dsmagic.com wrote: What is the exact URL you used? On Dec 22, 2008, at 11:18, hafez ahmad wrote: Dear P.A, I tried the following and I get the following out when I request the status: ?xml version='1.0'? mmsbox /mmsbox and I have 3 active connection, any Ideas please ? Regards, Hafez On Tue, Sep 2, 2008 at 1:45 PM, P. A. Bagyenda bagye...@dsmagic.com wrote: CVS now has the beginnings of the HTTP admin interface. No documentation updates yet, alas, but that should change over the coming hours. Briefly, you need to add the following config params to your mbuni conf group: mmsbox-admin-port = port_no admin-password = password admin-port-ssl = one_of_true_or_false You should then be able to access the HTTP admin port using http(s)://mbuni-host:port/?password=passwordcommand=cmdmmsc- id=mmsc In each case the HTTP response is XML formatted. The parameter 'cmd' is one of: - status: This spits out the status of the mmsc connection provided (if none is provided then status information for all active mmsc connections is provided) - start: This starts the mmsc connection whose ID (in the conf file) matches that provided (if none is provided then all are started) - stop: This stops the mmsc connection whose ID matches that provided (if none is provided then all are stopped) Feedback is welcomed of course. You will also notice additional updates in the Changelog, particularly with respect to dynamic configuration of Mbuni. (These are documented.) Regards, Paul. On Aug 30, 2008, at 11:27, Mohammad Abu Karim wrote: Hi Guys. Kannel Has HTTP administration to administer the kannel to check status, shutdown ..etc. Does mbuni has such administration HTTP or command interface to administer it? If yes tell me please how to access it, and how I can check mbuni vasgw status. I mean how I can check the vasgw queue, the served MMSes, the filed delivered MMses and so on. Regards. Mohammad Abu-Karim ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users -- Hafez A.Ahmad Amman-Jordan mobile:962-785259011 962-795708728 http://blog.hafezadnan.com -- Hafez A.Ahmad Amman-Jordan mobile:962-785259011 962-795708728 http://blog.hafezadnan.com -- Hafez A.Ahmad Amman-Jordan mobile:962-785259011 962-795708728 http://blog.hafezadnan.com ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
[Users] Re: Problem with incoming MMS ...
One would need to look at a fully log... On Dec 04, 2008, at 15:54, Marcin Bockowski wrote: Hello, i've noticed problems with MMS incoming to application via EAIF. When message hits application error occurs: 2008-12-04 13:43:38 [25873] [12] PANIC: gwlib/octstr.c:2486: seems_valid_real: Assertion `ostr-data != NULL' failed. (Called from gwlib/octstr.c:324:octstr_destroy.) 2008-12-04 13:43:38 [25873] [12] PANIC: /srv/mbuni/bin/mmsbox(gw_panic+0x15a) [0x443caa] 2008-12-04 13:43:38 [25873] [12] PANIC: /srv/mbuni/bin/mmsbox [0x446830] 2008-12-04 13:43:38 [25873] [12] PANIC: /srv/mbuni/bin/mmsbox(octstr_destroy+0x1d) [0x44861d] 2008-12-04 13:43:38 [25873] [12] PANIC: /srv/mbuni/bin/mmsbox [0x418e9f] 2008-12-04 13:43:38 [25873] [12] PANIC: /srv/mbuni/bin/mmsbox [0x41b739] 2008-12-04 13:43:38 [25873] [12] PANIC: /srv/mbuni/bin/mmsbox [0x43aed5] 2008-12-04 13:43:38 [25873] [12] PANIC: /lib/libpthread.so.0 [0x2b3a94a3bf1a] 2008-12-04 13:43:38 [25873] [12] PANIC: /lib/libc.so.6(__clone+0x72) [0x2b3a951555d2] I use latest mbuni cvs version. What happens? Thanks, -- Marcin Boćkowski tel. +48 506 482 946 ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
[Users] Re: Problem with incoming MMS ...
Send at least 200 lines prior from the log file. It helps to have some context to the crash On Dec 04, 2008, at 16:17, Marcin Bockowski wrote: W dniu 4 grudnia 2008 14:07 użytkownik P. A. Bagyenda [EMAIL PROTECTED] napisał: One would need to look at a fully log... It's all what can i find in mmsbox log file :-/ I guess it was ok in 1.4.0 Regards, -- Marcin Boćkowski ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
[Users] Re: Sendmms validity ...
There isn't, but it is easy to add for anybody who cares to do so :) On Nov 25, 2008, at 16:20, Marcin Bockowski wrote: Hello, is there a validity parameter (like in Kannel) for sendmms script? Is there a chance to set message validity time somehow? Thx! -- Marcin http://www.ktosiu.com ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] Failed to parse MMSC
Sorry I misunderstood your error message. The problem is Mbuni does not understand the response. To understand why I'd need to look at a fuller log. Paul. On Oct 15, 2008, at 01:42, hafez ahmad wrote: Hi P.A, can you please explain more, Please find the attached conf file. Regards, Hafez On Tue, Oct 14, 2008 at 4:19 PM, P. A. Bagyenda [EMAIL PROTECTED] wrote: There is clearly a problem with your MMSC URL format, not with the MM7 packet format - this error shouldn't occur. So you will need to share your *actual* conf with a trusted party for further help :) P. On Oct 13, 2008, at 18:11, hafez ahmad wrote: Dears List, I trying to send MMS, the user received the MMS successfully, but I have the following error: 2008-10-13 17:35:54 [26658] [9] INFO: Retry later MMSBox Outgoing Queue MMS Send: From [EMAIL PROTECTED], to 967711593356/TYPE=PLMN, msgsize=25269: msgid=[(null)], err=Failed to parse MMSC[url=http://username:[EMAIL PROTECTED]:80/mm7tomms.sh , id=HouseID] response! and I catch the following XMl Response , ?xml version=1.0 encoding=UTF-8? env:Envelope xmlns:env=http://schemas.xmlsoap.org/soap/envelope/; env:Header TransactionID xmlns=http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0 env:mustUnderstand=1[EMAIL PROTECTED]/TransactionID /env:Header env:Body SubmitRsp xmlns=http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0 MM7Version5.3.0/MM7Version MessageID17784199/MessageID Status StatusCode1000/StatusCode StatusTextSuccess/StatusText /Status /SubmitRsp /env:Body /env:Envelope The problem that the mbuni think that the MMS faild and still trying send the MMS again and again, Please advice. Regards, Hafez ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users -- Hafez A.Ahmad Amman-Jordan mobile:962-785259011 962-795708728 http://blog.hafezadnan.com mbuni.conf ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] Failed to parse MMSC
There is clearly a problem with your MMSC URL format, not with the MM7 packet format - this error shouldn't occur. So you will need to share your *actual* conf with a trusted party for further help :) P. On Oct 13, 2008, at 18:11, hafez ahmad wrote: Dears List, I trying to send MMS, the user received the MMS successfully, but I have the following error: 2008-10-13 17:35:54 [26658] [9] INFO: Retry later MMSBox Outgoing Queue MMS Send: From [EMAIL PROTECTED], to 967711593356/TYPE=PLMN, msgsize=25269: msgid=[(null)], err=Failed to parse MMSC[url=http://username:[EMAIL PROTECTED]:80/mm7tomms.sh , id=HouseID] response! and I catch the following XMl Response , ?xml version=1.0 encoding=UTF-8? env:Envelope xmlns:env=http://schemas.xmlsoap.org/soap/envelope/; env:Header TransactionID xmlns=http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0 env:mustUnderstand=1[EMAIL PROTECTED]/TransactionID /env:Header env:Body SubmitRsp xmlns=http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0 MM7Version5.3.0/MM7Version MessageID17784199/MessageID Status StatusCode1000/StatusCode StatusTextSuccess/StatusText /Status /SubmitRsp /env:Body /env:Envelope The problem that the mbuni think that the MMS faild and still trying send the MMS again and again, Please advice. Regards, Hafez ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] multiple mmsc connections
When using the sendmms interface, add a CGI parameter mmsc=mmsc_id -- this should be set to the ID of the mmsc in the conf file. This will do the trick. You can also of course use denied-sender-prefix/allowed-sender- prefix, denied-receiver-prefix/allowed-receiver-prefix in the conf file to control what messages are sent via any given mmsc. On Sep 14, 2008, at 11:49, hafez ahmad wrote: Dears, I have 2 MMSC connections, how I send mms to specific connection? is it by set the mmsc variable in the url? and what the mmsc in the config represent is it the id in the group = mmsc? Regards, Hafez ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] Help with Mbuni VASGW administration Interfaces
Not yet, coming up in a couple of months though! On Aug 30, 2008, at 11:27, Mohammad Abu Karim wrote: Hi Guys. Kannel Has HTTP administration to administer the kannel to check status, shutdown ..etc. Does mbuni has such administration HTTP or command interface to administer it? If yes tell me please how to access it, and how I can check mbuni vasgw status. I mean how I can check the vasgw queue, the served MMSes, the filed delivered MMses and so on. Regards. Mohammad Abu-Karim ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] pls reply me
mmsbox, assuming you are running it as VAS GW. On Aug 30, 2008, at 09:23, madhu 3433 wrote: Dear ALL users i have install the kannel and mbunigateway successfully but iam not getting howw to start and run the mms box .In kannel will start bearer box first and after that will start sms box but here what i have to start pls help me Thnaking You Madhu([EMAIL PROTECTED] ) ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] Mbuni is not sending audio/video files to mms service
a look at the conf and logs might help here. On Aug 13, 2008, at 09:30, pramod b wrote: Hi we r testing with mbuni-1.4.0 with image as well as audio/video files wher the mmsbox is not routing the audio/video files to mms service application but its routing the image file to service perfectly . Is ther any size concern for mmsbox while sending audio/video files?? What might b the problem??If u need logs for both i can send regards pramod ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] Freedom of MBUNI
Mbuni does not depend on Kannel as the WAP Gateway, so yes you can do as you suggest below. Paul. On Aug 06, 2008, at 12:01, Real World wrote: Hi , Is MBUNI directly depend on kannel WAP gateway ? Just for Fetch MSISDN for all mms request do we have to have kannel wap gateway infront of MBUNI ? For insrtance if we have different wap gateway from a different vendor , can't we use MBUNI as a MMS gateway since those WAP gateways are parsing MSISDN same as what kannel wap gateway does? Many Thanks Mark. ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] Freedom of MBUNI
We are aware of a number of operators using Mbuni in this way, it all depends how much traffic you will be handling. You would also do well to use the PostgreSQL queue driver instead of the file-based one, as this makes queue management faster and easier/cleaner. You can also of course speak to the Trained Professionals at Skycore ([EMAIL PROTECTED]) if some hand-holding is desired. P. On Aug 06, 2008, at 12:53, Real World wrote: Thanks for the reply. Just a small question . Say we going to put mbuni for in front of high load like what mobile operator receiving. Does mbuni handles that load very well ? or is there any modification we have to do for mbuni source codes ?? - Original Message From: P. A. Bagyenda [EMAIL PROTECTED] To: Real World [EMAIL PROTECTED] Cc: MBUNI - MMS Users@mbuni.org Sent: Wednesday, August 6, 2008 2:56:17 PM Subject: Re: [Users] Freedom of MBUNI Mbuni does not depend on Kannel as the WAP Gateway, so yes you can do as you suggest below. Paul. On Aug 06, 2008, at 12:01, Real World wrote: Hi , Is MBUNI directly depend on kannel WAP gateway ? Just for Fetch MSISDN for all mms request do we have to have kannel wap gateway infront of MBUNI ? For insrtance if we have different wap gateway from a different vendor , can't we use MBUNI as a MMS gateway since those WAP gateways are parsing MSISDN same as what kannel wap gateway does? Many Thanks Mark. ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] Re: Slow MMS MT delivery
Sorry, been on the road. What version are you using? If CVS then concurrency definitely works. You should also probably use the DB (PostgreSQL) storage module as that does a much better job delivering messages fast. On Jul 24, 2008, at 07:46, Leonard Cooper ::JimmyYakuza:: wrote: Anyone? Hard to advocate use of a product with no support! - Original Message - From: Leonard Cooper ::JimmyYakuza:: [EMAIL PROTECTED] To: users@mbuni.org Sent: Wednesday, July 23, 2008 5:14 PM Subject: Re: Slow MMS MT delivery Any ideas anyone? this is getting urgent! - Original Message - From: Leonard Cooper ::JimmyYakuza:: [EMAIL PROTECTED] To: users@mbuni.org Sent: Wednesday, July 23, 2008 3:31 PM Subject: Slow MMS MT delivery Hi all, I am attemtping to deliver MMS's to approx 6000 msisdns. These message have been queued on Mbuni. I have 2 different MMSC configured via mm7 to which I deliver. I have specified the MMSC to use on submit via sendmms CGI in the mmsc param. Mbuni, however, is only delivering 1 mms every 8 seconds in the order they recieved in the queue. Should this not be sending to mmsc1 and mmsc2 that I specified simultaneously? Also, should there not be some sort of concurrency when delivering to MMSC (MM7 -soap)? Thanks Leonard ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] Logs are different
When the encoding type is missing, then the message is in binary format. This should not cause any problems. On Jul 09, 2008, at 08:12, pramod bodla wrote: Hi From the logs in MMSBOX When MMSBOX recieved an mms (image) from Mbuni-MMSC the logs are showing all the fields like content id: 1.jpg content location :1.jpg content type :image/jpeg content-trnsfer encoding: base 64 while the MMSBOX sending to MMS Service (Http server) it is adding some additional headers like X-Mbuni-Message-ID,X-Mbuni-MMSC-ID,X-Mbuni-From,X-Mbuni-Subject,X- Mbuni-To etc.. and also content type,content location it is mentioning but its not mentioning content-transfer-encoding and the Image data recieved from MMSC (base 64 encoding )and sending to MMS-Service both are different(not mentioned any encoding type). recieved from MMSC : 2008-07-03 16:55:06 [2546] [3] DEBUG: data: 0d 0a 43 6f 6e 74 65 6e 74 2d 49 44 3a 20 3c 30 ..Content-ID: 0 2008-07-03 16:55:06 [2546] [3] DEBUG: data: 30 30 30 30 31 2e 6a 70 67 3e 0d 0a 43 6f 6e 74 1.jpg..Cont 2008-07-03 16:55:06 [2546] [3] DEBUG: data: 65 6e 74 2d 4c 6f 63 61 74 69 6f 6e 3a 20 30 30 ent-Location: 00 2008-07-03 16:55:06 [2546] [3] DEBUG: data: 30 30 30 31 2e 6a 70 67 0d 0a 43 6f 6e 74 65 6e 0001.jpg..Conten 2008-07-03 16:55:06 [2546] [3] DEBUG: data: 74 2d 54 79 70 65 3a 20 69 6d 61 67 65 2f 6a 70 t-Type: image/jp 2008-07-03 16:55:06 [2546] [3] DEBUG: data: 65 67 0d 0a 43 6f 6e 74 65 6e 74 2d 54 72 61 6e eg..Content-Tran 2008-07-03 16:55:06 [2546] [3] DEBUG: data: 73 66 65 72 2d 45 6e 63 6f 64 69 6e 67 3a 20 62 sfer-Encoding: b 2008-07-03 16:55:06 [2546] [3] DEBUG: data: 61 73 65 36 34 0d 0a 0d 0a 2f 39 6a 2f 34 41 41 ase64/9j/4AA 2008-07-03 16:55:06 [2546] [3] DEBUG: data: 51 53 6b 5a 4a 52 67 41 42 41 51 45 41 53 41 42 QSkZJRgABAQEASAB 2008-07-03 16:55:06 [2546] [3] DEBUG: data: 49 41 41 44 2f 32 77 42 44 41 41 67 47 42 67 63 IAAD/2wBDAAgGBgc 2008-07-03 16:55:06 [2546] [3] DEBUG: data: 47 42 51 67 48 42 77 63 4a 43 51 67 4b 44 42 51 GBQgHBwcJCQgKDBQ 2008-07-03 16:55:06 [2546] [3] DEBUG: data: 4e 44 41 73 4c 44 42 6b 53 45 77 38 55 48 52 6f NDAsLDBkSEw8UHRo Sending to MMS Service: 2008-07-03 16:55:09 [2546] [16] DEBUG: data: 62 6f 75 6e 64 61 72 79 5f 31 32 34 38 35 36 36 boundary_1248566 2008-07-03 16:55:09 [2546] [16] DEBUG: data: 39 38 39 5f 31 32 31 35 30 38 34 33 30 39 5f 51 989_1215084309_Q 2008-07-03 16:55:09 [2546] [16] DEBUG: data: 5f 67 5f 62 64 31 36 33 35 32 38 31 37 31 33 0d _g_bd1635281713. 2008-07-03 16:55:09 [2546] [16] DEBUG: data: 0a 43 6f 6e 74 65 6e 74 2d 44 69 73 70 6f 73 69 .Content-Disposi 2008-07-03 16:55:09 [2546] [16] DEBUG: data: 74 69 6f 6e 3a 20 66 6f 72 6d 2d 64 61 74 61 3b tion: form-data; 2008-07-03 16:55:09 [2546] [16] DEBUG: data: 20 6e 61 6d 65 3d 22 69 6d 61 67 65 73 5b 5d 22 name=images[] 2008-07-03 16:55:09 [2546] [16] DEBUG: data: 3b 20 66 69 6c 65 6e 61 6d 65 3d 22 30 30 30 30 ; filename= 2008-07-03 16:55:09 [2546] [16] DEBUG: data: 30 31 2e 6a 70 67 22 0d 0a 43 6f 6e 74 65 6e 74 01.jpg..Content 2008-07-03 16:55:09 [2546] [16] DEBUG: data: 2d 54 79 70 65 3a 20 69 6d 61 67 65 2f 6a 70 65 -Type: image/jpe 2008-07-03 16:55:09 [2546] [16] DEBUG: data: 67 0d 0a 0d 0a ff d8 ff e0 00 10 4a 46 49 46 00 g..JFIF. 2008-07-03 16:55:09 [2546] [16] DEBUG: data: 01 01 01 00 48 00 48 00 00 ff db 00 43 00 08 06 H.H.C... 2008-07-03 16:55:09 [2546] [16] DEBUG: data: 06 07 06 05 08 07 07 07 09 09 08 0a 0c 14 0d 0c 2008-07-03 16:55:09 [2546] [16] DEBUG: data: 0b 0b 0c 19 12 13 0f 14 1d 1a 1f 1e 1d 1a 1c 1c 2008-07-03 16:55:09 [2546] [16] DEBUG: data: 20 24 2e 27 20 22 2c 23 1c 1c 28 37 29 2c 30 31 $.' ,#..(7),01 2008-07-03 16:55:09 [2546] [16] DEBUG: data: 34 34 34 1f 27 39 3d 38 32 3c 2e 33 34 32 ff db 444.'9=82.342.. 2008-07-03 16:55:09 [2546] [16] DEBUG: data: 00 43 01 09 09 09 0c 0b 0c 18 0d 0d 18 32 21 1c .C...2!. 2008-07-03 16:55:09 [2546] [16] DEBUG: data: 21 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 !222 2008-07-03 16:55:09 [2546] [16] DEBUG: data: 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 2008-07-03 16:55:09 [2546] [16] DEBUG: data: 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 What might be the problem. help needed... regards pramod ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] Traces for mm7 messages
The OpenWave MM7 SDK documentation has some samples. Ditto Ericsson MM7 SDK docs as well as Nokia MMS Developer guides. On Jul 04, 2008, at 12:04, pramod bodla wrote: Hi can any one provide the traces for mm7 messages reagards pramod ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] Enforcing Supported file types
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 Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] Enforcing Supported file types
On Jul 03, 2008, at 16:35, Willis Vandevanter wrote: Thank you for your help. 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. So if content adaptation is turned on, but the MM doesn't contain one of the common image and audio types, then is the MM forwarded without modification to the receiver? What if the UAProf says the file cannot be handled by the receiver, is a delivery attempt still made? The unsupported *part* is removed and a message is inserted saying unsupported content type, removed by server. The rest of the message is left as-is. Not ideal but at least it means that the parts the device supports are left for the receiver to view. Now in an ideal setup you would have Mbuni configured to store the messages on a separate network entity as well, so subscribers can view them on the Web or such... Thanks. -Willis http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] MMS proxy issue
Vijay, Please switch to CVS and lets see if the error persists. We will soon put out a new build. 1.3.0 had issues. On Jul 02, 2008, at 14:52, Vijay wrote: Hi, Thanks in advance for your help Am running mbuni version 1.3.0 in ubuntu mmsbox,mmsproxy, mmsrelay Sending a mms using URL its working fine sendmms?username=gsmspassword=gsmsto=111smil=smil+xmlns=http://www.w3.org/2001/SMIL20/Language +xml:lang=en+title=SMIL+template++head++/head++bodyimg +src=party.jpg/++/body/smilbase-url=file://home/kodiak But same URL if i used to send an MMS running in Linux machine mmsbox,mmsproxy, mmsrelay Linux rtxes1 2.4.21-15.0.3.ELsmp #1 SMP Tue Jun 29 18:04:47 EDT 2004 i686 i686 i386 GNU/Linux Is there any problem in machine? Am getting this errors : Failed to see end boundary, parsed line is '/9j/ 4AAQSkZJRgABAQEASABIAAD/ 2wBDAAgGBgcGBQgHBwcJCQgKDBQNDAsLDBkSEw8UHRofHh0a'. Failed to see end boundary, parsed line is '?xml version=1.0? 2008-07-02 08:40:58 [27350] [4] DEBUG: -- Enterred mm7dispatch interface, mreq=[Ok] mtype=[SubmitReq] -- 2008-07-02 08:40:58 [27350] [4] PANIC: gwlib/octstr.c:2447: seems_valid_real: Assertion `ostr != NULL' failed. (Called from gwlib/octstr.c:661:octstr_base64_to_binary.) 2008-07-02 08:40:58 [27350] [4] PANIC: mmsproxy(gw_panic+0xfd) [0x80a19fd] 2008-07-02 08:40:58 [27350] [4] PANIC: mmsproxy [0x80a84ac] 2008-07-02 08:40:58 [27350] [4] PANIC: mmsproxy(octstr_base64_to_binary+0x27) [0x80a489f] 2008-07-02 08:40:58 [27350] [4] PANIC: mmsproxy(unbase64_mimeparts +0x13c) [0x8085b4c] 2008-07-02 08:40:58 [27350] [4] PANIC: mmsproxy(unbase64_mimeparts +0x42) [0x8085a52] 2008-07-02 08:40:58 [27350] [4] PANIC: mmsproxy(mms_frommime+0x50) [0x807cc24] 2008-07-02 08:40:58 [27350] [4] PANIC: mmsproxy(mm7_soap_to_mmsmsg +0x3f) [0x808a5ff] 2008-07-02 08:40:58 [27350] [4] PANIC: mmsproxy [0x8075a64] 2008-07-02 08:40:58 [27350] [4] PANIC: mmsproxy [0x8099227] 2008-07-02 08:40:58 [27350] [4] PANIC: /lib/tls/libpthread.so.0 [0xb746edec] 2008-07-02 08:40:58 [27350] [4] PANIC: /lib/tls/libc.so.6(__clone +0x5a) [0xb740ae8a] -- VIJAY ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] How to MM7 msg
Vijay, It helps if you explain your architecture broadly so that we know how to advise you. Also, the documentation is long and detailed, and there are numerous resources out there on the MMS architecture in general. They are a great help to begin with, particularly as MMS is a tad more complicated than SMS. P. On Jun 26, 2008, at 09:19, Vijay wrote: Hi am running VAS gateway, I want to send a MM7 incoming message to the VAS gateway Is there any application/stub/tool to do that. Also after VAS gateway gets an incoming message it will give it to service Is that service is http client we need to run or how should be the service Please guide me -- VIJAY ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] Multiple short codes
You can of course have multiple connections, to different MMSC. You can control how Mbuni routes incoming and out-going messages by number or directly when you use the send-mms interface. On Jun 24, 2008, at 17:00, Vijay wrote: Hi, Am running Mbuni as VAS gateway and am trying to connect to network MMSC. Can I have multiple short codes for my VAS gateway so that MMSC will route all those messages. If its possible tell me what the configuration need to be done in mbuni.conf So far i have seen is short code configuration only when am running as MMSC. -- VIJAY ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] How to get Message ID?
The message ID is reported as part of the HTTP response. On Jun 23, 2008, at 06:31, Yoj StamAria wrote: Hi, I seem to be Lost. I could not get the message ID of the mms message that I sent. I am using Mbuni as VAS gateway and I could not match which message was sent when the delivery report comes because I could not get the message ID from the MMSC but the MMSC returns it on the soap message replied to Mbuni. I use the sendmms cgi and I enabled accept-x-mbuni headers already. Thanks! ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] configure: error: Kannel gwlib is required
config.log should tell you what happened. What does it say? On Jun 23, 2008, at 15:53, Vijay wrote: These are the errors am getting when doing ./configure --disable-ssl checking Kannel version... cvs-20070722 checking Kannel libs... -L/usr/local/lib/kannel -lgw -lwap -lgwlib - lssl -lrt -lresolv -lnsl -lm -lpthread -L/usr/local/lib -lxml2 - lpthread -lm -L/usr/local/ssl/lib -lcrypto -lssl checking Kannel includes... -I/usr/local/include/kannel -g -O2 - D_XOPEN_SOURCE=600 -D_BSD_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/local/ include/libxml2 -I/usr/local/ssl/include checking for cfg_create in -lgwlib... no configure: error: Kannel gwlib is required! path: /usr/local/lib/kannel Libs found: libgw.a libgwlib.a libwap.a So can any one please suggest me whats the problem? -- VIJAY -- VIJAY ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] How do I receive MMS?
Mbuni assumes that the network is of course well-behaved :) On Jun 20, 2008, at 04:08, Yoj StamAria wrote: Thank you for your help. I had been tracing it overnight and found out that during the transmission, the packets were split into two groups. The request would be therefore incomplete hence, the bad request reply. I am still finding out if this is caused by our network or the MMSC's network. Is there a way to resolve this on Mbuni's side, like for instance waiting for x seconds? --- On Thu, 6/19/08, P. A. Bagyenda [EMAIL PROTECTED] wrote: From: P. A. Bagyenda [EMAIL PROTECTED] Subject: Re: [Users] How do I receive MMS? To: [EMAIL PROTECTED] Date: Thursday, June 19, 2008, 12:02 PM I hope that is not an empty line after the incoming-password field? The soap handler never sends a 404 error, so this error must be caused by the type of mmsc being wrong On Jun 19, 2008, at 06:55, Yoj StamAria wrote: They are sending it to port 7465 here is a part of my config #--MMSC group = mmsc id = ID mmsc-url = http://xx.xx.xx.xx:x/vas mm7-soap-xmlns = http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2 incoming-username = xx incoming-password = xx incoming-port = 7465 type = soap #MMS SERVICE CONFIGURATION group = mms-service name = RECEIVER post-url = http://localhost:1882/RequestServlet/RequestServlet catch-all = true #http-post-parameters = fx=trueimages[]=%itext[]=%t accept-x-mbuni-headers = true keyword = test --- On Thu, 6/19/08, P. A. Bagyenda [EMAIL PROTECTED] wrote: From: P. A. Bagyenda [EMAIL PROTECTED] Subject: Re: [Users] How do I receive MMS? To: [EMAIL PROTECTED] Date: Thursday, June 19, 2008, 11:46 AM what port are they sending to? What's your config file look like? On Jun 19, 2008, at 06:38, Yoj StamAria wrote: im sorry here is the log that I am getting 2008-06-18 23:33:44 [18859] [2] DEBUG: HTTP: Creating HTTPClient for `xxx.xxx.xx.xx. 2008-06-18 23:33:44 [18859] [2] DEBUG: HTTP: Created HTTPClient area 0x941cea0. 2008-06-18 23:33:44 [18859] [1] DEBUG: HTTP: Destroying HTTPClient area 0x941cea0. 2008-06-18 23:33:44 [18859] [1] DEBUG: HTTP: Destroying HTTPClient for `xxx.xxx.xx.xx. Here is what they are sending POST HTTP/1.1 Host: xx.xx.xx.xx: User-Agent: MMSC/2.2 Connection: keep-alive Content-Length: 1678 Content-Type: multipart/related; boundary=soap-border; type=text/xml; start=/soap-env/start Accept: text/xml, application/xml SOAPAction: --soap-border Content-Type: text/xml; charset=utf-8 Content-ID: /soap-env/start ?xml version=1.0 ? env:Envelope xmlns:env=http://schemas.xmlsoap.org/soap/envelope/; env:Header mm7:TransactionID xmlns:mm7=http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2 env:mustUnderstand=1AfqTmEXuy7GTKobI_/mm7:TransactionID /env:Header env:Body DeliverReq xmlns=http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2 MM7Version5.3.0/MM7Version MMSRelayServerIDMMH2/MMSRelayServerID SenderRFC2822Address+639175884526/TYPE=PLMN/RFC2822Address/ Sender Recipients To RFC2822Address+2373/TYPE=PLMN/RFC2822Address /To /Recipients TimeStamp2008-06-18T10:33:04Z/TimeStamp PriorityNormal/Priority Subjecttest mms/Subject Content href=cid:soap-attach-start / /DeliverReq /env:Body /env:Envelope --soap-border Content-Type: multipart/ related ;boundary=1_4858E460_282C9C4;Start=22383792;Type=application/ smil Content-ID: soap-attach-start --1_4858E460_282C9C4 content-type:text/plain;Charset=UTF-8;Name=Test.txt content-location:Test.txt content-transfer-encoding:7bit Test --1_4858E460_282C9C4 content-type:application/smil;Charset=UTF-8;Name=pres.smil content-id:22383792 content-transfer-encoding:7bit smilheadlayoutroot-layout width=176 height=208/region id=Text width=160 height=183 top=5 left=8 fit=scroll//layout/ headbodypar dur=5000mstext region=Text src=Test.txt//par/body/ smil --1_4858E460_282C9C4-- --soap-border-- they always get HTTP/1.1 400 Bad Request Server: Kannel/cvs-20061123 Content-Length: 0 Connection: close .. ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] How do I receive MMS?
To understand the 400 error you will need to look at the logs. Could you provide that part of the logs? On Jun 19, 2008, at 05:07, Yoj StamAria wrote: Currently, I can send MMS to the Operator MMSC. I have set- up my MBuni as a VAS Gateway But I cant seem to receive their MMS. they are getting this error HTTP/1.1 400 Bad Request Server: Kannel/cvs-20061123 Content-Length: 0 Connection: close .. I have set the incoming-port of mbuni. what else do I need? Do I need to turn on the wapbox from kannel too? ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] MM4 and Mbuni
Short answer: Yes! On Jun 17, 2008, at 05:59, Tharanga wrote: Hi All, I need to send/receive MMS using the the MM4 protocol . Is this opensource version supports this ? please let me know. Thanks, Tharanga ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] help setting up MBUNI as VAS gateway
One would need to see the log to understand what's going on. A 500 error should not ordinarily occur on the sendmms interface. On Jun 13, 2008, at 11:05, Christopher Dacuya wrote: I am new to mbuni and I am trying to set-up mbuni as a VAS gateway. I have previously used kannel before but I am confused in setting the configuration of mbuni. here is my configuration # mbuni.conf # mbuni configuration file #GROUP CORE CONFIGURATION group = core log-file = /appl/escplatform/logs/mmsgw.log log-level = 0 access-log = /appl/escplatform/access.log #MAIN GATEWAY CONFIGURATION GROUP group = mbuni name = MMSC storage-directory = /appl/escplatform/vas max-send-threads = 5 unified-prefix = 09,+639,639 maximum-send-attempts = 3 allow-ip = 127.0.0.1;192.168.0.* deny-ip = *.*.*.* sendmms-port = 10021 mm7-port = 8084 sendsms-url = http://localhost:14014/cgi-bin/sendsms sendsms-username = euser sendsms-password = grewq sendsms-global-sender = 2356 #MM7 CONFIGURATION group = mms-vasp vasp-id = itesting type = soap short-code = 100 vasp-username = 2356 vasp-password = 1V016B5P #MMSC CONNECTION CONFIGURATION group = mmsc id = iplaypen mmsc-url = http://xxx.xxx.xx.53:10021/vas incoming-username = 2356 incoming-password = 213dddc2 incoming-port = 7462 type = soap #SENDMMS USER CONFIGURATION group = send-mms-user username = euser password = grewq faked-sender = 100 #MMS SERVICE CONFIGURATION group = mms-service name = 'RECEIVER' post-url = http://localhost:1882/RequestServlet/RequestServlet catch-all = true http-post-parameters = fx=trueimages[]=%itext[]=%t accept-x-mbuni-headers = true keyword = test I am now in the process of sending my first MMS i used this: http://192.168.0.17:10021/cgi-bin/sendmms?to=09178101512username=euserpassword=grewqvasid=itestingfrom=2356text=testing i get HTTP status 500 please help ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] kannel + mbuni + gprs modem + mm1 interface
Hi Marvin, The MM1 plugin to do what you want is available from Skycore ([EMAIL PROTECTED] ). On Jun 09, 2008, at 16:19, Marvin Schmidt wrote: Hallo everybody, for a application for university we want to be able to send SMS/WAPPUSH/MMS. The first two things are no problem with our Kannel Server with a working PCMCIA Card from Vodafode (Option Colt). Sending an MMS for real to another mobile with this Modem (and any other) is more a problem, because obviously there is no way to send a MMS over MM1 interface. Does anybody knows a way to do it? Does anybody has contact with Skycore/Digital Solutions to get the MM1 Plugin for Mbuni. I tried it out a several times but i get no feedback. Does anybody know a application to send MMS over MM1 interface whitch is open source? Thanks! Marvin Schmidt TFH-Wildau marvin.schmidt [at] tfh-wildau.de ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] Sender element missing sub element in deliveryReq and deliveryReportReq
Hi, Use the CVS version and set the MM7 version in use to 5.3.0 (in the conf file) and Mbuni will do the right thing. Mbuni supports both older and new MM7 encodings, hence the apparent 'error'. On Jun 02, 2008, at 15:03, Ronnie Jones wrote: I'm a first time user of mbuni, and it seems to be a good piece of software but I've seem to have ran into an issue with deliveryReq and deliveryReportReq where the Sender element should contain the following sub elements: xs:element name=RFC2822Address xs:element name=Number xs:element name=ShortCode Can this please be reviewed and determine whether there is a mbuni fix Below is a snippet from the trace that was producted by mmsreply. It appears that the Sender address should have one of the three sub elements above. 2008-06-01 23:41:22 [19623] [27] INFO: MMS Relay: Send[soap] to VASP[newscorp], msg_type=[m-send-req], from=[100/TYPE=PLMN], to=[111/ TYPE=PLMN] 2008-06-01 23:41:22 [19623] [27] DEBUG: SOAP headers dump follows: 2008-06-01 23:41:22 [19623] [27] DEBUG: Dumping HTTP headers: 2008-06-01 23:41:22 [19623] [27] DEBUG: Octet string at 0x9fd5c60: 2008-06-01 23:41:22 [19623] [27] DEBUG:len: 14 2008-06-01 23:41:22 [19623] [27] DEBUG:size: 15 2008-06-01 23:41:22 [19623] [27] DEBUG:immutable: 0 2008-06-01 23:41:22 [19623] [27] DEBUG:data: 53 4f 41 50 41 63 74 69 6f 6e 3a 20 22 22 SOAPAction: 2008-06-01 23:41:22 [19623] [27] DEBUG: Octet string dump ends. 2008-06-01 23:41:22 [19623] [27] DEBUG: Octet string at 0x9fd7220: 2008-06-01 23:41:22 [19623] [27] DEBUG:len: 148 2008-06-01 23:41:22 [19623] [27] DEBUG:size: 149 2008-06-01 23:41:22 [19623] [27] DEBUG:immutable: 0 2008-06-01 23:41:22 [19623] [27] DEBUG:data: 43 6f 6e 74 65 6e 74 2d 54 79 70 65 3a 20 6d 75 Content-Type: mu 2008-06-01 23:41:22 [19623] [27] DEBUG:data: 6c 74 69 70 61 72 74 2f 72 65 6c 61 74 65 64 3b ltipart/related; 2008-06-01 23:41:22 [19623] [27] DEBUG:data: 20 74 79 70 65 3d 22 74 65 78 74 2f 78 6d 6c 22type=text/xml 2008-06-01 23:41:22 [19623] [27] DEBUG:data: 3b 20 73 74 61 72 74 3d 22 3c 73 31 32 31 32 33 ; start=s12123 2008-06-01 23:41:22 [19623] [27] DEBUG:data: 37 38 30 38 32 2e 31 30 34 35 39 31 37 30 36 30 78082.1045917060 2008-06-01 23:41:22 [19623] [27] DEBUG:data: 2e 46 72 2e 6d 73 67 3e 22 3b 20 62 6f 75 6e 64 .Fr.msg; bound 2008-06-01 23:41:22 [19623] [27] DEBUG:data: 61 72 79 3d 5f 62 6f 75 6e 64 61 72 79 5f 31 32 ary=_boundary_12 2008-06-01 23:41:22 [19623] [27] DEBUG:data: 34 31 39 35 31 32 36 32 5f 31 32 31 32 33 37 38 41951262_1212378 2008-06-01 23:41:22 [19623] [27] DEBUG:data: 30 38 32 5f 55 5f 67 5f 62 64 31 35 31 38 39 33 082_U_g_bd151893 2008-06-01 23:41:22 [19623] [27] DEBUG:data: 39 38 39 32 9892 2008-06-01 23:41:22 [19623] [27] DEBUG: Octet string dump ends. 2008-06-01 23:41:22 [19623] [27] DEBUG: Octet string at 0x9fd5ee0: 2008-06-01 23:41:22 [19623] [27] DEBUG:len: 17 2008-06-01 23:41:22 [19623] [27] DEBUG:size: 18 2008-06-01 23:41:22 [19623] [27] DEBUG:immutable: 0 2008-06-01 23:41:22 [19623] [27] DEBUG:data: 4d 49 4d 45 2d 56 65 72 73 69 6f 6e 3a 20 31 2e MIME-Version: 1. 2008-06-01 23:41:22 [19623] [27] DEBUG:data: 300 2008-06-01 23:41:22 [19623] [27] DEBUG: Octet string dump ends. 2008-06-01 23:41:22 [19623] [27] DEBUG: End of dump. 2008-06-01 23:41:22 [19623] [27] DEBUG: SOAP MSG is: -- _boundary_1241951262_1212378082_U_g_bd1518939892 Content-Type: text/xml Content-ID: s1212378082.1045917060.Fr.msg ?xml version='1.0' encoding='UTF-8'? SOAP-ENV:Envelope xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/ SOAP-ENV:Header mm7:TransactionID xmlns:mm7=http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2 SOAP-ENV:mustUnderstand=1mmsc-sipintel27-j-l2-qf8081.9.x501.40/ mm7:TransactionID /SOAP-ENV:Header SOAP-ENV:Body mm7:DeliverReq xmlns:mm7=http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2 mm7:MM7Version5.3.0/mm7:MM7Version mm7:Recipients mm7:To mm7:Number111/mm7:Number /mm7:To /mm7:Recipients mm7:MMSRelayServerIDmmsc-sipintel27/mm7:MMSRelayServerID mm7:LinkedIDmmsc-sipintel27-j-l2-qf8081.9.x501.40/mm7:LinkedID mm7:Sender100/mm7:Sender mm7:TimeStamp2008-06-02T03:41:16Z/mm7:TimeStamp mm7:SubjectParty Time/mm7:Subject mm7:Content href=cid:c1212378082.1835012365.Ui.msg/ /mm7:DeliverReq /SOAP-ENV:Body /SOAP-ENV:Envelope --_boundary_1241951262_1212378082_U_g_bd1518939892 Content-Type: text/plain Content-ID: c1212378082.1835012365.Ui.msg This is a test begin- -end
Re: [Users] No Service to handle message when accepted-mmscs or denied-mmscs specified
The validation problem is due to not setting the XMLNS to the value expected by the MMSC at the other end. There is a new option for setting that in the config (see doc in CVS). On the routing issue, you really have to be careful how you use the accepted-mmsc/denied-mmsc and allowed-prefix/denied-prefix settings. Again, see the doc in CVS for more information. If you feel the implementation/behaviour does not conform to the documentation, pray let us know (of course quoting chapter and verse). P. On May 05, 2008, at 13:58, Marco Lopes wrote: Apart from the original problem of being unable to route the messages to the right services, I noticed other totally unrelated but odd thing I think I should report. In the version cvs-20080326 I was unable to send messages due to a validation problem. I searched the mailling list and I found that this was a known problem that had been fixed April 2007 (thread: http://lists.mbuni.org/pipermail/users/2007-April/30.html ) The version cvs-20070508 I was using first don't have this problem, thus confirming the bug was fixed, but it seems to have returned and is now present on version cvs-20080326. Meanwhile, as the cvs-20080326 didn't solve the original routing problem that would allow me to receive MMS, I got back to the cvs-20070508 where I could at least send. P. A. Bagyenda wrote: send me the config and the log file. This should work! On Apr 16, 2008, at 12:10, Marco Lopes wrote: Yes, currently, for testing purposes I'm using only one mmsc configuration, to make sure no conflicts arise, and one mmsc- service configuration, the service configuration has catch-all set to true. P. A. Bagyenda wrote: Yes the 'fromproxy' is the sender mmsc. The way you print it below would not work as it is not a char *. This part should generally work without pain. I notice there is no keyword in this case. Do you have a catch-all service for when you have no keyword? On Apr 14, 2008, at 14:29, Marco Lopes wrote: Hi, I've been browsing through the source code and I found something that may help find out what's going on. The function get_service receives an Octsring as second paramenter, this parameter is called mmc_id inside the functions and is compared to the list of allowed_mmscs and the list of denied_mmscs using the gwlist_search function. The call to this functions sends as mmc_id the variable e- fromproxy being e a structure which represents the envelope. Is this what is supposed to happen, is the fromproxy and the mmsc id the same thing? I used the same function which is used to log the errors to log the e-fromproxy value with even stranger results. The code used was error(0, MYDEBUG: %s,octstr_get_cstr(octstr_format(temp: %s\n, e-fromproxy))); The output: 2008-04-07 09:43:39 [26582] [7] ERROR: MYDEBUG: temp: (^[^X^H Would this help in any way? Marco Lopes wrote: Hi, I've try to send a mail with the log of the full processing of an MMS but the mail didn't reach the ML due to the size of the text atachment (500K) so I'll send only the last few lines of the log to see if it helps. I'm using version cvs-20080326. 2008-03-27 17:35:54 [24566] [3] DEBUG: HTTP: Destroying HTTPClient area 0x8163010. 2008-03-27 17:35:54 [24566] [3] DEBUG: HTTP: Destroying HTTPClient for `194.65.126.96'. 2008-03-27 17:35:54 [24566] [3] DEBUG: -- leaving mm7dispatch interface, mresp=[ok], body=[ok], mm7_status=[1000] -- 2008-03-27 17:35:54 [24566] [3] DEBUG: entered free_clientinfo 0, ip=[135671016] 2008-03-27 17:35:54 [24566] [3] DEBUG: left free_clientinfo 2008-03-27 17:35:54 [24566] [0] WARNING: mms_queueread: Mal- formed address [351967111284] in file ./mmsbox_incoming/p/ qf9353.1.x566.38! Attempting fixup. 2008-03-27 17:35:54 [24566] [0] DEBUG: Queued to thread 0 for ./ mmsbox_incoming/p/qf9353.1.x566.38, sendt=1206639353, tnow=1206639354 2008-03-27 17:35:54 [24566] [6] WARNING: Faulty address [351967111284] format in field From! 2008-03-27 17:35:54 [24566] [6] DEBUG: WSP: decoding headers: 2008-03-27 17:35:54 [24566] [6] DEBUG: Octet string at 0x817e2d8: 2008-03-27 17:35:54 [24566] [6] DEBUG: len: 51 2008-03-27 17:35:54 [24566] [6] DEBUG: size: 52 2008-03-27 17:35:54 [24566] [6] DEBUG: immutable: 0 2008-03-27 17:35:54 [24566] [6] DEBUG: data: 19 61 70 70 6c 69 63 61 74 69 6f 6e 2f 73 6d 69 .application/smi 2008-03-27 17:35:54 [24566] [6] DEBUG: data: 6c 00 81 ea 85 41 41 41 41 00 c0 3c 41 41 41 41 l.. 2008-03-27 17:35:54 [24566] [6] DEBUG: data: 3e 00 4d 49 4d 45 2d 56 65 72 73 69 6f 6e 00 31 .MIME-Version.1 2008-03-27 17:35:54 [24566] [6] DEBUG: data: 2e 30 00 .0. 2008-03-27 17:35:54 [24566] [6] DEBUG: Octet string dump ends. 2008-03-27 17:35:54 [24566] [6] DEBUG: WSP: decoded headers: 2008-03-27 17:35:54 [24566] [6] DEBUG: Content-Type: application/smil; charset=utf-8; name= 2008-03-27 17:35:54 [24566] [6] DEBUG
Re: [Users] List of checked mobile phones
Mario, There are many. I've used at least the following satisfactorily over the years: - Nokia 6600, E-series, 6230, - Sony Ericsson T630, W800 On the MM1 interface generally any phone would work fine. Some problems arise for email2mms, due to some phones not being too happy with any extra headers that that interface tends to introduce. This is typically due to flakiness on the part of the phone software. Or at least we tend to think so for now, since other more robust phones work perfectly well. Paul. On Apr 25, 2008, at 12:29, [EMAIL PROTECTED] wrote: Dear all, Is there available anywhere a list of checked mobile phones for mbuni? Could any of you send me couple of models which works fine? Thanks in advance to all of you. -- Mario Pascual Carrasco Unidad de Investigación en Telemedicina y e-Salud Instituto de Salud Carlos III C/ Sinesio Delgado, 6 28029 MADRID (Spain) Tlno: (+34) 91 8222119 E-Mail: [EMAIL PROTECTED] ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] saving received mms to a db
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=trueimages[]=%itext[]=%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 [+] 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/users@mbuni.org/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.confkeyword_bouncer.phpmms_22.logreceive- mmsgw.logsend-mmsgw.log ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] saving received mms to a db
Could we have a look at mbuni's log to see if it is sending the data. On Apr 16, 2008, at 19:07, Jovan Kostovski wrote: Hi, I've compiled and configured mbuni from CVS (version from 2008-04-11) with Kannel CVS (daily snapshot from 2008-04-14) Everything works well and I'm able to send and receive MMS messages. I'm using Mbuni as VASGW to connect to NOKIA MMSC. I want to save the MT MMSs (MMS messages which are received by Mbuni). I found one list discussion (http://www.mail-archive.com/users@mbuni.org/msg00701.html), tried the solution presented, but I couldn't fetch the parts of the MMS with the post-url. I've tried to configure the mms-service group but I couldn't get it working. I also wanted to disable the delivery reports by setting suppress-reply = true but that didn't work either. You can find the mmsbox.conf and the post-url handler as attachments. Can anyone explain me what am I doing wrong? BEST REGARDS, Jovan mmsbox .conf mms_receiver .phpmms_receiver.log___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] Lost on how to locally test my MMSC
Ahmad, Since Mbuni also has an MMSC, there is no need for a 'fakemmsc' tool. When you install Mbuni it installs two sample configuration files. They are a good starting point. It is also useful to trawl the mailing list archives for additional hints, pointers, etc. I hope we can help. Paul. On Apr 16, 2008, at 11:59, Ahmad Amireh wrote: Hello all, Before I explain what I want to do, I'd like to state that I'm a total newbie to this field, I'm no system administrator at all, I'm a php developer, and I had no experience in such matters until a few days ago where I had to set up Kannel + SMSC + MMSC on my machine in order to set it up on our company's server later.. So, I'd really appreciate it if you considered that while you answer me, if you do at all. 1. The biggest problem I faced while learning how to configure Kannel was the lack of documentation, I've crashed my head against the wall trying to search for extra HOWTOs or tutorials or at least more detailed config-directives info, but to no luck. All I found was the Kannel official manual, and same for mbuni. I would really appreciate it if anyone could point me out to any book, or online- material that would further guide me and help me understand what really is going on. 2. I've correctly set up my Kannel, WAPbox, and SMSbox, and I tested my SMSC using the fakesms service, and there is where I failed when I tried to set up my Mbuni server. I can access my mbuni server from the http interface, but I looked for a way to do fakesms-like (fakemms), but all I got was 1 line saying Mbuni can be set up as a VAS gateway that would work as fakemms. I couldn't understand that, and I can't really tell how to set that up. I want a mechanism to test my MMSC locally to see what I need to fix with the configuration before I start implementing it on the main server. If anyone could clear it up for me, I would ever appreciate it. I sincerely apologize if I wasted your time reading my post, since I'm a newbie and I can't really talk technical in this field, but I don't know where else to go for support. If you need me to supply any config files used for my compilations, don't hesitate to ask please. Any reply is most welcome. Thanks alot for your time, Ahmad ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] No Service to handle message when accepted-mmscs or denied-mmscs specified
Yes the 'fromproxy' is the sender mmsc. The way you print it below would not work as it is not a char *. This part should generally work without pain. I notice there is no keyword in this case. Do you have a catch-all service for when you have no keyword? On Apr 14, 2008, at 14:29, Marco Lopes wrote: Hi, I've been browsing through the source code and I found something that may help find out what's going on. The function get_service receives an Octsring as second paramenter, this parameter is called mmc_id inside the functions and is compared to the list of allowed_mmscs and the list of denied_mmscs using the gwlist_search function. The call to this functions sends as mmc_id the variable e-fromproxy being e a structure which represents the envelope. Is this what is supposed to happen, is the fromproxy and the mmsc id the same thing? I used the same function which is used to log the errors to log the e-fromproxy value with even stranger results. The code used was error(0, MYDEBUG: %s,octstr_get_cstr(octstr_format(temp: %s\n, e-fromproxy))); The output: 2008-04-07 09:43:39 [26582] [7] ERROR: MYDEBUG: temp: (^[^X^H Would this help in any way? Marco Lopes wrote: Hi, I've try to send a mail with the log of the full processing of an MMS but the mail didn't reach the ML due to the size of the text atachment (500K) so I'll send only the last few lines of the log to see if it helps. I'm using version cvs-20080326. 2008-03-27 17:35:54 [24566] [3] DEBUG: HTTP: Destroying HTTPClient area 0x8163010. 2008-03-27 17:35:54 [24566] [3] DEBUG: HTTP: Destroying HTTPClient for `194.65.126.96'. 2008-03-27 17:35:54 [24566] [3] DEBUG: -- leaving mm7dispatch interface, mresp=[ok], body=[ok], mm7_status=[1000] -- 2008-03-27 17:35:54 [24566] [3] DEBUG: entered free_clientinfo 0, ip=[135671016] 2008-03-27 17:35:54 [24566] [3] DEBUG: left free_clientinfo 2008-03-27 17:35:54 [24566] [0] WARNING: mms_queueread: Mal-formed address [351967111284] in file ./mmsbox_incoming/p/ qf9353.1.x566.38! Attempting fixup. 2008-03-27 17:35:54 [24566] [0] DEBUG: Queued to thread 0 for ./ mmsbox_incoming/p/qf9353.1.x566.38, sendt=1206639353, tnow=1206639354 2008-03-27 17:35:54 [24566] [6] WARNING: Faulty address [351967111284] format in field From! 2008-03-27 17:35:54 [24566] [6] DEBUG: WSP: decoding headers: 2008-03-27 17:35:54 [24566] [6] DEBUG: Octet string at 0x817e2d8: 2008-03-27 17:35:54 [24566] [6] DEBUG: len: 51 2008-03-27 17:35:54 [24566] [6] DEBUG: size: 52 2008-03-27 17:35:54 [24566] [6] DEBUG: immutable: 0 2008-03-27 17:35:54 [24566] [6] DEBUG: data: 19 61 70 70 6c 69 63 61 74 69 6f 6e 2f 73 6d 69 .application/smi 2008-03-27 17:35:54 [24566] [6] DEBUG: data: 6c 00 81 ea 85 41 41 41 41 00 c0 3c 41 41 41 41 l.. 2008-03-27 17:35:54 [24566] [6] DEBUG: data: 3e 00 4d 49 4d 45 2d 56 65 72 73 69 6f 6e 00 31 .MIME-Version.1 2008-03-27 17:35:54 [24566] [6] DEBUG: data: 2e 30 00 .0. 2008-03-27 17:35:54 [24566] [6] DEBUG: Octet string dump ends. 2008-03-27 17:35:54 [24566] [6] DEBUG: WSP: decoded headers: 2008-03-27 17:35:54 [24566] [6] DEBUG: Content-Type: application/ smil; charset=utf-8; name= 2008-03-27 17:35:54 [24566] [6] DEBUG: Content-ID: 2008-03-27 17:35:54 [24566] [6] DEBUG: MIME-Version: 1.0 2008-03-27 17:35:54 [24566] [6] DEBUG: WSP: End of decoded headers. 2008-03-27 17:35:54 [24566] [6] DEBUG: WSP: decoding headers: 2008-03-27 17:35:54 [24566] [6] DEBUG: Octet string at 0x817ef30: 2008-03-27 17:35:54 [24566] [6] DEBUG: len: 48 2008-03-27 17:35:54 [24566] [6] DEBUG: size: 49 2008-03-27 17:35:54 [24566] [6] DEBUG: immutable: 0 2008-03-27 17:35:54 [24566] [6] DEBUG: data: 0a 9e 85 43 61 74 2e 6a 70 67 00 c0 3c 43 61 74 ...Cat.jpg..Cat 2008-03-27 17:35:54 [24566] [6] DEBUG: data: 2e 6a 70 67 3e 00 8e 43 61 74 2e 6a 70 67 00 4d .jpg..Cat.jpg.M 2008-03-27 17:35:54 [24566] [6] DEBUG: data: 49 4d 45 2d 56 65 72 73 69 6f 6e 00 31 2e 30 00 IME-Version.1.0. 2008-03-27 17:35:54 [24566] [6] DEBUG: Octet string dump ends. 2008-03-27 17:35:54 [24566] [6] DEBUG: WSP: decoded headers: 2008-03-27 17:35:54 [24566] [6] DEBUG: Content-Type: image/jpeg; name=Cat.jpg 2008-03-27 17:35:54 [24566] [6] DEBUG: Content-ID: Cat.jpg 2008-03-27 17:35:54 [24566] [6] DEBUG: Content-Location: Cat.jpg 2008-03-27 17:35:54 [24566] [6] DEBUG: MIME-Version: 1.0 2008-03-27 17:35:54 [24566] [6] DEBUG: WSP: End of decoded headers. 2008-03-27 17:35:54 [24566] [6] DEBUG: WSP: decoding headers: 2008-03-27 17:35:54 [24566] [6] DEBUG: Octet string at 0x81644b0: 2008-03-27 17:35:54 [24566] [6] DEBUG: len: 50 2008-03-27 17:35:54 [24566] [6] DEBUG: size: 51 2008-03-27 17:35:54 [24566] [6] DEBUG: immutable: 0 2008-03-27 17:35:54 [24566] [6] DEBUG: data: 0c 83 81 ea 85 41 72 32 2e 74 78 74 00 c0 3c 41 .Ar2.txt..A 2008-03-27 17:35:54 [24566] [6] DEBUG: data: 72 32 2e 74 78 74 3e 00 8e 41 72 32 2e 74 78 74
[Users] Re: Send Image MMS Problem
Please provide a bit more logging information so we can see what's going on. On Mar 22, 2008, at 01:27, Remon Magdy wrote: Hi There, Now I'm using content-url for sending an image, still unable to receive the image correctly, it is showing unable to open image on the handset, I can only receive text MMS when only I use the text parameter in the URL. For images I use the below URL http://XX.XX.XX.XX:10001/cgi-bin/sendmms?username=testpassword=testfrom=to=subject=testvasid=9894servicecode=2allow-adaptations=1content-url=http%3A%2F%2FXX.XX.XX.XX%3A8080%2Fimg%2Ftest.gif Any help on how to debug the problem, I'm unsure if the problem is from mbuni or the operator's side. And what is the use of content parameter and if possible please give me an example. Regards, Remon -Original Message- From: P. A. Bagyenda [mailto:[EMAIL PROTECTED] Sent: Fri 3/21/2008 6:26 AM To: Remon Magdy Cc: users@mbuni.org Subject: SUSPECT: Re: SUSPECT: Re: [Users] (no subject) It wouldn't IMHO, since it should not be referenced as an image. On Mar 20, 2008, at 19:14, Remon Magdy wrote: The text is not showing in my mobile and seems as a presentation with a missing attachment. I'm not sure if my SMIL is correct or not and the sending URL is correct or not. First I want to know, is it correct? Regards, Remon -Original Message- From: P. A. Bagyenda [mailto:[EMAIL PROTECTED] Sent: Thu 3/20/2008 3:06 PM To: Remon Magdy Cc: users@mbuni.org Subject: SUSPECT: Re: [Users] (no subject) Could you explain what you mean by 'weird presentation'? For starters you seem to be referencing a text file as an image in the SMIL On Mar 20, 2008, at 15:26, Remon Magdy wrote: Hello All, I'm trying to send a SMIL multimedia presentation through MBUNI to test it, but it always received in a weired presentation format on the phone. My SMIL document is something like that ?xml version=1.0 encoding=utf-8 standalone=no? smil body seq repeatCount=indefinite img src=http://XX.XX.XX.XX:8080/img/smil.txt; / /seq /body /smil And I use this URL http://XX.XX.XX.XX:10001/cgi-bin/sendmms?username=password=from=to=Xsubject=testvasid=9894servicecode=2allow-adaptations=1smil=%3C%3Fxml+version%3D%221.0%22+encoding%3D%22utf-8%22+standalone%3D%22no%22%3F%3E%3Csmil%3E%3Cbody%3E%3Cseq+repeatCount%3D%22indefinite%22%3E%3Cimg+src%3D%22http%3A%2F%2F75.125.38.194%3A8080%2Fimg%2Fsmil.txt%22+%2F%3E%3C%2Fseq%3E%3C%2Fbody%3E%3C%2Fsmil%3E What am I doing wrong? Regards, Remon ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] Mbuni as VAS; getting mms-service to deliver to email address via SMTP (rather than HTTP POST)
You are right. SMTP only works on the MMSC side. As-is you'd have to do a PHP or such web page that picks up the MMS and sends out email... Paul. On Mar 20, 2008, at 09:35, Giulio Harding wrote: I've gotten mbuni up and running in VAS mode (mmsbox), successfully receiving MMS via MM7 over HTTPS, and I'm trying to work out whether mbuni's SMTP support allows for mms-services to delivery MMS to external applications via SMTP rather than HTTP POST (e.g. using a mailbox as a bucket to collect MMS for a particular mms-service). I'm guessing no; mms-service seems to supports HTTP POST only, and I'd need an external application to receive the HTTP POST and then convert that to SMTP if I wanted to deliver to an email address. I just wanted to check with the mailing list if there might be some trick that would allow me to do something like this without relying on an external application - though it seems the SMTP functionality is MMSC-specific, and can't apply to a VAS? Thanks, -- Giulio Harding Systems Administrator m.Net Corporation Level 2, 8 Leigh Street Adelaide SA 5000, Australia Tel: +61 8 8210 2041 Fax: +61 8 8211 9620 Mobile: 0432 876 733 Yahoo: giulio.harding MSN: [EMAIL PROTECTED] http://www.mnetcorporation.com ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] (no subject)
Could you explain what you mean by 'weird presentation'? For starters you seem to be referencing a text file as an image in the SMIL On Mar 20, 2008, at 15:26, Remon Magdy wrote: Hello All, I'm trying to send a SMIL multimedia presentation through MBUNI to test it, but it always received in a weired presentation format on the phone. My SMIL document is something like that ?xml version=1.0 encoding=utf-8 standalone=no? smil body seq repeatCount=indefinite img src=http://XX.XX.XX.XX:8080/img/smil.txt; / /seq /body /smil And I use this URL http://XX.XX.XX.XX:10001/cgi-bin/sendmms?username=password=from=to=Xsubject=testvasid=9894servicecode=2allow-adaptations=1smil=%3C%3Fxml+version%3D%221.0%22+encoding%3D%22utf-8%22+standalone%3D%22no%22%3F%3E%3Csmil%3E%3Cbody%3E%3Cseq+repeatCount%3D%22indefinite%22%3E%3Cimg+src%3D%22http%3A%2F%2F75.125.38.194%3A8080%2Fimg%2Fsmil.txt%22+%2F%3E%3C%2Fseq%3E%3C%2Fbody%3E%3C%2Fsmil%3E What am I doing wrong? Regards, Remon ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] boundary in quotes
The quotes are put in by Kannels' gwlib/mime.c . But AFAIK really (according to the MIME RFC) they should not be the problem. For the non-MM7 headers again that should not matter but you can shave them off in mmlib/mm7_soap.c Would be happy to help more closely. Paul. On Mar 05, 2008, at 05:43, Muthu Nedumaran wrote: Hi All, I have been having some trouble in sending MMS MTs with mbuni. With suggestions that this may be caused by proprietary implementations/ extensions to the protocol, I did some extensive testing and tried working with the operator to figure where the differences were. I was able to make changes to the code to accommodate some of the specific requirements - which were very helpful. However, I'm still trying to figure where to make changes based on the final suggestion I received: --- begin The boundary should be enclosed in quotes: Content-Type: multipart/related; type=text/xml; start=s1202995795.2044686456.Ig.msg; boundary=_boundary_1055444703_1202995795_I_d_bd575326841 Also, the message contains some non-MM7 fields: X-Mms-MMS-Version: 1.0 .. X-Mms-Expiry: Thu, 21 Feb 2008 05:29:54 GMT .. Date: Thu, 14 Feb 2008 13:29:54 GMT .. Message-ID: Mbuni-qf5794.3.x412.78 --- end Anyone knows which source I can edit to implement this change - specifically the one to put boundary within quotes? Thanks. - MN ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] MP3 problem
On Jan 08, 2008, at 19:14, Stipe Tolj wrote:
Paul: Is there a phone-specific transcoding layer in Mbuni so far?
The idea is that the MMSC has a receiver-confirm push layer that
acts as filter while the receiver asks for the MMS. By this approach
you can assure that specific phones that don't support GIF image
will get a PNG or JPEG, and same can be performed for audio formats
in general. It's always better to reduce the quality drastically,
ie. by converting from mp3 11KHz mono to analog phone quality, then
to refuse to deliver the content in general.
Yes this layer exists (it is called content adaptation) and is the
one calling mpg123 and so on. What happens is that mbuni is converting
the message, then realising that the resulting message is too large
for the phone, and dropping it.
Stipe
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
___
Users mailing list
Users@mbuni.org
http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] Compiling mbuni on Solaris 10 / x86
Thank you. I have applied your patch (with some adjustments) to CVS, do let me know if it does not work. Paul. On Dec 19, 2007, at 21:08, Steven Xie wrote: Here is the patch for Solaris. It's built fine However I haven't done any testing. You may have to add -D_POSIX_PTHREAD_SEMANTICS in your Makefile to build it. This is the build enviorment I 'm using right now.I'll try it on SPARC later.It should be the same as x86. gcc -v Reading specs from /usr/sfw/lib/gcc/i386-pc-solaris2.10/3.4.3/specs Configured with: /builds/sfw10-gate/usr/src/cmd/gcc/gcc-3.4.3/ configure --prefix=/usr/sfw --with-as=/usr/sfw/bin/gas --with-gnu-as --with-ld=/usr/ccs/bin/ld --without-gnu-ld --enable-languages=c,c++ --enable-shared Thread model: posix gcc version 3.4.3 (csl-sol210-3_4-branch+sol_rpath) uname -a SunOS pingpong 5.10 Generic_120012-14 i86pc i386 i86pc P. A. Bagyenda wrote: Hi, would you kindly post a diff (unified) against latest CVS On Dec 18, 2007, at 20:28, Steven Xie wrote: I ported mbuni to Solaris 10 before. Just a few things needs to been changed. like below: Paul Bagyenda wrote: It would seem there are differences between Solaris and other unices. Can you poke around, see if you have a C include file sys/ file.h and see if flock is defined? Solaris sometimes requires certain macros to be defined before certain functions can be used. We use mostly OSX and Linux, so these sort of errors can be expected! Do let me know what you find, so we can see how best to resolve. Paul. On Dec 5, 2007 8:30 PM, Muthu Nedumaran [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Thank you, Paul. Made some progress - but there are still hickups. Here's a report : 1. I hit into the following error this time: mms_msg.c: In function `fixup_date': mms_msg.c:1354: error: too few arguments to function `asctime_r' mms_msg.c:1355: error: too few arguments to function `ctime_r' gmake[2]: *** [mms_msg.o] Error 1 I checked the man pages and it looks like asctime_r and ctime_r needed an extra parameter in Solaris - the buffer size. I made the changes as below: if (!tm || asctime_r(tm, buf, sizeof(buf)) == NULL) /* Then convert to ascii. If that fails...*/ ctime_r(t, buf, sizeof(buf)); /* .. just use current time. */ Using -D_POSIX_PTHREAD_SEMANTICS may have better portability. 2. Compilation passed the earlier stage and hit the same O_RDWR problem in mms_queue.c file. I added #include fcntl.h in this and continued... 3. I now get this error: mms_util.c: In function `lockfile': mms_util.c:820: error: `LOCK_NB' undeclared (first use in this function) mms_util.c:820: error: (Each undeclared identifier is reported only once mms_util.c:820: error: for each function it appears in.) mms_util.c:823: error: `LOCK_EX' undeclared (first use in this function) gmake[2]: *** [mms_util.o] Error 1 gmake[2]: Leaving directory `/usr/local/mbuni/mmlib' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/local/mbuni' gmake: *** [all] Error 2 Looks like flock() is not supported in Solaris -- is this true? flock is not desired under Solaris. I use fcntl instead. Appreciate your help, again. Regards, MN. - Original Message From: Paul Bagyenda [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] To: Muthu Nedumaran [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Cc: users@mbuni.org mailto:users@mbuni.org Sent: Thursday, December 6, 2007 1:00:30 AM Subject: Re: [Users] Compiling mbuni on Solaris 10 / x86 This could have to do with a missing include file. My guess is fcntl.h was not included in the file. I've made that change on CVS, do try that and see if it works fine. P. On Dec 5, 2007 7:37 PM, Muthu Nedumaran [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hello, I downloaded the cvs version of mbuni today (6 Dec, MYT). I was able to do bootstrap and configure. However, when I do a make (with gmake), I hit into problems. I've also tried the 1.3.0 version, the results are the same. Also the same with 'make' in Solaris. I'm using GCC 3.4.3 Are there any extra steps, keystrokes I need to perform for Solaris 10 / x86? It went though clean on my Mac OS X machine, through. Here's a fragment of the error thrown when did gmake: Making all in mmlib gmake[2]: Entering directory `/usr/local/mbuni-cvs-nov07/ mmlib' gcc -DHAVE_CONFIG_H -I. -I.. -I../mmlib -I../mmlib -g -O2 -DSunOS=1 -D_FILE_OFFSET_BITS=64 -I/usr/local/include/kannel -I/usr/local/gateway- 1.4.1 -g -O2 -fPIC -D_FILE_OFFSET_BITS=64 -I/usr/include/libxml2 -MT mms_mmbox.o -MD -MP -MF .deps/mms_mmbox.Tpo -c -o mms_mmbox.o mms_mmbox.c mms_mmbox.c: In function `mkdf': mms_mmbox.c:176: error: `O_RDWR' undeclared (first use in this function) mms_mmbox.c:176: error: (Each undeclared identifier is reported only once mms_mmbox.c:176: error: for each function it appears in.) mms_mmbox.c:176: error: `O_CREAT' undeclared (first use in this function) mms_mmbox.c:176: error: `O_EXCL' undeclared (first use
Re: [Users] Problems compiling
Compile against the Kannel given on the website. Note that you need not install the same Kannel as you compile with. On Dec 17, 2007, at 09:05, Aaron wrote: Paul, Just downloaded the latest, 1.4.1. On Dec 16, 2007 9:59 PM, Paul Bagyenda [EMAIL PROTECTED] wrote: Which version of Kannel are you compiling against? Paul. On Dec 17, 2007 8:31 AM, Aaron [EMAIL PROTECTED] wrote: I am getting the following errors when I try and compile v1.3.0 of mbuni. As far as I can tell I have kannel and all the prereqs compiled and installed just fine, but I get this error below: gcc -g -O2 -D_XOPEN_SOURCE=600 -D_BSD_SOURCE -O4 -Wall -D_FILE_OFFSET_BITS=64 -I/usr/include/openssl -I/home/drizzt/mms//include/kannel -g -O2 -D_XOPEN_SOURCE=600 -D_BSD_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include/libxml2 -I/usr/include/mysql -rdynamic -o mmsrelay mmsglobalsender.o mmsmobilesender.o mmsrelay.o -L/home/drizzt/mms//lib/kannel -lgw - lrt -lresolv -lnsl -lm -L/usr/lib /usr/lib/libxml2.so -lpcre -L/usr/lib/mysql /usr/lib/libmysqlclient_r.so libmmsc.a ../mmlib/libmms.a -lwap -lgwlib -lpthread -ldl -lcrypto -lssl ../mmlib/libmms.a(mms_util.o): In function `mms_load_core_settings': /home/drizzt/mbuni/mbuni- 1.3.0/mmlib/mms_util.c:109: undefined reference to `use_global_client_certkey_file' /home/drizzt/mbuni/mbuni-1.3.0/mmlib/mms_util.c:115: undefined reference to `use_global_server_certkey_file' /home/drizzt/mbuni/mbuni- 1.3.0/mmlib/mms_util.c:120: undefined reference to `use_global_trusted_ca_file' --Aaron ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] gwlib problem again on Mac OS X
Muthu, 1) Remove old libiconv and libxml2 2) Install new libiconv and libxml2 3) Install Kannel 4) Install mbuni That should work. You can also try installing fink, which is a much better means of managing GNU installs on OSX. I don't have a binary for Tiger/PPC. If it were Intel I could help... On Dec 11, 2007, at 10:33, Muthu Nedumaran wrote: Paul, There is no need for Rosetta as they are both the same architecture (PPC). When I remove the old libiconv.2.2.0.dylib file, Kannel would not compile. It fails saying that it can't locate file for -liconv So, it looks like kannel specifically wants 2.2.0 and mbuni is asking for something newer? The machine has a standard Tiger installation with all files installed in their default locations --- just wondering if there is an easier way to do this? I'll try compiling the iconv and libxml2 files. Alternatively, if there is a compiled binary for mbuni (Tiger/PPC) that will be really very helpful. MN. On Dec 11, 2007, at 2:53 PM, Paul Bagyenda wrote: They should work AFAIK once copied (because of Rosetta), but you need to ensure the old ones are no longer there. To upgrade, download the sources of iconv and libxml2, compile, install. You will want to ensure xml2-config is in the search path and is called before the older one. On Dec 11, 2007 9:35 AM, Muthu Nedumaran [EMAIL PROTECTED] wrote: I found libiconv.2.4.0.dylib and /usr/lib/libxml2.2.6.17.dylib in another Mac OS (PPC) machine. I'm not sure if I can just copy over these files to the /usr/lib dir of the machine I'm trying to compile mbuni. Anyways, I did that -- starting from make clean in Kannel and onwards. Hit into exactly the same problem at the same point of failure. I guess I can't just copy over the library files. Could you pls advice how I can do the upgrade of the libs? I only have command line access to the machine I need to install. Thanks so much for your help. MN - Original Message From: Paul Bagyenda [EMAIL PROTECTED] To: Muthu Nedumaran [EMAIL PROTECTED] Cc: users@mbuni.org Sent: Tuesday, December 11, 2007 1:03:38 PM Subject: Re: [Users] gwlib problem again on Mac OS X My guess is that the problem is related to libxml2, and the way it uses libiconv (for charset encoding conversion). You are using libxml2 v2.2. Upgrade to at least v2.6. If that succeeds then (hopefully) so should the compilation. While you are at it, you may also want to upgrade libiconv to v2.4 before updating libxml2, and see if that helps. On Dec 11, 2007 7:56 AM, Muthu Nedumaran [EMAIL PROTECTED] wrote: Paul, Thanks for the speedy response. I did a find on both the libs, and they are there: muthu$ sudo find / -name *libiconv* -print /Library/Documentation/Libraries/libiconv /usr/lib/libiconv.2.2.0.dylib /usr/lib/libiconv.2.dylib /usr/lib/libiconv.dylib /usr/lib/libiconv.la /usr/share/doc/libiconv muthu$ sudo find / -name *libxml2* -print /usr/include/libxml2 /usr/lib/libxml2.2.dylib /usr/lib/libxml2.dylib /usr/lib/libxml2.la /usr/share/doc/libxml2-2.6.16 Are they where they should be? Is there anything I need to add to ensure that config picks them up? Cheers! MN. - Original Message From: Paul Bagyenda [EMAIL PROTECTED] To: Muthu Nedumaran [EMAIL PROTECTED] Cc: users@mbuni.org Sent: Tuesday, December 11, 2007 12:02:43 PM Subject: Re: [Users] gwlib problem again on Mac OS X The part of the configure process that failed says: --- configure:21874: gcc -o conftest -g -O2 -DDARWIN=1 -O4 -Wall -I/usr/ include/openssl -I/usr/local/include/kannel -L/usr/local/lib/ kannel -lwap -lgwlib conftest.c -lgwlib -lssl -lpthread -ldl -L/ usr/lib -lcrypto -lssl 5 /usr/bin/ld: Undefined symbols: _libiconv _libiconv_close _libiconv_open _xmlAddEncodingAlias _xmlBufferAdd _xmlBufferCreate _xmlBufferFree _xmlCharEncInFunc _xmlCharEncOutFunc _xmlCleanupEncodingAliases _xmlFindCharEncodingHandler - which means that gwlib is in place but either a) libxml2 is older than v2.6 and/or b) libiconv development stuff is not installed or it is installed in a different location from what is expected. OSX definitely works (as it is primary development environment I use). Can you check that the above are installed, then install Kannel. On Dec 11, 2007 6:39 AM, Muthu Nedumaran [EMAIL PROTECTED] wrote: Hello, After repeated failures in compiling on Solaris, decided to do this on Mac OS instead. I was able to compile and run mbuni on my Intel MBP running Tiger. However, we need to run this on one of our PPC boxes - also running Tiger. 1. I downloaded kannel snapshot. Was able configure, make install and run. No problems here 2. Downloaded mbuni-1.3.0. bootstrap -- no problem! When I did a sudo ./configure it complains about gwlib required. I've searched the forum for this and there were others who had similar problems caused by the lib being out of date
Re: [Users] Questions about Mbuni capabilities
On Nov 17, 2007, at 10:55, Aaron wrote: So, to sum up this thread and try and avoid mis-interpretations: 1) Mbuni/Kannel can generate the WAP-Push SMS messages that can be sent via an SMS Aggregator to a mobile phone. That mobile phone would then follow its normal MMS routine. i.e. download the MMS message via the WAP link enclosed in the WAP-Push SMS message. This is all done over regular internet IP network. 2) Mbuni can also receive MMS messages via similar routine. Have an SMS message come in, be routed from the Aggregator to Mbuni, which then downloads the MMS message from the WAP link. This is all done over regular internet IP network. Alternatively, both 1 and 2 can be done either separately, or together over a GPRS serial attached modem. Yes You say below that the operators often block connecting to a non-operator WAP site? Are you referring to the WAP gateway setting on the mobile phone? Or the WAP APN Setting? And am I correct in saying that the WAP-Push message simply contains a URL, and that URL effectively is any internet routable IP address which happens to serve the MMS content? Because this kind of WAP-Push is received by the MMS client within the phone, the download will often be attempted over an MMS-specific APN. The settings I have seen typically block all URL requests via the MMS APN except to the operator MMSC Thank you, everyone, for your patience in answering my questions. It sounds like Mbuni is a great product, and once I get a little less confused and start to really understand the capabilities it probably will do exactly what we need. --Aaron On Nov 16, 2007 8:03 PM, P. A. Bagyenda [EMAIL PROTECTED] wrote: On Nov 16, 2007, at 22:46, Aaron wrote: Paul, Thank you for the quick response and the answers. I have a few more questions based on your responses. On the subject of sending to an Aggregator, I was refering to an SMS Aggregator, and using that to send the WAP-Push SMS messages. Would it be possible to send those messages out via the Aggregator instead of using a GPRS modem? You can of course send hte WAP-Push SMS, but note that WAP-Push is not enough for MMS delivery. When you refer to MM7, this would be a direct, internet IP based connection to the carriers SMPP? I am currently in the US and I don't believe we are able to get that kind of access, or not without alot of fees. MM7 is a direct IP protocol, however the SMPP reference was just by way of comparison (SMS vs MMS). MM7 has nothing to do with SMPP. When talking about having the WAP-Push message to the phone contain the IP which is a regular server hooked up to the internet with Mbuni, you said that the phones could pull the MMS message that way, Up to a point. What do you mean by that? What limitations would there be? You can send the notification to the phone and have it pull the message over IP if your operator does not block this (often they do). --Aaron On Nov 16, 2007 11:35 AM, Paul Bagyenda [EMAIL PROTECTED] wrote: Hi Aaron, answers below On 11/16/07, Aaron [EMAIL PROTECTED] wrote: I am evaluating Mbuni to use for my company, and I have a few questions. 1) From what I've read in google/mail list searches, would it be correct to say that Mbuni (with kannel) would be able to send an MMS to a MSISDN? Yes, 2) Going along with 1, if I currently have connection to an SMS aggregator, would it be possible to have Mbuni/Kannel push the SMS message through the aggregator and obviate the need for a GSM/GPRS modem? SMS Aggregator or MMS Aggregator? SMS and MMS work very differently from each other so you need to be sure. 3) What I've read indicates that Mbuni is currently unable to send an MMS messages to a carrier's MMSC directly and have the carrier worry about delivery supposing I have a GSM/GPRS modem, corect? It can send directly, using MM7 (think SMPP for MMS) or MM1 using a GPRS modem. 4) If using an aggregator is possible, the SMS WAP-Push message gets sent through there, all I need is a regular internet IP address for Mbuni/Kannel to have the mobile phone pull the MMS message from? Up to a point yes. Thank you very much for your replies. If some of the functionalityy does not currently exist, but would be desirable from the community, we might be interested in helping with the development. I am specifically thinking of connecting to an SMS aggregator, but it isn't limited to that. You will need to first be clear that the Aggregator can aggregate MMS. The MMS architecture is very different, and in some respects more complicated than SMS, so it is key that you understand it well before committing to the aggregator. --Aaron ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] Questions about Mbuni capabilities
On Nov 16, 2007, at 22:46, Aaron wrote: Paul, Thank you for the quick response and the answers. I have a few more questions based on your responses. On the subject of sending to an Aggregator, I was refering to an SMS Aggregator, and using that to send the WAP-Push SMS messages. Would it be possible to send those messages out via the Aggregator instead of using a GPRS modem? You can of course send hte WAP-Push SMS, but note that WAP-Push is not enough for MMS delivery. When you refer to MM7, this would be a direct, internet IP based connection to the carriers SMPP? I am currently in the US and I don't believe we are able to get that kind of access, or not without alot of fees. MM7 is a direct IP protocol, however the SMPP reference was just by way of comparison (SMS vs MMS). MM7 has nothing to do with SMPP. When talking about having the WAP-Push message to the phone contain the IP which is a regular server hooked up to the internet with Mbuni, you said that the phones could pull the MMS message that way, Up to a point. What do you mean by that? What limitations would there be? You can send the notification to the phone and have it pull the message over IP if your operator does not block this (often they do). --Aaron On Nov 16, 2007 11:35 AM, Paul Bagyenda [EMAIL PROTECTED] wrote: Hi Aaron, answers below On 11/16/07, Aaron [EMAIL PROTECTED] wrote: I am evaluating Mbuni to use for my company, and I have a few questions. 1) From what I've read in google/mail list searches, would it be correct to say that Mbuni (with kannel) would be able to send an MMS to a MSISDN? Yes, 2) Going along with 1, if I currently have connection to an SMS aggregator, would it be possible to have Mbuni/Kannel push the SMS message through the aggregator and obviate the need for a GSM/GPRS modem? SMS Aggregator or MMS Aggregator? SMS and MMS work very differently from each other so you need to be sure. 3) What I've read indicates that Mbuni is currently unable to send an MMS messages to a carrier's MMSC directly and have the carrier worry about delivery supposing I have a GSM/GPRS modem, corect? It can send directly, using MM7 (think SMPP for MMS) or MM1 using a GPRS modem. 4) If using an aggregator is possible, the SMS WAP-Push message gets sent through there, all I need is a regular internet IP address for Mbuni/Kannel to have the mobile phone pull the MMS message from? Up to a point yes. Thank you very much for your replies. If some of the functionalityy does not currently exist, but would be desirable from the community, we might be interested in helping with the development. I am specifically thinking of connecting to an SMS aggregator, but it isn't limited to that. You will need to first be clear that the Aggregator can aggregate MMS. The MMS architecture is very different, and in some respects more complicated than SMS, so it is key that you understand it well before committing to the aggregator. --Aaron ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] Sending multiple contents without a smil
Hi Angel, The short answer is that what you want to do is not possible, and you would not want to do that anyway as the resulting MM7/SOAP packet would not really make much sense. In theory the phones should understand and correctly handle any multipart formats but as you have discovered, the MMSC may or may not honour the format as sent. The best way to do this is do a SMIL file that references the parts. (And hope that the device can handle more than just a couple of parts in the MMS.) P. On Oct 26, 2007, at 20:55, qwerty wrote: Ok, I've found the following: If i sent a multipart/mixed or multipart/related mime with images, text, etc, to mbuni using content-url it will send a multifile/ related to the MMSC with two parts: First is a XML (the SOAP xml), and the second mime part is a multifile/(related|mixed) I sent in the first place. This is an issue since most MMSC doesn't convert that to phones defaults. I need to send it there the content sent to the MMSC is a N parts multipart/related message, where the first part is a SOAP XML and the rest of the parts are the file I send throw content- url, is that possible? Thanks, Angel 2007/10/24, qwerty [EMAIL PROTECTED]: Paul, Here is what I'm sending, it's a multipart/mixed genearted with Python's email module. I think it's ok, the only problem is that the image is a bmp. I'm calling sendsms with content-url: http://hosy:port/? username=upassword=pfrom=12345to=12345678vasid=vipriority=Normal subject=Url%20encodedallow-adaptations=1content-url=url-to-that - file-sending-headers-as-headers-and-not-part-of-the-message-body 2007/10/24, Paul Bagyenda [EMAIL PROTECTED]: Your best bet would be to point content-url to a multipart/mixed message formatted correctly. This should work. How exactly are you calling mmsbox to cause the crash? On 10/24/07, qwerty [EMAIL PROTECTED] wrote: Hi to all, I need to send two files, a image and a text file, as a VAS. Is that posible using content-url? I've trying sending a file to content-url like this: --===0337595869== Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Esta es la tierra --===0337595869== Content-Type: image/bmp MIME-Version: 1.0 Content-Transfer-Encoding: base64 iVBORw0KGgoNSUhEUgAAAGBgCAYAAADimHc4AXNSR0IArs4c6QRnQU 1BAACx ... FZNZtj+rrOV8QX3bneLmFc8qlqx7Xdu+9V1N2 +Z3C5ZteF3SvPJZ1oIld6Jy68/7JxTvdwlIXKVn 7lo6dbaio8Tw0VI9+DP/3cP6T3z/ /wdctPS8B2aEdABJRU5ErkJggg== --===0337595869==-- With the headers ok, but it doesn't work, in fact I get this trace from mmsbox before an assert: 2007-10-23 17:17:06 [21082] [5] DEBUG: Queued to thread 0 for /var/ lib/mbuni/spool//mmsbox _outgoing/0/s1/qf4224.1.x82.73, sendt=1193174224, tnow=1193174226 2007-10-23 17:17:06 [21082] [7] DEBUG: WSP: decoding headers: 2007-10-23 17:17:06 [21082] [7] DEBUG: Octet string at 0x815a8a0: 2007-10-23 17:17:06 [21082] [7] DEBUG: len: 45 2007-10-23 17:17:06 [21082] [7] DEBUG: size: 46 2007-10-23 17:17:06 [21082] [7] DEBUG: immutable: 0 2007-10-23 17:17:06 [21082] [7] DEBUG: data: 3d 3d 3d 3d 3d 3d 3d 3d 3d 3d 3d 3d 3d 3d 30 33 ==03 2007-10-23 17:17:06 [21082] [7] DEBUG: data: 33 37 35 39 35 38 36 39 3d 3d 0a 43 6f 6e 74 65 37595869==.Conte 2007-10-23 17:17:06 [21082] [7] DEBUG: data: 6e 74 2d 54 79 70 65 3a 20 74 65 78 74nt-Type: text 2007-10-23 17:17:06 [21082] [7] DEBUG: Octet string dump ends. 2007-10-23 17:17:06 [21082] [7] WARNING: Skipping faulty header. 2007-10-23 17:17:06 [21082] [7] WARNING: Parse error reading mime body [hlen=45, dlen=61, left=33730]! 2007-10-23 17:17:06 [21082] [7] ERROR: mms_queue_getdata: Failed to decode data file for queue entry qf4224.1.x82.73 in /var/lib/mbuni/spool//mmsbox_outgoing 2007-10-23 17:17:06 [21082] [7] PANIC: mms_msg.c:1216: mms_messagetype: Assertion `msg' failed. 2007-10-23 17:17:06 [21082] [7] PANIC: ./mmsbox(gw_panic+0xdc) [0x80899ec] 2007-10-23 17:17:06 [21082] [7] PANIC: ./mmsbox(mms_messagetype +0x4f) [0x805bd2f] 2007-10-23 17:17:06 [21082] [7] PANIC: ./mmsbox [0x8059912] 2007-10-23 17:17:06 [21082] [7] PANIC: ./mmsbox [0x80610f6] 2007-10-23 17:17:06 [21082] [7] PANIC: ./mmsbox [0x8080b70] 2007-10-23 17:17:06 [21082] [7] PANIC: /lib/libpthread.so.0 [0xb7e2b294] 2007-10-23 17:17:06 [21082] [7] PANIC: /lib/libc.so.6(__clone+0x5e) [0xb7c8932e] Thanks, Angel ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] Something to keep logs?
Documentation bug! Fixed. On Oct 16, 2007, at 15:19, qwerty wrote: Ok, I'll change, just to fix it: This module provides Queue management for mbuni using PostgreSQL as the storage engine. To use it, you need only add two lines to the mbuni config 'core' group: That's in the CVS Readme.txt file. Thanks! Angel 2007/10/16, Paul Bagyenda [EMAIL PROTECTED]: these config parameters should be within config group 'mbuni' not 'core' On 10/16/07, qwerty [EMAIL PROTECTED] wrote: 2007-10-15 20:13:29 [12024] [0] INFO: Debug_lvl = -1, log_file = none, log_lvl = 0 2007-10-15 20:13:29 [12024] [0] INFO: field `queue-manager-module' is not expected within group `core' at line 5 in conf file - skipped 2007-10-15 20:13:29 [12024] [0] INFO: field `queue-module-init- data' is not expected within group `core' at line 6 in conf file - skipped Any ideas? I'm running mmsbox from CVS co today. 2007/10/10, qwerty [EMAIL PROTECTED]: Thanks, I'm using PostgreSQL for most of my projects here so it'll be perfect :D I'll check the CVS now. Greets, Angel 2007/10/10, Paul Bagyenda [EMAIL PROTECTED]: Even better, but only for PostgreSQL at this stage. (I'll skip over the PostgreSQL evangelism for now, but of course MySQL implementations are welcome.) As of CVS (and naturally in next release), you can store all your queue data (received/sent messages) within PostgreSQL, and archive it by default. Take a peep inside the extras folder in the source, and the documentation that comes with CVS. P. On 10/10/07, qwerty [EMAIL PROTECTED] wrote: Hi, Is there a solution like SQLBox from Kannel but for mbuni? Thanks, Angel ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] MM7 problem
Mystery really. There must be something slightly mal-formed about the message body in the MM7 packet, but it is not obvious to the eye. Perhaps looking at the binary MMS packet would help. Also perhaps a full log on the MMSC side. On Oct 05, 2007, at 14:32, Kristof Szabo wrote: My script. I used it with a Nokia MMSC before. Am Freitag, den 05.10.2007, 14:25 +0300 schrieb P. A. Bagyenda: Who is doing the MM7 packet composition/creation, your script or Mbuni? On Oct 05, 2007, at 13:30, Kristof Szabo wrote: Thank's for the answer! Mbuni is the MMSC. When I open the downloaded message the phone (N70) says: Unable to display message. Select 'Objects' in options menu for details. Under Objects the image is listed, with it's filename, but when I try to open it, it says: Unable to open image. Altough it seems worthless, I tried with other content types eg. image/tiff. Of course it doesn't work. I also tried 8bit as transfer encoding, the result is the same. Am Freitag, den 05.10.2007, 12:41 +0300 schrieb Paul Bagyenda: As far as mbuni is concerned, text and image are no different. It may be that the MMSC side (if it is not mbuni) is not quite handling the base64-encoded content correctly. Or the device does not like the image type. A quick test is to try and look at the message properties on the device (nokia series 60 allow this at least) to figure out if the device is receiving ALL content elements. For this case, CVS will not be doing anything differently. On 10/5/07, [EMAIL PROTECTED] kris- [EMAIL PROTECTED] wrote: Hello, I\'d like to send MMS via the MM7 interface of Mbuni. Everything \'s fine with messages containing smil+text, but I cannot send messages containing smil nd image. Both arrive to the handset, but the image part isn\'t shown in the presentation and cannot be opened. Any idea? Here\'s my SOAP request: [EMAIL PROTECTED]:~/projects/mmstest$$ date; cat image3.smil | perl smil2mm7.pl +x Thu Oct 4 16:50:38 CEST 2007 Opening mmsc connection. POST / HTTP/1.1 Content-Type: multipart/related; type=text/xml; boundary==_Part_1334_4321325.1167917985736 Content-Length: 4522 Host: localhost:2081 Authorization: Basic x SOAPAction: --=_Part_1334_4321325.1167917985736 Content-Type: text/xml; charset=UTF-8 soap-env:Envelope xmlns:soap-env=http://schemas.xmlsoap.org/ soap/envelope/soap-env:Header TransactionID xmlns=http://www.3gpp.org/ftp/Specs/archive/ 23_series/23.140/schema/REL-5-MM7-1-2 soap- env:mustUnderstand=1MMS_74_20070104143945705/TransactionID /soap-env:Header soap-env:Body SubmitReq xmlns=http://www.3gpp.org/ftp/Specs/archive/ 23_series/23.140/schema/REL-5-MM7-1-2 MM7Version5.3.0/MM7Version SenderIdentification VASPIDx/VASPID VASIDx/VASID SenderAddress Number+x/Number /SenderAddress /SenderIdentification Recipients To Number+x/Number /To /Recipients ServiceCodeVM2MSS2/ServiceC ode MessageClassInformational/MessageClass TimeStamp2007-10-01T12:50:45+01:00/TimeStamp ExpiryDatePT1439M/ExpiryDate DeliveryReportfalse/Deliver yReport ReadReplyfalse/ReadReply PriorityNormal/Priority Subject/Subject Content href=comverse.cid allowAdaptations=true/ /SubmitReq /soap-env:Body /soap-env:Envelope --=_Part_1334_4321325.1167917985736 Content-Type: multipart/related; type=application/smil; boundary==_Part_1332 _5551572.1167917985629; start=smil Content-Id: comverse.cid --=_Part_1332_5551572.1167917985629 Content-Type: image/jpeg; name=image2.jpeg Content-Transfer-Encoding: base64 Content-Disposition: inline; filename=image2.jpeg Content-ID: image2.jpeg Content-Location: image2.jpeg /9j/4AAQSkZJRgABAQIAJQAlAAD//gAXQ3JlYXRlZCB3aXRoIFRoZSBHSU1Q/ 9sAQwABAQEBAQEB AQEBAQEBAQEBAQEBAQEBAQEBAQEBAQ EBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEB / 9sAQwEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEB AQEBAQEB AQEBAQEBAQEBAQEB/8AAEQgAIAAgAwEiAAIRAQMRAf/ EABkAAQEAAwEAAAkIBQYK Cgf/xAAjEAACAgMBAAIDAAMAAA AEBQMGAgcIAQkVExQWERcm/ 8QAGAEAAgMA BAUCBwj/xAAiEQADAQEBAQACAgMBAAACAwQBBQYHERMSIRQWIzP/ 2gAMAwEAAhEDEQA/ AOXX4/Pj8SboSQbt3bB+9rE77cCk0kBuWCXcCwSzUTN+/ ZojRGiREkaCHBqlQZwLt07BzPPzBrQI w1zS7cnZ3NnGrNNqGelWtbIMCQ0GqO sdcrkNdRLGZHjGFiB66Mo9YZAvmZzj39ulkPh4nyyxhPZF rkaUebBd7bIZ8ucjLEOofDqrIwOqGlai2VuCMGdGro9eaF+krj2MLVmYd/ MU8isCMPWAT5aQ3jsw T2JypHynmHS56T5KOWbLq3YKCg/HvHQiJOBUNnnNS8/33blM1EqT9m+Kwf2P/ pZqhkBuBUWE5Ed/ hGtqbOJ/ImFpm8oE8/5xmfMPAjzE /UWecR2qO30uWda/ RWqBtvQ4c1Wap0xnLG6vmroBvMnmwUFm 9J9Niabcbu9v+w9raC88NxyBJPRiihUWgpNbF/ghYOMaCgqglkNBs3Tz8IBaip7W/ e3I3UbP3UL5 YcvktRydWpqO6qhXiK7eWeZEzEBcN6I0uFY9ODZql/q8SzkKCghk +NRBVmNs5lxHgPzvL46B9XLC 9xc+KDptdqwcJb3QMTGbxnShwh8cJ7
Re: [Users] MM7 problem
Who is doing the MM7 packet composition/creation, your script or Mbuni? On Oct 05, 2007, at 13:30, Kristof Szabo wrote: Thank's for the answer! Mbuni is the MMSC. When I open the downloaded message the phone (N70) says: Unable to display message. Select 'Objects' in options menu for details. Under Objects the image is listed, with it's filename, but when I try to open it, it says: Unable to open image. Altough it seems worthless, I tried with other content types eg. image/tiff. Of course it doesn't work. I also tried 8bit as transfer encoding, the result is the same. Am Freitag, den 05.10.2007, 12:41 +0300 schrieb Paul Bagyenda: As far as mbuni is concerned, text and image are no different. It may be that the MMSC side (if it is not mbuni) is not quite handling the base64-encoded content correctly. Or the device does not like the image type. A quick test is to try and look at the message properties on the device (nokia series 60 allow this at least) to figure out if the device is receiving ALL content elements. For this case, CVS will not be doing anything differently. On 10/5/07, [EMAIL PROTECTED] kris- [EMAIL PROTECTED] wrote: Hello, I\'d like to send MMS via the MM7 interface of Mbuni. Everything \'s fine with messages containing smil+text, but I cannot send messages containing smil nd image. Both arrive to the handset, but the image part isn \'t shown in the presentation and cannot be opened. Any idea? Here\'s my SOAP request: [EMAIL PROTECTED]:~/projects/mmstest$$ date; cat image3.smil | perl smil2mm7.pl +x Thu Oct 4 16:50:38 CEST 2007 Opening mmsc connection. POST / HTTP/1.1 Content-Type: multipart/related; type=text/xml; boundary==_Part_1334_4321325.1167917985736 Content-Length: 4522 Host: localhost:2081 Authorization: Basic x SOAPAction: --=_Part_1334_4321325.1167917985736 Content-Type: text/xml; charset=UTF-8 soap-env:Envelope xmlns:soap-env=http://schemas.xmlsoap.org/soap/ envelope/soap-env:Header TransactionID xmlns=http://www.3gpp.org/ftp/Specs/archive/ 23_series/23.140/schema/REL-5-MM7-1-2 soap- env:mustUnderstand=1MMS_74_20070104143945705/TransactionID /soap-env:Header soap-env:Body SubmitReq xmlns=http://www.3gpp.org/ftp/Specs/archive/ 23_series/23.140/schema/REL-5-MM7-1-2 MM7Version5.3.0/MM7Version SenderIdentification VASPIDx/VASPID VASIDx/VASID SenderAddress Number+x/Number /SenderAddress /SenderIdentification Recipients To Number+x/Number /To /Recipients ServiceCodeVM2MSS2/ServiceC ode MessageClassInformational/MessageClass TimeStamp2007-10-01T12:50:45+01:00/TimeStamp ExpiryDatePT1439M/ExpiryDate DeliveryReportfalse/Deliver yReport ReadReplyfalse/ReadReply PriorityNormal/Priority Subject/Subject Content href=comverse.cid allowAdaptations=true/ /SubmitReq /soap-env:Body /soap-env:Envelope --=_Part_1334_4321325.1167917985736 Content-Type: multipart/related; type=application/smil; boundary==_Part_1332 _5551572.1167917985629; start=smil Content-Id: comverse.cid --=_Part_1332_5551572.1167917985629 Content-Type: image/jpeg; name=image2.jpeg Content-Transfer-Encoding: base64 Content-Disposition: inline; filename=image2.jpeg Content-ID: image2.jpeg Content-Location: image2.jpeg /9j/4AAQSkZJRgABAQIAJQAlAAD//gAXQ3JlYXRlZCB3aXRoIFRoZSBHSU1Q/ 9sAQwABAQEBAQEB AQEBAQEBAQEBAQEBAQEBAQEBAQEBAQ EBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEB / 9sAQwEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQ EBAQEB AQEBAQEBAQEBAQEB/8AAEQgAIAAgAwEiAAIRAQMRAf/ EABkAAQEAAwEAAAkIBQYK Cgf/xAAjEAACAgMBAAIDAAMAAA AEBQMGAgcIAQkVExQWERcm/ 8QAGAEAAgMA BAUCBwj/xAAiEQADAQEBAQACAgMBAAACAwQBBQYHERMSIRQWIzP/ 2gAMAwEAAhEDEQA/ AOXX4/Pj8SboSQbt3bB+9rE77cCk0kBuWCXcCwSzUTN+/ ZojRGiREkaCHBqlQZwLt07BzPPzBrQI w1zS7cnZ3NnGrNNqGelWtbIMCQ0GqO sdcrkNdRLGZHjGFiB66Mo9YZAvmZzj39ulkPh4nyyxhPZF rkaUebBd7bIZ8ucjLEOofDqrIwOqGlai2VuCMGdGro9eaF+krj2MLVmYd/ MU8isCMPWAT5aQ3jsw T2JypHynmHS56T5KOWbLq3YKCg/HvHQiJOBUNnnNS8/33blM1EqT9m+Kwf2P/ pZqhkBuBUWE5Ed/ hGtqbOJ/ImFpm8oE8/5xmfMPAjzE /UWecR2qO30uWda/ RWqBtvQ4c1Wap0xnLG6vmroBvMnmwUFm 9J9Niabcbu9v+w9raC88NxyBJPRiihUWgpNbF/ghYOMaCgqglkNBs3Tz8IBaip7W/ e3I3UbP3UL5 YcvktRydWpqO6qhXiK7eWeZEzEBcN6I0uFY9ODZql/q8SzkKCghk +NRBVmNs5lxHgPzvL46B9XLC 9xc+KDptdqwcJb3QMTGbxnShwh8cJ7 gkNaEsHLeqZxxel2kU4w1nVSPSH0c5NQmPjpMbbV4W6e1T bZqpNqu17AjxBCYiWrVVYtl5qTAczDLzKOFmBX4SgjgioSQjVbpcqZx5j4nRCTpj1LNh0 C8Svdp7 J5sirvSVHtY1nSnP9dPItsITIGexql6uBJBbO0tjQrJGQJKZ9lTWRDKN5nZSK6yauWx7N oyhgR8V /R+xj2PCfU/JHyfVQS1u4HrEcZ8LZX zMzThocYNDA/m39v60szndKID/ AOar1SWUGVAjy2y9jzvT GnmuYsLeadQOFgMH+nAGaO/y/A4OkQ/ vnbuf2SCapejd7a3Z9R8jLH2ofTrVIvOqG6qipVpyM2d5
Re: [Users] Mbuni behavior with malformed MMS
That MIME module has had its issues, so I would not be surprised that it crashes on malformed input. Without a log it is not easy to find offending code (i.e. code that should properly handle such problems)... Let me know if you are able to reproduce it... On Oct 03, 2007, at 17:31, Gabi Mahu wrote: Thank you for your reply, Paul. So, I understand that there are only two options for a bad MMS scenario a) mmsbox crashes b) mmsbox discards the message and creates a http response with a 4xx code and an error message, the choice between a) and b) depending on the actual content of the MMS. Unfortunately, I have no logs with mmsbox crashing, but I remember that when we encountered the situation described in my previous mail, the one with the multipart content missing, we solved it with a small hack in mime.c from the kannel sources. If I am not mistaking, there was a method, mime_something_to_entity, that at some point parses the boundary blocks in a loop. In that loop, since our actual block was only \r\n\r\n, some string operations caused the segmentation fault. Also, just to be on the safe side, we surrounded the recursive call in a string length sanity check for the boundary block . That did the trick, but it was just a small local fix. I hope that this can still help you somehow. Thanks again, Gabi Paul Bagyenda [EMAIL PROTECTED] wrote: The answer is it depends. In general it should return an error, but I would not rule out crashing. If you have a trace of such a crash, pray share as that helps improve the code. Paul. On 10/3/07, Gabi Mahu [EMAIL PROTECTED] wrote: Hello all, I am using mmsbox, mmsproxy and mmsrelay without any problems in a small project, a small application that sends a constructed MMS to mmsbox. I just have some questions regarding the behavior of Mbuni when a malformed MMS is sent to mmsbox. When I say malformed, I mean any kind of multipart headers or multipart content errors. At some point, due to some bugs, the MMS message that was created by the application was corrupted. Everything that was between the multipart boundaries (where headers and content for an images should have been, for example...), except the pair of \r\n, was missing. Mmsbox crashed due to a segmentation fault, caused by some string manipulation for the empty multipart. The code that generates the MMS is out of my reach now, so I can't answer my question by modifying the way the MMS is created and observing mmsbox reactions. And the application seams to works without a flaw now, so That is way I am writing this email. So, if someone could please explain how does mmsbox react when a corrupt MMS arrives? It forwards the MMS to mmsc, even though it doesn't understand it (it can't parse it, or finds some bad headers...), and responds with 200ok, or discards the message and answers with some 4xx code, or what? (I did leave out it crashes on purpose, because I hope that is not the case...) Thank you for your time Gabi Mahu Don't let your dream ride pass you by. Make it a reality with Yahoo! Autos. ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users Check out the hottest 2008 models today at Yahoo! Autos. ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] Problem with setup of mbuni
On Oct 01, 2007, at 17:07, Theis Borg wrote: Thanks for the quick reply Paul. The two checks: 1. Tried to do the interference test on the companys flatscreen TV – no interference available when sending an SMS to myself. Will test at home where I have available interference :-) Yes they don't react. CRTs do. 2. Yes – my phone is setup to point at my server. The phone must be connected to the MMSC – otherwise I would not be able to send the MMS into the system – right? Indeed. Apologies. I didn't understand. The project startet with me going to make the services only, then it evolved to include the VAS as well. Unfortunately our customer is _very_ slow to create the connection between their MMSC and our VAS. So we tried with an other customer. Same story – weeks went by. So I decided that our company needs our own MMSC so we can demo our products for potential customers. The idea is that when the customer at some point opens up for the connection we will simply point their MMSC to our VAS. Sothats why I have the full setup with MMSC and VAS. One thing at a time. My first test will not include the VAS – just a simple test that the MMSC works and that we can send and receive MMS’es. Test two will include the VAS and the services. I hope I will be back with an answer on the interference test tonight. Again: thanks for your help. That indeed is the first test: To see if your phone is receiving any SMS. Be sure as well that you have concatenate = true set in your send- sms-user config of Kannel. This is a common cause of problems: MMS notifications will typically consist of 2 or more concatenated SMS, which Kannel must split right. q:o)Theis -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Bagyenda Sent: 1. oktober 2007 15:27 To: Theis Borg Cc: users@mbuni.org Subject: Re: [Users] Problem with setup of mbuni Hi, Sounds like your phone may not be receiving the notification, or your phone has not been configured to talk to the Mbuni MMSC. To check if your phone is receiving the notification, you want to check if it shows any activity (one crude way is to have it near a radio or TV and watch out for any interference on the radio/TV consistent with a phone transacting with the network). For the second step, you need to check that your phone's MMSC address is the HTTP URL of the mbuni MMSC, not that of your operator. The other area you need to be clear on is whether you want to run your own MMSC (seems like that's what you've done) or merely want a VAS GW for sending/receiving messages from your existing operator. A bit confusing at first I know, but with help clarity can be achieved! Paul. On 10/1/07, Theis Borg [EMAIL PROTECTED] wrote: Hi all. I'm trying to setup a complete solution with kannel, MMSC, VAS and services. Installation of packages went fine. Kannel is connected to operator and can send SMSes. My first test is now to post an MMS to myself. Sending the MMS looks fine – the mmsproxy/mmsrelay catches the MMS and tells the Kannel to push out a notification that a MMS is ready for download. The smsbox/bearerbox receives the notification message and pushes it to the phone: 2007-10-01 13:58:05 [19197] [2] DEBUG: HTTP: Creating HTTPClient for `127.0.0.1'. 2007-10-01 13:58:05 [19197] [2] DEBUG: HTTP: Created HTTPClient area 0x814f088. 2007-10-01 13:58:05 [19197] [3] INFO: smsbox: Got HTTP request / cgi-bin/sendsms from 127.0.0.1 2007-10-01 13:58:05 [19197] [3] INFO: sendsms used by tdc 2007-10-01 13:58:05 [19197] [3] INFO: sendsms sender:tdc:10505 (127.0.0.1) to:004529492804 msg:ESC^F^C¾¯204214202230- qf9884.3.x983.31 2007-10-01 13:58:05 [19197] [3] DEBUG: Stored UUID 89ab22dc-2ce8-4484-8d24-3278949e2e90 2007-10-01 13:58:05 [19197] [3] DEBUG: message length 131, sending 1 messages 2007-10-01 13:58:05 [19197] [3] DEBUG: Status: 202 Answer: Sent. 2007-10-01 13:58:05 [19197] [3] DEBUG: Delayed reply - wait for bearerbox 2007-10-01 13:58:05 [19197] [0] DEBUG: Got ACK (0) of 89ab22dc-2ce8-4484-8d24-3278949e2e90 2007-10-01 13:58:05 [19197] [0] DEBUG: HTTP: Resetting HTTPClient for `127.0.0.1'. And then nothing happens... Anyone else have the same problem? How can I debug what went wrong? Hope you guys can help an mbuni newbie... BR q:o) Theis ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
[Users] Commercial licensing for Mbuni now available
Digital Solutions is pleased to announce the general availability of commercial Mbuni licensing, through our partnership with Skycore LLC. This licensing covers a number of areas, details of which may be found at the following links: Press Release: http://www.skycore.com/press.php?press=11 Commercial components: http://www.mbuni.org/commercial.shtml Thanks, Paul. ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] Using mbuni MM7 with external mmsc provider
Yes it is. Suggestion is to read the manual, look at the sample configs, as the configuration is not necessarily simple as it depends on your setup. On Sep 03, 2007, at 15:49, Rachid Rhouddani wrote: Hi, how i can use mbuni for connecting and sending MMS to an external mmsc using MM7 http soap? If this solution is possible, please suggest a configuration for this Thanks, Rachid Rhouddani ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
[Users] Mbuni 1.3.0 released
Hello, We have put out a new release of Mbuni, please find details on the website. Mostly this represents all the changes that have over the past eight months taken place (bug fixes, minor enhancements, etc). We will also shortly be announcing some commercial add-ons, in preparation of which you will see certain notes in Changelog file. Looking ahead, Mbuni really has matured in our view. In the main, what is required are the little bits of add-ons that can improve useability. Which is what changes since the last release have been mostly about. Also, one of the more requested features has been the ability to receive and send MMS using a GPRS/GSM modem on the VAS side. Generally we know how to do it, but have had a number of false starts caused by using the wrong hardware. It looks like we need a regular GPRS modem, not a phone that has a built-in modem (because this captures the MMS notification). The other missing component (concatenated MO SMS handling in Kannel) is now in place. Generally we consider this a low priority issue, but if somebody is interested in it, we can provide direction or they can provide the GPRS modem and we will get it working. Paul ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] Receiving MMSC submition status
Short answer: No because this is not the design. Mbuni first queues the message locally then tries to deliver... On Jul 25, 2007, at 19:21, Pedro Miguel Duque wrote: Hi all, Is there a way to make a direct submition to the MMSC using Mbuni as a VAS GW? The problem is: I submit the MMS into mbuni using the sendmms interface. Mbuni stores the MMS and give an Ok response. As soon as Mbuni submits the MMS into MMSC sometimes gets an error like: 2007-07-25 09:01:10 [24604] [11] INFO: parse.soap, h=TransactionID, [EMAIL PROTECTED] 2007-07-25 09:01:10 [24604] [11] INFO: parse.soap, h=Fault, v=! 2007-07-25 09:01:10 [24604] [11] INFO: parse.soap, h=faultcode, v=SOAP-ENV:Server! 2007-07-25 09:01:10 [24604] [11] INFO: parse.soap, h=faultstring, v=General service error! 2007-07-25 09:01:10 [24604] [11] INFO: parse.soap, h=MessageType, v=RSErrorRsp! 2007-07-25 09:01:10 [24604] [11] INFO: parse.soap, h=MM7Version, v=5.3.0! 2007-07-25 09:01:10 [24604] [11] INFO: parse.soap, h=Status, v=! 2007-07-25 09:01:10 [24604] [11] INFO: parse.soap, h=StatusCode, v=4000! 2007-07-25 09:01:10 [24604] [11] INFO: parse.soap, h=StatusText, v=General service error! 2007-07-25 09:01:10 [24604] [11] INFO: parse.soap, h=Details, v=3807:HLR lookup failed! 2007-07-25 09:01:10 [24604] [11] INFO: Send to MMSC[12089], failed, code=[4000=General service error], detail=3807:HLR looku p failed 2007-07-25 09:01:10 [24604] [11] INFO: Sent to MMC[12089], code= [4000=General service error], msgid [(none)] I would like to catch this error in order to handle it properly in mbuni. Is there any way to do it? Best regards, Pedro Duque ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] MM7 and EAIF documentation
Hello Angel, Not sure I understand your question, but let me try and provide some pointers: MM7/EAIF: Poke around forum.nokia.com -- there is a spec there somewhere. MM7/SOAP: 3GPP2 TS 23.140 I believe provides a full explanation of MM7/SOAP, complete with examples. On Jul 18, 2007, at 15:08, qwerty wrote: Hi, I've been learning how to setup a VASP gateway with mbuni but now I'm in the middle of some protocol related issues and I wanted to check in the protocols documentation about how they should be implemented. In resume: Can anyone point me to the MM7 documentation and the EAIF documentation? I've try the links in mbuni homepage and the one about eaif doesn't seem to work, and for MM7 is there a better (more complete) documentation that X.S0016-370_v1.0_022404.pdf ? Sorry for the (kind) offtopic, but I don't know any other places where this can be asked. Thanks, Angel ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] Loop Back
At the moment this is not possible. There are a few people working to get this going though, so that you can receive mms (to mmsbox) via a GPRS modem. At the moment only MM7 is supported. On Jul 10, 2007, at 18:42, Ding wrote: Hi List, Has anybody tried a loop back? I have setup mbuni and kannel and as of the moment, I am trying to do a loop back. I do an http get to send an mms, the url is like this. http://localhost:10001/cgi-bin/sendmms? to=92764411username=testerpassword=foobarvasid=newscorpfrom=927644 11text=testing The mmsrelay,mmsproxy,mmsbox is running together with bearerbox,wapbox of kannel. and carefully map their ports in their config. And also plug with my gprs modem. Of all this running processes, I trace the message successfully been forwarded from one process to another. The first message being sent is the mms indication. mmsrelay sends the message to smsbox for the sms notification. smsbox successfully send the message and after a while it received the sms it just send since it was send to its self. My question is, at to this point where I have received the mms indication. How could I pass this message to mbuni so that it will process it. I just end the flow inside the 'sms-service' of kannel and still reading how can I pass this back to mbuni for processing. Or this could be answered easily by the question how does mbuni received mms? Thanks, Ding ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] fetching mms attachments from filesystem
If you are using latest CVS then simply use file://path_to_image_file and it will fetch the message. On Jul 11, 2007, at 09:58, hinoglu wrote: hi, i'm using mbuni as gateway to providers mmsc and currently giving the url for the madia content in smil like: ... img src='http://localhost/images/img.gif' ... how can i make mbuni fetch the mms media content from the filesystem as below ? img src='/images/img.gif' ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] Receiving MMS with mbuni in smsc=at mode
any offlist discussions regarding developments are welcome :) On Jun 27, 2007, at 08:25, greg giannis wrote: Hi, I am also interested in implementing this functionality with Mbuni. Could I be included in this off list support please? Thanks Greg On 27/6/07 3:02 PM, P. A. Bagyenda [EMAIL PROTECTED] wrote: Basically it entails receiving the notification sms from the modem, parsing it, then fetching the message. Not difficult, if you want to help do it, contact me offlist and I'll be happy to help. On Jun 26, 2007, at 18:06, Stephen Keegan wrote: thanks for the info. How would I go about achieving this now? I am willing to try with Mbuni but would be willing to try any other solutions. I'd like to program myself (in any language). Anybody got any advice on this? at the moment this does not work... It is planned, but currently stuck at low priority :) On Jun 26, 2007, at 15:21, Stephen Keegan wrote: Hi, I have a gprs modem connected to my mbuni box. What I want to do is to enable it to receive MMS messages (sent from ordinary mobile phones). I have searched all the documentation and message forums but have been unable to get a definitive answer as to whether this is possible. Is it possible? Do anybody have an example of how it can be done? regards, Stephen. ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users http:// lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] HTTP returned status = 500!
mm7-soap-xmlns but only with current CVS On Jun 27, 2007, at 12:43, Nii Ako Ampa-Sowa wrote: Which parameter in the config file does this information go to? I can't seem to find one for specifying the namespace.. Thanks, Nii. On 6/27/07, P. A. Bagyenda [EMAIL PROTECTED] wrote: exactly as I thought. You want to ask the operator what URI you should use for the MM7 namespace. You should then put this into the config file. On Jun 27, 2007, at 12:23, Nii Ako Ampa-Sowa wrote: Here is the full response: 2007-06-25 18:56:45 [30552] [16] DEBUG: HTTP: Status line: HTTP/ 1.1 500 Internal Server Error 2007-06-25 18:56:45 [30552] [16] DEBUG: HTTP: Received response: 2007-06-25 18:56:45 [30552] [16] DEBUG: Octet string at 0x81594d0: 2007-06-25 18:56:45 [30552] [16] DEBUG: len: 710 2007-06-25 18:56:45 [30552] [16] DEBUG: size: 1024 2007-06-25 18:56:45 [30552] [16] DEBUG: immutable: 0 Server: Resin/2.1.6..Cache-Control: private..Set-Cookie: JSESSIONID=ar3CoKVA5m6c; Path=/..Content-Type: text/xml; charset=utf-8..Content-Length: 521..Date: Mon, 25 Jun 2007 18:47:36 GMT ?xml version=' 1.0' encoding='UTF-8'?.. SOAP-ENV:Envelope xmlns:SOAP-ENV= http://schemas.xmlsoap.org/soap/envelope/ xmlns:xsi=http://www.w3.org/1999/XMLSchema-instance xmlns:xsd= http://www.w3.org/1999/XMLSchema;. SOAP-ENV:Body. SOAP-ENV:Fault. faultcodeSOAP-ENV:Server/faultcode. faultstring service 'http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/ schema/REL-5-MM7-1-2 ' unknown /faultstring. faultactor/vasp/servlet/messagerouter/faultactor. /SOAP-ENV:Fault.. /SOAP-ENV:Body ./SOAP-ENV:Envelope. 2007-06-25 18:56:45 [30552] [16] DEBUG: Octet string dump ends. 2007-06-25 18:56:45 [30552] [11] INFO: Retry later MMSBox Outgoing Queue MMS Send: From 100/TYPE=PLMN, to 233999, msgsize=97: err=Failed to contact MMC[url= http://abc:[EMAIL PROTECTED]:xx/ abc] = HTTP returned status = 500! On 6/27/07, P. A. Bagyenda [EMAIL PROTECTED] wrote: you want to look at the MM7 packet returned to figure out what's going on *usually* this is caused by a mismatch in the XMLNS URL. On Jun 26, 2007, at 21:37, Nii Ako Ampa-Sowa wrote: Hi, I have mmsbox running and it successfully sends messages when I run a local MMSC on my box with mbuni. I just tried connecting to my mobile operator's MMSC to send the messages... After the content is sent, all I get is HTTP return code 500 (Internal Server Error). Here are the last few lines from the output of mmsbox: 2007-06-25 18:56:45 [30552] [16] DEBUG: Octet string dump ends. 2007-06-25 18:56:45 [30552] [11] INFO: Retry later MMSBox Outgoing Queue MMS Send: From 100/TYPE=PLMN, to 233999, msgsize=97: err=Failed to contact MMC[url= http:// abc:[EMAIL PROTECTED]:xx/abc] = HTTP returned status = 500! Any ideas what the cause of this could be? Thanks, Nii. ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] Receiving MMS with mbuni in smsc=at mode
at the moment this does not work... It is planned, but currently stuck at low priority :) On Jun 26, 2007, at 15:21, Stephen Keegan wrote: Hi, I have a gprs modem connected to my mbuni box. What I want to do is to enable it to receive MMS messages (sent from ordinary mobile phones). I have searched all the documentation and message forums but have been unable to get a definitive answer as to whether this is possible. Is it possible? Do anybody have an example of how it can be done? regards, Stephen. ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] segmentation fault upon receiving response
ooops. Yes. bug hopefully fixed in CVS.
On Jun 26, 2007, at 16:43, hinoglu wrote:
hi, still getting segmentation faults :(
below is the full backtrace.
2007-06-26 16:35:50 [25279] [10] DEBUG: Octet string dump ends.
2007-06-26 16:35:50 [25279] [8] INFO: XML sent is: ?xml
version='1.0' encoding='UTF-8'?
SOAP-ENV:Envelope xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/
envelope/ xmlns:xsi=http://www.w3.org/1999/XMLSchema-instance;
xmlns:xsd=http://www.w3.org/1999/XMLSchema;
SOAP-ENV:Header
mm7:TransactionID SOAP-ENV:mustUnderstand=1 xmlns:mm7=http://
www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-
MM7-1-2Mbuni-2-qf2868.1.x165.57/mm7:TransactionID
/SOAP-ENV:Header
SOAP-ENV:Body
MM7Version5.3.0/MM7Version
StatusStatusCode4000/StatusCodeStatusTextError occured/
StatusText/Status
MessageID/MessageID
/SOAP-ENV:Body
/SOAP-ENV:Envelope
!
2007-06-26 16:35:50 [25279] [8] INFO: parse.soap, h=TransactionID,
v=Mbuni-2-qf2868.1.x165.57!
2007-06-26 16:35:50 [25279] [8] INFO: parse.soap, h=MM7Version,
v=5.3.0!
2007-06-26 16:35:50 [25279] [8] INFO: parse.soap, h=Status, v=!
2007-06-26 16:35:50 [25279] [8] INFO: parse.soap, h=StatusCode,
v=4000!
2007-06-26 16:35:50 [25279] [8] INFO: parse.soap, h=StatusText,
v=Error occured!
2007-06-26 16:35:50 [25279] [8] INFO: parse.soap, h=MessageID, v=!
2007-06-26 16:35:50 [25279] [8] INFO: Send to MMSC[trcel], failed,
code=[4000=General service error], detail=[]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1094945696 (LWP 25289)]
0x0808d6d9 in seems_valid_real (ostr=0x80a5ab1, filename=0x80b04d5
gwlib/octstr.c, lineno=366,
function=0x80af7e3 octstr_duplicate_real) at gwlib/octstr.c:2467
2467gw_assert_place(ostr-data[ostr-len] == '\0',
(gdb) bt full
#0 0x0808d6d9 in seems_valid_real (ostr=0x80a5ab1,
filename=0x80b04d5 gwlib/octstr.c, lineno=366,
function=0x80af7e3 octstr_duplicate_real) at gwlib/octstr.c:2467
__func__ = seems_valid_real
#1 0x0808e14e in octstr_duplicate_real (ostr=0x80a5ab1,
file=0x80b04d5 gwlib/octstr.c, line=2309, func=0x80afc2f convert)
at gwlib/octstr.c:366
__func__ = octstr_duplicate_real
#2 0x080932ae in octstr_format_valist_real (fmt=0x80a477e S]!,
args=0x41438334 \216h\n\b\001) at gwlib/octstr.c:2309
format = {minus = 0, zero = 0, min_width = 0, has_prec = 0,
prec = 0, type = 0}
os = (Octstr *) 0x8164d08
__func__ = octstr_format_valist_real
#3 0x080934e8 in octstr_format (fmt=0x206c6172 Address 0x206c6172
out of bounds) at gwlib/octstr.c:2373
os = (Octstr *) 0x206c6172
#4 0x0805ad9f in sendMsg (e=0x815dcd8) at bearerbox.c:629
detail = (Octstr *) 0x0
tmp = 0x80a5ab1 General service error
msg = (MmsMsg *) 0x815da30
i = 0
n = 1
__func__ = sendMsg
#5 0x08063266 in tdeliver (qt=0x8159270) at mms_queue.c:942
res = 543973746
e = (MmsEnvelope *) 0x815dcd8
#6 0x08081860 in new_thread (arg=0x815b0b0) at gwlib/gwthread-
pthread.c:362
ret = 543973746
#7 0x401c7604 in start_thread (arg=0x41438ba0) at pthread_create.c:
261
__res = (void *) 0x206c6172
__ignore1 = 134891390
__ignore2 = 1701733703
pd = (struct pthread *) 0x41438ba0
now = 579354109105955186
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {1075654644, 0,
8195840, 1094943960, 376838212, 388622832},
mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0},
data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call = 0
robust = (__pthread_slist_t *) 0x0
#8 0x403c0c4e in clone () from /lib/libc.so.6
fstab_state = {fs_fp = 0x0, fs_buffer = 0x0, fs_mntres =
{mnt_fsname = 0x0, mnt_dir = 0x0, mnt_type = 0x0,
mnt_opts = 0x0, mnt_freq = 0, mnt_passno = 0}, fs_ret =
{fs_spec = 0x0, fs_file = 0x0, fs_vfstype = 0x0, fs_mntops = 0x0,
fs_type = 0x0, fs_freq = 0, fs_passno = 0}}
__elf_set___libc_subfreeres_element_fstab_free__ = (const
void *) 0x403fb890
___
Users mailing list
Users@mbuni.org
http://lists.mbuni.org/mailman/listinfo/users
___
Users mailing list
Users@mbuni.org
http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] Amd64 mbuni deb
Not at this stage, but we'd welcome a build. On Jun 26, 2007, at 18:03, Wayne Gemmell wrote: Hi all Are there plans to roll out an amd64 deb for Ubuntu? Cheers Wayne ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] Receiving MMS with mbuni in smsc=at mode
Basically it entails receiving the notification sms from the modem, parsing it, then fetching the message. Not difficult, if you want to help do it, contact me offlist and I'll be happy to help. On Jun 26, 2007, at 18:06, Stephen Keegan wrote: thanks for the info. How would I go about achieving this now? I am willing to try with Mbuni but would be willing to try any other solutions. I'd like to program myself (in any language). Anybody got any advice on this? at the moment this does not work... It is planned, but currently stuck at low priority :) On Jun 26, 2007, at 15:21, Stephen Keegan wrote: Hi, I have a gprs modem connected to my mbuni box. What I want to do is to enable it to receive MMS messages (sent from ordinary mobile phones). I have searched all the documentation and message forums but have been unable to get a definitive answer as to whether this is possible. Is it possible? Do anybody have an example of how it can be done? regards, Stephen. ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] MD5 Authentication
Yes. Nothing needed. It is automatic. simply provide the usual (user, pass, url). But you must use CVS. On Jun 19, 2007, at 16:55, Wayne Gemmell wrote: Hi all I need to connect mmbox to an mmsc using md5 authentication. Is this possible? What do I need to put in the config files to make this work? Cheers Wayne ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] MM1 configuration
At the moment Mbuni does not support what you have in mind. MM1 is only supported when mbuni acts as MMSC, not as VAS Gateway... On Jun 13, 2007, at 22:32, Francois Aucamp wrote: ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] VASP help
Patrick, Do you have a connection to the operator MMSC or are you running your own mmsc as well. Am a little confused as to your setup. On Jun 11, 2007, at 16:15, patrick meye wrote: Hi all,i set up mbuni as mmsc and as vasp gateway.When i test my vas gateway using : http://10.10.2.175:10001/sendmms?username=testerpassword=foobar; vasid=newscorpfrom=+2215387613/TYPE=PLMNto=+2215409962 smil=%3Csmil%3E%3Cbody%3E%3Cpar%20dur=%221ms%22%3E%3C text%20src%20=%20%22cid:FirstText.txt%22%20/%3E%3Cimg%20src%20=%20% 22cid: FirstImage.gif%22%20/%3E%3Caudio%20src%20=%20%22cid:FirstSound.amr% 22%20 /%3E%3C/par%3E%3Cpar%20dur=%221ms%22%3E%3Ctext%20src%20=%20%22cid: SecondText.txt%22%20/%3E%3Cimg%20src%20=%20%22cid:SecondImage.gif% 22%20 /%3E%3Caudio%20src%20=%20%22cid:SecondSound.wav%22%20/%3E%3C/par%3E% 3Cpar %20dur=%221ms%22%3E%3Ctext%20src%20=%20%22cid:ThirdText.txt%22% 20/%3E%3 Cimg%20src%20=%20%22cid:ThirdImage.gif%22%20/%3E%3C/par%3E%3C/body% 3E%3C/smil%3E I've this info: Retry later MMSBox Outgoing Queue MMS Send: From +100/TYPE=PLMN, to 2215409962/TYPE=PLMN, msgsize=648: err=Failed to contact MMC[url=http://127.0.0.1:1982] = HTTP returned status = 401! Can some body help me please? Am i missing something in my config or i wrong somewhere?Please help me. Thank you in advanced. __ ___ Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail mmsc.conf___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] Problems compiling mbuni.
hi, as per documentation you want to use the Kannel snapshot found here: http://www.mbuni.org/downloads/1.2.0/kannel-snapshot.tar.gz On Jun 12, 2007, at 17:49, Wayne Gemmell wrote: Hi, I'm trying to compile mbuni 1.2.0 with kannel 1.4.0 and I get the following error. make[2]: Entering directory `/home/wayne/mbuni/mbuni-1.2.0/mmlib' if /bin/bash ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../mmlib -I../mmlib-g -O2 - D_XOPEN_SOURCE=600 -D_BSD_SOURCE -O4 -Wall -I/usr/include/openssl - I/usr/include/kannel -D_XOPEN_SOURCE=600 -D_BSD_SOURCE -I/usr/ include/libxml2 -I/usr/include -I/usr/include/mysql -MT mms_util.lo -MD -MP -MF .deps/mms_util.Tpo -c -o mms_util.lo mms_util.c; \ then mv -f .deps/mms_util.Tpo .deps/mms_util.Plo; else rm -f .deps/mms_util.Tpo; exit 1; fi gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../mmlib -I../mmlib -g -O2 - D_XOPEN_SOURCE=600 -D_BSD_SOURCE -O4 -Wall -I/usr/include/openssl - I/usr/include/kannel -D_XOPEN_SOURCE=600 -D_BSD_SOURCE -I/usr/ include/libxml2 -I/usr/include -I/usr/include/mysql -MT mms_util.lo -MD -MP -MF .deps/mms_util.Tpo -c mms_util.c -fPIC -DPIC -o .libs/mms_util.o mms_util.c: In function 'mms_load_core_settings': mms_util.c:81: error: too many arguments to function 'http_use_proxy' I have the same problem with the CVS version of mbuni. Any ideas? Wayne Gemmell ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] VAS Gateway Conceptual question
You would indeed have to rely on the logs, or you could create a web page that first receives the message, logs it, then passes it on to another URL... On Jun 11, 2007, at 13:54, Sérgio Bernardo wrote: Hi! Thank you for the answer. The problem with your suggestion is that I intend do use the keyword functionality, by selecting the treatment for each MM based on the first word of the textual part of the MM received. In some occasions, the MM will be resent directly to outside partner's URL. I Don't want to develop a MM keyword interpreter myself if the Gateway has one with all I need :-) Can I do a specific treatment (based on keyword) and continue be able to call a generic URL to register each transaction? Suppose I will have to rely on the logs :-( -- Sérgio Bernardo Chief Technology Officer www.heylife.com On 6/8/07, P. A. Bagyenda [EMAIL PROTECTED] wrote: If you are going to connect directly to the operator MMSC, then all you will receive the MM and be able to hand them over to a URL. The URL can do whatever you want, prior to returning a response (which is then sent back to the operator MMSC). On Jun 08, 2007, at 17:07, Sérgio Bernardo wrote: Hi I'm new to Mbuni, in fact, I'm still in the conceptual evaluation. But I believe MBuni is what I need :-) Congratulations to the developers! As far as I can see, that's a very well structured software! And now a simple question... I'm planing to use tha VAS gateway to connect directly to mobile operators. Still on negotiations, but all o them will connect to me directly via MM7 protocol. The VAS gateway gives me all I need, except for an indexed database / backoffice where the help-desk will locate and solve client and operator specific situations and where monthly reports will be downloaded. Where can I connect the VAS gateway to the database? On the MMSC I have some points where I can insert my own scripts in the transactions, but can't see how to do that in the VAS gateway. One whay to do that is to write the log's to a pipe and use that information with an application of my own, but I suppose there is a better way to do this... is there? Thank you. -- Sérgio Bernardo ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] Corrupted MMS only to SonyEricsson Handsets
Note that MMSC may also carry out some content adaptation. Not sure if older SE support AMR. If they do not, then that part of the message would be removed. On Jun 08, 2007, at 09:14, Marios Fotiou wrote: No it has not been resolved. I sort of quit the MM7 connection for the time beeing and have returned to the mmsbox. I am now in communication with our production MMSC supplier and I have forwarded him some traces with the mbuni MM7 messages so as to see why for Sony Ericsson we get this problem. I suspect that the problem lies in the WAP gateway (not mbuni) From: P. A. Bagyenda [mailto:[EMAIL PROTECTED] Sent: 08 June 2007 07:52 To: Marios Fotiou Cc: Mbuni MMS Gateway Users List Subject: Re: [Users] Corrupted MMS only to SonyEricsson Handsets Hi, did this get resolved? A non-connection is really a network issue, since mbuni will connect to the port configured. On May 31, 2007, at 16:09, Marios Fotiou wrote: This is my configuration *** for mmsrelay group = core log-file = /tmp/log/mbuni-mmsc.log access-log = /tmp/log/mmsc-access.log log-level = 0 group = mbuni name = My MMSC hostname = vas-pc-10 host-alias = mmsc local-prefixes = 037;+25637;25637 storage-directory = /tmp/spool max-send-threads = 5 send-mail-prog = /usr/sbin/sendmail -f '%f' '%t' -G 10.22.0.50 unified-prefix = +25637,037,37 maximum-send-attempts = 1 default-message-expiry = 36 queue-run-interval = 5 send-attempt-back-off = 300 sendsms-url = http://localhost:13013/cgi-bin/sendsms sendsms-username = tester sendsms-password = foobar mms-port = 8191 mm7-port = 8192 #allow-ip = 192.168.129.11 email2mms-relay-hosts = mbuni.org;dsmagic.com;ds.co.ug billing-module-parameters = /tmp/log/cdr.log # billing-library = billdemo.so #prov-server-notify-script = ~/src/mmprov/provnotify.sh #prov-server-sub-status-script = ~/src/mmprov/rcptstatus.sh content-adaptation = true notify-unprovisioned = yes mms-notify-text = You have received a multimedia message from %S, go to XXX to view it mms-notify-unprovisioned-text = This is a test mms-to-email-txt = This is a multimedia message (HTML suppressed) mms-to-email-html = This is a multimedia message powered by emphDigital Solutions/emph mms-to-email-default-subject = This is a multimedia message mms-message-too-large-txt = You have received a multimedia message from %S that is too large for your phone. Go to xxx to view it group = mms-vasp vasp-id = newscorp type = soap short-code = 111 vasp-username = mbuni vasp-password = test vasp-url = http://user:[EMAIL PROTECTED]:12345/ group = mmsproxy name = A test mms proxy host = mms.areeba.com.cy allowed-prefix = 96 denied-prefix = 037 *** for mmsbox group = core log-file = /tmp/log/mbuni-mmmsbox.log access-log = /tmp/log/mmsbox-access.log log-level = 0 group = mbuni storage-directory = /tmp/spool max-send-threads = 5 maximum-send-attempts = 1 default-message-expiry = 36 queue-run-interval = 5 send-attempt-back-off = 300 sendmms-port = 10001 group = mmsc id = newscorp mmsc-url = http://mbuni:[EMAIL PROTECTED]:8192/ incoming-username = user incoming-password = pass incoming-port = 12345 type = soap group = send-mms-user username = tester password = foobar *** The error I get is 2007-05-31 16:08:20 [21589] [17] DEBUG: Parsing URL `http:// mbuni:[EMAIL PROTECTED]:8192/': 2007-05-31 16:08:20 [21589] [17] DEBUG: Scheme: http:// 2007-05-31 16:08:20 [21589] [17] DEBUG: Host: 10.22.0.132 2007-05-31 16:08:20 [21589] [17] DEBUG: Port: 8192 2007-05-31 16:08:20 [21589] [17] DEBUG: Username: mbuni 2007-05-31 16:08:20 [21589] [17] DEBUG: Password: test 2007-05-31 16:08:20 [21589] [17] DEBUG: Path: / 2007-05-31 16:08:20 [21589] [17] DEBUG: Query: (null) 2007-05-31 16:08:20 [21589] [17] DEBUG: Fragment: (null) 2007-05-31 16:08:20 [21589] [17] DEBUG: HTTP: Opening connection to `10.22.0.132:8192' (fd=46). 2007-05-31 16:08:20 [21589] [17] DEBUG: Socket connecting 2007-05-31 16:08:20 [21589] [16] DEBUG: Get info about connecting socket 2007-05-31 16:08:20 [21589] [16] DEBUG: Socket not connected 2007-05-31 16:08:20 [21589] [16] ERROR: Couldn't fetch http:// mbuni:[EMAIL PROTECTED]:8192/ 2007-05-31 16:08:20 [21589] [11] INFO: Retry later MMSBox Outgoing Queue MMS Send: From 96222524/TYPE=PLMN, to 96222524/TYPE=PLMN, msgsize=53869: err=Failed to contact MMC[url=http:// mbuni:[EMAIL PROTECTED]:8192/] = HTTP returned status = -1! This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late
Re: [Users] VAS Gateway Conceptual question
If you are going to connect directly to the operator MMSC, then all you will receive the MM and be able to hand them over to a URL. The URL can do whatever you want, prior to returning a response (which is then sent back to the operator MMSC). On Jun 08, 2007, at 17:07, Sérgio Bernardo wrote: Hi I'm new to Mbuni, in fact, I'm still in the conceptual evaluation. But I believe MBuni is what I need :-) Congratulations to the developers! As far as I can see, that's a very well structured software! And now a simple question... I'm planing to use tha VAS gateway to connect directly to mobile operators. Still on negotiations, but all o them will connect to me directly via MM7 protocol. The VAS gateway gives me all I need, except for an indexed database / backoffice where the help-desk will locate and solve client and operator specific situations and where monthly reports will be downloaded. Where can I connect the VAS gateway to the database? On the MMSC I have some points where I can insert my own scripts in the transactions, but can't see how to do that in the VAS gateway. One whay to do that is to write the log's to a pipe and use that information with an application of my own, but I suppose there is a better way to do this... is there? Thank you. -- Sérgio Bernardo ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] Corrupted MMS only to SonyEricsson Handsets
Hi, did this get resolved? A non-connection is really a network issue, since mbuni will connect to the port configured. On May 31, 2007, at 16:09, Marios Fotiou wrote: This is my configuration *** for mmsrelay group = core log-file = /tmp/log/mbuni-mmsc.log access-log = /tmp/log/mmsc-access.log log-level = 0 group = mbuni name = My MMSC hostname = vas-pc-10 host-alias = mmsc local-prefixes = 037;+25637;25637 storage-directory = /tmp/spool max-send-threads = 5 send-mail-prog = /usr/sbin/sendmail -f '%f' '%t' -G 10.22.0.50 unified-prefix = +25637,037,37 maximum-send-attempts = 1 default-message-expiry = 36 queue-run-interval = 5 send-attempt-back-off = 300 sendsms-url = http://localhost:13013/cgi-bin/sendsms sendsms-username = tester sendsms-password = foobar mms-port = 8191 mm7-port = 8192 #allow-ip = 192.168.129.11 email2mms-relay-hosts = mbuni.org;dsmagic.com;ds.co.ug billing-module-parameters = /tmp/log/cdr.log # billing-library = billdemo.so #prov-server-notify-script = ~/src/mmprov/provnotify.sh #prov-server-sub-status-script = ~/src/mmprov/rcptstatus.sh content-adaptation = true notify-unprovisioned = yes mms-notify-text = You have received a multimedia message from %S, go to XXX to view it mms-notify-unprovisioned-text = This is a test mms-to-email-txt = This is a multimedia message (HTML suppressed) mms-to-email-html = This is a multimedia message powered by emphDigital Solutions/emph mms-to-email-default-subject = This is a multimedia message mms-message-too-large-txt = You have received a multimedia message from %S that is too large for your phone. Go to xxx to view it group = mms-vasp vasp-id = newscorp type = soap short-code = 111 vasp-username = mbuni vasp-password = test vasp-url = http://user:[EMAIL PROTECTED]:12345/ group = mmsproxy name = A test mms proxy host = mms.areeba.com.cy allowed-prefix = 96 denied-prefix = 037 *** for mmsbox group = core log-file = /tmp/log/mbuni-mmmsbox.log access-log = /tmp/log/mmsbox-access.log log-level = 0 group = mbuni storage-directory = /tmp/spool max-send-threads = 5 maximum-send-attempts = 1 default-message-expiry = 36 queue-run-interval = 5 send-attempt-back-off = 300 sendmms-port = 10001 group = mmsc id = newscorp mmsc-url = http://mbuni:[EMAIL PROTECTED]:8192/ incoming-username = user incoming-password = pass incoming-port = 12345 type = soap group = send-mms-user username = tester password = foobar *** The error I get is 2007-05-31 16:08:20 [21589] [17] DEBUG: Parsing URL `http:// mbuni:[EMAIL PROTECTED]:8192/': 2007-05-31 16:08:20 [21589] [17] DEBUG: Scheme: http:// 2007-05-31 16:08:20 [21589] [17] DEBUG: Host: 10.22.0.132 2007-05-31 16:08:20 [21589] [17] DEBUG: Port: 8192 2007-05-31 16:08:20 [21589] [17] DEBUG: Username: mbuni 2007-05-31 16:08:20 [21589] [17] DEBUG: Password: test 2007-05-31 16:08:20 [21589] [17] DEBUG: Path: / 2007-05-31 16:08:20 [21589] [17] DEBUG: Query: (null) 2007-05-31 16:08:20 [21589] [17] DEBUG: Fragment: (null) 2007-05-31 16:08:20 [21589] [17] DEBUG: HTTP: Opening connection to `10.22.0.132:8192' (fd=46). 2007-05-31 16:08:20 [21589] [17] DEBUG: Socket connecting 2007-05-31 16:08:20 [21589] [16] DEBUG: Get info about connecting socket 2007-05-31 16:08:20 [21589] [16] DEBUG: Socket not connected 2007-05-31 16:08:20 [21589] [16] ERROR: Couldn't fetch http:// mbuni:[EMAIL PROTECTED]:8192/ 2007-05-31 16:08:20 [21589] [11] INFO: Retry later MMSBox Outgoing Queue MMS Send: From 96222524/TYPE=PLMN, to 96222524/TYPE=PLMN, msgsize=53869: err=Failed to contact MMC[url=http:// mbuni:[EMAIL PROTECTED]:8192/] = HTTP returned status = -1! This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e- mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard- copy version. areeba Limited, 87 Kennedy Avenue, Lefkosia, Cyprus, www.areeba.com.cy ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] MM4 invalid message type
Use CVS. That issue is fixed. On Jun 05, 2007, at 14:36, Marios Fotiou wrote: I configured mbuni as an MMSC and using the mmssend commend I tried sending an MMS to a number that the prefix is configured to be routed to another MMSC via MM4. The message is transmitted correctly via SMTP however there is an error on the other MMSC saying that Invalid MM4 message type 'm-send-req' Looking at the logs and traces I figured out that the header X-MMS- Message-Type is wrongly transmited as m-send-req via MM4 and according to 3GPP standards it should be set to MM4_forward.REQ. Is this an issue of configuration or mbuni does not have implimented the correct headers for MM4 MMSC interconnection. Marios ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] Corrupted MMS only to SonyEricsson Handsets
sorry for the delay. You are sure you have no HTTP proxy or firewall in between that is not correctly configured? It would seem your VAS Gateway can't reach the mbuni mmsc port. That is, there is a failure at the network (rather than the HTTP) level because we don't even see an HTTP response code. If the two are on the same machine, why not use localhost as host name, rather than IP. On Jun 04, 2007, at 10:32, Marios Fotiou wrote: So what do you think for the below configuration? Why I get this error when I try the mm7 port of mbuni? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Marios Fotiou Sent: 31 May 2007 16:09 To: P. A. Bagyenda Cc: Mbuni MMS Gateway Users List Subject: RE: [Users] Corrupted MMS only to SonyEricsson Handsets This is my configuration *** for mmsrelay group = core log-file = /tmp/log/mbuni-mmsc.log access-log = /tmp/log/mmsc-access.log log-level = 0 group = mbuni name = My MMSC hostname = vas-pc-10 host-alias = mmsc local-prefixes = 037;+25637;25637 storage-directory = /tmp/spool max-send-threads = 5 send-mail-prog = /usr/sbin/sendmail -f '%f' '%t' -G 10.22.0.50 unified-prefix = +25637,037,37 maximum-send-attempts = 1 default-message-expiry = 36 queue-run-interval = 5 send-attempt-back-off = 300 sendsms-url = http://localhost:13013/cgi-bin/sendsms sendsms-username = tester sendsms-password = foobar mms-port = 8191 mm7-port = 8192 #allow-ip = 192.168.129.11 email2mms-relay-hosts = mbuni.org;dsmagic.com;ds.co.ug billing-module-parameters = /tmp/log/cdr.log # billing-library = billdemo.so #prov-server-notify-script = ~/src/mmprov/provnotify.sh #prov-server-sub-status-script = ~/src/mmprov/rcptstatus.sh content-adaptation = true notify-unprovisioned = yes mms-notify-text = You have received a multimedia message from %S, go to XXX to view it mms-notify-unprovisioned-text = This is a test mms-to-email-txt = This is a multimedia message (HTML suppressed) mms-to-email-html = This is a multimedia message powered by emphDigital Solutions/emph mms-to-email-default-subject = This is a multimedia message mms-message-too-large-txt = You have received a multimedia message from %S that is too large for your phone. Go to xxx to view it group = mms-vasp vasp-id = newscorp type = soap short-code = 111 vasp-username = mbuni vasp-password = test vasp-url = http://user:[EMAIL PROTECTED]:12345/ group = mmsproxy name = A test mms proxy host = mms.areeba.com.cy allowed-prefix = 96 denied-prefix = 037 *** for mmsbox group = core log-file = /tmp/log/mbuni-mmmsbox.log access-log = /tmp/log/mmsbox-access.log log-level = 0 group = mbuni storage-directory = /tmp/spool max-send-threads = 5 maximum-send-attempts = 1 default-message-expiry = 36 queue-run-interval = 5 send-attempt-back-off = 300 sendmms-port = 10001 group = mmsc id = newscorp mmsc-url = http://mbuni:[EMAIL PROTECTED]:8192/ incoming-username = user incoming-password = pass incoming-port = 12345 type = soap group = send-mms-user username = tester password = foobar *** The error I get is 2007-05-31 16:08:20 [21589] [17] DEBUG: Parsing URL `http:// mbuni:[EMAIL PROTECTED]:8192/': 2007-05-31 16:08:20 [21589] [17] DEBUG: Scheme: http:// 2007-05-31 16:08:20 [21589] [17] DEBUG: Host: 10.22.0.132 2007-05-31 16:08:20 [21589] [17] DEBUG: Port: 8192 2007-05-31 16:08:20 [21589] [17] DEBUG: Username: mbuni 2007-05-31 16:08:20 [21589] [17] DEBUG: Password: test 2007-05-31 16:08:20 [21589] [17] DEBUG: Path: / 2007-05-31 16:08:20 [21589] [17] DEBUG: Query: (null) 2007-05-31 16:08:20 [21589] [17] DEBUG: Fragment: (null) 2007-05-31 16:08:20 [21589] [17] DEBUG: HTTP: Opening connection to `10.22.0.132:8192' (fd=46). 2007-05-31 16:08:20 [21589] [17] DEBUG: Socket connecting 2007-05-31 16:08:20 [21589] [16] DEBUG: Get info about connecting socket 2007-05-31 16:08:20 [21589] [16] DEBUG: Socket not connected 2007-05-31 16:08:20 [21589] [16] ERROR: Couldn't fetch http:// mbuni:[EMAIL PROTECTED]:8192/ 2007-05-31 16:08:20 [21589] [11] INFO: Retry later MMSBox Outgoing Queue MMS Send: From 96222524/TYPE=PLMN, to 96222524/TYPE=PLMN, msgsize=53869: err=Failed to contact MMC[url=http:// mbuni:[EMAIL PROTECTED]:8192/] = HTTP returned status = -1! This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e- mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail
Re: [Users] Corrupted MMS only to SonyEricsson Handsets
MM7 works. Perhaps a look at your config? You last mail to this list was culled for being too large. Perhaps you could zip the logs first? On May 31, 2007, at 10:30, Marios Fotiou wrote: Today I tried to setup mbuni as an MMSC as well. The trick is to forward the MMS received via HTTP GET on the VAS gateway to mbuni via MM7 and then mbuni to send the MM via MM4 on the active MMSC. However it seems like MM7 does not work on mbuni. I run bot mmsbox and mmsrelay. I setup mm7-port=8192 on the mmsc conf file and I use mmsc-url=http://mbuni:test@IP of mbuni:8192/ in the mmsbox conf file. However when I try to send I receive in the log Couldn't fetch http://mbuni:test@IP of mbuni:8192/. It seems like mm7 does not work. I looked into the documentation but I cannot find anything else than the steps I have taken. Do you have any ideas? -Original Message- From: P. A. Bagyenda [mailto:[EMAIL PROTECTED] Sent: 30 May 2007 14:34 To: Marios Fotiou Cc: Mbuni MMS Gateway Users List Subject: Re: [Users] Corrupted MMS only to SonyEricsson Handsets Content parts are only base64 encoded if they appear to contain binary data. This should not be the case for you unless you are using an old version of mbuni (i.e. try CVS). I have tested SE-T610i with Mbuni and it should work, so the MMSC must be doing something odd with the message. What you want to do is compare the MM7 packet from Mbuni and that from another gateway, and advise. On May 30, 2007, at 13:45, Marios Fotiou wrote: Dear Bagyenda, You were correct for the apache mime type mapping that worked straight away! Thank you very much! As for the SE issue, I tested in a few models including the SE- T610i. I will look UAProf URL however since the MMSC-WAP GW I use is not mbuni but an external one then I cannot see how this will affect the delivery of the MMS to these terminals. Some more information is that when I receive the message on a Nokia terminal and I forward it through the same MMSC via MM1 to a SE terminal the MMS is delivered without a problem. This is very strange... We have another platform that connects to the MMSC directly on MM7 interface and from that platform delivery to SE terminals works fine. I traced that MM7 connection only to find out that it sends the smil file encoded in base64. I decoded the SMIL and used the same on an mbuni MMS however I still get the MMS to be corrupted... This is very strange Marios -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of P. A. Bagyenda Sent: 30 May 2007 13:06 To: Mbuni MMS Gateway Users List Subject: Re: [Users] Corrupted MMS only to SonyEricsson Handsets When Mbuni receives the SMIL, it tries to fetch the content in order to build the MMS. For your case, it relies on the HTTP server to inform it of the content type of the content fetched. My hunch is this is where things are breaking. Check your HTTP server's mapping of file names to mime types (for apache, the file is mime.types in the conf directory). Ensure that .amr is mapped to mime type audio/AMR. for sony ericsson, the problem may be caused by content adaptation. Please advise on the handset type and also perhaps send me the UAProf URL for it. On May 30, 2007, at 12:31, Marios Fotiou wrote: Dear All, We have setup a test mbuni server to use as an MMS gateway. Using the sendmms command we have formulated the below URL to send to the mbuni mmsbox. The MMS is sent succesfully and it is then transmitted to mobile phone where it can be viewed. We have tested with Nokia, Samsung and Sony Ericsson handsets and only in SonyEricsson the message is displayed as corrupted. Are we missing something optional in the SMIL that is required by SonyEricsson MMS viewers to accept the SMIL as correct? http://10.22.0.132:10001/sendmms? sername=testerpassword=foobarvasid=we bserverfrom=96222524/TYPE=PLMNto=96222521/ TYPE=PLMNsmil=smilhead layoutregion id='Image' width='114' height='160' left='0' top='0' /region id='Text' width='160' height='50' left='0' top='120' //layout/headbodypar dur='5s'text src='http://myserver:/mms_content/happy_birthday.txt' region='Text'/img src='http://myserver:/mms_content/happy_birthday.jpg' region='Image'//par/body/smil In addition when we add audio src='http://myserver:/mms_content/happy_birthday.amr'/ the message appears as corrupted to all phones. Tracing on the 10001 port shows that the encoding for the audio file shows as Content-Type:text/plain. See below the trace. Thank you very much in advance! Regards, Marios Fotiou VAS Engineer Areeba Cyprus * POST /mmsc/mm7 HTTP/1.1 Host: areebammsc:3128 Connection: keep-alive SOAPAction: Content-Type: multipart/related; type=text/xml; start=s1180513372.897860030.Kq.msg; boundary=_boundary_1431855693_1180513372_I_a_bd1677038100 MIME-Version: 1.0 Content-Length: 75467 --_boundary_1431855693_1180513372_I_a_bd1677038100 Content-Type: text/xml Content
Re: [Users] Corrupted MMS only to SonyEricsson Handsets
When Mbuni receives the SMIL, it tries to fetch the content in order to build the MMS. For your case, it relies on the HTTP server to inform it of the content type of the content fetched. My hunch is this is where things are breaking. Check your HTTP server's mapping of file names to mime types (for apache, the file is mime.types in the conf directory). Ensure that .amr is mapped to mime type audio/AMR. for sony ericsson, the problem may be caused by content adaptation. Please advise on the handset type and also perhaps send me the UAProf URL for it. On May 30, 2007, at 12:31, Marios Fotiou wrote: Dear All, We have setup a test mbuni server to use as an MMS gateway. Using the sendmms command we have formulated the below URL to send to the mbuni mmsbox. The MMS is sent succesfully and it is then transmitted to mobile phone where it can be viewed. We have tested with Nokia, Samsung and Sony Ericsson handsets and only in SonyEricsson the message is displayed as corrupted. Are we missing something optional in the SMIL that is required by SonyEricsson MMS viewers to accept the SMIL as correct? http://10.22.0.132:10001/sendmms? sername=testerpassword=foobarvasid=we bserverfrom=96222524/TYPE=PLMNto=96222521/ TYPE=PLMNsmil=smilhead layoutregion id='Image' width='114' height='160' left='0' top='0' /region id='Text' width='160' height='50' left='0' top='120' //layout/headbodypar dur='5s'text src='http://myserver:/mms_content/happy_birthday.txt' region='Text'/img src='http://myserver:/mms_content/happy_birthday.jpg' region='Image'//par/body/smil In addition when we add audio src='http://myserver:/mms_content/happy_birthday.amr'/ the message appears as corrupted to all phones. Tracing on the 10001 port shows that the encoding for the audio file shows as Content-Type:text/plain. See below the trace. Thank you very much in advance! Regards, Marios Fotiou VAS Engineer Areeba Cyprus * POST /mmsc/mm7 HTTP/1.1 Host: areebammsc:3128 Connection: keep-alive SOAPAction: Content-Type: multipart/related; type=text/xml; start=s1180513372.897860030.Kq.msg; boundary=_boundary_1431855693_1180513372_I_a_bd1677038100 MIME-Version: 1.0 Content-Length: 75467 --_boundary_1431855693_1180513372_I_a_bd1677038100 Content-Type: text/xml Content-ID: s1180513372.897860030.Kq.msg ?xml version='1.0' encoding='UTF-8'? SOAP-ENV:Envelope xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/; SOAP-ENV:Header mm7:TransactionID xmlns:mm7=http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/ schema /REL-5-MM7-1-2 SOAP-ENV:mustUnderstand=1[EMAIL PROTECTED]/ mm7:TransactionID /SOAP-ENV:Header SOAP-ENV:Body mm7:SubmitReq xmlns:mm7=http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/ schema /REL-5-MM7-1-2 mm7:MM7Version5.3.0/mm7:MM7Version mm7:SenderIdentification mm7:VASPIDwebserver/mm7:VASPID mm7:VASIDwebserver/mm7:VASID mm7:SenderAddressmm7:Number96222524/mm7:Number /mm7:SenderAddress /mm7:SenderIdentification mm7:Recipients mm7:To mm7:Number96222521/mm7:Number /mm7:To /mm7:Recipients mm7:TimeStamp2007-05-30T08:22:51Z/mm7:TimeStamp mm7:Content href=cid:c1180513372.1132963618.Rw.msg/ /mm7:SubmitReq /SOAP-ENV:Body /SOAP-ENV:Envelope --_boundary_1431855693_1180513372_I_a_bd1677038100 X-Mms-MMS-Version: 1.0 X-Mms-Expiry: Wed, 06 Jun 2007 08:22:50 GMT Date: Wed, 30 May 2007 08:22:51 GMT Message-ID: [EMAIL PROTECTED] MIME-Version: 1.0 Content-Type: multipart/related; type=application/smil; start=presentation; boundary=_boundary_1908694232_1180513372_L_h_bd1536088165 Content-ID: c1180513372.1132963618.Rw.msg --_boundary_1908694232_1180513372_L_h_bd1536088165 Content-ID: 55 Content-Type: text/plain Content-Transfer-Encoding: base64 IyFBTVIKNMu3CEEP/PNWQ16H/v/1PAP+7VwAANE+ZeAANFITCi222nG+WBD//c4 +jsQzqP5n PU0S AoygNKoZii023a/uR9L/vIqlLKYhayDTzz.not included due to size --_boundary_1908694232_1180513372_L_h_bd1536088165 Content-ID: 56 Content-Type: text/plain Dear Antonis, areeba wishes you happy birthday! --_boundary_1908694232_1180513372_L_h_bd1536088165 Content-ID: 57 Content-Type: image/jpeg Content-Transfer-Encoding: base64 /9j/4AAQSkZJRgABAgAAZABkAAD/7AARRHVja3kAAQAETwAA/ +4ADkFkb2JlAGTA Af/b AIQAAwICAgICAwICAwQCAgI.not included due to size --_boundary_1908694232_1180513372_L_h_bd1536088165 Content-ID: presentation Content-Type: application/smil ?xml version=1.0? smil head layout region id=Image width=114 height=160 left=0 top=0/ region id=Text width=160 height=50 left=0 top=120/ /layout /head body par dur=5s audio src=cid:55/ text src=cid:56 region=Text/ img src=cid:57 region=Image/ /par /body /smil --_boundary_1908694232_1180513372_L_h_bd1536088165-- --_boundary_1431855693_1180513372_I_a_bd1677038100-- HTTP/1.1 200 OK Content-Type: text/xml; charset=utf-8 Connection: Keep-Alive Content-Length: 658 Soapaction: RESPONSE FROM MMSC ?xml
Re: [Users] VAS GW request for delivery report
the request should be part of the MMS message itself. Typically there is a header in the message X-Mms-Delivery-Report set to Yes. For the send-mms interface, setting the delivery report URL should do the trick. On May 16, 2007, at 17:32, Miguel Cartó wrote: Hi again, after i finally set up my mmsc-vasgw scenario, how can i make my vasgw to ask for a delivery report for a specific messageID? Is there any way to do it or I have to make something to get the delivery report? --MC ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] Sending MMS Messages with MBuni - How?
On May 15, 2007, at 01:26, Mark Easton wrote: Hi, We are based in New Zealand. We need to send MMS messages to mobile phones. MBuni looks an option. Do we have to get a MM7 connection with a local operator to do this. i.e. Telecom NZ or Vodafone NZ. Or are there other options? Yes you'd have to. ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users ___ Users mailing list Users@mbuni.org http://lists.mbuni.org/mailman/listinfo/users
Re: [Users] SMS notification not working?
I think these are two separate notifications. Once the mobile gets notified, it can indeed fetch the message, this seems to be a different notification. Please send through the log for better troubleshooting. P. On May 03, 2006, at 16:44, Deon van der Merwe wrote: Hi, Okay (after reading many more list emails...) the problem was with the length of the URL in the push. So, that is sorted... Next problem: - send MMS via MM7 to subscriber - subscriber gets the notification messages - subscriber connects - I see the request come in to the MMSC, but the subscriber does not get the content. - In the log I see this entry: INFO: Failed Global Queue MMS Send: From [EMAIL PROTECTED], to vsmsc/TYPE=PLMN, msgsize=65: err=MMSC error: Don't know how to deliver to vsmsc/TYPE=PLMN ! What does mbuni want to deliver back to the VASP client? Does this error prevent the subscriber from getting the content? On 5/3/06, Deon van der Merwe [EMAIL PROTECTED] wrote: Hi All, I feel like I am missing something very simple here... but I am missing it! I am running on/with: - Slackware 10.2 (2.4.31) - Kannel 1.4.0 (patched with full mbuni patch) - latest mbuni CVS - SMPP connection SMSC What happens is: - I can submit a MMS to the MMSC from mobiles and with MM7 - I see the SMS notification goes out - I see a delivery confirmation on the SMSC connection - The phone does not do anything... + on Nokia phones it show a data message- can not display + on Samsung I see nothing + on SonyEricsson I see nothing (after reboot of the phone I see the message as normal SMS in the inbox) What can be causing this? ___ Users mailing list Users@mbuni.org http://mbuni.org/mailman/listinfo/users_mbuni.org ___ Users mailing list Users@mbuni.org http://mbuni.org/mailman/listinfo/users_mbuni.org
Re: [Users] mbuni as vasgw
Davor, CVS has been updated to accomodate the two issues below:1. You can now specify that the service response should be dropped ignored, using suppress-reply = true in the mms-service config2. You can set pass-thro-headers = X-NOKIA-MMSC-Charging, Nokia-MMSC-Allow-Adaptation in the mms-service config, and set those headers in the service reply. These will then be transparently passed back the MMSC. Works for EAIF and SOAP. Documentation in CVS has also been updated. Of course all test feedback is most welcomeOn Apr 21, 2006, at 13:35, Davor Spasoski wrote: I am currently running mbuni as vasgw on Nokia MMSC. Works pretty stable. I am now trying to develop a simple service that will write the incoming parts (text, image, audio) into a DB and present them on the web. (Photoblog) Has anybody succeded to make such an application or has some tested php code?Also there seems to be no way of instructing mmsbox not to send a reply on the incoming mms. Something similar to “max-messages = 0” in Kannel, for instance.Additionally, is there a way of sending additional EAIF HTTP extension headers as specified in the protocol, such as X-NOKIA-MMSC-Charging, (very important for tariff indication) and X-NOKIA-MMSC-Allow-Adaptations (to explicitly direct the MMSC to/not-to adapt the content)? If not, can somebody point where to add this support in the source code? Davor Spasoski COSMOFON - Mobile Telecommunications Services - A.D. Skopje ___ This e-mail (including any attachments) is confidential and may be protected by legal privilege. If you are not the intended recipient, you should not copy it, re-transmit it, use it or disclose its contents, but should return it to the sender immediately and delete your copy from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. COSMOFON A.D. Skopje shall not be liable for the improper or incomplete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system.___Users mailing listUsers@mbuni.orghttp://mbuni.org/mailman/listinfo/users_mbuni.org ___ Users mailing list Users@mbuni.org http://mbuni.org/mailman/listinfo/users_mbuni.org
