Re: SMPPBOX - problem with long Incoming SMS (MO)
Hi, Yes, its the same issue. BR, Tomasz W Twoim liście datowanym 29 czerwca 2010 (04:18:36) można przeczytać: 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 licie 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
Re: SMPPBOX - problem with long Incoming SMS (MO)
Then the actual pdu should be even less than 254 B, since there is a constraint for an SMS not to exceed 140 B + SMPP headers ~ 170 B. BR, Nikos - Original Message - From: Tomasz ad...@impexrur.pl To: users@kannel.org Sent: Tuesday, June 29, 2010 9:14 AM Subject: Re: SMPPBOX - problem with long Incoming SMS (MO) Hi, Yes, its the same issue. BR, Tomasz W Twoim liście datowanym 29 czerwca 2010 (04:18:36) można przeczytać: 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
Datatype for timestamp for mysql dlr storage
Hi
I am using the mysql dlr storage type. I have everything working except for
the timestamp. This is the output from debug mode
sql: INSERT INTO delivery_receipts (smsc, received, source, destination,
service, url, mask, boxc, status) VALUES ('XXXYYYXXX', '50062911024679487',
'+123123123', '+123123123', 'simple', '', '31', '', '0');
I set the delivery_receipts table received column to timestamp but when I
query it I get this -00-00 00:00:00
What should the datatype of the received column be? I see in some places
people have left it as varchar. Is it up to me to do the translation.
Thanks and appreciate any assistance.
Regards,
Re: Datatype for timestamp for mysql dlr storage
Hi,
Please consult the online Mysql reference. This is not a kannel question. If
you use varchar or even datetime type column column, you better provide the
value yourself. If you use timestamp type column, you can have mysql
initialize it to current time.
BR,
Nikos
- Original Message -
From: brett skinner
To: users@kannel.org
Sent: Tuesday, June 29, 2010 12:12 PM
Subject: Datatype for timestamp for mysql dlr storage
Hi
I am using the mysql dlr storage type. I have everything working except for
the timestamp. This is the output from debug mode
sql: INSERT INTO delivery_receipts (smsc, received, source, destination,
service, url, mask, boxc, status) VALUES ('XXXYYYXXX', '50062911024679487',
'+123123123', '+123123123', 'simple', '', '31', '', '0');
I set the delivery_receipts table received column to timestamp but when I
query it I get this -00-00 00:00:00
What should the datatype of the received column be? I see in some places
people have left it as varchar. Is it up to me to do the translation.
Thanks and appreciate any assistance.
Regards,
Re: Recommended Operative System for Kannel
On FreeBSD 8/7 (amd64) runs grate just use gmake and try the trunk version, then the following when compiling: $./configure --enable-docs=no --with-malloc=native --enable-start-stop-daemon=no --prefix=/usr/local --with-cflags=-g --with-libs=-lpthread gmake gmake install On Jun 29, 2010, at 5:49 AM, Aldo Zavala wrote: 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
Re: Recommended Operative System for Kannel
Better use --with-cflags=-m64 -O6 -s -W -Wall if you intend to use it for profuction on a 64bit system. BR, Nikos - Original Message - From: Nicolas de Bari Embriz Garcia Rojas To: Aldo Zavala Cc: Nikos Balkanas ; users@kannel.org Sent: Tuesday, June 29, 2010 12:41 PM Subject: Re: Recommended Operative System for Kannel On FreeBSD 8/7 (amd64) runs grate just use gmake and try the trunk version, then the following when compiling: $./configure --enable-docs=no --with-malloc=native --enable-start-stop-daemon=no --prefix=/usr/local --with-cflags=-g --with-libs=-lpthread gmake gmake install On Jun 29, 2010, at 5:49 AM, Aldo Zavala wrote: 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
Re: Datatype for timestamp for mysql dlr storage
Problem is - Kannel stores the TS in different formats, depending on remote
SMSC protocol and implementation.
Sometimes i see numeric values, sometimes hex
So i dont think really anything but varchar would work well
2010/6/29 Nikos Balkanas nbalka...@gmail.com
Hi,
Please consult the online Mysql reference. This is not a kannel question.
If you use varchar or even datetime type column column, you better provide
the value yourself. If you use timestamp type column, you can have mysql
initialize it to current time.
BR,
Nikos
- Original Message - From: brett skinner
To: users@kannel.org
Sent: Tuesday, June 29, 2010 12:12 PM
Subject: Datatype for timestamp for mysql dlr storage
Hi
I am using the mysql dlr storage type. I have everything working except for
the timestamp. This is the output from debug mode
sql: INSERT INTO delivery_receipts (smsc, received, source, destination,
service, url, mask, boxc, status) VALUES ('XXXYYYXXX', '50062911024679487',
'+123123123', '+123123123', 'simple', '', '31', '', '0');
I set the delivery_receipts table received column to timestamp but when I
query it I get this -00-00 00:00:00
What should the datatype of the received column be? I see in some places
people have left it as varchar. Is it up to me to do the translation.
Thanks and appreciate any assistance.
Regards,
Re: Datatype for timestamp for mysql dlr storage
Hi
Thanks for your response Konstantin. So if I am understanding you correctly
the problem is that every SMSC is responding according to their own specific
implementation. So for timestamps I will need to implement something such as
a column with a default value.
Thanks for your input.
On Tue, Jun 29, 2010 at 11:53 AM, Konstantin Vayner pon...@appcell.netwrote:
Problem is - Kannel stores the TS in different formats, depending on remote
SMSC protocol and implementation.
Sometimes i see numeric values, sometimes hex
So i dont think really anything but varchar would work well
2010/6/29 Nikos Balkanas nbalka...@gmail.com
Hi,
Please consult the online Mysql reference. This is not a kannel question.
If you use varchar or even datetime type column column, you better provide
the value yourself. If you use timestamp type column, you can have mysql
initialize it to current time.
BR,
Nikos
- Original Message - From: brett skinner
To: users@kannel.org
Sent: Tuesday, June 29, 2010 12:12 PM
Subject: Datatype for timestamp for mysql dlr storage
Hi
I am using the mysql dlr storage type. I have everything working except
for the timestamp. This is the output from debug mode
sql: INSERT INTO delivery_receipts (smsc, received, source, destination,
service, url, mask, boxc, status) VALUES ('XXXYYYXXX', '50062911024679487',
'+123123123', '+123123123', 'simple', '', '31', '', '0');
I set the delivery_receipts table received column to timestamp but when I
query it I get this -00-00 00:00:00
What should the datatype of the received column be? I see in some places
people have left it as varchar. Is it up to me to do the translation.
Thanks and appreciate any assistance.
Regards,
ESME Session
Dear All, I am using SMPP BOX but getting some error. Scenario: I am using kannel as client and SMPPBOX as server. When I bind accounts for more than 1 instance on kannel and starting the kannel, then Unknown sessions on SMPP BOX (ESME) get increase automatically. Is this a bug or I have done any mistake. Waiting for reply. Thanks in advance, Sandesh
Does Kannel always place the message_id from a submit_sm_resp into timestamp for a DLR using SMPP 3.4
Hi I was checking in the SMPP 3.4 spec and came across the submit_sm_resp PDU which specifies a message_id field. According to the spec: This field contains the SMSC message ID of the submitted message. It may be used at a later stage to query the status of a message, cancel or replace the message. We are using MySql DLR. Looking at the debug output from Kannel: 2010-06-29 13:13:31 [3124] [6] DEBUG: message_id: 50062913133840086 2010-06-29 13:13:31 [3124] [6] DEBUG: SMPP PDU dump ends. 2010-06-29 13:13:31 [3124] [6] DEBUG: DLR[mysql]: Adding DLR smsc=, ts=50062913133840086, src=+1231234, dst=+1231234, mask=31, boxc= It seems that it is placing the message_id into the ts field. Is this always the case? Regards,
Re: Does Kannel always place the message_id from a submit_sm_resp into timestamp for a DLR using SMPP 3.4
Yes, that's the expected behavior. Regards, Alex On Tue, Jun 29, 2010 at 1:21 PM, brett skinner tatty.dishcl...@gmail.comwrote: Hi I was checking in the SMPP 3.4 spec and came across the submit_sm_resp PDU which specifies a message_id field. According to the spec: This field contains the SMSC message ID of the submitted message. It may be used at a later stage to query the status of a message, cancel or replace the message. We are using MySql DLR. Looking at the debug output from Kannel: 2010-06-29 13:13:31 [3124] [6] DEBUG: message_id: 50062913133840086 2010-06-29 13:13:31 [3124] [6] DEBUG: SMPP PDU dump ends. 2010-06-29 13:13:31 [3124] [6] DEBUG: DLR[mysql]: Adding DLR smsc=, ts=50062913133840086, src=+1231234, dst=+1231234, mask=31, boxc= It seems that it is placing the message_id into the ts field. Is this always the case? Regards,
RE: Kannel SMS speed control
Look at the troughput directive in group = smsc. -Original Message- From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of Harmeet Singh Dhingra Sent: dinsdag 29 juni 2010 4:51 To: users@kannel.org Subject: 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: ESME Session
I think current SMPP box version only allows for one session per user at the same time. From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of Sandesh Waman // Viva Sent: dinsdag 29 juni 2010 12:51 To: Kannel Users Subject: ESME Session Dear All, I am using SMPP BOX but getting some error. Scenario: I am using kannel as client and SMPPBOX as server. When I bind accounts for more than 1 instance on kannel and starting the kannel, then Unknown sessions on SMPP BOX (ESME) get increase automatically. Is this a bug or I have done any mistake. Waiting for reply. Thanks in advance, Sandesh
RE: Does Kannel always place the message_id from a submit_sm_resp into timestamp for a DLR using SMPP 3.4
Yes, this is always the case. But the row get deleted again after the message reaches a final delivery state. From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of brett skinner Sent: dinsdag 29 juni 2010 13:21 To: users@kannel.org Subject: Does Kannel always place the message_id from a submit_sm_resp into timestamp for a DLR using SMPP 3.4 Hi I was checking in the SMPP 3.4 spec and came across the submit_sm_resp PDU which specifies a message_id field. According to the spec: This field contains the SMSC message ID of the submitted message. It may be used at a later stage to query the status of a message, cancel or replace the message. We are using MySql DLR. Looking at the debug output from Kannel: 2010-06-29 13:13:31 [3124] [6] DEBUG: message_id: 50062913133840086 2010-06-29 13:13:31 [3124] [6] DEBUG: SMPP PDU dump ends. 2010-06-29 13:13:31 [3124] [6] DEBUG: DLR[mysql]: Adding DLR smsc=, ts=50062913133840086, src=+1231234, dst=+1231234, mask=31, boxc= It seems that it is placing the message_id into the ts field. Is this always the case? Regards,
RE: SMPPBOX - problem with long Incoming SMS (MO)
Sorry, I was mistaken. Point that I was making is that most of us have a day time occupation and have limited time available to make patches for Kannel. -Original Message- From: Nikos Balkanas [mailto:nbalka...@gmail.com] Sent: dinsdag 29 juni 2010 4:20 To: Rene Kluwen; 'Tomasz'; users@kannel.org Subject: 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
How to get the count of message sent
Hi, I am using kannel to send OTA XML messages , it include URLENCODED text . The length of URLENCODED text is about 2087 but message send by kannel is 2 msg as it calculate it into 185 length . How can i get the count of message sent by kannel in case of URLENCODED through HTTP Link. Regards Harmeet Singh
Re: Recommended Operative System for Kannel
Thanks, what you mean by 'trunk version' ? what is it? Thanks, Aldo Zavala - Original Message - From: Nicolas de Bari Embriz Garcia Rojas [mailto:nb...@backup.sh] To: Aldo Zavala [mailto:a...@cleartalk.net] Cc: Nikos Balkanas [mailto:nbalka...@gmail.com], users@kannel.org Sent: Tue, 29 Jun 2010 02:41:54 -0700 Subject: Re: Recommended Operative System for Kannel On FreeBSD 8/7 (amd64) runs grate just use gmake and try the trunk version, then the following when compiling: $./configure --enable-docs=no --with-malloc=native --enable-start-stop-daemon=no --prefix=/usr/local --with-cflags=-g --with-libs=-lpthread gmake gmake install On Jun 29, 2010, at 5:49 AM, Aldo Zavala wrote: 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
Re: Recommended Operative System for Kannel
Production server it's going to be a i386 box. Thanks, Aldo Zavala - Original Message - From: Nikos Balkanas [mailto:nbalka...@gmail.com] To: Nicolas de Bari Embriz Garcia Rojas [mailto:nb...@backup.sh], Aldo Zavala [mailto:a...@cleartalk.net] Cc: users@kannel.org Sent: Tue, 29 Jun 2010 02:50:15 -0700 Subject: Re: Recommended Operative System for Kannel Better use --with-cflags=-m64 -O6 -s -W -Wall if you intend to use it for profuction on a 64bit system. BR, Nikos - Original Message - From: Nicolas de Bari Embriz Garcia Rojas To: Aldo Zavala Cc: Nikos Balkanas ; users@kannel.org Sent: Tuesday, June 29, 2010 12:41 PM Subject: Re: Recommended Operative System for Kannel On FreeBSD 8/7 (amd64) runs grate just use gmake and try the trunk version, then the following when compiling: $./configure --enable-docs=no --with-malloc=native --enable-start-stop-daemon=no --prefix=/usr/local --with-cflags=-g --with-libs=-lpthread gmake gmake install On Jun 29, 2010, at 5:49 AM, Aldo Zavala wrote: 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
Re: Recommended Operative System for Kannel
Hi I mean this one: svn co https://svn.kannel.org/gateway/trunk regards. On Jun 29, 2010, at 4:10 PM, Aldo Zavala wrote: Thanks, what you mean by 'trunk version' ? what is it? Thanks, Aldo Zavala - Original Message - From: Nicolas de Bari Embriz Garcia Rojas [mailto:nb...@backup.sh] To: Aldo Zavala [mailto:a...@cleartalk.net] Cc: Nikos Balkanas [mailto:nbalka...@gmail.com], users@kannel.org Sent: Tue, 29 Jun 2010 02:41:54 -0700 Subject: Re: Recommended Operative System for Kannel On FreeBSD 8/7 (amd64) runs grate just use gmake and try the trunk version, then the following when compiling: $./configure --enable-docs=no --with-malloc=native --enable-start-stop-daemon=no --prefix=/usr/local --with-cflags=-g --with-libs=-lpthread gmake gmake install On Jun 29, 2010, at 5:49 AM, Aldo Zavala wrote: 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
Re: Kannel SMS speed control
Hi, You can also bench it for MOs, using the test/drive_smpp. But the real bottleneck is the SMSc. BR, Nikos - Original Message - From: Rene Kluwen rene.klu...@chimit.nl To: 'Harmeet Singh Dhingra' harmeet.dhing...@gmail.com; users@kannel.org Sent: Tuesday, June 29, 2010 4:25 PM Subject: RE: Kannel SMS speed control Look at the troughput directive in group = smsc. -Original Message- From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of Harmeet Singh Dhingra Sent: dinsdag 29 juni 2010 4:51 To: users@kannel.org Subject: 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
SMPP Delivery Reports Issue
Hello Users,
I've configured a new SMSC on my existing kannel installation. My DLRs are
not working on this SMSC. I'm using mysql DLR storage. I can see the insert
queries in the log but nothing gets inserted into the DB. DLRs are coming on
SMPP properly.
*
*
*
*
*2010-06-29 16:55:18 [24139] [22] DEBUG: priority_flag: 0 = 0x*
*2010-06-29 16:55:18 [24139] [22] DEBUG: schedule_delivery_time: NULL*
*2010-06-29 16:55:18 [24139] [22] DEBUG: validity_period: NULL*
*2010-06-29 16:55:18 [24139] [22] DEBUG: registered_delivery: 1 =
0x0001*
*2010-06-29 16:55:18 [24139] [22] DEBUG: replace_if_present_flag: 0 =
0x*
*2010-06-29 16:55:18 [24139] [22] DEBUG: data_coding: 0 = 0x*
*2010-06-29 16:55:18 [24139] [22] DEBUG: sm_default_msg_id: 0 = 0x
*
*2010-06-29 16:55:18 [24139] [22] DEBUG: sm_length: 8 = 0x0008*
*2010-06-29 16:55:18 [24139] [22] DEBUG: short_message: Test SMS*
*2010-06-29 16:55:18 [24139] [22] DEBUG: SMPP PDU dump ends.*
*2010-06-29 16:55:18 [24139] [22] DEBUG: SMPP[160by2SMPP]: Got PDU:*
*2010-06-29 16:55:18 [24139] [22] DEBUG: SMPP PDU 0x795bf0 dump:*
*2010-06-29 16:55:18 [24139] [22] DEBUG: type_name: submit_sm_resp*
*2010-06-29 16:55:18 [24139] [22] DEBUG: command_id: 2147483652 =
0x8004*
*2010-06-29 16:55:18 [24139] [22] DEBUG: command_status: 0 = 0x*
*2010-06-29 16:55:18 [24139] [22] DEBUG: sequence_number: 18 = 0x0012*
*2010-06-29 16:55:18 [24139] [22] DEBUG: message_id: 51*
*2010-06-29 16:55:18 [24139] [22] DEBUG: SMPP PDU dump ends.*
*2010-06-29 16:55:18 [24139] [22] DEBUG: DLR[mysql]: Adding DLR
smsc=160by2SMPP, ts=51, src=91X, dst=**91X, mask=31,
boxc=fabox*
*2010-06-29 16:55:18 [24139] [22] DEBUG: sql: INSERT INTO kannel_table
(smsc, ts, source, destination, service, url, mask, boxc, status) VALUES
('XXXSMPP', '51', '**91X', '**91X', '', '
http://xxx.xxx.xxx/dlr.php?type=%dkannel_id=%Fmsisdn=%pdlrvalue=%Amessage_id=900629222518-836128',
'31', 'faaabox', '0')*
*
*
*
*
This is not getting inserted into the DB. Is there anything to do with
msg-id-type? Can somebody help me on this?
Thanks
Jinson Abraham
RE: SMPP Delivery Reports Issue
What happens if you try to do the same insert, manually? Do you get an error
message?
== Rene
From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf
Of Jinson
Sent: dinsdag 29 juni 2010 19:00
To: users
Subject: SMPP Delivery Reports Issue
Hello Users,
I've configured a new SMSC on my existing kannel installation. My DLRs are
not working on this SMSC. I'm using mysql DLR storage. I can see the insert
queries in the log but nothing gets inserted into the DB. DLRs are coming on
SMPP properly.
2010-06-29 16:55:18 [24139] [22] DEBUG: priority_flag: 0 = 0x
2010-06-29 16:55:18 [24139] [22] DEBUG: schedule_delivery_time: NULL
2010-06-29 16:55:18 [24139] [22] DEBUG: validity_period: NULL
2010-06-29 16:55:18 [24139] [22] DEBUG: registered_delivery: 1 =
0x0001
2010-06-29 16:55:18 [24139] [22] DEBUG: replace_if_present_flag: 0 =
0x
2010-06-29 16:55:18 [24139] [22] DEBUG: data_coding: 0 = 0x
2010-06-29 16:55:18 [24139] [22] DEBUG: sm_default_msg_id: 0 = 0x
2010-06-29 16:55:18 [24139] [22] DEBUG: sm_length: 8 = 0x0008
2010-06-29 16:55:18 [24139] [22] DEBUG: short_message: Test SMS
2010-06-29 16:55:18 [24139] [22] DEBUG: SMPP PDU dump ends.
2010-06-29 16:55:18 [24139] [22] DEBUG: SMPP[160by2SMPP]: Got PDU:
2010-06-29 16:55:18 [24139] [22] DEBUG: SMPP PDU 0x795bf0 dump:
2010-06-29 16:55:18 [24139] [22] DEBUG: type_name: submit_sm_resp
2010-06-29 16:55:18 [24139] [22] DEBUG: command_id: 2147483652 =
0x8004
2010-06-29 16:55:18 [24139] [22] DEBUG: command_status: 0 = 0x
2010-06-29 16:55:18 [24139] [22] DEBUG: sequence_number: 18 = 0x0012
2010-06-29 16:55:18 [24139] [22] DEBUG: message_id: 51
2010-06-29 16:55:18 [24139] [22] DEBUG: SMPP PDU dump ends.
2010-06-29 16:55:18 [24139] [22] DEBUG: DLR[mysql]: Adding DLR
smsc=160by2SMPP, ts=51, src=91X, dst=91X, mask=31,
boxc=fabox
2010-06-29 16:55:18 [24139] [22] DEBUG: sql: INSERT INTO kannel_table (smsc,
ts, source, destination, service, url, mask, boxc, status) VALUES
('XXXSMPP', '51', '91X', '91X', '',
'http://xxx.xxx.xxx/dlr.php?type=%d
http://xxx.xxx.xxx/dlr.php?type=%25dkannel_id=%25Fmsisdn=%25pdlrvalue=%2
5Amessage_id=900629222518-836128
kannel_id=%Fmsisdn=%pdlrvalue=%Amessage_id=900629222518-836128', '31',
'faaabox', '0')
This is not getting inserted into the DB. Is there anything to do with
msg-id-type? Can somebody help me on this?
Thanks
Jinson Abraham
Re: SMPP Delivery Reports Issue
Hello,
I'm sorry for the confusion. It was getting inserted. But not processing the
DLRs.
I could see the following in my smsbox log
*
*
*010-06-29 17:35:36 [24643] [4] WARNING: No translation found for
id:70 sub:001 dlvrd:001 submit date:1006292305 done date:1006292305
stat:DELIVRD err:000 text:Test from +xx to +xx*
*2010-06-29 17:35:36 [24643] [4] ERROR: request failed*
Thanks
Jinson Abraham
On Tue, Jun 29, 2010 at 10:56 PM, Rene Kluwen rene.klu...@chimit.nl wrote:
What happens if you try to do the same insert, manually? Do you get an
error message?
== Rene
*From:* users-boun...@kannel.org [mailto:users-boun...@kannel.org] *On
Behalf Of *Jinson
*Sent:* dinsdag 29 juni 2010 19:00
*To:* users
*Subject:* SMPP Delivery Reports Issue
Hello Users,
I've configured a new SMSC on my existing kannel installation. My DLRs are
not working on this SMSC. I'm using mysql DLR storage. I can see the insert
queries in the log but nothing gets inserted into the DB. DLRs are coming on
SMPP properly.
*2010-06-29 16:55:18 [24139] [22] DEBUG: priority_flag: 0 = 0x*
*2010-06-29 16:55:18 [24139] [22] DEBUG: schedule_delivery_time: NULL*
*2010-06-29 16:55:18 [24139] [22] DEBUG: validity_period: NULL*
*2010-06-29 16:55:18 [24139] [22] DEBUG: registered_delivery: 1 =
0x0001*
*2010-06-29 16:55:18 [24139] [22] DEBUG: replace_if_present_flag: 0 =
0x*
*2010-06-29 16:55:18 [24139] [22] DEBUG: data_coding: 0 = 0x*
*2010-06-29 16:55:18 [24139] [22] DEBUG: sm_default_msg_id: 0 =
0x*
*2010-06-29 16:55:18 [24139] [22] DEBUG: sm_length: 8 = 0x0008*
*2010-06-29 16:55:18 [24139] [22] DEBUG: short_message: Test SMS*
*2010-06-29 16:55:18 [24139] [22] DEBUG: SMPP PDU dump ends.*
*2010-06-29 16:55:18 [24139] [22] DEBUG: SMPP[160by2SMPP]: Got PDU:*
*2010-06-29 16:55:18 [24139] [22] DEBUG: SMPP PDU 0x795bf0 dump:*
*2010-06-29 16:55:18 [24139] [22] DEBUG: type_name: submit_sm_resp*
*2010-06-29 16:55:18 [24139] [22] DEBUG: command_id: 2147483652 =
0x8004*
*2010-06-29 16:55:18 [24139] [22] DEBUG: command_status: 0 = 0x*
*2010-06-29 16:55:18 [24139] [22] DEBUG: sequence_number: 18 =
0x0012*
*2010-06-29 16:55:18 [24139] [22] DEBUG: message_id: 51*
*2010-06-29 16:55:18 [24139] [22] DEBUG: SMPP PDU dump ends.*
*2010-06-29 16:55:18 [24139] [22] DEBUG: DLR[mysql]: Adding DLR
smsc=160by2SMPP, ts=51, src=91X, dst=91X, mask=31,
boxc=fabox*
*2010-06-29 16:55:18 [24139] [22] DEBUG: sql: INSERT INTO kannel_table
(smsc, ts, source, destination, service, url, mask, boxc, status) VALUES
('XXXSMPP', '51', '91X', '91X', '', '
http://xxx.xxx.xxx/dlr.php?type=%dkannel_id=%Fmsisdn=%pdlrvalue=%Amessage_id=900629222518-836128http://xxx.xxx.xxx/dlr.php?type=%25dkannel_id=%25Fmsisdn=%25pdlrvalue=%25Amessage_id=900629222518-836128',
'31', 'faaabox', '0')*
This is not getting inserted into the DB. Is there anything to do with
msg-id-type? Can somebody help me on this?
Thanks
Jinson Abraham
RE: SMPP Delivery Reports Issue
Then maybe you should indeed set msg-id-type.
Someone else on the list may know what is going on.
I don't see how 51 translates to 70, no matter what base numerical system.
== Rene
From: Jinson [mailto:jin...@mobme.in]
Sent: dinsdag 29 juni 2010 19:37
To: Rene Kluwen
Cc: users
Subject: Re: SMPP Delivery Reports Issue
Hello,
I'm sorry for the confusion. It was getting inserted. But not processing the
DLRs.
I could see the following in my smsbox log
010-06-29 17:35:36 [24643] [4] WARNING: No translation found for
id:70 sub:001 dlvrd:001 submit date:1006292305 done date:1006292305
stat:DELIVRD err:000 text:Test from +xx to +xx
2010-06-29 17:35:36 [24643] [4] ERROR: request failed
Thanks
Jinson Abraham
On Tue, Jun 29, 2010 at 10:56 PM, Rene Kluwen rene.klu...@chimit.nl wrote:
What happens if you try to do the same insert, manually? Do you get an error
message?
== Rene
From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf
Of Jinson
Sent: dinsdag 29 juni 2010 19:00
To: users
Subject: SMPP Delivery Reports Issue
Hello Users,
I've configured a new SMSC on my existing kannel installation. My DLRs are
not working on this SMSC. I'm using mysql DLR storage. I can see the insert
queries in the log but nothing gets inserted into the DB. DLRs are coming on
SMPP properly.
2010-06-29 16:55:18 [24139] [22] DEBUG: priority_flag: 0 = 0x
2010-06-29 16:55:18 [24139] [22] DEBUG: schedule_delivery_time: NULL
2010-06-29 16:55:18 [24139] [22] DEBUG: validity_period: NULL
2010-06-29 16:55:18 [24139] [22] DEBUG: registered_delivery: 1 =
0x0001
2010-06-29 16:55:18 [24139] [22] DEBUG: replace_if_present_flag: 0 =
0x
2010-06-29 16:55:18 [24139] [22] DEBUG: data_coding: 0 = 0x
2010-06-29 16:55:18 [24139] [22] DEBUG: sm_default_msg_id: 0 = 0x
2010-06-29 16:55:18 [24139] [22] DEBUG: sm_length: 8 = 0x0008
2010-06-29 16:55:18 [24139] [22] DEBUG: short_message: Test SMS
2010-06-29 16:55:18 [24139] [22] DEBUG: SMPP PDU dump ends.
2010-06-29 16:55:18 [24139] [22] DEBUG: SMPP[160by2SMPP]: Got PDU:
2010-06-29 16:55:18 [24139] [22] DEBUG: SMPP PDU 0x795bf0 dump:
2010-06-29 16:55:18 [24139] [22] DEBUG: type_name: submit_sm_resp
2010-06-29 16:55:18 [24139] [22] DEBUG: command_id: 2147483652 =
0x8004
2010-06-29 16:55:18 [24139] [22] DEBUG: command_status: 0 = 0x
2010-06-29 16:55:18 [24139] [22] DEBUG: sequence_number: 18 = 0x0012
2010-06-29 16:55:18 [24139] [22] DEBUG: message_id: 51
2010-06-29 16:55:18 [24139] [22] DEBUG: SMPP PDU dump ends.
2010-06-29 16:55:18 [24139] [22] DEBUG: DLR[mysql]: Adding DLR
smsc=160by2SMPP, ts=51, src=91X, dst=91X, mask=31,
boxc=fabox
2010-06-29 16:55:18 [24139] [22] DEBUG: sql: INSERT INTO kannel_table (smsc,
ts, source, destination, service, url, mask, boxc, status) VALUES
('XXXSMPP', '51', '91X', '91X', '',
'http://xxx.xxx.xxx/dlr.php?type=%d
http://xxx.xxx.xxx/dlr.php?type=%25dkannel_id=%25Fmsisdn=%25pdlrvalue=%2
5Amessage_id=900629222518-836128
kannel_id=%Fmsisdn=%pdlrvalue=%Amessage_id=900629222518-836128', '31',
'faaabox', '0')
This is not getting inserted into the DB. Is there anything to do with
msg-id-type? Can somebody help me on this?
Thanks
Jinson Abraham
Re: SMPP Delivery Reports Issue
That was for a different message ID. I tried all the combinations of message ID. But I doubt that the SMSC is acting weired. Please find the logs. *2010-06-29 17:43:23 [24617] [22] DEBUG: SMPP[160by2SMPP]: Sending PDU:* *2010-06-29 17:43:23 [24617] [22] DEBUG: SMPP PDU 0x2c00a580 dump:* *2010-06-29 17:43:23 [24617] [22] DEBUG: type_name: submit_sm* *2010-06-29 17:43:23 [24617] [22] DEBUG: command_id: 4 = 0x0004* *2010-06-29 17:43:23 [24617] [22] DEBUG: command_status: 0 = 0x* *2010-06-29 17:43:23 [24617] [22] DEBUG: sequence_number: 37 = 0x0025* *2010-06-29 17:43:23 [24617] [22] DEBUG: service_type: NULL* *2010-06-29 17:43:23 [24617] [22] DEBUG: source_addr_ton: 1 = 0x0001* *2010-06-29 17:43:23 [24617] [22] DEBUG: source_addr_npi: 1 = 0x0001* *2010-06-29 17:43:23 [24617] [22] DEBUG: source_addr: 918089x* *2010-06-29 17:43:23 [24617] [22] DEBUG: dest_addr_ton: 1 = 0x0001* *2010-06-29 17:43:23 [24617] [22] DEBUG: dest_addr_npi: 1 = 0x0001* *2010-06-29 17:43:23 [24617] [22] DEBUG: destination_addr: Jinson* *2010-06-29 17:43:23 [24617] [22] DEBUG: esm_class: 3 = 0x0003* *2010-06-29 17:43:23 [24617] [22] DEBUG: protocol_id: 0 = 0x* *2010-06-29 17:43:23 [24617] [22] DEBUG: priority_flag: 0 = 0x* *2010-06-29 17:43:23 [24617] [22] DEBUG: schedule_delivery_time: NULL* *2010-06-29 17:43:23 [24617] [22] DEBUG: validity_period: NULL* *2010-06-29 17:43:23 [24617] [22] DEBUG: registered_delivery: 0 = 0x* *2010-06-29 17:43:23 [24617] [24] DEBUG: boxc_receiver: got ack* *2010-06-29 17:43:23 [24617] [22] DEBUG: replace_if_present_flag: 0 = 0x* *2010-06-29 17:43:23 [24617] [22] DEBUG: data_coding: 0 = 0x* *2010-06-29 17:43:23 [24617] [22] DEBUG: sm_default_msg_id: 0 = 0x * *2010-06-29 17:43:23 [24617] [22] DEBUG: sm_length: 14 = 0x000e* *2010-06-29 17:43:23 [24617] [22] DEBUG: short_message: Request Failed* *2010-06-29 17:43:23 [24617] [22] DEBUG: SMPP PDU dump ends.* *2010-06-29 17:43:23 [24617] [22] DEBUG: SMPP[160by2SMPP]: Got PDU:* *2010-06-29 17:43:23 [24617] [22] DEBUG: SMPP PDU 0x2c00a580 dump:* *2010-06-29 17:43:23 [24617] [22] DEBUG: type_name: submit_sm_resp* *2010-06-29 17:43:23 [24617] [22] DEBUG: command_id: 2147483652 = 0x8004* *2010-06-29 17:43:23 [24617] [22] DEBUG: command_status: 11 = 0x000b* *2010-06-29 17:43:23 [24617] [22] DEBUG: sequence_number: 37 = 0x0025* *2010-06-29 17:43:23 [24617] [22] DEBUG: message_id: NULL* *2010-06-29 17:43:23 [24617] [22] DEBUG: SMPP PDU dump ends.* Thanks Jinson Abraham On Tue, Jun 29, 2010 at 11:13 PM, Rene Kluwen rene.klu...@chimit.nl wrote: Then maybe you should indeed set msg-id-type. Someone else on the list may know what is going on. I don’t see how 51 translates to 70, no matter what base numerical system. == Rene *From:* Jinson [mailto:jin...@mobme.in] *Sent:* dinsdag 29 juni 2010 19:37 *To:* Rene Kluwen *Cc:* users *Subject:* Re: SMPP Delivery Reports Issue Hello, I'm sorry for the confusion. It was getting inserted. But not processing the DLRs. I could see the following in my smsbox log *010-06-29 17:35:36 [24643] [4] WARNING: No translation found for id:70 sub:001 dlvrd:001 submit date:1006292305 done date:1006292305 stat:DELIVRD err:000 text:Test from +xx to +xx* *2010-06-29 17:35:36 [24643] [4] ERROR: request failed* Thanks Jinson Abraham On Tue, Jun 29, 2010 at 10:56 PM, Rene Kluwen rene.klu...@chimit.nl wrote: What happens if you try to do the same insert, manually? Do you get an error message? == Rene *From:* users-boun...@kannel.org [mailto:users-boun...@kannel.org] *On Behalf Of *Jinson *Sent:* dinsdag 29 juni 2010 19:00 *To:* users *Subject:* SMPP Delivery Reports Issue Hello Users, I've configured a new SMSC on my existing kannel installation. My DLRs are not working on this SMSC. I'm using mysql DLR storage. I can see the insert queries in the log but nothing gets inserted into the DB. DLRs are coming on SMPP properly. *2010-06-29 16:55:18 [24139] [22] DEBUG: priority_flag: 0 = 0x* *2010-06-29 16:55:18 [24139] [22] DEBUG: schedule_delivery_time: NULL* *2010-06-29 16:55:18 [24139] [22] DEBUG: validity_period: NULL* *2010-06-29 16:55:18 [24139] [22] DEBUG: registered_delivery: 1 = 0x0001* *2010-06-29 16:55:18 [24139] [22] DEBUG: replace_if_present_flag: 0 = 0x* *2010-06-29 16:55:18 [24139] [22] DEBUG: data_coding: 0 = 0x* *2010-06-29 16:55:18 [24139] [22] DEBUG: sm_default_msg_id: 0 = 0x* *2010-06-29 16:55:18 [24139] [22] DEBUG: sm_length: 8 = 0x0008* *2010-06-29 16:55:18 [24139] [22] DEBUG: short_message: Test SMS* *2010-06-29 16:55:18 [24139] [22] DEBUG: SMPP PDU dump ends.* *2010-06-29 16:55:18 [24139] [22] DEBUG: SMPP[160by2SMPP]: Got PDU:* *2010-06-29 16:55:18 [24139] [22] DEBUG:
Re: SMPP Delivery Reports Issue
Hi,
What do you mean not processing? Have you specified a dlr-url? What is
your sendsms url?
Please post also detailed bb logs of the deliver_sm for the DLR along with
some context. It seems that bb doesn't consider it a DLR, instead it thinks
it is an MO SMS, tries to find an sms-service for it and fails.
BR,
Nikos
- Original Message -
From: Jinson
To: Rene Kluwen
Cc: users
Sent: Tuesday, June 29, 2010 8:37 PM
Subject: Re: SMPP Delivery Reports Issue
Hello,
I'm sorry for the confusion. It was getting inserted. But not processing the
DLRs.
I could see the following in my smsbox log
010-06-29 17:35:36 [24643] [4] WARNING: No translation found for
id:70 sub:001 dlvrd:001 submit date:1006292305 done date:1006292305
stat:DELIVRD err:000 text:Test from +xx to +xx
2010-06-29 17:35:36 [24643] [4] ERROR: request failed
Thanks
Jinson Abraham
On Tue, Jun 29, 2010 at 10:56 PM, Rene Kluwen rene.klu...@chimit.nl wrote:
What happens if you try to do the same insert, manually? Do you get an error
message?
== Rene
From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf
Of Jinson
Sent: dinsdag 29 juni 2010 19:00
To: users
Subject: SMPP Delivery Reports Issue
Hello Users,
I've configured a new SMSC on my existing kannel installation. My DLRs are
not working on this SMSC. I'm using mysql DLR storage. I can see the insert
queries in the log but nothing gets inserted into the DB. DLRs are coming on
SMPP properly.
2010-06-29 16:55:18 [24139] [22] DEBUG: priority_flag: 0 = 0x
2010-06-29 16:55:18 [24139] [22] DEBUG: schedule_delivery_time: NULL
2010-06-29 16:55:18 [24139] [22] DEBUG: validity_period: NULL
2010-06-29 16:55:18 [24139] [22] DEBUG: registered_delivery: 1 =
0x0001
2010-06-29 16:55:18 [24139] [22] DEBUG: replace_if_present_flag: 0 =
0x
2010-06-29 16:55:18 [24139] [22] DEBUG: data_coding: 0 = 0x
2010-06-29 16:55:18 [24139] [22] DEBUG: sm_default_msg_id: 0 = 0x
2010-06-29 16:55:18 [24139] [22] DEBUG: sm_length: 8 = 0x0008
2010-06-29 16:55:18 [24139] [22] DEBUG: short_message: Test SMS
2010-06-29 16:55:18 [24139] [22] DEBUG: SMPP PDU dump ends.
2010-06-29 16:55:18 [24139] [22] DEBUG: SMPP[160by2SMPP]: Got PDU:
2010-06-29 16:55:18 [24139] [22] DEBUG: SMPP PDU 0x795bf0 dump:
2010-06-29 16:55:18 [24139] [22] DEBUG: type_name: submit_sm_resp
2010-06-29 16:55:18 [24139] [22] DEBUG: command_id: 2147483652 =
0x8004
2010-06-29 16:55:18 [24139] [22] DEBUG: command_status: 0 = 0x
2010-06-29 16:55:18 [24139] [22] DEBUG: sequence_number: 18 = 0x0012
2010-06-29 16:55:18 [24139] [22] DEBUG: message_id: 51
2010-06-29 16:55:18 [24139] [22] DEBUG: SMPP PDU dump ends.
2010-06-29 16:55:18 [24139] [22] DEBUG: DLR[mysql]: Adding DLR
smsc=160by2SMPP, ts=51, src=91X, dst=91X, mask=31,
boxc=fabox
2010-06-29 16:55:18 [24139] [22] DEBUG: sql: INSERT INTO kannel_table (smsc,
ts, source, destination, service, url, mask, boxc, status) VALUES
('XXXSMPP', '51', '91X', '91X', '',
'http://xxx.xxx.xxx/dlr.php?type=%dkannel_id=%Fmsisdn=%pdlrvalue=%Amessage_id=900629222518-836128',
'31', 'faaabox', '0')
This is not getting inserted into the DB. Is there anything to do with
msg-id-type? Can somebody help me on this?
Thanks
Jinson Abraham
Re: SMPP Delivery Reports Issue
Yes. I have a dlr url and send-sms url works fine for all other SMSCs
configured. The problem is with this particular SMSC
I guess bb doesn't consider DLR and process it as an MO.
Have attached detailed logs.
Thanks
Jinson Abraham
2010/6/29 Nikos Balkanas nbalka...@gmail.com
Hi,
What do you mean not processing? Have you specified a dlr-url? What is
your sendsms url?
Please post also detailed bb logs of the deliver_sm for the DLR along with
some context. It seems that bb doesn't consider it a DLR, instead it thinks
it is an MO SMS, tries to find an sms-service for it and fails.
BR,
Nikos
- Original Message - From: Jinson
To: Rene Kluwen
Cc: users
Sent: Tuesday, June 29, 2010 8:37 PM
Subject: Re: SMPP Delivery Reports Issue
Hello,
I'm sorry for the confusion. It was getting inserted. But not processing
the DLRs.
I could see the following in my smsbox log
010-06-29 17:35:36 [24643] [4] WARNING: No translation found for
id:70 sub:001 dlvrd:001 submit date:1006292305 done date:1006292305
stat:DELIVRD err:000 text:Test from +xx to +xx
2010-06-29 17:35:36 [24643] [4] ERROR: request failed
Thanks
Jinson Abraham
On Tue, Jun 29, 2010 at 10:56 PM, Rene Kluwen rene.klu...@chimit.nl
wrote:
What happens if you try to do the same insert, manually? Do you get an
error message?
== Rene
From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf
Of Jinson
Sent: dinsdag 29 juni 2010 19:00
To: users
Subject: SMPP Delivery Reports Issue
Hello Users,
I've configured a new SMSC on my existing kannel installation. My DLRs are
not working on this SMSC. I'm using mysql DLR storage. I can see the insert
queries in the log but nothing gets inserted into the DB. DLRs are coming on
SMPP properly.
2010-06-29 16:55:18 [24139] [22] DEBUG: priority_flag: 0 = 0x
2010-06-29 16:55:18 [24139] [22] DEBUG: schedule_delivery_time: NULL
2010-06-29 16:55:18 [24139] [22] DEBUG: validity_period: NULL
2010-06-29 16:55:18 [24139] [22] DEBUG: registered_delivery: 1 =
0x0001
2010-06-29 16:55:18 [24139] [22] DEBUG: replace_if_present_flag: 0 =
0x
2010-06-29 16:55:18 [24139] [22] DEBUG: data_coding: 0 = 0x
2010-06-29 16:55:18 [24139] [22] DEBUG: sm_default_msg_id: 0 = 0x
2010-06-29 16:55:18 [24139] [22] DEBUG: sm_length: 8 = 0x0008
2010-06-29 16:55:18 [24139] [22] DEBUG: short_message: Test SMS
2010-06-29 16:55:18 [24139] [22] DEBUG: SMPP PDU dump ends.
2010-06-29 16:55:18 [24139] [22] DEBUG: SMPP[160by2SMPP]: Got PDU:
2010-06-29 16:55:18 [24139] [22] DEBUG: SMPP PDU 0x795bf0 dump:
2010-06-29 16:55:18 [24139] [22] DEBUG: type_name: submit_sm_resp
2010-06-29 16:55:18 [24139] [22] DEBUG: command_id: 2147483652 =
0x8004
2010-06-29 16:55:18 [24139] [22] DEBUG: command_status: 0 = 0x
2010-06-29 16:55:18 [24139] [22] DEBUG: sequence_number: 18 = 0x0012
2010-06-29 16:55:18 [24139] [22] DEBUG: message_id: 51
2010-06-29 16:55:18 [24139] [22] DEBUG: SMPP PDU dump ends.
2010-06-29 16:55:18 [24139] [22] DEBUG: DLR[mysql]: Adding DLR
smsc=160by2SMPP, ts=51, src=91X, dst=91X, mask=31,
boxc=fabox
2010-06-29 16:55:18 [24139] [22] DEBUG: sql: INSERT INTO kannel_table
(smsc, ts, source, destination, service, url, mask, boxc, status) VALUES
('XXXSMPP', '51', '91X', '91X', '', '
http://xxx.xxx.xxx/dlr.php?type=%dkannel_id=%Fmsisdn=%pdlrvalue=%Amessage_id=900629222518-836128',
'31', 'faaabox', '0')
This is not getting inserted into the DB. Is there anything to do with
msg-id-type? Can somebody help me on this?
Thanks
Jinson Abraham
2010-06-29 17:50:04 [24617] [22] DEBUG: SMPP[mysmpp1]: Sending PDU:
2010-06-29 17:50:04 [24617] [22] DEBUG: SMPP PDU 0x7d2df0 dump:
2010-06-29 17:50:04 [24617] [22] DEBUG: type_name: submit_sm
2010-06-29 17:50:04 [24617] [22] DEBUG: command_id: 4 = 0x0004
2010-06-29 17:50:04 [24617] [22] DEBUG: command_status: 0 = 0x
2010-06-29 17:50:04 [24617] [22] DEBUG: sequence_number: 53 = 0x0035
2010-06-29 17:50:04 [24617] [22] DEBUG: service_type: NULL
2010-06-29 17:50:04 [24617] [22] DEBUG: source_addr_ton: 5 = 0x0005
2010-06-29 17:50:04 [24617] [22] DEBUG: source_addr_npi: 0 = 0x
2010-06-29 17:50:04 [24617] [22] DEBUG: source_addr: Jinson
2010-06-29 17:50:04 [24617] [22] DEBUG: dest_addr_ton: 2 = 0x0002
2010-06-29 17:50:04 [24617] [22] DEBUG: dest_addr_npi: 1 = 0x0001
2010-06-29 17:50:04 [24617] [22] DEBUG: destination_addr: 9199x
2010-06-29 17:50:04 [24617] [22] DEBUG: esm_class: 3 = 0x0003
2010-06-29 17:50:04 [24617] [22] DEBUG: protocol_id: 0 = 0x
2010-06-29 17:50:04 [24617] [22] DEBUG: priority_flag: 0 = 0x
2010-06-29 17:50:04 [24617] [22] DEBUG: schedule_delivery_time: NULL
2010-06-29 17:50:04 [24617] [22] DEBUG: validity_period: NULL
2010-06-29 17:50:04
RE: SMPP Delivery Reports Issue
It looks like your smsc sends the wrong esm_class for delivery receipts.
== Rene
From: Jinson [mailto:jin...@mobme.in]
Sent: dinsdag 29 juni 2010 20:10
To: Nikos Balkanas
Cc: Rene Kluwen; users
Subject: Re: SMPP Delivery Reports Issue
Yes. I have a dlr url and send-sms url works fine for all other SMSCs
configured. The problem is with this particular SMSC
I guess bb doesn't consider DLR and process it as an MO. Have attached
detailed logs.
Thanks
Jinson Abraham
2010/6/29 Nikos Balkanas nbalka...@gmail.com
Hi,
What do you mean not processing? Have you specified a dlr-url? What is
your sendsms url?
Please post also detailed bb logs of the deliver_sm for the DLR along with
some context. It seems that bb doesn't consider it a DLR, instead it thinks
it is an MO SMS, tries to find an sms-service for it and fails.
BR,
Nikos
- Original Message - From: Jinson
To: Rene Kluwen
Cc: users
Sent: Tuesday, June 29, 2010 8:37 PM
Subject: Re: SMPP Delivery Reports Issue
Hello,
I'm sorry for the confusion. It was getting inserted. But not processing the
DLRs.
I could see the following in my smsbox log
010-06-29 17:35:36 [24643] [4] WARNING: No translation found for
id:70 sub:001 dlvrd:001 submit date:1006292305 done date:1006292305
stat:DELIVRD err:000 text:Test from +xx to +xx
2010-06-29 17:35:36 [24643] [4] ERROR: request failed
Thanks
Jinson Abraham
On Tue, Jun 29, 2010 at 10:56 PM, Rene Kluwen rene.klu...@chimit.nl wrote:
What happens if you try to do the same insert, manually? Do you get an error
message?
== Rene
From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf
Of Jinson
Sent: dinsdag 29 juni 2010 19:00
To: users
Subject: SMPP Delivery Reports Issue
Hello Users,
I've configured a new SMSC on my existing kannel installation. My DLRs are
not working on this SMSC. I'm using mysql DLR storage. I can see the insert
queries in the log but nothing gets inserted into the DB. DLRs are coming on
SMPP properly.
2010-06-29 16:55:18 [24139] [22] DEBUG: priority_flag: 0 = 0x
2010-06-29 16:55:18 [24139] [22] DEBUG: schedule_delivery_time: NULL
2010-06-29 16:55:18 [24139] [22] DEBUG: validity_period: NULL
2010-06-29 16:55:18 [24139] [22] DEBUG: registered_delivery: 1 =
0x0001
2010-06-29 16:55:18 [24139] [22] DEBUG: replace_if_present_flag: 0 =
0x
2010-06-29 16:55:18 [24139] [22] DEBUG: data_coding: 0 = 0x
2010-06-29 16:55:18 [24139] [22] DEBUG: sm_default_msg_id: 0 = 0x
2010-06-29 16:55:18 [24139] [22] DEBUG: sm_length: 8 = 0x0008
2010-06-29 16:55:18 [24139] [22] DEBUG: short_message: Test SMS
2010-06-29 16:55:18 [24139] [22] DEBUG: SMPP PDU dump ends.
2010-06-29 16:55:18 [24139] [22] DEBUG: SMPP[160by2SMPP]: Got PDU:
2010-06-29 16:55:18 [24139] [22] DEBUG: SMPP PDU 0x795bf0 dump:
2010-06-29 16:55:18 [24139] [22] DEBUG: type_name: submit_sm_resp
2010-06-29 16:55:18 [24139] [22] DEBUG: command_id: 2147483652 =
0x8004
2010-06-29 16:55:18 [24139] [22] DEBUG: command_status: 0 = 0x
2010-06-29 16:55:18 [24139] [22] DEBUG: sequence_number: 18 = 0x0012
2010-06-29 16:55:18 [24139] [22] DEBUG: message_id: 51
2010-06-29 16:55:18 [24139] [22] DEBUG: SMPP PDU dump ends.
2010-06-29 16:55:18 [24139] [22] DEBUG: DLR[mysql]: Adding DLR
smsc=160by2SMPP, ts=51, src=91X, dst=91X, mask=31,
boxc=fabox
2010-06-29 16:55:18 [24139] [22] DEBUG: sql: INSERT INTO kannel_table (smsc,
ts, source, destination, service, url, mask, boxc, status) VALUES
('XXXSMPP', '51', '91X', '91X', '',
'http://xxx.xxx.xxx/dlr.php?type=%d
http://xxx.xxx.xxx/dlr.php?type=%25dkannel_id=%25Fmsisdn=%25pdlrvalue=%2
5Amessage_id=900629222518-836128
kannel_id=%Fmsisdn=%pdlrvalue=%Amessage_id=900629222518-836128', '31',
'faaabox', '0')
This is not getting inserted into the DB. Is there anything to do with
msg-id-type? Can somebody help me on this?
Thanks
Jinson Abraham
RE: SMPP Delivery Reports Issue
It should be 2C hex or more.
From: Jinson [mailto:jin...@mobme.in]
Sent: dinsdag 29 juni 2010 20:21
To: Rene Kluwen
Cc: Nikos Balkanas; users
Subject: Re: SMPP Delivery Reports Issue
Whats the correct esm_class for DLRs?
Thanks
Jinson Abraham
On Tue, Jun 29, 2010 at 11:49 PM, Rene Kluwen rene.klu...@chimit.nl wrote:
It looks like your smsc sends the wrong esm_class for delivery receipts.
== Rene
From: Jinson [mailto:jin...@mobme.in]
Sent: dinsdag 29 juni 2010 20:10
To: Nikos Balkanas
Cc: Rene Kluwen; users
Subject: Re: SMPP Delivery Reports Issue
Yes. I have a dlr url and send-sms url works fine for all other SMSCs
configured. The problem is with this particular SMSC
I guess bb doesn't consider DLR and process it as an MO. Have attached
detailed logs.
Thanks
Jinson Abraham
2010/6/29 Nikos Balkanas nbalka...@gmail.com
Hi,
What do you mean not processing? Have you specified a dlr-url? What is
your sendsms url?
Please post also detailed bb logs of the deliver_sm for the DLR along with
some context. It seems that bb doesn't consider it a DLR, instead it thinks
it is an MO SMS, tries to find an sms-service for it and fails.
BR,
Nikos
- Original Message - From: Jinson
To: Rene Kluwen
Cc: users
Sent: Tuesday, June 29, 2010 8:37 PM
Subject: Re: SMPP Delivery Reports Issue
Hello,
I'm sorry for the confusion. It was getting inserted. But not processing the
DLRs.
I could see the following in my smsbox log
010-06-29 17:35:36 [24643] [4] WARNING: No translation found for
id:70 sub:001 dlvrd:001 submit date:1006292305 done date:1006292305
stat:DELIVRD err:000 text:Test from +xx to +xx
2010-06-29 17:35:36 [24643] [4] ERROR: request failed
Thanks
Jinson Abraham
On Tue, Jun 29, 2010 at 10:56 PM, Rene Kluwen rene.klu...@chimit.nl wrote:
What happens if you try to do the same insert, manually? Do you get an error
message?
== Rene
From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf
Of Jinson
Sent: dinsdag 29 juni 2010 19:00
To: users
Subject: SMPP Delivery Reports Issue
Hello Users,
I've configured a new SMSC on my existing kannel installation. My DLRs are
not working on this SMSC. I'm using mysql DLR storage. I can see the insert
queries in the log but nothing gets inserted into the DB. DLRs are coming on
SMPP properly.
2010-06-29 16:55:18 [24139] [22] DEBUG: priority_flag: 0 = 0x
2010-06-29 16:55:18 [24139] [22] DEBUG: schedule_delivery_time: NULL
2010-06-29 16:55:18 [24139] [22] DEBUG: validity_period: NULL
2010-06-29 16:55:18 [24139] [22] DEBUG: registered_delivery: 1 =
0x0001
2010-06-29 16:55:18 [24139] [22] DEBUG: replace_if_present_flag: 0 =
0x
2010-06-29 16:55:18 [24139] [22] DEBUG: data_coding: 0 = 0x
2010-06-29 16:55:18 [24139] [22] DEBUG: sm_default_msg_id: 0 = 0x
2010-06-29 16:55:18 [24139] [22] DEBUG: sm_length: 8 = 0x0008
2010-06-29 16:55:18 [24139] [22] DEBUG: short_message: Test SMS
2010-06-29 16:55:18 [24139] [22] DEBUG: SMPP PDU dump ends.
2010-06-29 16:55:18 [24139] [22] DEBUG: SMPP[160by2SMPP]: Got PDU:
2010-06-29 16:55:18 [24139] [22] DEBUG: SMPP PDU 0x795bf0 dump:
2010-06-29 16:55:18 [24139] [22] DEBUG: type_name: submit_sm_resp
2010-06-29 16:55:18 [24139] [22] DEBUG: command_id: 2147483652 =
0x8004
2010-06-29 16:55:18 [24139] [22] DEBUG: command_status: 0 = 0x
2010-06-29 16:55:18 [24139] [22] DEBUG: sequence_number: 18 = 0x0012
2010-06-29 16:55:18 [24139] [22] DEBUG: message_id: 51
2010-06-29 16:55:18 [24139] [22] DEBUG: SMPP PDU dump ends.
2010-06-29 16:55:18 [24139] [22] DEBUG: DLR[mysql]: Adding DLR
smsc=160by2SMPP, ts=51, src=91X, dst=91X, mask=31,
boxc=fabox
2010-06-29 16:55:18 [24139] [22] DEBUG: sql: INSERT INTO kannel_table (smsc,
ts, source, destination, service, url, mask, boxc, status) VALUES
('XXXSMPP', '51', '91X', '91X', '',
'http://xxx.xxx.xxx/dlr.php?type=%d
http://xxx.xxx.xxx/dlr.php?type=%25dkannel_id=%25Fmsisdn=%25pdlrvalue=%2
5Amessage_id=900629222518-836128
kannel_id=%Fmsisdn=%pdlrvalue=%Amessage_id=900629222518-836128', '31',
'faaabox', '0')
This is not getting inserted into the DB. Is there anything to do with
msg-id-type? Can somebody help me on this?
Thanks
Jinson Abraham
Costs
Is there any documentation on the ongoing costs of running the gateway? Thanks, Jeff
RE: ESME Session
I have personely checked that user created under smpp box can create n number of session via any smpp client (40 session tested). Regards Tapan Thapa On Tue, 29 Jun 2010 18:58 IST Rene Kluwen wrote: I think current SMPP box version only allows for one session per user at the same time. From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of Sandesh Waman // Viva Sent: dinsdag 29 juni 2010 12:51 To: Kannel Users Subject: ESME Session Dear All, I am using SMPP BOX but getting some error. Scenario: I am using kannel as client and SMPPBOX as server. When I bind accounts for more than 1 instance on kannel and starting the kannel, then Unknown sessions on SMPP BOX (ESME) get increase automatically. Is this a bug or I have done any mistake. Waiting for reply. Thanks in advance, Sandesh
Re: ESME Session
Thanks for reply, But I am using license SMPP BOX from last couple of months and getting this error. The extra unknown ESME sessions got removed after restarting SMPP BOX everytime. Please any more solution for this. Thanks Regards, Sandesh On Wed, Jun 30, 2010 at 8:02 AM, T.K.Thapa tapan_thapa2...@yahoo.comwrote: I have personely checked that user created under smpp box can create n number of session via any smpp client (40 session tested). Regards Tapan Thapa On Tue, 29 Jun 2010 18:58 IST Rene Kluwen wrote: I think current SMPP box version only allows for one session per user at the same time. From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of Sandesh Waman // Viva Sent: dinsdag 29 juni 2010 12:51 To: Kannel Users Subject: ESME Session Dear All, I am using SMPP BOX but getting some error. Scenario: I am using kannel as client and SMPPBOX as server. When I bind accounts for more than 1 instance on kannel and starting the kannel, then Unknown sessions on SMPP BOX (ESME) get increase automatically. Is this a bug or I have done any mistake. Waiting for reply. Thanks in advance, Sandesh
Re: ESME Session
Hi, You mean license, as in commercial? We are not supporting commercial versions of SMPPBox. Please address provider for support. BR, Nikos - Original Message - From: Sandesh Waman // Viva To: T.K.Thapa ; users@kannel.org Sent: Wednesday, June 30, 2010 7:25 AM Subject: Re: ESME Session Thanks for reply, But I am using license SMPP BOX from last couple of months and getting this error. The extra unknown ESME sessions got removed after restarting SMPP BOX everytime. Please any more solution for this. Thanks Regards, Sandesh On Wed, Jun 30, 2010 at 8:02 AM, T.K.Thapa tapan_thapa2...@yahoo.com wrote: I have personely checked that user created under smpp box can create n number of session via any smpp client (40 session tested). Regards Tapan Thapa On Tue, 29 Jun 2010 18:58 IST Rene Kluwen wrote: I think current SMPP box version only allows for one session per user at the same time. From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of Sandesh Waman // Viva Sent: dinsdag 29 juni 2010 12:51 To: Kannel Users Subject: ESME Session Dear All, I am using SMPP BOX but getting some error. Scenario: I am using kannel as client and SMPPBOX as server. When I bind accounts for more than 1 instance on kannel and starting the kannel, then Unknown sessions on SMPP BOX (ESME) get increase automatically. Is this a bug or I have done any mistake. Waiting for reply. Thanks in advance, Sandesh
Re: Costs
Hi, Gateway is open source without any licenses. It doesn't cost a thing to use it. Of course you have costs associated with the SMScs you are using, but these are subject to your contract with them, not kannel. BR, Nikos - Original Message - From: Jeff Bergamotto jeff.bergamo...@gmail.com To: users@kannel.org Sent: Wednesday, June 30, 2010 1:04 AM Subject: Costs Is there any documentation on the ongoing costs of running the gateway? Thanks, Jeff
Re: quick questions about Kannel
Hi, 1) Yes 2) Yes 3) Transiently only in the queue. For outgoing check sqlbox. Read User's guide from http://www.kannel.org BR, Nikos - Original Message - From: Aldo Zavala a...@cleartalk.net To: users@kannel.org Sent: Wednesday, June 30, 2010 12:27 AM Subject: quick questions about Kannel 1.- Is it possible to connect with multiple SMC Providers using the SMPP 3.4 at the same time? 2.- Is it possible to setup inbound and outbound rules for SMS Delivery? For instance choose the closer SMC provider to deliver certain message based in destination MDN. 3.-Is it possible to store in and out SMS's in a database? Thanks, Aldo Zavala
