Niels, -- Niels Jonker, njon...@gmail.com
2009/9/3 <users-requ...@kannel.org> > Send users mailing list submissions to > users@kannel.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://www.kannel.org/mailman/listinfo/users > or, via email, send a message with subject or body 'help' to > users-requ...@kannel.org > > You can reach the person managing the list at > users-ow...@kannel.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of users digest..." > > Today's Topics: > > 1. Re: Help required on Kannel (Nikos Balkanas) > 2. Re: Custom command_status in submit_sm_resp (Nikos Balkanas) > 3. Re: Custom command_status in submit_sm_resp (Nikos Balkanas) > 4. Re: Custom command_status in submit_sm_resp (Nikos Balkanas) > 5. Re: Wavecom Modem Not Responding. (Sam) > > > ---------- Forwarded message ---------- > From: "Nikos Balkanas" <nbalka...@gmail.com> > To: "Siddhartha` Adhikari" <grad...@gmail.com> > Date: Thu, 3 Sep 2009 21:05:13 +0300 > Subject: Re: Help required on Kannel > Hi, > > Please address the list so that others benefit as well. Do not send me > personnals. > > Actually store-file is outdated. Look in user-guide for both store-type & > store-location. And enable application log files (not access logs unless > needed). > > These 2 parameters configure kannels message queue. > > BR, > Nikos > > ----- Original Message ----- > *From:* Siddhartha` Adhikari <grad...@gmail.com> > *To:* Nikos Balkanas <nbalka...@gmail.com> > *Sent:* Thursday, September 03, 2009 5:38 PM > *Subject:* Re: Help required on Kannel > > Hi Nikos, > > How would these two parameters help? > > Regards > Siddhartha > > 2009/9/3 Nikos Balkanas <nbalka...@gmail.com> > >> Hi, >> >> You need to have store-file and store-location defined to start bearerbox. >> Read user's guide to configure them. >> >> BR, >> Nikos >> >> ----- Original Message ----- >> *From:* Siddhartha` Adhikari <grad...@gmail.com> >> *To:* users@kannel.org >> *Sent:* Thursday, September 03, 2009 4:46 PM >> *Subject:* Help required on Kannel >> >> Hi, >> >> I downloaded Kannel and installed Cygwin on my Windows XP machine. >> I have the following objective to be met:- >> >> a) Exchange of messages between my java application and Kannel >> b) Exchange of messages between Kannel and an Emulator/Device. >> c) Exchange of messages between my java application and Device via >> Kannel. >> >> I am unable to understand the configurations and not even able to start. >> >> My application needs to recieve a paramter from the device via Kannel and >> then send back a response to the device via Kannel again >> >> How do I change the configurations to send a message from Kannel to my >> java application which is hosted on Tomcat? >> >> Here are the configurations:- >> >> Operating system and version. – Windows XP SP3 version 2002 Professional >> Kannel version. – 1.4.3 >> Libxml version.- libxml2 >> Used client - ? >> Single or multi processor machine. – single processor >> Attach Kannel configuration file (remove passwords and login >> information!). – Attached the smskannel which came with the download. >> Attach Kannel log files from the failed attempt - N/A >> >> Can you please help me out with this? >> >> Regards >> Siddhartha >> >> > > > ---------- Forwarded message ---------- > From: "Nikos Balkanas" <nbalka...@gmail.com> > To: <kan...@rolandow.nl> > Date: Thu, 3 Sep 2009 21:34:35 +0300 > Subject: Re: Custom command_status in submit_sm_resp > Hi, > > Have you tried the %B parameter? Supposedly it returns billing info. It can > be used both in access logs and dlr-urls. Its implementation is smsc > specific. Otherwise i cannot think of any other case, other than application > logs in debug mode, that kannel returns the information you need. > > BR, > Nikos > ----- Original Message ----- From: "Rolandow" <kan...@rolandow.nl> > To: <users@kannel.org> > Sent: Wednesday, September 02, 2009 11:06 AM > Subject: Custom command_status in submit_sm_resp > > > Hi, >> >> I have configured my Kannel, using custom tlv fields. But, according to >> the documentation of the gateway, it's possible that the gateway returns a >> custom command_status in the submit_sm_resp. >> >> For example, they return 0x400 if they were unable to charge the enduser >> because of insufficient funds. >> >> How can I extract these vendor specific codes from Kannel? Will this >> result be returned when I do a request to the sendsms cgi-bin? Would I >> receive a Status 202, but with a different number (I would expect 1024 in >> this case?) >> >> Thanks for your help in advance! :-) >> >> Kind regards, >> Roland. >> >> > > > > > ---------- Forwarded message ---------- > From: "Nikos Balkanas" <nbalka...@gmail.com> > To: <kan...@rolandow.nl> > Date: Thu, 3 Sep 2009 21:48:17 +0300 > Subject: Re: Custom command_status in submit_sm_resp > Hi, > > It seems Alex G is working on a patch to provide this along with other > meta-data with %D. > > BR, > Nikos > ----- Original Message ----- From: "Nikos Balkanas" <nbalka...@gmail.com> > To: <kan...@rolandow.nl> > Cc: <users@kannel.org> > Sent: Thursday, September 03, 2009 9:34 PM > Subject: Re: Custom command_status in submit_sm_resp > > > Hi, >> >> Have you tried the %B parameter? Supposedly it returns billing info. It >> can be used both in access logs and dlr-urls. Its implementation is smsc >> specific. Otherwise i cannot think of any other case, other than application >> logs in debug mode, that kannel returns the information you need. >> >> BR, >> Nikos >> ----- Original Message ----- From: "Rolandow" <kan...@rolandow.nl> >> To: <users@kannel.org> >> Sent: Wednesday, September 02, 2009 11:06 AM >> Subject: Custom command_status in submit_sm_resp >> >> >> Hi, >>> >>> I have configured my Kannel, using custom tlv fields. But, according to >>> the documentation of the gateway, it's possible that the gateway returns a >>> custom command_status in the submit_sm_resp. >>> >>> For example, they return 0x400 if they were unable to charge the enduser >>> because of insufficient funds. >>> >>> How can I extract these vendor specific codes from Kannel? Will this >>> result be returned when I do a request to the sendsms cgi-bin? Would I >>> receive a Status 202, but with a different number (I would expect 1024 in >>> this case?) >>> >>> Thanks for your help in advance! :-) >>> >>> Kind regards, >>> Roland. >>> >>> >> > > > > > ---------- Forwarded message ---------- > From: "Nikos Balkanas" <nbalka...@gmail.com> > To: <kan...@rolandow.nl> > Date: Thu, 3 Sep 2009 21:48:17 +0300 > Subject: Re: Custom command_status in submit_sm_resp > Hi, > > It seems Alex G is working on a patch to provide this along with other > meta-data with %D. > > BR, > Nikos > ----- Original Message ----- From: "Nikos Balkanas" <nbalka...@gmail.com> > To: <kan...@rolandow.nl> > Cc: <users@kannel.org> > Sent: Thursday, September 03, 2009 9:34 PM > Subject: Re: Custom command_status in submit_sm_resp > > > Hi, >> >> Have you tried the %B parameter? Supposedly it returns billing info. It >> can be used both in access logs and dlr-urls. Its implementation is smsc >> specific. Otherwise i cannot think of any other case, other than application >> logs in debug mode, that kannel returns the information you need. >> >> BR, >> Nikos >> ----- Original Message ----- From: "Rolandow" <kan...@rolandow.nl> >> To: <users@kannel.org> >> Sent: Wednesday, September 02, 2009 11:06 AM >> Subject: Custom command_status in submit_sm_resp >> >> >> Hi, >>> >>> I have configured my Kannel, using custom tlv fields. But, according to >>> the documentation of the gateway, it's possible that the gateway returns a >>> custom command_status in the submit_sm_resp. >>> >>> For example, they return 0x400 if they were unable to charge the enduser >>> because of insufficient funds. >>> >>> How can I extract these vendor specific codes from Kannel? Will this >>> result be returned when I do a request to the sendsms cgi-bin? Would I >>> receive a Status 202, but with a different number (I would expect 1024 in >>> this case?) >>> >>> Thanks for your help in advance! :-) >>> >>> Kind regards, >>> Roland. >>> >>> >> > > > > > ---------- Forwarded message ---------- > From: Sam <nu.e...@gmail.com> > To: Nikos Balkanas <nbalka...@gmail.com> > Date: Fri, 4 Sep 2009 00:01:39 +0100 > Subject: Re: Wavecom Modem Not Responding. > Hi, > > Thank you very much Nikos.. It was actually a problem with the modem. > > -Regards > Sam > > 2009/9/3 Nikos Balkanas <nbalka...@gmail.com>: > > Hi, > > > > Please use: > > > > 1) dmesg | grep tty > > To verify that your modem is indeed in dev/ttyS0. If not update > > configuration and restart kannel. > > > > 2) minicom or wvdial and try to connect to modem to see if you get any > > replies. > > When typing AT to it you should get an OK response. Currently kannel > doesn't > > get any response from your modem and is searching in vain. If you don't > get > > a response either, you have a hardware problem (serial port, cable, > modem). > > > > BR, > > Nikos > > > > ----- Original Message ----- From: "nu mail" <nu.e...@gmail.com> > > To: <users@kannel.org> > > Sent: Thursday, September 03, 2009 1:26 AM > > Subject: Wavecom Modem Not Responding. > > > > > >> Hi, > >> > >> Please can someone advise me. I have a Wavecom supreme 10 modem > >> running on a RedHat linux box. Recently, i just observed the following > >> in the logfiles. The process loops indefinitely. Please advise. > >> > >> Your response will be appreciated. > >> > >> ######### Config file ################# > >> group = smsc > >> smsc = at > >> smsc-id = modemSmsc > >> modemtype = WAVECOM > >> device = /dev/ttyS0 > >> my-number = ******** > >> connect-allow-ip = 127.0.0.1 > >> log-level = 0 > >> keepalive = 4 > >> denied-prefix = 0;***;+***;+;* > >> > >> group = modems > >> id = WAVECOM > >> name = "WAVECOM" > >> detect-string = "WAVECOM" > >> > >> ####################################### > >> > >> #################################################### > >> > >> 2009-09-02 08:54:55 [5218] [0] INFO: > >> ---------------------------------------- > >> 2009-09-02 08:54:55 [5218] [0] INFO: Kannel bearerbox II version 1.4.3 > >> starting > >> 2009-09-02 08:54:55 [5218] [9] DEBUG: Thread 9 > >> (gw/bb_smscconn.c:sms_router) maps to pid 5218. > >> 2009-09-02 08:54:55 [5218] [0] INFO: MAIN: Start-up done, entering > >> mainloop > >> 2009-09-02 08:54:55 [5218] [0] DEBUG: AT2[modemSmsc]: start called > >> 2009-09-02 08:54:55 [5218] [8] DEBUG: Thread 8 > >> (gw/smsc/smsc_http.c:httpsmsc_send_cb) maps to pid 5218. > >> 2009-09-02 08:54:55 [5218] [7] DEBUG: Thread 7 > >> (gw/smsc/smsc_http.c:httpsmsc_receiver) maps to pid 5218. > >> 2009-09-02 08:54:55 [5218] [6] INFO: AT2[modemSmsc]: speed set to 9600 > >> 2009-09-02 08:54:55 [5218] [6] DEBUG: AT2[modemSmsc]: --> ^M > >> 2009-09-02 08:54:56 [5218] [5] INFO: Client connected from <127.0.0.1> > >> 2009-09-02 08:54:56 [5218] [5] DEBUG: Started thread 10 > >> (gw/bb_boxc.c:function) > >> 2009-09-02 08:54:56 [5218] [10] DEBUG: Thread 10 > >> (gw/bb_boxc.c:function) maps to pid 5218. > >> 2009-09-02 08:54:56 [5218] [10] DEBUG: Started thread 11 > >> (gw/bb_boxc.c:boxc_sender) > >> 2009-09-02 08:54:56 [5218] [11] DEBUG: Thread 11 > >> (gw/bb_boxc.c:boxc_sender) maps to pid 5218. > >> 2009-09-02 08:54:56 [5218] [10] DEBUG: boxc_receiver: got boxc_id > >> <smsbox> from <127.0.0.1> > >> 2009-09-02 08:54:57 [5218] [6] DEBUG: AT2[modemSmsc]: --> AT^M > >> 2009-09-02 08:54:59 [5218] [5] INFO: Client connected from <127.0.0.1> > >> 2009-09-02 08:54:59 [5218] [5] DEBUG: Started thread 12 > >> (gw/bb_boxc.c:function) > >> 2009-09-02 08:54:59 [5218] [12] DEBUG: Thread 12 > >> (gw/bb_boxc.c:function) maps to pid 5218. > >> 2009-09-02 08:54:59 [5218] [12] DEBUG: Started thread 13 > >> (gw/bb_boxc.c:boxc_sender) > >> 2009-09-02 08:54:59 [5218] [13] DEBUG: Thread 13 > >> (gw/bb_boxc.c:boxc_sender) maps to pid 5218. > >> 2009-09-02 08:54:59 [5218] [12] DEBUG: boxc_receiver: got boxc_id > >> <smsbox> from <127.0.0.1> > >> 2009-09-02 08:55:02 [5218] [6] DEBUG: AT2[modemSmsc]: --> AT^M > >> 2009-09-02 08:55:06 [5218] [6] DEBUG: AT2[modemSmsc]: --> AT^M > >> 2009-09-02 08:55:10 [5218] [6] INFO: AT2[modemSmsc]: Closing device > >> 2009-09-02 08:55:10 [5218] [6] INFO: AT2[modemSmsc]: speed in modem > >> definition don't work, will autodetect > >> 2009-09-02 08:55:10 [5218] [6] DEBUG: AT2[modemSmsc]: detecting modem > >> speed. > >> 2009-09-02 08:55:10 [5218] [6] INFO: AT2[modemSmsc]: opening device > >> 2009-09-02 08:55:10 [5218] [6] DEBUG: AT2[modemSmsc]: device opened. > >> Telnet mode = 0 > >> 2009-09-02 08:55:10 [5218] [6] DEBUG: AT2[modemSmsc]: device opened > >> 2009-09-02 08:55:10 [5218] [6] INFO: AT2[modemSmsc]: speed set to 115200 > >> 2009-09-02 08:55:10 [5218] [6] DEBUG: AT2[modemSmsc]: --> ^M > >> 2009-09-02 08:55:12 [5218] [6] DEBUG: AT2[modemSmsc]: --> AT^M > >> 2009-09-02 08:55:18 [5218] [6] DEBUG: AT2[modemSmsc]: --> AT^M > >> 2009-09-02 08:55:22 [5218] [6] DEBUG: AT2[modemSmsc]: --> AT^M > >> 2009-09-02 08:55:26 [5218] [6] INFO: AT2[modemSmsc]: Closing device > >> 2009-09-02 08:55:26 [5218] [6] INFO: AT2[modemSmsc]: opening device > >> 2009-09-02 08:55:26 [5218] [6] DEBUG: AT2[modemSmsc]: device opened. > >> Telnet mode = 0 > >> 2009-09-02 08:55:26 [5218] [6] DEBUG: AT2[modemSmsc]: device opened > >> 2009-09-02 08:55:26 [5218] [6] INFO: AT2[modemSmsc]: speed set to 57600 > >> 2009-09-02 08:55:26 [5218] [6] DEBUG: AT2[modemSmsc]: --> ^M > >> 2009-09-02 08:55:29 [5218] [6] DEBUG: AT2[modemSmsc]: --> AT^M > >> 2009-09-02 08:55:35 [5218] [6] DEBUG: AT2[modemSmsc]: --> AT^M > >> 2009-09-02 08:55:39 [5218] [6] DEBUG: AT2[modemSmsc]: --> AT^M > >> 2009-09-02 08:55:43 [5218] [6] INFO: AT2[modemSmsc]: Closing device > >> 2009-09-02 08:55:43 [5218] [6] INFO: AT2[modemSmsc]: opening device > >> 2009-09-02 08:55:43 [5218] [6] DEBUG: AT2[modemSmsc]: device opened. > >> Telnet mode = 0 > >> 2009-09-02 08:55:43 [5218] [6] DEBUG: AT2[modemSmsc]: device opened > >> 2009-09-02 08:55:43 [5218] [6] INFO: AT2[modemSmsc]: speed set to 38400 > >> 2009-09-02 08:55:43 [5218] [6] DEBUG: AT2[modemSmsc]: --> ^M > >> 2009-09-02 08:55:45 [5218] [6] DEBUG: AT2[modemSmsc]: --> AT^M > >> 2009-09-02 08:55:51 [5218] [6] DEBUG: AT2[modemSmsc]: --> AT^M > >> 2009-09-02 08:55:55 [5218] [6] DEBUG: AT2[modemSmsc]: --> AT^M > >> 2009-09-02 08:55:59 [5218] [6] INFO: AT2[modemSmsc]: Closing device > >> 2009-09-02 08:55:59 [5218] [6] INFO: AT2[modemSmsc]: opening device > >> 2009-09-02 08:55:59 [5218] [6] DEBUG: AT2[modemSmsc]: device opened. > >> Telnet mode = 0 > >> 2009-09-02 08:55:59 [5218] [6] DEBUG: AT2[modemSmsc]: device opened > >> 2009-09-02 08:55:59 [5218] [6] INFO: AT2[modemSmsc]: speed set to 19200 > >> 2009-09-02 08:55:59 [5218] [6] DEBUG: AT2[modemSmsc]: --> ^M > >> 2009-09-02 08:56:01 [5218] [6] DEBUG: AT2[modemSmsc]: --> AT^M > >> 2009-09-02 08:56:07 [5218] [6] DEBUG: AT2[modemSmsc]: --> AT^M > >> 2009-09-02 08:56:11 [5218] [6] DEBUG: AT2[modemSmsc]: --> AT^M > >> 2009-09-02 08:56:15 [5218] [6] INFO: AT2[modemSmsc]: Closing device > >> 2009-09-02 08:56:15 [5218] [6] INFO: AT2[modemSmsc]: opening device > >> 2009-09-02 08:56:15 [5218] [6] DEBUG: AT2[modemSmsc]: device opened. > >> Telnet mode = 0 > >> 2009-09-02 08:56:15 [5218] [6] DEBUG: AT2[modemSmsc]: device opened > >> 2009-09-02 08:56:15 [5218] [6] INFO: AT2[modemSmsc]: speed set to 9600 > >> 2009-09-02 08:56:15 [5218] [6] DEBUG: AT2[modemSmsc]: --> ^M > >> 2009-09-02 08:56:17 [5218] [6] DEBUG: AT2[modemSmsc]: --> AT^M > >> 2009-09-02 08:56:23 [5218] [6] DEBUG: AT2[modemSmsc]: --> AT^M > >> 2009-09-02 08:56:27 [5218] [6] DEBUG: AT2[modemSmsc]: --> AT^M > >> 2009-09-02 08:56:32 [5218] [6] INFO: AT2[modemSmsc]: Closing device > >> 2009-09-02 08:56:32 [5218] [6] INFO: AT2[modemSmsc]: cannot detect speed > >> 2009-09-02 08:56:32 [5218] [6] ERROR: AT2[modemSmsc]: Couldn't connect > >> (retrying in 10 seconds). > >> 2009-09-02 08:56:41 [5218] [6] INFO: AT2[modemSmsc]: trying to use > >> speed <9600> from modem definition > >> 2009-09-02 08:56:41 [5218] [6] INFO: AT2[modemSmsc]: opening device > >> 2009-09-02 08:56:42 [5218] [6] DEBUG: AT2[modemSmsc]: device opened. > >> Telnet mode = 0 > >> 2009-09-02 08:56:42 [5218] [6] DEBUG: AT2[modemSmsc]: device opened > >> 2009-09-02 08:56:42 [5218] [6] INFO: AT2[modemSmsc]: speed set to 9600 > >> 2009-09-02 08:56:42 [5218] [6] DEBUG: AT2[modemSmsc]: --> ^M > >> 2009-09-02 08:56:46 [5218] [6] DEBUG: AT2[modemSmsc]: --> AT^M > >> 2009-09-02 08:56:52 [5218] [6] DEBUG: AT2[modemSmsc]: --> AT^M > >> 2009-09-02 08:56:56 [5218] [6] DEBUG: AT2[modemSmsc]: --> AT^M > >> 2009-09-02 08:57:00 [5218] [6] INFO: AT2[modemSmsc]: Closing device > >> 2009-09-02 08:57:00 [5218] [6] INFO: AT2[modemSmsc]: speed in modem > >> definition don't work, will autodetect > >> 2009-09-02 08:57:00 [5218] [6] DEBUG: AT2[modemSmsc]: detecting modem > >> speed. > >> 2009-09-02 08:57:00 [5218] [6] INFO: AT2[modemSmsc]: opening device > >> 2009-09-02 08:57:00 [5218] [6] DEBUG: AT2[modemSmsc]: device opened. > >> Telnet mode = 0 > >> 2009-09-02 08:57:00 [5218] [6] DEBUG: AT2[modemSmsc]: device opened > >> 2009-09-02 08:57:00 [5218] [6] INFO: AT2[modemSmsc]: speed set to 115200 > >> 2009-09-02 08:57:00 [5218] [6] DEBUG: AT2[modemSmsc]: --> ^M > >> 2009-09-02 08:57:02 [5218] [6] DEBUG: AT2[modemSmsc]: --> AT^M > >> 2009-09-02 08:57:08 [5218] [6] DEBUG: AT2[modemSmsc]: --> AT^M > >> 2009-09-02 08:57:12 [5218] [6] DEBUG: AT2[modemSmsc]: --> AT^M > >> 2009-09-02 08:57:16 [5218] [6] INFO: AT2[modemSmsc]: Closing device > >> 2009-09-02 08:57:16 [5218] [6] INFO: AT2[modemSmsc]: opening device > >> 2009-09-02 08:57:16 [5218] [6] DEBUG: AT2[modemSmsc]: device opened. > >> Telnet mode = 0 > >> 2009-09-02 08:57:16 [5218] [6] DEBUG: AT2[modemSmsc]: device opened > >> 2009-09-02 08:57:16 [5218] [6] INFO: AT2[modemSmsc]: speed set to 57600 > >> #################################################### > >> > > > > > > > > _______________________________________________ > users mailing list > users@kannel.org > http://www.kannel.org/mailman/listinfo/users > >
