idle-timout
I eagerly tried the smsc_emi2 'idle-timeout' configuration committed by Jörg Pommitz a month or so ago, but get the following error: 2002-01-03 16:37:13 [0] INFO: Added logfile `/home/sms/kannel/log/kannel.log' with level `0'. 2002-01-03 16:37:13 [0] INFO: 2002-01-03 16:37:13 [0] INFO: Kannel bearerbox II version cvs starting 2002-01-03 16:37:13 [0] INFO: Started access logfile `/home/sms/kannel/log/kannelaccess.log'. 2002-01-03 16:37:13 [0] DEBUG: HTTP: Opening server at port 15000. 2002-01-03 16:37:13 [0] DEBUG: Started thread 1 (gwlib/fdset.c:poller) 2002-01-03 16:37:13 [0] DEBUG: Started thread 2 (gwlib/http.c:server_thread) 2002-01-03 16:37:13 [0] DEBUG: Started thread 3 (gw/bb_http.c:httpadmin_run) 2002-01-03 16:37:13 [0] DEBUG: starting smsbox connection module 2002-01-03 16:37:13 [0] DEBUG: Started thread 4 (gw/bb_boxc.c:smsboxc_run) 2002-01-03 16:37:13 [0] DEBUG: Started thread 5 (gw/smsc_emi2.c:emi2_listener) 2002-01-03 16:37:13 [0] DEBUG: Started thread 6 (gw/smsc_emi2.c:emi2_sender) 2002-01-03 16:37:13 [0] DEBUG: Started thread 7 (gw/bb_smscconn.c:sms_router) 2002-01-03 16:37:13 [0] INFO: MAIN: Start-up done, entering mainloop 2002-01-03 16:37:13 [0] DEBUG: smsc_emi2: start called 2002-01-03 16:37:13 [7] DEBUG: sms_router: time to sleep 2002-01-03 16:37:13 [6] DEBUG: Sending operation type 60, message with password not shown in log file. 2002-01-03 16:37:13 [7] DEBUG: sms_router: list_len = 0 2002-01-03 16:37:13 [6] DEBUG: emi2 parsing packet: 00/00036/R/60/A/test:030102163951/C5 2002-01-03 16:37:43 [6] INFO: emi2: closing idle connection. 2002-01-03 16:38:13 [6] PANIC: gwlib/conn.c:107: lock_in: Assertion `conn != NULL' failed. In the above example 'idle-timeout' is set to 30 and I've commented out the keepalive setting (I've tried various combinations of 'idle-timeout' and 'keepalive' settings but with the same result). Am I doing something wrong? cheers, Frederik Ammitzbøll Unwire Vestergade 12A, 3. 1456 København K Denmark Mobil: +45 27 11 99 99 Fax : +45 33 33 09 70 Web: www.unwire.dk From the updated Userguide: idle-timeout - number (seconds) If this option is set to a value larger than 0, then the connection will be closed after the configured amount of seconds without activity. This option interacts with the keepalive configuration option. If keepalive is smaller than idle-timeout, then the connection will never be idle and those this option has no effect. If keepalive is larger than idle-timeout, than keepalive reopens the connection. This allows one to poll for pending mobile originated Short Messages at the SMSC. In my limited testing everything worked fine. If nobody objects I'm going to commit my changes soon. Regards Jörg
Re: idle-timout
I eagerly tried the smsc_emi2 'idle-timeout' configuration committed by Jörg Pommitz a month or so ago, but get the following error: 2002-01-03 16:37:13 [0] INFO: Added logfile `/home/sms/kannel/log/kannel.log' with level `0'. 2002-01-03 16:37:13 [0] INFO: 2002-01-03 16:37:13 [0] INFO: Kannel bearerbox II version cvs starting 2002-01-03 16:37:13 [0] INFO: Started access logfile `/home/sms/kannel/log/kannelaccess.log'. 2002-01-03 16:37:13 [0] DEBUG: HTTP: Opening server at port 15000. 2002-01-03 16:37:13 [0] DEBUG: Started thread 1 (gwlib/fdset.c:poller) 2002-01-03 16:37:13 [0] DEBUG: Started thread 2 (gwlib/http.c:server_thread) 2002-01-03 16:37:13 [0] DEBUG: Started thread 3 (gw/bb_http.c:httpadmin_run) 2002-01-03 16:37:13 [0] DEBUG: starting smsbox connection module 2002-01-03 16:37:13 [0] DEBUG: Started thread 4 (gw/bb_boxc.c:smsboxc_run) 2002-01-03 16:37:13 [0] DEBUG: Started thread 5 (gw/smsc_emi2.c:emi2_listener) 2002-01-03 16:37:13 [0] DEBUG: Started thread 6 (gw/smsc_emi2.c:emi2_sender) 2002-01-03 16:37:13 [0] DEBUG: Started thread 7 (gw/bb_smscconn.c:sms_router) 2002-01-03 16:37:13 [0] INFO: MAIN: Start-up done, entering mainloop 2002-01-03 16:37:13 [0] DEBUG: smsc_emi2: start called 2002-01-03 16:37:13 [7] DEBUG: sms_router: time to sleep 2002-01-03 16:37:13 [6] DEBUG: Sending operation type 60, message with password not shown in log file. 2002-01-03 16:37:13 [7] DEBUG: sms_router: list_len = 0 2002-01-03 16:37:13 [6] DEBUG: emi2 parsing packet: 00/00036/R/60/A/test:030102163951/C5 2002-01-03 16:37:43 [6] INFO: emi2: closing idle connection. 2002-01-03 16:38:13 [6] PANIC: gwlib/conn.c:107: lock_in: Assertion `conn != NULL' failed. In the above example 'idle-timeout' is set to 30 and I've commented out the keepalive setting (I've tried various combinations of 'idle-timeout' and 'keepalive' settings but with the same result). Am I doing something wrong? No. I actually just fixed this bug 10 minutes ago. I'm committing it to CVS at the moment. -- Andreas Fink Fink-Consulting -- Tel: +41-61-6932730 Fax: +41-61-6932729 Mobile: +41-79-2457333 Address: A. Fink, Schwarzwaldallee 16, 4058 Basel, Switzerland E-Mail: [EMAIL PROTECTED] Homepage: http://www.finkconsulting.com -- Something urgent? Try http://www.smsrelay.com/ Nickname afink
Re: Stripping Kannel
so you would agree to have a configure switch that strips down everything WAP related in bearerbox, right?! I also agree with that! here we only use kannel for SMS purposes (for now ;) ) and it will be great if we don't need to compile wap related features! cheers, Valter Santos - Original Message - From: Stipe Tolj [EMAIL PROTECTED] Cc: Kannel Developers [EMAIL PROTECTED] Sent: Friday, January 04, 2002 2:15 PM Subject: Re: Stripping Kannel Angel Fradejas wrote: I agree this is an interesting thing. We also use kannel as a SMS gateway only, and striping down everything wap related makes sense to us, too. so you would agree to have a configure switch that strips down everything WAP related in bearerbox, right?! Nick, who is currently in charge of updating the wishlist or the TODO file? I'll put a item on my Kannel's new web site features for this. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: DLR and SMPP..
The same thing happens when connecting through EMI2.., so something must be broken in the DLR implementation. On Wed, 2 Jan 2002, Stefan Cars wrote: The patched worked (it doesn't crash anymore) but the problem that it doesn't find the DLR id is still there: 2002-01-02 11:01:41 [7] ERROR: Got DELIV REPORT but couldnt find message or was not interested in it A similar problems occurs when using CIMD2 (when receiving the delivery report from the SMSC): 2002-01-02 11:00:12 [4] INFO: Starting delivery report stefan from 46708443600 2002-01-02 11:00:12 [4] PANIC: gwlib/octstr.c:260: octstr_copy_real: Assertion `len = 0' failed. On Tue, 1 Jan 2002, Stipe Tolj wrote: When using DLR with my SMSC that uses SMPP kannel crashes (cvs version): 2001-12-31 21:42:27 [9] DEBUG: ** SMPP handle_pdu Got DELIVER REPORT 2001-12-31 21:42:27 [9] PANIC: gwlib/octstr.c:2032: seems_valid_real: Assertion `ostr != NULL' failed. (Called from gwlib/octstr.c:728:octstr_compare.) it seems that there is a octstr_compare() call within smsc_smpp.c at line 449-450 that cause this assertion. The following atteched patch should fix this NULL pointer assertion for octstr_compare?! Stefan, please try this patch and report and if there are no objections we will commit the patch to cvs. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
RE: Stripping Kannel
Stipe Tolj wrote: I agree this is an interesting thing. We also use kannel as a SMS gateway only, and striping down everything wap related makes sense to us, too. so you would agree to have a configure switch that strips down everything WAP related in bearerbox, right?! Yes, that would be fine. Regarding to the exclusion of some smsc drivers from bearerbox, I agree with you, I don't see any advantage in a --with-smsc-only=[xxx] flag. Angel.
Some issues with kannel
Hi I'm using cvs release dec 12 of kannel with CMG SMSC over emi2, I have some issues OTA call-type setting when I send wap settings through OTA, though I have call-type to analog in the configuration I get ISDN on my phone (NOKIA 3330) please explain why its happeneing Sneding message to ICQ can we use kannel to send SMS message to ICQ as we can send it through phone ICQ append +8869177427 as prefix to ICQ number but when Itry to send to ICQ as follows lynx -dump 'http://localhost:13013/cgi-bin/sendsms?username=usernamepassword=passwordfrom=333to=00886917742731541662text=Message' I don't get any message to ICQ, also don't get anything in bearerbox log, has anyone tried this, why I'm not getting message on ICQ DLR usage can somebody tell me how I cna use DLR like where will I get the delivery reports if I send message through kannel, I want to design a system like www.sms.ac which can tell the status of message and has any one tried to send Flasing SMS in which test is flashing? regards Steve
