SMS reciving problem
I use kannel: Kannel bearerbox version `1.4.1'. Build `Oct 16 2006 10:48:53', compiler `4.1.1 20060525 (Red Hat 4.1.1-1)'. System Linux, release 2.6.19-1.2288.2.4.fc5, version #1 SMP Sun Mar 4 15:57:52 EST 2007, machine x86_64. Hostname h8.dbweb.ee, IP 217.159.233.174. Libxml version 2.6.23. Using SQLite 2.8.17. Using native malloc. My kannel is connected to operator SMSC-es with two VPN IPSec tunnels. First tunnel: My kannel eth1: *.*.*.55 - VPN LAN: *.*.*.53 My VPN GW: 13.180.29.56 - Tunnel - Operator IPV GW: *.*.*.15 - Operator SMSC: *.*.*.119. I use it to send SMSes out. Second tunnel: My kannel eth1: *.*.*.55 - VPN LAN: *.*.*.53 My VPN GW: 13.180.29.56 - Tunnel - Operator IPV GW: *.*.*.15 - Operator SMSC: *.*.*.21 It's SMSC that sends mobile SMSes to my kannel. Operator uses CMG UCP/EMI type SMSC. Here is my kannel konf: group = core admin-port = 13000 admin-password = ** status-password = ** admin-deny-ip = *.*.*.* admin-allow-ip = *.*.*.* smsbox-port = 1301 box-allow-ip = *.*.*.* wdp-interface-name = * log-file = /var/log/kannel/bearerbox.log access-log = /var/log/kannel/access.log store-file = /var/log/kannel/store.log log-level = 0 group = smsbox bearerbox-host = localhost sendsms-port = 13013 global-sender = 12014 log-file = /var/log/kannel/smsbox.log log-level = 0 group = sms-service keyword = test get-url = http://localhost/smsservice.php?sender=%ptext=%r; group = smsc smsc-id = EMT_MT smsc = emi port = 1 host = *.*.*.119 smsc-username = smsc-password = group = sendsms-user username = password = My http status: SMS: received 0 (0 queued), sent 1 (0 queued), store size 0 SMS: inbound 0.00 msg/sec, outbound 0.00 msg/sec DLR: 0 queued, using internal storage Box connections: smsbox:(none), IP 127.0.0.1 (0 queued), (on-line 0d 5h 57m 13s) SMSC connections: EMT_MTEMI2:*.*.*.119:1:12014 (online 85s, rcvd 0, sent 1, failed 0, queued 0 msgs) And what is my problem? I can send sms out. But if I send SMS to my short number it's not coming to my kannel and I don't know what's wrong. If I change smsbox-port back to 13001 and run fakesmsc then all works fine. 1301 is because operator demands it. Ok if I send sms to my shortnumber http status shows: SMS: received 0 (0 queued), sent 1 (0 queued), store size 0 SMS: inbound 0.00 msg/sec, outbound 0.00 msg/sec DLR: 0 queued, using internal storage Box connections: smsbox:(none), IP 127.0.0.1 (0 queued), (on-line 0d 6h 9m 13s) smsbox:(none), IP *.*.*.21(Operator SMSC IP) (0 queued), (on-line 0d 0h 0m 22s) SMSC connections: EMT_MTEMI2:217.71.32.119:1:12014 (online 85s, rcvd 0, sent 1, failed 0, queued 0 msgs) in bearerbox.log: 2007-03-30 23:17:31 [18836] [5] INFO: Client connected from *.*.*.21 2007-03-30 23:17:31 [18836] [5] DEBUG: Started thread 24 (gw/bb_boxc.c:function) 2007-03-30 23:17:31 [18836] [24] DEBUG: Thread 24 (gw/bb_boxc.c:function) maps to pid 18836. 2007-123.618723 *.*.*.55 - *.*.*.21 TCP ci3-software-1 12785 [SYN, ACK] Seq=0 Ack=0 Win=5840 Len=0 MSS=1460 WS=5 123.624779 *.*.*.55 - *.*.*.21 TCP ci3-software-1 12785 [ACK] Seq=1 Ack=107 Win=183 Len=0-30 23:17:31 [18836] [24] DEBUG: Started thread 25 (gw/bb_boxc.c:boxc_sender) 2007-03-30 23:17:31 [18836] [25] DEBUG: Thread 25 (gw/bb_boxc.c:boxc_sender) maps to pid 18836. Same time thethereal shows: 123.618723 *.*.*.55 - *.*.*.21 TCP ci3-software-1 12785 [SYN, ACK] Seq=0 Ack=0 Win=5840 Len=0 MSS=1460 WS=5 123.624779 213.180.29.55 - 217.71.32.21 TCP ci3-software-1 12785 [ACK] Seq=1 Ack=107 Win=183 Len=0 And after about one minute in bearbox: 2007-03-30 23:19:02 [18836] [24] INFO: Connection closed by the box *.*.*.21 2007-03-30 23:19:02 [18836] [25] DEBUG: send_msg: sending msg to box: *.*.*.21 2007-03-30 23:19:02 [18836] [25] DEBUG: Thread 25 (gw/bb_boxc.c:boxc_sender) terminates. 2007-03-30 23:19:02 [18836] [24] DEBUG: Thread 24 (gw/bb_boxc.c:function) terminates. tcpflow is show nothing. And the same time tethereal shows: 215.071237 *.*.*.55 - *.*.*.21 TCP ci3-software-1 12785 [PSH, ACK] Seq=1 Ack=108 Win=183 [TCP CHECKSUM INCORRECT] Len=16[Unreassembled Packet [incorrect TCP checksum]] 215.071360 *.*.*.55 - *.*.*.21 TCP ci3-software-1 12785 [FIN, ACK] Seq=17 Ack=108 Win=183 Len=0 tcpflow shows: *.*.*.055.01301-*.*.*.021.16760: And it is always the same if sms tries to go into my kannel. I don't know where to search the error. Operator tells that all is ok in their side. Best regards, Margusja --- Margusja +37251780 skype: margusja msn: [EMAIL PROTECTED] homepage: http://margusja.pri.ee --- Margusja +37251780 skype: margusja msn: [EMAIL PROTECTED] homepage: http://margusja.pri.ee
Re: dlr errors
Iain, The store is not used for DLR's, just for messages. Thats why you don't see them in the store-status. I use PostgreSQL to store my DLRs, then I can look them up easily to see what's outstanding. Your error looks like the web-server that you are sending the DLRs to is not responding correctly (it looks like its just closing the connection instead of talking HTTP). Possibly a firewall issue? Regards Ben On 2 Apr 2007, at 05:15, Iain Dooley wrote: hi, i'm seeing this error quite a bit: 2007-04-02 11:58:12 [26174] [4] INFO: Starting delivery report USER from +NUMBER 2007-04-02 11:58:12 [26174] [9] ERROR: Error reading from fd 28: 2007-04-02 11:58:12 [26174] [9] ERROR: System error 54: Connection reset by peer what can that mean? also if i do: lynx -dump http://localhost:PORT/store-status.txt?password=PASS; i get an empty queue, but if i do: lynx -dump http://localhost:PORT/status.txt?password=PASS; it says that there are 194 queued DLR's, shouldn't they be showing up in the store-status report? i'm using internal dlr storage. cheers iain
Re: SMS reciving problem
ci3-software-1 = 1301 --- Margusja +37251780 skype: margusja msn: [EMAIL PROTECTED] homepage: http://margusja.pri.ee Margusja wrote: I use kannel: Kannel bearerbox version `1.4.1'. Build `Oct 16 2006 10:48:53', compiler `4.1.1 20060525 (Red Hat 4.1.1-1)'. System Linux, release 2.6.19-1.2288.2.4.fc5, version #1 SMP Sun Mar 4 15:57:52 EST 2007, machine x86_64. Hostname h8.dbweb.ee, IP 217.159.233.174. Libxml version 2.6.23. Using SQLite 2.8.17. Using native malloc. My kannel is connected to operator SMSC-es with two VPN IPSec tunnels. First tunnel: My kannel eth1: *.*.*.55 - VPN LAN: *.*.*.53 My VPN GW: 13.180.29.56 - Tunnel - Operator IPV GW: *.*.*.15 - Operator SMSC: *.*.*.119. I use it to send SMSes out. Second tunnel: My kannel eth1: *.*.*.55 - VPN LAN: *.*.*.53 My VPN GW: 13.180.29.56 - Tunnel - Operator IPV GW: *.*.*.15 - Operator SMSC: *.*.*.21 It's SMSC that sends mobile SMSes to my kannel. Operator uses CMG UCP/EMI type SMSC. Here is my kannel konf: group = core admin-port = 13000 admin-password = ** status-password = ** admin-deny-ip = *.*.*.* admin-allow-ip = *.*.*.* smsbox-port = 1301 box-allow-ip = *.*.*.* wdp-interface-name = * log-file = /var/log/kannel/bearerbox.log access-log = /var/log/kannel/access.log store-file = /var/log/kannel/store.log log-level = 0 group = smsbox bearerbox-host = localhost sendsms-port = 13013 global-sender = 12014 log-file = /var/log/kannel/smsbox.log log-level = 0 group = sms-service keyword = test get-url = http://localhost/smsservice.php?sender=%ptext=%r; group = smsc smsc-id = EMT_MT smsc = emi port = 1 host = *.*.*.119 smsc-username = smsc-password = group = sendsms-user username = password = My http status: SMS: received 0 (0 queued), sent 1 (0 queued), store size 0 SMS: inbound 0.00 msg/sec, outbound 0.00 msg/sec DLR: 0 queued, using internal storage Box connections: smsbox:(none), IP 127.0.0.1 (0 queued), (on-line 0d 5h 57m 13s) SMSC connections: EMT_MTEMI2:*.*.*.119:1:12014 (online 85s, rcvd 0, sent 1, failed 0, queued 0 msgs) And what is my problem? I can send sms out. But if I send SMS to my short number it's not coming to my kannel and I don't know what's wrong. If I change smsbox-port back to 13001 and run fakesmsc then all works fine. 1301 is because operator demands it. Ok if I send sms to my shortnumber http status shows: SMS: received 0 (0 queued), sent 1 (0 queued), store size 0 SMS: inbound 0.00 msg/sec, outbound 0.00 msg/sec DLR: 0 queued, using internal storage Box connections: smsbox:(none), IP 127.0.0.1 (0 queued), (on-line 0d 6h 9m 13s) smsbox:(none), IP *.*.*.21(Operator SMSC IP) (0 queued), (on-line 0d 0h 0m 22s) SMSC connections: EMT_MTEMI2:217.71.32.119:1:12014 (online 85s, rcvd 0, sent 1, failed 0, queued 0 msgs) in bearerbox.log: 2007-03-30 23:17:31 [18836] [5] INFO: Client connected from *.*.*.21 2007-03-30 23:17:31 [18836] [5] DEBUG: Started thread 24 (gw/bb_boxc.c:function) 2007-03-30 23:17:31 [18836] [24] DEBUG: Thread 24 (gw/bb_boxc.c:function) maps to pid 18836. 2007-123.618723 *.*.*.55 - *.*.*.21 TCP ci3-software-1 12785 [SYN, ACK] Seq=0 Ack=0 Win=5840 Len=0 MSS=1460 WS=5 123.624779 *.*.*.55 - *.*.*.21 TCP ci3-software-1 12785 [ACK] Seq=1 Ack=107 Win=183 Len=0-30 23:17:31 [18836] [24] DEBUG: Started thread 25 (gw/bb_boxc.c:boxc_sender) 2007-03-30 23:17:31 [18836] [25] DEBUG: Thread 25 (gw/bb_boxc.c:boxc_sender) maps to pid 18836. Same time thethereal shows: 123.618723 *.*.*.55 - *.*.*.21 TCP ci3-software-1 12785 [SYN, ACK] Seq=0 Ack=0 Win=5840 Len=0 MSS=1460 WS=5 123.624779 213.180.29.55 - 217.71.32.21 TCP ci3-software-1 12785 [ACK] Seq=1 Ack=107 Win=183 Len=0 And after about one minute in bearbox: 2007-03-30 23:19:02 [18836] [24] INFO: Connection closed by the box *.*.*.21 2007-03-30 23:19:02 [18836] [25] DEBUG: send_msg: sending msg to box: *.*.*.21 2007-03-30 23:19:02 [18836] [25] DEBUG: Thread 25 (gw/bb_boxc.c:boxc_sender) terminates. 2007-03-30 23:19:02 [18836] [24] DEBUG: Thread 24 (gw/bb_boxc.c:function) terminates. tcpflow is show nothing. And the same time tethereal shows: 215.071237 *.*.*.55 - *.*.*.21 TCP ci3-software-1 12785 [PSH, ACK] Seq=1 Ack=108 Win=183 [TCP CHECKSUM INCORRECT] Len=16[Unreassembled Packet [incorrect TCP checksum]] 215.071360 *.*.*.55 - *.*.*.21 TCP ci3-software-1 12785 [FIN, ACK] Seq=17 Ack=108 Win=183 Len=0 tcpflow shows: *.*.*.055.01301-*.*.*.021.16760: And it is always the same if sms tries to go into my kannel. I don't know where to search the error. Operator tells that all is ok in their side. Best regards, Margusja --- Margusja +37251780 skype: margusja msn: [EMAIL PROTECTED] homepage: http://margusja.pri.ee --- Margusja +37251780 skype: margusja msn: [EMAIL PROTECTED] homepage: http://margusja.pri.ee
Re:
If you compiled from source, AFAIK Kannel does not install a startup script. You have to make yours or Google it from somewhere. Regards, Alejandro. On 3/25/07, Piyush shingala [EMAIL PROTECTED] wrote: Hello Friends, I am using CentOS 4 and I tried to install Kannel it was successful but not been able to find file. problem /etc/init.d/kannel start not file found could any one help me or provide the step by step installation procedure for kannel? -- Piyush Shingala +91-9824290345 -- Alejandro Guerrieri Magicom http://www.magicom-bcn.net/ LinkedIn: http://www.linkedin.com/in/aguerrieri
Latest CVS problem
Hi all, I'm having problems in getting the latest CVS to run on CentOS 4.4. It compiles and runs OK, but when I try sending a message from the sendsms HTTP interface, the message gets sent but the HTTP connection doesn't return nor displays anything on the browser. It just get stuck there. Anybody else experienced the same problem? I'm currently using a 2006-11-13 snapshot with no problems, but when I update it to the latest CVS this problem arise. I've never had this problem before (I've compiled and upgraded Kannel tenths of times on CentOS without any issues). Here is part of my conf file: group = core admin-port = 13000 smsbox-port = 13001 #wapbox-port = 13002 wdp-interface-name = * admin-password = oo status-password = xx dlr-storage = mysql #admin-deny-ip = admin-allow-ip = xx box-deny-ip = *.*.*.* box-allow-ip = x access-log = /var/log/kannel/access.log log-file = /var/log/kannel/kannel.log log-level = 2 store-file = /home/kannel/kannel.store # SMSBOX SETUP group = smsbox bearerbox-host = localhost sendsms-port = 13013 log-file = /var/log/kannel/smsbox.log access-log = /var/log/kannel/access.log log-level = 2 http-request-retry = 5 # SEND-SMS USERS group = sendsms-user username = password = Am I missing something? Maybe some new parameters that I should include, or is it a bug on the code? Thank you in advance, Alejandro. -- Alejandro Guerrieri Magicom http://www.magicom-bcn.net/ LinkedIn: http://www.linkedin.com/in/aguerrieri
Forcing SMSC doesn't work
Hi -- when doing an MT push, I want to force the SMSC I want messages to go out on, regardless of what the handset's prefix happens to be. However, it doesn't seem to work -- messages just go out on a random SMSC, even when I include a smsc= value in the MT push URL. We're recently suffering the overhead of the telcos rolling out number portability, and want to achieve the following: -- force a message to be pushed to a specific SMSC, provided the SMSC is specified in the push URL -- set a default SMSC (or group of SMSCs) for a prefix, in case the SMSC *isn't* specified -- and have confidence it'll all work. I am currently connected to 4 SMSCs, 3 providing connectivity to telco T1 (call these SMSC-T1.A through SMSC-T1.C), and one connected to telco T2 (SMSC-T2.A). Previously if I pushed out to a handset prefixed with 6427, it went out (randomly) through one of the 3 SMSCs connected to telco T1. The three smsc groups looked like this: group = smsc smsc = smpp smsc-id = SMSC-T1.A [ this changed between SMSCs ] allowed-prefix = 027;6427;+6427 denied-smsc-id = SMS-T1.B;SMS-T1.C [ obviously this was different between SMSCs ] preferred-smsc-id = smsc-t1a And the fourth SMSC (to the other telco) was along these lines: group = smsc smsc = smpp smsc-id = SMSC-T2.A allowed-prefix = 021;6421;+6421 (Judging from these prefixes, you can probably guess what country I am in.) With number portability, messages sent to handsets beginning with 6427 could potentially be forced to be sent out through telco T2; likewise handsets prefixed with 6421 might have to have messages pushed out through one of the SMSCs associated with telco T1. So I tried a test -- knowing a handset number which happened to have been ported from T1 to T2, but still keeping the 6427 prefix, I made some changes to the Kannel configuration, namely changing the allowed prefixes for all the SMSCs to allow all prefixes: allowed-prefix = 027;6427;+6427;021;6421;+6421; I also added a preferred-prefix value in case we tried to push out messages without specifying the SMSC preferred-prefix = 021;6421;+6421 The URL I requested included a value for smsc set to SMSC-T2.A (url-encoded), and assumed this would forced the message to go out through SMSC-T2.A; instead the message goes to *any* of the four SMSCs (since they've all got 6427 as a valid prefix). It appears to be a random choice between the four. Your advice is appreciated. David
Re: One SMSC conf per shot code
Diego, You must set two almost identical configurations, except for the port and receive-port settings, and smsc-id. For example, if your operator directs you to use port 1234: #TX Link ... smsc-id = myconn-tx allowed-smsc-id = myconn port = 1234 receive-port = 0 ... #RX Link ... smsc-id = myconn allowed-smsc-id = myconn port = 0 receive-port = 1234 ... You get the idea, allowed-smsc-id is set to myconn in both cases, so any traffic directed to it will find it's way to the myconn-tx link. Hope it helps, Alejandro Guerrieri On 4/2/07, Diego Helmann [EMAIL PROTECTED] wrote: Hi all I have to connect to one cell operartor that is asking me to make one connection per shortnumber: Information for connecting: --- (Shortcode 1234) IP: aaa.bbb.ccc.ddd Port: 4000 Source: 1234 System ID: Password: System Type: smpp Source TON: 2 Source NPI: 1 Destination TON: 2 Destination NPI: 1 One bind for Rx, and one bind for Tx. --- My conf is like: group = smsc smsc = smpp smsc-id = carrier1 allowed-smsc-id = carrier1 host = aaa.bbb.ccc.ddd port = 4000 receive-port = 4000 smsc-username = smsc-password = system-type = smpp reconnect-delay = 10 address-range = connect-allow-ip = aaa.bbb.ccc.ddd source-addr-ton = 2 source-addr-npi = 1 dest-addr-ton = 2 dest-addr-npi = 1 But, I need to connec for short number 1234 and 5678 1) How can I tell kannel that a connection is for certain short number? 2) What One bind for Rx, and one bind for Tx. means? That I have to set: port = 4000 receive-port = 4000 ??? Thanks in advance Regards Diego -- Alejandro Guerrieri Magicom http://www.magicom-bcn.net/ LinkedIn: http://www.linkedin.com/in/aguerrieri
