R: [OTA] Sending Concatenated OTA Commands
Can I suggest searching dotmobi binary sms article ? Julien Buratto Linkas SRL Tel.02 30321419 -Original Message- From: Christopher Burke christopher.bu...@simulity.com Sender: users-bounces@kannel.orgDate: Tue, 26 Jun 2012 20:04:36 To: users@kannel.org Subject: [OTA] Sending Concatenated OTA Commands Hi All, I was wondering how I would go about setting the UDH parameter to send concatenated OTA commands. Currently, I set the UDH to 02 70 00 (%02%70%00) however it is my understanding that for concatenated SMS each message needs to be assigned a message part, i.e. 05 00 03 XX 0N 0n where: 05: UDH Length 00: IEI, Concatenated Short Messages 03: IE Data Length XX: Reference Number 0N: Number of Short Messages 0n: Sequence Number of the current Short Message I am going to go on a whim, and presume it should be something like: *09 02 70 00 05 00 03 XX 0N 0n* or *08 70 00 05 00 03 XX 0N 0n* (%09%02%70%00%05%00%03%XX%0N%0n) or (%08%70%00%05%00%03%XX%0N%0n) Any help or advice would be much appreciated! Kind Regards, Christopher -- *Christopher Burke* Software Engineer / Smart Card Developer http://simulity.com Mobile: +44 7590 571 833 Skype:krslynx
R: Re: R: Kannel MySQL problem
Why don't you try to measure how long that happens from start of connection ? Ie: start kannel and see what happens after x seconds until it goes to error.. Maybe is a timeout.. 120 secs is short if kannel is not keepaliving the connection.. Also check your my.cnf file as the compiled mysql libs us such conf file And check that libs are same version of server.. Test another mysql server instance and see if it happens again Julien Buratto Linkas SRL Tel.02 30321419 -Original Message- From: Moazzam Ali moz...@gmail.com Date: Sat, 23 Jun 2012 18:41:13 To: spamedenspame...@gmail.com Cc: julien.bura...@linkas.it; users-boun...@kannel.org; users@kannel.org Subject: Re: R: Kannel MySQL problem already upgraded to latest snapshot but error still persists 2012-06-23 13:29:59 [14633] [6] ERROR: MYSQL: database check failed! 2012-06-23 13:29:59 [14633] [6] ERROR: MYSQL: MySQL server has gone away On 06/23/2012 4:43 PM, spameden wrote: Why don't you use latest from the trunk? There were lots of fixes since 1.4.3. 2012/6/23 Moazzam Ali moz...@gmail.com mailto:moz...@gmail.com complied kannel 1.4.3 stable with mysql support from source on CentOS 6 64-bit //moazzam On 06/23/2012 4:40 PM, spameden wrote: How did you install kannel? Is it from debian's packages? Try to install latest from SVN. 2012/6/23 Moazzam Ali moz...@gmail.com mailto:moz...@gmail.com wait_timeout is set to 120, is it the case? there is no firewall between mysql and kannel as they are both on localhost //moazzam On 06/23/2012 2:38 AM, Julien Buratto wrote: Ali, Check also timeouts values in mysql.. Are you using a custom configured mysql ? Do you have any firewall/proxy/etc in between ? Julien Buratto Linkas SRL Tel.02 30321419 -Original Message- From: Moazzam Ali moz...@gmail.com mailto:moz...@gmail.com Sender: users-bounces@kannel.orgDate mailto:users-bounces@kannel.orgDate: Fri, 22 Jun 2012 23:33:00 To: users@kannel.org mailto:users@kannel.org Subject: Kannel MySQL problem I am facing one issue with the kannel 1.4.3 and MySQL, due to some unknown reason sometime kannel throw following error in the log 2012-06-22 17:14:50 [18671] [6] ERROR: MYSQL: database check failed! 2012-06-22 17:14:50 [18671] [6] ERROR: MYSQL: MySQL server has gone away 2012-06-22 17:14:50 [18671] [6] DEBUG: DBPool has too few connections, reconnecting up to maximum... 2012-06-22 17:14:50 [18671] [6] INFO: MYSQL: Connected to server at localhost. 2012-06-22 17:14:50 [18671] [6] INFO: MYSQL: server version 5.1.61-log, client version 5.1.61. 2012-06-22 17:14:50 [18671] [6] INFO: MYSQL: Connected to server at localhost. 2012-06-22 17:14:50 [18671] [6] INFO: MYSQL: server version 5.1.61-log, client version 5.1.61. i have already tried increasing the max_connection both in kannel db connection setting and in my.cnf but still same
R: Kannel MySQL problem
Ali, Check also timeouts values in mysql.. Are you using a custom configured mysql ? Do you have any firewall/proxy/etc in between ? Julien Buratto Linkas SRL Tel.02 30321419 -Original Message- From: Moazzam Ali moz...@gmail.com Sender: users-bounces@kannel.orgDate: Fri, 22 Jun 2012 23:33:00 To: users@kannel.org Subject: Kannel MySQL problem I am facing one issue with the kannel 1.4.3 and MySQL, due to some unknown reason sometime kannel throw following error in the log 2012-06-22 17:14:50 [18671] [6] ERROR: MYSQL: database check failed! 2012-06-22 17:14:50 [18671] [6] ERROR: MYSQL: MySQL server has gone away 2012-06-22 17:14:50 [18671] [6] DEBUG: DBPool has too few connections, reconnecting up to maximum... 2012-06-22 17:14:50 [18671] [6] INFO: MYSQL: Connected to server at localhost. 2012-06-22 17:14:50 [18671] [6] INFO: MYSQL: server version 5.1.61-log, client version 5.1.61. 2012-06-22 17:14:50 [18671] [6] INFO: MYSQL: Connected to server at localhost. 2012-06-22 17:14:50 [18671] [6] INFO: MYSQL: server version 5.1.61-log, client version 5.1.61. i have already tried increasing the max_connection both in kannel db connection setting and in my.cnf but still same
Re: not getting DLRs
Check the docs and search for smsbox-id on the smsbox config. When inserting the SMS, use that value in the boxc_id field of the db 2012/6/17 alok srivastava alok...@gmail.com Sir (are u telling for boxc_id field of send_sms table. plz have a look on configuration files coz there is no smsboxid field in my configuration file. *my kannel.conf* group = core admin-port = 16000 smsbox-port = 16001 admin-password = iadmin log-file = /project/kannel/logs/kannel4.log log-level = 0 #box-deny-ip = *.*.*.* #box-allow-ip = 127.0.0.1 dlr-storage = mysql group = smsc smsc = smpp smsc-id = bsnl host = 174.36.194.138 port = transceiver-mode = 1 receive-port = 14090 smsc-username = ? smsc-password = ? system-type = smpp address-range = group = smsbox bearerbox-host = 127.0.0.1 sendsms-port = 16013 global-sender = 16013 #sendsms-chars = 0123456789 +- log-file = /project/kannel/logs/smsbox4.log log-level = 0 access-log = /project/kannel/logs/access4.log group = sendsms-user username = abc_zxc password = qaz123 #user-deny-ip = user-allow-ip = *.*.*.* #dlr-url = http%3A%2F%2F122.160.154.189%2F%3Fdlrstring%3D%25a%26refid%3D249 #--- mysql connection group = mysql-connection id = mydlr host = localhost username = kannel password = distinct database = kannel max-connections = 1 # DLR table structure group = dlr-db id = mydlr table = kannel_dlr4 field-smsc = smsc field-timestamp = timestamp field-destination = destination field-source = source field-service = service field-url = url field-mask = mask field-status = status field-boxc-id = boxc_id *my sqlbox.conf* group = sqlbox id = sqlbox-db smsbox-id = sqlbox #global-sender = bearerbox-host = localhost bearerbox-port = 14001 smsbox-port = 14005 smsbox-port-ssl = false sql-log-table = sent_sms sql-insert-table = send_sms log-file = /var/log/kannel/kannel-sqlbox.log #log-file = /root/sqlbox-0.7.2/log/kannel4-sqlbox.log log-level = 0 group = mysql-connection #id = my-sqlbox id = sqlbox-db #id = mydlr host = localhost username = kannel password = iamalive database = kannel #max-connections = 1 Regards Abhi On Sun, Jun 17, 2012 at 6:22 PM, Julien Buratto julien.bura...@linkas.itwrote: ** Do you also run the smsbox ? If so, check also that when inserting the row in the db, you set the smsbox id in the sql as the smsbox id of the smsbox's config file Julien Buratto Linkas SRL Tel.02 30321419 -- *From: * alok srivastava alok...@gmail.com *Sender: * users-boun...@kannel.org *Date: *Sun, 17 Jun 2012 18:14:42 +0530 *To: *users@kannel.org *Subject: *not getting DLRs dear my kannel is working fine when things are passed from url. but when i try to send the message from send_sms table message send and move to sent_sms and also delivered to phone properly but not getting Delivery report. regards abhi -- Julien Buratto Linkas SRL Tel. 0230321419
Re: Different behaviour on concatenated with SQLBOX compared to SMSBOX
Hello, anyone has hints on what I could check/read/change in order to fix this strange thing ? Thanks Julien 2012/6/13 Julien Buratto julien.bura...@linkas.it Hello, when I send a long message via http to SMSBOX, everything is fine. When I use SQLBOX, I get a: 2012-06-13 17:08:18 [19527] [6] ERROR: SMPP[mysmsc]: SMSC returned error code 0x0001 (Message Length is invalid) in response to submit_sm. I'm inserting the text of the message into the send_sms.msgdata I'm I doing something wrong ? Show I set some other fields like sms_type ? -- Julien Buratto Linkas SRL Tel. 0230321419 -- Julien Buratto Linkas SRL Tel. 0230321419
R: not getting DLRs
Do you also run the smsbox ? If so, check also that when inserting the row in the db, you set the smsbox id in the sql as the smsbox id of the smsbox's config file Julien Buratto Linkas SRL Tel.02 30321419 -Original Message- From: alok srivastava alok...@gmail.com Sender: users-bounces@kannel.orgDate: Sun, 17 Jun 2012 18:14:42 To: users@kannel.org Subject: not getting DLRs dear my kannel is working fine when things are passed from url. but when i try to send the message from send_sms table message send and move to sent_sms and also delivered to phone properly but not getting Delivery report. regards abhi
Different behaviour on concatenated with SQLBOX compared to SMSBOX
Hello, when I send a long message via http to SMSBOX, everything is fine. When I use SQLBOX, I get a: 2012-06-13 17:08:18 [19527] [6] ERROR: SMPP[mysmsc]: SMSC returned error code 0x0001 (Message Length is invalid) in response to submit_sm. I'm inserting the text of the message into the send_sms.msgdata I'm I doing something wrong ? Show I set some other fields like sms_type ? -- Julien Buratto Linkas SRL Tel. 0230321419
Re: [Queued] Receive Messages using Kannel
to the recv Kannel to appear in the sent_sms table (I sometimes get them to appear if I send a message to the phone, and respond). Any pointers or help is much appreciated! Kind Regards, Christopher -- Julien Buratto Linkas SRL Tel. 0230321419
Re: kannel_dlr not recieving all the dlrs
can you please paste some portion of logs ? It might be a wrong database table (so kannel is not able to write the dlr in it) or simply the process is very quick and you don't see it :-) 2012/6/13 alok srivastava alok...@gmail.com daer pl tell me kannel_dlr table not recieving every sent sms dlrs while every time i insert same data from send_table some times it's showing the dlr entry in kannel_dlr table and sometimes not. plz help me not able to understand why it's going on. regards abhi -- Julien Buratto Linkas SRL Tel. 0230321419
Re: ubique id in send-table
Please read http://www.blogalex.com/wp-content/uploads/2008/11/userguide.html#AEN478 2012/6/12 alok srivastava alok...@gmail.com Sir plz tell me which field we will use as a reference id (ubique id for sms) in send-table, when inserting record in send-table. regards abhi -- Julien Buratto Linkas SRL Tel. 0230321419
Re: [Queued] Receive Messages using Kannel
Can you extract some logs ? I'm sure they will tell us more of what's happening 2012/6/13 Christopher Burke christopher.bu...@simulity.com Hi Julien, Strangely, I sometimes see received messages in my sent_sms table, do you know why this might occur? Kind Regards, Christopher On 13 June 2012 18:15, Julien Buratto julien.bura...@linkas.it wrote: The sent_sms table stores the sms that have been sent. Not the SMS that get received :-) It may happen that you see them appearing there when you send them from your sending instance of kannel ? So basically when you send a message (ie INSERT a row in the send_sms table), the sms get routed to your SMSC and then removed from the send_sms table and copied into the sent_sms table. When you receive messages, you should take care of saving them in your script: http://sub.url.tld/sms.php?p=%pmsg=message 2012/6/13 Christopher Burke christopher.bu...@simulity.com Hi, I currently have two SMSCs running on two separate Kannel instances. I am using version -r4979 Kannel from the SVN on a Linux machine, and I have set up the Kannel instances as follows: three separate configuration files for the bearerbox, smsbox and sqlbox respectively shown below. send_kannel.conf # KANNEL CONFIGURATION # group = core admin-port = 14000 smsbox-port = 14001 admin-password = ** log-file = /var/log/kannel/send/log_core.log access-log = /var/log/kannel/send/acc_core.log log-level = 0 box-deny-ip = *.*.*.* box-allow-ip = *.*.*.* # SMSC Connections# group = smsc smsc = smpp smsc-id = ** host = ** port = transceiver-mode = true smsc-username = ** smsc-password = ** system-type = SMPP address-range = ** source-addr-ton = 1 source-addr-npi = 1 dest-addr-ton = 1 dest-addr-npi = 1 bind-addr-ton = 1 bind-addr-npi = 1 group = smsbox send_smsbox.conf # KANNEL CONFIGURATION # group = core smsbox-port = 14005 group = smsbox smsbox-id = send_smsbox bearerbox-host = localhost bearerbox-port = 14005 sendsms-port= 14013 global-sender = 447797882105 sendsms-chars = 0123456789+ # -+ log-file= /var/log/kannel/send/log_smsbox.log log-level = 0 access-log = /var/log/kannel/send/acc_smsbox.log # SENDSMS USER CONFIGURATIONS # group = sendsms-user username = wim password = wim send_sqlbox.conf # KANNEL CONFIGURATION # group = sqlbox id = send_sqlbox smsbox-id = send_sqlbox #global-sender = bearerbox-host = localhost bearerbox-port = 14001 smsbox-port = 14005 smsbox-port-ssl = false sql-log-table = sent_sms sql-insert-table = send_sms log-file = /var/log/kannel/send/log_sqlbox.log log-level = 0 #ssl-client-certkey-file = #ssl-server-cert-file = #ssl-server-key-file = #ssl-trusted-ca-file = group = mysql-connection id = send_sqlbox host = localhost username = ** password = ** database = kannel I then launch Kannel with the following Shell script: #!/bin/bash # BEARERBOXES nohup /usr/local/sbin/bearerbox -v 1 /etc/kannel/recv/recv_kannel.conf nohup /usr/local/sbin/bearerbox -v 1 /etc/kannel/send/send_kannel.conf sleep 5 # SQLBOXES nohup /usr/local/sbin/sqlbox -v 1 /etc/kannel/recv/recv_sqlbox.conf nohup /usr/local/sbin/sqlbox -v 1 /etc/kannel/send/send_sqlbox.conf sleep 5 # SMSBOXES nohup /usr/local/sbin/smsbox -v 1 /etc/kannel/recv/recv_smsbox.conf nohup /usr/local/sbin/smsbox -v 1 /etc/kannel/send/send_smsbox.conf So I have two SMSCs, one which sends messages and another which receives messages. Both of the SMSCs have their own Kannel (Bearerbox, SMSBox, SQLBox) and one of the SMSCs is set to send messages, the other is set to receive them. The receive box has the following recv_smsbox.conf (sms-service etc); # SENDSMS USER CONFIGURATIONS # group = sendsms-user username = wim password = wim # SMS-SERVICE # group
SMPP TLV - how to combine them ? (IPX)
Hello, what I have unederstood is that TLVs allow to catch additional meta-data from a SMSC when encapsulated into a SMPP request. Configure them is quite easy: contact your smsc and ask for docs, they will basically tell what additional meta-data they add that you can use and they will also tell the lenght/type for each TLV, so it's a matter or adding it to my conf file in kannel. Now my issue comes when I need to make use of those TLVs. My SMSC does not use a unique id for each SMS (field-timestamp in the mysql DLR storage), so kannel gets crazy when receiving DLRs. For instance, the SMSC sets the field-timestamp with a friendly 0 or 1, so when the DLRs comes back, there is no guarantee that the correct SMS gets the delivered status because kannel makes use of that timestamp to map the DLR with the SMS (and yes, also the recipient number if remember correctly). In my case, my SMSC inserts its unique ID into the meta-data, so I'm wondering how to tell Kannel to use that info stored in the meta-data as the sms unique id. Any suggestion ? Thanks to all! -- Julien Buratto Linkas SRL Tel. 0230321419 PS: Some time ago, another guy went into this and made a patch for its 1.4.3 version. That works very well. Alejandro suggested to use TLVs but I suppose that guy made its own way without TLVs. I would be very interested to see how to solve that issue with TLVs instead of patching.
Re: Unicode messages in Kannel with SMPP
Check http://www.linkas.it/docs/kannel Julien 2009/6/17 Benaiad bena...@gmail.com: I think the Unicode must be supported at: 1- your programs. 2- database fields. 3- kannel. 4- for Linux, I don't think it's important Regards. Benaiad On Wed, Jun 17, 2009 at 10:16 AM, TheBlueSky eamh...@gmail.com wrote: Hello, Thanks for the info. One more question if I may and maybe it's irrelative but as you have tested it I appreciate if you can answer me. For the Unicode messages, do I have to have support for the language in the OS (e.g. Arabic support on Linux)? Although it's isn't a complicated thing to have, but I'm asking just to have information about it. Thanks. From: Benaiad Sent: Wednesday, June 17, 2009 11:58 AM To: TheBlueSky Cc: users@kannel.org Subject: Re: Unicode messages in Kannel with SMPP Hello, 1- yes ( I've tested the arabic, the sms limited to 70 char or less, it depends ). 2- yes, kannel will take care of this ( divide MT sms and concatenate MO sms ). Regards. Benaiad 2009/6/17 TheBlueSky eamh...@gmail.com Hello everyone, I'm using the latest version of Kannel (as for now 1.4.3) and want to use it to connect to SMSC over SMPP. I don't have SMPP for now so I appreciate if someone can answer my following questions: 1. Does Kannel support Unicode SMS over SMPP (Arabic, Chinese ... etc. SMS)? 2. If the answer of the first question is yes, does Kannel support Unicode multi-part SMS (divide and un-divide long SMS) Thanks -- Julien Buratto
Re: problem and solution sending concatenated messages by inserting into send_sms (sqlbox, smpp)
Hi Stefan, very cool, thanks for the hint. To which coding value have you set the sms in the send_sms table ? text sms should be most of the time as coding=0, while binary sms (like concatenated) should go as coding=1 Which one were you using ? I suppose coding=0 (as it could be by default using the smsbox) Julien 2009/6/16 Stefan Mada m...@beesoft.sk: Hi all when I tried to send long message (over 160 chars) by inserting into send_sms table, message was corrupted or wasn't delivered. The same message sent by http call was delivered. Problem was in coding value. While I send message by http request without coding value set, kannel set it by default to 0. The same data inserted into send_sms, without coding value set (no default value for coding field in table set, so null value set), after insert was message processed by sqlbox/kannel and coding was set to 4 (value from log files). So solution is to set default value in send_sms table or while inserting into send_sms table fill coding field too. May be it will help to someone. Sincerely, Stefan -- Julien Buratto
Re: Using kannel with GSM Modem pool
Hi Dennis, as RJ45 is a standard network cable, you should check what type of protocol the GSM pool has enabled. For example, if the GSM pool has a HTTP microserver to receive requests, you can use kannel http SMSC to transmit requests to it. Julien 2009/6/15 Dennis Low Weng Kin powered182...@live.com: Hi, I read about a piece of hardware called the GSM Modem pool. It is consists of 8 GSM module combined together into a single casing and it is connected to the PC through a RJ45 cable. I am planning to buy the GSM Modem pool but I am not sure whether kannel can support it. Therefore, my question is: Does anybody out there have experience with Kannel and a GSM Modem pool? Is it possible? If possible, how do I edit the configuration file to use kannel with it? Thanks in advance. Regards, Dennis Low What can you do with the new Windows Live? Find out -- Julien Buratto
Re: Send Long SMS with UTF-16BE
Omar, could you be more precise ? What do you need to do precisely ? Julien 2009/6/13 Omar Hussien Al-Amoodi oalamo...@elm.com.sa: I would like to know what are the best ways to send long UTF-16BE encoded messages using send-sms user in Kannel, Can anyone please the best combination ot configuration for Kannel? Regards, Omar Al-Amoodi | Solutions Developer | Al-Elm Information Security | | * oalamo...@elm.com.sa | DISCLAIMER: The information in this email is confidential. The contents may not be disclosed or used by anyone other than the addressee. If you are not the intended recipient(s), any use, disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you have received this communication in error please notify us by email then delete the email and all attachments and any copies thereof -- Julien Buratto
Re: OMA-Settings using sendota
Hi, if you check the previous posts, you will notice that 1.4.3 unfortunately had something broken in order to sendota. You will need to use cvs or older 1.4.1 for it. Julien 2009/6/12 Benaiad bena...@gmail.com: Hi, I am sending SyncML settings using sendota cgi, But on my handset I receive message format no supported. My Sending URL: == http://127.0.0.1/cgi-bin/sendota?username=mepassword=itismeagainto=$msisdntext=$omadoctype=settingspin=1234sec=userpin My OMA Prov Doc: == wap-provisioningdoc characteristic type=BOOTSTRAP parm name=NAME value=MySync/ /characteristic characteristic type=APPLICATION parm name=APPID value=w5/ parm name=TO-NAPID value=INTERNET/ parm name=NAME value=MySync/ parm name=ADDR value=http://127.0.0.1:8080/funambol/ds/ characteristic type=RESOURCE parm name=URI value=card/ parm name=NAME value=Contacts DB/ parm name=AACCEPT value=text/x-vcard/ /characteristic characteristic type=APPAUTH parm name=AAUTHNAME value=yourname/ parm name=AAUTHSECRET value=itisnome/ /characteristic /characteristic /wap-provisioningdoc - Note: I've tested this prov doc with NowSMS and it's working. From smsbox logs: = 2009-06-12 10:37:25 [9674] [3] INFO: smsbox: Got HTTP request /cgi-bin/sendota from 127.0.0.1 2009-06-12 10:37:25 [9674] [3] INFO: sendsms used by user7153 2009-06-12 10:37:25 [9674] [3] WARNING: OTA compiler: Unknown attribute 'type' in OTA source, with value 'BOOTSTRAP'. 2009-06-12 10:37:25 [9674] [3] WARNING: OTA compiler: Unknown attribute 'type' in OTA source, with value 'APPLICATION'. 2009-06-12 10:37:25 [9674] [3] WARNING: OTA compiler: Unknown attribute 'type' in OTA source, with value 'RESOURCE'. 2009-06-12 10:37:25 [9674] [3] WARNING: OTA compiler: Unknown attribute 'type' in OTA source, with value 'APPAUTH'. 2009-06-12 10:37:25 [9674] [3] INFO: /cgi-bin/sendota: XML request for target +676 2009-06-12 10:37:25 [9674] [3] INFO: /cgi-bin/sendota default +676 And I have tested setting url parameter type=oma-settings also type=syncsettings with no luck. smsbox logs when using type=oma-settings (no message received on my handset here) : 2009-06-12 10:36:26 [9674] [3] INFO: smsbox: Got HTTP request /cgi-bin/sendota from 127.0.0.1 2009-06-12 10:36:26 [9674] [3] INFO: sendsms used by user7153 2009-06-12 10:36:26 [9674] [3] WARNING: OTA compiler: Unknown attribute 'type' in OTA source, with value 'BOOTSTRAP'. 2009-06-12 10:36:26 [9674] [3] WARNING: OTA compiler: Unknown attribute 'type' in OTA source, with value 'APPLICATION'. 2009-06-12 10:36:26 [9674] [3] WARNING: OTA compiler: Unknown attribute 'type' in OTA source, with value 'RESOURCE'. 2009-06-12 10:36:26 [9674] [3] WARNING: OTA compiler: Unknown attribute 'type' in OTA source, with value 'APPAUTH'. 2009-06-12 10:36:26 [9674] [3] WARNING: OMA ProvCont: No SSL Support, 'oma-settings' not supported! == 2009-06-12 10:36:26 [9674] [3] INFO: /cgi-bin/sendota: XML request for target +676 2009-06-12 10:36:26 [9674] [3] INFO: /cgi-bin/sendota default +676 TIA Benaiad -- Julien Buratto
Re: sendota problems - SOLVED
Patch from Nikos has been committed to CVS. 2009/6/8 Nikos Balkanas nbalka...@gmail.com: No, you are not complaining. As usual you make unsubstantiated claims while being clueless. Have you bothered to check cvs to substantiate your words? I didn't think so. Well, don't loose your sleep over it. What you say hasn't happenned. - Original Message - From: Julien Buratto julien.bura...@gmail.com To: Nikos Balkanas nbalka...@gmail.com Cc: tom...@megalogika.lt; users@kannel.org; Pai Peng sipai...@gmail.com Sent: Monday, June 08, 2009 7:59 PM Subject: Re: sendota problems Hi Nikos, I'm not complaining, I'm just concerned how this was dropped and where :-) Julien 2009/6/8 Nikos Balkanas nbalka...@gmail.com: Interesting... Although it has been stressed to you, by 2 core developers (well actually 1.5 ;-) that kannel never supported wap-provisioningdoc, you skip thread, and restate that it is kannel who has dropped this feature. When in fact, it is yourself who has been feeding kannel with a different xml all these years and suddenly decide to change. Kannel supports legacy devices, and doesn't drop proven features no matter how old. New devices, however, like wap 2.0 are an issue. I am happy that you can work with characteristic-list. BR, Nikos - Original Message - From: Julien Buratto julien.bura...@gmail.com To: Nikos Balkanas nbalka...@gmail.com Cc: tom...@megalogika.lt; users@kannel.org; Pai Peng sipai...@gmail.com Sent: Monday, June 08, 2009 1:54 PM Subject: Re: sendota problems I think I will have no choice and I will try to convert it to characteristic-list .. Julien 2009/6/8 Julien Buratto julien.bura...@gmail.com: Hi Nikos, I've been happily using wap-provisioningdoc for a long time on 1.4.1... quite strange the implementation has been removed from 1.4.3.. Julien 2009/6/8 Nikos Balkanas nbalka...@gmail.com: Oops! Forgot to ask. Can't you use a characteristic-list xml document to do your job? Kannel fully supports those! BR, Nikos - Original Message - From: Nikos Balkanas nbalka...@gmail.com To: Julien Buratto julien.bura...@gmail.com Cc: tom...@megalogika.lt; users@kannel.org; Pai Peng sipai...@gmail.com Sent: Monday, June 08, 2009 6:11 AM Subject: Re: sendota problems Hi Julien, I looked it up and it is not trivial. As it stands kannel supports only the Nokia OTA characteristic-list specs. It doesn't support the wap-provisioningdoc specs. As such a complete reworking of the ota-compiler would be needed to accomodate it. Since I am lacking ota development/testing environment, and is only of marginal interest to me, I am sorry but I cannot pursue it further. What I can do is, to make a patch, so that kannel prints an error when it detects such a document and drops it. BR, Nikos - Original Message - From: Nikos Balkanas nbalka...@gmail.com To: Julien Buratto julien.bura...@gmail.com Cc: tom...@megalogika.lt; users@kannel.org Sent: Saturday, June 06, 2009 9:19 AM Subject: Re: sendota problems Not, unfortunately. I was going crazy all this time at work, but I just finished. I will look at it over this weekend. BR, Nikos - Original Message - From: Julien Buratto julien.bura...@gmail.com To: Nikos Balkanas nbalka...@gmail.com Cc: tom...@megalogika.lt; users@kannel.org Sent: Thursday, May 28, 2009 3:16 PM Subject: Re: sendota problems Hi Nikos, where you able to fix the issue ? 2009/3/17 Nikos Balkanas nbalka...@gmail.com: Hi, There seems to be an incombatibility between kannel's wbxml and Nokia's. I intend to fix it, but in a month or so. In the meantime you might want to compile the message manually, as described by Pai Peng. BR, Nikos - Original Message - From: Tomas Verbaitis tom...@megalogika.lt To: users@kannel.org Sent: Monday, March 16, 2009 1:24 PM Subject: sendota problems Hello, I want to configure synchronization for Nokia 6070 mobile phone. My program generates this XML provisioning document: ?xml version=1.0? !DOCTYPE wap-provisioningdoc PUBLIC -//WAPFORUM//DTD PROV 1.0//EN http://www.wapforum.org/DTD/prov.dtd; wap-provisioningdoc characteristic type=BOOTSTRAP parm name=NAME value=SKLADDEVEL/ /characteristic characteristic type=APPLICATION parm name=APPID value=w5/ parm name=TO-NAPID value=INTERNET / parm name=NAME value=SKLADDEVEL/ parm name=ADDR value=http://megalogika.stp.lt/funambol/ds/ characteristic type=RESOURCE parm name=URI value=card/ parm name=NAME value=Contacts DB/ parm name=AACCEPT value=text/x-vcard/ /characteristic characteristic type=RESOURCE parm name=URI value=cal/ parm name=NAME value=Calendar/ parm name=AACCEPT value=text/x-vcalendar/ /characteristic characteristic type=RESOURCE parm name=URI value=notes/ parm name=NAME value=Notes/ parm name=AACCEPT value=text/plain/ /characteristic characteristic type=APPAUTH parm name=AAUTHNAME value=funUsrVe/ parm name
Re: sendota problems
Hi Nikos, I've been happily using wap-provisioningdoc for a long time on 1.4.1... quite strange the implementation has been removed from 1.4.3.. Julien 2009/6/8 Nikos Balkanas nbalka...@gmail.com: Oops! Forgot to ask. Can't you use a characteristic-list xml document to do your job? Kannel fully supports those! BR, Nikos - Original Message - From: Nikos Balkanas nbalka...@gmail.com To: Julien Buratto julien.bura...@gmail.com Cc: tom...@megalogika.lt; users@kannel.org; Pai Peng sipai...@gmail.com Sent: Monday, June 08, 2009 6:11 AM Subject: Re: sendota problems Hi Julien, I looked it up and it is not trivial. As it stands kannel supports only the Nokia OTA characteristic-list specs. It doesn't support the wap-provisioningdoc specs. As such a complete reworking of the ota-compiler would be needed to accomodate it. Since I am lacking ota development/testing environment, and is only of marginal interest to me, I am sorry but I cannot pursue it further. What I can do is, to make a patch, so that kannel prints an error when it detects such a document and drops it. BR, Nikos - Original Message - From: Nikos Balkanas nbalka...@gmail.com To: Julien Buratto julien.bura...@gmail.com Cc: tom...@megalogika.lt; users@kannel.org Sent: Saturday, June 06, 2009 9:19 AM Subject: Re: sendota problems Not, unfortunately. I was going crazy all this time at work, but I just finished. I will look at it over this weekend. BR, Nikos - Original Message - From: Julien Buratto julien.bura...@gmail.com To: Nikos Balkanas nbalka...@gmail.com Cc: tom...@megalogika.lt; users@kannel.org Sent: Thursday, May 28, 2009 3:16 PM Subject: Re: sendota problems Hi Nikos, where you able to fix the issue ? 2009/3/17 Nikos Balkanas nbalka...@gmail.com: Hi, There seems to be an incombatibility between kannel's wbxml and Nokia's. I intend to fix it, but in a month or so. In the meantime you might want to compile the message manually, as described by Pai Peng. BR, Nikos - Original Message - From: Tomas Verbaitis tom...@megalogika.lt To: users@kannel.org Sent: Monday, March 16, 2009 1:24 PM Subject: sendota problems Hello, I want to configure synchronization for Nokia 6070 mobile phone. My program generates this XML provisioning document: ?xml version=1.0? !DOCTYPE wap-provisioningdoc PUBLIC -//WAPFORUM//DTD PROV 1.0//EN http://www.wapforum.org/DTD/prov.dtd; wap-provisioningdoc characteristic type=BOOTSTRAP parm name=NAME value=SKLADDEVEL/ /characteristic characteristic type=APPLICATION parm name=APPID value=w5/ parm name=TO-NAPID value=INTERNET / parm name=NAME value=SKLADDEVEL/ parm name=ADDR value=http://megalogika.stp.lt/funambol/ds/ characteristic type=RESOURCE parm name=URI value=card/ parm name=NAME value=Contacts DB/ parm name=AACCEPT value=text/x-vcard/ /characteristic characteristic type=RESOURCE parm name=URI value=cal/ parm name=NAME value=Calendar/ parm name=AACCEPT value=text/x-vcalendar/ /characteristic characteristic type=RESOURCE parm name=URI value=notes/ parm name=NAME value=Notes/ parm name=AACCEPT value=text/plain/ /characteristic characteristic type=APPAUTH parm name=AAUTHNAME value=funUsrVe/ parm name=AAUTHSECRET value=funPassVe/ /characteristic /characteristic /wap-provisioningdoc When i send it via Kannel's /sendota, via this request: /cgi-bin/sendota?password=##username=##type=oma-settingssec=USERPINpin=1234to=%2B37069953201text=%3C%3Fxml+version%3D%221.0%22%3F%3E%0A%3C%21DOCTYPE+wap-provisioningdoc+PUBLIC+%22-%2F%2FWAPFORUM%2F%2FDTD+PROV+1.0%2F%2FEN%22%0A%22http%3A%2F%2Fwww.wapforum.org%2FDTD%2Fprov.dtd%22%3E%0A%3Cwap-provisioningdoc%3E%0A%3Ccharacteristic+type%3D%22BOOTSTRAP%22%3E%0A%3Cparm+name%3D%22NAME%22+value%3D%22SKLADDEVEL%22%2F%3E%0A%3C%2Fcharacteristic%3E%0A%3Ccharacteristic+type%3D%22APPLICATION%22%3E%0A%3Cparm+name%3D%22APPID%22+value%3D%22w5%22%2F%3E%0A%3Cparm+name%3D%22TO-NAPID%22+value%3D%22INTERNET%22+%2F%3E%0A%3Cparm+name%3D%22NAME%22+value%3D%22SKLADDEVEL%22%2F%3E%0A%3Cparm+name%3D%22ADDR%22+value%3D%22http%3A%2F%2Fmegalogika.stp.lt%2Ffunambol%2Fds%22%2F%3E%0A%3Ccharacteristic+type%3D%22RESOURCE%22%3E%0A%3Cparm+name%3D%22URI%22+value%3D%22card%22%2F%3E%0A%3Cparm+name%3D%22NAME%22+value%3D%22Contacts+DB%22%2F%3E%0A%3Cparm+name%3D%22AACCEPT%22+value%3D%22text%2Fx-vcard%22%2F %3E%0A%3C%2Fcharacteristic%3E%0A%3Ccharacteristic+type%3D%22RESOURCE%22%3E%0A%3Cparm+name%3D%22URI%22+value%3D%22cal%22%2F%3E%0A%3Cparm+name%3D%22NAME%22+value%3D%22Calendar%22%2F%3E%0A%3Cparm+name%3D%22AACCEPT%22+value%3D%22text%2Fx-vcalendar%22%2F%3E%0A%3C%2Fcharacteristic%3E%0A%3Ccharacteristic+type%3D%22RESOURCE%22%3E%0A%3Cparm+name%3D%22URI%22+value%3D%22notes%22%2F%3E%0A%3Cparm+name%3D%22NAME%22+value%3D%22Notes%22%2F%3E%0A%3Cparm+name%3D%22AACCEPT%22+value%3D%22text%2Fplain%22%2F%3E%0A%3C%2Fcharacteristic%3E%0A%3Ccharacteristic+type%3D%22APPAUTH%22%3E%0A%3Cparm+name%3D
WAS sendota not using wbxml but plain xml from devel list
Hi, I'm moving the topic on the user list as per request. Based on the fact that I have both installed 1.4.1 and 1.4.3 compiled (with the same options) on the same machine and running on the same machine, and I'm using the same HTML form to post data to 1.4.1 and 1.4.3, I can firmly exclude that I'm sending different contents during the tests I'm performing. Both instances are running on the same machine with identical configurations (a part from some port numbering change). I understand then that the wap-provisioningdoc is not supported in any version of kannel, but at least it was working on 1.4.1 and now it is not. This is the only possible response possible from my understanding. As the 1.4.1 and 1.4.3 instances are running at same time on different ports, I've just changed the URL port from: myhost:13005 to myhost:15005 in order to perform the rest e re-submitted the same content. KANNEL 1.4.1 - 2009-06-08 12:43:30 [17186] [3] INFO: smsbox: Got HTTP request /cgi-bin/sendota from 10.100.10.51 2009-06-08 12:43:30 [17186] [3] INFO: sendsms used by fake 2009-06-08 12:43:30 [17186] [3] DEBUG: dlr-url found 2009-06-08 12:43:30 [17186] [3] DEBUG: dlr-mask found 2009-06-08 12:43:30 [17186] [3] DEBUG: OTA service with XML document 2009-06-08 12:43:30 [17186] [3] DEBUG: Octet string at 0x8b8b2a0: 2009-06-08 12:43:30 [17186] [3] DEBUG: len: 268 2009-06-08 12:43:30 [17186] [3] DEBUG: size: 1024 2009-06-08 12:43:30 [17186] [3] DEBUG: immutable: 0 2009-06-08 12:43:30 [17186] [3] DEBUG: data: 01 06 2f 1f 2d b6 91 81 92 33 34 33 46 38 45 35 ../.-343F8E5 2009-06-08 12:43:30 [17186] [3] DEBUG: data: 38 35 41 39 34 31 45 32 35 31 43 32 41 41 35 38 85A941E251C2AA58 2009-06-08 12:43:30 [17186] [3] DEBUG: data: 38 30 43 41 44 39 30 41 33 41 32 30 44 39 39 42 80CAD90A3A20D99B 2009-06-08 12:43:30 [17186] [3] DEBUG: data: 38 00 03 0b 6a 00 c5 46 01 c6 56 01 87 07 06 03 8...j..F..V. 2009-06-08 12:43:30 [17186] [3] DEBUG: data: 53 79 6e 63 50 72 6f 66 69 6c 65 00 01 01 c6 00 SyncProfile. 2009-06-08 12:43:30 [17186] [3] DEBUG: data: 01 55 01 87 36 06 03 77 35 00 01 87 00 00 07 06 .U..6..w5... 2009-06-08 12:43:30 [17186] [3] DEBUG: data: 03 53 79 6e 63 50 72 6f 66 69 6c 65 00 01 87 22 .SyncProfile... 2009-06-08 12:43:30 [17186] [3] DEBUG: data: 06 03 49 4e 54 45 52 4e 45 54 00 01 87 00 01 34 ..INTERNET.4 2009-06-08 12:43:30 [17186] [3] DEBUG: data: 06 03 68 74 74 70 3a 2f 2f 64 6f 6d 61 69 6e 2e ..http://domain. 2009-06-08 12:43:30 [17186] [3] DEBUG: data: 63 6f 6d 3a 38 30 2f 73 79 6e 63 00 01 87 05 03 com:80/sync. 2009-06-08 12:43:30 [17186] [3] DEBUG: data: 50 4f 52 54 00 06 03 38 30 00 01 c6 59 01 87 3a PORT...80...Y..: 2009-06-08 12:43:30 [17186] [3] DEBUG: data: 06 03 63 61 72 64 00 01 87 00 00 07 06 03 43 6f ..cardCo 2009-06-08 12:43:30 [17186] [3] DEBUG: data: 6e 74 61 63 74 73 00 01 87 00 01 2e 06 03 74 65 ntactste 2009-06-08 12:43:30 [17186] [3] DEBUG: data: 78 74 2f 78 2d 76 63 61 72 64 2c 74 65 78 74 2f xt/x-vcard,text/ 2009-06-08 12:43:30 [17186] [3] DEBUG: data: 76 63 61 72 64 00 01 01 c6 57 01 87 31 06 03 61 vcardW..1..a 2009-06-08 12:43:30 [17186] [3] DEBUG: data: 75 73 65 72 6e 61 6d 65 00 01 87 32 06 03 61 70 username...2..ap 2009-06-08 12:43:30 [17186] [3] DEBUG: data: 61 73 73 77 6f 72 64 00 01 01 01 01 assword. 2009-06-08 12:43:30 [17186] [3] DEBUG: Octet string dump ends. 2009-06-08 12:43:30 [17186] [3] INFO: /cgi-bin/sendota: XML request for target 012345678 KANNEL 1.4.3 - 2009-06-08 12:40:42 [5987] [3] INFO: smsbox: Got HTTP request /cgi-bin/sendota from 10.100.10.51 2009-06-08 12:40:42 [5987] [3] INFO: sendsms used by fake 2009-06-08 12:40:42 [5987] [3] DEBUG: OTA service with XML document 2009-06-08 12:40:42 [5987] [3] DEBUG: Octet string at 0x83a6d88: 2009-06-08 12:40:42 [5987] [3] DEBUG: len: 385 2009-06-08 12:40:42 [5987] [3] DEBUG: size: 1024 2009-06-08 12:40:42 [5987] [3] DEBUG: immutable: 0 2009-06-08 12:40:42 [5987] [3] DEBUG: data: 01 06 2f 1f 2d b6 91 81 92 36 35 43 45 43 30 38 ../.-65CEC08 2009-06-08 12:40:42 [5987] [3] DEBUG: data: 44 42 38 38 46 44 37 31 46 32 32 44 37 31 43 30 DB88FD71F22D71C0 2009-06-08 12:40:42 [5987] [3] DEBUG: data: 33 31 38 45 44 34 42 45 41 36 34 31 45 34 32 35 318ED4BEA641E425 2009-06-08 12:40:42 [5987] [3] DEBUG: data: 44 00 03 0b 6a 00 c5 45 03 31 2e 30 00 01 c6 50 D...j..E.1.0...P 2009-06-08 12:40:42 [5987] [3] DEBUG: data: 03 42 4f 4f 54 53 54 52 41 50 00 01 87 05 03 4e .BOOTSTRAP.N 2009-06-08 12:40:42 [5987] [3] DEBUG: data: 41 4d 45 00 06 03 53 79 6e 63 50 72 6f 66 69 6c AME...SyncProfil 2009-06-08 12:40:42 [5987] [3] DEBUG: data: 65 00 01 01 c6 50 03 41 50 50 4c 49 43 41 54 49 eP.APPLICATI 2009-06-08 12:40:42 [5987] [3] DEBUG: data: 4f 4e 00 01 87 05 03 41 50 50 49 44 00 06 03 77 ON.APPID...w 2009-06-08 12:40:42 [5987] [3]
Re: sendota problems
I think I will have no choice and I will try to convert it to characteristic-list .. Julien 2009/6/8 Julien Buratto julien.bura...@gmail.com: Hi Nikos, I've been happily using wap-provisioningdoc for a long time on 1.4.1... quite strange the implementation has been removed from 1.4.3.. Julien 2009/6/8 Nikos Balkanas nbalka...@gmail.com: Oops! Forgot to ask. Can't you use a characteristic-list xml document to do your job? Kannel fully supports those! BR, Nikos - Original Message - From: Nikos Balkanas nbalka...@gmail.com To: Julien Buratto julien.bura...@gmail.com Cc: tom...@megalogika.lt; users@kannel.org; Pai Peng sipai...@gmail.com Sent: Monday, June 08, 2009 6:11 AM Subject: Re: sendota problems Hi Julien, I looked it up and it is not trivial. As it stands kannel supports only the Nokia OTA characteristic-list specs. It doesn't support the wap-provisioningdoc specs. As such a complete reworking of the ota-compiler would be needed to accomodate it. Since I am lacking ota development/testing environment, and is only of marginal interest to me, I am sorry but I cannot pursue it further. What I can do is, to make a patch, so that kannel prints an error when it detects such a document and drops it. BR, Nikos - Original Message - From: Nikos Balkanas nbalka...@gmail.com To: Julien Buratto julien.bura...@gmail.com Cc: tom...@megalogika.lt; users@kannel.org Sent: Saturday, June 06, 2009 9:19 AM Subject: Re: sendota problems Not, unfortunately. I was going crazy all this time at work, but I just finished. I will look at it over this weekend. BR, Nikos - Original Message - From: Julien Buratto julien.bura...@gmail.com To: Nikos Balkanas nbalka...@gmail.com Cc: tom...@megalogika.lt; users@kannel.org Sent: Thursday, May 28, 2009 3:16 PM Subject: Re: sendota problems Hi Nikos, where you able to fix the issue ? 2009/3/17 Nikos Balkanas nbalka...@gmail.com: Hi, There seems to be an incombatibility between kannel's wbxml and Nokia's. I intend to fix it, but in a month or so. In the meantime you might want to compile the message manually, as described by Pai Peng. BR, Nikos - Original Message - From: Tomas Verbaitis tom...@megalogika.lt To: users@kannel.org Sent: Monday, March 16, 2009 1:24 PM Subject: sendota problems Hello, I want to configure synchronization for Nokia 6070 mobile phone. My program generates this XML provisioning document: ?xml version=1.0? !DOCTYPE wap-provisioningdoc PUBLIC -//WAPFORUM//DTD PROV 1.0//EN http://www.wapforum.org/DTD/prov.dtd; wap-provisioningdoc characteristic type=BOOTSTRAP parm name=NAME value=SKLADDEVEL/ /characteristic characteristic type=APPLICATION parm name=APPID value=w5/ parm name=TO-NAPID value=INTERNET / parm name=NAME value=SKLADDEVEL/ parm name=ADDR value=http://megalogika.stp.lt/funambol/ds/ characteristic type=RESOURCE parm name=URI value=card/ parm name=NAME value=Contacts DB/ parm name=AACCEPT value=text/x-vcard/ /characteristic characteristic type=RESOURCE parm name=URI value=cal/ parm name=NAME value=Calendar/ parm name=AACCEPT value=text/x-vcalendar/ /characteristic characteristic type=RESOURCE parm name=URI value=notes/ parm name=NAME value=Notes/ parm name=AACCEPT value=text/plain/ /characteristic characteristic type=APPAUTH parm name=AAUTHNAME value=funUsrVe/ parm name=AAUTHSECRET value=funPassVe/ /characteristic /characteristic /wap-provisioningdoc When i send it via Kannel's /sendota, via this request: /cgi-bin/sendota?password=##username=##type=oma-settingssec=USERPINpin=1234to=%2B37069953201text=%3C%3Fxml+version%3D%221.0%22%3F%3E%0A%3C%21DOCTYPE+wap-provisioningdoc+PUBLIC+%22-%2F%2FWAPFORUM%2F%2FDTD+PROV+1.0%2F%2FEN%22%0A%22http%3A%2F%2Fwww.wapforum.org%2FDTD%2Fprov.dtd%22%3E%0A%3Cwap-provisioningdoc%3E%0A%3Ccharacteristic+type%3D%22BOOTSTRAP%22%3E%0A%3Cparm+name%3D%22NAME%22+value%3D%22SKLADDEVEL%22%2F%3E%0A%3C%2Fcharacteristic%3E%0A%3Ccharacteristic+type%3D%22APPLICATION%22%3E%0A%3Cparm+name%3D%22APPID%22+value%3D%22w5%22%2F%3E%0A%3Cparm+name%3D%22TO-NAPID%22+value%3D%22INTERNET%22+%2F%3E%0A%3Cparm+name%3D%22NAME%22+value%3D%22SKLADDEVEL%22%2F%3E%0A%3Cparm+name%3D%22ADDR%22+value%3D%22http%3A%2F%2Fmegalogika.stp.lt%2Ffunambol%2Fds%22%2F%3E%0A%3Ccharacteristic+type%3D%22RESOURCE%22%3E%0A%3Cparm+name%3D%22URI%22+value%3D%22card%22%2F%3E%0A%3Cparm+name%3D%22NAME%22+value%3D%22Contacts+DB%22%2F%3E%0A%3Cparm+name%3D%22AACCEPT%22+value%3D%22text%2Fx-vcard%22%2F %3E%0A%3C%2Fcharacteristic%3E%0A%3Ccharacteristic+type%3D%22RESOURCE%22%3E%0A%3Cparm+name%3D%22URI%22+value%3D%22cal%22%2F%3E%0A%3Cparm+name%3D%22NAME%22+value%3D%22Calendar%22%2F%3E%0A%3Cparm+name%3D%22AACCEPT%22+value%3D%22text%2Fx-vcalendar%22%2F%3E%0A%3C%2Fcharacteristic%3E%0A%3Ccharacteristic+type%3D%22RESOURCE%22%3E%0A%3Cparm+name%3D%22URI%22+value%3D%22notes%22%2F%3E%0A%3Cparm+name%3D%22NAME%22+value%3D%22Notes%22%2F%3E%0A%3Cparm
Re: SQLBox with utf8 chars
Hi TIA, I think that somehow you will need to change the code, however there is a tutorial on stored procedures on mysql here: http://www.brainbell.com/tutorials/MySQL/Using_Stored_Procedures.htm I woudl prefer to see the code as a patch in kannel if required to work rather than rely on a specific sql implementation of stored procedures.. Julien 2009/6/8 Benaiad bena...@gmail.com: Thank you Nikos, But how can I configure kannel to call a stored procedure in mysql, I think this will help non programmers users. TIA 2009/6/8 Nikos Balkanas nbalka...@gmail.com You don't need smsbox to push SMS, if you have sqlbox. But you need it for incoming SMS and sms services. BR, Nikos - Original Message - From: Benaiad To: users Sent: Saturday, June 06, 2009 10:05 PM Subject: Re: SQLBox with utf8 chars Correction: I've successfully implemented this scenario, But I need to know if I can use this without the need of smsbox. Thanks! On Sat, Jun 6, 2009 at 9:03 PM, Benaiad bena...@gmail.com wrote: I've found this: 1- to convert from HEX to utf8 using mysql: SELECT CONVERT(UNHEX(msgdata) USING ucs2 )Β FROM sent_smsΒ WHERE sql_id = 14 AND coding = 2 2- to convert from utf8 to HEX using mysql: SELECT HEX(CONVERT(myutf8string USING ucs2)Β ) Now I want to use bearerbox with sqlbox only: Every MO message will be saved in sent_sms table by sqlbox. And every INSERT into sent_sms table will call a trigger, the trigger will analyze the MO message and insert it's response into the send_sms table. I've successfully implemented this scenario, But I need to know if I can use this with the need of smsbox. Thanks guys for your kind response and special thanks to Alejandro Guerrieri for his great support and concern. Best Regards. Monim Benaiad -- Julien Buratto
Re: sendota problems
Hi Nikos, I'm not complaining, I'm just concerned how this was dropped and where :-) Julien 2009/6/8 Nikos Balkanas nbalka...@gmail.com: Interesting... Although it has been stressed to you, by 2 core developers (well actually 1.5 ;-) that kannel never supported wap-provisioningdoc, you skip thread, and restate that it is kannel who has dropped this feature. When in fact, it is yourself who has been feeding kannel with a different xml all these years and suddenly decide to change. Kannel supports legacy devices, and doesn't drop proven features no matter how old. New devices, however, like wap 2.0 are an issue. I am happy that you can work with characteristic-list. BR, Nikos - Original Message - From: Julien Buratto julien.bura...@gmail.com To: Nikos Balkanas nbalka...@gmail.com Cc: tom...@megalogika.lt; users@kannel.org; Pai Peng sipai...@gmail.com Sent: Monday, June 08, 2009 1:54 PM Subject: Re: sendota problems I think I will have no choice and I will try to convert it to characteristic-list .. Julien 2009/6/8 Julien Buratto julien.bura...@gmail.com: Hi Nikos, I've been happily using wap-provisioningdoc for a long time on 1.4.1... quite strange the implementation has been removed from 1.4.3.. Julien 2009/6/8 Nikos Balkanas nbalka...@gmail.com: Oops! Forgot to ask. Can't you use a characteristic-list xml document to do your job? Kannel fully supports those! BR, Nikos - Original Message - From: Nikos Balkanas nbalka...@gmail.com To: Julien Buratto julien.bura...@gmail.com Cc: tom...@megalogika.lt; users@kannel.org; Pai Peng sipai...@gmail.com Sent: Monday, June 08, 2009 6:11 AM Subject: Re: sendota problems Hi Julien, I looked it up and it is not trivial. As it stands kannel supports only the Nokia OTA characteristic-list specs. It doesn't support the wap-provisioningdoc specs. As such a complete reworking of the ota-compiler would be needed to accomodate it. Since I am lacking ota development/testing environment, and is only of marginal interest to me, I am sorry but I cannot pursue it further. What I can do is, to make a patch, so that kannel prints an error when it detects such a document and drops it. BR, Nikos - Original Message - From: Nikos Balkanas nbalka...@gmail.com To: Julien Buratto julien.bura...@gmail.com Cc: tom...@megalogika.lt; users@kannel.org Sent: Saturday, June 06, 2009 9:19 AM Subject: Re: sendota problems Not, unfortunately. I was going crazy all this time at work, but I just finished. I will look at it over this weekend. BR, Nikos - Original Message - From: Julien Buratto julien.bura...@gmail.com To: Nikos Balkanas nbalka...@gmail.com Cc: tom...@megalogika.lt; users@kannel.org Sent: Thursday, May 28, 2009 3:16 PM Subject: Re: sendota problems Hi Nikos, where you able to fix the issue ? 2009/3/17 Nikos Balkanas nbalka...@gmail.com: Hi, There seems to be an incombatibility between kannel's wbxml and Nokia's. I intend to fix it, but in a month or so. In the meantime you might want to compile the message manually, as described by Pai Peng. BR, Nikos - Original Message - From: Tomas Verbaitis tom...@megalogika.lt To: users@kannel.org Sent: Monday, March 16, 2009 1:24 PM Subject: sendota problems Hello, I want to configure synchronization for Nokia 6070 mobile phone. My program generates this XML provisioning document: ?xml version=1.0? !DOCTYPE wap-provisioningdoc PUBLIC -//WAPFORUM//DTD PROV 1.0//EN http://www.wapforum.org/DTD/prov.dtd; wap-provisioningdoc characteristic type=BOOTSTRAP parm name=NAME value=SKLADDEVEL/ /characteristic characteristic type=APPLICATION parm name=APPID value=w5/ parm name=TO-NAPID value=INTERNET / parm name=NAME value=SKLADDEVEL/ parm name=ADDR value=http://megalogika.stp.lt/funambol/ds/ characteristic type=RESOURCE parm name=URI value=card/ parm name=NAME value=Contacts DB/ parm name=AACCEPT value=text/x-vcard/ /characteristic characteristic type=RESOURCE parm name=URI value=cal/ parm name=NAME value=Calendar/ parm name=AACCEPT value=text/x-vcalendar/ /characteristic characteristic type=RESOURCE parm name=URI value=notes/ parm name=NAME value=Notes/ parm name=AACCEPT value=text/plain/ /characteristic characteristic type=APPAUTH parm name=AAUTHNAME value=funUsrVe/ parm name=AAUTHSECRET value=funPassVe/ /characteristic /characteristic /wap-provisioningdoc When i send it via Kannel's /sendota, via this request: /cgi-bin/sendota?password=##username=##type=oma-settingssec=USERPINpin=1234to=%2B37069953201text=%3C%3Fxml+version%3D%221.0%22%3F%3E%0A%3C%21DOCTYPE+wap-provisioningdoc+PUBLIC+%22-%2F%2FWAPFORUM%2F%2FDTD+PROV+1.0%2F%2FEN%22%0A%22http%3A%2F%2Fwww.wapforum.org%2FDTD%2Fprov.dtd%22%3E%0A%3Cwap-provisioningdoc%3E%0A%3Ccharacteristic+type%3D%22BOOTSTRAP%22%3E%0A%3Cparm+name%3D%22NAME%22+value%3D%22SKLADDEVEL%22%2F%3E%0A%3C%2Fcharacteristic%3E%0A
Re: SQLBox with utf8 chars
Hi, I had a planning to test sqlbox with the latest version (1.4.2 and 1.4.3) as it changed the encoding, and also to test on the various encodings on mysql.. Unfrotunately I haven't had the chance yet. Julien 2009/6/1 seikath seik...@gmail.com: on Insert use the dcs value and some scripting language functions to detect the encoding of the text and then just convert it from ucs-2be to your local encoding then you could transliterate if you want cheers Benaiad wrote: Hi, I'm new to sqlbox and I'm trying to send and receive utf8 messages, but whenever I receive a message(MO in utf8 charset) it is stored in hex values , and I don't know is it normal or I'm messing something! I've tried the utf8 in table charset and msgdata field but it's the same Frankly, I'm trying to use sqlbox and mysql triggers for production system, When a new message is inserted, a trigger (inside db engine) will be executed and store a response in the send_sms table. Thanks Best Regards. -- Julien Buratto
Re: Kannel's Users
Well, do you really think that someone will share this info ? :-) Com'on :-) 2008/12/5 sangprabv sangpr...@gmail.com: Hi list, I'm doing a presentation and need some data of Kannel's users. Therefor if you don't mind please share with me your company's name, country, and your SMS traffic/month. TIA. Willy Stay away from hurricanes for a while. -- Julien Buratto
Re: HELP! Patent claim! Can we use an alternate protocol?
So, at the end no reply with patent id, so it's a buzz ?
Julien
2009/2/14 Stipe Tolj s...@gw.tolj.org:
David schrieb:
Hello,
Us users of SMS Shortcodes are getting hit in the US for violating a
patent by TCS Inc. The patent claims to cover:
A gateway, comprising: a first communication path to accept a short
message from a mobile device; a translation module to insert said short
message into an Hypertext Transfer Protocol (HTTP) message; a second
communication path to push said HTTP message to at least one Universal
Resource Locator (URL); and a return communication path to receive a
return message relating to said HTTP message.
The patent goes on to mention a whole bunch of stuff, ie, using HTTP
POST to send the http message, etc.
I just got out of a meeting with my lawyer. He says, the only way to
get around this is to NOT use HTTP.
Over the weekend, I tried to use the sms-service using EXEC instead of
GET-URL, which worked fine... and then the server crashed... i'm
guessing too many spawned processes?
My question to you all is: how can we NOT use HTTP but have the same
end result? ideally, it would use a command-line exec, but push it into
a waiting server, instead of spawning a new thread. Does anybody have
any ideas on how to do this?
Hi David,
there seems to be a HUGE buzz here in the list regarding this patent issue.
Can you please reference the patent with patent no./ID, so we can have access
to
it and READ what it actually claims to be an invention?
In any modern country, an invention has a precondition: the invention has to
be done FIRST by the claimer. If the pure concept is KNOWN to the public, even
without patent pending registration, a patenting IS NOT possible, and can't be
legally prosecuted.
Therefore, please state the exact patenting country, no., ID and name of
claimer.
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
---
--
Julien Buratto
Re: sendota kannel 1.4.1 VS 1.4.3 - differences
I'm adding a little piece of info: 1.4.1 converts XML to WBXML and send out the message 1.4.3 does not convert XML to WBXML but leave the XML in place Result: 1.4.3 is trying to send a plain XML file as a wap push to the correct ports but wrong content I'm now thinking that maybe when I recompiled the 1.4.3 some inclusion of libxml2 error...
Re: GIF Encoder - application
Mike, sure! 2009/5/28 Mike Nwaogu michael_nwa...@yahoo.com: This dimensions are in pixels right?? Regards, Mike Nwaogu Tel: 234_802_325_6437 From: Alejandro Guerrieri alejandro.guerri...@gmail.com To: Mike Nwaogu michael_nwa...@yahoo.com Cc: users@kannel.org Sent: Thursday, May 28, 2009 11:45:12 AM Subject: Re: GIF Encoder - application You mean those 72x14 and 72x28 B/W logos? I'd start by resizing the image to fit on one of those sizes beforehand... The SmartPhone and perhaps SCKL formats should work with most Nokias. Hope it helps, Alejandro On Thu, May 28, 2009 at 11:27 AM, Mike Nwaogu michael_nwa...@yahoo.com wrote: Hello All, I've been trying to encode the attached image to HEX and send it as a NOKIA Picture message. I've tried some of the hex strings I saw on the list and some of them work well, however, no matter what I use for the encoding it never appears on the phone. I've tried mike khorn's ringtonetools, enterflex, image magick would like to know how to convert correctly with any of these above mentioned converters and encoders. Regards, Mike Nwaogu Tel: 234_802_325_6437 -- Julien Buratto
Re: ASCII Message
Hi, sorry but I did not understand the issue. if you want to send hello via sms to a different port, you change the port via UDH (please don't use a standard wap-push port because any application listening on a mobile phone will throw exceptions if you try to open a port where the device is listening for configuration/wap messages). Once you find a port that is suitable for your application, you can send binary messages to it, just send the text hello and kannel will convert that to %68%65%6c%6c%6f which is the urlencoded version (let's say %+hex code) of the character. The device will receive it as hello nomatter how. If you want kannel to force the hello word to appear to your application as a text payload and not a binary payload you can try forcing the encoding to 0 with coding=0 parameter. I'm not sure this will work as kannel, by default, sets coding=1 when a UDH is set. Julien 2009/5/27 Irfan Malik irfan.ma...@tcm.com.pk: Hi, I require UDH header to change the destination port. It is working fine for simple SMS. That I can send simple SMS on different port now. http://localhost:13013/cgi-bin/sendsms?username=userpassword=passtext=Hell oudh==%06%05%04%40%7A%23%F0 Now, I want the same for WAP Push, I am using smss.php for WAP Push creation. Problem is that when I deliver WAP Push on non standard port, it becomes un readable. Do any one has Idea why WAP Push on non standard port for example becomes un readable on handset? Regards, Irfan Malik = Manager MIS TricastMedia Cell: +92 321-6099155 PH: +92 42 5845265 Web: www.tcm.com.pk -Original Message- From: Rodrigo Cremaschi [mailto:rodrigo.cremas...@gmail.com] Sent: Wednesday, May 27, 2009 10:45 PM To: Irfan Malik Cc: users@kannel.org Subject: Re: ASCII Message Hello Irfan, Omit the UDH header. Regards. On Wed, May 27, 2009 at 2:58 PM, Irfan Malik irfan.ma...@tcm.com.pk wrote: Hello every body, Is there any method with which we can send ASCII text instead of hexadecimal using sendsms? http://localhost:13013/cgi-bin/sendsm?username=userpassword=passudh=%06%05 %04%40%7A%23%F0text=test Kannel converts text test to hexadecimal and delivers message. Can we change default behavior of Kannel so it sends SMS and in ASCII format? Regards, Irfan Malik = Manager MIS TricastMedia Cell: +92 321-6099155 PH: +92 42 5845265 Web: www.tcm.com.pk -- Julien Buratto
Re: sendota problems
6032E2F63616C656E64617200018707060343616C656E646172 which are successfully delivered to the phone and recognized by it as a valid and working synchronization settings. Funnily enough, these three messages are routed via the same kannel. Therefore my questions are: * is Kannel wrongly transforming my request into OMA settings provisioning message? * if so, is it because of my error or because of a bug in Kannel? any other advice? -- Tomas Verbaitis Verbaitis ** http://megalogika.lt -- Julien Buratto
Re: SMPP - meda-data DLRs - getting parameters in DLR
Hi Sorry, maybe my question was not well specified. Alejandro I'm already using the smpp-tlv params and words fine. What I was wondering is I can pass those variables back to DLRs When I send an sms I use dlr-url=http://www.domain.com?sender=%P; and I get the sender=some number, but if I use the dlr-url as: http://www.domain.com?sender=%Pmeta-data=%meta-data I don't get anything (even if the logs show that some meta-data where detected). So I was wonder if: a) there is a special var that I need to pass to a dlr-url to get those params b) if passing back TLVs to dlr-url was already supported. Thanks again Julien 2009/5/26 Nikos Balkanas nbalka...@gmail.com: Hi, 1) Yes, it is supported in1.4.3. 2) AFAIK works only with SMPP amd need to have a tlv group defined to use it. BR, Nikos - Original Message - From: Julien Buratto julien.bura...@gmail.com To: users@kannel.org Sent: Tuesday, May 26, 2009 3:19 PM Subject: SMPP - meda-data DLRs - getting parameters in DLR Hi, normally I use some variables passed to the dlr-url parameters such as %P in order to get status informations. Now that I'm using cvs version with meta-data, I was wondering if anyone knows how to get the meta-data from deliver_sm PDUs in DLR urls. I've tried %D param wich was documented in smsbox.c, but I don't know if: 1) it's already supported feature 2) I was looking at the right place Thanks -- Julien Buratto -- Julien Buratto
sendota kannel 1.4.1 VS 1.4.3 - differences
Hi, I'm upgrading my 1.4.1 kannel to 1.4.3 and noticed that sendota with oma settings is not working same way. Both were compiled using the same machine and config.nice command My testing environment is: html page with a form to pass all the required variables to sendoda html page is iso-8859-1 encoding result is OK (ota is recognized by the device, saved and works) On 1.4.3 I did: Used the same page, change the html page's encoding to iso-8859-1 to UTF-8 result is: sms is sent, device require PIN, accept pim, device pretend to say configuration saved but profile is not saved. I've repeated this test a could of times resetting the device, restarting, deleted old profile (also tested on other devices and other phone numbers) and I can confirm that there is a difference that I cannot tell where it is. Anyone has a clue ?
Re: SMPP - meda-data DLRs - getting parameters in DLR
Hi Alejandro, now we are on the same page :-) As I was mentioning, I've already tried %D but seems not to pass anything back.. does the smsbox log would help ? Julien 2009/5/27 Alejandro Guerrieri alejandro.guerri...@gmail.com: Julien, The parameter is %D, not %meta-data. You should be able to retrieve the meta-data from the current deliver_sm or submit_sm_resp PDU with that parameter. Regards, Alejandro On Wed, May 27, 2009 at 11:45 AM, Julien Buratto julien.bura...@gmail.com wrote: Hi Sorry, maybe my question was not well specified. Alejandro I'm already using the smpp-tlv params and words fine. What I was wondering is I can pass those variables back to DLRs When I send an sms I use dlr-url=http://www.domain.com?sender=%P; and I get the sender=some number, but if I use the dlr-url as: http://www.domain.com?sender=%Pmeta-data=%meta-data I don't get anything (even if the logs show that some meta-data where detected). So I was wonder if: a) there is a special var that I need to pass to a dlr-url to get those params b) if passing back TLVs to dlr-url was already supported. Thanks again Julien 2009/5/26 Nikos Balkanas nbalka...@gmail.com: Hi, 1) Yes, it is supported in1.4.3. 2) AFAIK works only with SMPP amd need to have a tlv group defined to use it. BR, Nikos - Original Message - From: Julien Buratto julien.bura...@gmail.com To: users@kannel.org Sent: Tuesday, May 26, 2009 3:19 PM Subject: SMPP - meda-data DLRs - getting parameters in DLR Hi, normally I use some variables passed to the dlr-url parameters such as %P in order to get status informations. Now that I'm using cvs version with meta-data, I was wondering if anyone knows how to get the meta-data from deliver_sm PDUs in DLR urls. I've tried %D param wich was documented in smsbox.c, but I don't know if: 1) it's already supported feature 2) I was looking at the right place Thanks -- Julien Buratto -- Julien Buratto -- Julien Buratto
Re: Q: Service test using US based web2sms
This is a complex topic as the US market is very different from European market. In the US have fear of binary sms, dinamic senders and so on so carriers have different approaches. Also check clickkatell wich have contracts with the carriers in US and can provide you some sms, however to get a customized sender to Verizon for example is very complex. 2009/5/24 b poscout bposc...@gmail.com: Not directly related to Kannel, but rather to the testing of a service based on it. In Europe some operators offer a web based service to send and receive SMS using your MSISDN as part of their standard features. Very handy for testing. I'm looking for a US operator (or a third party) that offers the same. (Note. I expect to pay for this.) I need MO/MT SMS via a web based UI. Must be US MSISDN and cannot be a shortcode. However, the web UI must allow MO SMS to be sent to a US shortcode. I've looked at ATT and TMobile but see nothing that looks like this functionality. Anyone? -- Julien Buratto
Re: [ANNOUNCE] New Sqlbox version: 0.7.2
Hi Alejandro, about SQLbox have you ever tested if mysql (for example) acts in a differen way if creating tables with different encodings ? Does data in the table must be saved in utf-8 like new kannel 1.4.3 or still latin1 ? Julien 2009/5/20 Alejandro Guerrieri alejandro.guerri...@gmail.com: I’ve just updated SqlBox. Version 0.7.2 adds: * rpm target (already on the latest snapshot). You can now run ./configure and then make rpm to build an RPM! * Support for MS-SQL and Sybase over FreeTDS. You need a current Kannel snapshot to support this. * Some code cleanups. You can get it from here. Regards, Alejandro -- Julien Buratto
Re: message id through sendsms url
Hi Piyush, if you are using smpp tlv and your carrier provides one, yes, otherwise you need to play with dlr-url and dlr-mask to customize your own sms messages with a specific id that you can track back when the dlr comes back from the smsc... Julien 2009/5/27 Piyush piy...@ibibo.com: Hi, Can it be possible to get message id instead of 0: accepted for delivery in response when I call sendsms url. Thanks in advance Piyush Khandelwal ibibo Mail :: Get your FREE mail box with Music, Skins, Greetings and Stationery now! -- Julien Buratto
Re: way newbie question
I would just add that if you are paying 150$ for 1000 sms and the service is working perfectly, even if you can get half of the price, you will need to have a smsc contract, maintain your software, updates, configuration, time etc and for 12.000 sms a year it's maybe not worth to save 700$ Just find an smsc online (normally are called sms gateway) and implement their http interface creating an API. I feel kannel more interesting for people with tons of sms to cope with.. but yes, you can use it, why not :) J 2009/5/22 Jovan Kostovski chomb...@gmail.com: On Thu, May 21, 2009 at 11:22 PM, Hans Guth hg...@listingsmagic.com wrote: ok - so just diving into this world of sms. Here's my question. We are paying for a hosted pbx service whereby a potential home buyer calls 800#. We then text them back property information to their cell phone using this same pbx company's sms service. They are charging $150 per month for 1000 texts. I am wondering will I be able to do that through the use of kannel and save that money? Your provider sells you a bundle of 1000 sms/month for $150 meaning 15 cents/sms. There are two ways of connecting Kannel to your SMS provider. The first one is to connect directly to the SMS Center (SMSC) [1] via Short Message Peer 2 Peer (SMPP) [2] protocol. This means that you'll have to setup a machine with Kannel running on it which will connect to the SMSC. From commercial point of view, the provider will sell you X SMS/sec, hour or so. You'll have to pay for certain amount of messages per time interval, or you'll pay for the amount the messages you'll send. This means that you'll end up in the same position as you are now. The second option is to use mobile phone or GSM modem as a SMSC. This means that you'll set up Kannel box to which you'll connect mobile phone or a GSM modem. This way you'll pay the same way as you do when you are sending messages from your mobile phone. The good thing about this is that you'll pay only the messages that you send (you won't have to pay 1000 messages per month when you've only sent 300 for example) and you can choose some rate plan from your mobile operator which is designed for subscribers who send large number of SMSs. By choosing a proper rate plan and planing the message sending you can save some money. Comparing this to your current solution, this means that you have to find cheaper SMS than 15 cents or send less than 1000 messages/month Setting up a Kannel depends on the connection that you will use. Search the archives for connection types, commonly used gsm modems and read the user guide. References: [1] http://en.wikipedia.org/wiki/Short_message_service_center [2] http://en.wikipedia.org/wiki/Short_message_peer-to-peer_protocol BR, Jovan -- Julien Buratto
Re: Warning During make with latest CVS version (snapshot)
warnings are warnings, be warned but don't be scared ;) j 2009/5/22 sangprabv sangpr...@gmail.com: Hi, I received these warnings during make: gwlib/gwthread-pthread.c: In function ‘gwthread_wakeup’: gwlib/gwthread-pthread.c:679: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result gwlib/utils.c: In function ‘become_daemon’: gwlib/utils.c:219: warning: ignoring return value of ‘dup’, declared with attribute warn_unused_result gwlib/utils.c:220: warning: ignoring return value of ‘dup’, declared with attribute warn_unused_result gwlib/utils.c:222: warning: ignoring return value of ‘chdir’, declared with attribute warn_unused_result utils/start-stop-daemon.c: In function ‘main’: utils/start-stop-daemon.c:918: warning: ignoring return value of ‘chdir’, declared with attribute warn_unused_result utils/start-stop-daemon.c:926: warning: ignoring return value of ‘dup’, declared with attribute warn_unused_result utils/start-stop-daemon.c:927: warning: ignoring return value of ‘dup’, declared with attribute warn_unused_result Is it normal? Willy -- Julien Buratto
SMPP - meda-data DLRs - getting parameters in DLR
Hi, normally I use some variables passed to the dlr-url parameters such as %P in order to get status informations. Now that I'm using cvs version with meta-data, I was wondering if anyone knows how to get the meta-data from deliver_sm PDUs in DLR urls. I've tried %D param wich was documented in smsbox.c, but I don't know if: 1) it's already supported feature 2) I was looking at the right place Thanks -- Julien Buratto
SMS billing and encoding
Now that kannel uses UTF-8 characters in order to receive SMS contents to be delivered, I'm evaluating optional billings at smsc... so, if with version 1.4.1 of kannel I would have written: http://localhost:14000/cgi-bin/sendsms?text=%E8 in order to send out the character è (which is iso-8859-1) with version 1.4.3 I have to write: http://localhost:14000/cgi-bin/sendsms?text=%C3%A8 as %C3%A8 is the UTF-8 rappresentation of the %E8 If I'm sending standard text 160 character MT SMS, each char is 7 bit and for each 160 chars I get billed for 1 SMS. I'm expecting kannel to send to the smsc only the correct characters converted in the right encoding (based on coding= and charset= variables) and not using UTF-8 by default, is that correct ? Recap: I'm I correct when saying that kannel will use for internal/external communication UTF-8 chars but for smsc communication the encoding is what is set via coding/charset ? -- Julien Buratto
Re: Easy one: encoding between 1.4.1 and 1.4.1
Hi Alejandro, let me be more verbose to confirm if my understanding is correct. If I have an html FORM which sets the text message to be sent via SMS, the page encoding must be UTF-8 ? Currently I have this scenario: - my webpage is ISO-8859-1 and contains a form - i populate the form with destination number, sender and text - action of the form is a php page - php page makes an http request (GET) to kannel adding kannel specific params (such as drl, username, smsc id and so on) - php page get kannel return status to confirm if request was successfully performed Do you then suggest to convert the webpage to UTF-8 ? Thanks for helping Julien PS: What I could do is to use the php ut8_encode() function (utf8_encode — Encodes an ISO-8859-1 string to UTF-8) and apply it to the text field. If my page is ISO-8859-1, I presume all the input type=text / fields are also encoded into same page encoding so the php script would catch the text as ISO-8859-1 Appying the php utf8_encode will allow me to keep the pages in ISO-8859-1 but convert the text to UTF-8 before sending it to kannel. Am I correct ? 2009/5/12 Alejandro Guerrieri alejandro.guerri...@gmail.com: This is because Kannel now uses UTF-8 as default encoding. Encode the text with UTF-8 or change the charset to ISO-8859-1 instead. Regards, Alejandro On Tue, May 12, 2009 at 5:43 PM, Julien Buratto julien.bura...@gmail.com wrote: Hi guys, I'm running 1.4.1 with a configuration and 1.4.3 with (slightly adapted) same configuration. Sending MT messages with 1.4.1, I get characters correctly grave, same command with 1.4.3 I get grave letters screwed. Example: 1.4.1: Today is lunedì 18 maggio 1.4.3: Today is luned?8 maggio as you can see, ì is screwed into ? plus some other characters were eaten. What should I change/read in order to get old 1.4.1 behaviour back again ? Thanks for helping PS: If you have a direct link to a manual section pointing me to the right lines to read, I will be glad to read :-) General rtfm not useful :-)) -- Julien -- Julien Buratto
Re: Ethernet Modem vs. USB Modem
Hi Bryan, my experience with USB modems was not really a happy party till now. USB stacks on linux OS changed a lot in years/distributions so it's was sometimes bad to manage. Same modem's manufacturer changed the internal modules so same models bought in different timeframes had different configurations/issues USB compatibilities on some fedoras (for example). I've never used ethernet modems before, but I'd love to test some (can you suggest one ?) because I see some advantages: - more easy to cluster as it's nowadays easier to find a good working eth switch than a USB port replicator - usb ports die more frequently (in my opinion) and have more power problems that eth - eth can be more easily remoted from kannel than usb... (so for example you can host in house the modems and virtual-cloud your kannels somewhere else) On the otherside, I think that USB modems are less expensive... J 2009/5/13 Bryan Gintz bgi...@coyfc.org: If I am going to buy a new GPRS modem to use wieth Kannel, what would people recommend: Ethernet or USB? Thanks, Bryan -- Julien Buratto
Easy one: encoding between 1.4.1 and 1.4.1
Hi guys, I'm running 1.4.1 with a configuration and 1.4.3 with (slightly adapted) same configuration. Sending MT messages with 1.4.1, I get characters correctly grave, same command with 1.4.3 I get grave letters screwed. Example: 1.4.1: Today is lunedì 18 maggio 1.4.3: Today is luned?8 maggio as you can see, ì is screwed into ? plus some other characters were eaten. What should I change/read in order to get old 1.4.1 behaviour back again ? Thanks for helping PS: If you have a direct link to a manual section pointing me to the right lines to read, I will be glad to read :-) General rtfm not useful :-)) -- Julien
Re: Sent_sms and Send_sms
The time that you mention is passed to the SMSC you are connecting to, it's not up to kannel to manage the time delay. So, basically, if your SMS provider supports timed sms, it will work, if not, then it's not useful, however you could change the SQLBOX select query in order to select only those messages where the NOW() values is greater then the TimeStamp + time and if your database clock is set accordingly, you will get what you are looking for. 2008/8/9 info.ubichip [EMAIL PROTECTED] Hello all, Do someone know the purpose of the table send_sms in the sqlbox ? Sent_sms is the table that logs everything. When I put some sms in send_sms, they are sent automatically. Does there is anyway to send them with a specific time ? I saw a field time in this table but it look not working! Thanks in advance for your help. -- Julien Buratto
MO sms are stored but not forwarded to service
Hi, via my EMI connection, I'm receiving an sms and I can see, in the bearerbox, the line: 2008-06-18 18:22:54 [31314] [7] DEBUG: EMI2[carrier]: emi2 parsing packet: ^B02/00131/O/52/0039335635/0039320204/1806081822503//236C696E6B6173232070726F7661203111139/94^C ( means I've manually deleted 4 numbers :-) As a result, the received SMS is stored as: 0852ad11-3118-44a7-85ac-dce84a6b3acdMO 2008-06-18 20:45:580039320204 0039335635 carrier #linkas# test numero 2 but the SMS is not forwarded to the sms-service group which is: group = sms-service keyword = default get-url = http://myserver_url/inbox.php?Text=%aTimestamp=%TSender=%pDestination=%P; max-messages = 0 Now I face 2 questions: 1) I haven't set the my-number in the smsc configuration for the emi smsc, does this can prevent the receive of the sms ? 2) In the logs, just after that line, i get 2008-06-18 18:22:54 [31314] [7] WARNING: smsbox_list empty!, does this can prevent the receive of the sms ? Is there anything else I could check ? -- Julien Buratto
Re: Unconsistent re-submitted UDH
So, I came up to the end finally. The final note is: 1) if you send a concatenated message: - create your 7 bytes UDH - set your coding=0 - set the body with your 153 chars EXAMPLE1: Without using Kannel auto-splitting: sms1) coding=0udh=%05%00%03%81%02%01text=%31%32%33%34%35%36%37%38%39%2d%31%32%33%34%35%36%37%38%39%2d%31%32%33%34%35%36%37%38%39%2d%31%32%33%34%35%36%37%38%39%2d%31%32%33%34%35%36%37%38%39%2d%31%32%33%34%35%36%37%38%39%2d%31%32%33%34%35%36%37%38%39%2d%31%32%33%34%35%36%37%38%39%2d%31%32%33%34%35%36%37%38%39%2d%31%32%33%34%35%36%37%38%39%2d%31%32%33%34%35%36%37%38%39%2d%31%32%33%34%35%36%37%38%39%2d%31%32%33%34%35%36%37%38%39%2d%31%32%33%34%35%36%37%38%39%2d%39%38%37%36%35%34%33%32%31%2d%39%38%37 sms 2) coding=0udh=%05%00%03%81%02%02text=%36%35%34%33%32%31%2d%39%38%37%36%35%34%33%32%31%2d EXAMPLE 2: Using Kannel auto-splitting: text=123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-987654321-987654321-987654321- Note: %31%32%33 is the urlencoded form for 1+2+3 which is the string 123 2) if you send a plain 160 chars message - don't set any udh not coding and allow kannel to manage the coding (so coding=0 will be used as default) text=123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789- 3) if you send a OTA message - create your n-bytes UDH - set the coding=1 (8-bits) - set your body (available are 140-n-bytes used in the UDH) EXAMPLE (POP3 configuration): If you want to use a OMA-CP configuration message: ?xml version=1.0? !DOCTYPE wap-provisioningdoc PUBLIC -//WAPFORUM//DTD PROV 1.0//EN http://www.wapforum.org/DTD/prov.dtd; !-- So, let's start the configuratio using OMA CP 1.1 specifications -- wap-provisioningdoc version=1.1 characteristic type=APPLICATION !-- The APPID rappresents a unique identifier to POP3 -- parm name=APPID value=110 / !-- This is an internal ID to internal reference -- parm name=PROVIDER-ID value=MyPOPMail / !-- Here is the POP3 server details -- characteristic type=APPADDR parm name=ADDR value=pop.example.com / !-- Port number for POP3 is normally 110 -- characteristic type=PORT parm name=PORTNBR value=110 / /characteristic !-- Here are the username/password of your POP3 server -- /characteristic characteristic type=APPAUTH !-- Julien.buratto is my email's username to access via POP3 -- parm name=AAUTHNAME value=julien.buratto / parm name=AAUTHSECRET value=Password / /characteristic /characteristic !-- Now let's configure the SMTP to send emails -- characteristic type=APPLICATION !-- Same as per any .application. you want to configure, the unique ID for smtp is 25 -- parm name=APPID value=25 / !-- Same provider ID as per POP3 so both POP3 and SMTP will be bound together -- parm name=PROVIDER-ID value=MyPOPMail / !-- Emails will be sent as -- parm name=FROM value=[EMAIL PROTECTED] / !-- Here is the SMTP server address -- characteristic type=APPADDR parm name=ADDR value=smtp.example.com / !-- Here is the SMTP port -- characteristic type=PORT parm name=PORTNBR value=25 / /characteristic /characteristic !-- Here are the username/password to access the SMTP server if authenticated -- characteristic type=APPAUTH parm name=AAUTHNAME value=OutgoingName / parm name=AAUTHSECRET value=Password / /characteristic /characteristic !-- That's all folks, no more things to configure -- /wap-provisioningdoc This would result in 3 SMS sent: 1 SMS) coding=1 udh=%0b%05%04%0b%84%0b%84%00%03%82%03%01 text=%01%06%2f%1f%2d%b6%91%81%92%45%34%44%44%43%30%46%30%34%35%39%42%44%31%35%32%42%37%31%41%32%33%35%38%43%34%32%46%38%34%36%46%38%42%33%38%45%44%34%41%00%03%0b%6a%00%c5%45%03%31%2e%31%00%01%c6%00%01%55%01%87%36%06%03%31%31%30%00%01%87%38%06%03%4d%79%50%4f%50%4d%61%69%6c%00%01%c6%56%01%87%34%06%03%70%6f%70%2e%65%78%61%6d%70%6c%65%2e%63%6f%6d%00%01%c6%00%00%53%01%87%23%06%03%31%31%30%00 2 SMS) coding=1 udh=%0b%05%04%0b%84%0b%84%00%03%82%03%02 text=%01%01%01%c6%00%01%57%01%87%31%06%03%6a%75%6c%69%65%6e%2e%62%75%72%61%74%74%6f%00%01%87%32%06%03%50%61%73%73%77%6f%72%64%00%01%01%01%c6%55%01%87%36%06%03%32%35%00%01%87%38%06%03%4d%79%50%4f%50%4d%61%69%6c%00%01%87%05%03%46%52%4f%4d%00%06%03%73%6f%6d%65%6f%6e%65%40%65%78%61%6d%70%6c%65%2e%63%6f%6d%00%01%c6%56%01%87%34%06%03%73%6d%74%70%2e%65%78%61%6d%70%6c%65%2e%63%6f%6d%00%01%c6%00 3 SMS) coding=1udh=%0b%05%04%0b%84%0b%84%00%03%82%03%03text=%00%53%01%87%23%06%03%32%35%00%01%01%01%c6%00%01%57%01%87%31%06%03%4f%75%74%67%6f%69%6e%67%4e%61%6d%65%00%01%87%32%06%03%50%61%73%73%77%6f%72%64%00%01%01%01%01 (more info on how to create the binary stuff here: http://dev.mobi/article/email-configuration-sms) Julien 2008/5/24 Julien Buratto [EMAIL
Re: Unconsistent re-submitted UDH
Following my previous message, I've made some tests based on the documentation which states that the message coding, when submitting with the udh is changed to 8bits, I've added the coding=0 variable to my http request to smsbox and it seems that the UDH is not re-written. I will perform some more tests. Julien 2008/5/23 Julien Buratto [EMAIL PROTECTED]: Hello, I've performed a little test getting a kannel generated UDH message and re-submit it back to kannel and had a strange behavior. Via HTTP I've sent an sms to smsbox such as text=123456789-123456789- till the body was 170 chars (long message) On the bearerbox logs I've seen that the message is sent sending two concatenated messages. UDH is 05 00 03 03 02 01 (first chunk) and second UDH is 05 00 03 03 02 02 (second chunk) and this is a very cool feature of kannel: if you send a long message, kannel will automatically chunk it in n little chunks and write the correct UDH for you. So, now that I learnt how to chunk messages, I've tryed to send those 2 chunks separately,one at time, so that Kannel does not need to do the chunking automatically. So, I've taken the two generated chunk-sms that I've read before from the logs and resubmitted to the msbox as udh=%05%00%03%03%02%01 text=123456789-... (for the first 154 chars) and then sent out another sms with the second chunk... udh=%05%00%03%03%02%02 text=...the rest of the message What I've noticed, this time, is that Kannel changes the UDH to 0a 00 03 04 02 01 00 03 c9 02 01 while the text isn't changed at all. So the point is, why does Kannel change that ? How can I prevent this ? thanks -- Julien -- Julien Buratto
Re: Unconsistent re-submitted UDH
Investigation continues... So, the first test was related to a long message which went out fine using coding=0 The second test I've performed was to send out a OTA message with coding=0 but behavior is not the same In this case, the message coming from kannel is resent on the URL and the behavior is like the one described before, the message gets broken somehow. Checking for message details, the OTA is sent as a Octet byte (8 bits, not 7) so the correct behavior should be using the generic 8 bit encoding at 8 bits (coding=1) but... surprise... this does work only on 1 box on 3. 1st box (not working): Kannel bearerbox version `1.4.1'. Build `Oct 6 2006 13:34:37', compiler `4.0.2 20051125 (Red Hat 4.0.2-8)'. System Linux, release 2.6.11-1.1369_FC4, version #1 Thu Jun 2 22:55:56 EDT 2005, machine i686. Hostname komosubi, IP 10.100.10.10. Libxml version 2.6.20. Using OpenSSL 0.9.7f 22 Mar 2005. Compiled with MySQL 4.1.20, using MySQL 4.1.20. Using native malloc. (kannel stable 1.4.1) 2nd box (not working): Kannel bearerbox version `cvs-20080424'. Build `May 24 2008 14:54:26', compiler `4.0.2 20051125 (Red Hat 4.0.2-8)'. System Linux, release 2.6.11-1.1369_FC4, version #1 Thu Jun 2 22:55:56 EDT 2005, machine i686. Hostname komosubi, IP 10.100.10.10. Libxml version 2.6.20. Using OpenSSL 0.9.7f 22 Mar 2005. Compiled with MySQL 4.1.20, using MySQL 4.1.20. Using native malloc. (today CVS) 3rd box: (working): Kannel bearerbox version `1.4.1'. Build `Oct 17 2006 02:55:06', compiler `4.1.2 20061007 (prerelease) (Debian 4.1.1-16)'. System Linux, release 2.6.8-2-386, version #1 Thu May 19 17:40:50 JST 2005, machine i686. Hostname localhost.localdomain, IP 127.0.0.1. Libxml version 2.6.26. Using OpenSSL 0.9.8c 05 Sep 2006. Compiled with MySQL 5.0.24a, using MySQL 5.0.32. Using native malloc. (kannel_1.4.1-1sarge.1_i386.deb) 2008/5/24 Julien Buratto [EMAIL PROTECTED]: Following my previous message, I've made some tests based on the documentation which states that the message coding, when submitting with the udh is changed to 8bits, I've added the coding=0 variable to my http request to smsbox and it seems that the UDH is not re-written. I will perform some more tests. Julien 2008/5/23 Julien Buratto [EMAIL PROTECTED]: Hello, I've performed a little test getting a kannel generated UDH message and re-submit it back to kannel and had a strange behavior. Via HTTP I've sent an sms to smsbox such as text=123456789-123456789- till the body was 170 chars (long message) On the bearerbox logs I've seen that the message is sent sending two concatenated messages. UDH is 05 00 03 03 02 01 (first chunk) and second UDH is 05 00 03 03 02 02 (second chunk) and this is a very cool feature of kannel: if you send a long message, kannel will automatically chunk it in n little chunks and write the correct UDH for you. So, now that I learnt how to chunk messages, I've tryed to send those 2 chunks separately,one at time, so that Kannel does not need to do the chunking automatically. So, I've taken the two generated chunk-sms that I've read before from the logs and resubmitted to the msbox as udh=%05%00%03%03%02%01 text=123456789-... (for the first 154 chars) and then sent out another sms with the second chunk... udh=%05%00%03%03%02%02 text=...the rest of the message What I've noticed, this time, is that Kannel changes the UDH to 0a 00 03 04 02 01 00 03 c9 02 01 while the text isn't changed at all. So the point is, why does Kannel change that ? How can I prevent this ? thanks -- Julien -- Julien Buratto -- Julien Buratto
Unconsistent re-submitted UDH
Hello, I've performed a little test getting a kannel generated UDH message and re-submit it back to kannel and had a strange behavior. Via HTTP I've sent an sms to smsbox such as text=123456789-123456789- till the body was 170 chars (long message) On the bearerbox logs I've seen that the message is sent sending two concatenated messages. UDH is 05 00 03 03 02 01 (first chunk) and second UDH is 05 00 03 03 02 02 (second chunk) and this is a very cool feature of kannel: if you send a long message, kannel will automatically chunk it in n little chunks and write the correct UDH for you. So, now that I learnt how to chunk messages, I've tryed to send those 2 chunks separately,one at time, so that Kannel does not need to do the chunking automatically. So, I've taken the two generated chunk-sms that I've read before from the logs and resubmitted to the msbox as udh=%05%00%03%03%02%01 text=123456789-... (for the first 154 chars) and then sent out another sms with the second chunk... udh=%05%00%03%03%02%02 text=...the rest of the message What I've noticed, this time, is that Kannel changes the UDH to 0a 00 03 04 02 01 00 03 c9 02 01 while the text isn't changed at all. So the point is, why does Kannel change that ? How can I prevent this ? thanks -- Julien
Re: Using ttyACM0 as modem
Solved, so I post my solution: kernel upgrade ! gosh Julien Julien Buratto ha scritto: Hi all, I'm trying a new modem usb. When I plugit into my linux box, I get from kernel: Jun 1 14:43:37 db kernel: cdc_acm 4-1:1.0: ttyACM0: USB ACM device If I set this tty to kannel.conf and launch kannel, I get in the logs: 2007-06-01 14:46:24 [5106] [7] INFO: AT2[Modem_TEST]: opening device 2007-06-01 14:46:24 [5106] [7] DEBUG: AT2[Modem_TEST]: device opened 2007-06-01 14:46:25 [5106] [7] DEBUG: AT2[Modem_TEST]: device opened 2007-06-01 14:46:25 [5106] [7] INFO: AT2[Modem_TEST]: speed set to 57600 2007-06-01 14:46:25 [5106] [7] DEBUG: AT2[Modem_TEST]: -- ^M 2007-06-01 14:46:27 [5106] [7] DEBUG: AT2[Modem_TEST]: -- AT^M 2007-06-01 14:46:31 [5106] [7] DEBUG: AT2[Modem_TEST]: -- AT^M 2007-06-01 14:46:35 [5106] [7] DEBUG: AT2[Modem_TEST]: -- AT^M 2007-06-01 14:46:39 [5106] [7] INFO: AT2[Modem_TEST]: closing device 2007-06-01 14:46:39 [5106] [7] INFO: AT2[Modem_TEST]: opening device 2007-06-01 14:46:39 [5106] [7] DEBUG: AT2[Modem_TEST]: device opened 2007-06-01 14:46:40 [5106] [7] DEBUG: AT2[Modem_TEST]: device opened 2007-06-01 14:46:40 [5106] [7] INFO: AT2[Modem_TEST]: speed set to 38400 2007-06-01 14:46:40 [5106] [7] DEBUG: AT2[Modem_TEST]: -- ^M 2007-06-01 14:46:42 [5106] [7] DEBUG: AT2[Modem_TEST]: -- AT^M 2007-06-01 14:46:46 [5106] [7] DEBUG: AT2[Modem_TEST]: -- AT^M 2007-06-01 14:46:50 [5106] [7] DEBUG: AT2[Modem_TEST]: -- AT^M 2007-06-01 14:46:54 [5106] [7] INFO: AT2[Modem_TEST]: closing device 2007-06-01 14:46:54 [5106] [7] INFO: AT2[Modem_TEST]: opening device 2007-06-01 14:46:54 [5106] [7] DEBUG: AT2[Modem_TEST]: device opened 2007-06-01 14:46:55 [5106] [7] DEBUG: AT2[Modem_TEST]: device opened 2007-06-01 14:46:55 [5106] [7] INFO: AT2[Modem_TEST]: speed set to 19200 My configuration for that modem is: group = smsc smsc = at smsc-id = Modem_TEST max-error-count = 10 device = /dev/ttyACM0 pin = keepalive = 60 Any ideas ? Is there a way I can emulate a serial port for that modem ? Thanks
Using ttyACM0 as modem
Hi all, I'm trying a new modem usb. When I plugit into my linux box, I get from kernel: Jun 1 14:43:37 db kernel: cdc_acm 4-1:1.0: ttyACM0: USB ACM device If I set this tty to kannel.conf and launch kannel, I get in the logs: 2007-06-01 14:46:24 [5106] [7] INFO: AT2[Modem_TEST]: opening device 2007-06-01 14:46:24 [5106] [7] DEBUG: AT2[Modem_TEST]: device opened 2007-06-01 14:46:25 [5106] [7] DEBUG: AT2[Modem_TEST]: device opened 2007-06-01 14:46:25 [5106] [7] INFO: AT2[Modem_TEST]: speed set to 57600 2007-06-01 14:46:25 [5106] [7] DEBUG: AT2[Modem_TEST]: -- ^M 2007-06-01 14:46:27 [5106] [7] DEBUG: AT2[Modem_TEST]: -- AT^M 2007-06-01 14:46:31 [5106] [7] DEBUG: AT2[Modem_TEST]: -- AT^M 2007-06-01 14:46:35 [5106] [7] DEBUG: AT2[Modem_TEST]: -- AT^M 2007-06-01 14:46:39 [5106] [7] INFO: AT2[Modem_TEST]: closing device 2007-06-01 14:46:39 [5106] [7] INFO: AT2[Modem_TEST]: opening device 2007-06-01 14:46:39 [5106] [7] DEBUG: AT2[Modem_TEST]: device opened 2007-06-01 14:46:40 [5106] [7] DEBUG: AT2[Modem_TEST]: device opened 2007-06-01 14:46:40 [5106] [7] INFO: AT2[Modem_TEST]: speed set to 38400 2007-06-01 14:46:40 [5106] [7] DEBUG: AT2[Modem_TEST]: -- ^M 2007-06-01 14:46:42 [5106] [7] DEBUG: AT2[Modem_TEST]: -- AT^M 2007-06-01 14:46:46 [5106] [7] DEBUG: AT2[Modem_TEST]: -- AT^M 2007-06-01 14:46:50 [5106] [7] DEBUG: AT2[Modem_TEST]: -- AT^M 2007-06-01 14:46:54 [5106] [7] INFO: AT2[Modem_TEST]: closing device 2007-06-01 14:46:54 [5106] [7] INFO: AT2[Modem_TEST]: opening device 2007-06-01 14:46:54 [5106] [7] DEBUG: AT2[Modem_TEST]: device opened 2007-06-01 14:46:55 [5106] [7] DEBUG: AT2[Modem_TEST]: device opened 2007-06-01 14:46:55 [5106] [7] INFO: AT2[Modem_TEST]: speed set to 19200 My configuration for that modem is: group = smsc smsc = at smsc-id = Modem_TEST max-error-count = 10 device = /dev/ttyACM0 pin = keepalive = 60 Any ideas ? Is there a way I can emulate a serial port for that modem ? Thanks
Re: Using ttyACM0 as modem
Hi Alejandro, I did it also with minicom but the modem seems not to respond to AT commands at all. I mean, that pretty strange... it seems like the modem does not start the AT interface... Julien Alejandro Guerrieri ha scritto: Try opening the port with minicom and closing without resetting just after launching Kannel. I don't know why, but Kannel seems to have problems initializing the modem for the first time and that may fix it. Regards, Alejandro On 6/1/07, Julien Buratto [EMAIL PROTECTED] wrote: Hi all, I'm trying a new modem usb. When I plugit into my linux box, I get from kernel: Jun 1 14:43:37 db kernel: cdc_acm 4-1:1.0: ttyACM0: USB ACM device If I set this tty to kannel.conf and launch kannel, I get in the logs: 2007-06-01 14:46:24 [5106] [7] INFO: AT2[Modem_TEST]: opening device 2007-06-01 14:46:24 [5106] [7] DEBUG: AT2[Modem_TEST]: device opened 2007-06-01 14:46:25 [5106] [7] DEBUG: AT2[Modem_TEST]: device opened 2007-06-01 14:46:25 [5106] [7] INFO: AT2[Modem_TEST]: speed set to 57600 2007-06-01 14:46:25 [5106] [7] DEBUG: AT2[Modem_TEST]: -- ^M 2007-06-01 14:46:27 [5106] [7] DEBUG: AT2[Modem_TEST]: -- AT^M 2007-06-01 14:46:31 [5106] [7] DEBUG: AT2[Modem_TEST]: -- AT^M 2007-06-01 14:46:35 [5106] [7] DEBUG: AT2[Modem_TEST]: -- AT^M 2007-06-01 14:46:39 [5106] [7] INFO: AT2[Modem_TEST]: closing device 2007-06-01 14:46:39 [5106] [7] INFO: AT2[Modem_TEST]: opening device 2007-06-01 14:46:39 [5106] [7] DEBUG: AT2[Modem_TEST]: device opened 2007-06-01 14:46:40 [5106] [7] DEBUG: AT2[Modem_TEST]: device opened 2007-06-01 14:46:40 [5106] [7] INFO: AT2[Modem_TEST]: speed set to 38400 2007-06-01 14:46:40 [5106] [7] DEBUG: AT2[Modem_TEST]: -- ^M 2007-06-01 14:46:42 [5106] [7] DEBUG: AT2[Modem_TEST]: -- AT^M 2007-06-01 14:46:46 [5106] [7] DEBUG: AT2[Modem_TEST]: -- AT^M 2007-06-01 14:46:50 [5106] [7] DEBUG: AT2[Modem_TEST]: -- AT^M 2007-06-01 14:46:54 [5106] [7] INFO: AT2[Modem_TEST]: closing device 2007-06-01 14:46:54 [5106] [7] INFO: AT2[Modem_TEST]: opening device 2007-06-01 14:46:54 [5106] [7] DEBUG: AT2[Modem_TEST]: device opened 2007-06-01 14:46:55 [5106] [7] DEBUG: AT2[Modem_TEST]: device opened 2007-06-01 14:46:55 [5106] [7] INFO: AT2[Modem_TEST]: speed set to 19200 My configuration for that modem is: group = smsc smsc = at smsc-id = Modem_TEST max-error-count = 10 device = /dev/ttyACM0 pin = keepalive = 60 Any ideas ? Is there a way I can emulate a serial port for that modem ? Thanks
Re: Using ttyACM0 as modem
: available ** PhoneStatus: ready 16:00:30,79 SIM: Ready ** USIM: NO 16:00:30,79 Mobile: SIEMENS ** Model: MC75 ** Version: REVISION 03.010 16:00:30,79 FlexVersion: ** DSP SW Version: 16:00:30,79 IMSI: 222014100703021 ** IMEI: 355634003847156 16:00:30,79 ChannelStatus: ** szPhoneNumber: 33ANONYMIZED 16:00:30,79 Network registered : normal 16:00:30,79 Operator: LongName TIM (IT), ShortName NO, HomeNetworkNumber 22201 16:00:30,79 SignalStrength 15 ** BatteryLevel 100 ** GPRS attached: YES 16:00:30,79 ServiceCenter: +393359609600 ** DeliveryReport YES 16:00:30,79 SMS SIM Read 0/Used 0/Capa 55 16:00:30,79 SMS ME Read 0/Used 0/Capa 25 16:00:30,79 PBK SIM First 1/Last 250/Used 14, SizeName 14, SizeNumber 20 16:00:30,79 PBK ME First 1/Last 250/Used 0, SizeName 21, SizeNumber 20 16:00:30,79 AdvancedServices: YES ** ChangePin: YES ** ActivatePin: YES ** ChangeBand: NO 16:00:30,79 RingerManage: NO ** MasterReset: NO ** MasterClear: NO ** Barring: YES Forwarding YES 16:00:30,79 OperatorList: YES ** ChoiceBand : Automatic, Current 2 (EDGE) 16:00:30,89 lineDrop 16:00:30,92 Modem MC75 EDGE USB Modem #2 State ConnectTapi = 5 16:00:31,10 CallBack Tapi entry: dwMsg = 2, hDevice = 00010057 dwParam1 = 4000 dwParam2 = 0001 16:00:31,10 CallBack Tapi entry: dwMsg = 2, hDevice = 00010057 dwParam1 = 0001 dwParam2 = 16:00:31,10 CallBack Tapi entry: dwMsg = 12, hDevice = dwParam1 = 0001008A dwParam2 = 16:00:31,14 Modem MC75 EDGE USB Modem #2 State ConnectTapi = 8 Alejandro Guerrieri ha scritto: Try opening the port with minicom and closing without resetting just after launching Kannel. I don't know why, but Kannel seems to have problems initializing the modem for the first time and that may fix it. Regards, Alejandro On 6/1/07, Julien Buratto [EMAIL PROTECTED] wrote: Hi all, I'm trying a new modem usb. When I plugit into my linux box, I get from kernel: Jun 1 14:43:37 db kernel: cdc_acm 4-1:1.0: ttyACM0: USB ACM device If I set this tty to kannel.conf and launch kannel, I get in the logs: 2007-06-01 14:46:24 [5106] [7] INFO: AT2[Modem_TEST]: opening device 2007-06-01 14:46:24 [5106] [7] DEBUG: AT2[Modem_TEST]: device opened 2007-06-01 14:46:25 [5106] [7] DEBUG: AT2[Modem_TEST]: device opened 2007-06-01 14:46:25 [5106] [7] INFO: AT2[Modem_TEST]: speed set to 57600 2007-06-01 14:46:25 [5106] [7] DEBUG: AT2[Modem_TEST]: -- ^M 2007-06-01 14:46:27 [5106] [7] DEBUG: AT2[Modem_TEST]: -- AT^M 2007-06-01 14:46:31 [5106] [7] DEBUG: AT2[Modem_TEST]: -- AT^M 2007-06-01 14:46:35 [5106] [7] DEBUG: AT2[Modem_TEST]: -- AT^M 2007-06-01 14:46:39 [5106] [7] INFO: AT2[Modem_TEST]: closing device 2007-06-01 14:46:39 [5106] [7] INFO: AT2[Modem_TEST]: opening device 2007-06-01 14:46:39 [5106] [7] DEBUG: AT2[Modem_TEST]: device opened 2007-06-01 14:46:40 [5106] [7] DEBUG: AT2[Modem_TEST]: device opened 2007-06-01 14:46:40 [5106] [7] INFO: AT2[Modem_TEST]: speed set to 38400 2007-06-01 14:46:40 [5106] [7] DEBUG: AT2[Modem_TEST]: -- ^M 2007-06-01 14:46:42 [5106] [7] DEBUG: AT2[Modem_TEST]: -- AT^M 2007-06-01 14:46:46 [5106] [7] DEBUG: AT2[Modem_TEST]: -- AT^M 2007-06-01 14:46:50 [5106] [7] DEBUG: AT2[Modem_TEST]: -- AT^M 2007-06-01 14:46:54 [5106] [7] INFO: AT2[Modem_TEST]: closing device 2007-06-01 14:46:54 [5106] [7] INFO: AT2[Modem_TEST]: opening device 2007-06-01 14:46:54 [5106] [7] DEBUG: AT2[Modem_TEST]: device opened 2007-06-01 14:46:55 [5106] [7] DEBUG: AT2[Modem_TEST]: device opened 2007-06-01 14:46:55 [5106] [7] INFO: AT2[Modem_TEST]: speed set to 19200 My configuration for that modem is: group = smsc smsc = at smsc-id = Modem_TEST max-error-count = 10 device = /dev/ttyACM0 pin = keepalive = 60 Any ideas ? Is there a way I can emulate a serial port for that modem ? Thanks
Re: problem running kannel
Piyush shingala ha scritto: Hello Friends, I am using CentOS 4 and I tried to install Kannel it was successful but not been able to find file. problem /root/init.d/kannel start not file found could any one help me or provide the step by step installation procedure for kannel? -- Piyush Shingala +91-9824290345 try to execute ./bearerbox /PATH_TO_YOUR_KANNEL.CONF_FILE
smpp: mysql delivery pdu message has no destination - dest_addr_ton needed ?
Actually I'm using a new carrier and it seems that the DLR is inserted correctly but not retrived propertly from kannel in the dlr_mysql.c In kannel logs, upon smpp deliver_sm, I get all the parsing of the PDU and at the end kannel reports: 2007-03-16 16:34:29 [10563] [6] DEBUG: DLR[mysql]: Looking for DLR smsc=mysmsc, ts=101748338, dst=0, type=2 But in the PDU I can read: 2007-03-16 16:34:29 [10563] [6] DEBUG: dest_addr_ton: 0 = 0x 2007-03-16 16:34:29 [10563] [6] DEBUG: dest_addr_npi: 0 = 0x 2007-03-16 16:34:29 [10563] [6] DEBUG: destination_addr: 393356359515 Infact usually I get: 2007-01-25 00:34:44 [2346] [7] DEBUG: DLR[mysql]: Looking for DLR smsc=myothersmsc, ts=250107004454, dst=00393356359515, type=2 So, the question is: do you think I should set the dest_addr_ton and npd in a special way to get the dst correctly parsed ? Thanks Julien PS: The smsc I'm using reports to be smpp 3.4 standard compliant PPS: I know that kannel does not use, in its original version, the dst value to retrive the DLR from the database, but using only the TS can be a problem when using EMI smsc that has no unique sms id
Re: The most compatible udh header for multipart sms-messages
Hi Tomi, wouldn't be bad to connect a generic usb modem to kannel with a serial cable, send the sms from the 6300 to the modem and then trace the binary message you received ? This could maybe answer the question: wich header the 6300 sends ? Let me know what you think Julien Tomi Tukiainen ha scritto: Hello, I'm sending multipart messages through Kannel by using udh-header and thus not depending upon Kannel's multipart sms handling. This is to avoid problems that I mentioned in my earlier post. The problem with my current udh-header is that the message can not be received by all phones. Instead some phones (eg. nokia 3110) seem to silently ignore my multipart sms-messages. But When I send a multipart SMS from my nokia 6300i to such a phone it works. I haven't yet found a phone that can't receive multipart sms-messages from my 6300i. Thus it seems that the multipart sms-message that have been sent from my phone are more compatible than multipart messages with this udh-header. Does anybody know what I can try to change in my udh-header to make it work with more phones? Here is my udh-header code my $udh=%0B%05%04%1A%FF%1A%FF%00%03%00%0'.$sms_part_count.'%0'.$sms_part_number; And thus for 1st and 2nd part the udh value will be: %0B%05%04%1A%FF%1A%FF%00%03%00%02%01 %0B%05%04%1A%FF%1A%FF%00%03%00%02%02 Thanks, Tomi Tukiainen
sendota can't use DLR ?
Quote strange, when using sendota to send come otas, DLR seems not to work (I don't mean I get a failure dlr, I mean dlr-mask and dlr-url seems to be ignored) When I do it manually with sendsms and use a binary message I get the DLRs any suggestions ? Cheers J
Re: Calendar format
You need to send V-Card for contacts and V-Calendars for appointments via SMS J Stuart Steele ha scritto: Whats the format for sending an appointment via sms, which a user can save into their mobile phone calendar ( if they have one) If there is any documentation around anywhere then please point me at that first, sorry to trouble anyone Stuart -- Stuart Steele StuWeb Race Management Services www.stuweb.co.uk http://www.stuweb.co.uk
Sending settings: DLR and costs
I'm sending some settings (using the ota interface of kannel 1.4.1) and I've noticed that adding dlr-mask and dlr-url no DLR status at all are returned. Am I missing something or it's just a feature not implemented to have DLRs on sendota ? How could I undestand how many SMS will be sent for each configuration ? will the gateway provide split into N° messages or I just need to guess ? Thanks J
Re: Problems with DLR delivery through HTTP
Can you post the complete HTTP request you are sending to kannel ? Adriaan Mol ha scritto: Hi, We're looking for some help/advice with a Kannel problem we've just encountered. We're sending a message by posting a HTTP request to kannel from our PHP-software. Here we include the dlr-url and dlr-mask parameters (both urlencoded). But for some reason the smsbox.log tells it could not deliver the DLR report because the URL doesn't start with `http://' nor `https://'. But we are sure that we posted the DLR how it should be posted. We tried it by using 'http://www.mollie.nl/a/dlr/dr.php'. The weird thing is, when we try using another host, for example 'http://www.apple.com/a/dlr/dr.php' it just works without a problem. We can't figure out what the problem is. This is what we receive in the smsbox.log: 2007-01-24 18:58:21 [31356] [3] INFO: smsbox: Got HTTP request /cgi-bin/sendsms from 82.94.255.119 2007-01-24 18:58:21 [31356] [3] INFO: sendsms used by m0lli3 2007-01-24 18:58:21 [31356] [3] INFO: sendsms sender:m0lli3:Mollie (82.94.255.119) to:31649139210 msg:TEST:ROUTE:1075 2007-01-24 18:58:22 [31357] [4] INFO: Starting delivery report m0lli3 from Mollie 2007-01-24 18:58:22 [31493] [9] ERROR: URL /a/dlr/dr.php doesn't start with `http://' nor `https://' 2007-01-24 18:58:22 [31493] [9] ERROR: Couldn't send request to /a/dlr/dr.phpp Can someone help us here? Thanks in advance. Best regards, Adriaan LinkedIn: http://www.linkedin.com/in/adriaan
Re: EMI/UCP
Rolandow ha scritto: Hi all, Does kannel support EMI/UCP? Or does anybody know a piece of software that does? Hope I don't have to develop a daemon myself :-) Thanks in advance! Kind regards, Roland. The Netherlands. It does have client libs to send sms,not server to receive. Julien
SQLBOX saves DLR to file store and not dlr-storage
SQLBOX saves DLR-MO messages to file storage and not to dlr-storage set in the kannel.conf file. Does anyone patched this saving DLR-MO to mysql ? Thanks Julien
Re: SQLBOX saves DLR to file store and not dlr-storage
So where can I find it ? I've sqlbox-standalone version downloaded not so long time ago.. How can I tell kannel to procell dlr-urls ? Thanks Julien Collin, Stephane ha scritto: C'est fait... Stéphane Collin Conseiller Grand Montréal CGI T: 514-873-1101 p.3298 1350 René-Lévesque Ouest, 20ième étage Montréal (Québec) H3G 1T4 http://www.cgi.com Avis de confidentialité : ce message peut contenir des renseignements confidentiels appartenant exclusivement au Groupe CGI Inc. ou à ses filiales. Si vous n'êtes pas le destinataire indiqué ou prévu dans ce message (ou responsable de livrer ce message à la personne indiquée ou prévue) ou si vous pensez que ce message vous a été adressé par erreur, vous ne pouvez pas utiliser ou reproduire ce message, ni le livrer à quelqu'un d'autre. Dans ce cas, vous devez le détruire et vous êtes prié d'avertir l'expéditeur en répondant au courriel. -Message d'origine- De : Julien Buratto [mailto:[EMAIL PROTECTED] Envoyé : Wednesday, November 22, 2006 11:03 AM À : users@kannel.org Objet : SQLBOX saves DLR to file store and not dlr-storage SQLBOX saves DLR-MO messages to file storage and not to dlr-storage set in the kannel.conf file. Does anyone patched this saving DLR-MO to mysql ? Thanks Julien
Re: [commercial] SMS Provider wanted in India
abhishek jain ha scritto: Hi, I currently is located in bangalore india and do require a SMS provider which should be very reliable with the best rates for smaller quantities at start. The SMS use will not be for marketing purpose but for company use. Help required in this respect. -- Regards , jain So you want: - reliability quality - low cost - no setups - no required pre-payments suggestion: install kannel and setup you own phone with it. Julien
Re: Sms (or URL) on RING
Please try to init your modem adding ;+CLIP=1 to your init-string command line This should activate CLIP Julien Iain Dooley ha scritto: On Thu, 9 Nov 2006, Thomas G�ttgens wrote: Hello Iain, we use a similar setup to accept requests for sending out alert SMS batches. Caller calls an extension on our pbx from a registered phone and triggers the sending of a couple of SMS to a predefined list. Clients use this predominantly to trigger alert sms by dialup devices. don't even try to fiddle with modems or direct serial scripting here, use an asterisk server for the call processing like we did. In our case the calls are not even sent in via ISDN cards, but via SIP directly from the phone company, although ISDN would work as well. We simply pick up the ring, compare with our CLI-Database and trigger Kannel to send the SMS. For details in the setup, you can contact me. the big issue here is that my client needs to be able to deploy a server in a large number of geographically disparate locations, so it cannot be assumed that he has call termination where the server is deployed necessarily. and you can't get CLI information on international numbers, so i need to have the dial in happening on a GSM modem, that way we just have to deploy the server with a modem+sim card attached and we can do CLI in almost any country with a lot less hassle. i don't actually know asterisk that well, but i'm assuming that i can't just plug a GSM modem into asterisk ... cheers iain -- Best regards, Thomasmailto:[EMAIL PROTECTED]
Sms (or URL) on RING
If any of you is interested in developing with me a kind of ring service on demand, please contact me. This should work like you have a smsc modem connected to kannel, when that modem receives a call from a phone, it sends and SMS or better call a service URL Anyone ? Cheers Julien
Sqlbox: mysql Can't connect to external db ? (Error 111)
I haven't read many docs, however if you are trying to connect to an external database (not localhost) with mysql, please remember to include: port = 3306 in your group = mysql-connection I know that 3306 is the default mysql port, but without this will not work for me. Cheers Julien
Sqlbox: my experience
Really great! Downloaded from the http://www.kannel.org/~mconte/sqlbox/ Unpacked, launched bootstrap program, installed a few required components with yum (automake and libtool) and the compiled successfully. Made some edits on the provided conf file under example and launched sqlbox with the just edited conf file. An INSERT in the db caused the sms to leave and get delivered to the phone. My server is: Fedora Core release 4 (Stentz) Kannel bearerbox version `1.4.1' MySQL 4.1.20 The only things missing in the INSTALL file is the fact that sqlbox will automagically create the two send_sms and sent_sms tables in the db accordingly, however, really entusiast on it. Will try to deploy on production use asap and let you know. Cheers Julien
Re: Sending Unicode Message Using Sqlbox
Does your SQL server supports unicode chars ? Have you tryed simply putting inside the db the unicode char not as a code ? I mean: if you want to put the double quot char just insert in the db the char and not %22 and not 22 Cavit Dolgun ha scritto: Hi All, I am trying to send arabic message using sqlbox but no chance so far. When i send it through http simply i put the http://host:port/cgi-bin/sendsms?userntext=%06%61coding=2 http://host:port/cgi-bin/sendsms?userntext=%06%61coding=2 I receive the messages on my phone as arabic. When I insert an English text like “hello” into the sqlbox db to the msgdate field I receive it fine. I want to send Unicode (Arabic) message the same way by inserting the data into sqlbox send_sms table. I have already tried putting 0661 or %06%61 into the msgdata field and set the coding to 2 but I receive some squares on my phone as the message. Is there a way to do this? Thanks, Cavit Dolgun -- Il messaggio risulta non infetto. Linkas Srl
Re: WAP Push Over CDMA Network
Wouldn't be a good idea to post the diff ? Julien Rene Kluwen ha scritto: I am not sure if you are from the same company as the person as I spoke to earlier this week. Also I am not sure if your problem is the same as I have solved for another company earlier this year. But I do have a patch for Kannel that solves sending WAP Pushes over sending CDMA networks. It works by replacing a submit_sm pdu with a data_sm pdu. It is open source. Let me know if you are interested to try it out. Rene Kluwen Chimit -Original Message- *From:* Fajar [mailto:[EMAIL PROTECTED] *Sent:* dinsdag 17 oktober 2006 6:11 *To:* Kannel Users *Subject:* WAP Push Over CDMA Network Hello there, I'm connecting to SMPP server our telco company. We would like to send wap push that will be sent into cdma mobile. Is Kannel supporting this feature? I'm settingup ppg, but it seems the wap push never get sent into mobile? Maybe someone willing helping me out. Thanks Fajar -- Il messaggio risulta non infetto. Linkas Srl
SyncSetting remeber to encode password
To those who want to test SyncML Settings to be sent over sms, please note that the XML must be urlencoded as documented but the XML won't work if the password in the XML Cred is not base64encoded, so this is the working XML to be sent urlencoded: SyncSettings Version1.0/Version HostAddrhttp://syncml.server.com/HostAddr RemoteDB CTTypetext/x-vcard/CTType CTVer2.1/CTVer URIcontact/URI NameAddress Book/Name /RemoteDB NameSynchonization/Name Auth AuthLevel1/AuthLevel AuthScheme1/AuthScheme Usernameyourusername/Username CredcGFzc3dvcmQ=/Cred /Auth /SyncSettings This is the encoded version: %3CSyncSettings%3E%0A%3CVersion%3E1.0%3C%2FVersion%3E%0A%3CHostAddr%3Ehttp%3A%2F%2Fsyncml.server.com%3C%2FHostAddr%3E%0A%3CRemoteDB%3E%0A%3CCTType%3Etext%2Fx-vcard%3C%2FCTType%3E%0A%3CCTVer%3E2.1%3C%2FCTVer%3E%0A%3CURI%3Econtact%3C%2FURI%3E%0A%3CName%3EAddress+Book%3C%2FName%3E%0A%3C%2FRemoteDB%3E%0A%3CName%3ESynchonization%3C%2FName%3E%0A%3CAuth%3E%0A%3CAuthLevel%3E1%3C%2FAuthLevel%3E%0A%3CAuthScheme%3E1%3C%2FAuthScheme%3E%0A%3CUsername%3Eyourusername%3C%2FUsername%3E%0A%3CCred%3EcGFzc3dvcmQ%3D%3C%2FCred%3E%0A%3C%2FAuth%3E%0A%3C%2FSyncSettings%3E Enjoy Julien
Compiling upon mysql 4
Upon compiling on fedora core 4 the rpm sources for the stable released 26/9 I'm getting gcc -D_REENTRANT=1 -I. -Igw -D_XOPEN_SOURCE=600 -D_BSD_SOURCE -I/usr/include/libxml2 -I/usr/include/mysql -o gw/dlr_mysql.o -c gw/dlr_mysql.c In file included from /usr/include/mysql/mysql.h:62, from gw/dlr_mysql.c:74: /usr/include/mysql/my_list.h:32: error: conflicting types for ‘list_delete’ ./gwlib/list.h:179: error: previous declaration of ‘list_delete’ was here make: *** [gw/dlr_mysql.o] Error 1 Does anyone has compiled on mysql 4 ? Does anyone suggests to use mysql 3.23 ? Cheers Julien
Re: Compiling upon mysql 4
Enver ALTIN ha scritto: On Fri, 2006-10-06 at 09:05 -0400, Marcelo Aguila wrote: I had the same problem using version 1.4.0. The solution is to rename the function list_delete for gw_list_delete (there is a patch for that) or you can start using cvs version of kannel, what is periodically actualized. 1.4.1 is out, this is not needed. You are right, thank you. 1.4.1 compiles on fedora core 4 does anyone interested in a vmware virtual appliance with precompiled kannel ? :D Julien
Re: compile kannel
If I were in you, I would just write a conf file then try to start the bearerbox with that, then you will be able to copy the executables wherever you want to. J alaa a ha scritto: iwant to compile kannel using cygwin 2.510.2.2 to use kannel in Windows XP. i compiled it with some error messages . then i had bearerbox.exe,smsbox.exe,wapbox.exe this is what i had when execute ./cofigure: $ ./configure loading cache ./config.cache Configuring for Kannel gateway version 1.4.0 ... Running system checks ... checking host system type... i686-pc-cygwin checking for gcc... gcc checking whether the C compiler (gcc ) works... yes checking whether the C compiler (gcc ) is a cross-compiler... no checking whether we are using GNU C... yes checking whether gcc accepts -g... yes checking for a BSD compatible install... /usr/bin/install -c checking for ranlib... ranlib checking for bison... no checking for byacc... no checking for flex... lex checking for yywrap in -ll... no checking for convert... /cygdrive/d/PROGRA~1/Borland/CBUILD~1/Bin/convert checking for perl... /cygdrive/d/Program Files/Rational/Rational Test/perl checking size of short... 2 checking size of int... 4 checking size of long... 4 checking size of long long... 8 checking for log in -lm... yes checking for accept in -lsocket... no checking for inet_ntoa in -lnsl... no checking for inet_ntop in -lresolv... no checking for inet_ntop in -lbind... no checking for pthread_exit in -lpthread... yes checking for libiconv in -liconv... yes checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for sys/ioctl.h... yes checking for sys/time.h... yes checking for sys/types.h... yes checking for unistd.h... yes checking for sys/poll.h... yes checking for pthread.h... yes checking for getopt.h... yes checking for syslog.h... yes checking for iconv.h... yes checking for zlib.h... yes checking for execinfo.h... no checking for stdlib.h... yes checking for sys/socket.h... yes checking for sys/sockio.h... no checking for net/if.h... yes checking for netinet/in.h... yes checking for gettimeofday... yes checking for select... yes checking for socket... yes checking for strdup... yes checking for getopt_long... yes checking for localtime_r... yes checking for gmtime_r... yes checking for backtrace... no checking for srandom... yes checking for getopt... yes checking for gethostbyname_r... no checking for gethostbyname... yes checking for socklen_t in sys/socket.h... yes checking for getopt in stdio.h... no checking for getopt in unistd.h... yes checking for regex.h... yes checking for regcomp... yes Checking for POSIX threads support ... checking for working pthreads... yes checking for pthread_spinlock support... no checking for pthread_rwlock support... yes checking for sem_init in -lrt... no checking for semaphore support... yes Checking for libxml2 support ... checking for xml2-config... /usr/bin/xml2-config checking libxml version... 2.6.26 Configuring for PCRE support ... checking whether to compile with PCRE support... disabled Configuring DocBook support ... checking for jade... no checking for jadetex... no checking for pdfjadetex... no checking for dvips... no checking for fig2dev... no checking for convert... /cygdrive/d/PROGRA~1/Borland/CBUILD~1/Bin/convert checking for /usr/lib/sgml/stylesheet/dsssl/docbook/nwalsh/html/docbook.dsl... n o checking for /usr/lib/sgml/stylesheets/nwalsh-modular/html/docbook.dsl... no checking for /usr/share/sgml/docbook/dsssl-stylesheets-1.59/html/docbook.dsl... no checking for /usr/share/sgml/docbook/dsssl-stylesheets-1.77/html/docbook.dsl... no checking for /usr/share/sgml/docbook/dsssl-stylesheets/html/docbook.dsl... no checking for /usr/share/sgml/docbook/dsssl/modular/html/docbook.dsl... no checking for /usr/local/lib/sgml/stylesheet/dsssl/docbook/nwalsh/html/docbook.ds l... no checking for /usr/local/lib/sgml/stylesheets/nwalsh-modular/html/docbook.dsl... no checking for /usr/local/share/sgml/docbook/dsssl-stylesheets-1.59/html/docbook.d sl... no checking for /usr/local/share/sgml/docbook/dsssl-stylesheets-1.77/html/docbook.d sl... no checking for /usr/local/share/sgml/docbook/dsssl-stylesheets/html/docbook.dsl... no checking for /usr/local/share/sgml/docbook/dsssl/modular/html/docbook.dsl... no checking for /usr/lib/sgml/stylesheet/dsssl/docbook/nwalsh/print/docbook.dsl... no checking for /usr/lib/sgml/stylesheets/nwalsh-modular/print/docbook.dsl... no checking for /usr/share/sgml/docbook/dsssl-stylesheets-1.59/print/docbook.dsl... no checking for /usr/share/sgml/docbook/dsssl-stylesheets-1.77/print/docbook.dsl... no checking for /usr/share/sgml/docbook/dsssl-stylesheets/print/docbook.dsl... no checking for /usr/share/sgml/docbook/dsssl/modular/print/docbook.dsl... no checking for
Re: Wbxml sending to phones
Hi Stipe,
I've seen the ota configuration for APN settings in the docs but I
need to configure the SyncML settings.
Actually I'm doing so with Nokia/SonyEricsson Smart Messaging 7.0
documentation, but that docs has been deprecated and oma cp 1.1.
Does kannel has a wbxml - bin compiler already ?
Julien
Stipe Tolj ha scritto:
Julien Buratto wrote:
Hi,
I'm trying to send some ota configuration to some phones.
What I'm doing is to set the UDH as %06%05%04%C3%4C%C0%02
Then I've encoded my XML (which follows) with the xml2wbxml too from
wbxml library.
then I used bin2hex to convert each char created by the tool to it's hex
rappresentation and added % in front of it then passed to kannel as the
text of the message.
This is quite rought but fast, does anyone see any thing wrong in this
procedure or something could be done in a different way ?
My phone make buzz on speakers but do not react
I haven't reviewed the details so far, but question: why not use the OMA
OTA support that we have *already* inside CVS HEAD version?
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
---
Wbxml sending to phones
Hi, I'm trying to send some ota configuration to some phones. What I'm doing is to set the UDH as %06%05%04%C3%4C%C0%02 Then I've encoded my XML (which follows) with the xml2wbxml too from wbxml library. then I used bin2hex to convert each char created by the tool to it's hex rappresentation and added % in front of it then passed to kannel as the text of the message. This is quite rought but fast, does anyone see any thing wrong in this procedure or something could be done in a different way ? My phone make buzz on speakers but do not react Thanks J PS: XML file ?xml version=1.0? !DOCTYPE wap-provisioningdoc PUBLIC -//WAPFORUM//DTD PROV 1.0//EN http://www.wapforum.org/DTD/prov.dtd; wap-provisioningdoc characteristic type=APPLICATION parm name=APPID value=w5/ parm name=NAME value=Sync Server/ parm name=ADDR value=http://www.syncserver.com:8080/sync/ parm name=TO-NAPID value=INTERNET/ characteristic type=APPAUTH parm name=AAUTHTYPE value=HTTP-DIGEST/ parm name=AAUTHNAME value=name/ parm name=AAUTHSECRET value=secret/ /characteristic characteristic type=APPAUTH parm name=AAUTHLEVEL value=APPSRV/ parm name=AAUTHTYPE value=DIGEST/ parm name=AAUTHNAME value=servername/ parm name=AAUTHSECRET value=serversecret/ /characteristic characteristic type=RESOURCE parm name=URI value=./Contacts/ parm name=NAME value=Contact DB/ parm name=AACCEPT value=text/x-vcard,text/vcard/ parm name=AAUTHTYPE value=DIGEST/ parm name=AAUTHNAME value=databasename/ parm name=AAUTHSECRET value=databasesecret/ /characteristic characteristic type=RESOURCE parm name=URI value=./Calendar/ parm name=NAME value=Calendar DB/ parm name=AACCEPT value=text/x-vcalendar,text/vcal/ /characteristic /characteristic characteristic type=NAPDEF parm name=NAPID value=INTERNET/ parm name=BEARER value=GSM-GPRS/ parm name=NAME value=Internet/ parm name=NAP-ADDRESS value=internet/ parm name=NAP-ADDRTYPE value=APN/ /characteristic /wap-provisioningdoc PS: After encoding to wbxml, convert to hex and added % to each couple of hex numbers: %03%0b%6a%09%49%4e%54%45%52%4e%45%54%00%45%c6%00%01%55%01%87%36%00%00%06%03%77%35%00%01%87%07%06%03%53%79%6e%63%20%53%65%72%76%65%72%00%01%87%00%01%34%00%00%06%03%68%74%74%70%3a%2f%2f%77%77%77%2e%73%79%6e%63%73%65%72%76%65%72%2e%63%6f%6d%3a%38%30%38%30%2f%73%79%6e%63%00%01%87%22%06%83%00%01%c6%00%01%57%01%87%33%00%00%06%9d%01%87%00%01%31%00%00%06%03%6e%61%6d%65%00%01%87%00%01%32%00%00%06%03%73%65%63%72%65%74%00%01%01%c6%00%01%57%01%87%30%00%00%06%00%01%8d%01%87%33%00%00%06%00%01%93%01%87%31%00%00%06%03%73%65%72%76%65%72%6e%61%6d%65%00%01%87%00%01%32%00%00%06%03%73%65%72%76%65%72%73%65%63%72%65%74%00%01%01%c6%00%01%59%01%87%3a%00%00%06%03%2e%2f%43%6f%6e%74%61%63%74%73%00%01%87%07%06%03%43%6f%6e%74%61%63%74%20%44%42%00%01%87%00%01%2e%00%00%06%03%74%65%78%74%2f%78%2d%76%63%61%72%64%00%00%01%90%03%74%65%78%74%2f%76%63%61%72%64%00%01%87%33%00%00%06%00%01%93%01%87%31%00%00%06%03%64%61%74%61%62%61%73%65%6e%61%6d%65%00%01%87%00%01%32%00%00%06%03%64%61%74%61%62%61%73%65%73%65%63%72%6 5%74%00%01%01%c6%00%01%59%01%87%3a%00%00%06%03%2e%2f%43%61%6c%65%6e%64%61%72%00%01%87%07%06%03%43%61%6c%65%6e%64%61%72%20%44%42%00%01%87%00%01%2e%00%00%06%03%74%65%78%74%2f%78%2d%76%63%61%6c%65%6e%64%61%72%00%00%01%90%03%74%65%78%74%2f%76%63%61%6c%00%01%01%01%c6%00%00%55%01%87%11%06%83%00%01%87%10%06%ab%01%87%07%06%03%49%6e%74%65%72%6e%65%74%00%01%87%08%06%03%69%6e%74%65%72%6e%65%74%00%01%87%09%06%89%01%01%01
Re: Problem with splitted SMS messages
Splitted SMS needs some additional char to get re-joined at destination phone, this limits the nr of chars in each message to a little lower than 160. Dividing each message is not automagically done as I know. J Matti Koljonen ha scritto: Hi, I would like to send SMS messages max. length of 480 characters splitted into 1-3 short messages. When I send message smaller than 160 charactes I get response “Sent.” If I send message length between 160 and 306 character I get response “Sent. Message splits: 2”. That’s ok. But If I send message length between 307 and 320 character I get response “Sent. Message splits: 3”. Why it’s splitted to three messages instead of two? It also seems that messages shorten than 459 characters are spliited correctly to three short messages but messages larger than 459 are splitted to four messages. Is it possible to configure Kannel so that messages with length between 0-160 are sent as one message, length between 160-320 are splitted to two messages and length between 320-480 are splitted to three short messages? That’s problem because I assume that I have to pay for each splitted message Thanks for any help! -mattijko
Re: Massive SMS sent
Yo guys this is an english-spoken list :-D Let us understand your thoughts :-D J Chronis N. ha scritto: Giasou Kiriako, Efraristo poly gia to minima. Twra, stelvo sto kannel 10.000 sms / 20 secs. Ala ithela va do ama baroussa va ta stelvo pio rgrigora. Ama 8eis, grapsta sta englika pio efkola eivai gia ollous. Niko. - Original Message - *From:* Kiriakos Tsourapas mailto:[EMAIL PROTECTED] *To:* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] *Sent:* Tuesday, June 20, 2006 8:43 AM *Subject:* RE: Massive SMS sent Καλημέρα Είδα το μήνυμά σου στη λίστα του kannel. Δουλεύω καιρό τώρα πάνω σε μαζικές αποστολές. Αν μου πεις τι ακριβώς θες να κάνεις ίσως μπορώ να βοηθήσω. Πως θες να τα στείλεις τα SMS? το kannel με τι το συνδέεις ? Θες να γίνεται αυτόματα η αποστόλή ή κάποιος χρήστης θα τα στέλνει όταν θέλει ? Εγώ έχω φτιάξει μια εφαρμογή η οποία συνδέεται απευθείας σε SMSCs (CIMD ή SMPP) για μαζικές αποστολές μηνυμάτων (μιλάω για εκατομύρια όχι χιλιάδες). Φιλικά Κυριάκος Τσουράπας
Re: Error receiving DLRs
Does the DLR gets correctly saved in the db ?
Fourat Zouari ha scritto:
Hello all,
Am having errors in my logs saying that i have problems receiving DLRs,
let's let this bearerbox log talk about it :
-- BEGIN PASTING
2006-06-20 16:57:08 [801] [6] DEBUG: DLR[pgsql]: Adding DLR
smsc=SMPP-01-BB, ts=5B03, src=17700, dst=28347018, mask=31, boxc=
2006-06-20 16:57:08 [801] [6] DEBUG: sql: INSERT INTO dlr (smsc, date,
soa, da, service, url, mask, boxcid, status) VALUES ('SMPP-01-BB',
'5B03', '17700', '28347018', 'tt', '
http://localhost/servlets/recdlr.php?status=%danswer=%Ats=%tmsgid=165574
http://localhost/servlets/recdlr.php?status=%danswer=%Ats=%tmsgid=165574',
'31', '', '0');
2006-06-20 16:57:08 [801] [6] DEBUG: SMSC[SMPP-01-BB]: creating DLR message
2006-06-20 16:57:08 [801] [6] DEBUG: SMSC[SMPP-01-BB]: DLR =
http://localhost/servlets/recdlr.php?status=%danswer=%Ats=%tmsgid=165574
http://localhost/servlets/recdlr.php?status=%danswer=%Ats=%tmsgid=165574
2006-06-20 16:57:08 [837] [20] DEBUG: send_msg: sending msg to box:
127.0.0.1 http://127.0.0.1
2006-06-20 16:57:08 [837] [20] DEBUG: boxc_sender: sent message to
127.0.0.1 http://127.0.0.1
2006-06-20 16:57:08 [836] [19] DEBUG: boxc_receiver: got ack
2006-06-20 16:57:09 [797] [2] DEBUG: HTTP: Creating HTTPClient for
`127.0.0.1'.
2006-06-20 16:57:09 [797] [2] DEBUG: HTTP: Created HTTPClient area
0x8258b28.
2006-06-20 16:57:09 [798] [3] DEBUG: sql: SELECT count(*) FROM dlr;
2006-06-20 16:57:09 [798] [3] DEBUG: HTTP: Destroying HTTPClient area
0x8258b28.
2006-06-20 16:57:09 [798] [3] DEBUG: HTTP: Destroying HTTPClient for
`127.0.0.1'.
2006-06-20 16:57:09 [797] [2] DEBUG: HTTP: Creating HTTPClient for
`127.0.0.1'.
2006-06-20 16:57:09 [797] [2] DEBUG: HTTP: Created HTTPClient area
0x8258b28.
2006-06-20 16:57:09 [798] [3] DEBUG: sql: SELECT count(*) FROM dlr;
2006-06-20 16:57:09 [798] [3] DEBUG: HTTP: Destroying HTTPClient area
0x8258b28.
2006-06-20 16:57:09 [798] [3] DEBUG: HTTP: Destroying HTTPClient for
`127.0.0.1'.
2006-06-20 16:57:15 [803] [8] DEBUG: SMPP[SMPP-01-TZ]: Sending enquire link:
2006-06-20 16:57:15 [803] [8] DEBUG: SMPP PDU 0x8258d48 dump:
2006-06-20 16:57:15 [803] [8] DEBUG: type_name: enquire_link
2006-06-20 16:57:15 [803] [8] DEBUG: command_id: 21 = 0x0015
2006-06-20 16:57:15 [803] [8] DEBUG: command_status: 0 = 0x
2006-06-20 16:57:15 [803] [8] DEBUG: sequence_number: 23806 = 0x5cfe
2006-06-20 16:57:15 [803] [8] DEBUG: SMPP PDU dump ends.
2006-06-20 16:57:15 [803] [8] DEBUG: SMPP[SMPP-01-TZ]: Got PDU:
2006-06-20 16:57:15 [803] [8] DEBUG: SMPP PDU 0x8258d48 dump:
2006-06-20 16:57:15 [803] [8] DEBUG: type_name: enquire_link_resp
2006-06-20 16:57:15 [803] [8] DEBUG: command_id: 2147483669 = 0x8015
2006-06-20 16:57:15 [803] [8] DEBUG: command_status: 0 = 0x
2006-06-20 16:57:15 [803] [8] DEBUG: sequence_number: 23806 = 0x5cfe
2006-06-20 16:57:15 [803] [8] DEBUG: SMPP PDU dump ends.
2006-06-20 16:57:16 [802] [7] DEBUG: SMPP[SMPP-01-BB]: Got PDU:
2006-06-20 16:57:16 [802] [7] DEBUG: SMPP PDU 0x8258d48 dump:
2006-06-20 16:57:16 [802] [7] DEBUG: type_name: deliver_sm
2006-06-20 16:57:16 [802] [7] DEBUG: command_id: 5 = 0x0005
2006-06-20 16:57:16 [802] [7] DEBUG: command_status: 0 = 0x
2006-06-20 16:57:16 [802] [7] DEBUG: sequence_number: 180 = 0x00b4
2006-06-20 16:57:16 [802] [7] DEBUG: service_type: NULL
2006-06-20 16:57:16 [802] [7] DEBUG: source_addr_ton: 2 = 0x0002
2006-06-20 16:57:16 [802] [7] DEBUG: source_addr_npi: 1 = 0x0001
2006-06-20 16:57:16 [802] [7] DEBUG: source_addr: 28347018
2006-06-20 16:57:16 [802] [7] DEBUG: dest_addr_ton: 2 = 0x0002
2006-06-20 16:57:16 [802] [7] DEBUG: dest_addr_npi: 1 = 0x0001
2006-06-20 16:57:16 [802] [7] DEBUG: destination_addr: 17700
2006-06-20 16:57:16 [802] [7] DEBUG: esm_class: 4 = 0x0004
2006-06-20 16:57:16 [802] [7] DEBUG: protocol_id: 0 = 0x
2006-06-20 16:57:16 [802] [7] DEBUG: priority_flag: 0 = 0x
2006-06-20 16:57:16 [802] [7] DEBUG: schedule_delivery_time: NULL
2006-06-20 16:57:16 [802] [7] DEBUG: validity_period: NULL
2006-06-20 16:57:16 [802] [7] DEBUG: registered_delivery: 0 = 0x
2006-06-20 16:57:16 [802] [7] DEBUG: replace_if_present_flag: 0 =
0x
2006-06-20 16:57:16 [802] [7] DEBUG: data_coding: 0 = 0x
2006-06-20 16:57:16 [802] [7] DEBUG: sm_default_msg_id: 0 = 0x
2006-06-20 16:57:16 [802] [7] DEBUG: sm_length: 12 = 0x000c
2006-06-20 16:57:16 [802] [7] DEBUG: short_message: 5B03 201
2006-06-20 16:57:16 [802] [7] DEBUG: SMPP PDU dump ends.
2006-06-20 16:57:16 [802] [7] DEBUG: SMPP[SMPP-01-BB] handle_pdu, got DLR
2006-06-20 16:57:16 [802] [7] DEBUG: SMPP[SMPP-01-BB]: Couldnot parse
DLR string sscanf way,fallback to old way. Please report!
2006-06-20 16:57:16 [802] [7] ERROR: SMPP[SMPP-01-BB]: got
Re: Error receiving DLRs
However it seems you don't receive the ID of the message from the smpp
server ?
J
Fourat Zouari ha scritto:
Hello all,
Am having errors in my logs saying that i have problems receiving DLRs,
let's let this bearerbox log talk about it :
-- BEGIN PASTING
2006-06-20 16:57:08 [801] [6] DEBUG: DLR[pgsql]: Adding DLR
smsc=SMPP-01-BB, ts=5B03, src=17700, dst=28347018, mask=31, boxc=
2006-06-20 16:57:08 [801] [6] DEBUG: sql: INSERT INTO dlr (smsc, date,
soa, da, service, url, mask, boxcid, status) VALUES ('SMPP-01-BB',
'5B03', '17700', '28347018', 'tt', '
http://localhost/servlets/recdlr.php?status=%danswer=%Ats=%tmsgid=165574
http://localhost/servlets/recdlr.php?status=%danswer=%Ats=%tmsgid=165574',
'31', '', '0');
2006-06-20 16:57:08 [801] [6] DEBUG: SMSC[SMPP-01-BB]: creating DLR message
2006-06-20 16:57:08 [801] [6] DEBUG: SMSC[SMPP-01-BB]: DLR =
http://localhost/servlets/recdlr.php?status=%danswer=%Ats=%tmsgid=165574
http://localhost/servlets/recdlr.php?status=%danswer=%Ats=%tmsgid=165574
2006-06-20 16:57:08 [837] [20] DEBUG: send_msg: sending msg to box:
127.0.0.1 http://127.0.0.1
2006-06-20 16:57:08 [837] [20] DEBUG: boxc_sender: sent message to
127.0.0.1 http://127.0.0.1
2006-06-20 16:57:08 [836] [19] DEBUG: boxc_receiver: got ack
2006-06-20 16:57:09 [797] [2] DEBUG: HTTP: Creating HTTPClient for
`127.0.0.1'.
2006-06-20 16:57:09 [797] [2] DEBUG: HTTP: Created HTTPClient area
0x8258b28.
2006-06-20 16:57:09 [798] [3] DEBUG: sql: SELECT count(*) FROM dlr;
2006-06-20 16:57:09 [798] [3] DEBUG: HTTP: Destroying HTTPClient area
0x8258b28.
2006-06-20 16:57:09 [798] [3] DEBUG: HTTP: Destroying HTTPClient for
`127.0.0.1'.
2006-06-20 16:57:09 [797] [2] DEBUG: HTTP: Creating HTTPClient for
`127.0.0.1'.
2006-06-20 16:57:09 [797] [2] DEBUG: HTTP: Created HTTPClient area
0x8258b28.
2006-06-20 16:57:09 [798] [3] DEBUG: sql: SELECT count(*) FROM dlr;
2006-06-20 16:57:09 [798] [3] DEBUG: HTTP: Destroying HTTPClient area
0x8258b28.
2006-06-20 16:57:09 [798] [3] DEBUG: HTTP: Destroying HTTPClient for
`127.0.0.1'.
2006-06-20 16:57:15 [803] [8] DEBUG: SMPP[SMPP-01-TZ]: Sending enquire link:
2006-06-20 16:57:15 [803] [8] DEBUG: SMPP PDU 0x8258d48 dump:
2006-06-20 16:57:15 [803] [8] DEBUG: type_name: enquire_link
2006-06-20 16:57:15 [803] [8] DEBUG: command_id: 21 = 0x0015
2006-06-20 16:57:15 [803] [8] DEBUG: command_status: 0 = 0x
2006-06-20 16:57:15 [803] [8] DEBUG: sequence_number: 23806 = 0x5cfe
2006-06-20 16:57:15 [803] [8] DEBUG: SMPP PDU dump ends.
2006-06-20 16:57:15 [803] [8] DEBUG: SMPP[SMPP-01-TZ]: Got PDU:
2006-06-20 16:57:15 [803] [8] DEBUG: SMPP PDU 0x8258d48 dump:
2006-06-20 16:57:15 [803] [8] DEBUG: type_name: enquire_link_resp
2006-06-20 16:57:15 [803] [8] DEBUG: command_id: 2147483669 = 0x8015
2006-06-20 16:57:15 [803] [8] DEBUG: command_status: 0 = 0x
2006-06-20 16:57:15 [803] [8] DEBUG: sequence_number: 23806 = 0x5cfe
2006-06-20 16:57:15 [803] [8] DEBUG: SMPP PDU dump ends.
2006-06-20 16:57:16 [802] [7] DEBUG: SMPP[SMPP-01-BB]: Got PDU:
2006-06-20 16:57:16 [802] [7] DEBUG: SMPP PDU 0x8258d48 dump:
2006-06-20 16:57:16 [802] [7] DEBUG: type_name: deliver_sm
2006-06-20 16:57:16 [802] [7] DEBUG: command_id: 5 = 0x0005
2006-06-20 16:57:16 [802] [7] DEBUG: command_status: 0 = 0x
2006-06-20 16:57:16 [802] [7] DEBUG: sequence_number: 180 = 0x00b4
2006-06-20 16:57:16 [802] [7] DEBUG: service_type: NULL
2006-06-20 16:57:16 [802] [7] DEBUG: source_addr_ton: 2 = 0x0002
2006-06-20 16:57:16 [802] [7] DEBUG: source_addr_npi: 1 = 0x0001
2006-06-20 16:57:16 [802] [7] DEBUG: source_addr: 28347018
2006-06-20 16:57:16 [802] [7] DEBUG: dest_addr_ton: 2 = 0x0002
2006-06-20 16:57:16 [802] [7] DEBUG: dest_addr_npi: 1 = 0x0001
2006-06-20 16:57:16 [802] [7] DEBUG: destination_addr: 17700
2006-06-20 16:57:16 [802] [7] DEBUG: esm_class: 4 = 0x0004
2006-06-20 16:57:16 [802] [7] DEBUG: protocol_id: 0 = 0x
2006-06-20 16:57:16 [802] [7] DEBUG: priority_flag: 0 = 0x
2006-06-20 16:57:16 [802] [7] DEBUG: schedule_delivery_time: NULL
2006-06-20 16:57:16 [802] [7] DEBUG: validity_period: NULL
2006-06-20 16:57:16 [802] [7] DEBUG: registered_delivery: 0 = 0x
2006-06-20 16:57:16 [802] [7] DEBUG: replace_if_present_flag: 0 =
0x
2006-06-20 16:57:16 [802] [7] DEBUG: data_coding: 0 = 0x
2006-06-20 16:57:16 [802] [7] DEBUG: sm_default_msg_id: 0 = 0x
2006-06-20 16:57:16 [802] [7] DEBUG: sm_length: 12 = 0x000c
2006-06-20 16:57:16 [802] [7] DEBUG: short_message: 5B03 201
2006-06-20 16:57:16 [802] [7] DEBUG: SMPP PDU dump ends.
2006-06-20 16:57:16 [802] [7] DEBUG: SMPP[SMPP-01-BB] handle_pdu, got DLR
2006-06-20 16:57:16 [802] [7] DEBUG: SMPP[SMPP-01-BB]: Couldnot parse
DLR string sscanf way,fallback to old way. Please report!
2006-06-20 16:57:16
Re: USB Modem supported ?
Leonard ha scritto: Could not say for sure, but if it supports AT command set and is CDC-ACM complaint it should work.. (on linux box anyways.) Can you please mail me off list with the details. we require a stack of modems as well Yep it works! :D I have some problems with my Redhat 9 USB support, but it works perfect on Fedora Core 3. Note: on that redhat 9 I always had usb problems, so is not modem-related trouble. If you need some, write me directly. Cheers J PS: I'm not an hardware reseller tooh! :D
Re: j2me kannel: Sms to different port
Loïc Minier ha scritto:
On Thu, Jun 08, 2006, Julien Buratto wrote:
You need a source port, and I don't think you need to add %00 at the
end. The typical WAP PUSH UDH is 0605040B8423F0, where 0B84 is the
destination port (2948) and 23F0 the source port (9200).
I've tested that with a source port too, seems doesn't work either.
I confirm it works for us to wake J2ME apps with messages which are
logged as follows:
[msg:5:48656C6C6F] [udh:7:060504C35323F0]
Hi I'm keep on testing.
I've changed my smsc to a real modem and not a emi/uci smsc to make some
tests.
Now the sms arrives to the phone, if the j2me application is not
listening, the message goes to the Inbox folder of my phone.
However, my j2me application has this condition:
if (msg instanceof TextMessage) {
// does things
} else {
// send alert
}
The message gets to the j2me now, but the aler is thrown, so this means
the sms I do receive is not textual but binary.
That is BinaryMessageImplementation and not TextMessage.
Any clue on how to force kannel to send the message as a textual ?
Thanks
Julien
Re: j2me kannel: Sms to different port
Loïc Minier ha scritto: On Thu, Jun 08, 2006, Linkas wrote: So I did my UDH as %06%05%04 %40%74 %00 Where the %40%74 is 16500 in HEX. You need a source port, and I don't think you need to add %00 at the end. The typical WAP PUSH UDH is 0605040B8423F0, where 0B84 is the destination port (2948) and 23F0 the source port (9200). I've tested that with a source port too, seems doesn't work either. :-( J (the DLR gets back delivered as other tests)
Re: Re: j2me kannel: Sms to different port
Funny, my UDH without the last %00 works, if I use the %00 it give malformed. With your UDH give no errors. However my application does not intercept the message even if listening to port 16664... Should I add something else as a parameter like coding or wmi or similar ? Thanks J Oscar Elfving ha scritto: udh=%06%05%04%41%18%00%00 This is how my UDH-string looks for sending to my java app at 16664 :) Hope this helps! You seem to be missing the terminating %00. Regards, Oscar Elfving On Jun 8, 2006, at 9:43 AM, Linkas wrote: I think you misunderstood my question or my question was not clear: the problem is not an HTTP port to call for kannel url, but special ports used in sms to get different services. Example: RTTTL (ringtones) normally go to phone in a special port - in this way the phone can understand it's not a standard sms but a ringtone. Cheers. Julien
Re: j2me kannel: Sms to different port
Loïc Minier ha scritto: On Thu, Jun 08, 2006, Julien Buratto wrote: You need a source port, and I don't think you need to add %00 at the end. The typical WAP PUSH UDH is 0605040B8423F0, where 0B84 is the destination port (2948) and 23F0 the source port (9200). I've tested that with a source port too, seems doesn't work either. I confirm it works for us to wake J2ME apps with messages which are logged as follows: [msg:5:48656C6C6F] [udh:7:060504C35323F0] Are you adding some other parameters to the http call ? Do you encode the content in text= or you leave it as normal text like hello ? Any particular conf in the kannel.conf file ? It's strange, I can send any type of message (sync, wap) but not these one... J
Re: j2me kannel: Sms to different port
Loïc Minier ha scritto: On Thu, Jun 08, 2006, Julien Buratto wrote: Are you adding some other parameters to the http call ? Usual parameters, sender, recipient, nothing special apart from text and udh. Any particular conf in the kannel.conf file ? No. It's strange, I can send any type of message (sync, wap) but not these one... Might your provider filter out SM to non-standard ports? I've tested a java client and with high-number ports such as 65XXX is not working. I've tryed with 3334 and works in java, but not kannel. My kannel url is: http://10.100.10.5:13013/cgi-bin/invia?username=XXXpassword=XXXto=%2B393477657857from=%2B393477657857text=%63%69%61%6Fudh=%06%05%04%0D%06%00%00 still not working :( Julien
USB Modem supported ?
Hello, till now I used Fastrack serial modems, but costs are getting high and serial interfaces are getting hard to find and replicators have high costs. I've found a chinese GPRS modem sold in USB with a bundled antenna - it says it supports: Tri-band EGSM900/1800/1900, GPRS multi-slot class 8, AT command set GSM 07.05, 07.07, Does anyone knows if kannel can connect to this ? Thanks for anyone. Julien
Re: How to support Thai language?
Is that set of chars also included in UTF-8 ? J Kavuri Prasad ha scritto: Dear All, I am facing a problem in transmitting thai message.. Is there any special encoding for thai dialect. I think thai language is format is TIS-620 (Windows). My modile phone supports Thai dialect. Thanks to the group. -- Thanks, Prasad Kavuri Software Consultant Mobile Lifestyle Berhad Unit F10 Block 3 (2320) Century Square 63000 Cyberjaya Malaysia. Tel: +60 3 8318 6691 Fax:+60 3 8318 7760 HP: +60 12 927 4711
Re: WAP push - please fill in the blank
Simon C. Wex ha scritto: I have an SMPP connection to an SMSC that I currently use for an application that acts as an SMS chat server. I'd like to add mobile content delivery (ringtones, wallpapers etc) to the application. As I understand it, the best way to do this is via WAP push. So, sending the WAP Push message shouldn't be too complicated, but this is where my expertise (and I use that term lightly) ends. I know I need to set up a WAP gateway (Kannel seems like the best choice) that will then proxy the request/response with my webserver. How do I get the wap server addressed? Is it simply over DNS? Do the carriers use the internet for communicating with WAP gateways? No this is not true. A wap gateway is not mandatory, and I think is really too much. You can also send a simple wap-push using a binary SMS as a Service Indication. In the wap-push message you will need to set the URL for the content. The URL can be a normal webserver with good wap headers. The wapbox could be useful if you don't know how to create a wap-push binary sms. If someone could explain this or point me to that document that I've been unable to find I would be eternally grateful. Cheers, Simon. Check for http://www.google.it/search?hl=itq=sms+%22service+indication%22+wap+pushbtnG=Cercameta= you will find some google links to read, this one can be a point to start: http://discussion.forum.nokia.com/forum/archive/index.php/t-7278.html J PS: I've not tested the binary in that link, it's just to let you understand what I mean.
PANIC: Memory allocation failed
In these days I'm getting this error: 2006-04-06 08:07:24 [18269] [8] PANIC: Memory allocation failed 2006-04-06 08:07:24 [18269] [8] PANIC: System error 12: Cannot allocate memory 2006-04-06 08:07:25 [18269] [8] PANIC: 0x80caed2 2006-04-06 08:07:25 [18269] [8] PANIC: 0x80bf9d0 2006-04-06 08:07:25 [18269] [8] PANIC: 0x80cbfcd 2006-04-06 08:07:25 [18269] [8] PANIC: 0x80cc42a 2006-04-06 08:07:25 [18269] [8] PANIC: 0x805ee33 2006-04-06 08:07:25 [18269] [8] PANIC: 0x8075abc 2006-04-06 08:07:25 [18269] [8] PANIC: 0x806328c 2006-04-06 08:07:25 [18269] [8] PANIC: 0x8057a78 2006-04-06 08:07:25 [18269] [8] PANIC: 0x8057cfd 2006-04-06 08:07:25 [18269] [8] PANIC: 0x8071db6 2006-04-06 08:07:25 [18269] [8] PANIC: 0x80752a5 2006-04-06 08:07:25 [18269] [8] PANIC: 0x80c0b98 2006-04-06 08:07:25 [18269] [8] PANIC: 0x4007e484 2006-04-06 08:07:25 [18269] [8] PANIC: 0x420df147 Can anyone suggest anything ? J
SMPP: again query_sm for DLR
I've seen that a lot of people was wondering if it was possible for kannel to query the smpp server asking for the dlr status of a specific id. When I set the DLR-MASK the dlr is correctly saved in the database, but my operator ask me to do a query_sm for the id in order to fetch the DLR status. Anyone has a patch for this ? Ideal would be that for every enquire_link kannel send, also query the dlr database and query_sm for stored dlrs... Thanks J
Re: Sim storage SM cannot parse all memory locations
It seems to be an error of all old Wavecom modems with old firmware. New firmware return correct strings, however modifying a little the code, also newer can work fine. J Julien Buratto ha scritto: I have a simple problem but important to me: If there is a problem with my modem and messages are stored to Sim Memory, then Kannel seems not able to read them. To read the messages, I must put the SIM in my phone and read them from the SIM Memory. Maybe there is an issue with my conf, or maybe I'm using Can anyone suggest what to check for ? Thank Julien First of all my configuration: group = smsc smsc = at smsc-id = Modem #sim-buffering = true modemtype = wavecom device = /dev/ttyS4 my-number = +39HIDDEN pin = speed = 9600 keepalive = 120 group = modems id = wavecom name = Wavecom message-storage = SM init-string = AT+CNMI=1,2,0,0,0;+CLIP=1 detect-string = WAVECOM reset-string = AT+CFUN=1 keepalive-cmd = AT+CREG?;+CSQ And second here what it happens: 2006-03-26 03:48:24 [28708] [8] DEBUG: AT2[Modem]: device opened 2006-03-26 03:48:24 [28708] [8] INFO: AT2[Modem]: init device 2006-03-26 03:48:24 [28708] [8] INFO: AT2[Modem]: speed set to 9600 2006-03-26 03:48:24 [28708] [8] DEBUG: AT2[Modem]: -- ATZ^M 2006-03-26 03:48:24 [28708] [8] DEBUG: AT2[Modem]: -- OK 2006-03-26 03:48:24 [28708] [8] DEBUG: AT2[Modem]: -- AT^M 2006-03-26 03:48:24 [28708] [8] DEBUG: AT2[Modem]: -- AT 2006-03-26 03:48:24 [28708] [8] DEBUG: AT2[Modem]: -- OK 2006-03-26 03:48:24 [28708] [8] DEBUG: AT2[Modem]: -- ATF^M 2006-03-26 03:48:24 [28708] [8] DEBUG: AT2[Modem]: -- ATF 2006-03-26 03:48:25 [28708] [8] DEBUG: AT2[Modem]: -- OK 2006-03-26 03:48:25 [28708] [8] DEBUG: AT2[Modem]: -- ATE0^M 2006-03-26 03:48:25 [28708] [8] DEBUG: AT2[Modem]: -- ATE0 2006-03-26 03:48:25 [28708] [8] DEBUG: AT2[Modem]: -- OK 2006-03-26 03:48:25 [28708] [8] DEBUG: AT2[Modem]: -- AT+IFC=2,2^M 2006-03-26 03:48:25 [28708] [8] DEBUG: AT2[Modem]: -- OK 2006-03-26 03:48:25 [28708] [8] DEBUG: AT2[Modem]: -- AT+CPIN?^M 2006-03-26 03:48:25 [28708] [8] DEBUG: AT2[Modem]: -- +CPIN: READY 2006-03-26 03:48:36 [28708] [8] DEBUG: AT2[Modem]: -- AT+CMGF=0^M 2006-03-26 03:48:36 [28708] [8] DEBUG: AT2[Modem]: -- OK 2006-03-26 03:48:36 [28708] [8] DEBUG: AT2[Modem]: -- AT+CSMS=?^M 2006-03-26 03:48:36 [28708] [8] DEBUG: AT2[Modem]: -- +CSMS: (0) 2006-03-26 03:48:36 [28708] [8] DEBUG: AT2[Modem]: -- OK 2006-03-26 03:48:36 [28708] [8] DEBUG: AT2[Modem]: -- AT+CNMI=1,2,0,0,0;+CLIP=1^M 2006-03-26 03:48:36 [28708] [8] DEBUG: AT2[Modem]: -- OK 2006-03-26 03:48:36 [28708] [8] DEBUG: AT2[Modem]: -- AT+CPMS=SM^M 2006-03-26 03:48:36 [28708] [8] DEBUG: AT2[Modem]: -- +CPMS: 30,30 2006-03-26 03:48:36 [28708] [8] DEBUG: AT2[Modem]: -- OK 2006-03-26 03:48:36 [28708] [8] INFO: AT2[Modem]: AT SMSC successfully opened. 2006-03-26 03:48:38 [28708] [8] DEBUG: AT2[Modem]: -- AT+CREG?;+CSQ^M 2006-03-26 03:48:38 [28708] [8] DEBUG: AT2[Modem]: -- +CREG: 0,1 2006-03-26 03:48:38 [28708] [8] DEBUG: AT2[Modem]: -- +CSQ: 16,0 2006-03-26 03:48:38 [28708] [8] DEBUG: AT2[Modem]: -- OK 2006-03-26 03:48:38 [28708] [8] DEBUG: AT2[Modem]: -- AT+CPMS?^M 2006-03-26 03:48:38 [28708] [8] DEBUG: AT2[Modem]: -- +CPMS: SM,30,30 2006-03-26 03:48:38 [28708] [8] DEBUG: AT2[Modem]: -- OK 2006-03-26 03:48:38 [28708] [8] DEBUG: AT2[Modem]: couldn't parse all memory locations : 2:''. 2006-03-26 03:48:38 [28708] [8] DEBUG: AT2[Modem]: memory check error 2006-03-26 03:48:38 [28708] [8] INFO: AT2[Modem]: closing device 2006-03-26 03:48:38 [28708] [8] ERROR: AT2[Modem]: Couldn't connect (retrying in 10 seconds). 2006-03-26 03:48:48 [28708] [8] INFO: AT2[Modem]: opening device 2006-03-26 03:48:48 [28708] [8] DEBUG: AT2[Modem]: device opened 2006-03-26 03:48:48 [28708] [8] DEBUG: AT2[Modem]: device opened 2006-03-26 03:48:48 [28708] [8] INFO: AT2[Modem]: init device 2006-03-26 03:48:48 [28708] [8] INFO: AT2[Modem]: speed set to 9600
Sim storage SM cannot parse all memory locations
I have a simple problem but important to me: If there is a problem with my modem and messages are stored to Sim Memory, then Kannel seems not able to read them. To read the messages, I must put the SIM in my phone and read them from the SIM Memory. Maybe there is an issue with my conf, or maybe I'm using Can anyone suggest what to check for ? Thank Julien First of all my configuration: group = smsc smsc = at smsc-id = Modem #sim-buffering = true modemtype = wavecom device = /dev/ttyS4 my-number = +39HIDDEN pin = speed = 9600 keepalive = 120 group = modems id = wavecom name = Wavecom message-storage = SM init-string = AT+CNMI=1,2,0,0,0;+CLIP=1 detect-string = WAVECOM reset-string = AT+CFUN=1 keepalive-cmd = AT+CREG?;+CSQ And second here what it happens: 2006-03-26 03:48:24 [28708] [8] DEBUG: AT2[Modem]: device opened 2006-03-26 03:48:24 [28708] [8] INFO: AT2[Modem]: init device 2006-03-26 03:48:24 [28708] [8] INFO: AT2[Modem]: speed set to 9600 2006-03-26 03:48:24 [28708] [8] DEBUG: AT2[Modem]: -- ATZ^M 2006-03-26 03:48:24 [28708] [8] DEBUG: AT2[Modem]: -- OK 2006-03-26 03:48:24 [28708] [8] DEBUG: AT2[Modem]: -- AT^M 2006-03-26 03:48:24 [28708] [8] DEBUG: AT2[Modem]: -- AT 2006-03-26 03:48:24 [28708] [8] DEBUG: AT2[Modem]: -- OK 2006-03-26 03:48:24 [28708] [8] DEBUG: AT2[Modem]: -- ATF^M 2006-03-26 03:48:24 [28708] [8] DEBUG: AT2[Modem]: -- ATF 2006-03-26 03:48:25 [28708] [8] DEBUG: AT2[Modem]: -- OK 2006-03-26 03:48:25 [28708] [8] DEBUG: AT2[Modem]: -- ATE0^M 2006-03-26 03:48:25 [28708] [8] DEBUG: AT2[Modem]: -- ATE0 2006-03-26 03:48:25 [28708] [8] DEBUG: AT2[Modem]: -- OK 2006-03-26 03:48:25 [28708] [8] DEBUG: AT2[Modem]: -- AT+IFC=2,2^M 2006-03-26 03:48:25 [28708] [8] DEBUG: AT2[Modem]: -- OK 2006-03-26 03:48:25 [28708] [8] DEBUG: AT2[Modem]: -- AT+CPIN?^M 2006-03-26 03:48:25 [28708] [8] DEBUG: AT2[Modem]: -- +CPIN: READY 2006-03-26 03:48:36 [28708] [8] DEBUG: AT2[Modem]: -- AT+CMGF=0^M 2006-03-26 03:48:36 [28708] [8] DEBUG: AT2[Modem]: -- OK 2006-03-26 03:48:36 [28708] [8] DEBUG: AT2[Modem]: -- AT+CSMS=?^M 2006-03-26 03:48:36 [28708] [8] DEBUG: AT2[Modem]: -- +CSMS: (0) 2006-03-26 03:48:36 [28708] [8] DEBUG: AT2[Modem]: -- OK 2006-03-26 03:48:36 [28708] [8] DEBUG: AT2[Modem]: -- AT+CNMI=1,2,0,0,0;+CLIP=1^M 2006-03-26 03:48:36 [28708] [8] DEBUG: AT2[Modem]: -- OK 2006-03-26 03:48:36 [28708] [8] DEBUG: AT2[Modem]: -- AT+CPMS=SM^M 2006-03-26 03:48:36 [28708] [8] DEBUG: AT2[Modem]: -- +CPMS: 30,30 2006-03-26 03:48:36 [28708] [8] DEBUG: AT2[Modem]: -- OK 2006-03-26 03:48:36 [28708] [8] INFO: AT2[Modem]: AT SMSC successfully opened. 2006-03-26 03:48:38 [28708] [8] DEBUG: AT2[Modem]: -- AT+CREG?;+CSQ^M 2006-03-26 03:48:38 [28708] [8] DEBUG: AT2[Modem]: -- +CREG: 0,1 2006-03-26 03:48:38 [28708] [8] DEBUG: AT2[Modem]: -- +CSQ: 16,0 2006-03-26 03:48:38 [28708] [8] DEBUG: AT2[Modem]: -- OK 2006-03-26 03:48:38 [28708] [8] DEBUG: AT2[Modem]: -- AT+CPMS?^M 2006-03-26 03:48:38 [28708] [8] DEBUG: AT2[Modem]: -- +CPMS: SM,30,30 2006-03-26 03:48:38 [28708] [8] DEBUG: AT2[Modem]: -- OK 2006-03-26 03:48:38 [28708] [8] DEBUG: AT2[Modem]: couldn't parse all memory locations : 2:''. 2006-03-26 03:48:38 [28708] [8] DEBUG: AT2[Modem]: memory check error 2006-03-26 03:48:38 [28708] [8] INFO: AT2[Modem]: closing device 2006-03-26 03:48:38 [28708] [8] ERROR: AT2[Modem]: Couldn't connect (retrying in 10 seconds). 2006-03-26 03:48:48 [28708] [8] INFO: AT2[Modem]: opening device 2006-03-26 03:48:48 [28708] [8] DEBUG: AT2[Modem]: device opened 2006-03-26 03:48:48 [28708] [8] DEBUG: AT2[Modem]: device opened 2006-03-26 03:48:48 [28708] [8] INFO: AT2[Modem]: init device 2006-03-26 03:48:48 [28708] [8] INFO: AT2[Modem]: speed set to 9600
Backup SMSC
I would like to set a backup smsc, that is smsc A - primary smsc B - backup If A it's disconnected, then the SMS is routed to B Is it possible ? Second question) Is it possible to store the message in the store only after smsc B also has failed connection ? Third question) Is it possible to use the smsc B in the case smsc A is connected but giving errors (like authorization or some specific text in the response) ? Thanks J
Re: compatibility
Teo wrote: Hi at all! Support Kannel the mobile phone Nokia 6230i or Nokia 6600 or 3650? Thanks! Matteo What do U mean ? It's a strange question... J
Ringing modem
Hello, I've seen the bearbox log when I call the SIM number in the modem and the bearerbox react with a: 2005-10-25 13:08:41 [18384] [7] DEBUG: AT2[Modem]: -- RING Does anyone has implemented some code to send an HTTP call somewhere in case of a RING ? Thanks J
Re: Wap Push DLR Help
Kaushik wrote: RE: Wap Push DLR HelpHi I have added the following to kannel.conf : PPG core group ppg-smsbox-id = dlrbox smsbox group smsbox-id = dlrbox and also I have the headers in the POST message, but I still do not receive any notifications. Any other suggestion. Thanks I do have the same problem. I've tried inline variables, post variables, header variables.. nothing works. The only way it so send a binary SMS with smsbox with DLR without using PPG J
Re: [REPOST] DLR on wappushes ?
Alexander Malysh wrote: Hi, I believe you need to run smsbox in order to be able to process dlrs. Thanks, Alex I do have wapbox/ppg to convert XML files (SID and PAP) to binary. Then kannel, internally, give the binary to smsbox and sends it to the smsgateway. right ? :D J
[REPOST] DLR on wappushes ?
Hello I'm reposting this question because I have still no clue. 1) In the past I used binary SMS messages to send WAP-PUSHES in that way I was able to set dlr-mask=31 and a dlr-url and I have been receiving DLRs easily when the phone received the SMS. Sometimes the phone did not understand the wap-push message as a binary-message but the DLR arrived in any case. The 'call' was something like GET /sendsms? and I was using the bearerbox and the smsbox to send those binary sms. 2) Now I use the bearerbox, smsbox and wapbox and I send XML files to the wapbox using a POST but when I set the dlr-url and dlr-mark variables in the POST, I receive no DLRs at all. Does anyone know if the transcodification from XML to BINARY made by the wapbox do include dlr ? Thanks PS: I'm not interested to be notified if the wappush is understood or not, I just want to know if the wappush sms is got by the phone.
Re: [REPOST] DLR on wappushes ?
Mike Nwaogu wrote: Hello Julien, The position on your dlr-mask in the post command is what I think the issue is. Maybe you are true, but if I do POST /wappush HTTP/1.1 Host: 10.100.10.5:8080 Connection: close Content-Type: multipart/related; boundary=123321; type=application/xml Content-Length: 1174 username=ppgusernamepassword=ppgpassworddlr-mask=31dlr-url=[encoded url] XML ATTACHMENT CUT then the ppg says: HTTP/1.1 401 Unauthorized Server: Kannel/1.4.0 Content-Length: 32 Connection: close WWW-Authenticate: Basic realm=berlinzoowappush You must show your credentials. if I do: POST /wappush?username=ppgusernamepassword=ppgpassword HTTP/1.1 Host: 10.100.10.5:8080 Connection: close Content-Type: multipart/related; boundary=123321; type=application/xml Content-Length: 1174 username=ppgusernamepassword=ppgpassworddlr-mask=31dlr-url=[encoded url] (same as before but with user/pass in the POST url) the I get: HTTP/1.1 202 Accepted Perhaps you should URL ENCODE the content or relocate the dlr-mask parameter before the actual message. I could be wrong though but I think that's what it is. It is encoded,the protocol implementation seems ok to me, I think is something different related to the box receiving and decoding the paramenters. Cheers Julien --- Julien Buratto [EMAIL PROTECTED] wrote: Hello I'm reposting this question because I have still no clue. 1) In the past I used binary SMS messages to send WAP-PUSHES in that way I was able to set dlr-mask=31 and a dlr-url and I have been receiving DLRs easily when the phone received the SMS. Sometimes the phone did not understand the wap-push message as a binary-message but the DLR arrived in any case. The 'call' was something like GET /sendsms? and I was using the bearerbox and the smsbox to send those binary sms. 2) Now I use the bearerbox, smsbox and wapbox and I send XML files to the wapbox using a POST but when I set the dlr-url and dlr-mark variables in the POST, I receive no DLRs at all. Does anyone know if the transcodification from XML to BINARY made by the wapbox do include dlr ? Thanks PS: I'm not interested to be notified if the wappush is understood or not, I just want to know if the wappush sms is got by the phone. Mike Nwaogu Metro Technologies Resources Ltd. 48 Tunde Idiagbon Road, Tanke, Ilorin. __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com
