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" <[email protected]>
To: <[email protected]>
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" <[email protected]>
To: <[email protected]>
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
[email protected]
http://lists.mbuni.org/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.mbuni.org/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.mbuni.org/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.mbuni.org/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.mbuni.org/mailman/listinfo/users