Arne K. Haaje, Thanks for the suggestion Mr.Arne.
After doing some research for a particular healthy msisdn, I found that, this error is caused due to the inbox filled up, for that phone. +1 for, Kannel should have handled it differently. Because of the large outgoing queue, my bearerbox handles. I don't want these messages to be retried again and again. I want to try the patch you're using. Please post it to my email address as an attachment([EMAIL PROTECTED]). Appreciating your help. Surya ---------------------------------------------------------------------- Message: 1 Date: Thu, 4 Dec 2008 13:16:28 +0100 From: "Arne K. Haaje" <[EMAIL PROTECTED]> Subject: Re: users Digest, Vol 31, Issue 1 [PATCH] To: [email protected] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="iso-8859-15" It is correct that this is the queue at the SMSC that it is full, but I think Kannel should have handled it differently. We have this problem with the largest operator where I live. We have asked, but they *will not* change the behaviour. What happens is that the queue to a msisdn gets full. With this operator the limit is at 100 messages to be delivered to to the msisdn. This can easily occur with numbers becoming inactive, phones lost, automatic appliances losing power, and so on. Kannel treats "message queue full" as a temporary error, and will try the message again. If you have a large outgoing queue, then this will clog up the queue and create delays for the remaining messages. If the reason you are getting the "message queue full" error is one of the above, then it will not likely clear up anytime soon. So, you will continue to get delays for your remaining queue. I believe Kannel should treat "message queue full" as a permanent error, and reject the message that caused it. You will get a status 16 error if using delivery reports, and the remaining queue wont be delayed. It is ofcourse up to the developers if they want to change this, but I've included a tiny patch that works for us, and should fix the problem for Surya > Thursdag 04 desember 2008 00:45:29 wrote Nikos Balkanas: > This one is a keeper! > ----- Original Message ----- > From: Alejandro Guerrieri > To: Surya > Cc: [email protected] > Sent: Wednesday, December 03, 2008 6:53 PM > Subject: Re: users Digest, Vol 31, Issue 1 > > > It's the SMSC queue which is full, not Kannel's. > > Talk to your SMSC provider and report the error, they're the only ones > that can do something about it. > > Regards, > > Alejandro > > > On Wed, Dec 3, 2008 at 1:26 PM, Surya <[EMAIL PROTECTED]> wrote: > > Thanks for the response. > > > > "SMSC returned error code 0x00000014 (Message Queue Full) in response > to submit_sm." > > > > Is there a way to delete these messages? or any parameter in the > kannel-config file which prevents the retry? > > > > Your help is appreciated. > > Thanks and Regards, > > Surya > > > > > > > --------------------------------------------------------------------------- >- > > From: Alejandro Guerrieri [mailto:[EMAIL PROTECTED] > Sent: Monday, December 01, 2008 10:01 PM > To: Surya > Cc: [email protected] > Subject: Re: users Digest, Vol 31, Issue 1 > > > > Surya, > > As the userguide clearly verses: > > "Optional the maximum number of outstanding (i.e. acknowledged) SMPP > operations between an ESME and SMSC. This number is not specified > explicitly in the SMPP Protocol Specification and will be governed by the > SMPP implementation on the SMSC. As a guideline it is recommended that no > more than 10 (default) SMPP messages are outstanding at any time." > > This means that kannel will open up to max-pending-submits messages > without waiting for a response. > > Regards, > > Alejandro > > On Mon, Dec 1, 2008 at 1:59 PM, Surya <[EMAIL PROTECTED]> wrote: > > > Thanks Alejandro, > > > What exactly does max-pending-submits? > Lets say, if max-pending-submits = 50, what will happen? > > Does it push 50 messages to the Bearerbox or > Does it push 50 messages to the SMSC > > After pushing how much time Does it wait for? And what will happen in > that time? > > Whats the role of throughput in this.. > > Sorry too many questions.. what to do perplexed mind try to understand. > Thanks in advance. > > Regards, > Surya > -----Original Message----- > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 30 Nov 2008 16:37:35 -0200 > From: "Alejandro Guerrieri" <[EMAIL PROTECTED]> > Subject: Re: get mesage ID without DLR > To: Surya <[EMAIL PROTECTED]>, "[email protected]" <[email protected]> > Message-ID: > <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="windows-1252" > > Surya, > > [This is only relevant to SMPP links, other SMSC's may have different > behaviour] > > If the messages are already queued, there's not too much you can do > about it: default kannel's priority is 0 (maximum) so you won't be able to > prioritize anything. > > You can improve things a little in the future by setting the priority > to a higher number for regular messages (valid values are 0 to 4, being 0 > the highest priority and 4 the lowest). For example, you could set 2 as > default, and then use 0 or 1 when you want to speed things. > > Regarding your throughput, that "10" figure is a limit imposed by the > SMSC I suppose. If not, you could play with some tweaking of the > "throughput" and "max-pending-submits" parameters and see if you can get a > better performance. > > Regards, > > Alejandro > > On Sun, Nov 30, 2008 at 3:47 PM, Surya <[EMAIL PROTECTED]> wrote: > > Hi Alejandro, > > > > > > > > Message_id for billing, I actually mean that after successful > > delivery of the message we can initiate the billing module?some kind > > of it. > > > > > > > > %F would be the new parameter for the message_id, I guess. Hope Alex > > Malyish completed his part. > > > > > > > > I have a big problem of the kannel queue, I can thousands of > > messages are in the store file, > > > > Current throughput is 10. How do I set priority to the message to be > > sent immediately. > > > > > > > > Can you share your experience on the kannel internal queue, as I just > > went through this page. > > > > http://www.mail-archive.com/[email protected]/msg10857.html > > > > > > > > I know its different from the priority optional parameter of the > > SMPP. > > > > > > > > And also how to the priority of the deliver_sm of the DLR message? > > Any idea. > > > > > > > > > > > > Thanks in advance, > > > > Surya > > > > > > ------------------------------ > > > > *From:* Alejandro Guerrieri [mailto:[EMAIL PROTECTED] > > *Sent:* Friday, November 28, 2008 11:18 PM > > > > *To:* Surya > > *Subject:* Re: get mesage ID without DLR > > > > > > > > Surya, > > > > Yes, seems like everybody's using message_id for billing nowadays ;) > > > > Alex Malyish proposed a few tweaks that makes a lot of sens, will > > copy to you as well when those changes are made. > > > > Regards, > > > > Alejandro > > > > On Fri, Nov 28, 2008 at 3:40 PM, Surya <[EMAIL PROTECTED]> wrote: > > > > Kudos!!! > > > > > > > > I believe you finally made it!! > > > > Many users face this problem of message id which is very critical for > > all the billing purpose.. > > > > Not only billing, we can also play with the messages, specially when > > using SMPP.(Query, Cancel, Replace). > > > > > > > > Small request, I don't know the status of my subscription to devel > > list, can you send me the patch. > > > > If they are updating the patch immediately, I'll be the first one to > > use it. > > > > I have windows system which has internet, how to get the CVS check > > out, > > I'm > > > trying to get the Tortoise CVS tool. > > > > > > > > Thanks and Regards, > > > > Surya > > > > > > ------------------------------ > > > > *From:* Alejandro Guerrieri [mailto:[EMAIL PROTECTED] > > *Sent:* Friday, November 28, 2008 9:53 PM > > > > > > *To:* Surya > > *Subject:* Re: get mesage ID without DLR > > > > > > > > Surya, > > > > The patch was posted to devel a few hours ago, though it will still > > suffer a few changes before being commited. > > > > Regards, > > > > Alejandro > > > > On Fri, Nov 28, 2008 at 4:30 AM, Surya <[EMAIL PROTECTED]> wrote: > > > > Hi Alex, > > > > > > > > Sorry, I don't mind waiting a day? work pressure sometimes wants > > things to happen right now. > > > > > > > > Which parameter replaced %w. > > > > > > > > I also subscribed to the devel list. > > > > > > > > Thanks & Regards > > > > Surya > > > > > > > > > > ------------------------------ > > > > *From:* Alejandro Guerrieri [mailto:[EMAIL PROTECTED] > > *Sent:* Friday, November 28, 2008 12:22 AM > > *To:* Surya > > *Subject:* Re: get mesage ID without DLR > > > > > > > > Surya, > > > > Will post the patch to the devel list when it's ready. To subscribe > > to the list: http://www.kannel.org/lists.shtml > > > > The %w patch is a deprecated version of what I'm doing now. The new > > patch will be quite similar, though the sms structure will differ. If > > you can > > wait > > > one more day I'd recommend you to wait for the new patch to be > > available. > > > > Regards, > > > > Alex > > > > On Thu, Nov 27, 2008 at 4:05 PM, Surya <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > > > > > Can you forward the patch to me.. I'll try with %w > > > > > > > > I was going thorough this > > http://www.mail-archive.com/[email protected]/msg13407.html > > > > > > > > How to subscribe to the Devel List ? > > > > > > > > Thanks and Regards, > > > > Surya > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > http://www.kannel.org/pipermail/users/attachments/20081130/c212c028/attachm >e nt-0001.html > > ------------------------------ > > _______________________________________________ > users mailing list > [email protected] > http://www.kannel.org/mailman/listinfo/users > > > End of users Digest, Vol 31, Issue 1 > ************************************ -- -------------------------------- Arne K. Haaje | www.drx.no T: 69 51 15 52 | M: 92 88 44 66 -------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: msgqful.diff Type: text/x-patch Size: 353 bytes Desc: not available Url : http://www.kannel.org/pipermail/users/attachments/20081204/cc781f49/attachme nt-0001.bin ------------------------------ Message: 2 Date: Thu, 4 Dec 2008 19:04:32 +0530 From: "Kaliya perumal" <[EMAIL PROTECTED]> Subject: Hi to all To: [email protected] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="iso-8859-1" <[email protected]>Hi I have installed kannel on windows xp ,then i run the bearebox its executed perfectly,after that i am running smsbox its not executed properly,Its shows some error ,i dont know how to rectify it,so that i paste my kannel.config here group = core admin-port = 13000 admin-password = foobar smsbox-port = 13003 admin-deny-ip = "" admin-allow-ip = "127.0.0.1, 11.11.11.11" smsbox-port = 13003 box-deny-ip = "" box-allow-ip = "127.0.0.1,11.11.11.11" wdp-interface-name = "" log-file = "C:/cygwin/var/log/kannel_bearerbox.txt" log-level = 0 group = smsc smsc = smpp log-level = 0 interface-version = 33 host = xxx.xxx.xx.xxx <http://216.121.82.190:0/9001:dev:> receive-port = 9001 smsc-username = xxx smsc-password =xxx system-type = "" address-range = "" transceiver-mode = true source-addr-ton = 0 source-addr-npi = 1 dest-addr-ton = 1 dest-addr-npi = 1 group = smsbox bearerbox-host = 127.0.0.1 sendsms-port = 13131 sendsms-chars = "0123456789+#" access-log = "C:/cygwin/tmp/access.log" log-file = "C:/cygwin/var/log/kannel_bearerbox1.txt" log-level = 0 group = sms-service keyword = keyword-regex = .* catch-all = yes max-messages = 0 get-url = "http://localhost:13000/contrib/sendsms ?username=tester&password=foobar&to=919986131642&text=su" group = sms-service keyword = default text = "No service specified" *then i run the bearerbox * $ ./bearerbox Friday_kannel_tem.conf 2008-12-04 17:26:00 [3524] [0] INFO: Debug_lvl = -1, log_file = <none>, log_lvl = 0 2008-12-04 17:26:00 [3524] [0] WARNING: DLR: using default 'internal' for storage type. 2008-12-04 17:26:00 [3524] [0] INFO: DLR using storage type: internal 2008-12-04 17:26:00 [3524] [0] DEBUG: Kannel bearerbox version `1.4.1'. Build `Nov 25 2008 11:57:49', compiler `3.4.4 (cygming special, gdc 0.12, using dmd 0.125)'. System CYGWIN_NT-5.1, release 1.5.25(0.156/4/2), version 2008-06-12 19:34, machine i686. Hostname Sys1, IP xxx.xxx.x.xx <http://192.168.1.36/>. Libxml version 2.7.2. Using OpenSSL 0.9.8i 15 Sep 2008. Using native malloc. 2008-12-04 17:26:00 [3524] [0] INFO: Added logfile `C:/cygwin/var/log/kannel_bearerbox.txt' with leve `3'. 2008-12-04 17:26:00 [3524] [0] INFO: HTTP: Opening server at port 13000. 2008-12-04 17:26:00 [3524] [1] DEBUG: Thread 1 (gwlib/fdset.c:poller) maps to pid 3524. 2008-12-04 17:26:00 [3524] [0] DEBUG: Started thread 1 (gwlib/fdset.c:poller) 2008-12-04 17:26:00 [3524] [2] DEBUG: Thread 2 (gwlib/http.c:server_thread) maps to pid 3524. 2008-12-04 17:26:00 [3524] [0] DEBUG: Started thread 2 (gwlib/http.c:server_thread) 2008-12-04 17:26:00 [3524] [3] DEBUG: Thread 3 (gw/bb_http.c:httpadmin_run) maps to pid 3524. 2008-12-04 17:26:00 [3524] [0] DEBUG: Started thread 3 (gw/bb_http.c:httpadmin_run) 2008-12-04 17:26:00 [3524] [0] DEBUG: starting smsbox connection module 2008-12-04 17:26:00 [3524] [0] INFO: BOXC: 'smsbox-max-pending' not set, using default (100). 2008-12-04 17:26:00 [3524] [4] DEBUG: Thread 4 (gw/bb_boxc.c:sms_to_smsboxes) maps to pid 3524. 2008-12-04 17:26:00 [3524] [0] DEBUG: Started thread 4 (gw/bb_boxc.c:sms_to_smsboxes) 2008-12-04 17:26:00 [3524] [5] DEBUG: Thread 5 (gw/bb_boxc.c:smsboxc_run) maps to pid 3524. 2008-12-04 17:26:00 [3524] [0] DEBUG: Started thread 5 (gw/bb_boxc.c:smsboxc_run) 2008-12-04 17:26:00 [3524] [0] INFO: Set SMS resend frequency to 60 seconds. 2008-12-04 17:26:00 [3524] [0] INFO: SMS resend retry set to unlimited. 2008-12-04 17:26:00 [3524] [0] INFO: DLR rerouting for smsc id <(null)> disabled. 2008-12-04 17:26:00 [3524] [6] DEBUG: Thread 6 (gw/smsc/smsc_smpp.c:io_thread) maps to pid 3524. 2008-12-04 17:26:00 [3524] [0] DEBUG: Started thread 6 (gw/smsc/smsc_smpp.c:io_thread) 2008-12-04 17:26:00 [3524] [7] DEBUG: Thread 7 (gw/bb_smscconn.c:sms_router) maps to pid 3524. 2008-12-04 17:26:00 [3524] [0] DEBUG: Started thread 7 (gw/bb_smscconn.c:sms_router) 2008-12-04 17:26:00 [3524] [7] DEBUG: sms_router: time to sleep 30.00 secs. 2008-12-04 17:26:00 [3524] [0] INFO: ---------------------------------------- 2008-12-04 17:26:00 [3524] [0] INFO: Kannel bearerbox II version 1.4.1 starting 2008-12-04 17:26:00 [3524] [0] INFO: MAIN: Start-up done, entering mainloop 2008-12-04 17:26:00 [3524] [7] DEBUG: sms_router: gwlist_len = 0 2008-12-04 17:26:01 [3524] [6] DEBUG: SMPP[SMPP:xxx.xxx.xx.190:0/9001:dev<http://216.121.82.190:0/9001:dev:> : <http://216.121.82.190:0/9001:dev:>]: Sending PDU: 2008-12-04 17:26:01 [3524] [6] DEBUG: SMPP PDU 0x9799b8 dump: 2008-12-04 17:26:01 [3524] [6] DEBUG: type_name: bind_receiver 2008-12-04 17:26:01 [3524] [6] DEBUG: command_id: 1 = 0x00000001 2008-12-04 17:26:01 [3524] [6] DEBUG: command_status: 0 = 0x00000000 2008-12-04 17:26:01 [3524] [6] DEBUG: sequence_number: 1 = 0x00000001 2008-12-04 17:26:01 [3524] [6] DEBUG: system_id: "dev" 2008-12-04 17:26:01 [3524] [6] DEBUG: password: "dev" 2008-12-04 17:26:01 [3524] [6] DEBUG: system_type: "" 2008-12-04 17:26:01 [3524] [6] DEBUG: interface_version: 51 = 0x00000033 2008-12-04 17:26:01 [3524] [6] DEBUG: addr_ton: 0 = 0x00000000 2008-12-04 17:26:01 [3524] [6] DEBUG: addr_npi: 0 = 0x00000000 2008-12-04 17:26:01 [3524] [6] DEBUG: address_range: "" 2008-12-04 17:26:01 [3524] [6] DEBUG: SMPP PDU dump ends. 2008-12-04 17:26:01 [3524] [6] DEBUG: SMPP[SMPP:xxx.xxx.xx.190:0/9001:dev<http://216.121.82.190:0/9001:dev:> : <http://216.121.82.190:0/9001:dev:>]: Got PDU: 2008-12-04 17:26:01 [3524] [6] DEBUG: SMPP PDU 0x97a368 dump: 2008-12-04 17:26:01 [3524] [6] DEBUG: type_name: bind_receiver_resp 2008-12-04 17:26:01 [3524] [6] DEBUG: command_id: 2147483649 = 0x80000001 2008-12-04 17:26:01 [3524] [6] DEBUG: command_status: 0 = 0x00000000 2008-12-04 17:26:01 [3524] [6] DEBUG: sequence_number: 1 = 0x00000001 2008-12-04 17:26:01 [3524] [6] DEBUG: system_id: "NowSMS" 2008-12-04 17:26:01 [3524] [6] DEBUG: SMPP PDU dump ends. 2008-12-04 17:26:04 [3524] [5] INFO: Client connected from <127.0.0.1> 2008-12-04 17:26:04 [3524] [8] DEBUG: Thread 8 (gw/bb_boxc.c:function) maps to pid 3524. 2008-12-04 17:26:04 [3524] [5] DEBUG: Started thread 8 (gw/bb_boxc.c:function) 2008-12-04 17:26:04 [3524] [9] DEBUG: Thread 9 (gw/bb_boxc.c:boxc_sender) maps to pid 3524. 2008-12-04 17:26:04 [3524] [8] DEBUG: Started thread 9 (gw/bb_boxc.c:boxc_sender) 2008-12-04 17:26:31 [3524] [6] DEBUG: SMPP[SMPP:xxx.xxx.xx.190:0/9001:dev<http://216.121.82.190:0/9001:dev:> : <http://216.121.82.190:0/9001:dev:>]: Sending enquire link: 2008-12-04 17:26:31 [3524] [6] DEBUG: SMPP PDU 0x97e420 dump: 2008-12-04 17:26:31 [3524] [6] DEBUG: type_name: enquire_link 2008-12-04 17:26:31 [3524] [6] DEBUG: command_id: 21 = 0x00000015 2008-12-04 17:26:31 [3524] [6] DEBUG: command_status: 0 = 0x00000000 2008-12-04 17:26:31 [3524] [6] DEBUG: sequence_number: 2 = 0x00000002 2008-12-04 17:26:31 [3524] [6] DEBUG: SMPP PDU dump ends. 2008-12-04 17:26:31 [3524] [6] DEBUG: SMPP[SMPP:xxx.xxx.xx.190:0/9001:dev<http://216.121.82.190:0/9001:dev:> : <http://216.121.82.190:0/9001:dev:>]: Got PDU: 2008-12-04 17:26:31 [3524] [6] DEBUG: SMPP PDU 0x97e450 dump: 2008-12-04 17:26:31 [3524] [6] DEBUG: type_name: enquire_link_resp 2008-12-04 17:26:31 [3524] [6] DEBUG: command_id: 2147483669 = 0x80000015 2008-12-04 17:26:31 [3524] [6] DEBUG: command_status: 0 = 0x00000000 2008-12-04 17:26:31 [3524] [6] DEBUG: sequence_number: 2 = 0x00000002 2008-12-04 17:26:31 [3524] [6] DEBUG: SMPP PDU dump ends. 2008-12-04 17:27:01 [3524] [6] DEBUG: SMPP[SMPP:xxx.xxx.xx.190:0/9001:dev<http://216.121.82.190:0/9001:dev:> : <http://216.121.82.190:0/9001:dev:>: <http://216.121.82.190:0/9001:dev:>]: Sending enquire link: 2008-12-04 17:27:01 [3524] [6] DEBUG: SMPP PDU 0x97e4b0 dump: 2008-12-04 17:27:01 [3524] [6] DEBUG: type_name: enquire_link 2008-12-04 17:27:01 [3524] [6] DEBUG: command_id: 21 = 0x00000015 2008-12-04 17:27:01 [3524] [6] DEBUG: command_status: 0 = 0x00000000 2008-12-04 17:27:01 [3524] [6] DEBUG: sequence_number: 3 = 0x00000003 2008-12-04 17:27:01 [3524] [6] DEBUG: SMPP PDU dump ends. 2008-12-04 17:27:02 [3524] [6] DEBUG: SMPP[SMPP:xxx.xxx.xx.190:0/9001:dev<http://216.121.82.190:0/9001:dev:> : <http://216.121.82.190:0/9001:dev:>]: Got PDU: 2008-12-04 17:27:02 [3524] [6] DEBUG: SMPP PDU 0x97e4e0 dump: 2008-12-04 17:27:02 [3524] [6] DEBUG: type_name: enquire_link_resp 2008-12-04 17:27:02 [3524] [6] DEBUG: command_id: 2147483669 = 0x80000015 2008-12-04 17:27:02 [3524] [6] DEBUG: command_status: 0 = 0x00000000 2008-12-04 17:27:02 [3524] [6] DEBUG: sequence_number: 3 = 0x00000003 2008-12-04 17:27:02 [3524] [6] DEBUG: SMPP PDU dump ends. 2008-12-04 17:27:31 [3524] [6] DEBUG: SMPP[SMPP:xxx.xxx.xx.190:0/9001:dev<http://216.121.82.190:0/9001:dev:> : <http://216.121.82.190:0/9001:dev:>]: Sending enquire link: 2008-12-04 17:27:31 [3524] [6] DEBUG: SMPP PDU 0x97e4b0 dump: 2008-12-04 17:27:31 [3524] [6] DEBUG: type_name: enquire_link 2008-12-04 17:27:31 [3524] [6] DEBUG: command_id: 21 = 0x00000015 2008-12-04 17:27:31 [3524] [6] DEBUG: command_status: 0 = 0x00000000 2008-12-04 17:27:31 [3524] [6] DEBUG: sequence_number: 4 = 0x00000004 2008-12-04 17:27:31 [3524] [6] DEBUG: SMPP PDU dump ends. 2008-12-04 17:27:31 [3524] [6] DEBUG: SMPP[SMPP:xxx.xxx.xx.190:0/9001:dev<http://216.121.82.190:0/9001:dev:> : <http://216.121.82.190:0/9001:dev:>: <http://216.121.82.190:0/9001:dev:>]: Got PDU: 2008-12-04 17:27:31 [3524] [6] DEBUG: SMPP PDU 0x97e4e0 dump: 2008-12-04 17:27:31 [3524] [6] DEBUG: type_name: enquire_link_resp 2008-12-04 17:27:31 [3524] [6] DEBUG: command_id: 2147483669 = 0x80000015 2008-12-04 17:27:31 [3524] [6] DEBUG: command_status: 0 = 0x00000000 2008-12-04 17:27:31 [3524] [6] DEBUG: sequence_number: 4 = 0x00000004 2008-12-04 17:27:31 [3524] [6] DEBUG: SMPP PDU dump ends. 2008-12-04 17:28:01 [3524] [6] DEBUG: SMPP[SMPP:xxx.xxx.xx.190:0/9001:dev<http://216.121.82.190:0/9001:dev:> : <http://216.121.82.190:0/9001:dev:>]: Sending enquire link: 2008-12-04 17:28:01 [3524] [6] DEBUG: SMPP PDU 0x97e540 dump: 2008-12-04 17:28:01 [3524] [6] DEBUG: type_name: enquire_link 2008-12-04 17:28:01 [3524] [6] DEBUG: command_id: 21 = 0x00000015 2008-12-04 17:28:01 [3524] [6] DEBUG: command_status: 0 = 0x00000000 2008-12-04 17:28:01 [3524] [6] DEBUG: sequence_number: 5 = 0x00000005 2008-12-04 17:28:01 [3524] [6] DEBUG: SMPP PDU dump ends. 2008-12-04 17:28:01 [3524] [6] DEBUG: SMPP[SMPP:xxx.xxx.xx.190:0/9001:dev<http://216.121.82.190:0/9001:dev:> : <http://216.121.82.190:0/9001:dev:>: <http://216.121.82.190:0/9001:dev:>]: Got PDU: 2008-12-04 17:28:01 [3524] [6] DEBUG: SMPP PDU 0x97e570 dump: 2008-12-04 17:28:01 [3524] [6] DEBUG: type_name: enquire_link_resp 2008-12-04 17:28:01 [3524] [6] DEBUG: command_id: 2147483669 = 0x80000015 2008-12-04 17:28:01 [3524] [6] DEBUG: command_status: 0 = 0x00000000 2008-12-04 17:28:01 [3524] [6] DEBUG: sequence_number: 5 = 0x00000005 2008-12-04 17:28:01 [3524] [6] DEBUG: SMPP PDU dump ends. 2008-12-04 17:28:31 [3524] [6] DEBUG: SMPP[SMPP:xxx.xxx.xx.190:0/9001:dev<http://216.121.82.190:0/9001:dev:> : <http://216.121.82.190:0/9001:dev:>]: Sending enquire link: 2008-12-04 17:28:31 [3524] [6] DEBUG: SMPP PDU 0x97e540 dump: 2008-12-04 17:28:31 [3524] [6] DEBUG: type_name: enquire_link 2008-12-04 17:28:31 [3524] [6] DEBUG: command_id: 21 = 0x00000015 2008-12-04 17:28:31 [3524] [6] DEBUG: command_status: 0 = 0x00000000 2008-12-04 17:28:31 [3524] [6] DEBUG: sequence_number: 6 = 0x00000006 2008-12-04 17:28:31 [3524] [6] DEBUG: SMPP PDU dump ends. 2008-12-04 17:28:31 [3524] [6] DEBUG: SMPP[SMPPxxx.xxx.xx.190:0/9001:dev<http://216.121.82.190:0/9001:dev:> : <http://216.121.82.190:0/9001:dev:>]: Got PDU: 2008-12-04 17:28:31 [3524] [6] DEBUG: SMPP PDU 0x97e570 dump: 2008-12-04 17:28:31 [3524] [6] DEBUG: type_name: enquire_link_resp 2008-12-04 17:28:31 [3524] [6] DEBUG: command_id: 2147483669 = 0x80000015 2008-12-04 17:28:31 [3524] [6] DEBUG: command_status: 0 = 0x00000000 2008-12-04 17:28:31 [3524] [6] DEBUG: sequence_number: 6 = 0x00000006 2008-12-04 17:28:31 [3524] [6] DEBUG: SMPP PDU dump ends. 2008-12-04 17:29:01 [3524] [6] DEBUG: SMPP[SMPP:xxx.xxx.xx.190:0/9001:dev<http://216.121.82.190:0/9001:dev:> : <http://216.121.82.190:0/9001:dev:>]: Sending enquire link: 2008-12-04 17:29:01 [3524] [6] DEBUG: SMPP PDU 0x97e5d0 dump: 2008-12-04 17:29:01 [3524] [6] DEBUG: type_name: enquire_link 2008-12-04 17:29:01 [3524] [6] DEBUG: command_id: 21 = 0x00000015 2008-12-04 17:29:01 [3524] [6] DEBUG: command_status: 0 = 0x00000000 2008-12-04 17:29:01 [3524] [6] DEBUG: sequence_number: 7 = 0x00000007 2008-12-04 17:29:01 [3524] [6] DEBUG: SMPP PDU dump ends. 2008-12-04 17:29:02 [3524] [6] DEBUG: SMPP[SMPP:xxx.xxx.xx.190:0/9001:dev<http://216.121.82.190:0/9001:dev:> : <http://216.121.82.190:0/9001:dev:>]: Got PDU: 2008-12-04 17:29:02 [3524] [6] DEBUG: SMPP PDU 0x97e600 dump: 2008-12-04 17:29:02 [3524] [6] DEBUG: type_name: enquire_link_resp 2008-12-04 17:29:02 [3524] [6] DEBUG: command_id: 2147483669 = 0x80000015 2008-12-04 17:29:02 [3524] [6] DEBUG: command_status: 0 = 0x00000000 2008-12-04 17:29:02 [3524] [6] DEBUG: sequence_number: 7 = 0x00000007 2008-12-04 17:29:02 [3524] [6] DEBUG: SMPP PDU dump ends. 2008-12-04 17:29:31 [3524] [6] DEBUG: SMPP[SMPP:xxx.xxx.xx.190:0/9001:dev<http://216.121.82.190:0/9001:dev:> : <http://216.121.82.190:0/9001:dev:>: <http://216.121.82.190:0/9001:dev:>]: Sending enquire link: 2008-12-04 17:29:31 [3524] [6] DEBUG: SMPP PDU 0x97e5d0 dump: 2008-12-04 17:29:31 [3524] [6] DEBUG: type_name: enquire_link 2008-12-04 17:29:31 [3524] [6] DEBUG: command_id: 21 = 0x00000015 2008-12-04 17:29:31 [3524] [6] DEBUG: command_status: 0 = 0x00000000 2008-12-04 17:29:31 [3524] [6] DEBUG: sequence_number: 8 = 0x00000008 2008-12-04 17:29:31 [3524] [6] DEBUG: SMPP PDU dump ends. 2008-12-04 17:29:31 [3524] [6] DEBUG: SMPP[SMPP:xxx.xxx.xx.190:0/9001:dev<http://216.121.82.190:0/9001:dev:> : <http://216.121.82.190:0/9001:dev:>]: Got PDU: 2008-12-04 17:29:31 [3524] [6] DEBUG: SMPP PDU 0x97e600 dump: 2008-12-04 17:29:31 [3524] [6] DEBUG: type_name: enquire_link_resp 2008-12-04 17:29:31 [3524] [6] DEBUG: command_id: 2147483669 = 0x80000015 2008-12-04 17:29:31 [3524] [6] DEBUG: command_status: 0 = 0x00000000 2008-12-04 17:29:31 [3524] [6] DEBUG: sequence_number: 8 = 0x00000008 2008-12-04 17:29:31 [3524] [6] DEBUG: SMPP PDU dump ends. 2008-12-04 17:30:01 [3524] [6] DEBUG: SMPP[SMPP:xxx.xxx.xx.190:0/9001:dev<http://216.121.82.190:0/9001:dev:> : <http://216.121.82.190:0/9001:dev:>]: Sending enquire link: 2008-12-04 17:30:01 [3524] [6] DEBUG: SMPP PDU 0x97e660 dump: 2008-12-04 17:30:01 [3524] [6] DEBUG: type_name: enquire_link 2008-12-04 17:30:01 [3524] [6] DEBUG: command_id: 21 = 0x00000015 2008-12-04 17:30:01 [3524] [6] DEBUG: command_status: 0 = 0x00000000 2008-12-04 17:30:01 [3524] [6] DEBUG: sequence_number: 9 = 0x00000009 2008-12-04 17:30:01 [3524] [6] DEBUG: SMPP PDU dump ends. 2008-12-04 17:30:01 [3524] [6] DEBUG: SMPP[SMPP:xxx.xxx.xx.190:0/9001:dev<http://216.121.82.190:0/9001:dev:> : <http://216.121.82.190:0/9001:dev:>]: Got PDU: 2008-12-04 17:30:01 [3524] [6] DEBUG: SMPP PDU 0x97e690 dump: 2008-12-04 17:30:01 [3524] [6] DEBUG: type_name: enquire_link_resp 2008-12-04 17:30:01 [3524] [6] DEBUG: command_id: 2147483669 = 0x80000015 2008-12-04 17:30:01 [3524] [6] DEBUG: command_status: 0 = 0x00000000 2008-12-04 17:30:01 [3524] [6] DEBUG: sequence_number: 9 = 0x00000009 2008-12-04 17:30:01 [3524] [6] DEBUG: SMPP PDU dump ends. 2008-12-04 17:30:31 [3524] [6] DEBUG: SMPP[SMPP:xxx.xxx.xx.190:0/9001:dev:<http://216.121.82.190:0/9001:dev:>]: Sending enquire link: 2008-12-04 17:30:31 [3524] [6] DEBUG: SMPP PDU 0x97e660 dump: 2008-12-04 17:30:31 [3524] [6] DEBUG: type_name: enquire_link 2008-12-04 17:30:31 [3524] [6] DEBUG: command_id: 21 = 0x00000015 2008-12-04 17:30:31 [3524] [6] DEBUG: command_status: 0 = 0x00000000 2008-12-04 17:30:31 [3524] [6] DEBUG: sequence_number: 10 = 0x0000000a 2008-12-04 17:30:31 [3524] [6] DEBUG: SMPP PDU dump ends. 2008-12-04 17:30:31 [3524] [6] DEBUG: SMPP[SMPP:xxx.xxx.xx.190:0/9001:dev<http://216.121.82.190:0/9001:dev:> : <http://216.121.82.190:0/9001:dev:>]: Got PDU: 2008-12-04 17:30:31 [3524] [6] DEBUG: SMPP PDU 0x97e690 dump: 2008-12-04 17:30:31 [3524] [6] DEBUG: type_name: enquire_link_resp 2008-12-04 17:30:31 [3524] [6] DEBUG: command_id: 2147483669 = 0x80000015 2008-12-04 17:30:31 [3524] [6] DEBUG: command_status: 0 = 0x00000000 2008-12-04 17:30:31 [3524] [6] DEBUG: sequence_number: 10 = 0x0000000a 2008-12-04 17:30:31 [3524] [6] DEBUG: SMPP PDU dump ends. After i am running my smsbox $ ./smsbox Friday_kannel_tem.conf 2008-12-04 17:26:04 [1968] [0] INFO: Debug_lvl = -1, log_file = <none>, log_lvl = 0 2008-12-04 17:26:04 [1968] [0] DEBUG: Kannel smsbox version `1.4.1'. Build `Nov 25 2008 11:57:49', compiler `3.4.4 (cygming special, gdc 0.12, using dmd 0.125)'. System CYGWIN_NT-5.1, release 1.5.25(0.156/4/2), version 2008-06-12 19:34, machine i686. Hostname Sys1, IP xxx.xxx.1.xx <http://192.168.1.36/>. Libxml version 2.7.2. Using OpenSSL 0.9.8i 15 Sep 2008. Using native malloc. 2008-12-04 17:26:04 [1968] [0] INFO: Starting to log to file C:/cygwin/var/log/kannel_bearerbox1.txt l evel 0 2008-12-04 17:26:04 [1968] [0] INFO: Added logfile `C:/cygwin/var/log/kannel_bearerbox1.txt' with leve l `0'. 2008-12-04 17:26:04 [1968] [0] INFO: Logging accesses to 'C:/cygwin/tmp/access.log'. 2008-12-04 17:26:04 [1968] [0] INFO: Started access logfile `C:/cygwin/tmp/access.log'. 2008-12-04 17:26:04 [1968] [0] INFO: HTTP: Opening server at port 13131. 2008-12-04 17:26:04 [1968] [1] DEBUG: Thread 1 (gwlib/fdset.c:poller) maps to pid 1968. 2008-12-04 17:26:04 [1968] [0] DEBUG: Started thread 1 (gwlib/fdset.c:poller) 2008-12-04 17:26:04 [1968] [2] DEBUG: Thread 2 (gwlib/http.c:server_thread) maps to pid 1968. 2008-12-04 17:26:04 [1968] [0] DEBUG: Started thread 2 (gwlib/http.c:server_thread) 2008-12-04 17:26:04 [1968] [0] INFO: Set up send sms service at port 13131 2008-12-04 17:26:04 [1968] [3] DEBUG: Thread 3 (gw/smsbox.c:sendsms_thread) maps to pid 1968. 2008-12-04 17:26:04 [1968] [0] DEBUG: Started thread 3 (gw/smsbox.c:sendsms_thread) 2008-12-04 17:26:04 [1968] [0] DEBUG: ---------------------------------------------- 2008-12-04 17:26:04 [1968] [0] DEBUG: Kannel smsbox version 1.4.1 starting 2008-12-04 17:26:04 [1968] [4] DEBUG: Thread 4 (gw/smsbox.c:obey_request_thread) maps to pid 1968. 2008-12-04 17:26:04 [1968] [0] DEBUG: Started thread 4 (gw/smsbox.c:obey_request_thread) 2008-12-04 17:26:04 [1968] [5] DEBUG: Thread 5 (gw/smsbox.c:url_result_thread) maps to pid 1968. 2008-12-04 17:26:04 [1968] [0] DEBUG: Started thread 5 (gw/smsbox.c:url_result_thread) 2008-12-04 17:26:04 [1968] [6] DEBUG: Thread 6 (gw/smsbox.c:http_queue_thread) maps to pid 1968. 2008-12-04 17:26:04 [1968] [0] DEBUG: Started thread 6 (gw/smsbox.c:http_queue_thread) 2008-12-04 17:26:04 [1968] [0] INFO: Connected to bearerbox at 127.0.0.1port 13003. 2008-12-04 17:26:04 [1968] [7] DEBUG: Thread 7 (gw/heartbeat.c:heartbeat_thread) maps to pid 1968. 2008-12-04 17:26:04 [1968] [0] DEBUG: Started thread 7 (gw/heartbeat.c:heartbeat_thread) 2008-12-04 17:31:01 [1968] [0] ERROR: Error reading from fd 21: 2008-12-04 17:31:01 [1968] [0] ERROR: System error 104: Connection reset by peer 2008-12-04 17:31:01 [1968] [0] ERROR: Connection to bearerbox broke. 2008-12-04 17:31:01 [1968] [0] INFO: Received (and handled?) 0 requests in 297 seconds (0.00 per secon d) 2008-12-04 17:31:01 [1968] [0] INFO: Kannel smsbox terminating. 2008-12-04 17:31:01 [1968] [7] ERROR: Error writing 12 octets to fd 21: 2008-12-04 17:31:01 [1968] [7] ERROR: System error 104: Connection reset by peer 2008-12-04 17:31:01 [1968] [7] ERROR: Couldn't write Msg to bearerbox. 2008-12-04 17:31:01 [1968] [7] DEBUG: Thread 7 (gw/heartbeat.c:heartbeat_thread) terminates. 2008-12-04 17:31:01 [1968] [0] DEBUG: Waiting for 2 (gwlib/http.c:server_thread) to terminate 2008-12-04 17:31:01 [1968] [3] DEBUG: HTTP: No clients with requests, quitting. 2008-12-04 17:31:01 [1968] [2] DEBUG: Thread 2 (gwlib/http.c:server_thread) terminates. 2008-12-04 17:31:01 [1968] [3] DEBUG: Thread 3 (gw/smsbox.c:sendsms_thread) terminates. 2008-12-04 17:31:01 [1968] [1] DEBUG: Thread 1 (gwlib/fdset.c:poller) terminates. 2008-12-04 17:31:01 [1968] [4] DEBUG: Thread 4 (gw/smsbox.c:obey_request_thread) terminates. 2008-12-04 17:31:01 [1968] [6] DEBUG: Thread 6 (gw/smsbox.c:http_queue_thread) terminates. 2008-12-04 17:31:01 [1968] [5] DEBUG: Thread 5 (gw/smsbox.c:url_result_thread) terminates. 2008-12-04 17:31:01 [1968] [0] ERROR: Error writing 12 octets to fd 21: 2008-12-04 17:31:01 [1968] [0] ERROR: System error 104: Connection reset by peer Then how do rectify this proplem,then where i have mention my receiver number,text message,after that how do i send message to any number,I dont know that procedure and all Please give me solution, with regards Kaliyaperumal.M *India* -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.kannel.org/pipermail/users/attachments/20081204/59f3cdaf/attachme nt.html ------------------------------ _______________________________________________ users mailing list [email protected] http://www.kannel.org/mailman/listinfo/users End of users Digest, Vol 31, Issue 14 *************************************
