unsubscribe
Mit freundlichen Grüßen Thomas F. Wenzel Geschäftsleitung escape GmbH Büro Berlin: Kastanienallee 71 10435 Berlin (Prenzlauer Berg) Büro Frankfurt: Kontorhaus Osthafen Lindleystraße 12 60314 Frankfurt am Main Telefon +49 69 46 09 61 - 51 Telefax +49 69 46 09 61 - 99 Mobil +49 179 69 57 460 mailto:[EMAIL PROTECTED] www.escape-germany.de ESC58 - eine Kooperation der Firmen escape GmbH und fiftyeight GmbH www.esc58.de escape Gesellschaft für Computersysteme mbH vertreten durch die Geschäftsleitung Harald Trebs | Thomas Wenzel | Hubert Wombacher | Christian J. Allihn, geschäftsansässig unter der vorgenannten Anschrift, eingetragen im Handelsregister beim Amtsgericht Frankfurt am Main HRB 52046 | Ust-IdNr. DE 183918915 I St-Nr.: 452 324 803 9
Has anyone worked out playsms with Kannel successfully ?
I have installed playsms but i am unable to integrate it with kannel successfully. i have a basic confusion that will i access Kannel through Playsms web interface or i'll run playsms php scripts from kannel ?? Regards, wahib -- View this message in context: http://www.nabble.com/Has-anyone-worked-out-playsms-with-Kannel-successfully---tp19835440p19835440.html Sent from the Kannel - User mailing list archive at Nabble.com.
Re: Mobile phones that are known to work with kannel
@Nathan : Hi buddy. I searched and found your post. Today, i shifted to the mobile phase and tested whether Kannel works fine with Mobile as it was working fine as a fakesmsc. I have K500i and i found the configuration details of K510 in one of the posts and tried it. It worked and smsc was connected successfully. My modems.conf details are like this: group = modems id = K500i name = K500i detect-string = K500 init-string = AT+CNMI=2,3,0,1,0;+CMEE=1 message-storage = ME # PARA TEST: keepalive-cmd = AT+CSQ reset-string = AT+CFUN=1,0 In bearer-box it shows that a message is received and show it in hexadecimal form i guess !!... the part of the bearerbox log file is shown below ... 2008-10-06 14:15:18 [5868] [6] DEBUG: AT2[k500i]: -- AT+CNMI=2,3,0,1,0;+CMEE=1^M 2008-10-06 14:15:18 [5868] [6] DEBUG: AT2[k500i]: -- OK 2008-10-06 14:15:18 [5868] [6] INFO: AT2[k500i]: AT SMSC successfully opened. 2008-10-06 14:16:00 [5868] [5] INFO: Client connected from 127.0.0.1 2008-10-06 14:16:00 [5868] [10] DEBUG: Thread 10 (gw/bb_boxc.c:function) maps to pid 5868. 2008-10-06 14:16:00 [5868] [5] DEBUG: Started thread 10 (gw/bb_boxc.c:function) 2008-10-06 14:17:29 [5868] [6] DEBUG: AT2[k500i]: -- +CMTI: ME,33.c:boxc_sender) 2008-10-06 14:17:29 [5868] [6] DEBUG: AT2[k500i]: +CMTI incoming SMS indication: +CMTI: ME,33 2008-10-06 14:17:30 [5868] [6] DEBUG: AT2[k500i]: -- AT+CMGR=33^M 2008-10-06 14:17:30 [5868] [6] DEBUG: AT2[k500i]: -- +CMGR: 1,,159 2008-10-06 14:17:30 [5868] [6] DEBUG: AT2[k500i]: -- 079129030411240C9129135382813380016031636302A08A6B19447C83623018E8F87E93415474DA7D9EB314CEB7F84DCE83A4C566B1292C4AA7218542712D83886F500C4445A7DD67D055FE769F430AE75BFC26E741C6A7F458A44E5D0A8522493D4D41C7271174453E41C7A4B53865298E496B710A32818C4FE931692D4E5D0A8522493FCD41C87A3BEC065DD16FD0B14C9FB314C722750A32818C4FE9B1489DBA42 2008-10-06 14:17:30 [5868] [6] DEBUG: AT2[k500i]: received message from SMSC: +92304011 2008-10-06 14:17:30 [5868] [6] DEBUG: AT2[k500i]: Numeric sender (international) +923135281833 2008-10-06 14:17:30 [5868] [6] DEBUG: AT2[k500i]: User data length read as (160) 2008-10-06 14:17:30 [5868] [6] DEBUG: AT2[k500i]: Udh decoding done len=160 udhi=0 udhlen=0 udh='' 2008-10-06 14:17:30 [5868] [11] DEBUG: send_msg: sending msg to box: 127.0.0.1 2008-10-06 14:17:30 [5868] [11] DEBUG: boxc_sender: sent message to 127.0.0.1 2008-10-06 14:17:30 [5868] [10] DEBUG: boxc_receiver: sms received 2008-10-06 14:17:30 [5868] [10] DEBUG: send_msg: sending msg to box: 127.0.0.1 2008-10-06 14:17:30 [5868] [10] DEBUG: boxc_receiver: got ack 2008-10-06 14:17:30 [5868] [6] DEBUG: AT2[k500i]: -- OK 2008-10-06 14:17:30 [5868] [6] DEBUG: AT2[k500i]: -- AT+CMGD=33^M 2008-10-06 14:17:30 [5868] [6] DEBUG: AT2[k500i]: -- OK 2008-10-06 14:17:30 [5868] [6] DEBUG: AT2[k500i]: TP-Validity-Period: 24.0 hours 2008-10-06 14:17:30 [5868] [6] DEBUG: AT2[k500i]: -- AT+CMGS=32^M 2008-10-06 14:17:30 [5868] [6] DEBUG: AT2[k500i]: -- 2008-10-06 14:17:30 [5868] [6] DEBUG: AT2[k500i]: send command status: 1 2008-10-06 14:17:30 [5868] [6] DEBUG: AT2[k500i]: -- 0011000C9129135382813300F1A714CE37685E96DBD3E332680E2F8FD3E674990C 2008-10-06 14:17:30 [5868] [6] DEBUG: AT2[k500i]: -- ^Z 2008-10-06 14:17:30 [5868] [10] DEBUG: boxc_receiver: heartbeat with load value 0 received 2008-10-06 14:17:34 [5868] [6] DEBUG: AT2[k500i]: -- 2008-10-06 14:17:34 [5868] [6] DEBUG: AT2[k500i]: -- OK 2008-10-06 14:17:34 [5868] [6] DEBUG: AT2[k500i]: send command status: 0 2008-10-06 14:17:41 [5868] [9] DEBUG: Dumping 0 messages to store The problem is that the auto-reply which was working with fakesmsc is not working !! It should send for e.g. hello dear if nop is sent in the message as a key-word. Plz help ... is there some more variables i need to define in the modems group in the modems.conf file ?? or smthing else. Regards, wahib -- View this message in context: http://www.nabble.com/Mobile-phones-that-are-known-to-work-with-kannel-tp16976217p19835347.html Sent from the Kannel - User mailing list archive at Nabble.com.
Unexplained queuing of messages
I have had Kannel running for a couple of months without a hitch. For no apparent reason, a couple of weeks ago it suddenly quit sending messages but started queuing them. I am using a Multitech modem. When I looked at Kannel's status page it showed my SMSC connection name in red and the SMS: sent (in the middle of the status page) said (98 queued). I tried to to restart Kannel and bearer box would not shut down. I assume it was waiting to process the queued messages. I finally kill -9'd it and restarted Kannel. It would not connect to my modem. So I shut Kannel back down. I left it down for a couple of days until I had some time to look at it. When I started kannel up again, everything was working fine. I never like problems that fix themselves because I know they will be back. Two days ago it stopped sending messages again, after only 3 days of functioning. This time the SMS connection does not show in red but, everything is being queued. I have tried to shutdown just the SMSC connection to my modem. The response I get is Denied. Can this only be done if I have included a password in the smsc group in the config file? I also tried to place kannel in the suspend mode using the status password but also received the Denied response. Below I have included the current response page. Can anyone tell me why Kannel would simply start queuing instead of sending messages? Could this be a full memory problem in my modem? If it could, what are the best settings for equipment/memory/SIM usage using a GSM modem to manage the memories of this equipment? I asked this question earlier without any response here: http://www.kannel.org/pipermail/users/2008-September/005616.html Thanks for any help you can give. I really appreciate it. -Tony Kannel bearerbox version `cvs-20080613'. Build `Jun 24 2008 23:13:52', compiler `4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)'. System Linux, release 2.6.22-14-generic, version #1 SMP Tue Feb 12 02:46:46 UTC 2008, machine x86_64. Hostname message1, IP 127.0.1.1. Libxml version 2.6.30. Using native malloc. Status: running, uptime 5d 0h 32m 37s WDP: received 0 (0 queued), sent 0 (0 queued) SMS: received 0 (0 queued), sent 22 (0 queued), store size -1 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 5d 0h 32m 36s) SMSC connections: *vzn00*AT2[vzn00] (online 433944s, rcvd 0, sent 22, failed 0, queued 1522 msgs)
Re: Unexplained queuing of messages
Hmm, the store size -1 looks pretty suspicious for me. Try setting log-level to 0, restart kannel and see if you find something of interest on kannel.log. Regards, Alejandro On Mon, Oct 6, 2008 at 1:45 PM, Tony Kirkham [EMAIL PROTECTED] wrote: I have had Kannel running for a couple of months without a hitch. For no apparent reason, a couple of weeks ago it suddenly quit sending messages but started queuing them. I am using a Multitech modem. When I looked at Kannel's status page it showed my SMSC connection name in red and the SMS: sent (in the middle of the status page) said (98 queued). I tried to to restart Kannel and bearer box would not shut down. I assume it was waiting to process the queued messages. I finally kill -9'd it and restarted Kannel. It would not connect to my modem. So I shut Kannel back down. I left it down for a couple of days until I had some time to look at it. When I started kannel up again, everything was working fine. I never like problems that fix themselves because I know they will be back. Two days ago it stopped sending messages again, after only 3 days of functioning. This time the SMS connection does not show in red but, everything is being queued. I have tried to shutdown just the SMSC connection to my modem. The response I get is Denied. Can this only be done if I have included a password in the smsc group in the config file? I also tried to place kannel in the suspend mode using the status password but also received the Denied response. Below I have included the current response page. Can anyone tell me why Kannel would simply start queuing instead of sending messages? Could this be a full memory problem in my modem? If it could, what are the best settings for equipment/memory/SIM usage using a GSM modem to manage the memories of this equipment? I asked this question earlier without any response here: http://www.kannel.org/pipermail/users/2008-September/005616.html Thanks for any help you can give. I really appreciate it. -Tony Kannel bearerbox version `cvs-20080613'. Build `Jun 24 2008 23:13:52', compiler `4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)'. System Linux, release 2.6.22-14-generic, version #1 SMP Tue Feb 12 02:46:46 UTC 2008, machine x86_64. Hostname message1, IP 127.0.1.1. Libxml version 2.6.30. Using native malloc. Status: running, uptime 5d 0h 32m 37s WDP: received 0 (0 queued), sent 0 (0 queued) SMS: received 0 (0 queued), sent 22 (0 queued), store size -1 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 5d 0h 32m 36s) SMSC connections: *vzn00*AT2[vzn00] (online 433944s, rcvd 0, sent 22, failed 0, queued 1522 msgs)
Re: Regular Expressions
Put the 3 services upper on the list, and a default service for the rest. This way, the messages matching one, two and four will get processed by that services and all the rest will go to the default route. Hope it helps, Alejandro Guerrieri On Mon, Oct 6, 2008 at 3:05 PM, Paco [EMAIL PROTECTED] wrote: Hello, I'm trying to use a regular expression for not matching sms starting with one, two or four. For what I have read the POSIX regular expression for this should be: ^(?!one|two|four) However kannel fails to compile it with: regex compilation `^(?!one|two|four)' failed: Invalid preceding regular expression. Is there a way to make an inverse regular expression match? thing is that I have 3 services with keyword one, two and four and I need another one to match everything else (but one, two and four of course). Thanks
Re: Unexplained queuing of messages
Store Size reflects the number of messages on the filesystem store. A value of 0 is expected if no messages are currently on the store. -1 suggests me that something's probably wrong somewhere, because it means that the Dict (if store is file) or Counter (if it's spool) variable that holds the messages (or the number of) is not defined. This is definitely not normal, should be = 0. Your log file may be showing something for what matters. Try enqueueing a new message and see what shows in there. Regarding memory problems, try emptying the sim messages and see if that solves the problem, maybe you're not deleting the messages from the SIM after sending? You can shutdown kannel fromt the web interface with the shutdown command. Look for the details on the userguide. Regards, Alejandro Guerrieri On Mon, Oct 6, 2008 at 6:10 PM, Tony Kirkham [EMAIL PROTECTED] wrote: I have been running with log-level 0 and I haven't noticed anything, although I do not know what to expect. What should I be looking for? I believe I have always seen a store size -1 even when things were working. What does this mean? If messages are queued but not being processed, is there a way to shut Kannel down other than kill -9? I would like to do this so I can restart Kannel and watch the log on start up as you have suggested. Thanks, -Tony On Mon, Oct 6, 2008 at 11:57 AM, Alejandro Guerrieri [EMAIL PROTECTED] wrote: Hmm, the store size -1 looks pretty suspicious for me. Try setting log-level to 0, restart kannel and see if you find something of interest on kannel.log. Regards, Alejandro On Mon, Oct 6, 2008 at 1:45 PM, Tony Kirkham [EMAIL PROTECTED]wrote: I have had Kannel running for a couple of months without a hitch. For no apparent reason, a couple of weeks ago it suddenly quit sending messages but started queuing them. I am using a Multitech modem. When I looked at Kannel's status page it showed my SMSC connection name in red and the SMS: sent (in the middle of the status page) said (98 queued). I tried to to restart Kannel and bearer box would not shut down. I assume it was waiting to process the queued messages. I finally kill -9'd it and restarted Kannel. It would not connect to my modem. So I shut Kannel back down. I left it down for a couple of days until I had some time to look at it. When I started kannel up again, everything was working fine. I never like problems that fix themselves because I know they will be back. Two days ago it stopped sending messages again, after only 3 days of functioning. This time the SMS connection does not show in red but, everything is being queued. I have tried to shutdown just the SMSC connection to my modem. The response I get is Denied. Can this only be done if I have included a password in the smsc group in the config file? I also tried to place kannel in the suspend mode using the status password but also received the Denied response. Below I have included the current response page. Can anyone tell me why Kannel would simply start queuing instead of sending messages? Could this be a full memory problem in my modem? If it could, what are the best settings for equipment/memory/SIM usage using a GSM modem to manage the memories of this equipment? I asked this question earlier without any response here: http://www.kannel.org/pipermail/users/2008-September/005616.html Thanks for any help you can give. I really appreciate it. -Tony Kannel bearerbox version `cvs-20080613'. Build `Jun 24 2008 23:13:52', compiler `4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)'. System Linux, release 2.6.22-14-generic, version #1 SMP Tue Feb 12 02:46:46 UTC 2008, machine x86_64. Hostname message1, IP 127.0.1.1. Libxml version 2.6.30. Using native malloc. Status: running, uptime 5d 0h 32m 37s WDP: received 0 (0 queued), sent 0 (0 queued) SMS: received 0 (0 queued), sent 22 (0 queued), store size -1 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 5d 0h 32m 36s) SMSC connections: *vzn00*AT2[vzn00] (online 433944s, rcvd 0, sent 22, failed 0, queued 1522 msgs)
Re: Unexplained queuing of messages
Alejandro Guerrieri schrieb: Store Size reflects the number of messages on the filesystem store. A value of 0 is expected if no messages are currently on the store. -1 suggests me that something's probably wrong somewhere, because it means that the Dict (if store is file) or Counter (if it's spool) variable that holds the messages (or the number of) is not defined. This is definitely not normal, should be = 0. [...] Look for the details on the userguide. Looking at the userguide is always a good idea. Under core-configuration you find that for example: Set maximum size of incoming message queue. After number of messages has hit this value, Kannel began to discard them. Value 0 means giving strict priority to outgoing messages. -1, default, means that the queue of infinite length is accepted. (This works with any normal input, use this variable only when Kannel message queues grow very long). So -1 is not only normal but even default. Sorry that I can't state anything productive to the problem, but this is it surely not.
Re: Unexplained queuing of messages
Falko, You're getting confused with the queue-limit setting. Store Size displays the number of messages currently on the store, and that should be 0 or greater. Regards, Alejandro Guerrieri No, that's not the meaning of the Store Size indicator on the status page. On Mon, Oct 6, 2008 at 7:42 PM, Falko Ziemann [EMAIL PROTECTED] wrote: Alejandro Guerrieri schrieb: Store Size reflects the number of messages on the filesystem store. A value of 0 is expected if no messages are currently on the store. -1 suggests me that something's probably wrong somewhere, because it means that the Dict (if store is file) or Counter (if it's spool) variable that holds the messages (or the number of) is not defined. This is definitely not normal, should be = 0. [...] Look for the details on the userguide. Looking at the userguide is always a good idea. Under core-configuration you find that for example: Set maximum size of incoming message queue. After number of messages has hit this value, Kannel began to discard them. Value 0 means giving strict priority to outgoing messages. -1, default, means that the queue of infinite length is accepted. (This works with any normal input, use this variable only when Kannel message queues grow very long). So -1 is not only normal but even default. Sorry that I can't state anything productive to the problem, but this is it surely not.
Re: Can anyone please help me?
Hi, Thanks for the reply. No I am not using a prebuilt package. I compiled it myself. However, my problem went away when I used the latest CSV instead of the 1.4.1 . So everything is fine now. On Sat, Oct 4, 2008 at 1:45 PM, Kashif Ali Bukhari [EMAIL PROTECTED]wrote: seems you are using prebuilt packeg please compile it yourself On Mon, Sep 22, 2008 at 2:36 PM, Shoeb Ahmed [EMAIL PROTECTED] wrote: I sent this message below but haven't got any reply back. Can anyone please provide any insight into this problem? I really really need it to be solved. On Thu, Sep 11, 2008 at 2:43 PM, [EMAIL PROTECTED] wrote: Message: 1 Date: Thu, 11 Sep 2008 14:22:31 +0600 From: Shoeb Ahmed [EMAIL PROTECTED] Subject: Bearerbox crash when using dlr To: users@kannel.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=iso-8859-1 Hi, I have kannel 1.4.1 running in Ubuntu 7.10 for a few months now. It works perfectly. But recently when I tried to use dlr-url and dlr-mask when sending SMS through http interface, bearerbox crashes everytime. I have tried using both internal dlr storage and mysql dlr storage but that doesn't seem to have any effect on it. Below is the log of crash: 2008-09-11 12:36:16 [5394] [8] PANIC: Memory re-allocation failed 2008-09-11 12:36:16 [5394] [8] PANIC: System error 12: Cannot allocate memory 2008-09-11 12:36:17 [5394] [8] PANIC: /usr/local/sbin/bearerbox(gw_panic+0x107) [0x80c4517] 2008-09-11 12:36:17 [5394] [8] PANIC: /usr/local/sbin/bearerbox(gw_native_realloc+0x7d) [0x80b8f3d] 2008-09-11 12:36:17 [5394] [8] PANIC: /usr/local/sbin/bearerbox [0x80c57a5] 2008-09-11 12:36:17 [5394] [8] PANIC: /usr/local/sbin/bearerbox(octstr_insert_data+0x63) [0x80c7b23] 2008-09-11 12:36:17 [5394] [8] PANIC: /usr/local/sbin/bearerbox(octstr_append_char+0x39) [0x80c7d49] 2008-09-11 12:36:17 [5394] [8] PANIC: /usr/local/sbin/bearerbox [0x8067e2b] 2008-09-11 12:36:17 [5394] [8] PANIC: /usr/local/sbin/bearerbox [0x806b19a] 2008-09-11 12:36:17 [5394] [8] PANIC: /usr/local/sbin/bearerbox [0x80baf31] 2008-09-11 12:36:17 [5394] [8] PANIC: /lib/tls/i686/cmov/libpthread.so.0 [0xb7f3e46b] 2008-09-11 12:36:17 [5394] [8] PANIC: /lib/tls/i686/cmov/libc.so.6(clone+0x5e) [0xb7bb973e] When using debug log level, I get this about my smsc: 2008-09-11 12:58:32 [6041] [0] INFO: SMS resend retry set to 10. 2008-09-11 12:58:32 [6041] [0] INFO: DLR rerouting for smsc id FAKE disabled. 2008-09-11 12:58:32 [6041] [0] DEBUG: Started thread 6 (gw/smsc/smsc_fake.c:fake_listener) *2008-09-11 12:58:32 [6041] [0] INFO: DLR rerouting for smsc id smsc_warid disabled.* 2008-09-11 12:58:32 [6041] [0] INFO: Added logfile `/home/freebdsms/kannel_run/smsc.log' with level `1'. 2008-09-11 12:58:32 [6041] [0] INFO: AT2[smsc_warid]: configuration doesn't show modemtype. will autodetect 2008-09-11 12:58:32 [6041] [0] DEBUG: Started thread 7 (gw/smsc/smsc_at.c:at2_device_thread) *2008-09-11 12:58:32 [6041] [0] INFO: DLR rerouting for smsc id smsc_banglalink disabled.* 2008-09-11 12:58:32 [6041] [0] INFO: Added logfile `/home/freebdsms/kannel_run/smsc.log' with level `1'. 2008-09-11 12:58:32 [6041] [0] INFO: AT2[smsc_banglalink]: configuration doesn't show modemtype. will autodetect 2008-09-11 12:58:32 [6041] [0] DEBUG: Started thread 8 (gw/smsc/smsc_at.c:at2_device_thread) 2008-09-11 12:58:32 [6041] [0] DEBUG: Started thread 9 (gw/bb_smscconn.c:sms_router) 2008-09-11 12:58:32 [6041] [0] INFO: 2008-09-11 12:58:32 [6041] [0] INFO: Kannel bearerbox II version 1.4.1 starting 2008-09-11 12:58:32 [6041] [1] DEBUG: Thread 1 (gwlib/fdset.c:poller) maps to pid 6041. 2008-09-11 12:58:32 [6041] [6] DEBUG: Thread 6 (gw/smsc/smsc_fake.c:fake_listener) maps to pid 6041. 2008-09-11 12:58:32 [6041] [7] DEBUG: Thread 7 (gw/smsc/smsc_at.c:at2_device_thread) maps to pid 6041. 2008-09-11 12:58:32 [6041] [7] INFO: Logging thread `7' to logfile `/home/freebdsms/kannel_run/smsc.log' with level `1'. 2008-09-11 12:58:32 [6041] [8] DEBUG: Thread 8 (gw/smsc/smsc_at.c:at2_device_thread) maps to pid 6041. 2008-09-11 12:58:32 [6041] [8] INFO: Logging thread `8' to logfile `/home/freebdsms/kannel_run/smsc.log' with level `1'. 2008-09-11 12:58:32 [6041] [9] DEBUG: Thread 9 (gw/bb_smscconn.c:sms_router) maps to pid 6041. 2008-09-11 12:58:32 [6041] [9] DEBUG: sms_router: time to sleep 30.00 secs. 2008-09-11 12:58:32 [6041] [2] DEBUG: Thread 2 (gwlib/http.c:server_thread) maps to pid 6041. 2008-09-11 12:58:32 [6041] [0] INFO: MAIN: Start-up done, entering mainloop 2008-09-11 12:58:32 [6041] [0] DEBUG: smsc_fake: start called 2008-09-11 12:58:32 [6041] [0] DEBUG: AT2[smsc_warid]: start called 2008-09-11 12:58:32 [6041] [0] DEBUG: AT2[smsc_banglalink]: start called 2008-09-11 12:58:32 [6041] [3] DEBUG: Thread 3
