Re: Reconcile of incoming SMS (MO SMS)
In its default behaviour, bearerbox does the reassembling of fragments of long sms before delivering a one long sms to smsbox, so in access log you'll only see the reassembled sms without udh header set. Setting sms-combine-concatenated-mo to false will lead bearerbox to not to reassemble fragments, you'll get every fragment in a separate line in access log, but you'll get to reassemble the fragments by yourself in this case and i think this is not what you expect :) There's still two solutions: 1. Set your smsc log to debug and then grep for 'deliver_sm' lines, every deliver_sm is a MO. 2. In case your log will grow quick with high sms traffic when set to debug level, reset the level to its default and play with tcp traffic snooping, some users even made a snort pattern on the deliver_sm pdu and count them using Snort. Regards, Fourat On Sat, Mar 17, 2012 at 10:29 PM, Saad Omer s...@aeon.pk wrote: I checked the logs in access file. Incoming long messages do not have udh starting with 0500 in access-kannel file. Example: ** ** 2011-03-09 15:12:38 Receive SMS [SMSC:710] [SVC:] [ACT:710] [BINF:] [FID:] [META:?smpp?] [from:] [to:710] [flags:-1:0:-1:0:-1] [msg:190:xxx] [udh:0:] ** ** Am I looking in the wrong file? ** ** Regards, ** ** *From:* Fourat ZOUARI [mailto:fou...@gmail.com] *Sent:* Wednesday, February 22, 2012 11:54 PM *To:* ha...@aeon.pk *Cc:* kannel users *Subject:* Re: Reconcile of incoming SMS (MO SMS) ** ** You can check if udh starts with 0500, that's a fragmented SMS. ** ** And of course, set sms-combine-concatenated-mo = false ** ** This will lead you to receive long MOs in a parted way, if it's not what you want, then you can set your smsc log to debug level and grep for submit_sm PDUs On Mon, Sep 13, 2010 at 2:40 PM, ha...@aeon.pk ha...@aeon.pk wrote: Hi, ** ** I need to bill my operator for the incoming SMS to my application (MO messages). For calculating all the received SMS, I grep the phrase Receive SMS from the access-log file, which should give the me actual count of incoming SMS. However, there are issues I see by comparing different files: ** ** - If I get a long SMS (more than 160 characters), the operator counts it as 2 messages (of course it is logical as per GSM standard), but kannel considers it as one single message (in access-log file: *EXAMPLE*: 2010-09-09 20:00:24 Receive SMS [SMSC:polling] [SVC:] [ACT:] [BINF:] [FID:] [from:] [to:71606] [flags:-1:0:-1:0:-1] [msg:210:] [udh:0:]). Since I grep the word Receive SMS, I am unable to capture the additional information of additional SMS unless I do some advanced scripting. How to fix this bug in reconcile? Any other log file/method that could give me correct count for incoming SMS? Can sqlbox do it? Currently I am not using it. ** ** - I see difference between total counts of received SMS from the kannel status page (*polling*SMPP:xxx.xx.xx.xxx:17601/17601:716:716 (online 17563s, rcvd 2454, sent 54088, failed 0, queued 0 msgs) and the count I get by running grep command on access-log (grep Receive SMS access-log.log). Apparantly, messages reported by kannel status are more than what I can see in the logs. If I assume that kannel status is reporting the correct number of incoming SMS including the long message factor, then how can I extract this count from kannel status, since its counters are reset everytime I restart bearerbox. ** ** Regards, ** ** Hamza ** **
Concatenated SMS MO have corrupt UDH when sms-combine-concatenated-mo is set to false
Hi, By default, Kannel concatenates fragmented MOs into one long SMS MO, by setting sms-combine-concatenated-mo to false, it delivers every fragment as is with an UDH indicating it is a long sms fragment, so for a long sms fragment i get this UDH in access-log: [udh:6:0500031D6332] So, this udh: 0500031D0302 means: - 05 UDH length - 00 IEI, concatenated short messages - 03 IE Data length - 1D reference number (29) - 03 number of short messages in the concatenated short message (3) - 02 sequence number of the current short message, that means this is the second fragment of 3 fragments I use PHP scripts to make one message from such messages, but in my PHP application I do not get this UDH, instead I get something like this: 0500031Dc2 In my smsbox access-log I see: 2007-08-08 20:51:18 SMS HTTP-request sender:26392390208295477 request: '' url: 'http://test.dev/receive.php?text=enaidnieki+513)+automashinas%3 B+514)+kugji+515)+traktori+516)+zobenzivis+517)+buldozeri+518)+sanitaari+519)+draugi+520)+ienaidnieki+521)+automashinas%3B+522)keyword=enaidniekikeyword2=51 3)from=26392390208295477to=1827smsc=5time=2007-08-08+17:51:18drv=-1coding=0charset=ISO-8859-1udh=%05%00%03%1Dc2' reply: 200 ' successful ' What is it? %05%00%03%1Dc2 is not HEX anymore. I use Kannel 1.4.3. My kannel SMS service: # SMS SERVICE Default group = sms-service keyword = default accept-x-kannel-headers = true get-url = http://test.dev/receive.php?text=%akeyword=%kkeyword2=%sfrom=%pto=%Psmsc=%itime=%tdrv=%dcoding=%ccharset=%Cudh=%u max-messages = 0 omit-empty = true How can I stop kannel to make such conversations? Binary SMS text sometimes also is converted to something meaningless. For information, using a tcpdump i see that i get correct udh for every fragmented SMS-MO delivered to bearerbox, but once received from smsbox, the udh gets corrupted.
Kannel 1.4.3 wont start and no errors are shown
Hi, I've just compiled Kannel 1.4.3 and tried to start bearerbox like this: # /usr/local/sbin/bearerbox -v 0 main.conf 2011-10-25 20:29:53 [19391] [0] INFO: Debug_lvl = 0, log_file = none, log_lvl = 0 2011-10-25 20:29:53 [19391] [0] WARNING: DLR: using default 'internal' for storage type. 2011-10-25 20:29:53 [19391] [0] INFO: DLR using storage type: internal 2011-10-25 20:29:53 [19391] [0] DEBUG: Kannel bearerbox version `1.4.3'. Build `Oct 25 2011 20:27:35', compiler `4.4.3'. System Linux, release 2.6.32-32-generic-pae, version #62-Ubuntu SMP Wed Apr 20 22:10:33 UTC 2011, machine i686. Hostname app-kannel, IP 127.0.1.1. Libxml version 2.7.6. Using OpenSSL 0.9.8k 25 Mar 2009. Using native malloc. 2011-10-25 20:29:53 [19391] [0] WARNING: Kannel was compiled without WAP support 2011-10-25 20:29:53 [19391] [0] INFO: HTTP: Opening server at port 1300. 2011-10-25 20:29:53 [19391] [0] DEBUG: Started thread 1 (gwlib/fdset.c:poller) 2011-10-25 20:29:53 [19391] [1] DEBUG: Thread 1 (gwlib/fdset.c:poller) maps to pid 19391. 2011-10-25 20:29:53 [19391] [0] DEBUG: Started thread 2 (gwlib/http.c:server_thread) 2011-10-25 20:29:53 [19391] [2] DEBUG: Thread 2 (gwlib/http.c:server_thread) maps to pid 19391. 2011-10-25 20:29:53 [19391] [0] DEBUG: Started thread 3 (gw/bb_http.c:httpadmin_run) 2011-10-25 20:29:53 [19391] [3] DEBUG: Thread 3 (gw/bb_http.c:httpadmin_run) maps to pid 19391. 2011-10-25 20:29:53 [19391] [0] INFO: 2011-10-25 20:29:53 [19391] [0] INFO: Kannel bearerbox II version 1.4.3 starting 2011-10-25 20:29:58 [19391] [0] INFO: MAIN: Start-up done, entering mainloop 2011-10-25 20:29:58 [19391] [0] DEBUG: Shutting down Kannel... 2011-10-25 20:29:58 [19391] [0] DEBUG: shutting down smsc 2011-10-25 20:29:58 [19391] [0] INFO: All flow threads have died, killing core 2011-10-25 20:29:58 [19391] [0] DEBUG: Waiting for 2 (gwlib/http.c:server_thread) to terminate 2011-10-25 20:29:58 [19391] [3] DEBUG: HTTP: No clients with requests, quitting. 2011-10-25 20:29:58 [19391] [3] DEBUG: Thread 3 (gw/bb_http.c:httpadmin_run) terminates. 2011-10-25 20:29:58 [19391] [2] DEBUG: Thread 2 (gwlib/http.c:server_thread) terminates. 2011-10-25 20:29:58 [19391] [1] DEBUG: Thread 1 (gwlib/fdset.c:poller) terminates. 2011-10-25 20:29:58 [19391] [0] INFO: Total SMS messages: received 0, sent 0 2011-10-25 20:29:58 [19391] [0] DEBUG: Immutable octet strings: 58. As for the main.conf file, i've simplified it to the minimum so i can focus more on the problem, here is it: group = core admin-port = 1300 admin-password = fxxbar Any idea ? thanks
Re: Kannel 1.4.3 wont start and no errors are shown
All my configuration is the main.conf file containing this: group = core admin-port = 1300 admin-password = fxxbar These 3 lines shall keep bearerbox running and listening on port 1300. On Tue, Oct 25, 2011 at 8:49 PM, Otandeka Simon Peter sotand...@gmail.comwrote: Please post your configuration file. There could be an error. P. On Tue, Oct 25, 2011 at 10:37 PM, Fourat ZOUARI fou...@gmail.com wrote: Hi, I've just compiled Kannel 1.4.3 and tried to start bearerbox like this: # /usr/local/sbin/bearerbox -v 0 main.conf 2011-10-25 20:29:53 [19391] [0] INFO: Debug_lvl = 0, log_file = none, log_lvl = 0 2011-10-25 20:29:53 [19391] [0] WARNING: DLR: using default 'internal' for storage type. 2011-10-25 20:29:53 [19391] [0] INFO: DLR using storage type: internal 2011-10-25 20:29:53 [19391] [0] DEBUG: Kannel bearerbox version `1.4.3'. Build `Oct 25 2011 20:27:35', compiler `4.4.3'. System Linux, release 2.6.32-32-generic-pae, version #62-Ubuntu SMP Wed Apr 20 22:10:33 UTC 2011, machine i686. Hostname app-kannel, IP 127.0.1.1. Libxml version 2.7.6. Using OpenSSL 0.9.8k 25 Mar 2009. Using native malloc. 2011-10-25 20:29:53 [19391] [0] WARNING: Kannel was compiled without WAP support 2011-10-25 20:29:53 [19391] [0] INFO: HTTP: Opening server at port 1300. 2011-10-25 20:29:53 [19391] [0] DEBUG: Started thread 1 (gwlib/fdset.c:poller) 2011-10-25 20:29:53 [19391] [1] DEBUG: Thread 1 (gwlib/fdset.c:poller) maps to pid 19391. 2011-10-25 20:29:53 [19391] [0] DEBUG: Started thread 2 (gwlib/http.c:server_thread) 2011-10-25 20:29:53 [19391] [2] DEBUG: Thread 2 (gwlib/http.c:server_thread) maps to pid 19391. 2011-10-25 20:29:53 [19391] [0] DEBUG: Started thread 3 (gw/bb_http.c:httpadmin_run) 2011-10-25 20:29:53 [19391] [3] DEBUG: Thread 3 (gw/bb_http.c:httpadmin_run) maps to pid 19391. 2011-10-25 20:29:53 [19391] [0] INFO: 2011-10-25 20:29:53 [19391] [0] INFO: Kannel bearerbox II version 1.4.3 starting 2011-10-25 20:29:58 [19391] [0] INFO: MAIN: Start-up done, entering mainloop 2011-10-25 20:29:58 [19391] [0] DEBUG: Shutting down Kannel... 2011-10-25 20:29:58 [19391] [0] DEBUG: shutting down smsc 2011-10-25 20:29:58 [19391] [0] INFO: All flow threads have died, killing core 2011-10-25 20:29:58 [19391] [0] DEBUG: Waiting for 2 (gwlib/http.c:server_thread) to terminate 2011-10-25 20:29:58 [19391] [3] DEBUG: HTTP: No clients with requests, quitting. 2011-10-25 20:29:58 [19391] [3] DEBUG: Thread 3 (gw/bb_http.c:httpadmin_run) terminates. 2011-10-25 20:29:58 [19391] [2] DEBUG: Thread 2 (gwlib/http.c:server_thread) terminates. 2011-10-25 20:29:58 [19391] [1] DEBUG: Thread 1 (gwlib/fdset.c:poller) terminates. 2011-10-25 20:29:58 [19391] [0] INFO: Total SMS messages: received 0, sent 0 2011-10-25 20:29:58 [19391] [0] DEBUG: Immutable octet strings: 58. As for the main.conf file, i've simplified it to the minimum so i can focus more on the problem, here is it: group = core admin-port = 1300 admin-password = fxxbar Any idea ? thanks
Re: Kannel 1.4.3 wont start and no errors are shown
Same thing with kannel.conf from kannel's package: Here's the execution outcome of bearerbox: # bearerbox -v 0 kannel.conf 2011-10-25 20:59:29 [3263] [0] INFO: Debug_lvl = 0, log_file = none, log_lvl = 0 2011-10-25 20:59:29 [3263] [0] WARNING: DLR: using default 'internal' for storage type. 2011-10-25 20:59:29 [3263] [0] INFO: DLR using storage type: internal 2011-10-25 20:59:29 [3263] [0] DEBUG: Kannel bearerbox version `1.4.3'. Build `Oct 25 2011 20:27:35', compiler `4.4.3'. System Linux, release 2.6.32-34-generic-pae, version #77-Ubuntu SMP Tue Sep 13 21:16:18 UTC 2011, machine i686. Hostname app-kannel, IP 127.0.1.1. Libxml version 2.7.6. Using OpenSSL 0.9.8k 25 Mar 2009. Using native malloc. 2011-10-25 20:59:29 [3263] [0] INFO: Added logfile `/tmp/bearerbox.log' with level `0'. 2011-10-25 20:59:29 [3263] [0] WARNING: Kannel was compiled without WAP support 2011-10-25 20:59:29 [3263] [0] INFO: HTTP: Opening server at port 13000. 2011-10-25 20:59:29 [3263] [0] DEBUG: Started thread 1 (gwlib/fdset.c:poller) 2011-10-25 20:59:29 [3263] [1] DEBUG: Thread 1 (gwlib/fdset.c:poller) maps to pid 3263. 2011-10-25 20:59:29 [3263] [0] DEBUG: Started thread 2 (gwlib/http.c:server_thread) 2011-10-25 20:59:29 [3263] [2] DEBUG: Thread 2 (gwlib/http.c:server_thread) maps to pid 3263. 2011-10-25 20:59:29 [3263] [0] DEBUG: Started thread 3 (gw/bb_http.c:httpadmin_run) 2011-10-25 20:59:29 [3263] [3] DEBUG: Thread 3 (gw/bb_http.c:httpadmin_run) maps to pid 3263. 2011-10-25 20:59:29 [3263] [0] INFO: 2011-10-25 20:59:29 [3263] [0] INFO: Kannel bearerbox II version 1.4.3 starting 2011-10-25 20:59:33 [3263] [2] DEBUG: HTTP: Creating HTTPClient for `127.0.0.1'. 2011-10-25 20:59:33 [3263] [2] DEBUG: HTTP: Created HTTPClient area 0x8755700. 2011-10-25 20:59:33 [3263] [3] INFO: HTTP admin tried from denied host 127.0.0.1, disconnected 2011-10-25 20:59:33 [3263] [3] DEBUG: HTTP: Destroying HTTPClient area 0x8755700. 2011-10-25 20:59:33 [3263] [3] DEBUG: HTTP: Destroying HTTPClient for `127.0.0.1'. 2011-10-25 20:59:34 [3263] [0] INFO: MAIN: Start-up done, entering mainloop 2011-10-25 20:59:34 [3263] [0] DEBUG: Shutting down Kannel... 2011-10-25 20:59:34 [3263] [0] DEBUG: shutting down smsc 2011-10-25 20:59:34 [3263] [0] INFO: All flow threads have died, killing core 2011-10-25 20:59:34 [3263] [0] DEBUG: Waiting for 2 (gwlib/http.c:server_thread) to terminate 2011-10-25 20:59:34 [3263] [3] DEBUG: HTTP: No clients with requests, quitting. 2011-10-25 20:59:34 [3263] [3] DEBUG: Thread 3 (gw/bb_http.c:httpadmin_run) terminates. 2011-10-25 20:59:34 [3263] [2] DEBUG: Thread 2 (gwlib/http.c:server_thread) terminates. 2011-10-25 20:59:34 [3263] [1] DEBUG: Thread 1 (gwlib/fdset.c:poller) terminates. 2011-10-25 20:59:34 [3263] [0] INFO: Total SMS messages: received 0, sent 0 2011-10-25 20:59:34 [3263] [0] DEBUG: Immutable octet strings: 80. The configuration file 'kannel.conf' contains: # # Sample configuration file for Kannel bearerbox on Debian. # See the documentation for explanations of fields. # # HTTP administration is disabled by default. Make sure you set the # password if you enable it. group = core admin-port = 13000 admin-password = bar admin-deny-ip = *.*.*.* admin-allow-ip = wapbox-port = 13002 wdp-interface-name = * log-file = /tmp/bearerbox.log box-deny-ip = *.*.*.* box-allow-ip = 127.0.0.1 group = wapbox bearerbox-host = localhost log-file = /tmp/wapbox.log On Tue, Oct 25, 2011 at 8:56 PM, Otandeka Simon Peter sotand...@gmail.comwrote: And that is why your kannel is shutting down. Your main.conf is missing a lot of must-have parameters. The kannel package comes with a sample and basic configuration file. Look it up and start from there. Kind regards, P. On Tue, Oct 25, 2011 at 10:51 PM, Fourat ZOUARI fou...@gmail.com wrote: All my configuration is the main.conf file containing this: group = core admin-port = 1300 admin-password = fxxbar These 3 lines shall keep bearerbox running and listening on port 1300. On Tue, Oct 25, 2011 at 8:49 PM, Otandeka Simon Peter sotand...@gmail.com wrote: Please post your configuration file. There could be an error. P. On Tue, Oct 25, 2011 at 10:37 PM, Fourat ZOUARI fou...@gmail.comwrote: Hi, I've just compiled Kannel 1.4.3 and tried to start bearerbox like this: # /usr/local/sbin/bearerbox -v 0 main.conf 2011-10-25 20:29:53 [19391] [0] INFO: Debug_lvl = 0, log_file = none, log_lvl = 0 2011-10-25 20:29:53 [19391] [0] WARNING: DLR: using default 'internal' for storage type. 2011-10-25 20:29:53 [19391] [0] INFO: DLR using storage type: internal 2011-10-25 20:29:53 [19391] [0] DEBUG: Kannel bearerbox version `1.4.3'. Build `Oct 25 2011 20:27:35', compiler `4.4.3'. System Linux, release 2.6.32-32-generic-pae, version #62-Ubuntu SMP Wed Apr 20 22:10:33 UTC 2011, machine i686. Hostname app-kannel, IP 127.0.1.1
Re: Message Queue :: Clarification
Thank you Abdulraheem, Betwise, shall i configure the throughput to what my operator is slowing down to ? (1 sms/s) Regards, On Mon, Oct 19, 2009 at 3:27 AM, Abdulraheem Obaisi aopa...@hotmail.comwrote: Hi, I have faced same issue month ago (throughput problem) , last CVS has solved this issue please try to install the latest one with configuring the throughput in your SMSC connection. ... Best Regards Eng: Abdulraheem Ali Obaisi Software Engineer -- Date: Sun, 18 Oct 2009 13:07:17 +0100 Subject: Re: Message Queue :: Clarification From: fou...@gmail.com To: cornejo.alv...@gmail.com CC: users@kannel.org Thank you for this information. I have an issue with Kannel, am sending some 10K sms-mt campaign, in the normal behaviour i have a decreasing store and increasing sent message counter. But suddenly, the store stops to be decreased, the sent in queue counter starts increasing till getting the same value than store and they both keep that for some hours. The logs are in debug, and i have nothing saying the smsc is rejecting or something like that ... i realy dont know how to resolve such a problem. On Sat, Oct 17, 2009 at 3:37 PM, Alvaro Cornejo cornejo.alv...@gmail.comwrote: the values shown in the specific smsc correspond to messages queues in that specific SMSC. Messages in store size are messages that were not yet assigned to an smsc. kind of global queue. Regards Alvaro On Mon, Sep 7, 2009 at 6:09 AM, Jinson jin...@mobme.in wrote: Hello Group, Below is my http admin view of kannel. I'm not able to understand the exact differnce between message in stored queue and ones shown in each smsc connection. SMS: received 18762 (0 queued), sent 12983 (0 queued), store size 20 SMS: inbound (0.50,7.02,3.44) msg/sec, outbound (0.13,3.37,2.38) msg/sec DLR: 67291 queued, using mysql storage Box connections: smsbox:smsbox, IP 127.0.0.1 (0 queued), (on-line 0d 1h 30m 44s) SMSC connections: xSMPP:xxx: (online 2266s, rcvd 6920, sent 6920, failed 0, queued 0 msgs) xSMPP:xxx: (online 5447s, rcvd 0, sent 0, failed 0, queued 0 msgs) xSMPP:xxx: (online 5447s, rcvd 2102, sent 952, failed 2, queued 716 msgs) xSMPP:xxx: (online 5447s, rcvd 2060, sent 909, failed 3, queued 593 msgs) xSMPP:xxx: (online 5447s, rcvd 2363, sent 1216, failed 1, queued 228 msgs) xSMPP:xxx: (online 5447s, rcvd 2592, sent 1442, failed 4, queued 19 msgs) xSMPP:xxx: (online 5447s, rcvd 2725, sent 1544, failed 33, queued 0 msgs) xSMPP:xxx: (online 5447s, rcvd 0, sent 0, failed 0, queued 0 msgs) --- Thanks Jinson Abraham -- |-| Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier celular y Nextel en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS y GPRS online Visitenos en www.perusms.NET http://www.perusms.net/ www.smsglobal.com.mx y www.pravcom.com -- Windows Live: Keep your friends up to date with what you do online.http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_1:092010
Re: Message Queue :: Clarification
Thank you for this information. I have an issue with Kannel, am sending some 10K sms-mt campaign, in the normal behaviour i have a decreasing store and increasing sent message counter. But suddenly, the store stops to be decreased, the sent in queue counter starts increasing till getting the same value than store and they both keep that for some hours. The logs are in debug, and i have nothing saying the smsc is rejecting or something like that ... i realy dont know how to resolve such a problem. On Sat, Oct 17, 2009 at 3:37 PM, Alvaro Cornejo cornejo.alv...@gmail.comwrote: the values shown in the specific smsc correspond to messages queues in that specific SMSC. Messages in store size are messages that were not yet assigned to an smsc. kind of global queue. Regards Alvaro On Mon, Sep 7, 2009 at 6:09 AM, Jinson jin...@mobme.in wrote: Hello Group, Below is my http admin view of kannel. I'm not able to understand the exact differnce between message in stored queue and ones shown in each smsc connection. SMS: received 18762 (0 queued), sent 12983 (0 queued), store size 20 SMS: inbound (0.50,7.02,3.44) msg/sec, outbound (0.13,3.37,2.38) msg/sec DLR: 67291 queued, using mysql storage Box connections: smsbox:smsbox, IP 127.0.0.1 (0 queued), (on-line 0d 1h 30m 44s) SMSC connections: xSMPP:xxx: (online 2266s, rcvd 6920, sent 6920, failed 0, queued 0 msgs) xSMPP:xxx: (online 5447s, rcvd 0, sent 0, failed 0, queued 0 msgs) xSMPP:xxx: (online 5447s, rcvd 2102, sent 952, failed 2, queued 716 msgs) xSMPP:xxx: (online 5447s, rcvd 2060, sent 909, failed 3, queued 593 msgs) xSMPP:xxx: (online 5447s, rcvd 2363, sent 1216, failed 1, queued 228 msgs) xSMPP:xxx: (online 5447s, rcvd 2592, sent 1442, failed 4, queued 19 msgs) xSMPP:xxx: (online 5447s, rcvd 2725, sent 1544, failed 33, queued 0 msgs) xSMPP:xxx: (online 5447s, rcvd 0, sent 0, failed 0, queued 0 msgs) --- Thanks Jinson Abraham -- |-| Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier celular y Nextel en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS y GPRS online Visitenos en www.perusms.NET www.smsglobal.com.mx y www.pravcom.com
Re: kannel queue
Did you solve your problem ? On Wed, Oct 14, 2009 at 6:23 AM, SG ositest...@yahoo.com wrote: Hi Manoj Can you send us any other useful stats like... Any errors in the log files.. access logs any debug logs... I think you need to start Kannel with debug enabled this time to note future error. number of messages delivered between start and restart. amount of time kannel is up and running. any such info can be helpful to use our experience. -SG --- On *Tue, 13/10/09, Manoj B kannel.ma...@gmail.com* wrote: From: Manoj B kannel.ma...@gmail.com Subject: kannel queue To: users@kannel.org, manojs...@rediff.co.in Date: Tuesday, 13 October, 2009, 10:10 PM Hi, I have kannel set for send and received sms separately, but from last some days my sending sms is stop working sometime and only receiving works, due to that queue is getting high and after restart the kannel its works again fine.. can u give me some clue to overcome this issue... Thanks Manoj bhamre -- Try the new Yahoo! India Homepage. Click herehttp://in.rd.yahoo.com/tagline_metro_1/*http://in.yahoo.com/trynew .
Re: Message Queue :: Clarification
same here :) On Mon, Sep 7, 2009 at 12:09 PM, Jinson jin...@mobme.in wrote: Hello Group, Below is my http admin view of kannel. I'm not able to understand the exact differnce between message in stored queue and ones shown in each smsc connection. SMS: received 18762 (0 queued), sent 12983 (0 queued), *store size 20* SMS: inbound (0.50,7.02,3.44) msg/sec, outbound (0.13,3.37,2.38) msg/sec DLR: 67291 queued, using mysql storage Box connections: smsbox:smsbox, IP 127.0.0.1 (0 queued), (on-line 0d 1h 30m 44s) SMSC connections: xSMPP:xxx: (online 2266s, rcvd 6920, sent 6920, failed 0, queued 0 msgs) xSMPP:xxx: (online 5447s, rcvd 0, sent 0, failed 0, queued 0 msgs) xSMPP:xxx: (online 5447s, rcvd 2102, sent 952, failed 2,* **queued 716 msgs)* xSMPP:xxx: (online 5447s, rcvd 2060, sent 909, failed 3,* queued 593 msgs)* xSMPP:xxx: (online 5447s, rcvd 2363, sent 1216, failed 1, *queued 228 msgs)* xSMPP:xxx: (online 5447s, rcvd 2592, sent 1442, failed 4, *queued 19 msgs)* xSMPP:xxx: (online 5447s, rcvd 2725, sent 1544, failed 33, queued 0 msgs) xSMPP:xxx: (online 5447s, rcvd 0, sent 0, failed 0, queued 0 msgs) --- Thanks Jinson Abraham
SqlboxBearerbox architecture, kannel is freezing on mass sms
Hello all, I have Kannel 1.4.3 with Sqlbox 0.7.2 installed successfully, the solution hangs when executing mass SMS campaigns. I have advanced monitoring on the queues, sqlbox queue table, bearerbox's store and even parsing the http kannel status page and plottinh the values to some graphs. The hanging is made at a random time, the store stops to be sent and the *queued sent* items starts growing with no reason and nothing in the logs (debug level), the *queued sent* value is got from SMS: received 1 (0 queued), sent 0 (*0 queued*), store size 0 from the kannel's status page. I want to know where is those messages are queued ? what process is responsible of them ... i thought the store was the last step before delivering the MT SMS to the operator (i have an SMPP one). Can you please get me a clear idea of that ?
Store's growing, smsbox doesnt seem to take MOs
I have a problem with MOs get no execution and stay on the bearer side (queued). Problem is detected on 1.4.1, upgraded to the latest cvs HEAD (cvs-20080409) and still have the same problem. I receive MOs, but nothing gets passed to smsbox, reading the logs, for every received MO (in the access log) i get a line in the bearerbox-log like this: 2008-04-14 16:44:44 [19228] [9] WARNING: smsbox_list empty! I thought smsbox is not connected to bearerbox, but it's not the case, i have lines like this: 2008-04-14 16:39:59 [19228] [5] INFO: Client connected from 127.0.0.1 I get such problem in a non regular basis, kannel keeps going without problems and with nothing new, it gets into queuing MOs and stops forwarding to smsbox. here's a typical status page of kannel at the queuing stage: Kannel bearerbox version `cvs-20080409'. Build `Apr 14 2008 16:34:09', compiler `4.1.2 20061115 (prerelease) (Debian 4.1.1-21)'. System Linux, release 2.6.18-5-686, version #1 SMP Tue Dec 18 21:24:20 UTC 2007, machine i686. Hostname tux2.tun-school.com, IP 127.0.1.1. Libxml version 2.6.27.Using OpenSSL 0.9.8c 05 Sep 2006. Using native malloc. Status: running, uptime 0d 0h 7m 3s WDP: received 0 (0 queued), sent 0 (0 queued) SMS: received 89 (89 queued), sent 0 (0 queued), store size 89 SMS: inbound 0.21 msg/sec, outbound 0.00 msg/sec DLR: 19 queued, using pgsql storage Box connections: smsbox:smsbox-01, IP 127.0.0.1 (0 queued), (on-line 0d 0h 7m 1s) smsbox:smsbox-01, IP 127.0.0.1 (0 queued), (on-line 0d 0h 6m 2s) SMSC connections: *SMPP-01-TT*SMPP:172.17.23.6:2775/2775:smgs:VMA (online 423s, rcvd 0, sent 0, failed 0, queued 0 msgs) *SMPP-02-TT*SMPP:192.168.160.18:2775/2775:reclamationtt:VMA (online 423s, rcvd 89, sent 0, failed 0, queued 0 msgs) As you can see, and as i can understand :) ,smsbox is connected (i dont know why it shows two smsboxes with the same id, i have only one) and there's nothing queued at smsbox side ... Am using sqlbox for MT sending, but as i think, it has nothing to do with this randomly occured problem. Hoping to get any help, thanks,
Re: Store's growing, smsbox doesnt seem to take MOs
Ok: smsc.conf: group = smsc denied-smsc-id = SMPP-02-TX smsc-id = SMPP-01-TX smsc = smpp interface-version = 33 host = 172.12.22.2 port = 2775 receive-port = 2775 smsc-username = kannel smsc-password = sa1654kk system-type = VMA reroute-dlr = true log-file = /var/log/kannel/smpp01tt.log log-level = 1 group = smsc denied-smsc-id = SMPP-01-TX smsc-id = SMPP-02-TX smsc = smpp interface-version = 33 host = 192.168.162.23 port = 2775 receive-port = 2775 smsc-username = aaz788 smsc-password = system-type = VMA log-file = /var/log/kannel/smpp02tt.log log-level = 2 routing-mo.conf group = sms-service keyword = default get-url = http://10.10.4.3/kannel/prvservlet/rec.php?sender=%ptext=%abinarycontent=%bsmscid=%ireceiver=%Pcoding=%ccharset=%Cudh=%uaccount=%odate=%ttimestamp=%Tsmsservicename=%nsmsid=%IdeliveryReportValue=%d max-messages = 0 routing-mt.conf group = sendsms-user forced-smsc = SMPP-01-TX username = mxg00 password = mxg00 default-sender = 1654 max-messages = 3 group = sendsms-user forced-smsc = SMPP-02-TX username = modem password = modem default-sender = 17229 db.conf group = pgsql-connection id = dlr-01-db host = localhost port = 5432 username = kannel password = kannadmxx database = kannel max-connections = 4 routing-dlr.conf group = dlr-db id = dlr-01-db table = dlr field-smsc = smsc field-timestamp = date field-destination = da field-source = soa field-service = service field-url = url field-mask = mask field-status = status field-boxc-id = boxcid Hope i was helpfull enough ;) On Mon, Apr 14, 2008 at 8:58 PM, info.ubichip [EMAIL PROTECTED] wrote: Hello, could you provide the following files, in order to see if something missing : include = /etc/kannel/bx-sms.conf include = /etc/kannel/smsc.conf include = /etc/kannel/routing-mo.conf include = /etc/kannel/routing-mt.conf include = /etc/kannel/db.conf include = /etc/kannel/routing-dlr.conf regards -- *From:* Fourat ZOUARI [mailto:[EMAIL PROTECTED] *Sent:* lundi 14 avril 2008 11:05 *To:* seik *Cc:* users @ kannel. org *Subject:* Re: Store's growing, smsbox doesnt seem to take MOs Here's the configs: group = core admin-port = 13000 admin-password = fxxbar status-password = sTtx admin-deny-ip = *.*.*.* admin-allow-ip = *.*.*.* box-deny-ip = *.*.*.* box-allow-ip = *.*.*.* wdp-interface-name = * log-file = /var/log/kannel/main.log log-level = 1 access-log = /var/log/kannel/raw.log smsbox-port = 13001 dlr-storage = pgsql store-type = spool store-location = /var/spool/kannel #include = /etc/kannel/bx-sql.conf include = /etc/kannel/bx-sms.conf include = /etc/kannel/smsc.conf include = /etc/kannel/routing-mo.conf include = /etc/kannel/routing-mt.conf include = /etc/kannel/db.conf include = /etc/kannel/routing-dlr.conf group = smsbox bearerbox-host = localhost log-file = /var/log/kannel/bx-sms.log log-level = 0 mo-recode = true http-request-retry = 10 http-queue-delay = 60 smsbox-id = smsbox-01 sendsms-port = 13002 #bearerbox-is-sqlbox = true group = smsbox bearerbox-host = localhost log-file = /var/log/kannel/bx-sms2.log log-level = 0 mo-recode = true http-request-retry = 10 http-queue-delay = 60 #smsbox-id = smsbox-01 sendsms-port = 13002 #bearerbox-is-sqlbox = true group = sqlbox id = dlr-01-db smsbox-id = smsbox-01 bearerbox-host = 127.0.0.1 bearerbox-port = 13001 smsbox-port = 13005 smsbox-port-ssl = false sql-log-table = k_messaginglog sql-insert-table = k_messagingqueues log-file = /var/log/kannel/bx-sql.log log-level = 2 And here's the startup script: #!/bin/sh START_SMSBOX='YES' START_WAPBOX='' START_SQLBOX='YES' BOXPATH=/usr/local/sbin PIDFILES=/var/kannel CONF=/etc/kannel/bx-bearer.conf CONFSQL=/etc/kannel/bx-sql.conf PATH=$BOXPATH:$PATH case $1 in start) echo -n Starting Kannel: echo -n bearerbox start-stop-daemon --start --quiet \ --pidfile $PIDFILES/bearerbox.pid \ --chuid kannel \ --exec $BOXPATH/run_kannel_box \ -- \ --pidfile $PIDFILES/bearerbox.pid \ --no-extra-args \ $BOXPATH/bearerbox -v 4 -- $CONF sleep 1 # Wait for bearerbox test ! -z $START_SQLBOX ( echo -n SQL start-stop-daemon --start --quiet \ --pidfile $PIDFILES/sqlbox.pid \ --chuid kannel \ --exec $BOXPATH/run_kannel_box \ -- \ --pidfile $PIDFILES/sqlbox.pid \ --no-extra-args \ /usr/local/bin/sqlbox -v 4 -- $CONFSQL ) test ! -z $START_WAPBOX ( echo -n WAP start-stop-daemon --start --quiet \ --pidfile $PIDFILES/wapbox.pid \ --chuid kannel \ --exec $BOXPATH/run_kannel_box \ -- \ --pidfile
Re: Re[2]: Store's growing, smsbox doesnt seem to take MOs
.
;;
reload)
# We don't have support for this yet.
exit 1
;;
restart|force-reload)
$0 stop
sleep 10
$0 start
;;
*)
echo Usage: $0 {start|stop|restart|force-reload}
exit 1
esac
exit 0
On Mon, Apr 14, 2008 at 7:01 PM, seik [EMAIL PROTECTED] wrote:
what is the start order of your kannel boxes ?
bearerbox, then sqlbox, then smsbox ?
OR bearerbox, smsbox, sqlbox ?
what ARE the sqlbox and the smsbox config ?
-Original Message-
From: users@kannel.org [EMAIL PROTECTED]
Sent: 14 ? 2008 ?.
To: seik
Subject:Store's growing, smsbox doesnt seem to take MOs
I have a problem with MOs get no execution and stay on the bearer side
(queued).
Problem is detected on 1.4.1, upgraded to the latest cvs HEAD
(cvs-20080409) and still have the same problem.
I receive MOs, but nothing gets passed to smsbox, reading the logs,
for every received MO (in the access log) i get a line in the
bearerbox-log like this:
2008-04-14 16:44:44 [19228] [9] WARNING: smsbox_list empty!
I thought smsbox is not connected to bearerbox, but it's not the case,
i have lines like this:
2008-04-14 16:39:59 [19228] [5] INFO: Client connected from 127.0.0.1
I get such problem in a non regular basis, kannel keeps going
without problems and with nothing new, it gets into queuing MOs and
stops forwarding to smsbox.
here's a typical status page of kannel at the queuing stage:
Kannel bearerbox version `cvs-20080409'. Build `Apr 14 2008
16:34:09', compiler `4.1.2 20061115 (prerelease) (Debian 4.1.1-21)'.
System Linux, release 2.6.18-5-686, version #1 SMP Tue Dec 18
21:24:20 UTC 2007, machine i686. Hostname tux2.tun-school.com, IP
127.0.1.1. Libxml version 2.6.27. Using OpenSSL 0.9.8c 05 Sep 2006.
Using native malloc.
Status: running, uptime 0d 0h 7m 3s
WDP: received 0 (0 queued), sent 0 (0 queued)
SMS: received 89 (89 queued), sent 0 (0 queued), store size 89
SMS: inbound 0.21 msg/sec, outbound 0.00 msg/sec
DLR: 19 queued, using pgsql storage
Box connections:
smsbox:smsbox-01, IP 127.0.0.1 (0 queued), (on-line 0d 0h 7m 1s)
smsbox:smsbox-01, IP 127.0.0.1 (0 queued), (on-line 0d 0h 6m 2s)
SMSC connections:
SMPP-01-TTSMPP:172.17.23.6:2775/2775:smgs:VMA (online 423s,
rcvd 0, sent 0, failed 0, queued 0 msgs)
SMPP-02-TTSMPP:192.168.160.18:2775/2775:reclamationtt:VMA
(online 423s, rcvd 89, sent 0, failed 0, queued 0 msgs)
As you can see, and as i can understand ,smsbox is connected (i
dont know why it shows two smsboxes with the same id, i have only
one) and there's nothing queued at smsbox side ...
Am using sqlbox for MT sending, but as i think, it has nothing to
do with this randomly occured problem.
Hoping to get any help, thanks,
--
Fourat Zouari
TriTUX - You think it, we do it!
Web : http://www.tritux.com
Office : +216 71 84 88 44
Mobile : +216 20 20 30 60
Fax : +216 71 84 68 48
Email : [EMAIL PROTECTED]
Skype : tritux
Re: Forcing timetoleave value
Hope this will help : Using Kannel 1.4.1 and standalone sqlbox version on : Linux tux2 2.6.18-3-686 #1 SMP Mon Dec 4 16:41:14 UTC 2006 i686 GNU/Linux Here's two MT message sending cases : -[ Case 1 ]- Begin Message received on cellphone : OK Message ACK : OK System Time : mardi 27 février 2007, 14:56:43 (UTC+0100) SMPP LOG : 2007-02-27 14:56:43 [6518] [12] DEBUG: SMPP PDU 0xabe00ae8 dump: 2007-02-27 14:56:43 [6518] [12] DEBUG: type_name: submit_sm 2007-02-27 14:56:43 [6518] [12] DEBUG: command_id: 4 = 0x0004 2007-02-27 14:56:43 [6518] [12] DEBUG: command_status: 0 = 0x 2007-02-27 14:56:43 [6518] [12] DEBUG: sequence_number: 16142 = 0x3f0e 2007-02-27 14:56:43 [6518] [12] DEBUG: service_type: NULL 2007-02-27 14:56:43 [6518] [12] DEBUG: source_addr_ton: 2 = 0x0002 2007-02-27 14:56:43 [6518] [12] DEBUG: source_addr_npi: 1 = 0x0001 2007-02-27 14:56:43 [6518] [12] DEBUG: source_addr: 27200 2007-02-27 14:56:43 [6518] [12] DEBUG: dest_addr_ton: 1 = 0x0001 2007-02-27 14:56:43 [6518] [12] DEBUG: dest_addr_npi: 1 = 0x0001 2007-02-27 14:56:43 [6518] [12] DEBUG: destination_addr: 26276778 2007-02-27 14:56:43 [6518] [12] DEBUG: esm_class: 3 = 0x0003 2007-02-27 14:56:43 [6518] [12] DEBUG: protocol_id: 0 = 0x 2007-02-27 14:56:43 [6518] [12] DEBUG: priority_flag: 0 = 0x 2007-02-27 14:56:43 [6518] [12] DEBUG: schedule_delivery_time: 070227135643000+ 2007-02-27 14:56:43 [6518] [12] DEBUG: validity_period: 070227135643000+ 2007-02-27 14:56:43 [6518] [12] DEBUG: registered_delivery: 1 = 0x0001 2007-02-27 14:56:43 [6518] [12] DEBUG: replace_if_present_flag: 0 = 0x 2007-02-27 14:56:43 [6518] [12] DEBUG: data_coding: 0 = 0x 2007-02-27 14:56:43 [6518] [12] DEBUG: sm_default_msg_id: 0 = 0x 2007-02-27 14:56:43 [6518] [12] DEBUG: sm_length: 4 = 0x0004 2007-02-27 14:56:43 [6518] [12] DEBUG: short_message: test 2007-02-27 14:56:43 [6518] [12] DEBUG: SMPP PDU dump ends. -[ Case 1 ]- End -[ Case 2 ]- Begin Message received on cellphone : KO Message ACK : OK System Time : mardi 27 février 2007, 12:59:08 (UTC+0100) SMPP LOG : 2007-02-27 12:59:08 [6518] [12] DEBUG: SMPP PDU 0xabe00ae8 dump: 2007-02-27 12:59:08 [6518] [12] DEBUG: type_name: submit_sm 2007-02-27 12:59:08 [6518] [12] DEBUG: command_id: 4 = 0x0004 2007-02-27 12:59:08 [6518] [12] DEBUG: command_status: 0 = 0x 2007-02-27 12:59:08 [6518] [12] DEBUG: sequence_number: 16195 = 0x3f43 2007-02-27 12:59:08 [6518] [12] DEBUG: service_type: NULL 2007-02-27 12:59:08 [6518] [12] DEBUG: source_addr_ton: 2 = 0x0002 2007-02-27 12:59:08 [6518] [12] DEBUG: source_addr_npi: 1 = 0x0001 2007-02-27 12:59:08 [6518] [12] DEBUG: source_addr: 27200 2007-02-27 12:59:08 [6518] [12] DEBUG: dest_addr_ton: 1 = 0x0001 2007-02-27 12:59:08 [6518] [12] DEBUG: dest_addr_npi: 1 = 0x0001 2007-02-27 12:59:08 [6518] [12] DEBUG: destination_addr: 26276778 2007-02-27 12:59:08 [6518] [12] DEBUG: esm_class: 3 = 0x0003 2007-02-27 12:59:08 [6518] [12] DEBUG: protocol_id: 0 = 0x 2007-02-27 12:59:08 [6518] [12] DEBUG: priority_flag: 0 = 0x 2007-02-27 12:59:08 [6518] [12] DEBUG: schedule_delivery_time: 070227115908000+ 2007-02-27 12:59:08 [6518] [12] DEBUG: validity_period: 070227115908000+ 2007-02-27 12:59:08 [6518] [12] DEBUG: registered_delivery: 1 = 0x0001 2007-02-27 12:59:08 [6518] [12] DEBUG: replace_if_present_flag: 0 = 0x 2007-02-27 12:59:08 [6518] [12] DEBUG: data_coding: 0 = 0x 2007-02-27 12:59:08 [6518] [12] DEBUG: sm_default_msg_id: 0 = 0x 2007-02-27 12:59:08 [6518] [12] DEBUG: sm_length: 4 = 0x0004 2007-02-27 12:59:08 [6518] [12] DEBUG: short_message: test 2007-02-27 12:59:08 [6518] [12] DEBUG: SMPP PDU dump ends. -[ Case 2 ]- End And here's the configuration settings for the SMSC handling these messages : -[ SMSC Conf ]- Begin group = smsc denied-smsc-id = SMPP-01-TB;SMPP-02-TB;SMPP-03-TB smsc-id = SMPP-02-TF smsc = smpp interface-version = 34 host = 122.27.24.61 port = 2275 receive-port = 2275 smsc-username = tikcom smsc-password = tiki223 system-type = VMA address-range = reroute-dlr = true enquire-link-interval = 4 throughput = 2 validityperiod = 1440 -[ SMSC Conf ]- End I have the same problem, with and without that 'validityperiod' On 2/26/07, Alexander Malysh [EMAIL PROTECTED] wrote: Hi again, Fourat Zouari wrote: Am in dicussion with the SMSC Gateway provider support, they say that kannel is forcing the validityperiod depending on its system local time, this is a snapshot of log when sending an SMS-MT : did you tried to send this output to SMSC guys? see bellow... -- BEGIN 2007-02-26 19:57:58 [24849] [12] DEBUG: SMPP PDU 0xb01053f0 dump: 2007-02-26 19:57:58 [24849] [12] DEBUG: type_name: submit_sm 2007-02-26 19:57:58 [24849
Re: Forcing timetoleave value
Hi, I dont really see where can i get that thing since am using sqlbox to bypass smsbox (injecting directly into SQL Table). How can we debug this ? Thanks for your support On 2/27/07, Alexander Malysh [EMAIL PROTECTED] wrote: Hi, could you please provide URL with all cgi vars you used to send these messages. On Dienstag, 27. Februar 2007, Fourat Zouari wrote: Hope this will help : Using Kannel 1.4.1 and standalone sqlbox version on : Linux tux2 2.6.18-3-686 #1 SMP Mon Dec 4 16:41:14 UTC 2006 i686 GNU/Linux Here's two MT message sending cases : -[ Case 1 ]- Begin Message received on cellphone : OK Message ACK : OK System Time : mardi 27 février 2007, 14:56:43 (UTC+0100) SMPP LOG : 2007-02-27 14:56:43 [6518] [12] DEBUG: SMPP PDU 0xabe00ae8 dump: 2007-02-27 14:56:43 [6518] [12] DEBUG: type_name: submit_sm 2007-02-27 14:56:43 [6518] [12] DEBUG: command_id: 4 = 0x0004 2007-02-27 14:56:43 [6518] [12] DEBUG: command_status: 0 = 0x 2007-02-27 14:56:43 [6518] [12] DEBUG: sequence_number: 16142 = 0x3f0e 2007-02-27 14:56:43 [6518] [12] DEBUG: service_type: NULL 2007-02-27 14:56:43 [6518] [12] DEBUG: source_addr_ton: 2 = 0x0002 2007-02-27 14:56:43 [6518] [12] DEBUG: source_addr_npi: 1 = 0x0001 2007-02-27 14:56:43 [6518] [12] DEBUG: source_addr: 27200 2007-02-27 14:56:43 [6518] [12] DEBUG: dest_addr_ton: 1 = 0x0001 2007-02-27 14:56:43 [6518] [12] DEBUG: dest_addr_npi: 1 = 0x0001 2007-02-27 14:56:43 [6518] [12] DEBUG: destination_addr: 26276778 2007-02-27 14:56:43 [6518] [12] DEBUG: esm_class: 3 = 0x0003 2007-02-27 14:56:43 [6518] [12] DEBUG: protocol_id: 0 = 0x 2007-02-27 14:56:43 [6518] [12] DEBUG: priority_flag: 0 = 0x 2007-02-27 14:56:43 [6518] [12] DEBUG: schedule_delivery_time: 070227135643000+ 2007-02-27 14:56:43 [6518] [12] DEBUG: validity_period: 070227135643000+ 2007-02-27 14:56:43 [6518] [12] DEBUG: registered_delivery: 1 = 0x0001 2007-02-27 14:56:43 [6518] [12] DEBUG: replace_if_present_flag: 0 = 0x 2007-02-27 14:56:43 [6518] [12] DEBUG: data_coding: 0 = 0x 2007-02-27 14:56:43 [6518] [12] DEBUG: sm_default_msg_id: 0 = 0x 2007-02-27 14:56:43 [6518] [12] DEBUG: sm_length: 4 = 0x0004 2007-02-27 14:56:43 [6518] [12] DEBUG: short_message: test 2007-02-27 14:56:43 [6518] [12] DEBUG: SMPP PDU dump ends. -[ Case 1 ]- End -[ Case 2 ]- Begin Message received on cellphone : KO Message ACK : OK System Time : mardi 27 février 2007, 12:59:08 (UTC+0100) SMPP LOG : 2007-02-27 12:59:08 [6518] [12] DEBUG: SMPP PDU 0xabe00ae8 dump: 2007-02-27 12:59:08 [6518] [12] DEBUG: type_name: submit_sm 2007-02-27 12:59:08 [6518] [12] DEBUG: command_id: 4 = 0x0004 2007-02-27 12:59:08 [6518] [12] DEBUG: command_status: 0 = 0x 2007-02-27 12:59:08 [6518] [12] DEBUG: sequence_number: 16195 = 0x3f43 2007-02-27 12:59:08 [6518] [12] DEBUG: service_type: NULL 2007-02-27 12:59:08 [6518] [12] DEBUG: source_addr_ton: 2 = 0x0002 2007-02-27 12:59:08 [6518] [12] DEBUG: source_addr_npi: 1 = 0x0001 2007-02-27 12:59:08 [6518] [12] DEBUG: source_addr: 27200 2007-02-27 12:59:08 [6518] [12] DEBUG: dest_addr_ton: 1 = 0x0001 2007-02-27 12:59:08 [6518] [12] DEBUG: dest_addr_npi: 1 = 0x0001 2007-02-27 12:59:08 [6518] [12] DEBUG: destination_addr: 26276778 2007-02-27 12:59:08 [6518] [12] DEBUG: esm_class: 3 = 0x0003 2007-02-27 12:59:08 [6518] [12] DEBUG: protocol_id: 0 = 0x 2007-02-27 12:59:08 [6518] [12] DEBUG: priority_flag: 0 = 0x 2007-02-27 12:59:08 [6518] [12] DEBUG: schedule_delivery_time: 070227115908000+ 2007-02-27 12:59:08 [6518] [12] DEBUG: validity_period: 070227115908000+ 2007-02-27 12:59:08 [6518] [12] DEBUG: registered_delivery: 1 = 0x0001 2007-02-27 12:59:08 [6518] [12] DEBUG: replace_if_present_flag: 0 = 0x 2007-02-27 12:59:08 [6518] [12] DEBUG: data_coding: 0 = 0x 2007-02-27 12:59:08 [6518] [12] DEBUG: sm_default_msg_id: 0 = 0x 2007-02-27 12:59:08 [6518] [12] DEBUG: sm_length: 4 = 0x0004 2007-02-27 12:59:08 [6518] [12] DEBUG: short_message: test 2007-02-27 12:59:08 [6518] [12] DEBUG: SMPP PDU dump ends. -[ Case 2 ]- End And here's the configuration settings for the SMSC handling these messages : -[ SMSC Conf ]- Begin group = smsc denied-smsc-id = SMPP-01-TB;SMPP-02-TB;SMPP-03-TB smsc-id = SMPP-02-TF smsc = smpp interface-version = 34 host = 122.27.24.61 port = 2275 receive-port = 2275 smsc-username = tikcom smsc-password = tiki223 system-type = VMA address-range = reroute-dlr = true enquire-link-interval = 4 throughput = 2 validityperiod = 1440 -[ SMSC Conf ]- End I have the same problem, with and without that 'validityperiod' On 2/26/07, Alexander Malysh [EMAIL PROTECTED] wrote: Hi again, Fourat Zouari wrote: Am
Re: Forcing timetoleave value
seems to be the reason for that :) thanks for your help. anyway, where can we found a well documented sqlbox integration ? On 2/27/07, Alexander Malysh [EMAIL PROTECTED] wrote: Then it seems your error... Please try insert deferred and validity as NULL not 0 into table for sqlbox. Fourat Zouari wrote: Hi, I dont really see where can i get that thing since am using sqlbox to bypass smsbox (injecting directly into SQL Table). How can we debug this ? Thanks for your support On 2/27/07, Alexander Malysh [EMAIL PROTECTED] wrote: Hi, could you please provide URL with all cgi vars you used to send these messages. On Dienstag, 27. Februar 2007, Fourat Zouari wrote: Hope this will help : Using Kannel 1.4.1 and standalone sqlbox version on : Linux tux2 2.6.18-3-686 #1 SMP Mon Dec 4 16:41:14 UTC 2006 i686 GNU/Linux Here's two MT message sending cases : -[ Case 1 ]- Begin Message received on cellphone : OK Message ACK : OK System Time : mardi 27 février 2007, 14:56:43 (UTC+0100) SMPP LOG : 2007-02-27 14:56:43 [6518] [12] DEBUG: SMPP PDU 0xabe00ae8 dump: 2007-02-27 14:56:43 [6518] [12] DEBUG: type_name: submit_sm 2007-02-27 14:56:43 [6518] [12] DEBUG: command_id: 4 = 0x0004 2007-02-27 14:56:43 [6518] [12] DEBUG: command_status: 0 = 0x 2007-02-27 14:56:43 [6518] [12] DEBUG: sequence_number: 16142 = 0x3f0e 2007-02-27 14:56:43 [6518] [12] DEBUG: service_type: NULL 2007-02-27 14:56:43 [6518] [12] DEBUG: source_addr_ton: 2 = 0x0002 2007-02-27 14:56:43 [6518] [12] DEBUG: source_addr_npi: 1 = 0x0001 2007-02-27 14:56:43 [6518] [12] DEBUG: source_addr: 27200 2007-02-27 14:56:43 [6518] [12] DEBUG: dest_addr_ton: 1 = 0x0001 2007-02-27 14:56:43 [6518] [12] DEBUG: dest_addr_npi: 1 = 0x0001 2007-02-27 14:56:43 [6518] [12] DEBUG: destination_addr: 26276778 2007-02-27 14:56:43 [6518] [12] DEBUG: esm_class: 3 = 0x0003 2007-02-27 14:56:43 [6518] [12] DEBUG: protocol_id: 0 = 0x 2007-02-27 14:56:43 [6518] [12] DEBUG: priority_flag: 0 = 0x 2007-02-27 14:56:43 [6518] [12] DEBUG: schedule_delivery_time: 070227135643000+ 2007-02-27 14:56:43 [6518] [12] DEBUG: validity_period: 070227135643000+ 2007-02-27 14:56:43 [6518] [12] DEBUG: registered_delivery: 1 = 0x0001 2007-02-27 14:56:43 [6518] [12] DEBUG: replace_if_present_flag: 0 = 0x 2007-02-27 14:56:43 [6518] [12] DEBUG: data_coding: 0 = 0x 2007-02-27 14:56:43 [6518] [12] DEBUG: sm_default_msg_id: 0 = 0x 2007-02-27 14:56:43 [6518] [12] DEBUG: sm_length: 4 = 0x0004 2007-02-27 14:56:43 [6518] [12] DEBUG: short_message: test 2007-02-27 14:56:43 [6518] [12] DEBUG: SMPP PDU dump ends. -[ Case 1 ]- End -[ Case 2 ]- Begin Message received on cellphone : KO Message ACK : OK System Time : mardi 27 février 2007, 12:59:08 (UTC+0100) SMPP LOG : 2007-02-27 12:59:08 [6518] [12] DEBUG: SMPP PDU 0xabe00ae8 dump: 2007-02-27 12:59:08 [6518] [12] DEBUG: type_name: submit_sm 2007-02-27 12:59:08 [6518] [12] DEBUG: command_id: 4 = 0x0004 2007-02-27 12:59:08 [6518] [12] DEBUG: command_status: 0 = 0x 2007-02-27 12:59:08 [6518] [12] DEBUG: sequence_number: 16195 = 0x3f43 2007-02-27 12:59:08 [6518] [12] DEBUG: service_type: NULL 2007-02-27 12:59:08 [6518] [12] DEBUG: source_addr_ton: 2 = 0x0002 2007-02-27 12:59:08 [6518] [12] DEBUG: source_addr_npi: 1 = 0x0001 2007-02-27 12:59:08 [6518] [12] DEBUG: source_addr: 27200 2007-02-27 12:59:08 [6518] [12] DEBUG: dest_addr_ton: 1 = 0x0001 2007-02-27 12:59:08 [6518] [12] DEBUG: dest_addr_npi: 1 = 0x0001 2007-02-27 12:59:08 [6518] [12] DEBUG: destination_addr: 26276778 2007-02-27 12:59:08 [6518] [12] DEBUG: esm_class: 3 = 0x0003 2007-02-27 12:59:08 [6518] [12] DEBUG: protocol_id: 0 = 0x 2007-02-27 12:59:08 [6518] [12] DEBUG: priority_flag: 0 = 0x 2007-02-27 12:59:08 [6518] [12] DEBUG: schedule_delivery_time: 070227115908000+ 2007-02-27 12:59:08 [6518] [12] DEBUG: validity_period: 070227115908000+ 2007-02-27 12:59:08 [6518] [12] DEBUG: registered_delivery: 1 = 0x0001 2007-02-27 12:59:08 [6518] [12] DEBUG: replace_if_present_flag: 0 = 0x 2007-02-27 12:59:08 [6518] [12] DEBUG: data_coding: 0 = 0x 2007-02-27 12:59:08 [6518] [12] DEBUG: sm_default_msg_id: 0 = 0x 2007-02-27 12:59:08 [6518] [12] DEBUG: sm_length: 4 = 0x0004 2007-02-27 12:59:08 [6518] [12] DEBUG: short_message: test 2007-02-27 12:59:08 [6518] [12] DEBUG: SMPP PDU dump ends. -[ Case 2 ]- End And here's the configuration settings for the SMSC handling these messages : -[ SMSC Conf ]- Begin group = smsc denied-smsc-id = SMPP-01-TB;SMPP-02-TB;SMPP-03-TB smsc-id = SMPP-02-TF smsc = smpp interface-version = 34 host = 122.27.24.61
Re: Forcing timetoleave value
yes it is, how can i fix this ? On 2/23/07, Alexander Malysh [EMAIL PROTECTED] wrote: Hi, what kannel version? if this is 1.4.1 then it must be bug at SMSC because kannel send validity and deferred always in UTC and set it correctly according to SMPP spec. Fourat Zouari wrote: anyone ? On 2/21/07, Fourat Zouari [EMAIL PROTECTED] wrote: Hello, I have Kannel connected to Telecom Operator's SMSC 'SMPP3.4'. The Operator's servers time has +2 hours on me, the correct time is mine and the operator wont adjust his time. The problem is when trying to send an MT, my MT is marked on the operator's SMSC with a timetoleave inferior to its time so it will not be delivered to mobile. As a workaround i synchronize my time on the operator's time and all's done, but after all i wont have a incorrect time. I tryed to set validityperiod to : validityperiod = 1440 But no difference, MTs will pass only when i synchronize my server time on the operator server time. -- Thanks, Alex
Re: Forcing timetoleave value
Am in dicussion with the SMSC Gateway provider support, they say that kannel is forcing the validityperiod depending on its system local time, this is a snapshot of log when sending an SMS-MT : -- BEGIN 2007-02-26 19:57:58 [24849] [12] DEBUG: SMPP PDU 0xb01053f0 dump: 2007-02-26 19:57:58 [24849] [12] DEBUG: type_name: submit_sm 2007-02-26 19:57:58 [24849] [12] DEBUG: command_id: 4 = 0x0004 2007-02-26 19:57:58 [24849] [12] DEBUG: command_status: 0 = 0x 2007-02-26 19:57:58 [24849] [12] DEBUG: sequence_number: 914 = 0x0392 2007-02-26 19:57:58 [24849] [12] DEBUG: service_type: NULL 2007-02-26 19:57:58 [24849] [12] DEBUG: source_addr_ton: 2 = 0x0002 2007-02-26 19:57:58 [24849] [12] DEBUG: source_addr_npi: 1 = 0x0001 2007-02-26 19:57:58 [24849] [12] DEBUG: source_addr: 22700 2007-02-26 19:57:58 [24849] [12] DEBUG: dest_addr_ton: 1 = 0x0001 2007-02-26 19:57:58 [24849] [12] DEBUG: dest_addr_npi: 1 = 0x0001 2007-02-26 19:57:58 [24849] [12] DEBUG: destination_addr: 28582653 2007-02-26 19:57:58 [24849] [12] DEBUG: esm_class: 3 = 0x0003 2007-02-26 19:57:58 [24849] [12] DEBUG: protocol_id: 0 = 0x 2007-02-26 19:57:58 [24849] [12] DEBUG: priority_flag: 0 = 0x 2007-02-26 19:57:58 [24849] [12] DEBUG: schedule_delivery_time: 070226185758000+ 2007-02-26 19:57:58 [24849] [12] DEBUG: validity_period: 070226185758000+ 2007-02-26 19:57:58 [24849] [12] DEBUG: registered_delivery: 1 = 0x0001 2007-02-26 19:57:58 [24849] [12] DEBUG: replace_if_present_flag: 0 = 0x 2007-02-26 19:57:58 [24849] [12] DEBUG: data_coding: 0 = 0x 2007-02-26 19:57:58 [24849] [12] DEBUG: sm_default_msg_id: 0 = 0x 2007-02-26 19:57:58 [24849] [12] DEBUG: sm_length: 4 = 0x0004 2007-02-26 19:57:58 [24849] [12] DEBUG: short_message: test 2007-02-26 19:57:58 [24849] [12] DEBUG: SMPP PDU dump ends. -- END This message is passed to the mobile (succeeded) See the time when sending, it's 2007-02-26 19:57:58 when it was 17:57 really. here's another log snapshot wich doesnt succeed sending the MT : i've just fixed the system time to the real time (18:01) -- BEGIN 2007-02-26 18:01:19 [24849] [12] DEBUG: SMPP PDU 0x85a3920 dump: 2007-02-26 18:01:19 [24849] [12] DEBUG: type_name: submit_sm 2007-02-26 18:01:19 [24849] [12] DEBUG: command_id: 4 = 0x0004 2007-02-26 18:01:19 [24849] [12] DEBUG: command_status: 0 = 0x 2007-02-26 18:01:19 [24849] [12] DEBUG: sequence_number: 1005 = 0x03ed 2007-02-26 18:01:19 [24849] [12] DEBUG: service_type: NULL 2007-02-26 18:01:19 [24849] [12] DEBUG: source_addr_ton: 2 = 0x0002 2007-02-26 18:01:19 [24849] [12] DEBUG: source_addr_npi: 1 = 0x0001 2007-02-26 18:01:19 [24849] [12] DEBUG: source_addr: 22700 2007-02-26 18:01:19 [24849] [12] DEBUG: dest_addr_ton: 1 = 0x0001 2007-02-26 18:01:19 [24849] [12] DEBUG: dest_addr_npi: 1 = 0x0001 2007-02-26 18:01:19 [24849] [12] DEBUG: destination_addr: 28582653 2007-02-26 18:01:19 [24849] [12] DEBUG: esm_class: 3 = 0x0003 2007-02-26 18:01:19 [24849] [12] DEBUG: protocol_id: 0 = 0x 2007-02-26 18:01:19 [24849] [12] DEBUG: priority_flag: 0 = 0x 2007-02-26 18:01:19 [24849] [12] DEBUG: schedule_delivery_time: 070226170119000+ 2007-02-26 18:01:19 [24849] [12] DEBUG: validity_period: 070226170119000+ 2007-02-26 18:01:19 [24849] [12] DEBUG: registered_delivery: 1 = 0x0001 2007-02-26 18:01:19 [24849] [12] DEBUG: replace_if_present_flag: 0 = 0x 2007-02-26 18:01:19 [24849] [12] DEBUG: data_coding: 0 = 0x 2007-02-26 18:01:19 [24849] [12] DEBUG: sm_default_msg_id: 0 = 0x 2007-02-26 18:01:19 [24849] [12] DEBUG: sm_length: 4 = 0x0004 2007-02-26 18:01:19 [24849] [12] DEBUG: short_message: test 2007-02-26 18:01:19 [24849] [12] DEBUG: SMPP PDU dump ends. -- END On 2/26/07, Alexander Malysh [EMAIL PROTECTED] wrote: Hi, this is not a kannel bug and you can do nothing to fix the problem. You can only put pressure on SMSC guys that they fix validity parsing on SMSC side. Fourat Zouari wrote: yes it is, how can i fix this ? On 2/23/07, Alexander Malysh [EMAIL PROTECTED] wrote: Hi, what kannel version? if this is 1.4.1 then it must be bug at SMSC because kannel send validity and deferred always in UTC and set it correctly according to SMPP spec. Fourat Zouari wrote: anyone ? On 2/21/07, Fourat Zouari [EMAIL PROTECTED] wrote: Hello, I have Kannel connected to Telecom Operator's SMSC 'SMPP3.4'. The Operator's servers time has +2 hours on me, the correct time is mine and the operator wont adjust his time. The problem is when trying to send an MT, my MT is marked on the operator's SMSC with a timetoleave inferior to its time so it will not be delivered to mobile. As a workaround i synchronize my time
Re: Forcing timetoleave value
anyone ? On 2/21/07, Fourat Zouari [EMAIL PROTECTED] wrote: Hello, I have Kannel connected to Telecom Operator's SMSC 'SMPP3.4'. The Operator's servers time has +2 hours on me, the correct time is mine and the operator wont adjust his time. The problem is when trying to send an MT, my MT is marked on the operator's SMSC with a timetoleave inferior to its time so it will not be delivered to mobile. As a workaround i synchronize my time on the operator's time and all's done, but after all i wont have a incorrect time. I tryed to set validityperiod to : validityperiod = 1440 But no difference, MTs will pass only when i synchronize my server time on the operator server time.
Re: sqlbox-standalone problem
Can you do a : mysql -uUSER -p -h192.168.1.68 And see if it works ? On 2/22/07, Mi Reflejo [EMAIL PROTECTED] wrote: Why doesn't work?? It should. M On 2/21/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi, Yeah, I have add that directive and it's now connected. But I read on the archieve that sqlbox-standalone doesn't work with 1.4.1. Is that true? Any recommended kannel's version to work best with sqlbox-standalone? Many thanks for the helps. Regards Willy - Original Message - From: Cezary Siwek [EMAIL PROTECTED] To: users@kannel.org Sent: Wednesday, February 21, 2007 5:13 PM Subject: Re: sqlbox-standalone problem hi Willy i had the same problem when i didn't set port = 3306 in sqlbox.conf BTW ... sqlbox was working properly without setting this value when mysql database was installed on the same box with kannel . Cezary
Forcing timetoleave value
Hello, I have Kannel connected to Telecom Operator's SMSC 'SMPP3.4'. The Operator's servers time has +2 hours on me, the correct time is mine and the operator wont adjust his time. The problem is when trying to send an MT, my MT is marked on the operator's SMSC with a timetoleave inferior to its time so it will not be delivered to mobile. As a workaround i synchronize my time on the operator's time and all's done, but after all i wont have a incorrect time. I tryed to set validityperiod to : validityperiod = 1440 But no difference, MTs will pass only when i synchronize my server time on the operator server time.
Re: Setting dlr-url and not receiving DLRs
No, didnt got any solution On 1/19/07, Hofferek Attila [EMAIL PROTECTED] wrote: Fourat Zouari írta: Hello, Am setting dlr-mask to 31, dlr-url to http://localhost/mg/recdlr.php?status=%danswer=%Ats=%tmsgid=3 http://localhost/mg/recdlr.php?status=%danswer=%Ats=%tmsgid=3 msgid is for internal use, the whole url is urlencoded when passed to smsbox, and when sending an MT, i have this in my modem's log: I have this problem too, but with emi connection. Have you got the solution since you asked? -- Hofferek Attila
Re: Setting dlr-url and not receiving DLRs
Nothing in error and access log.
It's very strange
On 12/23/06, Cavit Dolgun [EMAIL PROTECTED] wrote:
Did you check the error log of your apache?
--
*From:* Fourat Zouari [mailto:[EMAIL PROTECTED]
*Sent:* Saturday, December 23, 2006 00:01
*To:* users@kannel.org
*Subject:* Setting dlr-url and not receiving DLRs
Hello,
Am setting dlr-mask to 31, dlr-url to
http://localhost/mg/recdlr.php?status=%danswer=%Ats=%tmsgid=3http://localhost/mg/recdlr.php?status=%25danswer=%25Ats=%25tmsgid=3
msgid is for internal use, the whole url is urlencoded when passed to
smsbox, and when sending an MT, i have this in my modem's log:
-LOG BEGIN
2006-12-22 21:47:50 [27334] [6] DEBUG: AT2[MODEM-01]: send command status:
1
2006-12-22 21:47:50 [27334] [6] DEBUG: AT2[MODEM-01]: --
003100088102020306000FF4F29C0E229741EC30482E83DD00
2006-12-22 21:47:56 [27334] [6] DEBUG: AT2[MODEM-01]: -- ^Z
2006-12-22 21:48:02 [27334] [6] DEBUG: AT2[MODEM-01]: -- +CMGS: 45
2006-12-22 21:48:02 [27334] [6] DEBUG: AT2[MODEM-01]: -- OK
2006-12-22 21:48:02 [27334] [6] DEBUG: AT2[MODEM-01]: send command status:
0
2006-12-22 21:48:02 [27334] [6] DEBUG: DLR[pgsql]: Adding DLR
smsc=MODEM-01, ts=45, src=, dst=20203060, mask=31, boxc=
2006-12-22 21:48:02 [27334] [6] DEBUG: sql: INSERT INTO dlr (smsc, date,
soa, da, service, url, mask, boxcid, status) VALUES ('MODEM-01', '45', '',
'10204080', '', '
http://localhost/mg/recdlr.php?status=%danswer=%Ats=%tmsgid=3http://localhost/mg/recdlr.php?status=%25danswer=%25Ats=%25tmsgid=3',
'31', '', '0');
2006-12-22 21:48:02 [27334] [6] DEBUG: SMSC[MODEM-01]: creating DLR
message
2006-12-22 21:48:02 [27334] [6] DEBUG: SMSC[MODEM-01]: DLR =
http://localhost/mg/recdlr.php?status=%danswer=%Ats=%tmsgid=3http://localhost/mg/recdlr.php?status=%25danswer=%25Ats=%25tmsgid=3
-LOG END
The problem is, the recdlr.php script is never called from kannel, i have
no trace of that in my apache's access log.
Any idea ?
Thanks
Setting dlr-url and not receiving DLRs
Hello,
Am setting dlr-mask to 31, dlr-url to
http://localhost/mg/recdlr.php?status=%danswer=%Ats=%tmsgid=3
msgid is for internal use, the whole url is urlencoded when passed to
smsbox, and when sending an MT, i have this in my modem's log:
-LOG BEGIN
2006-12-22 21:47:50 [27334] [6] DEBUG: AT2[MODEM-01]: send command status: 1
2006-12-22 21:47:50 [27334] [6] DEBUG: AT2[MODEM-01]: --
003100088102020306000FF4F29C0E229741EC30482E83DD00
2006-12-22 21:47:56 [27334] [6] DEBUG: AT2[MODEM-01]: -- ^Z
2006-12-22 21:48:02 [27334] [6] DEBUG: AT2[MODEM-01]: -- +CMGS: 45
2006-12-22 21:48:02 [27334] [6] DEBUG: AT2[MODEM-01]: -- OK
2006-12-22 21:48:02 [27334] [6] DEBUG: AT2[MODEM-01]: send command status: 0
2006-12-22 21:48:02 [27334] [6] DEBUG: DLR[pgsql]: Adding DLR smsc=MODEM-01,
ts=45, src=, dst=20203060, mask=31, boxc=
2006-12-22 21:48:02 [27334] [6] DEBUG: sql: INSERT INTO dlr (smsc, date,
soa, da, service, url, mask, boxcid, status) VALUES ('MODEM-01', '45', '',
'10204080', '', '
http://localhost/mg/recdlr.php?status=%danswer=%Ats=%tmsgid=3', '31',
'', '0');
2006-12-22 21:48:02 [27334] [6] DEBUG: SMSC[MODEM-01]: creating DLR message
2006-12-22 21:48:02 [27334] [6] DEBUG: SMSC[MODEM-01]: DLR =
http://localhost/mg/recdlr.php?status=%danswer=%Ats=%tmsgid=3
-LOG END
The problem is, the recdlr.php script is never called from kannel, i have no
trace of that in my apache's access log.
Any idea ?
Thanks
Re: Re[2]: Failed installing Kannel with a WaveCom Modem
I have it in debug level as long as smsbox and sqlbox On 12/19/06, seik [EMAIL PROTECTED] wrote: Well, according my config ALL the activity regarding SMS traffic is in the main kannel logs. I dont know what data should go to the modem activity log when kannel is not in debug mode:/ Regards seik -Original Message- From: Fourat Zouari [EMAIL PROTECTED] Sent: Monday, December 18, 2006 To: seik Subject:Failed installing Kannel with a WaveCom Modem is it normal that i dont have anything in my logs ? On 12/18/06, [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi Fourat, in general i use the following lines for wavecom modem note i use kermit to preset the pin and the sms-center before to start the bearerbox include = /etc/kannel/seik.modems.conf # SMSC GSM group = smsc smsc = at smsc-id = modem0 denied-smsc-id = clickatell modemtype = wavecom device = /dev/ttyS0 validityperiod = 167 sim-buffering = true sms-center = +3598910 in the /etc/kannel/seik.modems.conf i have for wavecom these settings : group = modems id = wavecom name = Wavecom detect-string = WAVECOM #AT+CGSN #IMEI: 332055336044120 #OK #AT+CNMI=? #+CNMI: (0-3),(0-3),(0-3),(0-2),(0,1) #init-string =AT+CNMI=1,3,2,2,1 #init-string =AT+CNMI=2,1,0,0,0 init-string =AT+CNMI=2,2,0,0,0 speed = 9600 # enable-hwhs = AT\\Q3 #message-storage = MT #enable-mms = true keepalive-cmd = AT+CBC;+CSQ On Mon, Dec 18, 2006 at 09:17:09PM +0100, Fourat Zouari wrote: Hello all, Something strange with kannel, i've configured it for my WAVECOM 1213A GSM modem this way : - ... group = modems id = WAVECOM name = wavecom detect-string = WAVECOM init-string = AT+CNMI=2,2,0,0,0;+CMEE=1 need-sleep = true sendline-sleep = 6000 no-pin = true ... group = smsc smsc-id = MODEM-01 smsc = at modemtype = WAVECOM device = /dev/ttyS0 speed = 9600 log-file = /var/log/smgs/modem.log log-level = 0 - When kannel is started, no modem.log is created, and on the bearerbox log, all is working except that there's no wavecom in the log... Seems just if kannel didnt read the config to go and intiate the modem :( The same config is working on an SMSC, just added those two groups and a serial linked new modem. Any one can help ? thanks
Failed installing Kannel with a WaveCom Modem
Hello all, Something strange with kannel, i've configured it for my WAVECOM 1213A GSM modem this way : - ... group = modems id = WAVECOM name = wavecom detect-string = WAVECOM init-string = AT+CNMI=2,2,0,0,0;+CMEE=1 need-sleep = true sendline-sleep = 6000 no-pin = true ... group = smsc smsc-id = MODEM-01 smsc = at modemtype = WAVECOM device = /dev/ttyS0 speed = 9600 log-file = /var/log/smgs/modem.log log-level = 0 - When kannel is started, no modem.log is created, and on the bearerbox log, all is working except that there's no wavecom in the log... Seems just if kannel didnt read the config to go and intiate the modem :( The same config is working on an SMSC, just added those two groups and a serial linked new modem. Any one can help ? thanks
Re: Failed installing Kannel with a WaveCom Modem
is it normal that i dont have anything in my logs ? On 12/18/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi Fourat, in general i use the following lines for wavecom modem note i use kermit to preset the pin and the sms-center before to start the bearerbox include = /etc/kannel/seik.modems.conf # SMSC GSM group = smsc smsc = at smsc-id = modem0 denied-smsc-id = clickatell modemtype = wavecom device = /dev/ttyS0 validityperiod = 167 sim-buffering = true sms-center = +3598910 in the /etc/kannel/seik.modems.conf i have for wavecom these settings : group = modems id = wavecom name = Wavecom detect-string = WAVECOM #AT+CGSN #IMEI: 332055336044120 #OK #AT+CNMI=? #+CNMI: (0-3),(0-3),(0-3),(0-2),(0,1) #init-string =AT+CNMI=1,3,2,2,1 #init-string =AT+CNMI=2,1,0,0,0 init-string =AT+CNMI=2,2,0,0,0 speed = 9600 # enable-hwhs = AT\\Q3 #message-storage = MT #enable-mms = true keepalive-cmd = AT+CBC;+CSQ On Mon, Dec 18, 2006 at 09:17:09PM +0100, Fourat Zouari wrote: Hello all, Something strange with kannel, i've configured it for my WAVECOM 1213A GSM modem this way : - ... group = modems id = WAVECOM name = wavecom detect-string = WAVECOM init-string = AT+CNMI=2,2,0,0,0;+CMEE=1 need-sleep = true sendline-sleep = 6000 no-pin = true ... group = smsc smsc-id = MODEM-01 smsc = at modemtype = WAVECOM device = /dev/ttyS0 speed = 9600 log-file = /var/log/smgs/modem.log log-level = 0 - When kannel is started, no modem.log is created, and on the bearerbox log, all is working except that there's no wavecom in the log... Seems just if kannel didnt read the config to go and intiate the modem :( The same config is working on an SMSC, just added those two groups and a serial linked new modem. Any one can help ? thanks
[sqlbox] MT is allways sent as flash message.
I'm using sqlbox and it's sending MT and receiving MO, only one problem is that the MTs are sent as flash message. tryed to set the mclass field to 0,1,2 and 3, the message is allways a flash one. The message is stored in sql-log-table with those mclass values, so nothing goes wrong, except it's a flash message.
Re: Queued for later delivery (where is the problem and where I should check?)
did you reolve the problem ? i've got the same issue than you. I can't reproduce it. On 11/8/06, Marcelo Aguila [EMAIL PROTECTED] wrote: Hi. I'm recently started to work with an operator that use SMPP 3.4 so I'm using kannel 1.4.1 (CVS) in a Dell PowerEdge 2950 with one intel xeon dual core processor. Since the problem started I've not touched nor reinitializing anything to see what is happening. Well, after several days of testing suddenly my logs shows that since 2006-11-02 16:55 to 2006-11-07 17:43 (for 5 days) the sendsms started to return Queued for later delivery (158 messages). So, without any intervention since 2006-11-07 17:53 until now (17 new messages), sendsms started to return Accepted for delivery I could check that first queued message was delivered to SMSC at 2006-11-03 02:41 (almost 12 hours after its creation) and the delivery to the phone was made a minute later at 2:42. Why the messages could be queued for later delivey and why the problem stopped 5 days later without any manual intervention. I'm lost because I can't find any clue in the logs (they are configured in debug mode). What could it be, a configuration problem, a communication problem with operator ? Please, any tip? M.
Re: Kannel is sometime freezing and wont let MTs messages go
Hello, Am reopening this issue, because i didnt succeed in resolving it throtling and other recommendations didnt work. To get other informations, kannel isnt stressed enough to be throtled, it's receiving/sending some 100 sms/day But in general, this MT sending freezzz issue is reproduced every time the smpp connectors got a good uptime, as in the status snapshot (44000 seconds and so ...) On 8/21/06, Aarno Syvänen [EMAIL PROTECTED] wrote: Hello, Another possiblity is that your kannel is confifured for debugging, then it will be slow If this is the case, configure for speed (--with-defaults option) Aarno On 11 Aug 2006, at 17:34, Fourat Zouari wrote: Hello, Thanks for your help SMSC is limiting the traffic to 2sms/s, i dont have a big trafic, doing some 1000 to 3000 per day. But if so, should i apply a throttling on my smpp connectors ? On 8/10/06, Aarno Syvänen [EMAIL PROTECTED] wrote: Hi, The queue is simply too long. You must try to find the bottleneck of your system . (SMSC just not accept too many messages, i would quess. If it is so, you should throttle the traffic) Aarno On 26 Jul 2006, at 15:05, Fourat Zouari wrote: heello ;) On 7/24/06, Fourat Zouari [EMAIL PROTECTED] wrote: Am unable to reproduce this phenomen, but it happens sometimes and i just need to reboot kannel service to get the queued MTs go out and sent properly. here's the kannel status when it's blocking/queuing MTs : BEGIN Kannel bearerbox version `cvs-20060301'. Build `May 26 2006 03:43:23', compiler `3.3.5 (Debian 1: 3.3.5-13)'. System Linux, release 2.4.27-2-686, version #1 Wed Aug 17 10:34:09 UTC 2005, machine i686. Hostname tux1.trit.com, IP 172.17.35.130. Libxml version 2.6.16. Using OpenSSL 0.9.7e 25 Oct 2004. Using native malloc. Status: running, uptime 12d 16h 53m 25s WDP: received 0 (0 queued), sent 0 (0 queued) SMS: received 657 (0 queued), sent 161 (566 queued), store size 566 SMS: inbound 0.00 msg/sec, outbound 0.00 msg/sec DLR: 18502 queued, using pgsql storage Box connections: smsbox:(none), IP 127.0.0.1 (0 queued), (on-line 12d 16h 52m 25s) SMSC connections: SMPP-01-TXSMPP: 172.128.30.18:4000/4000:smpp1:VMA (online 44793s, rcvd 257, sent 55, failed 0, queued 0 msgs) SMPP-01-TYSMPP: 172.128.30.23:4000/4000:smpp2:VMA (online 138661s, rcvd 87, sent 37, failed 0, queued 0 msgs) SMPP-02-TZSMPP: 172.128.30.20:4000/4000:smpp3:VMA (online 138644s, rcvd 313, sent 69, failed 0, queued 0 msgs) END And here's the status just after the kannel's reboot, you can see how much MTs were sent BEGIN Kannel bearerbox version `cvs-20060301'. Build `May 26 2006 03:43:23', compiler `3.3.5 (Debian 1:3.3.5-13 )'. System Linux, release 2.4.27-2-686, version #1 Wed Aug 17 10:34:09 UTC 2005, machine i686. Hostname tux1.trit.com, IP 172.17.35.130. Libxml version 2.6.16. Using OpenSSL 0.9.7e 25 Oct 2004. Using native malloc. Status: running, uptime 0d 0h 0m 41s WDP: received 0 (0 queued), sent 0 (0 queued) SMS: received 567 (0 queued), sent 567 (0 queued), store size 0 SMS: inbound 13.83 msg/sec, outbound 13.83 msg/sec DLR: 19071 queued, using pgsql storage Box connections: smsbox:(none), IP 127.0.0.1 (0 queued), (on-line 0d 0h 0m 40s) SMSC connections: SMPP-01-TXSMPP: 172.128.30.18:4000/4000:smpp1:VMA (online 41s, rcvd 0, sent 0, failed 0, queued 0 msgs) SMPP-01-TYSMPP: 172.128.30.23:4000/4000:smpp2:VMA (online 41s, rcvd 3, sent 3, failed 0, queued 0 msgs) SMPP-02-TZSMPP: 172.128.30.20:4000/4000:smpp3:VMA (online 41s, rcvd 564, sent 564, failed 0, queued 0 msgs) END Anyone can help please ?
Re: problem with special chars as @ and °
anyone can help please ?On 10/6/06, Fourat Zouari [EMAIL PROTECTED] wrote: HelloTrying to send a message like this :test of degree: ° and test of [at]: @i receive this :test of degree: o and test of [at]: any idea ?thanks
Re: Re: ringtone : a simple tutorial
Alejandro, can you share your code snippet ?thanksOn 9/20/06, Alejandro Guerrieri [EMAIL PROTECTED] wrote:You have 2 options:1. Use Kannel's PPG to compile the wap-push. Kannel does all the magic, though many people seems to have problems getting it to workright (me included).2. Compile the binary message yourself and send like any other SMS.Being a binary SMS, you'll have to set the UDH field. There are many code snippets to do this on many languages, (I've personallycontributed one of them for php).For both cases, check the list archives, this issue was asked andanswered a zillion times on this list, so you should be able to find all needed parts easily if you dig a little.Hope it helps,On 9/19/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: please answer me the following question: I want to set up a ringtone service using kannel and for that i want to use wap push SI. The sequence of the service will be as follow: 1.users will send a request via sms specifying a keyword for ringtone. 2.In response of that keyword kannel will send a wap push. To do so what will be my kannel.conf configuration. where will i specify the keyword for ringtone in kannnel.conf for incoming message that will eventually pass the request for wap push SI. Thanks Mamun -- This message was sent on behalf of [EMAIL PROTECTED] at openSubscriber.com http://www.opensubscriber.com/message/users@kannel.org/4111775.html --Alejandro GuerrieriMagicomhttp://www.magicom-bcn.net/LinkedIn: http://www.linkedin.com/in/aguerrieri
Re: Kannel is sometime freezing and wont let MTs messages go
the throttling path.. is it available in the last cvs snapshot or should i patch it ?On 8/14/06, Stuart Beck [EMAIL PROTECTED] wrote:Hi,You should configure throttling for the smpp adapter, we had the same issue and it was only by stopping kannel from being able to send toomany messages at once were we able to get rid of it. I would alsosuggest checking out the smpp throttling patch that was sent to the devlists recently as the default throttling code does not work properly. Stuart.Fourat Zouari wrote: Hello, Thanks for your help SMSC is limiting the traffic to 2sms/s, i dont have a big trafic, doing some 1000 to 3000 per day. But if so, should i apply a throttling on my smpp connectors ? On 8/10/06, *Aarno Syvänen* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi, The queue is simply too long. You must try to find the bottleneck of your system . (SMSC just not accept too many messages, i would quess. If it is so, you should throttle the traffic) Aarno On 26 Jul 2006, at 15:05, Fourat Zouari wrote: heello ;) On 7/24/06, *Fourat Zouari* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Am unable to reproduce this phenomen, but it happens sometimes and i just need to reboot kannel service to get the queued MTs go out and sent properly. here's the kannel status when it's blocking/queuing MTs : BEGIN Kannel bearerbox version `cvs-20060301'. Build `May 26 2006 03:43:23', compiler `3.3.5 (Debian 1: 3.3.5-13)'. System Linux, release 2.4.27-2-686,version #1 Wed Aug 17 10:34:09 UTC 2005, machine i686. Hostname tux1.trit.com http://tux1.trit.com, IP 172.17.35.130 http://172.17.35.130. Libxml version 2.6.16. Using OpenSSL 0.9.7e25 Oct 2004. Using native malloc.Status: running, uptime 12d 16h 53m 25s WDP: received 0 (0 queued), sent 0 (0 queued)SMS: received 657 (0 queued), sent 161 (566 queued), store size 566SMS: inbound 0.00 msg/sec, outbound 0.00 msg/secDLR: 18502 queued, using pgsql storageBox connections:smsbox:(none), IP 127.0.0.1 http://127.0.0.1 (0 queued), (on-line 12d 16h 52m 25s)SMSC connections:SMPP-01-TXSMPP: 172.128.30.18:4000/4000:smpp1:VMA http://172.128.30.18:4000/4000:smpp1:VMA (online 44793s, rcvd 257, sent 55, failed 0, queued 0 msgs)SMPP-01-TYSMPP: 172.128.30.23:4000/4000:smpp2:VMA http://172.128.30.23:4000/4000:smpp2:VMA (online 138661s, rcvd 87, sent 37, failed 0, queued 0 msgs)SMPP-02-TZSMPP: 172.128.30.20:4000/4000:smpp3:VMA http://172.128.30.20:4000/4000:smpp3:VMA (online 138644s, rcvd 313, sent 69, failed 0, queued 0 msgs) END And here's the status just after the kannel's reboot, you can see how much MTs were sent BEGINKannel bearerbox version `cvs-20060301'. Build `May 26 2006 03:43:23', compiler `3.3.5 (Debian 1:3.3.5-13 )'. System Linux, release 2.4.27-2-686,version #1 Wed Aug 17 10:34:09 UTC 2005, machine i686. Hostname tux1.trit.com http://tux1.trit.com , IP 172.17.35.130 http://172.17.35.130. Libxml version 2.6.16. Using OpenSSL 0.9.7e25 Oct 2004. Using native malloc. Status: running, uptime 0d 0h 0m 41sWDP: received 0 (0 queued), sent 0 (0 queued)SMS: received 567 (0 queued), sent 567 (0 queued), store size 0 SMS: inbound 13.83 msg/sec, outbound 13.83 msg/secDLR: 19071 queued, using pgsql storageBox connections:smsbox:(none), IP 127.0.0.1 http://127.0.0.1 (0 queued), (on-line 0d 0h 0m 40s)SMSC connections:SMPP-01-TXSMPP: 172.128.30.18:4000/4000:smpp1:VMA http://172.128.30.18:4000/4000:smpp1:VMA (online 41s, rcvd 0, sent 0, failed 0, queued 0 msgs)SMPP-01-TYSMPP: 172.128.30.23:4000/4000:smpp2:VMA http://172.128.30.23:4000/4000:smpp2:VMA (online 41s, rcvd 3, sent 3, failed 0, queued 0 msgs)SMPP-02-TZSMPP: 172.128.30.20:4000/4000:smpp3:VMA http://172.128.30.20:4000/4000:smpp3:VMA (online 41s, rcvd 564, sent 564, failed 0, queued 0 msgs) END Anyone can help please ? --Stuart BeckSystems Administratorm.Net CorporationLevel 13, 99 Gawler PlaceAdelaide SA 5000, Australia
Re: Kannel is sometime freezing and wont let MTs messages go
Hello,Thanks for your helpSMSC is limiting the traffic to 2sms/s, i dont have a big trafic, doing some 1000 to 3000 per day.But if so, should i apply a throttling on my smpp connectors ? On 8/10/06, Aarno Syvänen [EMAIL PROTECTED] wrote: Hi,The queue is simply too long. You must try to find the bottleneck of your system .(SMSC just not accept too many messages, i would quess. If it is so, you should throttle the traffic)AarnoOn 26 Jul 2006, at 15:05, Fourat Zouari wrote: heello ;)On 7/24/06, Fourat Zouari [EMAIL PROTECTED] wrote: Am unable to reproduce this phenomen, but it happens sometimes and i just need to reboot kannel service to get the queued MTs go out and sent properly. here's the kannel status when it's blocking/queuing MTs : BEGIN Kannel bearerbox version `cvs-20060301'. Build `May 26 2006 03:43:23', compiler `3.3.5 (Debian 1: 3.3.5-13)'. System Linux, release 2.4.27-2-686, version #1 Wed Aug 17 10:34:09 UTC 2005, machine i686. Hostname tux1.trit.com, IP 172.17.35.130. Libxml version 2.6.16. Using OpenSSL 0.9.7e 25 Oct 2004. Using native malloc. Status: running, uptime 12d 16h 53m 25s WDP: received 0 (0 queued), sent 0 (0 queued) SMS: received 657 (0 queued), sent 161 (566 queued), store size 566 SMS: inbound 0.00 msg/sec, outbound 0.00 msg/sec DLR: 18502 queued, using pgsql storage Box connections: smsbox:(none), IP 127.0.0.1 (0 queued), (on-line 12d 16h 52m 25s) SMSC connections: SMPP-01-TX SMPP: 172.128.30.18:4000/4000:smpp1:VMA (online 44793s, rcvd 257, sent 55, failed 0, queued 0 msgs) SMPP-01-TY SMPP: 172.128.30.23:4000/4000:smpp2:VMA (online 138661s, rcvd 87, sent 37, failed 0, queued 0 msgs) SMPP-02-TZ SMPP: 172.128.30.20:4000/4000:smpp3:VMA (online 138644s, rcvd 313, sent 69, failed 0, queued 0 msgs) END And here's the status just after the kannel's reboot, you can see how much MTs were sent BEGIN Kannel bearerbox version `cvs-20060301'. Build `May 26 2006 03:43:23', compiler `3.3.5 (Debian 1:3.3.5-13 )'. System Linux, release 2.4.27-2-686, version #1 Wed Aug 17 10:34:09 UTC 2005, machine i686. Hostname tux1.trit.com, IP 172.17.35.130. Libxml version 2.6.16. Using OpenSSL 0.9.7e 25 Oct 2004. Using native malloc. Status: running, uptime 0d 0h 0m 41s WDP: received 0 (0 queued), sent 0 (0 queued) SMS: received 567 (0 queued), sent 567 (0 queued), store size 0 SMS: inbound 13.83 msg/sec, outbound 13.83 msg/sec DLR: 19071 queued, using pgsql storage Box connections: smsbox:(none), IP 127.0.0.1 (0 queued), (on-line 0d 0h 0m 40s) SMSC connections: SMPP-01-TX SMPP: 172.128.30.18:4000/4000:smpp1:VMA (online 41s, rcvd 0, sent 0, failed 0, queued 0 msgs) SMPP-01-TY SMPP: 172.128.30.23:4000/4000:smpp2:VMA (online 41s, rcvd 3, sent 3, failed 0, queued 0 msgs) SMPP-02-TZ SMPP: 172.128.30.20:4000/4000:smpp3:VMA (online 41s, rcvd 564, sent 564, failed 0, queued 0 msgs) END Anyone can help please ?
Re: SQLBOX : the purpose of service and sms_type columns
hello !On 8/4/06, Fourat Zouari [EMAIL PROTECTED] wrote: Hi, What is the purpose of service and sms_type columns in SQLBOX's tables? Regards, Fourat
SQLBOX : the purpose of service and sms_type columns
Hi, What is the purpose of service and sms_type columns in SQLBOX's tables? Regards, Fourat
Re: Kannel is sometime freezing and wont let MTs messages go
heello ;)On 7/24/06, Fourat Zouari [EMAIL PROTECTED] wrote: Am unable to reproduce this phenomen, but it happens sometimes and i just need to reboot kannel service to get the queued MTs go out and sent properly.here's the kannel status when it's blocking/queuing MTs : BEGIN Kannel bearerbox version `cvs-20060301'. Build `May 26 2006 03:43:23', compiler `3.3.5 (Debian 1:3.3.5-13)'. System Linux, release 2.4.27-2-686, version #1 Wed Aug 17 10:34:09 UTC 2005, machine i686. Hostname tux1.trit.com, IP 172.17.35.130. Libxml version 2.6.16. Using OpenSSL 0.9.7e 25 Oct 2004. Using native malloc. Status: running, uptime 12d 16h 53m 25s WDP: received 0 (0 queued), sent 0 (0 queued) SMS: received 657 (0 queued), sent 161 (566 queued), store size 566 SMS: inbound 0.00 msg/sec, outbound 0.00 msg/sec DLR: 18502 queued, using pgsql storage Box connections: smsbox:(none), IP 127.0.0.1 (0 queued), (on-line 12d 16h 52m 25s) SMSC connections: SMPP-01-TX SMPP: 172.128.30.18:4000/4000:smpp1:VMA (online 44793s, rcvd 257, sent 55, failed 0, queued 0 msgs) SMPP-01-TY SMPP: 172.128.30.23:4000/4000:smpp2:VMA (online 138661s, rcvd 87, sent 37, failed 0, queued 0 msgs) SMPP-02-TZ SMPP:172.128.30.20:4000/4000:smpp3:VMA (online 138644s, rcvd 313, sent 69, failed 0, queued 0 msgs) END And here's the status just after the kannel's reboot, you can see how much MTs were sent BEGIN Kannel bearerbox version `cvs-20060301'. Build `May 26 2006 03:43:23', compiler `3.3.5 (Debian 1:3.3.5-13)'. System Linux, release 2.4.27-2-686, version #1 Wed Aug 17 10:34:09 UTC 2005, machine i686. Hostname tux1.trit.com, IP 172.17.35.130. Libxml version 2.6.16. Using OpenSSL 0.9.7e 25 Oct 2004. Using native malloc. Status: running, uptime 0d 0h 0m 41s WDP: received 0 (0 queued), sent 0 (0 queued) SMS: received 567 (0 queued), sent 567 (0 queued), store size 0 SMS: inbound 13.83 msg/sec, outbound 13.83 msg/sec DLR: 19071 queued, using pgsql storage Box connections: smsbox:(none), IP 127.0.0.1 (0 queued), (on-line 0d 0h 0m 40s) SMSC connections: SMPP-01-TX SMPP: 172.128.30.18:4000/4000:smpp1:VMA (online 41s, rcvd 0, sent 0, failed 0, queued 0 msgs) SMPP-01-TY SMPP: 172.128.30.23:4000/4000:smpp2:VMA (online 41s, rcvd 3, sent 3, failed 0, queued 0 msgs) SMPP-02-TZ SMPP:172.128.30.20:4000/4000:smpp3:VMA (online 41s, rcvd 564, sent 564, failed 0, queued 0 msgs) END Anyone can help please ?
Kannel is sometime freezing and wont let MTs messages go
Am unable to reproduce this phenomen, but it happens sometimes and i just need to reboot kannel service to get the queued MTs go out and sent properly.here's the kannel status when it's blocking/queuing MTs : BEGIN Kannel bearerbox version `cvs-20060301'. Build `May 26 2006 03:43:23', compiler `3.3.5 (Debian 1:3.3.5-13)'. System Linux, release 2.4.27-2-686, version #1 Wed Aug 17 10:34:09 UTC 2005, machine i686. Hostname tux1.trit.com, IP 172.17.35.130. Libxml version 2.6.16. Using OpenSSL 0.9.7e 25 Oct 2004. Using native malloc. Status: running, uptime 12d 16h 53m 25s WDP: received 0 (0 queued), sent 0 (0 queued) SMS: received 657 (0 queued), sent 161 (566 queued), store size 566 SMS: inbound 0.00 msg/sec, outbound 0.00 msg/sec DLR: 18502 queued, using pgsql storage Box connections: smsbox:(none), IP 127.0.0.1 (0 queued), (on-line 12d 16h 52m 25s) SMSC connections: SMPP-01-TX SMPP: 172.128.30.18:4000/4000:smpp1:VMA (online 44793s, rcvd 257, sent 55, failed 0, queued 0 msgs) SMPP-01-TY SMPP:172.128.30.23:4000/4000:smpp2:VMA (online 138661s, rcvd 87, sent 37, failed 0, queued 0 msgs) SMPP-02-TZ SMPP:172.128.30.20:4000/4000:smpp3:VMA (online 138644s, rcvd 313, sent 69, failed 0, queued 0 msgs) END And here's the status just after the kannel's reboot, you can see how much MTs were sent BEGIN Kannel bearerbox version `cvs-20060301'. Build `May 26 2006 03:43:23', compiler `3.3.5 (Debian 1:3.3.5-13)'. System Linux, release 2.4.27-2-686, version #1 Wed Aug 17 10:34:09 UTC 2005, machine i686. Hostname tux1.trit.com, IP 172.17.35.130. Libxml version 2.6.16. Using OpenSSL 0.9.7e 25 Oct 2004. Using native malloc. Status: running, uptime 0d 0h 0m 41s WDP: received 0 (0 queued), sent 0 (0 queued) SMS: received 567 (0 queued), sent 567 (0 queued), store size 0 SMS: inbound 13.83 msg/sec, outbound 13.83 msg/sec DLR: 19071 queued, using pgsql storage Box connections: smsbox:(none), IP 127.0.0.1 (0 queued), (on-line 0d 0h 0m 40s) SMSC connections: SMPP-01-TX SMPP:172.128.30.18:4000/4000:smpp1:VMA (online 41s, rcvd 0, sent 0, failed 0, queued 0 msgs) SMPP-01-TY SMPP:172.128.30.23:4000/4000:smpp2:VMA (online 41s, rcvd 3, sent 3, failed 0, queued 0 msgs) SMPP-02-TZ SMPP:172.128.30.20:4000/4000:smpp3:VMA (online 41s, rcvd 564, sent 564, failed 0, queued 0 msgs) END Anyone can help please ?
Kannel's site is down ?
Is kannel site down ? i get no access, no ping, no cvs access to kannel server.Do you have the same case ?
Re: SQLBOX question
It's ok, i got the sqlbox workingBut still have one problem :I have PGSQL going on the server, created a user owning a database and configured my db group to fit that, the db connexion is ok, but sqlbox throw an error in sqlbox.log :-2006-07-14 16:19:16 [7744] [0] INFO: Added logfile `/var/log/smgs/sqlbox.log' with level `0'.2006-07-14 16:19:16 [7744] [0] ERROR: PGSQL: connection to database 'smgstest' failed! 2006-07-14 16:19:16 [7744] [0] PANIC: PGSQL: could not connect to server: Connection refused Is the server running on host localhost and accepting TCP/IP connections on port 1735355439? 2006-07-14 16:19:16 [7744] [0] PANIC: /usr/local/sbin/sqlbox(gw_panic+0xe1) [0x806c030]2006-07-14 16:19:16 [7744] [0] PANIC: /usr/local/sbin/sqlbox [0x8060731]2006-07-14 16:19:16 [7744] [0] PANIC: /usr/local/sbin/sqlbox(dbpool_increase+0xe1) [0x8060cf0] 2006-07-14 16:19:16 [7744] [0] PANIC: /usr/local/sbin/sqlbox(dbpool_create+0x79) [0x8060dba]2006-07-14 16:19:16 [7744] [0] PANIC: /usr/local/sbin/sqlbox(sqlbox_init_pgsql+0x2f4) [0x80538b5]2006-07-14 16:19:16 [7744] [0] PANIC: /usr/local/sbin/sqlbox(main+0x379) [0x805087f] 2006-07-14 16:19:16 [7744] [0] PANIC: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xd2) [0xb7b39ea2]2006-07-14 16:19:16 [7744] [0] PANIC: /usr/local/sbin/sqlbox [0x804f911]- Verifying with netstat, postgresql is listening, and i can log into db and create any table i want.here's my conf :--SQLBOX-- group = sqlbox# id corresponds to id in group = mysql-connection.# this is analogous to id in group = dlr-dbid = dlr-01-db# smsbox-id indicates the box where SQL-injected messages appear to be coming from smsbox-id = smsbox-01# bearerbox host to connect tobearerbox-host = 127.0.0.1# smsbox port to be listening onsmsbox-port = 13002smsbox-port-ssl = false # sql-log-table is the table used to log all sent messagessql-log-table = sent_sms# sql-insert-table is the table that is monitored for new messages to sendsql-insert-table = send_sms# global sender: If no sender is specified in sql-insert-table then this # value is used.global-sender = 06121log-file = /var/log/smgs/sqlbox.loglog-level = 0# ssl-client-certkey-file = # ssl-server-cert-file = # ssl-server-key-file = # ssl-trusted-ca-file = --SQLBOX-- --SMSBOX--smsbox.conf smsc.conf smsc-fake.conf[EMAIL PROTECTED]:/etc/smgs# cat smsbox.confgroup = smsboxbearerbox-host = localhost log-file = /var/log/kannel/smsbox.loglog-level = 0mo-recode = truehttp-request-retry = 10http-queue-delay = 60smsbox-id = smsbox-01sendsms-port = 13002bearerbox-is-sqlbox=true --SMSBOXBEARERBOX-- group = coreadmin-port = 13000admin-password = fxxbarstatus-password = sTtxadmin-deny-ip = *.*.*.*admin-allow-ip = 127.0.0.1box-deny-ip = *.*.*.* box-allow-ip = 127.0.0.1wdp-interface-name = *log-file = /var/log/kannel/bearerbox.loglog-level = 0access-log = /var/log/kannel/access.log smsbox-port = 13001store-file = /var/log/kannel/storedlr-storage = pgsql--BEARERBOX-- --SMSC-- group = smscsmsc = fakesmsc-id = SMPP-01-FAKEport = 1connect-allow-ip = 127.0.0.1--SMSC-- --PGSQLCONNEXION-- group = pgsql-connectionid = dlr-01-dbhost = localhostusername = testpassword = testdatabase = testmax-connections = 6--PGSQLCONNEXION-- --DLR-DB-- group = dlr-dbid = dlr-01-dbtable = dlrfield-smsc = smscfield-timestamp = datefield-destination = dafield-source = soafield-service = servicefield-url = "">field-mask = maskfield-status = status field-boxc-id = boxcid--DLR-DB-- On 7/1/06, Mi Reflejo [EMAIL PROTECTED] wrote: Maybe this snapshot isn't CVS HEAD version. Follow these steps:# cvs -d:pserver:[EMAIL PROTECTED]:/home/cvs co gateway# cvs -d:pserver:[EMAIL PROTECTED]:/home/cvs co sqlbox# cd sqlbox# make patch # cd ../gateway# ./configure [PARAMS]# make# make installMartinOn 6/30/06, Fourat Zouari [EMAIL PROTECTED] wrote: Thanks for your help, I got it, but not working ... I downloaded the latest snapshot of kannel untared the kannel-snapshot, renamed the folder to gateway/ downloaded sqlbox from cvs, moved i
Re: Error receiving DLRs
dlrs are saved into db, but as you said, am not receiving the idsOn 6/20/06, Julien Buratto [EMAIL PROTECTED] wrote:
However it seems you don't receive the ID of the message from the smppserver ?
JFourat Zouari ha scritto: Hello all, Am having errors in my logs saying that i have problems receiving DLRs, let's let this bearerbox log talk about it : -- BEGIN PASTING
2006-06-20 16:57:08 [801] [6] DEBUG: DLR[pgsql]: Adding DLR smsc=SMPP-01-BB, ts=5B03, src="" dst=28347018, mask=31, boxc= 2006-06-20 16:57:08 [801] [6] DEBUG: sql: INSERT INTO dlr (smsc, date,
soa, da, service, url, mask, boxcid, status) VALUES ('SMPP-01-BB', '5B03', '17700', '28347018', 'tt', '
http://localhost/servlets/recdlr.php?status=%danswer=%Ats=%tmsgid=165574 http://localhost/servlets/recdlr.php?status=%danswer=%Ats=%tmsgid=165574
', '31', '', '0'); 2006-06-20 16:57:08 [801] [6] DEBUG: SMSC[SMPP-01-BB]: creating DLR message 2006-06-20 16:57:08 [801] [6] DEBUG: SMSC[SMPP-01-BB]: DLR =
http://localhost/servlets/recdlr.php?status=%danswer=%Ats=%tmsgid=165574 http://localhost/servlets/recdlr.php?status=%danswer=%Ats=%tmsgid=165574
2006-06-20 16:57:08 [837] [20] DEBUG: send_msg: sending msg to box: 127.0.0.1 http://127.0.0.1 2006-06-20 16:57:08 [837] [20] DEBUG: boxc_sender: sent message to
127.0.0.1 http://127.0.0.1 2006-06-20 16:57:08 [836] [19] DEBUG: boxc_receiver: got ack 2006-06-20 16:57:09 [797] [2] DEBUG: HTTP: Creating HTTPClient for
`127.0.0.1'. 2006-06-20 16:57:09 [797] [2] DEBUG: HTTP: Created HTTPClient area 0x8258b28. 2006-06-20 16:57:09 [798] [3] DEBUG: sql: SELECT count(*) FROM dlr; 2006-06-20 16:57:09 [798] [3] DEBUG: HTTP: Destroying HTTPClient area
0x8258b28. 2006-06-20 16:57:09 [798] [3] DEBUG: HTTP: Destroying HTTPClient for `127.0.0.1'. 2006-06-20 16:57:09 [797] [2] DEBUG: HTTP: Creating HTTPClient for `127.0.0.1'. 2006-06-20 16:57:09 [797] [2] DEBUG: HTTP: Created HTTPClient area
0x8258b28. 2006-06-20 16:57:09 [798] [3] DEBUG: sql: SELECT count(*) FROM dlr; 2006-06-20 16:57:09 [798] [3] DEBUG: HTTP: Destroying HTTPClient area 0x8258b28. 2006-06-20 16:57:09 [798] [3] DEBUG: HTTP: Destroying HTTPClient for
`127.0.0.1'. 2006-06-20 16:57:15 [803] [8] DEBUG: SMPP[SMPP-01-TZ]: Sending enquire link: 2006-06-20 16:57:15 [803] [8] DEBUG: SMPP PDU 0x8258d48 dump: 2006-06-20 16:57:15 [803] [8] DEBUG: type_name: enquire_link
2006-06-20 16:57:15 [803] [8] DEBUG: command_id: 21 = 0x0015 2006-06-20 16:57:15 [803] [8] DEBUG: command_status: 0 = 0x 2006-06-20 16:57:15 [803] [8] DEBUG: sequence_number: 23806 = 0x5cfe
2006-06-20 16:57:15 [803] [8] DEBUG: SMPP PDU dump ends. 2006-06-20 16:57:15 [803] [8] DEBUG: SMPP[SMPP-01-TZ]: Got PDU: 2006-06-20 16:57:15 [803] [8] DEBUG: SMPP PDU 0x8258d48 dump: 2006-06-20 16:57:15 [803] [8] DEBUG: type_name: enquire_link_resp
2006-06-20 16:57:15 [803] [8] DEBUG: command_id: 2147483669 = 0x8015 2006-06-20 16:57:15 [803] [8] DEBUG: command_status: 0 = 0x 2006-06-20 16:57:15 [803] [8] DEBUG: sequence_number: 23806 = 0x5cfe
2006-06-20 16:57:15 [803] [8] DEBUG: SMPP PDU dump ends. 2006-06-20 16:57:16 [802] [7] DEBUG: SMPP[SMPP-01-BB]: Got PDU: 2006-06-20 16:57:16 [802] [7] DEBUG: SMPP PDU 0x8258d48 dump: 2006-06-20 16:57:16 [802] [7] DEBUG: type_name: deliver_sm
2006-06-20 16:57:16 [802] [7] DEBUG: command_id: 5 = 0x0005 2006-06-20 16:57:16 [802] [7] DEBUG: command_status: 0 = 0x 2006-06-20 16:57:16 [802] [7] DEBUG: sequence_number: 180 = 0x00b4
2006-06-20 16:57:16 [802] [7] DEBUG: service_type: NULL 2006-06-20 16:57:16 [802] [7] DEBUG: source_addr_ton: 2 = 0x0002 2006-06-20 16:57:16 [802] [7] DEBUG: source_addr_npi: 1 = 0x0001
2006-06-20 16:57:16 [802] [7] DEBUG: source_addr: 28347018 2006-06-20 16:57:16 [802] [7] DEBUG: dest_addr_ton: 2 = 0x0002 2006-06-20 16:57:16 [802] [7] DEBUG: dest_addr_npi: 1 = 0x0001
2006-06-20 16:57:16 [802] [7] DEBUG: destination_addr: 17700 2006-06-20 16:57:16 [802] [7] DEBUG: esm_class: 4 = 0x0004 2006-06-20 16:57:16 [802] [7] DEBUG: protocol_id: 0 = 0x
2006-06-20 16:57:16 [802] [7] DEBUG: priority_flag: 0 = 0x 2006-06-20 16:57:16 [802] [7] DEBUG: schedule_delivery_time: NULL 2006-06-20 16:57:16 [802] [7] DEBUG: validity_period: NULL
2006-06-20 16:57:16 [802] [7] DEBUG: registered_delivery: 0 = 0x 2006-06-20 16:57:16 [802] [7] DEBUG: replace_if_present_flag: 0 = 0x 2006-06-20 16:57:16 [802] [7] DEBUG: data_coding: 0 = 0x
2006-06-20 16:57:16 [802] [7] DEBUG: sm_default_msg_id: 0 = 0x 2006-06-20 16:57:16 [802] [7] DEBUG: sm_length: 12 = 0x000c 2006-06-20 16:57:16 [802] [7] DEBUG: short_message: 5B03 201
2006-06-20 16:57:16 [802] [7] DEBUG: SMPP PDU dump ends. 2006-06-20 16:57:16 [802] [7] DEBUG: SMPP[SMPP-01-BB] handle_pdu, got DLR 2006-06-20 16:57:16 [802] [7] DEBUG: SMPP[SMPP-01-BB]: Couldnot parse
DLR string sscanf way,fallback to old way. Please report! 2006-06-20 16:57:16 [802] [7]
Error receiving DLRs
Hello all,Am having errors in my logs saying that i have problems receiving DLRs, let's let this bearerbox log talk about it :-- BEGIN PASTING2006-06-20 16:57:08 [801] [6] DEBUG: DLR[pgsql]: Adding DLR smsc=SMPP-01-BB, ts=5B03, src="" dst=28347018, mask=31, boxc=
2006-06-20 16:57:08 [801] [6] DEBUG: sql: INSERT INTO dlr (smsc, date, soa, da, service, url, mask, boxcid, status) VALUES ('SMPP-01-BB', '5B03', '17700', '28347018', 'tt', '
http://localhost/servlets/recdlr.php?status=%danswer=%Ats=%tmsgid=165574', '31', '', '0');2006-06-20 16:57:08 [801] [6] DEBUG: SMSC[SMPP-01-BB]: creating DLR message2006-06-20 16:57:08 [801] [6] DEBUG: SMSC[SMPP-01-BB]: DLR =
http://localhost/servlets/recdlr.php?status=%danswer=%Ats=%tmsgid=1655742006-06-20 16:57:08 [837] [20] DEBUG: send_msg: sending msg to box:
127.0.0.12006-06-20 16:57:08 [837] [20] DEBUG: boxc_sender: sent message to 127.0.0.12006-06-20 16:57:08 [836] [19] DEBUG: boxc_receiver: got ack
2006-06-20 16:57:09 [797] [2] DEBUG: HTTP: Creating HTTPClient for `127.0.0.1'.2006-06-20 16:57:09 [797] [2] DEBUG: HTTP: Created HTTPClient area 0x8258b28.2006-06-20 16:57:09 [798] [3] DEBUG: sql: SELECT count(*) FROM dlr;
2006-06-20 16:57:09 [798] [3] DEBUG: HTTP: Destroying HTTPClient area 0x8258b28.2006-06-20 16:57:09 [798] [3] DEBUG: HTTP: Destroying HTTPClient for `127.0.0.1'.2006-06-20 16:57:09 [797] [2] DEBUG: HTTP: Creating HTTPClient for `127.0.0.1'.
2006-06-20 16:57:09 [797] [2] DEBUG: HTTP: Created HTTPClient area 0x8258b28.2006-06-20 16:57:09 [798] [3] DEBUG: sql: SELECT count(*) FROM dlr;2006-06-20 16:57:09 [798] [3] DEBUG: HTTP: Destroying HTTPClient area 0x8258b28.
2006-06-20 16:57:09 [798] [3] DEBUG: HTTP: Destroying HTTPClient for `127.0.0.1'.2006-06-20 16:57:15 [803] [8] DEBUG: SMPP[SMPP-01-TZ]: Sending enquire link:2006-06-20 16:57:15 [803] [8] DEBUG: SMPP PDU 0x8258d48 dump:
2006-06-20 16:57:15 [803] [8] DEBUG: type_name: enquire_link2006-06-20 16:57:15 [803] [8] DEBUG: command_id: 21 = 0x00152006-06-20 16:57:15 [803] [8] DEBUG: command_status: 0 = 0x2006-06-20 16:57:15 [803] [8] DEBUG: sequence_number: 23806 = 0x5cfe
2006-06-20 16:57:15 [803] [8] DEBUG: SMPP PDU dump ends.2006-06-20 16:57:15 [803] [8] DEBUG: SMPP[SMPP-01-TZ]: Got PDU:2006-06-20 16:57:15 [803] [8] DEBUG: SMPP PDU 0x8258d48 dump:2006-06-20 16:57:15 [803] [8] DEBUG: type_name: enquire_link_resp
2006-06-20 16:57:15 [803] [8] DEBUG: command_id: 2147483669 = 0x80152006-06-20 16:57:15 [803] [8] DEBUG: command_status: 0 = 0x2006-06-20 16:57:15 [803] [8] DEBUG: sequence_number: 23806 = 0x5cfe
2006-06-20 16:57:15 [803] [8] DEBUG: SMPP PDU dump ends.2006-06-20 16:57:16 [802] [7] DEBUG: SMPP[SMPP-01-BB]: Got PDU:2006-06-20 16:57:16 [802] [7] DEBUG: SMPP PDU 0x8258d48 dump:2006-06-20 16:57:16 [802] [7] DEBUG: type_name: deliver_sm
2006-06-20 16:57:16 [802] [7] DEBUG: command_id: 5 = 0x00052006-06-20 16:57:16 [802] [7] DEBUG: command_status: 0 = 0x2006-06-20 16:57:16 [802] [7] DEBUG: sequence_number: 180 = 0x00b4
2006-06-20 16:57:16 [802] [7] DEBUG: service_type: NULL2006-06-20 16:57:16 [802] [7] DEBUG: source_addr_ton: 2 = 0x00022006-06-20 16:57:16 [802] [7] DEBUG: source_addr_npi: 1 = 0x00012006-06-20 16:57:16 [802] [7] DEBUG: source_addr: 28347018
2006-06-20 16:57:16 [802] [7] DEBUG: dest_addr_ton: 2 = 0x00022006-06-20 16:57:16 [802] [7] DEBUG: dest_addr_npi: 1 = 0x00012006-06-20 16:57:16 [802] [7] DEBUG: destination_addr: 17700
2006-06-20 16:57:16 [802] [7] DEBUG: esm_class: 4 = 0x00042006-06-20 16:57:16 [802] [7] DEBUG: protocol_id: 0 = 0x2006-06-20 16:57:16 [802] [7] DEBUG: priority_flag: 0 = 0x2006-06-20 16:57:16 [802] [7] DEBUG: schedule_delivery_time: NULL
2006-06-20 16:57:16 [802] [7] DEBUG: validity_period: NULL2006-06-20 16:57:16 [802] [7] DEBUG: registered_delivery: 0 = 0x2006-06-20 16:57:16 [802] [7] DEBUG: replace_if_present_flag: 0 = 0x
2006-06-20 16:57:16 [802] [7] DEBUG: data_coding: 0 = 0x2006-06-20 16:57:16 [802] [7] DEBUG: sm_default_msg_id: 0 = 0x2006-06-20 16:57:16 [802] [7] DEBUG: sm_length: 12 = 0x000c2006-06-20 16:57:16 [802] [7] DEBUG: short_message: 5B03 201
2006-06-20 16:57:16 [802] [7] DEBUG: SMPP PDU dump ends.2006-06-20 16:57:16 [802] [7] DEBUG: SMPP[SMPP-01-BB] handle_pdu, got DLR2006-06-20 16:57:16 [802] [7] DEBUG: SMPP[SMPP-01-BB]: Couldnot parse DLR string sscanf way,fallback to old way. Please report!
2006-06-20 16:57:16 [802] [7] ERROR: SMPP[SMPP-01-BB]: got DLR but could not find message or was not interested in it id dst28347018, type22006-06-20 16:57:16 [802] [7] DEBUG: SMPP[SMPP-01-BB]: Sending PDU:
2006-06-20 16:57:16 [802] [7] DEBUG: SMPP PDU 0x8258e20 dump:2006-06-20 16:57:16 [802] [7] DEBUG: type_name: deliver_sm_resp2006-06-20 16:57:16 [802] [7] DEBUG: command_id: 2147483653 = 0x8005-- END PASTING
Re: ringtone : a simple tutorial
Excuse me, am not talking about polyphonic ringtones, these are MMS-like.I was talking about simple ringtone and logos, basic ones :)On 5/15/06, Mi Reflejo [EMAIL PROTECTED] wrote:Hey Fourat, The scheme for polyphonic ringtone is:Kannel ---WAP PUSH-- Phone ---Http Request -- kannel/Wap Gateway -- webserverWAP Push is a SMS within the header of which is included a link to a WAP address. On receiving a WAP Push, the compatible mobile handsetautomatically gives the user the option to access the WAP content onhis handset. The WAP Push directs the end-user to a WAP address wherecontent is stored ready for viewing or downloading onto the handset. This wap address may be a page or a WAP site.For wap pushes, kannel uses a Push Proxy Gateway. To know howconfigure it and send wap pushes i sugest you start off reading: http://www.kannel.org/download/kannel-userguide-snapshot/userguide.html#PPGRegardsOn 5/14/06, Fourat Zouari [EMAIL PROTECTED] wrote: Dear friends, Can anyone provide a simple tutorial on how to send a ringtone over http with kannel ? Thanks
Re: ringtone : a simple tutorial
ok thanks for helping,I've found the contrib files in contrib/webThe problem that it's working using a java applet that is not provided, here's the code :APPLET CODE=composer.RingRing.class WIDTH=300 HEIGHT=40 ARCHIVE=ringring/classes.zip MAYSCRIPT /APPLET Do you have any idea ?On 5/28/06, Alejandro Guerrieri [EMAIL PROTECTED] wrote: Fourat,There are many formats, text-only and binary:SmartMessaging (Nokia, Binary) SCKL (Nokia, Text-Only)EMS (Sony/Motorola/Alcatel/Siemens, Binary)iMELODY (Motorola and some others, Text-Only)Basically, you need to prepare the content encoding it in the properformat and use Kannel to deliver it. That means putting the encoded text as a regular message or, if it's a binary format, encoding theUDH header and binary payload (you'll have to pass the udh and textfields instead of only the text field).Check the kannel source tree, there are some PHP examples included. Hope it helps,On 5/28/06, Fourat Zouari [EMAIL PROTECTED] wrote: Excuse me, am not talking about polyphonic ringtones, these are MMS-like. I was talking about simple ringtone and logos, basic ones :) On 5/15/06, Mi Reflejo [EMAIL PROTECTED] wrote: Hey Fourat, The scheme for polyphonic ringtone is: Kannel ---WAP PUSH-- Phone ---Http Request -- kannel/Wap Gateway -- webserver WAP Push is a SMS within the header of which is included a link to a WAP address. On receiving a WAP Push, the compatible mobile handset automatically gives the user the option to access the WAP content on his handset. The WAP Push directs the end-user to a WAP address where content is stored ready for viewing or downloading onto the handset. This wap address may be a page or a WAP site. For wap pushes, kannel uses a Push Proxy Gateway. To know how configure it and send wap pushes i sugest you start off reading: http://www.kannel.org/download/kannel-userguide-snapshot/userguide.html#PPG Regards On 5/14/06, Fourat Zouari [EMAIL PROTECTED] wrote: Dear friends, Can anyone provide a simple tutorial on how to send a ringtone over http with kannel ? Thanks--Alejandro GuerrieriMagicom http://www.magicom-bcn.net/LinkedIn: http://www.linkedin.com/in/aguerrieri
Re: storing 8bits messages to database
it's already escaped using the qstr() member from addb classOn 5/26/06, Amar [EMAIL PROTECTED] wrote: I think if u insert the url encoded value or escaped string.. it will accept -- amar On 5/25/06, Fourat Zouari [EMAIL PROTECTED] wrote: Hello all,Am forwarding MO trafic to php script that save data to a postgresql database.It's working fine until the moment i have 8bit MOs, it seems that i cant save this data into database, at least without transformations, so i would like to get from you any ideas to do it. thanks here's a log snapshot for an MO received from Kannel with charset = 8-BIT:Date : 2006-02-23 19:18:54Ip : 127.0.0.1Level: E_WARNINGStr : pg_query() [a href=''function.pg-query/a]: Query failed: ERREUR: séquence d'octets UTF-8 invalide détectée près de l'octet 0xe4File : /var/classes/adodb/drivers/adodb- postgres7.inc.phpLine : 110Date : 2006-02-23 19:18:54Ip : 127.0.0.1Level: E_USER_ERRORStr : postgres7 error: [0: ] in EXECUTE(INSERT INTO hotq (directionType, timecreated, charset, udh, coding, bcontent, tcontent, soa, da, smscid, extra) VALUES( 'MO', '1148404734', '8-BIT', ' \\0ä\\0\\0\\0', '1', '101T00 END:VEVENTEND:VCALENDAR', '101T00 END:VEVENT END:VCALENDAR', '22175902', '87090', '2', 'DATE=2006-05-23 17:18:53 - ACCOUNT= - SERVICENAME=default - SMSID=ffcb16f7-10a3-4504-bf2f-98cc930a106f - DELIVERYREPORT=-1' )) -- Amar
Re: sms_router
what' does this affect ?On 5/24/06, Alexander Malysh [EMAIL PROTECTED] wrote: Hi,see sms-resend-freq in user guide. Please note that this optionavailable only in CVS.Thanks,AlexHillel schrieb: Hi, What configuration option causes sms_router: time to sleep 30.00 secs and is this the default? 2006-05-24 09:37:22 [4854] [9] DEBUG: sms_router: time to sleep 30.00 secs. Is there anyway to decrease the sleep time? Thanks
Queuing, where's the storage ?
Hello,I would like to know where do kannel store queue lists for dlr ans mts.Thanks
storing 8bits messages to database
Hello all,Am forwarding MO trafic to php script that save data to a postgresql database.It's working fine until the moment i have 8bit MOs, it seems that i cant save this data into database, at least without transformations, so i would like to get from you any ideas to do it. thanks here's a log snapshot for an MO received from Kannel with charset = 8-BIT:Date : 2006-02-23 19:18:54Ip : 127.0.0.1 Level: E_WARNINGStr : pg_query() [a href=''function.pg-query/a]: Query failed: ERREUR: séquence d'octets UTF-8 invalide détectée près de l'octet 0xe4File : /var/classes/adodb/drivers/adodb- postgres7.inc.phpLine : 110Date : 2006-02-23 19:18:54Ip : 127.0.0.1Level: E_USER_ERRORStr : postgres7 error: [0: ] in EXECUTE(INSERT INTO hotq (directionType, timecreated, charset, udh, coding, bcontent, tcontent, soa, da, smscid, extra) VALUES( 'MO', '1148404734', '8-BIT', ' \\0ä\\0\\0\\0', '1', '101T00 END:VEVENTEND:VCALENDAR', '101T00 END:VEVENT END:VCALENDAR', '22175902', '87090', '2', 'DATE=2006-05-23 17:18:53 - ACCOUNT= - SERVICENAME=default - SMSID=ffcb16f7-10a3-4504-bf2f-98cc930a106f - DELIVERYREPORT=-1' ))
mmsbox ?
Hello friends,Am working with kannel as an sms gateway and it's very stable.Now it's time to work with MMS, i saw there were Mbuni project, but it's install seems to be bloody, does kannel plan to integrate an mmsbox or shoul we try to integrate other projects (Mbuni) to kannel ? Thanks
Re: sms_router sleeping when bulking
Hello Alejandro,How to use it ? is there a conceptual model for the database ? is there any tutorial talking about that ?thanksOn 5/17/06, Alejandro Guerrieri [EMAIL PROTECTED] wrote: Use sqlbox for bulk sms. It _flies_ comparing to opening an httpconnection for each message you sent. You just have to insert themessages to send in an sql table and the module makes the job for you,fast and reliably. Hope it helps,--Alejandro GuerrieriMagicomhttp://www.magicom-bcn.net/LinkedIn: http://www.linkedin.com/in/aguerrieri On 5/13/06, Fourat Zouari [EMAIL PROTECTED] wrote: Am doing bulk sms, attacking kannel '/cgi-bin/sendsms' url, and it's going very slowly, when debugging, i see this line in the bearerbox log repeating each 60 MT messages : 2006-05-13 16:38:58 [4556] [8] DEBUG: sms_router: time to sleep 30.00 secs. Am using SMS-C connexion. Anyone can help ? how to increase/decrease this sleep time value ?
ringtone : a simple tutorial
Dear friends,Can anyone provide a simple tutorial on how to send a ringtone over http with kannel ?Thanks
sms_router sleeping when bulking
Am doing bulk sms, attacking kannel '/cgi-bin/sendsms' url, and it's going very slowly, when debugging, i see this line in the bearerbox log repeating each 60 MT messages :2006-05-13 16:38:58 [4556] [8] DEBUG: sms_router: time to sleep 30.00 secs.Am using SMS-C connexion.Anyone can help ?how to increase/decrease this sleep time value ?
receiving strange encoded MOs
Hello, Am receiving arabic MO-SMS encoded strangely : 2006-05-07 17:29:29 Receive SMS [SMSC:SMPP-01-EE] [SVC:] [ACT:] [BINF:] [from:21968403585] [to:87090] [flags:-1:2:-1:0:-1][msg:12:062C062F063306280641062F] [udh:0:] 2006-05-07 17:30:24 Receive SMS [SMSC:SMPP-01-EE] [SVC:] [ACT:] [BINF:] [from:21968403585] [to:87090] [flags:-1:2:-1:0:-1][msg:8:0641062F064A062A] [udh:0:]
Re: receiving strange encoded MOs
should i utf8_decode() it ? (php) On 5/7/06, issam [EMAIL PROTECTED] wrote: Hello this 062C062F063306280641062F is a unicode to send or receive arabic text you must use unicode - Original Message - From: Fourat Zouari [EMAIL PROTECTED] To: users@kannel.org Sent: Sunday, May 07, 2006 5:36 PM Subject: receiving strange encoded MOs Hello, Am receiving arabic MO-SMS encoded strangely : 2006-05-07 17:29:29 Receive SMS [SMSC:SMPP-01-EE] [SVC:] [ACT:] [BINF:] [from:21968403585] [to:87090] [flags:-1:2:-1:0:-1][msg:12:062C062F063306280641062F] [udh:0:] 2006-05-07 17:30:24 Receive SMS [SMSC:SMPP-01-EE] [SVC:] [ACT:] [BINF:] [from:21968403585] [to:87090] [flags:-1:2:-1:0:-1][msg:8:0641062F064A062A] [udh:0:]
