Alphanumeric source
Dear List, Is there anything wrong with my kannel configuration? Alphanumeric doesn't go. The url is http://localhost:13001/cgi-bin/sendsms?username=user1 http://localhost:13001/cgi-bin/sendsms?username=user1password=pass1from=m yserviceto=123456789011text=check%20sendercharset=UTF-16BEmclass=2codin g=2pid=0priority=3smsc=smsc1 password=pass1from=myserviceto=123456789011text=check%20sendercharset=U TF-16BEmclass=2coding=2pid=0priority=3smsc=smsc1 also tried this url http://localhost:13001/cgi-bin/sendsms?username=user1 http://localhost:13001/cgi-bin/sendsms?username=user1password=pass1from=m yserviceto=123456789011text=check%20sender password=pass1from=myserviceto=123456789011text=check%20sender Here are the logs of a single request: -- 2009-01-19 16:23:57 [5387] [6] DEBUG: SMPP[BSNL]: Manually forced source addr ton = 5, source add npi = 0 2009-01-19 16:23:57 [5387] [6] DEBUG: SMPP[BSNL]: Manually forced dest addr ton = 1, dest add npi = 1 2009-01-19 16:23:57 [5387] [6] DEBUG: SMPP[BSNL]: Sending PDU: 2009-01-19 16:23:57 [5387] [6] DEBUG: SMPP PDU 0xafc00740 dump: 2009-01-19 16:23:57 [5387] [6] DEBUG: type_name: submit_sm 2009-01-19 16:23:57 [5387] [6] DEBUG: command_id: 4 = 0x0004 2009-01-19 16:23:57 [5387] [6] DEBUG: command_status: 0 = 0x 2009-01-19 16:23:57 [5387] [6] DEBUG: sequence_number: 35 = 0x0023 2009-01-19 16:23:57 [5387] [6] DEBUG: service_type: NULL 2009-01-19 16:23:57 [5387] [6] DEBUG: source_addr_ton: 5 = 0x0005 2009-01-19 16:23:57 [5387] [6] DEBUG: source_addr_npi: 0 = 0x 2009-01-19 16:23:57 [5387] [6] DEBUG: source_addr: myservice 2009-01-19 16:23:57 [5387] [6] DEBUG: dest_addr_ton: 1 = 0x0001 2009-01-19 16:23:57 [5387] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2009-01-19 16:23:57 [5387] [6] DEBUG: destination_addr: 123456789011 2009-01-19 16:23:57 [5387] [6] DEBUG: esm_class: 3 = 0x0003 2009-01-19 16:23:57 [5387] [6] DEBUG: protocol_id: 0 = 0x 2009-01-19 16:23:57 [5387] [6] DEBUG: priority_flag: 3 = 0x0003 2009-01-19 16:23:57 [5387] [6] DEBUG: schedule_delivery_time: NULL 2009-01-19 16:23:57 [5387] [6] DEBUG: validity_period: NULL 2009-01-19 16:23:57 [5387] [6] DEBUG: registered_delivery: 0 = 0x 2009-01-19 16:23:57 [5387] [6] DEBUG: replace_if_present_flag: 0 = 0x 2009-01-19 16:23:57 [5387] [6] DEBUG: data_coding: 26 = 0x001a 2009-01-19 16:23:57 [5387] [6] DEBUG: sm_default_msg_id: 0 = 0x 2009-01-19 16:23:57 [5387] [6] DEBUG: sm_length: 12 = 0x000c 2009-01-19 16:23:57 [5387] [6] DEBUG: short_message: check sender 2009-01-19 16:23:57 [5387] [6] DEBUG: SMPP PDU dump ends. 2009-01-19 16:23:57 [5387] [6] DEBUG: SMPP[BSNL]: Got PDU: 2009-01-19 16:23:57 [5387] [6] DEBUG: SMPP PDU 0xafc00758 dump: 2009-01-19 16:23:57 [5387] [6] DEBUG: type_name: submit_sm_resp 2009-01-19 16:23:57 [5387] [6] DEBUG: command_id: 2147483652 = 0x8004 2009-01-19 16:23:57 [5387] [6] DEBUG: command_status: 10 = 0x000a 2009-01-19 16:23:57 [5387] [6] DEBUG: sequence_number: 35 = 0x0023 2009-01-19 16:23:57 [5387] [6] DEBUG: message_id: NULL 2009-01-19 16:23:57 [5387] [6] DEBUG: SMPP PDU dump ends. 2009-01-19 16:23:57 [5387] [6] ERROR: SMPP[BSNL]: SMSC returned error code 0x000a (Invalid Source Address) in response to submit_sm. Here is my configuration: - # SMSC SMPP #my-number = x group = smsc smsc = smpp smsc-id = smsc1 host = host-ip port = port log-file = /kannel/log/kannel.log transceiver-mode = 0 alt-dcs = true receive-port = port smsc-username = smsc-password = system-type = address-range = source-addr-ton = 5 source-addr-npi = 0 dest-addr-ton = 1 dest-addr-npi = 1 msg-id-type = 0x01 throughput = 30 max-pending-submits = 5 enquire-link-interval= 60 # SMSBOX SETUP group = smsbox bearerbox-host = localhost sendsms-port = 13001 log-file = /kannel/log/smsbox.log log-level = 0 access-log = /kannel/log/access.log # SEND-SMS USERS group = sendsms-user username = user1 password = pass1 dlr-url = http://localhost:/myservice/dlrstatus?oa=%pda=%Psmsc=%itype=%d; max-messages = 3 concatenation = true The regular values for ton and npi are 1 and 1. Any help would be appreciated. TIA, Regards, Surya
Re: DLR DB processing
Hi Nikos, PostgreSQL was always most reliable for me, I had some post-crash data loss experience with 3.x series that thankfully kept me away from the mess called MySQL since then. With recent improvements after 8.2, PostgreSQL is performing either very close to MySQL or outperforming it in some cases. SQLite is probably another good choice if you don't plan scaling it up to multiple bearerbox processes writing to the same database. libsdb is essentially a multiplexing database abstraction layer if I'm not wrong; so that's probably not what you want. And please, I beg you, don't use Oracle. Using Oracle should be made a crime against humanity in as many countries as possible. -HTH On Thu, 2009-01-15 at 20:03 +0200, Nikos Balkanas wrote: Hi, I am considering using a DB for DLR storage. Up till now I was using internal DLRs. Of the many options supported, (Mysql, PostgresSQL, Oracle, LibSdb, sqlbox, sqllite) which one would you consider best suited for bulk SMS, in terms of performance and reliability. If you could also give a one liner for your choice, it would be most appreciated. I thing it is fair to say, that internal is the fastest and least reliable of all. Thanx Nikos -- Enver
Re: Alphanumeric source
Hi, kannel works perfect. TON/NPI 5/0 is exactly what it has to set when you use alphanum sender. TON/NPI 1/1 says e.164 number and myservice is not really e.164 ;-) So, looks like your service provider hasn't activated alphanum sender for your account or doesn't support it for the target network. Regards Falko Am 19.01.2009 um 13:19 schrieb Surya: Dear List, Is there anything wrong with my kannel configuration? Alphanumeric doesn’t go. The url is http://localhost:13001/cgi-bin/sendsms?username=user1password=pass1from=myserviceto=123456789011text=check%20sendercharset=UTF-16BEmclass=2coding=2pid=0priority=3smsc=smsc1 also tried this url http://localhost:13001/cgi-bin/sendsms?username=user1password=pass1from=myserviceto=123456789011text=check%20sender Here are the logs of a single request: -- 2009-01-19 16:23:57 [5387] [6] DEBUG: SMPP[BSNL]: Manually forced source addr ton = 5, source add npi = 0 2009-01-19 16:23:57 [5387] [6] DEBUG: SMPP[BSNL]: Manually forced dest addr ton = 1, dest add npi = 1 2009-01-19 16:23:57 [5387] [6] DEBUG: SMPP[BSNL]: Sending PDU: 2009-01-19 16:23:57 [5387] [6] DEBUG: SMPP PDU 0xafc00740 dump: 2009-01-19 16:23:57 [5387] [6] DEBUG: type_name: submit_sm 2009-01-19 16:23:57 [5387] [6] DEBUG: command_id: 4 = 0x0004 2009-01-19 16:23:57 [5387] [6] DEBUG: command_status: 0 = 0x 2009-01-19 16:23:57 [5387] [6] DEBUG: sequence_number: 35 = 0x0023 2009-01-19 16:23:57 [5387] [6] DEBUG: service_type: NULL 2009-01-19 16:23:57 [5387] [6] DEBUG: source_addr_ton: 5 = 0x0005 2009-01-19 16:23:57 [5387] [6] DEBUG: source_addr_npi: 0 = 0x 2009-01-19 16:23:57 [5387] [6] DEBUG: source_addr: myservice 2009-01-19 16:23:57 [5387] [6] DEBUG: dest_addr_ton: 1 = 0x0001 2009-01-19 16:23:57 [5387] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2009-01-19 16:23:57 [5387] [6] DEBUG: destination_addr: 123456789011 2009-01-19 16:23:57 [5387] [6] DEBUG: esm_class: 3 = 0x0003 2009-01-19 16:23:57 [5387] [6] DEBUG: protocol_id: 0 = 0x 2009-01-19 16:23:57 [5387] [6] DEBUG: priority_flag: 3 = 0x0003 2009-01-19 16:23:57 [5387] [6] DEBUG: schedule_delivery_time: NULL 2009-01-19 16:23:57 [5387] [6] DEBUG: validity_period: NULL 2009-01-19 16:23:57 [5387] [6] DEBUG: registered_delivery: 0 = 0x 2009-01-19 16:23:57 [5387] [6] DEBUG: replace_if_present_flag: 0 = 0x 2009-01-19 16:23:57 [5387] [6] DEBUG: data_coding: 26 = 0x001a 2009-01-19 16:23:57 [5387] [6] DEBUG: sm_default_msg_id: 0 = 0x 2009-01-19 16:23:57 [5387] [6] DEBUG: sm_length: 12 = 0x000c 2009-01-19 16:23:57 [5387] [6] DEBUG: short_message: check sender 2009-01-19 16:23:57 [5387] [6] DEBUG: SMPP PDU dump ends. 2009-01-19 16:23:57 [5387] [6] DEBUG: SMPP[BSNL]: Got PDU: 2009-01-19 16:23:57 [5387] [6] DEBUG: SMPP PDU 0xafc00758 dump: 2009-01-19 16:23:57 [5387] [6] DEBUG: type_name: submit_sm_resp 2009-01-19 16:23:57 [5387] [6] DEBUG: command_id: 2147483652 = 0x8004 2009-01-19 16:23:57 [5387] [6] DEBUG: command_status: 10 = 0x000a 2009-01-19 16:23:57 [5387] [6] DEBUG: sequence_number: 35 = 0x0023 2009-01-19 16:23:57 [5387] [6] DEBUG: message_id: NULL 2009-01-19 16:23:57 [5387] [6] DEBUG: SMPP PDU dump ends. 2009-01-19 16:23:57 [5387] [6] ERROR: SMPP[BSNL]: SMSC returned error code 0x000a (Invalid Source Address) in response to submit_sm. Here is my configuration: - # SMSC SMPP #my-number = x group = smsc smsc = smpp smsc-id = smsc1 host = host-ip port = port log-file = /kannel/log/kannel.log transceiver-mode = 0 alt-dcs = true receive-port = port smsc-username = smsc-password = system-type = address-range = source-addr-ton = 5 source-addr-npi = 0 dest-addr-ton = 1 dest-addr-npi = 1 msg-id-type = 0x01 throughput = 30 max-pending-submits = 5 enquire-link-interval= 60 # SMSBOX SETUP group = smsbox bearerbox-host = localhost sendsms-port = 13001 log-file = /kannel/log/smsbox.log log-level = 0 access-log = /kannel/log/access.log # SEND-SMS USERS group = sendsms-user username = user1 password = pass1 dlr-url = http://localhost:/myservice/dlrstatus?oa=%pda= %Psmsc=%itype=%d max-messages = 3 concatenation = true The regular values for ton and npi are 1 and 1. Any help would be appreciated. TIA, Regards, Surya
kannel stops with 1.4.2
Hi Users, My bearerbox panics: 2009-01-18 20:36:32 [8499] [7] PANIC: octstr_format format string syntax error. 2009-01-18 20:36:32 [8499] [7] PANIC: ./bearerbox(gw_panic+0xc2) [0x80ca042] 2009-01-18 20:36:32 [8499] [7] PANIC: ./bearerbox(octstr_format_valist_real+0x1a8) [0x80ce1b8] 2009-01-18 20:36:32 [8499] [7] PANIC: ./bearerbox(octstr_format+0x1b) [0x80ceafb] 2009-01-18 20:36:32 [8499] [7] PANIC: ./bearerbox [0x8085d0c] 2009-01-18 20:36:32 [8499] [7] PANIC: ./bearerbox [0x8086ce0] 2009-01-18 20:36:32 [8499] [7] PANIC: ./bearerbox [0x8088619] 2009-01-18 20:36:32 [8499] [7] PANIC: ./bearerbox [0x80c09c1] 2009-01-18 20:36:32 [8499] [7] PANIC: /lib/libpthread.so.0 [0xbc145b] 2009-01-18 20:36:32 [8499] [7] PANIC: /lib/libc.so.6(clone+0x5e) [0xb18e5e] 2009-01-18 20:36:32 [8511] [0] ERROR: Connection closed by the bearerbox. 2009-01-18 20:36:32 [8511] [0] INFO: Received (and handled?) 15 requests in 7 seconds (2.14 per second) 2009-01-18 20:36:32 [8511] [0] INFO: Kannel smsbox terminating. [1]- Exit 1 ./bearerbox -v 1 kannel.conf [2]+ Done./smsbox -v 1 kannel.conf Please let me know what information you need to assist me. Any help would be appreciated. Regards, Surya
Re: DLR DB processing
tend to agreed for oracle .. when you call their tech support you get only standard response - check our FAQ db ... Enver ALTIN wrote: Hi Nikos, PostgreSQL was always most reliable for me, I had some post-crash data loss experience with 3.x series that thankfully kept me away from the mess called MySQL since then. With recent improvements after 8.2, PostgreSQL is performing either very close to MySQL or outperforming it in some cases. SQLite is probably another good choice if you don't plan scaling it up to multiple bearerbox processes writing to the same database. libsdb is essentially a multiplexing database abstraction layer if I'm not wrong; so that's probably not what you want. And please, I beg you, don't use Oracle. Using Oracle should be made a crime against humanity in as many countries as possible. -HTH On Thu, 2009-01-15 at 20:03 +0200, Nikos Balkanas wrote: Hi, I am considering using a DB for DLR storage. Up till now I was using internal DLRs. Of the many options supported, (Mysql, PostgresSQL, Oracle, LibSdb, sqlbox, sqllite) which one would you consider best suited for bulk SMS, in terms of performance and reliability. If you could also give a one liner for your choice, it would be most appreciated. I thing it is fair to say, that internal is the fastest and least reliable of all. Thanx Nikos
[Fwd: Re: DLR DB processing]
---BeginMessage--- :) every sql db has its advantages. I use PostgreSQL in a view its stability and features I cant find in MySQL or Oracle ... In short rules on insert/update and MO service descriptions stored in the db make my life easier. We simply avoid http requests because we handle the MO on insert ... :) And we have implemented the MT charging of value added services very easily. I am quite sure there are similar or even better implementations of MySQL , Oracle or MS SQL. RE: setting sqlbox to handle all the traffic, its good idea to contact the current sqlbox maintainer, there were a lot of improvements these days. I use old patched version of the sqlbox. In short, you set the sqlbox to listen to the bearerbox, and the smsbox to listen to the sqlbox port instead to the bearerbox .. :) the following scheme is not full but i hope you will get the idea .. SMSC-bearerbox:port-sqlbox:port-smsbox-http:sendsmsport:bearerbox-SMSC cheers Nikos Balkanas wrote: Hi Seikath, Postgress might be a bit on the heavy side for plain DLR storage. I tend to agree with you about SQLbox being a better choice for DLRs. Thanx for the input, Nikos - Original Message - From: seikath seik...@gmail.com To: Nikos Balkanas nbalka...@gmail.com Cc: users@kannel.org Sent: Thursday, January 15, 2009 11:03 PM Subject: Re: DLR DB processing sql and postgresql and rules on insert /its pgsql only feature/ set the sqlbox to handle MT and DLR and set the postgresql to allow like 2000 concurrent connections - you need some RAM for that ... Nikos Balkanas wrote: Hi, I am considering using a DB for DLR storage. Up till now I was using internal DLRs. Of the many options supported, (Mysql, PostgresSQL, Oracle, LibSdb, sqlbox, sqllite) which one would you consider best suited for bulk SMS, in terms of performance and reliability. If you could also give a one liner for your choice, it would be most appreciated. I thing it is fair to say, that internal is the fastest and least reliable of all. Thanx Nikos ---End Message---
Re: [ANNOUNCE] Kannel 1.4.2 stable release available
Congratulations! On Tue, 2009-01-13 at 00:47 +0100, Stipe Tolj wrote: The Kannel Group is pleased to announce the availability of Kannel 1.4.2 stable release via our web site at URL -- Enver
