Slashdot Mirror

Beats me, but I wrote a notification service in 2007 using Kannel and that goes back to Oct 2004 date as the reference implementation for WAP 2.0.... Something tells me it's older than that. In fact, IIRC, I wrote an email/SMS sending app back around 2003 that leveraged some commercial service for another job, and they weren't new either, but I can't recall who that was.

Verizon has consistantly pissed me off since I got their service, they've killed Kannel on their network, upgraded to prevent hacking the GetItNow service, and the only way to add custom anything is to locate an impossible to find cable & hack it using BitPim

Sure, you CAN add custom photos and ringtones, which I might do if I had to pay ONCE for, but Verizon charges a monthly fee just for having them on your phone. It's a blatent ripoff and I got tired of being fucked by Verizon.

I don't have any input on them crippling bluetooth, but frankly it doesn't suprise me. This company is a shit providor and I don't understand why anyone has their service. I'm sure they will offer better Bluetooth enabled devices, with many new features, as long as you pay X amount per month to have them enabled, and a fee for using them, and the fee for airtime, and the activation fee, and ...

Well, we USED to be able to run our own free SMS services that only cost airtime via kannel, but Verizon quickly upgraded their network to stop people from bypassing their overly-inflated rates.

Fuck Verisign, er...Verizon

Just set up your own kannel wap gateway. Use your own gateway instead of the one your provider gives you (it's in your wap settings). They might block it though (my provider started blocking this last month)... But if they do, you should complain, because there's no legit reason to keep you from connecting to your own servers, when it's clearly possible, and requires no effort on their part. Oh, take a look at push too. You can use Kannel for this. You might need a way to get content to the mobile net though, to send sms.

We used an old Sun Ultra 5 acting as the "base station" and Kannel to talk to a mobile phone plugged into the serial port. That's basically it. We could generate an SMS via email or directly scripting Kannel, depending on what we were trying to do, and also provided a webform for human use.

Wapit was making Mobile Phone Service Stuff. You know, stuff for this "WAP" thing that was such a major success that almost three people bought a cell phone that supported it and one actually tried the services once... one prominent figure employed by them was Lars Wirzenius, friend of Linus Torvalds, a Debian guy and, um, appeared in the newsgroups or something.

Some stuff from Wapit is still alive due to this "open source" idea thingy. People say Kannel beats Nokia's WAP/SMS gateway software easily =)

Kannel, a free WAP and SMS gateway, for all your ringtoning needs.

There are Ways to do this... I know a couple of sites on the web that will do it, but i doubt that they are Free (such as MTNSMS)

The probable cheapest way to do this is with a Linux BOX, a GSM Modem, and some SMS gateway software (such as: kannel).

Using this method, you could provide each user with a number of there own, and all messages sent to that number use your GSM Modem number as thier SMS Gateway. The messages can then be delivered straight into a mailbox, or an SQL DB for a Web App etc....

You may try Kannel. Its is a free open source WAP and SMS gateway.

There's no difference between WML pages and HTML pages other than the MIME type that is used and the format in which they're written. Hence Apache can be used to serve them.

If, on the other hand, you wish to make a dialin gateway that WAP devices can talk to, you'll need something like Kannel.

Good article but I found some technical misnomers in the features of wap...
Wireless Sessions- actually wap support connection orientated and connection-less sessions, which means you have to choose the connection orientated session in both the client and the server(the default in most servers is connection-less). Connection orientated sessions are slower because they have the overhead of tcp/ip like handshake.
Device Abstraction - this is a bad thing! it is simliar to the problems writing html content for IE and netscape. Here you are creating special versions for specific phones. Isn't this what standards are suppposed to avoid?
Bearer Abstraction - this is wap's biggest strength.
Data/Header Compression - actually they are compiled to byte code.
Reliability - wap doesn't support fragmentation, which means if you send a packet that is too big for the phone (i.e. Nokia 7110 has a max page size of less than 1400 bytes) it blows!
Otherwise a good article, although a bit biased towards the author's company. Also no mention of the open source wap gateway project Kannel

Of course the proprietary 5nine.net solution might be workable (couldn't see a download though.)

This article really left me thinking, though. How could I get free advertisment for my closed-source product on Slashdot... yeah! Now I know. I'll write a introductory article to a opinions website and link it to my product, then email CmdrTaco!

Presto!

The most advanced is currently Kannel, followed by Ophelia and GNUws.

And here is the gateway link missing from the article :)