unsubscribe
Kannel connection using Internet Proxy
Hi everyone, Though we configured Kannel specifying the correct proxy settings (Microsoft ISA Server), the Clickatell (http) connection with respective message center is not working. Does anyone has any experience of configuring Kannel behind an Internet proxy? Kind Regards, Gjergji
RE: Kannel connection using Internet Proxy
Thanks Nikos, Just to clarify any ambiguity, do you mean that by setting core http-proxy-host we can send SMS though the external Clicktell smsc connection? Kind Regards, Gjergji -Original Message- From: Nikos Balkanas [mailto:nbalka...@gmail.com] Sent: Tuesday, June 21, 2011 6:04 PM To: Gjergji Guri; us...@vm1.kannel.org Cc: David Naco Subject: Re: Kannel connection using Internet Proxy Hi, core uses http-proxy-host, for outgoing HTTP connections to outside servers. This affects core, wapbox and smsbox. There is no such proxy support for smsc connections. BR, Nikos - Original Message - From: Gjergji Guri To: users@kannel.org Cc: David Naco Sent: Tuesday, June 21, 2011 4:20 PM Subject: Kannel connection using Internet Proxy Hi everyone, Though we configured Kannel specifying the correct proxy settings (Microsoft ISA Server), the Clickatell (http) connection with respective message center is not working. Does anyone has any experience of configuring Kannel behind an Internet proxy? Kind Regards, Gjergji
Upgrade to Rel 1.5
Hi All, I just wanted to ask some feedback if someone has carried out the upgrade from v. 1.4.3 to the latest 1.5 Release. Were there issues after the upgrade using the same configurations? Has real benefits been experienced as listed in new release features? Kind Regards, Gjergji
DLR Callback Unexpected Error with Clickatell
Hi everyone, We had a problem to set the dlr callback URL using Clicktell portal for a new user account yesterday. I was not able to set the Delivery URL in the configuration Clickatell using their web site for a new account. When setting the value of the Enable SMS Status Notification (MT Callback) to http://OurRealIP:13015/cgi-bin/sendsmshttp://217.24.241.130:13015/cgi-bin/sendsms that points to our Kannel server, we’re getting an error message saying *Clickatell was unable to verify the URL specified. Reason code: HTTP (400) : Bad Request. * * * We then tried to set the Delivery URL for another Clickatell account for which we were succesfully receiving DLR untill 5 minutes ago, but again the request was not succesfull and the bb log was showing the following lines 2010-10-06 00:33:58 [2121] [6] DEBUG: HTTP[clickatell]: Got request `/cgi-bin/sendsms' 2010-10-06 00:33:58 [2121] [6] DEBUG: HTTP[clickatell]: Received a request 2010-10-06 00:33:58 [2121] [6] ERROR: HTTP[clickatell]: Insufficient args. 2010-10-06 00:33:58 [2121] [6] DEBUG: HTTP[clickatell]: Sending reply `Insufficient arguments, rejected.'. 2010-10-06 00:33:58 [2121] [6] DEBUG: HTTP: Resetting HTTPClient for `196.5.254.33'. 2010-10-06 00:33:58 [2121] [6] DEBUG: HTTP[clickatell]: Destroying client information 2010-10-06 00:33:59 [2121] [1] DEBUG: HTTP: Destroying HTTPClient area 0x9430a40. I raised an issue with Clickatell immediatelly as we did not make any changes at our end and I still do not have an answer. Does anyone have any clue about what my be the reason? Regards, Gjergji
Issue when processing DLR using model
Hi everyone, I'm able to process incomming SMS with Kannel default modem configuratin, but I'm not able to process message delivery report, which as shown in the bb log attached are received, but not processed correctly. I get the got +CMT but pdu_extract failed message and though I've played for a day with init strings for my ZTE USB modem, the processing of delivery does not happen. The DLR-URL that I use is identical for clickatell SMSC and modem and a sample of sendsms url is shown below http://localhost:13011/cgi-bin/sendsms?username=userpassword=userto=355682073698from=%22FZ%20Sh.p.k%22text=CiaoGjergjidlr-mask=31dlr-url=http%3A%2F%2F192.168.1.15%2Fdlr.php%3Fdlr%3D%25d%26to%3D%25p%26from%3D%25P%26ts%3D%25T%26smsID%3D120343994592 Does anybody has any idea or suggestion what shall I fix? Kind Regards, Gjergji kannel.conf Description: Binary data 2010-09-29 10:22:05 [17716] [0] INFO: 2010-09-29 10:22:05 [17716] [0] INFO: Kannel bearerbox II version 1.4.3 starting 2010-09-29 10:22:05 [17716] [0] INFO: Loading store file `/var/log/kannel/bearerbox.store' 2010-09-29 10:22:05 [17716] [0] INFO: Store-file size 0, starting to unpack 2010-09-29 10:22:05 [17716] [0] INFO: Retrieved 0 messages, non-acknowledged messages: 0 2010-09-29 10:22:05 [17716] [0] DEBUG: Started thread 10 (gw/bb_store_file.c:store_dumper) 2010-09-29 10:22:05 [17716] [0] INFO: MAIN: Start-up done, entering mainloop 2010-09-29 10:22:05 [17716] [0] DEBUG: AT2[AMCZTE]: start called 2010-09-29 10:22:05 [17716] [9] DEBUG: Thread 9 (gw/bb_smscconn.c:sms_router) maps to pid 17716. 2010-09-29 10:22:05 [17716] [10] DEBUG: Thread 10 (gw/bb_store_file.c:store_dumper) maps to pid 17716. 2010-09-29 10:22:05 [17716] [10] DEBUG: Dumping 0 messages to store 2010-09-29 10:22:05 [17716] [8] DEBUG: Thread 8 (gw/smsc/smsc_at.c:at2_device_thread) maps to pid 17716. 2010-09-29 10:22:05 [17716] [8] INFO: AT2[AMCZTE]: trying to use speed 9600 from modem definition 2010-09-29 10:22:05 [17716] [8] INFO: AT2[AMCZTE]: opening device 2010-09-29 10:22:06 [17716] [8] DEBUG: AT2[AMCZTE]: device opened. Telnet mode = 0 2010-09-29 10:22:06 [17716] [8] DEBUG: AT2[AMCZTE]: device opened 2010-09-29 10:22:06 [17716] [8] INFO: AT2[AMCZTE]: speed set to 9600 2010-09-29 10:22:06 [17716] [8] DEBUG: AT2[AMCZTE]: -- ^M 2010-09-29 10:22:06 [17716] [5] INFO: Client connected from 127.0.0.1 2010-09-29 10:22:06 [17716] [5] DEBUG: Started thread 11 (gw/bb_boxc.c:function) 2010-09-29 10:22:06 [17716] [11] DEBUG: Thread 11 (gw/bb_boxc.c:function) maps to pid 17716. 2010-09-29 10:22:06 [17716] [11] DEBUG: Started thread 12 (gw/bb_boxc.c:boxc_sender) 2010-09-29 10:22:06 [17716] [12] DEBUG: Thread 12 (gw/bb_boxc.c:boxc_sender) maps to pid 17716. 2010-09-29 10:22:08 [17716] [8] DEBUG: AT2[AMCZTE]: -- AT^M 2010-09-29 10:22:08 [17716] [8] DEBUG: AT2[AMCZTE]: -- OK 2010-09-29 10:22:08 [17716] [8] INFO: AT2[AMCZTE]: Closing device 2010-09-29 10:22:08 [17716] [8] INFO: AT2[AMCZTE]: speed is 9600 2010-09-29 10:22:08 [17716] [8] INFO: AT2[AMCZTE]: opening device 2010-09-29 10:22:08 [17716] [8] DEBUG: AT2[AMCZTE]: device opened. Telnet mode = 0 2010-09-29 10:22:08 [17716] [8] DEBUG: AT2[AMCZTE]: device opened 2010-09-29 10:22:08 [17716] [8] INFO: AT2[AMCZTE]: Logging in 2010-09-29 10:22:09 [17716] [8] INFO: AT2[AMCZTE]: init device 2010-09-29 10:22:09 [17716] [8] INFO: AT2[AMCZTE]: speed set to 9600 2010-09-29 10:22:09 [17716] [8] DEBUG: AT2[AMCZTE]: -- ATZ^M 2010-09-29 10:22:09 [17716] [8] DEBUG: AT2[AMCZTE]: -- OK 2010-09-29 10:22:09 [17716] [8] DEBUG: AT2[AMCZTE]: -- AT^M 2010-09-29 10:22:09 [17716] [8] DEBUG: AT2[AMCZTE]: -- AT 2010-09-29 10:22:09 [17716] [8] DEBUG: AT2[AMCZTE]: -- OK 2010-09-29 10:22:09 [17716] [8] DEBUG: AT2[AMCZTE]: -- ATF^M 2010-09-29 10:22:09 [17716] [8] DEBUG: AT2[AMCZTE]: -- ATF 2010-09-29 10:22:09 [17716] [8] DEBUG: AT2[AMCZTE]: -- OK 2010-09-29 10:22:09 [17716] [8] DEBUG: AT2[AMCZTE]: -- ATE0^M 2010-09-29 10:22:09 [17716] [8] DEBUG: AT2[AMCZTE]: -- ATE0 2010-09-29 10:22:09 [17716] [8] DEBUG: AT2[AMCZTE]: -- OK 2010-09-29 10:22:09 [17716] [8] DEBUG: AT2[AMCZTE]: -- AT+IFC=2,2^M 2010-09-29 10:22:09 [17716] [8] DEBUG: AT2[AMCZTE]: -- OK 2010-09-29 10:22:09 [17716] [8] DEBUG: AT2[AMCZTE]: -- AT+CPIN?^M 2010-09-29 10:22:10 [17716] [8] DEBUG: AT2[AMCZTE]: -- +CPIN: READY 2010-09-29 10:22:10 [17716] [8] DEBUG: AT2[AMCZTE]: -- OK 2010-09-29 10:22:10 [17716] [8] DEBUG: AT2[AMCZTE]: -- AT+CSCA=+35568100^M 2010-09-29 10:22:10 [17716] [8] DEBUG: AT2[AMCZTE]: -- OK 2010-09-29 10:22:10 [17716] [8] DEBUG: AT2[AMCZTE]: -- AT+CMGF=0^M 2010-09-29 10:22:10 [17716] [8] DEBUG: AT2[AMCZTE]: -- OK 2010-09-29 10:22:10 [17716] [8] DEBUG: AT2[AMCZTE]: -- AT+CSMS=?^M 2010-09-29 10:22:10 [17716] [8] DEBUG: AT2[AMCZTE]: -- +CSMS: (0-1) 2010-09-29 10:22:10 [17716] [8] DEBUG: AT2[AMCZTE]: -- OK 2010-09-29 10:22:10 [17716] [8] DEBUG: AT2[AMCZTE]: -- AT+CNMI=1,2,0,1,0^M 2010-09-29 10:22:10 [17716] [8] DEBUG: AT2[AMCZTE]: -- OK 2010-09-29 10:22:10
Re: Nokia N73
Hi Zak, Have you checked the init string? you can use wvdialconf from the command prompt to find out the inits string of your modem. Are you able to send SMS using the AT commands. You can use minicom program. Cheers, Gjergji On Sun, Aug 29, 2010 at 10:32 AM, Zak xi...@netscape.net wrote: Here's more log from kannel: 2010-08-28 21:28:41 [4145] [0] INFO: Debug_lvl = 1, log_file = none, log_lvl = 0 2010-08-28 21:28:41 [4145] [0] WARNING: DLR: using default 'internal' for storage type. 2010-08-28 21:28:41 [4145] [0] INFO: DLR using storage type: internal 2010-08-28 21:28:41 [4145] [0] INFO: Added logfile `/usr/local/kannel/logs/kannel.log' with level `0'. 2010-08-28 21:28:41 [4145] [0] INFO: Started access logfile `/usr/local/kannel/logs/core_access.log'. 2010-08-28 21:28:41 [4145] [0] INFO: HTTP: Opening server at port 13000. 2010-08-28 21:28:41 [4145] [0] INFO: BOXC: 'smsbox-max-pending' not set, using default (100). 2010-08-28 21:28:41 [4145] [0] INFO: Set SMS resend frequency to 60 seconds. 2010-08-28 21:28:41 [4145] [0] INFO: SMS resend retry set to unlimited. 2010-08-28 21:28:41 [4145] [0] INFO: DLR rerouting for smsc id modem disabled. 2010-08-28 21:28:41 [4145] [0] INFO: Added logfile `/usr/local/kannel/logs/modem.log' with level `1'. 2010-08-28 21:28:41 [4145] [0] INFO: AT2[modem]: configuration shows modemtype Nokia 2010-08-28 21:28:41 [4145] [0] INFO: AT2[modem]: read modem definition for Nokia 2010-08-28 21:28:41 [4145] [0] INFO: 2010-08-28 21:28:41 [4145] [0] INFO: Kannel bearerbox II version 1.4.3 starting 2010-08-28 21:28:41 [4145] [0] INFO: MAIN: Start-up done, entering mainloop 2010-08-28 21:28:41 [4145] [6] INFO: Logging thread `6' to logfile `/usr/local/kannel/logs/modem.log' with level `1'. 2010-08-28 21:28:51 [4145] [0] WARNING: Killing signal or HTTP admin command received, shutting down... 2010-08-28 21:28:54 [4145] [0] INFO: All flow threads have died, killing core 2010-08-28 21:28:54 [4145] [0] INFO: Total WDP messages: received 0, sent 0 2010-08-28 21:28:54 [4145] [0] INFO: Total SMS messages: received 0, sent 0 -Original Message- From: Nikos Balkanas nbalka...@gmail.com To: users@kannel.org; Zak xi...@netscape.net Sent: Sun, Aug 29, 2010 1:24 am Subject: Re: Nokia N73 Please repost same logs at maximum detail. BR, Nikos - Original Message - From: Zak To: users@kannel.org Sent: Saturday, August 28, 2010 11:43 PM Subject: Nokia N73 Hi All, I have a Nokia N73 that I could use to send SMS with minicom and also managed to get the init string using wvdial. But not been able to use kannel to get it send or receive SMS. The log from kannel is below and it just keeps on openning and closing device. 2010-08-28 21:28:41 [4145] [6] INFO: AT2[modem]: opening device 2010-08-28 21:28:42 [4145] [6] INFO: AT2[modem]: Logging in 2010-08-28 21:28:42 [4145] [6] INFO: AT2[modem]: init device 2010-08-28 21:28:42 [4145] [6] INFO: AT2[modem]: speed set to 460800 2010-08-28 21:28:43 [4145] [6] INFO: AT2[modem]: AT SMSC successfully opened. 2010-08-28 21:28:45 [4145] [6] INFO: AT2[modem]: Closing device 2010-08-28 21:28:45 [4145] [6] ERROR: AT2[modem]: Couldn't connect (retrying in 10 seconds). My modem config is: group = modems id = Nokia name = Nokia detect-string = Nokia Mobile Phones detect-string2 = N93 need-sleep = true init-string=ATZ enable-mms = true and SMSC group = smsc smsc = at smsc-id = modem modemtype = Nokia device = /dev/ttyACM0 speed = 460800 sim-buffering = true keepalive = 180 idle-timeout = 160 denied-prefix = 633;213;286;200;633;8001;277 log-file = /usr/local/kannel/logs/modem.log log-level=1 My wvdialconf file generated: [Dialer Defaults] Modem = /dev/ttyACM0 Baud = 460800 Init1 = ATZ Init2 = ATQ0 V1 E1 S0=0 C1 D2 +FCLASS=0 ISDN = 0 Modem Type = USB Modem ; Phone = Target Phone Number ; Username = Your Login Name ; Password = Your Password Any help appreciated. Thanks, Zak
Getting DLR reports for AT SMSC
Hi, I have no problem to get DLR report for http SMSC by setting the correct dlr-mask and dlr-url. Nevertheless, though my modem driver and network support receiving delivery reports the bearerbox do not process any delivery reports. At page 64 of the User Guide (Feature checklist) or Table 6-2. SMSC driver features I can see that for AT driver the “Can Use DLR” is set to N. Nevertheless, N is set even for http request where the delivery is working fine in my configuration. Do I need to setup some specific processing for the incoming SMS delivery reports retrieved by the AT modem? Has anyone configured delivery reports with Kannel using a modem (AT SMSC driver)? Any hint, guidance? Cheers, Gjergji
Re: Getting DLR reports for AT SMSC
Many thanks Nikos and good to hear that it works. I've configured DLR callback with Clickatell (system-type = clickatell) having the smsc variable set to http. This is configured as a separate SMSC and I have no problem with processing DLR. I've configure a HUAWEI E618 Mobile Connect - 3G Modem and can send SMS messages using HTTP Push service. In my current configuration I do not see the dlr-url to be called, when I use the GSM modem, which works when message is routed via clickatell. Do I need to make any specific configuration for the GSM modem smsc in order for the delivery status reports to be processed? Kind Regards, Gjergji 2010/8/28 Nikos Balkanas nbalka...@gmail.com Yes, and it works. Note that using a GSM modem is more reliable than a phone. Some providers do not send DLRs to a phone. But what do you mean by http SMSc? A GSM modem is different than an HTTP smsc. BR, Nikos - Original Message - From: Gjergji Guri To: users@kannel.org Sent: Saturday, August 28, 2010 10:39 AM Subject: Getting DLR reports for AT SMSC Hi, I have no problem to get DLR report for http SMSC by setting the correct dlr-mask and dlr-url. Nevertheless, though my modem driver and network support receiving delivery reports the bearerbox do not process any delivery reports. At page 64 of the User Guide (Feature checklist) or Table 6-2. SMSC driver features I can see that for AT driver the “Can Use DLR” is set to N. Nevertheless, N is set even for http request where the delivery is working fine in my configuration. Do I need to setup some specific processing for the incoming SMS delivery reports retrieved by the AT modem? Has anyone configured delivery reports with Kannel using a modem (AT SMSC driver)? Any hint, guidance? Cheers, Gjergji
Re: Getting DLR reports for AT SMSC
That's correct Alvaro, but if I take the SIM card out of the modem and insert it in my Nokia phone I get delivery status. I tested the same by turning off and on the recipient phone, and the Vodafone network in Albania support the delivery status reports. Regards, Gjergji On Sat, Aug 28, 2010 at 3:41 PM, Alvaro Cornejo cornejo.alv...@gmail.comwrote: Hi As noted by Nikos, many operators do not send any dlr back to phone numbers, so it might be OK not to have any dlr from you operator. In this case, the only dlr you will receive is the one generated by kannel saying that it has sent the message to the smsc and it --the smsc-- received the sms. YOu won´t receive any further info of its status. Regards Alvaro |-| 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 2010/8/28 Nikos Balkanas nbalka...@gmail.com: Nothing different from your http smsc connection. Do you see any DLRs in access log from GSM modem? Please post your configuration and detailed bb logs of a deliver_sm pdu from your GSM modem, with context. BR, Nikos - Original Message - From: Gjergji Guri To: Nikos Balkanas Cc: users@kannel.org Sent: Saturday, August 28, 2010 3:30 PM Subject: Re: Getting DLR reports for AT SMSC Many thanks Nikos and good to hear that it works. I've configured DLR callback with Clickatell (system-type = clickatell) having the smsc variable set to http. This is configured as a separate SMSC and I have no problem with processing DLR. I've configure a HUAWEI E618 Mobile Connect - 3G Modem and can send SMS messages using HTTP Push service. In my current configuration I do not see the dlr-url to be called, when I use the GSM modem, which works when message is routed via clickatell. Do I need to make any specific configuration for the GSM modem smsc in order for the delivery status reports to be processed? Kind Regards, Gjergji 2010/8/28 Nikos Balkanas nbalka...@gmail.com Yes, and it works. Note that using a GSM modem is more reliable than a phone. Some providers do not send DLRs to a phone. But what do you mean by http SMSc? A GSM modem is different than an HTTP smsc. BR, Nikos - Original Message - From: Gjergji Guri To: users@kannel.org Sent: Saturday, August 28, 2010 10:39 AM Subject: Getting DLR reports for AT SMSC Hi, I have no problem to get DLR report for http SMSC by setting the correct dlr-mask and dlr-url. Nevertheless, though my modem driver and network support receiving delivery reports the bearerbox do not process any delivery reports. At page 64 of the User Guide (Feature checklist) or Table 6-2. SMSC driver features I can see that for AT driver the “Can Use DLR” is set to N. Nevertheless, N is set even for http request where the delivery is working fine in my configuration. Do I need to setup some specific processing for the incoming SMS delivery reports retrieved by the AT modem? Has anyone configured delivery reports with Kannel using a modem (AT SMSC driver)? Any hint, guidance? Cheers, Gjergji
Re: SMPP Configuration with Clickatell
Many thanks to everyone who promptly responded and have a nice weekend. Gjergji On Fri, Aug 20, 2010 at 11:36 PM, Alejandro Guerrieri alejandro.guerri...@gmail.com wrote: I've connected to their SMPP gateway time ago (5 years). Not sure if they've changed anything in the meantime, but you shouldn't have any issues with it. Kannel is fully SMPP 3.4 compliant and the SVN version supports the optional parameters (which is the only custom thing you'd expect to find in any case). Regards, Alex On Fri, Aug 20, 2010 at 5:37 PM, Gjergji Guri gjergji.g...@facilization.com wrote: Hi, Before starting the configuration work, I just wanted to know whether someone has configured Kannel SMPP gateway with Clickatell, whose API acknolidges compliance with SMPP version 3.4. Regards, Gjergji
SMPP Configuration with Clickatell
Hi, Before starting the configuration work, I just wanted to know whether someone has configured Kannel SMPP gateway with Clickatell, whose API acknolidges compliance with SMPP version 3.4. Regards, Gjergji
Hardware GSM Modem to use with Kannel
Hi, The GSM modem configuration using my Nokia phone is running perfictly. Thanks to everyone for the advice given. Message routing work fine and my only mistake was adding comments at the same line with configuration parameter. At this moment I wanted to buy some GMS modems (USP or other connection) for use instead of the my mobile phone. Does anyone recommend me any hardware that he's been tested with Kannel? Nice weekend for all, Cheers, Gjergji
FW: Outbound force routing for a proffered-prefix in Kannel
Hi Nikos, I’m sending this request directly as I did not received any response from other users. Is it possible to tell Kannel which SMSC to use for a particular prefix? I have different outbound SMSC costs for different operators and I want to implement some basic costs routing. Any other advice? Kind Regards, Gjergji *From:* Gjergji Guri [mailto:gjergji.g...@facilization.com] *Sent:* Thursday, July 08, 2010 6:34 PM *To:* users@kannel.org *Subject:* Outbound force routing for a proffered-prefix in Kannel Hi, I'm having some difficulties in configuring outbound routing in Kannel, though I tried a number of option according to the latest user guide. The objective I want to achieve is have the http PUSH SMS messages that come from a predefined prefix to be routed by default to a predefined SMSC. I've tried various configuration, but it seems that Kannel is using load sharing. Some more details in included below: I use the following PUSH URL where I tell which smsc to use as below http://localhost:13011/cgi-bin/sendsms?smsc=nokiae90username=userpassword=passwordfrom=xxto=35569xxtext=Hello As you may see from the status log Kannel tries to use the click smsc-id SMSC connections: *click*HTTP:clickatell (online 122s, rcvd 0, sent 0, failed 1, queued 0 msgs) *nokiae90*AT2[nokiae90] (online 116s, rcvd 0, sent 4, failed 0, queued 0 msgs) # SMSC SETUP: Clickatell HTTP group = smsc smsc = http smsc-id = click system-type = clickatell port = 13015 connect-allow-ip = 127.0.0.1;196.5.254.33;192.168.*.* system-id = xxx smsc-username = i smsc-password = xx send-url = http://api.clickatell.com/http/sendmsg; # allowed-smsc-id = click *denied-prefix = 35569;069;69 * reroute = yes # Added by Gj.G reroute-smsc-id = nokiae90 #SMSC SETUP: Nokia E90 GSM Modem group = smsc smsc = at smsc-id = nokiae90 modemtype = nokiaphone device=/dev/ttyACM0 *preferred-smsc-id = nokiae90 * *preferred-prefix = 35569 * # SEND-SMS USERS group = sendsms-user username = user password = password #forced-smsc = # default-smsc = click# Added by Gj.G #default-smsc = nokiae90 max-messages = 3 It seems that kannel cannot force routing to a predefined smsc-id. Does anyone have any configuration suggestion? Cheers, Gjergji
Outbound force routing for a proffered-prefix in Kannel
Hi, I'm having some difficulties in configuring outbound routing in Kannel, though I tried a number of option according to the latest user guide. The objective I want to achieve is have the http PUSH SMS messages that come from a predefined prefix to be routed by default to a predefined SMSC. I've tried various configuration, but it seems that Kannel is using load sharing. Some more details in included below: I use the following PUSH URL where I tell which smsc to use as below http://localhost:13011/cgi-bin/sendsms?smsc=nokiae90username=userpassword=passwordfrom=xxto=35569xxtext=Hello As you may see from the status log Kannel tries to use the click smsc-id SMSC connections: *click*HTTP:clickatell (online 122s, rcvd 0, sent 0, failed 1, queued 0 msgs) *nokiae90*AT2[nokiae90] (online 116s, rcvd 0, sent 4, failed 0, queued 0 msgs) # SMSC SETUP: Clickatell HTTP group = smsc smsc = http smsc-id = click system-type = clickatell port = 13015 connect-allow-ip = 127.0.0.1;196.5.254.33;192.168.*.* system-id = xxx smsc-username = i smsc-password = xx send-url = http://api.clickatell.com/http/sendmsg; # allowed-smsc-id = click *denied-prefix = 35569;069;69 * reroute = yes # Added by Gj.G reroute-smsc-id = nokiae90 #SMSC SETUP: Nokia E90 GSM Modem group = smsc smsc = at smsc-id = nokiae90 modemtype = nokiaphone device=/dev/ttyACM0 *preferred-smsc-id = nokiae90 * *preferred-prefix = 35569 * # SEND-SMS USERS group = sendsms-user username = user password = password #forced-smsc = # default-smsc = click# Added by Gj.G #default-smsc = nokiae90 max-messages = 3 It seems that kannel cannot force routing to a predefined smsc-id. Does anyone have any configuration suggestion? Cheers, Gjergji
Re: Problem in Pushing SMS messages using Nokia E90 model
Hi Nikos, I've attached the smsbox log. The command that I use for sendning a message is lynx -dump http://localhost:13011/cgi-bin/sendsms?username=fcsuserpassword=fcsuserfrom=FZSh.p.kto=355692032105text=Hello; or I can use a web browser similarly. The command works with a web gateway like for example Clickatell. I get 3: Queued for later delivery. I've played a lot with configuration strings as advised in the manual. The other commands as explained in my previous e-mail work. I'm attaching the kannel.conf file. Looking forward of some help or advice, Cheers, Gjergji 2010/6/26 Nikos Balkanas nbalka...@gmail.com Hi, Please read latest User's guide. There is a special section devoted to modem initialization. If that doesn't help, post detailed bb + smsbox logs of modem initialization and attempt to push. Also post your push url. BR, Nikos - Original Message - From: Gjergji Guri gjergji.g...@facilization.com To: users@kannel.org Sent: Saturday, June 26, 2010 5:48 PM Subject: Problem in Pushing SMS messages using Nokia E90 model Hi, I've configured Kannel on Ubuntu and I have no issues if I try to send messages with my clickatell account. Nevertheless, I'm not able to get Kannel modem configuration right using my Nokia E90 phone. A briefing of the configuration has been included below #SMSC SETUP: Nokia E90 GSM Modem group = smsc smsc = at smsc-id = nokiae90 modemtype = Nokia device=/dev/ttyACM0 speed = 460800 pin = # Modem SETUP group = modems id = Nokia name = Nokia #init-string = ATZ init-string = ATQ0 V1 E1 S0=0 C1 D2 +FCLASS=0 #init-string = AT+CNMI=0,0,0,0,0 #init-string = AT+CNMI=1,0,1,2,0 detect-string = Nokia Mobile Phone need-sleep = true keepalive-cmd = AT+CBC;+CSQ The output of status when starting smsbox is shown below: r...@ubu1004:/etc/kannel# lynx -dump http://localhost:13000/status?password=fcsadmin; Kannel bearerbox version `1.4.3'. Build `Jun 11 2010 06:46:37', compiler `4.4.3'. System Linux, release 2.6.32-22-generic, version #36-Ubuntu SMP Thu Jun 3 22:02:19 UTC 2010, machine i686. Hostname ubu1004, IP 127.0.1.1. Libxml version 2.7.6. Compiled with MySQL 5.1.41, using MySQL 5.1.41. Using native malloc. Status: running, uptime 0d 0h 14m 35s WDP: received 0 (0 queued), sent 0 (0 queued) SMS: received 0 (0 queued), sent 0 (1 queued), store size 1 SMS: inbound (0.00,0.00,0.00) msg/sec, outbound (0.00,0.00,0.00) msg/sec DLR: 0 queued, using internal storage Box connections: smsbox:fcs_smsbox, IP 127.0.0.1 (0 queued), (on-line 0d 0h 14m 33s) SMSC connections: nokiae90AT2[nokiae90] (connecting, rcvd 0, sent 0, failed 0, queued 0 msgs) I'm able to send SMS with no issue using gsmsendsms -d /dev/ttyACM0 0692032105 “hello” The output of wvdialconf command is included below ttyACM0*1: Modem Identifier: ATI -- Nokia ttyACM0*1: Speed 4800: AT -- OK ttyACM0*1: Speed 9600: AT -- OK ttyACM0*1: Speed 19200: AT -- OK ttyACM0*1: Speed 38400: AT -- OK ttyACM0*1: Speed 57600: AT -- OK ttyACM0*1: Speed 115200: AT -- OK ttyACM0*1: Speed 230400: AT -- OK ttyACM0*1: Speed 460800: AT -- OK ttyACM0*1: Max speed is 460800; that should be safe. ttyACM0*1: ATQ0 V1 E1 S0=0 C1 D2 +FCLASS=0 -- OK Found an USB modem on /dev/ttyACM0. Modem configuration written to /etc/wvdial.conf. ttyACM0Info: Speed 460800; init ATQ0 V1 E1 S0=0 C1 D2 +FCLASS=0 I would greatly appreciate an advice from a senior person as to how I can get the nokia modem status to on-line. Thanks and regards, Gjergji 2010-06-30 08:42:38 [12907] [0] INFO: Added logfile `/var/log/kannel/smsbox.log' with level `0'. 2010-06-30 08:42:38 [12907] [0] INFO: HTTP: Opening server at port 13011. 2010-06-30 08:42:38 [12907] [0] DEBUG: Started thread 1 (gwlib/fdset.c:poller) 2010-06-30 08:42:38 [12907] [0] DEBUG: Started thread 2 (gwlib/http.c:server_thread) 2010-06-30 08:42:38 [12907] [0] INFO: Set up send sms service at port 13011 2010-06-30 08:42:38 [12907] [0] DEBUG: Started thread 3 (gw/smsbox.c:sendsms_thread) 2010-06-30 08:42:38 [12907] [0] DEBUG: -- 2010-06-30 08:42:38 [12907] [0] DEBUG: Kannel smsbox version 1.4.3 starting 2010-06-30 08:42:38 [12907] [1] DEBUG: Thread 1 (gwlib/fdset.c:poller) maps to pid 12907. 2010-06-30 08:42:38 [12907] [3] DEBUG: Thread 3 (gw/smsbox.c:sendsms_thread) maps to pid 12907. 2010-06-30 08:42:38 [12907] [2] DEBUG: Thread 2 (gwlib/http.c:server_thread) maps to pid 12907. 2010-06-30 08:42:38 [12907] [0] DEBUG: dumping group (sendsms-user): 2010-06-30 08:42:38 [12907] [0] DEBUG: faked-sender = FZ Sh.p.k 2010-06-30 08:42:38 [12907] [0] DEBUG: group = sendsms-user 2010-06-30 08:42:38 [12907] [0] DEBUG: default-smsc = nokiae90 2010-06-30 08:42:38 [12907] [0] DEBUG: max-messages = 3 2010-06-30 08:42:38 [12907] [0] DEBUG: username = fcsuser 2010-06-30 08:42:38 [12907] [0] DEBUG: password = fcsuser 2010-06-30 08:42
Re: Problem in Pushing SMS messages using Nokia E90 model
Dear All, I resolved the issue of the modem staying under the Connecting Stage. The reason was access permissions. Though, I start kannel as a root user it seemed that it did not have access to /dev/ttyACM0 or /dev/bus/usb/002 port. I had to change the permission of the port. Is this normal? Regards, Gjergji On Wed, Jun 30, 2010 at 8:53 AM, Gjergji Guri gjergji.g...@facilization.com wrote: Hi Nikos, I've attached the smsbox log. The command that I use for sendning a message is lynx -dump http://localhost:13011/cgi-bin/sendsms?username=fcsuserpassword=fcsuserfrom=FZSh.p.kto=355692032105text=Hello; or I can use a web browser similarly. The command works with a web gateway like for example Clickatell. I get 3: Queued for later delivery. I've played a lot with configuration strings as advised in the manual. The other commands as explained in my previous e-mail work. I'm attaching the kannel.conf file. Looking forward of some help or advice, Cheers, Gjergji 2010/6/26 Nikos Balkanas nbalka...@gmail.com Hi, Please read latest User's guide. There is a special section devoted to modem initialization. If that doesn't help, post detailed bb + smsbox logs of modem initialization and attempt to push. Also post your push url. BR, Nikos - Original Message - From: Gjergji Guri gjergji.g...@facilization.com To: users@kannel.org Sent: Saturday, June 26, 2010 5:48 PM Subject: Problem in Pushing SMS messages using Nokia E90 model Hi, I've configured Kannel on Ubuntu and I have no issues if I try to send messages with my clickatell account. Nevertheless, I'm not able to get Kannel modem configuration right using my Nokia E90 phone. A briefing of the configuration has been included below #SMSC SETUP: Nokia E90 GSM Modem group = smsc smsc = at smsc-id = nokiae90 modemtype = Nokia device=/dev/ttyACM0 speed = 460800 pin = # Modem SETUP group = modems id = Nokia name = Nokia #init-string = ATZ init-string = ATQ0 V1 E1 S0=0 C1 D2 +FCLASS=0 #init-string = AT+CNMI=0,0,0,0,0 #init-string = AT+CNMI=1,0,1,2,0 detect-string = Nokia Mobile Phone need-sleep = true keepalive-cmd = AT+CBC;+CSQ The output of status when starting smsbox is shown below: r...@ubu1004:/etc/kannel# lynx -dump http://localhost:13000/status?password=fcsadmin; Kannel bearerbox version `1.4.3'. Build `Jun 11 2010 06:46:37', compiler `4.4.3'. System Linux, release 2.6.32-22-generic, version #36-Ubuntu SMP Thu Jun 3 22:02:19 UTC 2010, machine i686. Hostname ubu1004, IP 127.0.1.1. Libxml version 2.7.6. Compiled with MySQL 5.1.41, using MySQL 5.1.41. Using native malloc. Status: running, uptime 0d 0h 14m 35s WDP: received 0 (0 queued), sent 0 (0 queued) SMS: received 0 (0 queued), sent 0 (1 queued), store size 1 SMS: inbound (0.00,0.00,0.00) msg/sec, outbound (0.00,0.00,0.00) msg/sec DLR: 0 queued, using internal storage Box connections: smsbox:fcs_smsbox, IP 127.0.0.1 (0 queued), (on-line 0d 0h 14m 33s) SMSC connections: nokiae90AT2[nokiae90] (connecting, rcvd 0, sent 0, failed 0, queued 0 msgs) I'm able to send SMS with no issue using gsmsendsms -d /dev/ttyACM0 0692032105 “hello” The output of wvdialconf command is included below ttyACM0*1: Modem Identifier: ATI -- Nokia ttyACM0*1: Speed 4800: AT -- OK ttyACM0*1: Speed 9600: AT -- OK ttyACM0*1: Speed 19200: AT -- OK ttyACM0*1: Speed 38400: AT -- OK ttyACM0*1: Speed 57600: AT -- OK ttyACM0*1: Speed 115200: AT -- OK ttyACM0*1: Speed 230400: AT -- OK ttyACM0*1: Speed 460800: AT -- OK ttyACM0*1: Max speed is 460800; that should be safe. ttyACM0*1: ATQ0 V1 E1 S0=0 C1 D2 +FCLASS=0 -- OK Found an USB modem on /dev/ttyACM0. Modem configuration written to /etc/wvdial.conf. ttyACM0Info: Speed 460800; init ATQ0 V1 E1 S0=0 C1 D2 +FCLASS=0 I would greatly appreciate an advice from a senior person as to how I can get the nokia modem status to on-line. Thanks and regards, Gjergji
Problem in Pushing SMS messages using Nokia E90 model
Hi, I've configured Kannel on Ubuntu and I have no issues if I try to send messages with my clickatell account. Nevertheless, I'm not able to get Kannel modem configuration right using my Nokia E90 phone. A briefing of the configuration has been included below #SMSC SETUP: Nokia E90 GSM Modem group = smsc smsc = at smsc-id = nokiae90 modemtype = Nokia device=/dev/ttyACM0 speed = 460800 pin = # Modem SETUP group = modems id = Nokia name = Nokia #init-string = ATZ init-string = ATQ0 V1 E1 S0=0 C1 D2 +FCLASS=0 #init-string = AT+CNMI=0,0,0,0,0 #init-string = AT+CNMI=1,0,1,2,0 detect-string = Nokia Mobile Phone need-sleep = true keepalive-cmd = AT+CBC;+CSQ The output of status when starting smsbox is shown below: r...@ubu1004:/etc/kannel# lynx -dump http://localhost:13000/status?password=fcsadmin; Kannel bearerbox version `1.4.3'. Build `Jun 11 2010 06:46:37', compiler `4.4.3'. System Linux, release 2.6.32-22-generic, version #36-Ubuntu SMP Thu Jun 3 22:02:19 UTC 2010, machine i686. Hostname ubu1004, IP 127.0.1.1. Libxml version 2.7.6. Compiled with MySQL 5.1.41, using MySQL 5.1.41. Using native malloc. Status: running, uptime 0d 0h 14m 35s WDP: received 0 (0 queued), sent 0 (0 queued) SMS: received 0 (0 queued), sent 0 (1 queued), store size 1 SMS: inbound (0.00,0.00,0.00) msg/sec, outbound (0.00,0.00,0.00) msg/sec DLR: 0 queued, using internal storage Box connections: smsbox:fcs_smsbox, IP 127.0.0.1 (0 queued), (on-line 0d 0h 14m 33s) SMSC connections: nokiae90AT2[nokiae90] (connecting, rcvd 0, sent 0, failed 0, queued 0 msgs) I'm able to send SMS with no issue using gsmsendsms -d /dev/ttyACM0 0692032105 “hello” The output of wvdialconf command is included below ttyACM0*1: Modem Identifier: ATI -- Nokia ttyACM0*1: Speed 4800: AT -- OK ttyACM0*1: Speed 9600: AT -- OK ttyACM0*1: Speed 19200: AT -- OK ttyACM0*1: Speed 38400: AT -- OK ttyACM0*1: Speed 57600: AT -- OK ttyACM0*1: Speed 115200: AT -- OK ttyACM0*1: Speed 230400: AT -- OK ttyACM0*1: Speed 460800: AT -- OK ttyACM0*1: Max speed is 460800; that should be safe. ttyACM0*1: ATQ0 V1 E1 S0=0 C1 D2 +FCLASS=0 -- OK Found an USB modem on /dev/ttyACM0. Modem configuration written to /etc/wvdial.conf. ttyACM0Info: Speed 460800; init ATQ0 V1 E1 S0=0 C1 D2 +FCLASS=0 I would greatly appreciate an advice from a senior person as to how I can get the nokia modem status to on-line. Thanks and regards, Gjergji
