I think it will be much simpler if you code a script from zero, instead of having to translate every wap page into an SMS (which may end up in more than 160 chars).
On Fri, Oct 17, 2008 at 12:06 PM, Carlos Ruiz Diaz <[EMAIL PROTECTED]> wrote: > Thank for the reply Stipe. > Let me explain myself better with an example, maybe there was something > wrong with my bad English :). > I want to send the following kind of messages to the users: > ---------------------------- > Make your choice: > A. Vote for Carlos > B. Vote for Augusto > ---------------------------- > if the user sends me a reply with an "A" or "B" I want to send: > > -------------------------------------------------------- > You have selected the option "A|B" > -------------------------------------------------------- > > and if not: > > -------------------------------------------------------- > No such option > -------------------------------------------------------- > > I already have a wap page for the above example and but I don't know if > there exists a way to translate it transparently to interactive SMS or I > should write my own system using sms services with keywords like "A", "B". > > > > > > > On Fri, Oct 17, 2008 at 8:20 AM, Stipe Tolj <[EMAIL PROTECTED]> wrote: >> >> Alejandro Guerrieri schrieb: >> > Carlos, >> > >> > Of course you could program a system that responds an SMS with a >> > wap-push that points to a particular wap page, but I'm not sure if >> > that's what you're trying to achieve. Could you please clarify further? >> > >> > Regarding sending wap pages using SMS transport, that sounds a lot like >> > [EMAIL PROTECTED] which is precisely that (a subste of wml over SMS >> > transport). If >> > that's the case, Kannel cannot help you on that department, you'd need a >> > [EMAIL PROTECTED] gateway for that. >> >> what is [EMAIL PROTECTED] Any URL reference for that? >> >> A WAP Push can have a WML conent-type as payload. From a protocol >> architecture >> this is possible, as the PPG (push proxy gateway) knows how to encode >> this. >> >> The problem is (like most times) on the device side. I don't know exactly >> how >> many devices are out there that DO support WAP push messages, but KNOW how >> to >> interpret WML pushed payload too. Obviously they know how to display WML, >> using >> the browser component in the device. But the WAP Push component has >> usually an >> "own browser" that does the handling. So there is no nice "registry mime >> type" >> correlation as we know if from the Windows world ;) >> >> In addition USSD may be used for what you intend to do. But this requires >> again >> more dependencies in the core network structure and a dedicated USSD >> gateway too. >> >> The way I would do it: >> >> - let the user initiate, via a normal MO SMS keyword >> - send a WAP push SI (session indication) to the user, this will pop up on >> the >> screen and ask the user if he wants to make his decission. >> - the user can either say "yes" or "no", yes means opening the embeded >> URL. >> - and the URL is your WML deck with the decision A or B. >> >> This has the benefits: >> >> a) you know that SI documents work on any WAP push capable phones, no >> failures. >> b) adding a session ID to the URL in the SI, maps the MSISDN of the user >> into >> your application, so when the user "comes into" the application you know >> who it >> is by MSISDN number, which makes later notifications or other SMS >> transmissions >> MT wise very easy to him >> >> 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 >> ------------------------------------------------------------------- >> > >
