Sending SMS from a remote host !!!
Good morning; I have tried for a long period to find a solution but without succes. My problem is; when I send an SMS directly from kannel everything works fine, but if I access to kannel from a remote host belong to another network, I recieve the following error although the SMS was successfully sent. 2010-04-01 11:43:23 [24388] [9] DEBUG: HTTP: Opening connection to `196.xxx.xxx.xxx:80' (fd=28). 2010-04-01 11:43:23 [24388] [9] DEBUG: Socket connecting 2010-04-01 11:46:32 [24388] [8] DEBUG: Get info about connecting socket 2010-04-01 11:46:32 [24388] [8] DEBUG: Socket not connected 2010-04-01 11:46:32 [24388] [8] ERROR: Couldn't fetch http://196.xxx.xxx.xxx/uvtsms/plugin/gateway/kannel/dlr.php?type=16s lid=311uid=1 Please did anyone faced this problem ?? -- View this message in context: http://old.nabble.com/Sending-SMS-from-a-remote-host-%21%21%21-tp29008530p29008530.html Sent from the Kannel - User mailing list archive at Nabble.com.
Re: Sending SMS from a remote host !!!
Your remote host can not access the dlr.php script placed on your 196.xxx.xxx.xxx server so DLR can not routed until Kannel. BR, Emmanuel 2010/6/28 ramous ram...@live.fr Good morning; I have tried for a long period to find a solution but without succes. My problem is; when I send an SMS directly from kannel everything works fine, but if I access to kannel from a remote host belong to another network, I recieve the following error although the SMS was successfully sent. 2010-04-01 11:43:23 [24388] [9] DEBUG: HTTP: Opening connection to `196.xxx.xxx.xxx:80' (fd=28). 2010-04-01 11:43:23 [24388] [9] DEBUG: Socket connecting 2010-04-01 11:46:32 [24388] [8] DEBUG: Get info about connecting socket 2010-04-01 11:46:32 [24388] [8] DEBUG: Socket not connected 2010-04-01 11:46:32 [24388] [8] ERROR: Couldn't fetch http://196.xxx.xxx.xxx/uvtsms/plugin/gateway/kannel/dlr.php?type=16s lid=311uid=1 Please did anyone faced this problem ?? -- View this message in context: http://old.nabble.com/Sending-SMS-from-a-remote-host-%21%21%21-tp29008530p29008530.html Sent from the Kannel - User mailing list archive at Nabble.com. -- Emmanuel CHANSON Emmanuel Mobile Nouvelle-Calédonie: +687.77.35.02 Mobile France: +33 (0) 6.68.03.89.56 @email : emmanuelchan...@gmail.com
Re: Kannel drop MT's when bearerbox is stopped.
Hi, (2) Yes. You can have 2 sendsms-user accounts within the same smsbox. Additionally you can specify smsc=smsc-id in your push URL, plus there are several options in you sendsms-user configuration such as default-smsc, forced-smsc, etc. Read User's guide about them. BR, Nikos - Original Message - From: ahmad aburass To: Nikos Balkanas Cc: users@kannel.org Sent: Sunday, June 27, 2010 5:26 PM Subject: Re: Kannel drop MT's when bearerbox is stopped. Hello Nikos, Your assumption is correct, the * is not in the included config file its just in the email :). For your second point, when I deployed Kannel I wanted to have a distinct smsbox for each operator so that each operator MT's will be routed to its smsbox and smsc, and i searched the internet and found that its possible to do it this way, is there any other way to configure Kannel to achieve this approach. Regards, Ahmad. From: Nikos Balkanas nbalka...@gmail.com To: ahmad aburass ahmad1985_2...@yahoo.com; users@kannel.org Sent: Wed, June 23, 2010 7:04:40 PM Subject: Re: Kannel drop MT's when bearerbox is stopped. Hi, What is your included operator1.conf file? Is this your: *** operator1 smsbox config file I am surprised this thing works at all. 1) Comments are specified by #, not *. I presume this is just in the email. 2) If the included file is the operator1.conf you post, then you end up with a configuration with 2 core groups! It should panic. BR, Nikos - Original Message - From: ahmad aburass To: users@kannel.org Sent: Wednesday, June 23, 2010 3:20 PM Subject: Kannel drop MT's when bearerbox is stopped. Hello All, I know that there is a lot of links indicating that Kannel doesnt do it, but i face it in my deployment, so I thought maybe its something wrong in my configuration. I'm using bearerbox with multiple smsboxes attached to it, along side with sqlbox. I have configured store subsystem as well. Whenever i stop bearerbox, all the queued MT's are dropped from the store and i get a delivery report (NACK/no SMSC) in the access log: 2010-03-27 11:33:15 Receive DLR [SMSC:op1smsc] [SVC:] [ACT:] [BINF:] [FID:] [from:999] [to:9647809863597] [flags:-1:-1:-1:-1:16] [msg:12:NACK/no SMSC] [udh:0:] 2010-03-27 11:34:55 Receive DLR [SMSC:op1smsc] [SVC:] [ACT:] [BINF:] [FID:] [from:999] [to:9647807102585] [flags:-1:-1:-1:-1:16] [msg:12:NACK/no SMSC] [udh:0:] Below is the config I made, PS: Kannel version 1.4.3, sqlbox version 0.7.2: ***smskannel.conf: group = core admin-port = 1500 smsbox-port = 13001 dlr-storage = mysql sms-resend-retry = 9 store-location = /var/spool/kannel/kannel_mt.store store-type = file store-dump-freq = 600 include = /usr/local/kannel/etc/smsc_connections/operator1.conf group = smsbox bearerbox-host = 127.0.0.1 bearerbox-port = 13002 http-request-retry = 600 http-queue-delay = 60 smsbox-id = smsbox group = smsbox-route smsbox-id = smsbox smsc-id = op group = smsbox-route smsbox-id = operator1smsbox smsc-id = op1smsc shortcode = 999 ***sqlbox configuration group = sqlbox id = compsqlbox smsbox-id = sqlbox bearerbox-host = localhost bearerbox-port = 13001 smsbox-port = 13002 sql-log-table = sent_sms sql-insert-table = send_sms ***operator1 smsbox config file group = core admin-port = 1500 smsbox-port = 13001 dlr-storage = mysql sms-resend-retry = 9 store-location = /var/spool/kannel/kannel_mt.store store-type = file store-dump-freq = 600 group = smsbox bearerbox-host = 127.0.0.1 bearerbox-port = 13002 http-request-retry = 600 http-queue-delay = 60 smsbox-id = operator1smsbox group = smsbox-route smsbox-id = smsbox smsc-id = op group = smsbox-route smsbox-id = operator1smsbox smsc-id = op1smsc shortcode = 999 Appreciate your help. Ahmad Aburass,
Re: Kannel drop MT's when bearerbox is stopped.
Hi Nikos, Unfortunately I'm not using sendsms-user to push the MT's, I have sqlbox and the backend application posts the MT's to a cgi that inserts them in sqlbox send_sms table. please advise. Regards, Ahmad. From: Nikos Balkanas nbalka...@gmail.com To: ahmad aburass ahmad1985_2...@yahoo.com Cc: users@kannel.org Sent: Mon, June 28, 2010 3:04:24 PM Subject: Re: Kannel drop MT's when bearerbox is stopped. Hi, (2) Yes. You can have 2 sendsms-user accounts within the same smsbox. Additionally you can specify smsc=smsc-id in your push URL, plus there are several options in you sendsms-user configuration such as default-smsc, forced-smsc, etc. Read User's guide about them. BR, Nikos - Original Message - From: ahmad aburass To: Nikos Balkanas Cc: users@kannel.org Sent: Sunday, June 27, 2010 5:26 PM Subject: Re: Kannel drop MT's when bearerbox is stopped. Hello Nikos, Your assumption is correct, the * is not in the included config file its just in the email :). For your second point, when I deployed Kannel I wanted to have a distinct smsbox for each operator so that each operator MT's will be routed to its smsbox and smsc, and i searched the internet and found that its possible to do it this way, is there any other way to configure Kannel to achieve this approach. Regards, Ahmad. From: Nikos Balkanas nbalka...@gmail.com To: ahmad aburass ahmad1985_2...@yahoo.com; users@kannel.org Sent: Wed, June 23, 2010 7:04:40 PM Subject: Re: Kannel drop MT's when bearerbox is stopped. Hi, What is your included operator1.conf file? Is this your: *** operator1 smsbox config file I am surprised this thing works at all. 1) Comments are specified by #, not *. I presume this is just in the email. 2) If the included file is the operator1.conf you post, then you end up with a configuration with 2 core groups! It should panic. BR, Nikos - Original Message - From: ahmad aburass To: users@kannel.org Sent: Wednesday, June 23, 2010 3:20 PM Subject: Kannel drop MT's when bearerbox is stopped. Hello All, I know that there is a lot of links indicating that Kannel doesnt do it, but i face it in my deployment, so I thought maybe its something wrong in my configuration. I'm using bearerbox with multiple smsboxes attached to it, along side with sqlbox. I have configured store subsystem as well. Whenever i stop bearerbox, all the queued MT's are dropped from the store and i get a delivery report (NACK/no SMSC) in the access log: 2010-03-27 11:33:15 Receive DLR [SMSC:op1smsc] [SVC:] [ACT:] [BINF:] [FID:] [from:999] [to:9647809863597] [flags:-1:-1:-1:-1:16] [msg:12:NACK/no SMSC] [udh:0:] 2010-03-27 11:34:55 Receive DLR [SMSC:op1smsc] [SVC:] [ACT:] [BINF:] [FID:] [from:999] [to:9647807102585] [flags:-1:-1:-1:-1:16] [msg:12:NACK/no SMSC] [udh:0:] Below is the config I made, PS: Kannel version 1.4.3, sqlbox version 0.7.2: ***smskannel.conf: group = core admin-port = 1500 smsbox-port = 13001 dlr-storage = mysql sms-resend-retry = 9 store-location = /var/spool/kannel/kannel_mt.store store-type = file store-dump-freq = 600 include = /usr/local/kannel/etc/smsc_connections/operator1.conf group = smsbox bearerbox-host = 127.0.0.1 bearerbox-port = 13002 http-request-retry = 600 http-queue-delay = 60 smsbox-id = smsbox group = smsbox-route smsbox-id = smsbox smsc-id = op group = smsbox-route smsbox-id = operator1smsbox smsc-id = op1smsc shortcode = 999 ***sqlbox configuration group = sqlbox id = compsqlbox smsbox-id = sqlbox bearerbox-host = localhost bearerbox-port = 13001 smsbox-port = 13002 sql-log-table = sent_sms sql-insert-table = send_sms ***operator1 smsbox config file group = core admin-port = 1500 smsbox-port = 13001 dlr-storage = mysql sms-resend-retry = 9 store-location = /var/spool/kannel/kannel_mt.store store-type = file store-dump-freq = 600 group = smsbox bearerbox-host = 127.0.0.1 bearerbox-port = 13002 http-request-retry = 600 http-queue-delay = 60 smsbox-id = operator1smsbox group = smsbox-route smsbox-id = smsbox smsc-id = op group = smsbox-route smsbox-id = operator1smsbox smsc-id = op1smsc shortcode = 999 Appreciate your help. Ahmad Aburass,
Re: Sending SMS from a remote host !!!
Kannel machine can't open the requested URL - Check firewall routing config in both machines. Test to manual fetch the url from kannel machine. - you need to URL encode the dlr-url when sending it to kannel Home helps Regards Alvaro |-| Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier celular y Nextel en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS y GPRS online Visitenos en www.perusms.NET www.smsglobal.com.mx y www.pravcom.com On Mon, Jun 28, 2010 at 5:10 AM, Emmanuel CHANSON emmanuelchan...@gmail.com wrote: Your remote host can not access the dlr.php script placed on your 196.xxx.xxx.xxx server so DLR can not routed until Kannel. BR, Emmanuel 2010/6/28 ramous ram...@live.fr Good morning; I have tried for a long period to find a solution but without succes. My problem is; when I send an SMS directly from kannel everything works fine, but if I access to kannel from a remote host belong to another network, I recieve the following error although the SMS was successfully sent. 2010-04-01 11:43:23 [24388] [9] DEBUG: HTTP: Opening connection to `196.xxx.xxx.xxx:80' (fd=28). 2010-04-01 11:43:23 [24388] [9] DEBUG: Socket connecting 2010-04-01 11:46:32 [24388] [8] DEBUG: Get info about connecting socket 2010-04-01 11:46:32 [24388] [8] DEBUG: Socket not connected 2010-04-01 11:46:32 [24388] [8] ERROR: Couldn't fetch http://196.xxx.xxx.xxx/uvtsms/plugin/gateway/kannel/dlr.php?type=16s lid=311uid=1 Please did anyone faced this problem ?? -- View this message in context: http://old.nabble.com/Sending-SMS-from-a-remote-host-%21%21%21-tp29008530p29008530.html Sent from the Kannel - User mailing list archive at Nabble.com. -- Emmanuel CHANSON Emmanuel Mobile Nouvelle-Calédonie: +687.77.35.02 Mobile France: +33 (0) 6.68.03.89.56 @email : emmanuelchan...@gmail.com
Re: Kannel drop MT's when bearerbox is stopped.
Hi Ahmad, Please, read sqlbox userguide (here for example: http://www.blogalex.com/wp-content/uploads/2008/11/userguide.html#AEN478 ) Specifically, see Inserting MT messages by SQL section Regards, Konstantin On Mon, Jun 28, 2010 at 3:52 PM, ahmad aburass ahmad1985_2...@yahoo.comwrote: Hi Nikos, Unfortunately I'm not using sendsms-user to push the MT's, I have sqlbox and the backend application posts the MT's to a cgi that inserts them in sqlbox send_sms table. please advise. Regards, Ahmad. -- *From:* Nikos Balkanas nbalka...@gmail.com *To:* ahmad aburass ahmad1985_2...@yahoo.com *Cc:* users@kannel.org *Sent:* Mon, June 28, 2010 3:04:24 PM *Subject:* Re: Kannel drop MT's when bearerbox is stopped. Hi, (2) Yes. You can have 2 sendsms-user accounts within the same smsbox. Additionally you can specify smsc=smsc-id in your push URL, plus there are several options in you sendsms-user configuration such as default-smsc, forced-smsc, etc. Read User's guide about them. BR, Nikos - Original Message - From: ahmad aburass To: Nikos Balkanas Cc: users@kannel.org Sent: Sunday, June 27, 2010 5:26 PM Subject: Re: Kannel drop MT's when bearerbox is stopped. Hello Nikos, Your assumption is correct, the * is not in the included config file its just in the email :). For your second point, when I deployed Kannel I wanted to have a distinct smsbox for each operator so that each operator MT's will be routed to its smsbox and smsc, and i searched the internet and found that its possible to do it this way, is there any other way to configure Kannel to achieve this approach. Regards, Ahmad. From: Nikos Balkanas nbalka...@gmail.com To: ahmad aburass ahmad1985_2...@yahoo.com; users@kannel.org Sent: Wed, June 23, 2010 7:04:40 PM Subject: Re: Kannel drop MT's when bearerbox is stopped. Hi, What is your included operator1.conf file? Is this your: *** operator1 smsbox config file I am surprised this thing works at all. 1) Comments are specified by #, not *. I presume this is just in the email. 2) If the included file is the operator1.conf you post, then you end up with a configuration with 2 core groups! It should panic. BR, Nikos - Original Message - From: ahmad aburass To: users@kannel.org Sent: Wednesday, June 23, 2010 3:20 PM Subject: Kannel drop MT's when bearerbox is stopped. Hello All, I know that there is a lot of links indicating that Kannel doesnt do it, but i face it in my deployment, so I thought maybe its something wrong in my configuration. I'm using bearerbox with multiple smsboxes attached to it, along side with sqlbox. I have configured store subsystem as well. Whenever i stop bearerbox, all the queued MT's are dropped from the store and i get a delivery report (NACK/no SMSC) in the access log: 2010-03-27 11:33:15 Receive DLR [SMSC:op1smsc] [SVC:] [ACT:] [BINF:] [FID:] [from:999] [to:9647809863597] [flags:-1:-1:-1:-1:16] [msg:12:NACK/no SMSC] [udh:0:] 2010-03-27 11:34:55 Receive DLR [SMSC:op1smsc] [SVC:] [ACT:] [BINF:] [FID:] [from:999] [to:9647807102585] [flags:-1:-1:-1:-1:16] [msg:12:NACK/no SMSC] [udh:0:] Below is the config I made, PS: Kannel version 1.4.3, sqlbox version 0.7.2: ***smskannel.conf: group = core admin-port = 1500 smsbox-port = 13001 dlr-storage = mysql sms-resend-retry = 9 store-location = /var/spool/kannel/kannel_mt.store store-type = file store-dump-freq = 600 include = /usr/local/kannel/etc/smsc_connections/operator1.conf group = smsbox bearerbox-host = 127.0.0.1 bearerbox-port = 13002 http-request-retry = 600 http-queue-delay = 60 smsbox-id = smsbox group = smsbox-route smsbox-id = smsbox smsc-id = op group = smsbox-route smsbox-id = operator1smsbox smsc-id = op1smsc shortcode = 999 ***sqlbox configuration group = sqlbox id = compsqlbox smsbox-id = sqlbox bearerbox-host = localhost bearerbox-port = 13001 smsbox-port = 13002 sql-log-table = sent_sms sql-insert-table = send_sms ***operator1 smsbox config file group = core admin-port = 1500 smsbox-port = 13001 dlr-storage = mysql sms-resend-retry = 9 store-location = /var/spool/kannel/kannel_mt.store store-type = file store-dump-freq = 600 group = smsbox bearerbox-host = 127.0.0.1 bearerbox-port = 13002 http-request-retry = 600 http-queue-delay = 60 smsbox-id = operator1smsbox group = smsbox-route smsbox-id = smsbox smsc-id = op group = smsbox-route smsbox-id = operator1smsbox smsc-id = op1smsc shortcode = 999 Appreciate your help. Ahmad Aburass,
Re: SMPPBOX - problem with long Incoming SMS (MO)
Hi, I've read in SMPP specification that short_message field in The deliver_sm PDU can contain 0-254 chars only. I've found that SMPPBOX sends more characters here so it breaks SMPP protocol and that is why Kannel 1 can't receive that message correctly. So it is 100% SMPPBOX bug. In SMPP specification (by SMPP Developers Forum), near short_message field description I can read : Up to 254 octets of short message user data. When sending messages longer than 254 octets the message_payload parameter should be used and the sm_length parameter should be set to zero. Note: The message data should be inserted in either the short_message or the message_payload parameters. Both parameters must not be used simultaneously. Could someone provide a patch to resolve this issue? Thanks, Tomasz W Twoim liście datowanym 25 czerwca 2010 (07:41:05) można przeczytać: Hi, I'm sending logs of Bearerbox 1 2 and SMPPBOX on debug level: SMPPBOX log (Kannel 2): 2010-06-25 07:12:01 [21850] [1] INFO: We received an SMS message. 2010-06-25 07:12:01 [21850] [1] DEBUG: SMPP[main]: Manually forced source addr ton = 0, source add npi = 0 2010-06-25 07:12:01 [21850] [1] DEBUG: SMPP[main]: Manually forced dest addr ton = 0, dest add npi = 0 2010-06-25 07:12:01 [21850] [1] DEBUG: SMPP[main]: Sending PDU: 2010-06-25 07:12:01 [21850] [1] DEBUG: SMPP PDU 0x70b3c0 dump: 2010-06-25 07:12:01 [21850] [1] DEBUG: type_name: deliver_sm 2010-06-25 07:12:01 [21850] [1] DEBUG: command_id: 5 = 0x0005 2010-06-25 07:12:01 [21850] [1] DEBUG: command_status: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: sequence_number: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: service_type: NULL 2010-06-25 07:12:01 [21850] [1] DEBUG: source_addr_ton: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: source_addr_npi: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: source_addr: +48601232323 2010-06-25 07:12:01 [21850] [1] DEBUG: dest_addr_ton: 1 = 0x0001 2010-06-25 07:12:01 [21850] [1] DEBUG: dest_addr_npi: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: destination_addr: 48513123434 2010-06-25 07:12:01 [21850] [1] DEBUG: esm_class: 3 = 0x0003 2010-06-25 07:12:01 [21850] [1] DEBUG: protocol_id: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: priority_flag: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: schedule_delivery_time: NULL 2010-06-25 07:12:01 [21850] [1] DEBUG: validity_period: 100625051201000+ 2010-06-25 07:12:01 [21850] [1] DEBUG: registered_delivery: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: replace_if_present_flag: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: data_coding: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: sm_default_msg_id: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: sm_length: 256 = 0x0100 2010-06-25 07:12:01 [21850] [1] DEBUG: short_message: 2010-06-25 07:12:01 [21850] [1] DEBUG:Octet string at 0x70b5d0: 2010-06-25 07:12:01 [21850] [1] DEBUG: len: 256 2010-06-25 07:12:01 [21850] [1] DEBUG: size: 257 2010-06-25 07:12:01 [21850] [1] DEBUG: immutable: 0 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 54 65 73 74 20 74 65 73 74 20 74 75 74 75 75 75 Test test tutuuu 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 20 6a 6a 6a 6a 6a 20 6a 6a 6a 6a 6a 20 6b 6c 61j j kla 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 63 63 61 63 61 63 61 20 62 61 62 61 20 6a 6a 6a ccacaca baba jjj 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 6a 6a 20 6a 6a 6a 6a 6a 20 6a 6a 6a 6a 6a 20 6b jj j j k 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 6c 69 6b 20 3a 2d 29 3a 2d 29 3a 2d 29 3a 2d 29 lik :-):-):-):-) 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 2e 31 3a 2d 29 3a 2d 29 3a 2d 29 3a 2d 29 3a 2d .1:-):-):-):-):- 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 29 3a 2d 29 3a 2d 29 3a 2d 29 3a 2d 29 3a 2d 29 ):-):-):-):-):-) 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 3a 29 3a 2d 29 3a 2d 29 3a 2d 29 3a 2d 29 3a 2d :):-):-):-):-):- 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 29 3a 2d 29 3a 2d 29 3a 2d 29 3a 2d 29 3a 2d 29 ):-):-):-):-):-) 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 3a 29 62 61 20 3a 2d 29 3a 2d 29 3a 2d 29 3a 2d :)ba :-):-):-):- 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 29 2e 2d 62 61 62 61 31 61 61 61 61 61 61 61 61 ).-baba1 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 61 61 61 61 61 61 61 61 6f 6f 6f 6f 6f 6f 6f 6f 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 6f 6f 6f 6f 6f 6f 6f 6f 6f 6f 6f 6f 6f 6f 6f 6f 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 6f 6f 6f 6f 6f 6f 6f 6f 6f 6f 6f 6f 6f 6f 6f 6f 2010-06-25 07:12:01 [21850] [1]
Recommended Operative System for Kannel
Hi, in the past I have troubles trying to install Kannel in FreeBSD 7.0, so before give it another try I would like to ask for some suggestion what would be the best Operative System (or Linux Distro) for hosting Kannel? In terms of clean compile, no general dependency issues, autostart... I know how dumb can this sound, but I don;t have much time for troubleshoot an installation, will prefer to use that time for configuring Kannel. Thanks a lot! Aldo
RE: SMPPBOX - problem with long Incoming SMS (MO)
Sure thing. We are working on it at this very moment. Just remember: This is free software (free as in speech AND as in beer). Sometimes it takes a little bit longer to get things done. == Rene -Original Message- From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of Tomasz Sent: maandag 28 juni 2010 22:02 To: users@kannel.org Subject: Re: SMPPBOX - problem with long Incoming SMS (MO) Hi, I've read in SMPP specification that short_message field in The deliver_sm PDU can contain 0-254 chars only. I've found that SMPPBOX sends more characters here so it breaks SMPP protocol and that is why Kannel 1 can't receive that message correctly. So it is 100% SMPPBOX bug. In SMPP specification (by SMPP Developers Forum), near short_message field description I can read : Up to 254 octets of short message user data. When sending messages longer than 254 octets the message_payload parameter should be used and the sm_length parameter should be set to zero. Note: The message data should be inserted in either the short_message or the message_payload parameters. Both parameters must not be used simultaneously. Could someone provide a patch to resolve this issue? Thanks, Tomasz W Twoim liście datowanym 25 czerwca 2010 (07:41:05) można przeczytać: Hi, I'm sending logs of Bearerbox 1 2 and SMPPBOX on debug level: SMPPBOX log (Kannel 2): 2010-06-25 07:12:01 [21850] [1] INFO: We received an SMS message. 2010-06-25 07:12:01 [21850] [1] DEBUG: SMPP[main]: Manually forced source addr ton = 0, source add npi = 0 2010-06-25 07:12:01 [21850] [1] DEBUG: SMPP[main]: Manually forced dest addr ton = 0, dest add npi = 0 2010-06-25 07:12:01 [21850] [1] DEBUG: SMPP[main]: Sending PDU: 2010-06-25 07:12:01 [21850] [1] DEBUG: SMPP PDU 0x70b3c0 dump: 2010-06-25 07:12:01 [21850] [1] DEBUG: type_name: deliver_sm 2010-06-25 07:12:01 [21850] [1] DEBUG: command_id: 5 = 0x0005 2010-06-25 07:12:01 [21850] [1] DEBUG: command_status: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: sequence_number: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: service_type: NULL 2010-06-25 07:12:01 [21850] [1] DEBUG: source_addr_ton: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: source_addr_npi: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: source_addr: +48601232323 2010-06-25 07:12:01 [21850] [1] DEBUG: dest_addr_ton: 1 = 0x0001 2010-06-25 07:12:01 [21850] [1] DEBUG: dest_addr_npi: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: destination_addr: 48513123434 2010-06-25 07:12:01 [21850] [1] DEBUG: esm_class: 3 = 0x0003 2010-06-25 07:12:01 [21850] [1] DEBUG: protocol_id: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: priority_flag: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: schedule_delivery_time: NULL 2010-06-25 07:12:01 [21850] [1] DEBUG: validity_period: 100625051201000+ 2010-06-25 07:12:01 [21850] [1] DEBUG: registered_delivery: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: replace_if_present_flag: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: data_coding: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: sm_default_msg_id: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: sm_length: 256 = 0x0100 2010-06-25 07:12:01 [21850] [1] DEBUG: short_message: 2010-06-25 07:12:01 [21850] [1] DEBUG:Octet string at 0x70b5d0: 2010-06-25 07:12:01 [21850] [1] DEBUG: len: 256 2010-06-25 07:12:01 [21850] [1] DEBUG: size: 257 2010-06-25 07:12:01 [21850] [1] DEBUG: immutable: 0 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 54 65 73 74 20 74 65 73 74 20 74 75 74 75 75 75 Test test tutuuu 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 20 6a 6a 6a 6a 6a 20 6a 6a 6a 6a 6a 20 6b 6c 61j j kla 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 63 63 61 63 61 63 61 20 62 61 62 61 20 6a 6a 6a ccacaca baba jjj 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 6a 6a 20 6a 6a 6a 6a 6a 20 6a 6a 6a 6a 6a 20 6b jj j j k 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 6c 69 6b 20 3a 2d 29 3a 2d 29 3a 2d 29 3a 2d 29 lik :-):-):-):-) 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 2e 31 3a 2d 29 3a 2d 29 3a 2d 29 3a 2d 29 3a 2d .1:-):-):-):-):- 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 29 3a 2d 29 3a 2d 29 3a 2d 29 3a 2d 29 3a 2d 29 ):-):-):-):-):-) 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 3a 29 3a 2d 29 3a 2d 29 3a 2d 29 3a 2d 29 3a 2d :):-):-):-):-):- 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 29 3a 2d 29 3a 2d 29 3a 2d 29 3a 2d 29 3a 2d 29 ):-):-):-):-):-) 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 3a 29 62 61 20 3a 2d 29 3a 2d 29 3a 2d 29 3a 2d :)ba :-):-):-):- 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 29 2e 2d 62 61 62 61 31 61 61 61 61 61 61 61 61 ).-baba1 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 61 61 61 61 61 61 61 61 61 61 61 61 61
Re: Recommended Operative System for Kannel
Hi, Any Linux distro should be fine. BSD and Solaris are also pretty good, although the 64bit version needs a bit tweeking. Just remember to download latest svn: svn co https://svn.kannel.org/gateway/trunk You need libiconv and multithreaded openssl (if using SSL) and any other development libraries for DBs you plan to use. Docbook would be nice, too. Latest gcc has upped its warnings, so you may get some incorrect types you can safely ignore. We are working to remove them. BR, Nikos - Original Message - From: Aldo Zavala a...@cleartalk.net To: users@kannel.org Sent: Monday, June 28, 2010 9:48 PM Subject: Recommended Operative System for Kannel Hi, in the past I have troubles trying to install Kannel in FreeBSD 7.0, so before give it another try I would like to ask for some suggestion what would be the best Operative System (or Linux Distro) for hosting Kannel? In terms of clean compile, no general dependency issues, autostart... I know how dumb can this sound, but I don;t have much time for troubleshoot an installation, will prefer to use that time for configuring Kannel. Thanks a lot! Aldo
Re: SMPPBOX - problem with long Incoming SMS (MO)
Correct me if I am wrong, is this the same issue with last week's ticket about long MOs? Then it is only for MOs. Patch is ready, we are in the process of testing it. BR, Nikos - Original Message - From: Tomasz ad...@impexrur.pl To: users@kannel.org Sent: Monday, June 28, 2010 11:01 PM Subject: Re: SMPPBOX - problem with long Incoming SMS (MO) Hi, I've read in SMPP specification that short_message field in The deliver_sm PDU can contain 0-254 chars only. I've found that SMPPBOX sends more characters here so it breaks SMPP protocol and that is why Kannel 1 can't receive that message correctly. So it is 100% SMPPBOX bug. In SMPP specification (by SMPP Developers Forum), near short_message field description I can read : Up to 254 octets of short message user data. When sending messages longer than 254 octets the message_payload parameter should be used and the sm_length parameter should be set to zero. Note: The message data should be inserted in either the short_message or the message_payload parameters. Both parameters must not be used simultaneously. Could someone provide a patch to resolve this issue? Thanks, Tomasz W Twoim li�cie datowanym 25 czerwca 2010 (07:41:05) moΏna przeczytaζ: Hi, I'm sending logs of Bearerbox 1 2 and SMPPBOX on debug level: SMPPBOX log (Kannel 2): 2010-06-25 07:12:01 [21850] [1] INFO: We received an SMS message. 2010-06-25 07:12:01 [21850] [1] DEBUG: SMPP[main]: Manually forced source addr ton = 0, source add npi = 0 2010-06-25 07:12:01 [21850] [1] DEBUG: SMPP[main]: Manually forced dest addr ton = 0, dest add npi = 0 2010-06-25 07:12:01 [21850] [1] DEBUG: SMPP[main]: Sending PDU: 2010-06-25 07:12:01 [21850] [1] DEBUG: SMPP PDU 0x70b3c0 dump: 2010-06-25 07:12:01 [21850] [1] DEBUG: type_name: deliver_sm 2010-06-25 07:12:01 [21850] [1] DEBUG: command_id: 5 = 0x0005 2010-06-25 07:12:01 [21850] [1] DEBUG: command_status: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: sequence_number: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: service_type: NULL 2010-06-25 07:12:01 [21850] [1] DEBUG: source_addr_ton: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: source_addr_npi: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: source_addr: +48601232323 2010-06-25 07:12:01 [21850] [1] DEBUG: dest_addr_ton: 1 = 0x0001 2010-06-25 07:12:01 [21850] [1] DEBUG: dest_addr_npi: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: destination_addr: 48513123434 2010-06-25 07:12:01 [21850] [1] DEBUG: esm_class: 3 = 0x0003 2010-06-25 07:12:01 [21850] [1] DEBUG: protocol_id: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: priority_flag: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: schedule_delivery_time: NULL 2010-06-25 07:12:01 [21850] [1] DEBUG: validity_period: 100625051201000+ 2010-06-25 07:12:01 [21850] [1] DEBUG: registered_delivery: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: replace_if_present_flag: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: data_coding: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: sm_default_msg_id: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: sm_length: 256 = 0x0100 2010-06-25 07:12:01 [21850] [1] DEBUG: short_message: 2010-06-25 07:12:01 [21850] [1] DEBUG:Octet string at 0x70b5d0: 2010-06-25 07:12:01 [21850] [1] DEBUG: len: 256 2010-06-25 07:12:01 [21850] [1] DEBUG: size: 257 2010-06-25 07:12:01 [21850] [1] DEBUG: immutable: 0 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 54 65 73 74 20 74 65 73 74 20 74 75 74 75 75 75 Test test tutuuu 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 20 6a 6a 6a 6a 6a 20 6a 6a 6a 6a 6a 20 6b 6c 61j j kla 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 63 63 61 63 61 63 61 20 62 61 62 61 20 6a 6a 6a ccacaca baba jjj 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 6a 6a 20 6a 6a 6a 6a 6a 20 6a 6a 6a 6a 6a 20 6b jj j j k 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 6c 69 6b 20 3a 2d 29 3a 2d 29 3a 2d 29 3a 2d 29 lik :-):-):-):-) 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 2e 31 3a 2d 29 3a 2d 29 3a 2d 29 3a 2d 29 3a 2d .1:-):-):-):-):- 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 29 3a 2d 29 3a 2d 29 3a 2d 29 3a 2d 29 3a 2d 29 ):-):-):-):-):-) 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 3a 29 3a 2d 29 3a 2d 29 3a 2d 29 3a 2d 29 3a 2d :):-):-):-):-):- 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 29 3a 2d 29 3a 2d 29 3a 2d 29 3a 2d 29 3a 2d 29 ):-):-):-):-):-) 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 3a 29 62 61 20 3a 2d 29 3a 2d 29 3a 2d 29 3a 2d :)ba :-):-):-):- 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 29 2e 2d 62 61 62 61 31 61 61 61 61 61 61 61 61 ).-baba1 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 61 61 61 61 61 61 61 61 6f 6f 6f
Re: SMPPBOX - problem with long Incoming SMS (MO)
But, beer is not free! :-( Nikos - Original Message - From: Rene Kluwen rene.klu...@chimit.nl To: 'Tomasz' ad...@impexrur.pl; users@kannel.org Sent: Monday, June 28, 2010 11:43 PM Subject: RE: SMPPBOX - problem with long Incoming SMS (MO) Sure thing. We are working on it at this very moment. Just remember: This is free software (free as in speech AND as in beer). Sometimes it takes a little bit longer to get things done. == Rene -Original Message- From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of Tomasz Sent: maandag 28 juni 2010 22:02 To: users@kannel.org Subject: Re: SMPPBOX - problem with long Incoming SMS (MO) Hi, I've read in SMPP specification that short_message field in The deliver_sm PDU can contain 0-254 chars only. I've found that SMPPBOX sends more characters here so it breaks SMPP protocol and that is why Kannel 1 can't receive that message correctly. So it is 100% SMPPBOX bug. In SMPP specification (by SMPP Developers Forum), near short_message field description I can read : Up to 254 octets of short message user data. When sending messages longer than 254 octets the message_payload parameter should be used and the sm_length parameter should be set to zero. Note: The message data should be inserted in either the short_message or the message_payload parameters. Both parameters must not be used simultaneously. Could someone provide a patch to resolve this issue? Thanks, Tomasz W Twoim li¶cie datowanym 25 czerwca 2010 (07:41:05) moΏna przeczytaζ: Hi, I'm sending logs of Bearerbox 1 2 and SMPPBOX on debug level: SMPPBOX log (Kannel 2): 2010-06-25 07:12:01 [21850] [1] INFO: We received an SMS message. 2010-06-25 07:12:01 [21850] [1] DEBUG: SMPP[main]: Manually forced source addr ton = 0, source add npi = 0 2010-06-25 07:12:01 [21850] [1] DEBUG: SMPP[main]: Manually forced dest addr ton = 0, dest add npi = 0 2010-06-25 07:12:01 [21850] [1] DEBUG: SMPP[main]: Sending PDU: 2010-06-25 07:12:01 [21850] [1] DEBUG: SMPP PDU 0x70b3c0 dump: 2010-06-25 07:12:01 [21850] [1] DEBUG: type_name: deliver_sm 2010-06-25 07:12:01 [21850] [1] DEBUG: command_id: 5 = 0x0005 2010-06-25 07:12:01 [21850] [1] DEBUG: command_status: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: sequence_number: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: service_type: NULL 2010-06-25 07:12:01 [21850] [1] DEBUG: source_addr_ton: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: source_addr_npi: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: source_addr: +48601232323 2010-06-25 07:12:01 [21850] [1] DEBUG: dest_addr_ton: 1 = 0x0001 2010-06-25 07:12:01 [21850] [1] DEBUG: dest_addr_npi: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: destination_addr: 48513123434 2010-06-25 07:12:01 [21850] [1] DEBUG: esm_class: 3 = 0x0003 2010-06-25 07:12:01 [21850] [1] DEBUG: protocol_id: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: priority_flag: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: schedule_delivery_time: NULL 2010-06-25 07:12:01 [21850] [1] DEBUG: validity_period: 100625051201000+ 2010-06-25 07:12:01 [21850] [1] DEBUG: registered_delivery: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: replace_if_present_flag: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: data_coding: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: sm_default_msg_id: 0 = 0x 2010-06-25 07:12:01 [21850] [1] DEBUG: sm_length: 256 = 0x0100 2010-06-25 07:12:01 [21850] [1] DEBUG: short_message: 2010-06-25 07:12:01 [21850] [1] DEBUG:Octet string at 0x70b5d0: 2010-06-25 07:12:01 [21850] [1] DEBUG: len: 256 2010-06-25 07:12:01 [21850] [1] DEBUG: size: 257 2010-06-25 07:12:01 [21850] [1] DEBUG: immutable: 0 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 54 65 73 74 20 74 65 73 74 20 74 75 74 75 75 75 Test test tutuuu 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 20 6a 6a 6a 6a 6a 20 6a 6a 6a 6a 6a 20 6b 6c 61j j kla 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 63 63 61 63 61 63 61 20 62 61 62 61 20 6a 6a 6a ccacaca baba jjj 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 6a 6a 20 6a 6a 6a 6a 6a 20 6a 6a 6a 6a 6a 20 6b jj j j k 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 6c 69 6b 20 3a 2d 29 3a 2d 29 3a 2d 29 3a 2d 29 lik :-):-):-):-) 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 2e 31 3a 2d 29 3a 2d 29 3a 2d 29 3a 2d 29 3a 2d .1:-):-):-):-):- 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 29 3a 2d 29 3a 2d 29 3a 2d 29 3a 2d 29 3a 2d 29 ):-):-):-):-):-) 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 3a 29 3a 2d 29 3a 2d 29 3a 2d 29 3a 2d 29 3a 2d :):-):-):-):-):- 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 29 3a 2d 29 3a 2d 29 3a 2d 29 3a 2d 29 3a 2d 29 ):-):-):-):-):-) 2010-06-25 07:12:01 [21850] [1] DEBUG: data: 3a 29 62 61 20 3a 2d 29 3a 2d 29 3a 2d 29 3a 2d :)ba :-):-):-):-
http adminstration commands
Hi, I am using kannel CVS Version as a SMS gateway to send XML settings message. As in kannel I have following command to check the status of Kannel : http://localhost:13000/status.html?password=password Now i want to restart kannel service by using http adminstation commands Please help me to know the exact command for it .As the command i am using below which is not working. http://localhost:13000/restart?password=pasword Kannel returns me Denied. Regards Harmeet Singh
Kannel SMS speed control
Hi, I am using Kannel CVS Version. Please help me to know that How many SMS can kannel sent PER/MIN using SMPP server. Can i control the speed of sending message of Kannel on the basis of send-sms user group. Regards Harmeet Singh
Re: http adminstration commands
Hi, What password are you using? You can use status-password to view status, but you need admin password to restart service. Read User's Guide. BR, Nikos - Original Message - From: Harmeet Singh Dhingra harmeet.dhing...@gmail.com To: users@kannel.org Sent: Tuesday, June 29, 2010 5:47 AM Subject: http adminstration commands Hi, I am using kannel CVS Version as a SMS gateway to send XML settings message. As in kannel I have following command to check the status of Kannel : http://localhost:13000/status.html?password=password Now i want to restart kannel service by using http adminstation commands Please help me to know the exact command for it .As the command i am using below which is not working. http://localhost:13000/restart?password=pasword Kannel returns me Denied. Regards Harmeet Singh
Re: Recommended Operative System for Kannel
That is just great, I would like to run my Kannel in a FreeBSD Box, I don't really use GNU Linux for production. I will download the svn version then. Thanks, Aldo Zavala - Original Message - From: Nikos Balkanas [mailto:nbalka...@gmail.com] To: users@kannel.org, Aldo Zavala [mailto:a...@cleartalk.net] Sent: Mon, 28 Jun 2010 19:13:38 -0700 Subject: Re: Recommended Operative System for Kannel Hi, Any Linux distro should be fine. BSD and Solaris are also pretty good, although the 64bit version needs a bit tweeking. Just remember to download latest svn: svn co https://svn.kannel.org/gateway/trunk You need libiconv and multithreaded openssl (if using SSL) and any other development libraries for DBs you plan to use. Docbook would be nice, too. Latest gcc has upped its warnings, so you may get some incorrect types you can safely ignore. We are working to remove them. BR, Nikos - Original Message - From: Aldo Zavala a...@cleartalk.net To: users@kannel.org Sent: Monday, June 28, 2010 9:48 PM Subject: Recommended Operative System for Kannel Hi, in the past I have troubles trying to install Kannel in FreeBSD 7.0, so before give it another try I would like to ask for some suggestion what would be the best Operative System (or Linux Distro) for hosting Kannel? In terms of clean compile, no general dependency issues, autostart... I know how dumb can this sound, but I don;t have much time for troubleshoot an installation, will prefer to use that time for configuring Kannel. Thanks a lot! Aldo
