Just getting into this after the holiday season. Good to see you got it working!

I am thinking of stripping out libcurl, but that would require patching 
Kannel's http lib to allow  per-request proxy settings... Not hard, just need 
to get to it. The reason for this is that when the modem comes up, we need to 
send all MMS transactions via the operator proxy (if available)
On Jan 02, 2010, at 09:12, Ray Pitmon wrote:

> Hi,
> 
> I got it to work!
> 
> Specifying content-url in the request to mbuni did not work.  Instead, I 
> posted an SMIL file that pointed to the image, and it just worked.  Yay!
> 
> -Ray
> 
> 
> Ray Pitmon wrote:
>> Hi Nikos,
>> 
>> (Sorry in advance, as this is becoming a long message.)
>> 
>> Regarding the port 49202 thing, I was expecting port 9201 for WAP (like you 
>> indicate), but wireshark was saying that everything was happening on 49202 
>> for some reason.. Maybe it was confused...  Anyway, I've made some progress 
>> and don't really care about that issue any more... So...
>> 
>> A couple other things:
>> 1. (as a side note) I've discovered that kannel is very sensitive, if you do 
>> stop or start-smsc admin request to kannel via 
>> "http://localhost:13000/stop-smsc?smsc=blah"; and blah isn't defined in 
>> kannel as an smsc, bearerbox will most definitely crash and burn.
>> 2. I'm only using kannel to handle incoming/outgoing SMS.  I need to send 
>> MMS via my operators mmsc, so I'm not dealing with notification or wapbox in 
>> kannel or wap requests to mbuni.  (Let me know if I'm not on the right track 
>> here.)  So SMS goes through kannel, and I'm hitting mbuni with an HTTP 
>> request to get it to send out an MMS.
>> 
>> I am so close I can almost taste it... (I discovered that something is wrong 
>> with one of my GSM modems or accounts, but I've got one that almost works..)
>> 
>> Here's where I'm at:
>> 
>> (Kannel and Mbuni are running, of course)
>> 1. I inject an MMS into Mbuni via a URL that looks like this:  
>> http://testserver:8193/?username=user&password=pass&from=100&to=16125555555&subject=SomeSubject&mmsc=modem&content-url=http://testserver/img/mms/offer_10.jpg
>>  
>> 
>> 2. Mbuni hits my webserver, downloads the offer_10.jpg image. (works great)  
>> Log entries on mbuni look like this:
>> 
>> 2009-12-29 21:58:24 [2425] [23] DEBUG: Octet string dump ends.
>> 2009-12-29 21:58:24 [2425] [20] DEBUG: WSP: Mapping `image/jpeg', WSP 1.2 to 
>> 0x001e.
>> 2009-12-29 21:58:24 [2425] [20] INFO: mmsbox.c:1355 <make_and_queue_msg> 
>> [mmsbox] [n/a] MMSBox: Queued message from service [sendmms-user], [transid 
>> [Mbuni-msg.5504.x1.25.8]: e-to-qf5504.2.x425.96
>> 2009-12-29 21:58:24 [2425] [20] INFO: System error 2: No such file or 
>> directory
>> 2009-12-29 21:58:24 [2425] [20] DEBUG: HTTP: Resetting HTTPClient for 
>> `172.18.3.10'.
>> 2009-12-29 21:58:24 [2425] [20] INFO: mmsbox.c:1602 <dispatch_sendmms_recv> 
>> [mmsbox] [n/a] MMSBox.mmssend: u=user, Queued [Accepted: 
>> Mbuni-msg.5504.x1.25.8]
>> 2009-12-29 21:58:27 [2425] [7] DEBUG: Queued to thread 1 for 
>> /var/spool/mbuni/mmsbox_outgoing/e/to/qf5504.2.x425.96, sendt=1262145504, 
>> tnow=1262145507
>>  SMSC `modem' shut down
>> 
>> 3. Mbuni shuts the kannel connection down. (works great)
>> 4. PPP starts up. (works great)
>> 5. Mbuni POSTs the MMS to the operator's mmsc.  Request header looks like 
>> this:
>> 
>> POST http://mmsc.cingular.com HTTP/1.1
>> Host: mmsc.cingular.com
>> User-Agent: Mbuni-MmsBox/1.0.0
>> x-wap-profile: http://shortcode.someserver.com/mbuni.xml
>> Accept: */*, application/vnd.wap.mms-message
>> Content-Type: application/vnd.wap.mms-message
>> Content-Length: 41540
>> ..a bunch of binary data, followed by..:
>> HTTP/1.1 200 OK
>> content-type: application/vnd.wap.mms-message
>> Content-Length: 54
>> Via: 1.1 alpmag2r1fe04WAP2-mbl:8080
>> 
>> ...00001......Message accepted..123005015110000300003.
>> 
>> (Everything looks really good.. other MMSC accepted my message!).
>> 
>> However, the message is never delivered to my handset.  If I change the URL 
>> that I'm using to inject the msg into mbuni and add '&text=SomeTextHere', 
>> then I actually get the message.  I would appear that mbuni is not 
>> formatting the mms properly when I'm trying to send an image or something.
>> 
>> I am evaluating a couple commercial MMS-sending apps, and found that they 
>> can send out an MMS that looks very similar (in wireshark anyway), and I do 
>> receive the MMS (so I know that the modem is good, the plan supports MMS, 
>> etc).
>> 
>> Any ideas?
>> 
>> Thanks for your help!
>> 
>> -Ray
>> 
>> 
>> Nikos Balkanas wrote:
>>> Hi,
>>> 
>>> I have lots of experience with kannel and the at driver. Normally bearerbox 
>>> panics when the modem goes down. It is always nice to learn about new 
>>> tricks ;-)
>>> 
>>> What you are reading is not WAP. Wap 1.x works over udp ports 9200 - 9203, 
>>> not 49202. Kannel's bearerbox listens in at these ports for wap traffic. 
>>> Post packet dump to verify it.
>>> 
>>> Mbuni works with kannel both for notification (smsbox) and wap traffic for 
>>> older mobiles. Kannel's wapbox is configured with map-url to redirect wap 
>>> requests to mbuni. Read mbuni configuration.
>>> 
>>> Also please post POST request you are sending along with detailed logs of 
>>> attempt.
>>> 
>>> BR,
>>> Nikos
>>> ----- Original Message ----- From: "Ray Pitmon" <r...@pitmon.com>
>>> To: <users@mbuni.org>
>>> Sent: Tuesday, December 29, 2009 7:12 AM
>>> Subject: Re: [Users] mm1 using wrong interface to send
>>> 
>>> 
>>>> So, it looks like I'm having problems sending out to 
>>>> wireless.cingular.com.  I tried to POST the content of the data file 
>>>> directly using curl, and I pretty much get the same thing that I get when 
>>>> mbuni tries.  (It does a POST of the data and just sits there.)
>>>> 
>>>> I've looked at a commercial app that works (on Windows), and when I do a 
>>>> packet trace,  I see that it's sending everything UDP and the content 
>>>> looks to be SMIL.  So I'm thinking that it's using the WAP1 gateway and 
>>>> sending SMIL formatted data instead.  (Although the udp port (49202) and 
>>>> host IP) are not what I thought I would find, so maybe I don't understand 
>>>> WAP as well as I thought I did.)
>>>> 
>>>> Any ideas?  Can I configure mbuni to send via a wap1 gateway?  Am I even 
>>>> looking in the right direction?
>>>> 
>>>> Thanks,
>>>> 
>>>> -Ray
>>>> 
>>>> Ray Pitmon wrote:
>>>>> Hi Nikos,
>>>>> 
>>>>> The libmmsbox_mm1 library does a great job of telling kannel to take the 
>>>>> modem offline so that the dialup PPP session can start (and that works 
>>>>> well).  The problem that I'm seeing seems to be related more with libcurl 
>>>>> binding to the wrong interface.  I was able to add a configuration 
>>>>> setting to specify the libcurl interface (ppp0) and recompile.  This, 
>>>>> with a couple sleeps, causes it to bind to ppp0.  (I'm getting further, 
>>>>> but it still isn't working correctly; I'll post my next issue soon :)
>>>>> 
>>>>> Thanks,
>>>>> 
>>>>> -Ray
>>>>> 
>>>>> 
>>>>> Nikos Balkanas wrote:
>>>>>> Hi,
>>>>>> 
>>>>>> Do you need to shutdown kannel? Can mbuni notification work without 
>>>>>> kannel? You know that kannel supports HTTP smsc and therefore you can 
>>>>>> connect through it.
>>>>>> 
>>>>>> BR,
>>>>>> Nikos
>>>>>> ----- Original Message ----- From: "Ray Pitmon" <r...@pitmon.com>
>>>>>> To: <users@mbuni.org>
>>>>>> Sent: Monday, December 28, 2009 7:45 AM
>>>>>> Subject: [Users] mm1 using wrong interface to send
>>>>>> 
>>>>>> 
>>>>>>> Hi,
>>>>>>> 
>>>>>>> I'm very close to getting mbuni to send out vi MM1 on a GSM modem.
>>>>>>> 
>>>>>>> Mbuni will tell kannel to shut down (which it does), and it brings up 
>>>>>>> the ppp connection.
>>>>>>> 
>>>>>>> However, it never seems to connect to AT&T's SMSC.  So I did a tcpdump 
>>>>>>> on the ppp0 interface, and I can see mbuni trying to send packets on 
>>>>>>> port 80 to the AT&T proxy (wireless.cingular.com), but the source 
>>>>>>> address is my Ethernet IP instead of what's assigned to ppp0:
>>>>>>> 
>>>>>>> tcpdump -i ppp0 -n
>>>>>>> tcpdump: verbose output suppressed, use -v or -vv for full protocol 
>>>>>>> decode
>>>>>>> listening on ppp0, link-type LINUX_SLL (Linux cooked), capture size 96 
>>>>>>> bytes
>>>>>>> 23:26:12.984086 IP 172.18.3.15.45500 > 66.209.11.32.80: Flags [S], seq 
>>>>>>> 3553051624, win 5840, options [mss 1460,sackOK,TS val 151026241 ecr 
>>>>>>> 0,nop,wscale 5], length 0
>>>>>>> 
>>>>>>> 
>>>>>>> I've got a static route in place and I can do 'telnet 
>>>>>>> wireless.cingular.com 80' and it connects to the proxy fine.
>>>>>>> 
>>>>>>> Any ideas?  I'm looking at changing the libcurl stuff in mmsbox-mm1, 
>>>>>>> but I thought I'd check to see if there was an easier way.
>>>>>>> 
>>>>>>> Here's my custom-settings:
>>>>>>> 
>>>>>>> group = mmsc
>>>>>>> id = modem
>>>>>>> type = custom
>>>>>>> custom-settings = "smsc-on=lynx -dump 
>>>>>>> 'http://localhost:13000/start-smsc?password=pass&smsc=modem';smsc-off=lynx
>>>>>>>   -dump 
>>>>>>> 'http://localhost:13000/stop-smsc?password=pass&smsc=modem';gprs-on=/root/startppp.sh;gprs-pid=cat
>>>>>>>  /root/ppp-wrapper.pid|head 
>>>>>>> -1;port=13014;mmsc-url=http://mmsc.cingular.com;proxy=wireless.cingular.com:80;msisdn=6128891111";
>>>>>>>  
>>>>>>> mmsc-library = /usr/local/lib/libmmsbox_mm1.so
>>>>>>> 
>>>>>>> 
>>>>>>> Thanks in advance,
>>>>>>> 
>>>>>>> -Ray
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> _______________________________________________
>>>>>>> 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
>>>> 
>>>> _______________________________________________
>>>> 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
> 
> _______________________________________________
> 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

Reply via email to