Re: SMS schdeduling
in case your SMSC does not support deferred flag what about simple usage of crontab or nice or at driven script? in case you use *nix, info crontab, info at, info nice, in case you use MS, there are some free decent proggies for scheduling task i believe .. -Original Message- From: Ajay Chadha [EMAIL PROTECTED] Sent: 11 ??? 2007 ?. To: seik Subject:SMS schdeduling Dear i am using kannel with plasms . i am lokking for sms scheduling application like reminder services etc is there any open source application i am googled but did not find any , please help me out on this ajay
ERROR: SMPP: Unknown TLV(0x0210,0x0001,34) for PDU type (deliver_sm) received!
Hi, recently switched to a new SMSC and started getting the following error: 2007-05-11 11:41:33 [14907] [8] ERROR: SMPP: Unknown TLV(0x0210,0x0001,34) for PDU type (deliver_sm) received! version = kannel 1.4.0, libxml 2.6.26 I'd appreciate any help.
Re: smppbox reg.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] wrote: Hi friends, I got a msg from our mailing list like this. Kannel is just SMSC client not SMSC server :) You need to buy separate module, like smppbox which is a commercial product, to enable kannel as SMSC :) contact creator of kannel :) what is mean by smppbox and if we had the smppbox we can send sms from pc via internet to mobile without any other service provider like clickatel or other sms centre service providers.. As Rene stated, smppbox is a SMPP server add-on component to the normal Kannel allowing you to act as vSMSC (vitual SMSC), leaveraging client SMSC connections as own SMPP server to customers. ie. as SMS aggregator. There is NO WAY to transmit a SMS without bridging from the IP world (internet) into the GSM (SS7 layer) world via a SMSC. What Kannel DOES support is connecting GSM modems to act as it's SMSC connections, so you can send SMS via a connected mobile, and hence use the SIM card in the modem for sending. 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 - --- -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGRDI/9ez0oeKvYs0RAlurAJ9YQU2TTSEyLThSDlNgnzqMGbgy4QCg6j17 aIrxuyLDfrYssdLvveG2zdE= =YCAU -END PGP SIGNATURE-
Kannel-service (param %s: messagetyp not supported)
Hello i need Information / help in case KANNEl-SERVICE. Ih have written a kannel service: if sms receives a perl-script starts to select some DB-Information (Sybase-DB). The result i push to to the requester-gsm via the Kannel-param %s This works on all Siemens-Benq - GSMs. But now i am informed that all Nokia or Motorola or else handies do not work. The message alwas is like this messagetyp not supported Whe i send the same message by Kannel-http-request it works. Some idea ? thank you very much Gottfried e.g. kannel-service group= sms-service keyword = key_bereit exec = perlscriptname.pl %s max-messages = 10 concatenation= true
RE: smppbox reg.
To be complete: There do exist Kannel SS7 smsc drivers. They are just not open source. Rene Kluwen Chimit -Original Message- From: Stipe Tolj [mailto:[EMAIL PROTECTED] Sent: vrijdag 11 mei 2007 11:07 To: [EMAIL PROTECTED] Cc: users@kannel.org Subject: Re: smppbox reg. -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] wrote: Hi friends, I got a msg from our mailing list like this. Kannel is just SMSC client not SMSC server :) You need to buy separate module, like smppbox which is a commercial product, to enable kannel as SMSC :) contact creator of kannel :) what is mean by smppbox and if we had the smppbox we can send sms from pc via internet to mobile without any other service provider like clickatel or other sms centre service providers.. As Rene stated, smppbox is a SMPP server add-on component to the normal Kannel allowing you to act as vSMSC (vitual SMSC), leaveraging client SMSC connections as own SMPP server to customers. ie. as SMS aggregator. There is NO WAY to transmit a SMS without bridging from the IP world (internet) into the GSM (SS7 layer) world via a SMSC. What Kannel DOES support is connecting GSM modems to act as it's SMSC connections, so you can send SMS via a connected mobile, and hence use the SIM card in the modem for sending. 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 - --- -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGRDI/9ez0oeKvYs0RAlurAJ9YQU2TTSEyLThSDlNgnzqMGbgy4QCg6j17 aIrxuyLDfrYssdLvveG2zdE= =YCAU -END PGP SIGNATURE-
Re: Problem: Wap push as a text SMS
Alejandro, your application does not work for this operator. The original we have (that works for the other operators) is very similiar to this one, and as it depends on the actual kannel and smsc configuration, the problem remains. We built a small java application that opens a socket to the smsc, it builds the smpp package as the smpp v.3.4 specifications, it encodes all the necesary things and send them throught the connection. As you see, we are not using any kannel libraries nor special stuff, we only took the ".cap" file the operator gaved us (with their working example), we splited it, changed some things, and send it. This works really fine, but as i said in the first time... that is not the final idea. Regards Joaquin, Yep, I've noticed that right after pushing "send" :P What are you using to construct the binary message? I've made a small php function a few years ago to encode a wap push. It's on the list archives here: http://osdir.com/ml/mobile.kannel.user/2004-04/msg7.html Please try encoding the wap-push with it, maybe you have more luck that way. I'm using it with many operators on many Latin American countries with no problems. Kannel can set the DCS by using headers/parameters on the sendsms interface, but I'm not sure if the SMPP driver supports this. Hope it helps, Alejandro. On 5/10/07, Joaquin Vera A. [EMAIL PROTECTED] wrote: Yes, the operator accepts binary messages, as i said previously "we know is not an operator's problem cause if we send the packages manually throught a socket connection, the wap push works" Taking this base, we had to contruct an application to send the wap pushes... so, for now, we receive ans send sms throught kannel, but send the wap push throught this small application; but the final idea is to use kannel for all the services (as we have with the others operators) We already ask the operator about this, and the problem is ours (also, other people connected with this operator, also had to construct an application to send the wap pushes 'cause kannel didnt make it and cant pay for licenced applications) Greetings Joaquin, Are you sure that the operator accepts binary messages? If you're sure that the binary message is ok (and it seems, since it works with other operators) maybe you should ask the operator about it. Maybe he has to configure something to allow you to send binary messages (wap-pushes for example). Hope it helps, Alejandro. On 5/10/07, Joaquin Vera A. [EMAIL PROTECTED] wrote: Hi all, i hope that anyone can help me, we are trying to send a Wap Push, but the phone receives a SMS instead (with a lot of weird characters) Here are the actual details: - We use kannel 1.4.1, downloaded from CVS and installed with the following options in Debian: --with-mysql --enable-pcre --disable-docs --disable-keepalive --disable-ssl --with-sysconfdir=/etc/kannel - Is already connected to the operator's SMSC and we can send and receive normal SMS - The orig and dest TONs and NPI are fixed as 1, as the operator said to us - The posting URL we are using is: http://host:port/cgi-bin/sendsms?username=userpassword=passto=numberfrom=4 number shor codeudh=%06%05%04%0B%84%23%F0text=%1B%06%01%AE%02%05%6A%00%45%C6%0C%03%77%61%70%2E%74%6D%6F%76%69%6C%2E%63%6C%2F%74%6D%63%2F%70%6F%72%74%61%6C%2F%77%61%70%2F%6A%75%65%67%6F%73%2F%69%6E%64%65%78%2E%70%68%70%3F%49%44%58%50%3D%26%49%44%42%41%53%45%3D%33%26%49%44%4E%4F%44%4F%3D%33%00%01%03%4D%6F%76%69 - Using this same configuration and post url but for ANOTHER Operator, the wap push is received OK - We have an example (a trace) of a correct wap push, and the differences we see with our trace are in the Data Coding (0xf5 in the correct one, and 0x04 in ours), Header lenght (20 bytes in the correct one and 32 bytes in ours ---may be the 12 extra bytes are the "options", cause our trace names "options: (12 bytes)", and the correct trace does not name it), and a "extra" line inside the indication tag where the url is (the correct one has indication href='' '1''Title'/indication -- has a "1" after the URL) We know is not an operator's problem cause if we send the packages manually throught a socket connection, the wap push works. How can we solve this? How can we set the DCS in kannel? Please, would be a great help if any of you can guide us Regards -- ___ Joaqun Vera Aguilera Technology Supervisor Mobile:+56 (8) 500 4290 / +56 (9) 675 6727 Phone: +56 (2) 333 1650 Fax:+56 (2) 333 0597 Skype: joaquinatech Email:[EMAIL PROTECTED] URL:http://www.andinatech.com
Re: Problem: Wap push as a text SMS
Well, this is a first case, then. We've tried this function with many operators and never had any problems. You may check the wap-push specs, maybe something shows up there. Regards, Alejandro. On 5/11/07, Joaquin Vera A. [EMAIL PROTECTED] wrote: Alejandro, your application does not work for this operator. The original we have (that works for the other operators) is very similiar to this one, and as it depends on the actual kannel and smsc configuration, the problem remains. We built a small java application that opens a socket to the smsc, it builds the smpp package as the smpp v.3.4 specifications, it encodes all the necesary things and send them throught the connection. As you see, we are not using any kannel libraries nor special stuff, we only took the .cap file the operator gaved us (with their working example), we splited it, changed some things, and send it. This works really fine, but as i said in the first time... that is not the final idea. Regards Joaquin, Yep, I've noticed that right after pushing send :P What are you using to construct the binary message? I've made a small php function a few years ago to encode a wap push. It's on the list archives here: http://osdir.com/ml/mobile.kannel.user/2004-04/msg7.html Please try encoding the wap-push with it, maybe you have more luck that way. I'm using it with many operators on many Latin American countries with no problems. Kannel can set the DCS by using headers/parameters on the sendsms interface, but I'm not sure if the SMPP driver supports this. Hope it helps, Alejandro. On 5/10/07, Joaquin Vera A. [EMAIL PROTECTED] wrote: Yes, the operator accepts binary messages, as i said previously we know is not an operator's problem cause if we send the packages manually throught a socket connection, the wap push works Taking this base, we had to contruct an application to send the wap pushes... so, for now, we receive ans send sms throught kannel, but send the wap push throught this small application; but the final idea is to use kannel for all the services (as we have with the others operators) We already ask the operator about this, and the problem is ours (also, other people connected with this operator, also had to construct an application to send the wap pushes 'cause kannel didnt make it and cant pay for licenced applications) Greetings Joaquin, Are you sure that the operator accepts binary messages? If you're sure that the binary message is ok (and it seems, since it works with other operators) maybe you should ask the operator about it. Maybe he has to configure something to allow you to send binary messages (wap-pushes for example). Hope it helps, Alejandro. On 5/10/07, Joaquin Vera A. [EMAIL PROTECTED] wrote: Hi all, i hope that anyone can help me, we are trying to send a Wap Push, but the phone receives a SMS instead (with a lot of weird characters) Here are the actual details: - We use kannel 1.4.1, downloaded from CVS and installed with the following options in Debian: --with-mysql --enable-pcre --disable-docs --disable-keepalive --disable-ssl --with-sysconfdir=/etc/kannel - Is already connected to the operator's SMSC and we can send and receive normal SMS - The orig and dest TONs and NPI are fixed as 1, as the operator said to us - The posting URL we are using is: http://host:port/cgi-bin/sendsms?username=userpassword=passto=numberfrom=4 number shor codeudh=%06%05%04%0B%84%23%F0text=%1B%06%01%AE%02%05%6A%00%45%C6%0C%03%77%61%70%2E%74%6D%6F%76%69%6C%2E%63%6C%2F%74%6D%63%2F%70%6F%72%74%61%6C%2F%77%61%70%2F%6A%75%65%67%6F%73%2F%69%6E%64%65%78%2E%70%68%70%3F%49%44%58%50%3D%26%49%44%42%41%53%45%3D%33%26%49%44%4E%4F%44%4F%3D%33%00%01%03%4D%6F%76%69 - Using this same configuration and post url but for ANOTHER Operator, the wap push is received OK - We have an example (a trace) of a correct wap push, and the differences we see with our trace are in the Data Coding (0xf5 in the correct one, and 0x04 in ours), Header lenght (20 bytes in the correct one and 32 bytes in ours ---may be the 12 extra bytes are the options, cause our trace names options: (12 bytes), and the correct trace does not name it), and a extra line inside the indication tag where the url is (the correct one has indication href='http://lalalala.com' '1''Title'/indication -- has a 1 after the URL) We know is not an operator's problem cause if we send the packages manually throught a socket connection, the wap push works. How can we solve this? How can we set the DCS in kannel? Please, would be a great help if any of you can guide us Regards -- ___ *Joaquín Vera Aguilera* Technology Supervisor ** Mobile: +56 (8) 500 4290 / +56 (9) 675 6727 Phone: +56 (2) 333 1650 Fax: +56 (2) 333 0597 Skype:joaquinatech Email: [EMAIL PROTECTED] [EMAIL PROTECTED] URL:
Re: ERROR: SMPP: Unknown TLV(0x0210, 0x0001, 34) for PDU type (deliver_sm) received!
The other party is sending a TLV (Tag, Lenght, Value) that Kannel does not understand, so it's ignored. It's not really an error in fact. Unless they're using this TLV to tell you something (some SMSC use it for billing purposes or to send a message ticket to enforce 1x1 MO/MT balance, for example) you may ignore the error. You should check with your operator to check if this TLV should be used for anything. Hope it helps, Alejandro Guerrieri On 5/11/07, Robert Itwara Busingye [EMAIL PROTECTED] wrote: Hi, recently switched to a new SMSC and started getting the following error: 2007-05-11 11:41:33 [14907] [8] ERROR: SMPP: Unknown TLV(0x0210,0x0001,34) for PDU type (deliver_sm) received! version = kannel 1.4.0, libxml 2.6.26 I'd appreciate any help. -- Alejandro Guerrieri Magicom http://www.magicom-bcn.net/ LinkedIn: http://www.linkedin.com/in/aguerrieri
pdu error
i always get this error after sending sms it seems to be some kind of delivery report , i am using Sony erricsson Model K608i as GSM modem with CNMI:2,3,0,1,0 +CDS: 29 2007-05-12 09:31:09 [26924] [6] DEBUG: AT2[sony]: -- 06E30C91194973697075705021 80743400705021906263070D 2007-05-12 09:31:09 [26924] [6] DEBUG: AT2[sony]: received message from SMSC: C0 19919437 2007-05-12 09:31:09 [26924] [6] ERROR: AT2[sony]: could not decode PDU to a mess age. please tell me where i am wrong i have set broken = true in kannel.conf otherwise i get pdu_extract failed and i am also unable to get delibvery reports ajay